Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gdmux stalls after a varrying number of lines in a largish file #2

Open
mentarus opened this issue Apr 23, 2014 · 6 comments
Open

gdmux stalls after a varrying number of lines in a largish file #2

mentarus opened this issue Apr 23, 2014 · 6 comments

Comments

@mentarus
Copy link
Contributor

Example that stalls gdmux here: http://hastebin.com/kidoqijeve.avrasm

@saljam
Copy link
Contributor

saljam commented Apr 29, 2014

OK, it's worth trying a smaller baud rate. baudrate is an argument to gdmux now.

@saljam
Copy link
Contributor

saljam commented May 5, 2014

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?

@mentarus
Copy link
Contributor Author

mentarus commented May 6, 2014

I'm not sure, can always test again!

On 5 May 2014 19:07, سلمان الجمّاز (Salmān Aljammāz) <
[email protected]> 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//issues/2#issuecomment-42218052
.

@saljam
Copy link
Contributor

saljam commented May 11, 2014

Still happening. I can sort of reproduce it. I think this will be my mission for the next week.

@mentarus
Copy link
Contributor Author

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) <
[email protected]> 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//issues/2#issuecomment-42773155
.

saljam added a commit that referenced this issue May 13, 2014
this works around issue #2, since when the serial line fails the V+ routines read in (0, 0, 0) which is now out of the arm's reach.

also, clean up the output and fix sign error for the clockwise/anticlockwise arc.
@saljam
Copy link
Contributor

saljam commented May 17, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants