Mini Integrated Developement Environment was programmed for helping developers to get quickly familiar with the usage of USB2.DLL and the USB 2.6 module from Braintechnology using Visual Basic Version 6.

Not all commands were shown, because many of them need to have custom hardware designs

connected to be proofed , such as I2C, SPI and some parallel port modes that require handshake signals from hardware.

The first step is to init a connected module by USBInit(), otherwise there is no firmware loaded and the module wonґ t work at all.

Also by experimenting/programming it can be possible that the module must be resetted

and initialized again. Keep in mind, that the module needs some seconds to be unplugged

and also Windows needs some seconds to enumerate the module again, before it is ready again to be accessed by software. This is normal but sometimes confusing.

-Mini Integrated Developement Environment was programmed for helping developers　to get quickly familiar with the usage of USB2.DLL and the USB 2.6 module from Braintechnology using Visual Basic Version 6.　

Not all commands were shown, because many of them need to have custom hardware designs

connected to be proofed , such as I2C, SPI and some parallel port modes that require handshake signals from hardware.

The first step is to init a connected module by USBInit(), otherwise there is no firmware loaded and the module wonґ t work at all.

Also by experimenting/programming it can be possible that the module must be resetted

and initialized again. Keep in mind, that the module needs some seconds to be unplugged

and also Windows needs some seconds to enumerate the module again, before it is ready again to be accessed by software. This is normal but sometimes confusing.