Thread: Fusion Control Centre MDX & Configurator -- Major Update 22/12/2008

The driver uninstall/reinstall went fine on my box.

I've been using FusionUSB.dll, but I'm looking at updating the code to support the new FusionBrain_WinUSB.dll. I found the dll in the MDX install, and I was able to add it as a reference in VB2008. I see the structure is quite different. What do I need to do to connect, send/receive, and disconnect?

Here is my new USB code: http://www.fusioncontrolcentre.com/M...cationClass.cs

This is what you call to connect to a device.

Code:

public static Boolean FindMyDevice(int Fusion_Index, int Fusion_Version) {...}

Fusion_Index is the n-th device you want to connect to. First brain, it is 0. Second brain it is 1, third is 2, and so on.
Fusion_Version is either 3 for version 3 or 4 for version 4

If it connects ok, it returns true. Otherwise it returns false.


To send a byte array to a device use:

Code:

public static bool SendAndReceiveViaInterruptTransfers(ref byte[] dataBuffer, int Fusion_Index, int Fusion_Version) {...}

dataBuffer is where the data goes. The byte[] you pass in goes to the Fusion Brain. What you get back from the Fusion Brain goes back in the same location.
Fusion_Index is the same as the index used to find the device.
Fusion_Version is the version of the brain to send to. 3 for version 3 and 4 for version 4




To dispose of all brains, call this:

Code:

public static bool Zombie() {...}

It disposes all FusionUSBDevice Instances currently handled by the dll



To dispose of a single device, then call the device's method

Code:

        public class FusionUSBDevice
        {
            public bool Internal_Zombie() {...}
        }

This will dispose of only that device.



-----------------------------


That is pretty much it. Much more simple.

Some key things to note is that the dll takes care of all the usb handles and everything. You just give an integer index and the dll takes care of everything else. Much less work.

you spelled center wrong.

Originally Posted by Quattro

you spelled center wrong.

Just depends on who taught you English.

Wow, that was easy. I updated the FBDemo program to support the new DLL. Currently it only works with the version 3 FBs. When the v4 gets here, I'll look into adding support for it into the FBDemo program.

-Lance

What is the byte format of the data going to and from the v4 FBs?

Code:

*******************************
* FUSION BRAIN V4 BYTE STREAM *
*                             *
* Deterministic Difference:   *
*     PID Suffix: E           *
*                             *
*******************************


**** ID CODE ****
Version 3a: VID_04D8&PID_000A
Version 3b: VID_04D8&PID_000B
Version 3c: VID_04D8&PID_000C
Version 3d: VID_04D8&PID_000D
Version 4:  VID_04D8&PID_000E


**** STREAM ****

Bytes
  [00-31] Digital Outputs 00 through 15
  [32-57] Analogue Inputs 00 through 12
  [57-59] Not Used Now, Maybe in future
  [60]    Number of Streams to Receive
  [61]    Initialize/Watchdog byte
  [62]    Hardware Version
  [63]    Firmware Version

Bits 0bMxxxxxxL | M = MSB and L = LSB
  Digital Outputs
    2 bytes per output
    [PPPPPPPS][TTTTTTMM]
      P = Value of PWM
        ([7bit Value + 1]/128)% duty cycle
        Details of full period to be determined later
      S = 1bit state
        0 = Off
        1 = on
      T = 6bits of Timer to shutoff --> [Evaluated Units in Seconds]
        If 6'bTTTTTT is 0, then shut off immediately on disconnect
        If 6'bTTTTTT is between 1 and 10 inclusive, then wait [6'bTTTTTT] seconds after disconnect
        If 6'bTTTTTT is 11, then wait 30 seconds after disconnect
        If 6'bTTTTTT is 12, then wait 60 seconds after disconnect
        If 6'bTTTTTT is 13, then wait 90 seconds after disconnect
        If 6'bTTTTTT is greater than 14, then wait ([6'bTTTTTT] * 10) seconds after disconnect
      M = 2bit Output Mode
        2'b00: Normal Full-Off or Full-On Operation Mode
        2'b01: Pulse Width Modulation Operation Mode
        2'b10: Yet to be determined
        2'b11: Yet to be determined
  Analogue Inputs
    2 bytes per input
    [index][index + 1] = [000000Mx][xxxxxxxL] | M = MSB and L = LSB
  Number of Streams to Receive
    1 byte
    [NNNNNNNN] | N = Number of streams to receive
      If [8'bNNNNNNNN] is 0 (default) then receive 1 byte and send 1 byte
      If [8'bNNNNNNNN] is greater than 0 then receive 1 byte and send 1 byte [8'bNNNNNNNN] times
        Each of these "extra" byte streams received may not coorespond with the details of this byte stream outline
        Each of the "extra" byte streams sent back to the PC may not coorespond with the details of this byte stream
  Initialize/Watchdog Byte
    1 byte
    [000000IF] | F = Flipping Bit and I = Initialize Bit
      F = Instead of flipping a bit in every digital output, flip 1 bit constantly
      I = Needs I high to turn anything on, just like default behaviour of byte[61] now
  Hardware Version
    [MMMMLLLL]
      M = Major Version. Currently Version 4, so MMMM = 0100
      L = Minor Version. Currently Version 0, so LLLL = 0000 
  Firmware Version
    1 byte
    [????????]

Well, my attempt at updating has been a giant leap backward.

I think I got the drivers loaded correctly since my v3 Brain doesn't show up under libUSB anymore. Its listed in Device Manager as The Fusion Brain Version 3 under Fusion Control Center.

When I run the Configurator, the one Brain I have connected shows up in the config file as a v3 which it is. When I go through the process of identifying it using the blinking LEDs, it works until I try to exit that at which point the configurator dies and asks if I want to send an error report.

When I start up FCC Uber MDX, it dies right away and asks if I want to send an error report.

I've completely reinstalled the sw from the FCC site (except for the updater because the installer complains it can't replace it and I don't seem to be able to get rid of it completely either).

Any suggestions?