-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
[FR]: RF2000 support #568
Comments
It would require some changes I think. Could you enable debug logging in the plugin's settings, restart octoprint and then do an update mesh process. Then share the plugin_bedlevelvisualizer_debug.log file from the logging section of OctoPrint's settings. |
Here is the log file. Doesn't contain much helpful info, though. |
I may have it working with the above commit. If you don't mind installing by copying/pasting the URL below into plugin manager > get more > ...fromURL and clicking Install and reporting back that would be great.
|
Thx a lot. We are almost there ;-) the current log:
|
Yeah, it's as i expected. The one line |
Hmm, not sure where these dots come from. |
yeah, that's similar to what I'm already using here, but since I'm supporting all kinds of firmware have to handle it slightly different and can't include the |
Thanks for your help. If I should test more and send you a log, please let me know. |
The firmware of my printer (Renkforce RF2000) is based on Repetier.
It supports bed scanning and can output the bed matrix like this using the GCODE command
M3013
.See also https://www.rf1000.de/wiki/index.php/GCodes
On the Octoprint terminal this looks like this:
M3013 P1
outputs this in [mm], without theP1
is in [steps]. I guess [mm] is more useful.The plugin is not able to understand this. Is there a way to make this working?
When using the commands for "GCODE Commands for Mesh Update Process"
I get this error:
which is most likely because it cannot interpret the firmware output correctly.
The text was updated successfully, but these errors were encountered: