Open mentarus opened 10 years ago
OK, it's worth trying a smaller baud rate. baudrate
is an argument to gdmux now.
I've not seen this happen since we pushed down the baudrate and switched to synchronous moves. Did you say it crapped out once? Was is the same error message?
I'm not sure, can always test again!
On 5 May 2014 19:07, سلمان الجمّاز (Salmān Aljammāz) < notifications@github.com> wrote:
I've not seen this happen since we pushed down the baudrate and switched to synchronous moves. Did you say it crapped out once? Was is the same error message?
— Reply to this email directly or view it on GitHubhttps://github.com/LHSRobotics/gdmux/issues/2#issuecomment-42218052 .
Still happening. I can sort of reproduce it. I think this will be my mission for the next week.
So it's more likely to be the 5v USB line where the interference starts. Try running GDmux on asimov, if you can't reproduce the problem there than it's almost certainly due to the USB-Serial converters
On 11 May 2014 16:12, سلمان الجمّاز (Salmān Aljammāz) < notifications@github.com> wrote:
Still happening. I can sort of reproduce it. I think this will be my mission for the next week.
— Reply to this email directly or view it on GitHubhttps://github.com/LHSRobotics/gdmux/issues/2#issuecomment-42773155 .
This doesn't affect asimov with the hardware serial port. So it's either the USB serial adapter or something more sinister on the Pi.
I'll keep the issue open till that's sorted.
Example that stalls gdmux here: http://hastebin.com/kidoqijeve.avrasm