Ok, after working my arse off for a month tackling the evil that is Vista, I have finally won. It was a very difficult victory, and I had to actually ask for help in creating a new dll interface for the low level USB calls which is definately not my speciality. I would like to take the time to thank
Gudon Malamud, a very good dll library programmer, that allowed me to pick his brain for about 3 weeks.
Ok, so first off, this new release (if it wasn't apparent immediately
) completely changed the way the Fusion Brain talks to the PC. For most people, they dont care as long as it works, and that is fine. It now works.
Before we had distinguished seperate Brains via their VID/PID combination. This method was easy to program for, but a pain in all other aspects. It means you cant have 2 Brains with version 1 on the same PC. Well this is no more. The vid/pid now does what it is supposed to be used for. A Vendor ID and a Product ID. XP and Vista create "instances" of devices each time you plug it in. This is why your computer doesnt have to reinstall your printer every time it restarts or you power cycle it, yet can have 100 of the same make/model printer connected and choose which you print too how you want. I have done the same thing.
These instances each have an "Instance ID" which is a very boring string of numbers and ampersands like this:
5&38631973&0&1 This is unique to each device plugged into a unique hub. So the average Fusion Brain user will only have 1 connected to some port. You will only have 1 instance. But if you have 3, you can now choose which to send to.
The coding behind multiple of the same VID/PID is not yet there in this beta release, but all the architecture is there. Right now it needs a unique instance ID per unique VID/PID. This will be abolished within the next few weeks when this release goes post-beta.
Now to find this instance ID, you need to go to your Device Manager, and select it from the driver's details tab's dropdown. (That's a lot of possessive nouns!
)
Now you need to take this ID, and put only the ID part (in the above it is
5&38631973&0&1) in a file named VIDPID.inf so in the example it would be into a file called "
VID_04D8&PID_000C.inf".
So this should set everything up correctly.
I have the entire installation procedure documented in the "ReadMe.txt" file.
You can download the new drivers and new software here:
ZIP:
http://www.fusioncontrolcentre.com/T...a%20v2.0.0.zip
RAR:
http://www.fusioncontrolcentre.com/T...a%20v2.0.0.rar
This is in beta right now. If there are any errors, please let me know.
Some things I added is allow an analogue input to be used as a digital input for controlling digital outputs. What I mean is thatyou can connect a button from the +5v to v_input on an analogue sensor, and using the configuration options, you can either have:
(a) An output that is on as long as the button is held down
(b) Toggle the state of an output every time the button is pressed
The logging right now is turned off as I develope it.
Digital inputs have sort of been finicky right now so they may not compltely work.
But the biggest improvement is the driver, and the biggest change is the install procedure.
Make sure you completely uninstall the old driver first.
READ ME.txt