Can I get current status on these outstanding issues?
-
- M37 Simulation
- Missing Machine Model Items
- Heater Model and saving via M500
- Job
- layer
- layerTime
- layers
- timesLeft.filament
- timesLeft.layer
As always, I'd like to help get these things implemented but it's hard to do that without knowing whether you want them implemented in RRF or DSF or both, and what you already have in the works for the model.
-
These are awaiting implementation in DSF. M37 is due to be implemented shortly. @chrishamm may be able to provide further details.
-
Oops, one more...
"duration" : 0, "extrudedRaw" : [ 1302.6 ], "file" : { "filament" : [ 1254.9 ],
Should extrudedRaw be greater than filament on a stopped print?
-
@gtj0 said in Can I get current status on these outstanding issues?:
Oops, one more...
"duration" : 0, "extrudedRaw" : [ 1302.6 ], "file" : { "filament" : [ 1254.9 ],
Should extrudedRaw be greater than filament on a stopped print?
Yes, if either the value written by the slicer is not accurate, or you have increased the extrusion factor, or you are using firmware retraction with a additional extrusion on reprime.
-
@dc42 said in Can I get current status on these outstanding issues?:
Yes, if either the value written by the slicer is not accurate, or you have increased the extrusion factor, or you are using firmware retraction with a additional extrusion on reprime.
Extrusion factor, that was it, thanks!
-
@dc42 said in Can I get current status on these outstanding issues?:
These are awaiting implementation in DSF. M37 is due to be implemented shortly. @chrishamm may be able to provide further details.
@dc42 since there's no RRF support in the object model for heaters yet, are you expecting that the DSF would just issue an M307 and parse the text results?
-
@gtj0 said in Can I get current status on these outstanding issues?:
@dc42 said in Can I get current status on these outstanding issues?:
These are awaiting implementation in DSF. M37 is due to be implemented shortly. @chrishamm may be able to provide further details.
@dc42 since there's no RRF support in the object model for heaters yet, are you expecting that the DSF would just issue an M307 and parse the text results?
No, I will shortly be adding more OM support to RRF. I'm finalising the RRF 3.0RC1 release first, and hope to release it on Monday. It includes a refactoring of the in-application programmer to make additional space available, which is a prerequisite for conditional GCode and the enlarged OM.
-
@dc42 said:
These are awaiting implementation in DSF. M37 is due to be implemented shortly. @chrishamm may be able to provide further details.
I must have misunderstood.
Ah well, I'll just chuck away the last 7 hours of work.And this is why I said...
it's hard to (contribute) without knowing whether you want them implemented in RRF or DSF or both, and what you already have in the works for the model