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

Fix communication with standard reprapHost-Software #135

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

jschleic
Copy link
Contributor

I'm currently using Sprinter together with the standard reprap host software at [1](version 20111115). There are several modifications required to make this host software communicate with Sprinter.
One problem is, that the host software gets confused with line numbering if several lines are returned as reply (like in the 'unknown command' or temperature reporting case of M109).

According to http://reprap.org/wiki/G-code#Replies_from_the_RepRap_machine_to_the_host_computer
there should be only replies starting with one of 'ok', 'rs', '!!', '//'. So I modified replies not starting with ok to be comments starting with '//' and modified the M114 reply to be consistent with the host software and with the format reported by M105.
Please test those modifications with your host software and merge them into master, if appropriate.

[1] https://github.com/reprap/release

The host software obviously expects ok and the coordinates
to be in the same line and the coordinates separated with spaces.
to work with standard host software
According to http://reprap.org/wiki/G-code#Replies_from_the_RepRap_machine_to_the_host_computer
replies have to start with one of 'ok', 'rs', '!!', '//'.
Actually the current RepRap standard software fails
communicating with Sprinter, because it sends 'T0' in
the beginning to select a Extruder.
use spaces as indentation consistently
@jschleic
Copy link
Contributor Author

jschleic commented Mar 3, 2012

Any comments / progress on this?

What host software(s) are you using?

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

Successfully merging this pull request may close these issues.

3 participants