Personal tools
You are here: Home Issue Tracker Weird communication behavior
Document Actions

#4 — Weird communication behavior

State Resolved
Release:
Area Core Software
Issue type Bug
Severity Critical
Submitted by sirloon
Submitted on 2006-11-29
Responsible Sébastien Lelong
Target release:
Return to tracker
Last modified on 2007-03-02 by Sébastien Lelong
While using the console, weird communication problems can occur (but they are not quite easily
reproductible...):
- no pong after a ping
- flushed chars where not expected
- problem with echoes
- ...
Should have a look on a the whole com process...

The Read-Timeout of the RS232 module is important in the communication process.
Set to 0 for optimization (flush of chars took too long), read chars becomes
unreliable (not enough time to read). This impacts the flush, and seems to
explain the weird com. behavior.
To be more analysed...
Added by sirloon on 2007-01-11 09:59
Issue state: unconfirmedopen
Added by sirloon on 2007-01-11 10:50
Issue state: openresolved
Severity: ImportantCritical
not reproductible
The read-timeout setting seems to be the solution
Added by Sébastien Lelong on 2007-03-02 20:27
Issue state: newunconfirmed
Responsible manager: sirloonadmin
Added by Sébastien Lelong on 2007-03-02 20:27
Issue state: unconfirmedopen
Added by Sébastien Lelong on 2007-03-02 20:28
Issue state: openresolved
not reproductible
The read-timeout setting seems to be the solution

Powered by My Hands Powered by Jalv2 Hosted by Google Code