The first time that you connect your TUSBA in your computer, you will take notice
about really your TUSBA are several devices living in the same hardware. In fact,
inside your TUSBA there are:
- A Boot system, to allow you to update TUSBA with new firmware.
- A HID Game Device, to let you communicate TUSBA directly with MS operating
system and let you control your simulator or some other game with DX axes and
buttons.
- Two additional comms ports for special comms with the device.
As soon as you connect TUSBA, MS operating system will detect it and will start
looking in its data base to install the appropriate drivers for it. As you know, from the
FSSB R3 we have avoided custom drivers or additional special system in order not to
have any problems in the future with new MS operating systems. Just as you know,
every time MS improve its OS, all of us have a headshake with incompatibilities,
drivers, etc. so we have learnt from the past, that the best is to use the own legacy MS
drivers for comms and this is what we have done in the TUSBA system, use only MS
drivers, so when you connect your TUSBA to the computer, MS will look in its data
base for the best MS driver for it, in fact its own HID drivers.
The first device to look for drivers is the TUSBA Boot system, and a few seconds after
taking comms with MS, the TUSBA Boot will left the system and will be disconnect to
allow working the Game device and additional Comms ports. You will see as this USB