-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
[Bug]: Doesn't work with Snapmaker 2.0 A350 #65
Comments
The problem here is that the firmware has messed with the format of the response. A typical M503 response looks like this:
The key difference is the missing |
@DavidKuhn136 did the above comment clear things up for you? |
I am considering this issue solved - if you have more questions please ask. |
Description of the bug
When I tried to load the eeprom for the snapmaker 2.0 a350, it didn't pull in any information. I can only see "Firmware Info"
If i run M503, it pulls back all the information in the terminal, but I can't get the EEPROM editor to work. I have an 11x11 grid for bed calibration set on the snapmaker, so not sure if that is the issue.
As an FYI, I also have this installed on another instance with an Ender 3 and it is amazing!
this is what is coming back from "Firmware info":
Firmware Name: Marlin SM2-4.4.16 (Github)
Source Code Url: https://github.com/whimsycwd/SnapmakerMarlin
Protocol Version: 1.0
Plugin version
3.2.0
OctoPrint version
1.8.1
M503 Response
API Response
OctoPrint logs
octoprint.log
The text was updated successfully, but these errors were encountered: