This app has been updated to support the new drivers, which has really cleaned up the code. It also supports both the v3 and v4 fusion brains, and by default does an auto-detect.
It will first try to connect to the first v4 FB, and if that fails, it will try to connect to the first v3 FB.
PWM and Timers haven't yet been implemented in the released firmware of the v4, so I haven't tested those. I think I have written all the code to support that, but obviously haven't tested it.
The links in the original post of this thread link to the new version.
This is good stuff!
Stole your work and modified it to work with both a v3 and v4 at the same time (having difficulties with MDX at the moment). Not completely sure it works with both or with the v4 (v4 is in the mail) yet, but it should pending a little debugging. Anybody that want's it, send a PM or email.
On the downside, you're gonna get me fired as I've spent more time the last 3 days learning how to use VB2k8 than working. Good thing the auto industry isn't doing anything right now.... Can't believe how easy it is to use VB2k8 Express - practically tells you how to write the code vs VB6.
Any idea why this code sets FoundFBv3 & holderv3=true when only a v4 is connected? Works correctly with only a v3 connected - something in firmware version? The effect is also weird - everything seems to work normally, but it sets the first 6 outputs to on (at least the LEDs flash, might be resetting them faster than they can all be set on?)Code:
For i = 0 To 1
FoundFBv4 = FusionBrain_WinUSB.MainUSBClass.FindMyDevice(i, 4)
If FoundFBv4 Then
FBv4 = i
holderv4 = True
FoundFBv3 = FusionBrain_WinUSB.MainUSBClass.FindMyDevice(i, 3)
If FoundFBv3 Then
FBv3 = i
holderv3 = True
I never really got any feedback since I had released the latest version of the app, and my testing only included the brains I have. It is entirely possible you have a different firmware version on the v3 that is acting a bit different than mine.
The outputs shouldn't be on unless you turn them on with the red/green buttons. The byte stream for v3 and v4 are different, so if a v3 brain gets detected as a v4, it will be sent v4 data which might make it do odd things with the outputs.
The odd behavior of the first 6 outputs is due to the v3 vs v4 byte structure (i think) commenting out the v3 code that sets the bytes for the outputs stops the issues. that doesn't help me though- FindMyDevice(0,4) is picking up the v3 brain & I don't know why. Is there any other way to differentiate between the 2 different versions?
Oh, yeah, I saw that bug too. The .dll is reporting that it found a v3 FB when there isn't one on the system. I think I reported it to 2k1, but I never pushed it any further.
As I recall, I can open the app and it will connect correctly the first time, but disconnect and reconnect again and it detects it wrong. Close the app and reopen it and all is well again.
Has anyone had any luck getting mx270a's great app running on a 64 bit machine?
It works great on a generic x86 PC (WinXP) but I haven't had any luck with a 64 bit Win7 computer. I tried the drivers that www.fusioncontrolcentre.com, including the "AMD64" driver, but no luck.
If I plug the brain into the Win7 it ask for the driver. OK, navigated to a folder with the fusioncontrolcentre drivers in it and hit OK. Drivers appeared to install OK, at least it didn't give any error messages.
The brain now shows up in device manager, which claims it is "working properly".
Tried mx270a compiled demo. It starts up OK but complains that it can't find the fusionbrain.
Anyone have any thoughts?
I also tried opening up mx270a source in VisualBasic 2008 Express and recompiling. No go, the program's GUI comes up just fine but it still can't find the brain.