Open noobydp opened 7 months ago
Hey, I will have a look to see if there is a possibility to update the parser of the different data objects. However, I think there will be more parsing errors after we fix this one.
The error you posted above is actually caused by the gcode_move
object (The toolhead will fail too tho).
Can you provide me the query response of the gcode_move /printer/objects/query?gcode_move
?
Thank you, I'm happy to help/test, but my dev skills are pretty limited.
/printer/objects/query?gcode_move
{
"result": {
"eventtime": 41.543546703,
"status": {
"gcode_move": {
"speed_factor": 1.0,
"speed": 1500.0,
"extrude_factor": 1.0,
"absolute_coordinates": true,
"absolute_extrude": true,
"homing_origin": [
0.0,
0.0,
0.0,
null,
null,
null,
0.0
],
"position": [
0.0,
0.0,
0.0,
null,
null,
null,
0.0
],
"gcode_position": [
0.0,
0.0,
0.0,
null,
null,
null,
0.0
]
}
}
}
}
Feature Request
I use the fork "klipper-for-cnc" https://github.com/naikymen/klipper-for-cnc on my CNC router, but it has support for additional axes "XYZABCE". I'd like to use Mobileraker as a mobile client, but it throws errors when adding the machine.
Problem Description
I believe the issue is caused by a change in the toolhead object which has additional values for the axes, even for machines with only XYZ movement axes (like mine) The toolhead object includes null or numeric values for the ABC axes.
i.e. from /printer/objects/query?toolhead data
Proposed Solution
I'm not sure if the position data for the ABC axes is important (as I don't have them installed right now). Extending the Mobileraker UI to show/support the additional axes sounds like a ton of work (although the ideal solution), but it would still be great if we could use Mobileraker and have it ignore the ABC axes.
Alternatives Considered
Since I only use XYZ right, I considered requesting changes in the klipper-for-cnc fork to send a compliant object, however adding the ABC axes in the future would break the app again. I may add another axis soon so thought adding support here would be better long term.
Additional Context
Errors from the app:
Checklist To help us understand your feature request, please ensure you've covered the following points:
Your input is valuable in shaping the development of our project. Thank you for taking the time to submit your feature request!