You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sending a command that typically returns answer slower than other commands. Interesting thing is that if i am in debug and i stop for 5 minutes before trying to read and then i read, the answer is returned as expected, but if i start reading in a loop immediately the answer never comes even if i wait for 10 or 15 minutes. If i put tread.sleep for 5 minutes before the read() again answer never comes. If i use SerialInputOutputManager for event-driven read again the answer never comes. I tried different baudrates but the result is the same. I downloaded the UsbSerialExample project and there the command takes some time and then return answer as expected. The expected answer is 908 bytes.
Here is the code i am using. If i send a command that returns answer faster there is no problem. Code example.txt
I am sending a command that typically returns answer slower than other commands. Interesting thing is that if i am in debug and i stop for 5 minutes before trying to read and then i read, the answer is returned as expected, but if i start reading in a loop immediately the answer never comes even if i wait for 10 or 15 minutes. If i put tread.sleep for 5 minutes before the read() again answer never comes. If i use SerialInputOutputManager for event-driven read again the answer never comes. I tried different baudrates but the result is the same. I downloaded the UsbSerialExample project and there the command takes some time and then return answer as expected. The expected answer is 908 bytes.
Here is the code i am using. If i send a command that returns answer faster there is no problem.
Code example.txt
` public byte[] SeekUSBDeviceAndSendCommand(boolean fiscal)
{
UsbManager manager = (UsbManager) App.currentActivity.getSystemService(Context.USB_SERVICE);
return null;
} `
The text was updated successfully, but these errors were encountered: