Thread: RRFusion- My Fusion Brain plugin for RR

If you need another tester let me know, have FB working in the car with 2 temp sensors.

Very excited about this plug in, thanks for your hard work Sonic.

working in car = you get to test too lol. pm'ing link now

Maybe I'll pull mine out and blow of the collected dust and give this a try sometime in the near future..

couple of other tidbits i should note:

-there is currently no support for digital INPUTS. Quite honestly i dont even know what they are lol
- i have NO IDEA how i'm going to make this plugin work for those people who have more than one fusion brain. I think eventually i'll have to make this .dll callable from a rrfusion2.dll etc etc to create multiple instances.

Originally Posted by Sonicxtacy02

couple of other tidbits i should note:

-there is currently no support for digital INPUTS. Quite honestly i dont even know what they are lol
- i have NO IDEA how i'm going to make this plugin work for those people who have more than one fusion brain. I think eventually i'll have to make this .dll callable from a rrfusion2.dll etc etc to create multiple instances.

The way you handle it is in iterate through the instances, and call initialize and free everytime you send. So 2 brains, intiialize 1 send/receive 1, free 1, initialize 2, send/receive 2, free 2, initialize 1, ... repeat. And of course for however many there are.

Now this can get slow. So to combat this, I keep the last instance string in a temp variable. So when it goes to initialize, it checks if the brain it is going to initialize is the one it already had (meaning only 1 connected). If so it passes back true for initialized. Now if it is different, then it frees the old one, and connects the new one. and so forth. So for 1 brain it is fastest because it only initializes once and frees once. But for 2 you have to do one at a time unless there is some voodoo magic I am not aware of.

Oh, and a digital input is an input that can only be true or false (0v or 5v) 2.4999 volts gets rounded to 0 and therefore false (binary 0). 2.5v gets rounded to 5 and therefore true (binary 1).

So you can think of it as a 1bit analogue input, which essentially it is.

Originally Posted by 2k1Toaster

The way you handle it is in iterate through the instances, and call initialize and free everytime you send. So 2 brains, intiialize 1 send/receive 1, free 1, initialize 2, send/receive 2, free 2, initialize 1, ... repeat. And of course for however many there are.

Now this can get slow. So to combat this, I keep the last instance string in a temp variable. So when it goes to initialize, it checks if the brain it is going to initialize is the one it already had (meaning only 1 connected). If so it passes back true for initialized. Now if it is different, then it frees the old one, and connects the new one. and so forth. So for 1 brain it is fastest because it only initializes once and frees once. But for 2 you have to do one at a time unless there is some voodoo magic I am not aware of.

got it... now how does the registry get set for multiple instances? i'm guessing the "0" key means the first instance and if 2 brains are connected it will add a "1" key?

Originally Posted by 2k1Toaster

Oh, and a digital input is an input that can only be true or false (0v or 5v) 2.4999 volts gets rounded to 0 and therefore false (binary 0). 2.5v gets rounded to 5 and therefore true (binary 1).

So you can think of it as a 1bit analogue input, which essentially it is.

understood... i can code the digital INs with a simple boolean riddle then.

Originally Posted by Sonicxtacy02

got it... now how does the registry get set for multiple instances? i'm guessing the "0" key means the first instance and if 2 brains are connected it will add a "1" key?



understood... i can code the digital INs with a simple boolean riddle then.

digital inputs will be gone in the next version since any analogue input can be used a digital input, but a digital input is locked to digital only.

Also the FCC software does nothing to the registry other than put in where it was started from so the updater can update all instances.

The keys in the registry are created by windows. And there is no method to its madness. That is what the huge VID/PID/InstanceID string is in the device manager and it is uniquely assigned to each device, but not something that can be guessed. There is a function in the dll to try and get all device instances connected so you could try to use that. But I dont use it as it doesnt work all the time.

Originally Posted by 2k1Toaster

digital inputs will be gone in the next version since any analogue input can be used a digital input, but a digital input is locked to digital only.

Also the FCC software does nothing to the registry other than put in where it was started from so the updater can update all instances.

The keys in the registry are created by windows. And there is no method to its madness. That is what the huge VID/PID/InstanceID string is in the device manager and it is uniquely assigned to each device, but not something that can be guessed. There is a function in the dll to try and get all device instances connected so you could try to use that. But I dont use it as it doesnt work all the time.

well that might be a problem. I may have to change the my plugin so that u can manually enter a instance #. I dunno.. i'll wait til the second FB comes to see if i can see how windows creates its instances. Its good to know that FCC doesnt add the registry entry. That means FCC is officially NOT required for this plugin to work.