Topics created by DaveA

@DaveA this is now fixed in time for the next 3.6 beta release. Thank you for reporting it.

m36 "1732895968432-reservoirspacer-1mm.gcode" { "err": 0, "fileName": "1732895968432-reservoirspacer-1mm.gcode", "size": 100995, "lastModified": "2024-12-01T08:49:22", "height": 1, "layerHeight": 0.2, "numLayers": 5, "filament": [ 824.1 ], "thumbnails": [], "generatedBy": "Simplify3D(R) Version 4.1.2" }

@DaveA it may be spurious but it would be worth checking the wiring on driver 0

@jay_s_uk Oops, you're right. I missed that. I do wonder why 3.4.5 didn't seem to care - didn't produce
any error and printed the purge line just fine.

Thanks.

@gaweyo That works except I'm not always wanting to immediately print the file I'm uploading. The M23 selects the file and generates an error if the printer is already printing.

Anyway, never mind.

I confirm that the 12864 encoder does not work in RRF 3.3beta1 for the Maestro. I will fix it in beta2.

I've updated the M540 entry

@Phaedrux I think so.
This is the current M307 that's running on the printer now and seems to control the bed well.
M307 H0 R0.196 C734.056:734.056 D0.65 S1.00 V12.1 B0

This is config-override.g from a backup I made in June, 2020
M307 H0 A172.9 C784.9 D0.4 S1.00 V11.9 B0

At the fourth try the tune returned a result:
Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 3 idle and 25 tuning cycles in 3280 seconds. This heater needs the following M307 command:
M307 H0 R0.223 C738.8 D0.64 S1.00 V12.1

The values appear to not be very much different from the current M307.

I captured a portion of the temperature chart. The whole tune cycle looked like this portion. A gentle sawtooth moving between 65 and 70 degrees. I never saw anything that looked inconsistent.

d3492461-39d4-47c4-9ce4-053fe8e706c5-image.png

@DaveA I already do something similar. You can use the workplace coordinates to same information and then calculate from.
I mainly use this when probing on my CNC. Examples can be found here https://forum.duet3d.com/topic/19698/rrf3-2-request-to-enable-g43-g44-tool-height-offset?_=1609278343985

@DaveA thanks for doing that testing.

This might be one for @chrishamm to take a look at.

I'm not certain but that may only apply to a single G30 and not G29. Just speculating.

Regardless, I would suggest that if you're going to use the A parameter, use a larger value for retries like 10.

Thanks. I looked around the Duet doc. site but I guess I missed it. This is for a Duet Ethernet 1.02.
Great Amazon can sell me 100. I'll keep looking.

@dc42 Same here now. I just powered up the printer and the PanelDue is working fine @115200 with the two M575 entries. Not sure what happened last night. Maybe I didn't really reboot after editing the config file. Anyway, all is well for now.

@demonlibra you can get RRF to ignore that line by putting a command starting with ;E or ; E at the end of it.

@deckingman Thanks for the idea. I'll do that.

I believe this is a known bug. See post

Well there were some bugs in 2.03 with delta calibration.

Thanks, that was it. I just assumed (I know) that if I had only one tool that I wouldn't need to specify it.

@davea
Please Note: while I am certain that this will be seen and replied to by Duet. They do have a different forum for Requests. I posted my request to this forum too... -Not that I think my opinion matters much to Duet, owning only one Maestro. I think this is a useful feature to request, but how best to implement is the difficult question.

I think this should be added as a global OPTION. To make it enable confirmation for all or most buttons or always off.

I have seen similar function added to many other interfaces, and I appreciate when feature like this are enabled by choice as sometimes they are useful and some times not.

I think that this could be added as a per feature enabled but I could imagine the over head to the code would be nuts complicated, never mind the interface changes.

I think that the feature could be added to a more specific set up functions rather than blanket all, always on or always off.
~ However this may require some sort of community conversation as to what buttons should come with a confirmation.