From: Stephen W. <sa...@us...> - 2004-02-22 15:37:56
|
I am experimenting with the Sanyo SCP-5500, starting with understanding the phonebook protocol first. There are strong similarities with the protocol for the other Sanyo phones. The headers are larger and the packets are bigger, but the hex codes in the headers for different packets are usually the same and the payload formats are similar. I'll probably be able to reuse a lot of code. When reading the phonebook, I will get a timeout at a random place. The retry hack used for writing to the other Sanyo phones does not help. I worry that this is a similar problem to those experienced with the VX4400 when using the straight through cable. Is there a clean way to trap communications timeouts so that I can try reinitializing communications or such? Stephen 9:41:40.729 /dev/input/ttyACM0: Timed out - flushing and trying again 9:41:43.731 /dev/input/ttyACM0: Timed out - flushing and trying again 9:41:46.733 /dev/input/ttyACM0: Timed out waiting for 7e, requested bytes 1 - 0 bytes read 9:41:46.733 Error: Device needs attention - SCP-5500 on /dev/input/ttyACM0 SCP-5500 on /dev/input/ttyACM0: The phone is not responding while manipulating the phonebook. |