On 31 October, 2016 - Willem Ferguson wrote: > On 31/10/2016 22:01, Anton Lundin wrote: > >I think you did some snafu there, and didn't capture a log file > >using the ftdi driver? (or overwrote your log file...) The ftdi > >log file should start with: INFO: Open: name=ftdi Anyhow. The same > >"error" shows up in these log files, so I'm confident that this is > >just a quirk of the oceanic_atom2 protocol. There are quite a bit > >of retry / error handling in the code so I don't think there is > >anything to worry about. I would love to see a real ftdi log from > >that computer anyway... //Anton > Apologies. I need to keep a few balls in the air, including the > character device number that changes when I reboot. > > Here it is. >
Awesome. Looking great. It should just work<tm> on Android to. > INFO: Open: name=ftdi > INFO: Configure: baudrate=38400, databits=8, parity=0, stopbits=0, > flowcontrol=0 .. > INFO: Custom Write: size=0, data= > INFO: Custom Read: size=1, data=A5 > ERROR: Unexpected answer start byte(s). [in ../../src/oceanic_atom2.c:479 > (oceanic_atom2_packet)] > INFO: Sleep: value=100 > INFO: Purge: direction=1 > INFO: Sleep: value=1 > INFO: Custom Write: size=0, data= > INFO: Custom Read: size=1, data=5A The error recovery path looks the same, so thats probably a quirk of the protocol. Just as I guessed. Nothing to worry about. //Anton -- Anton Lundin +46702-161604 _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
