, as follows: 1. The Android client and control board boot, connected to the USB line, the control panel to send a set of byte [16] content to come over, found that the inside of the data length is 16 but data into gibberish
Such as panel actually send data is AA 00 00 01 00 00 00 00 00 00 00 00 02 81 78 25 after four CRC32 checksum but Android depending on the print receipt data will become a AA 00 00 01 C0 FF 00 00 00 00 00 00 02, 81, 78, 25 control panel connected a serial printing connect the USB cable under the Windows use tools to see data are normal, this is what the Android client accept to will become like this, is the USB line is different material lead to data transmission interference received?
2. Receive data, there was an obvious delay about 2 s print information, this is hid blocked communication?
3. Hid in the process of communication, if the hardware side crash, restart the system, after a reboot, then send instruction to Android, Android end don't get any printed information, this is because hid the load driver has been changed, pointing or before that, so don't get the data?
4. The USB hid communication connection is not very stable, now you have what good advice or demo or third party jar package communication framework of communication such as recommended?
Help you greatly help me slag/tears!