Max wrote:I was able to switch OFF/ON LED. As I click on Switch ON, then Input HEX reads: 1 b1, and 1 b0 for OFF.
Ok, the first byte "1" is for the amount of useful bytes in the transmission.
"xb1" is the "acknowledge" of the instruction "x41" because the response is created by adding 0x80 (setting the msb) to the request.
((( "x41" is for LED_4 ON and "x40" is for LED_4 OFF )))
Max wrote:But when I click Device or Version, it reads: 1 ff, for both the options. And it doesn't display the info in the software. So something might be wrong in passing input from the software to the circuit, I guess?
0xff means ERROR (unknown command)
I guess this is because I changed the command IDs. In the early versions the Device was x10 and the vesion x11.
Now they are 0x0f for the device and 0x0e for the version. There is a hint in post #4.
You can easily check this if you use the "HEX OUT 1" and "HEX OUT 2" buttons on the first tab which are preset with these comands.
<edit>Sorry, of course you have to edit them to 0x10 and 0x11 then </edit>
Max wrote:BTW, which USB driver did you use for implementing your software? Did use Windows' built-in HID drivers to communicate with device?
I use Alan Ott's HID-API which can be used for Win, Linux and MAC OS. It uses the Windows build-in HID driver ...