Posts made by Phaedrux

Are they displaying correct on the web control?

What exactly are you seeing on the PanelDue? Photo?

Can you describe the heater layout for the printer?

Can you post an image of your heightmap and the bed.g and config.g files so we can see what it's actually doing?

To read mcu and driver temperatures on an expansion board connected to a Duet 3 mainboard, put the CAN address at the start of a dummy P parameter. For example, a board at CAN address 1 would use:

M308 S12 Y"mcu-temp" P"1.dummy" A"3HC MCU"
M308 S13 Y"drivertemp" P"1.dummy" A"3HC Steppers"

https://docs.duet3d.com/User_manual/Reference/Gcodes#m308-set-or-report-sensor-parameters
See the tab for MCU and driver temp

How are you testing?

Please try this guide: https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors

Please share your config.g start.g and your cura start code.

@cichaczech said in [3.6.0 RC1] MultiMotor Z bed leveling:

May there be problem with Bltouch? I do not know.

One way to check that would be to switch to probe type 0 (M558 P0) to use manual probing where you get prompted to jog the nozzle down to touch the bed. This would isolate any bltouch issues.

@jltx You can still send M997 S0 to flash the firmware if you've uploaded it. And you can use P to refer to the file name directly if it isn't the default.

@jltx said in SZP for bed level in 3.6-RC1:

@Phaedrux said in SZP for bed level in 3.6-RC1:

https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup#update-firmware

I know how to do that when the firmware is via a depot but this is from a dropbox so I assume there is a manual procedure. Do I need to sftp them over?

Are you already on the unstable branch? If so, you should be able to upload the bin file and send M997 to flash to it. See here for parameter details for M997 in SBC mode.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

@jltx said in SZP for bed level in 3.6-RC1:

@droftarts I can't get that firmware to load with my SBC. Maybe I'm doing it wrong. I don't see any sbc file. I may have to wait for official release to try.

See here for updating your firmware with an SBC.

https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup#update-firmware

@Timothee-Leblond said in Disabling filament retraction?:

@Phaedrux

I'm not using any slicer, I've a custom script in Grasshopper that transforms a path into Gcode.
Thats why I'd like to know how to configure retraction. Do you know what command should I use?

M209 is not working in RRF although it was on Marlin.

Best,

Can you share one of these gcode files?

I'm not really clear on what you're trying to do.

@gsch1803 said in Unresponsive duet 3 6HC board:

@Phaedrux I believe it was purchased from Amazon in October

Who is the amazon seller?

That would be up to your slicer to decide when a retraction occurs. Or if you have your slicer set to use firmware retraction, you could then configuring config.g to use a distance of 0.

To start I would suggest disabling microstep interpolation and try x64 microsteps.

I assume the pen movements would be fairly slow speed, so you shouldn't run into skipped steps hopefully.

When and where did you purchase the Duet?

You can try to increase your microstep size with m350 and recalculate your steps per mm in m92 at the expense of top speed.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m350-set-microstepping-mode

But I still think you're likely to run into rigidity issues. 3d printing is generally a zero contact point process so the print head doesn't make contact with a hard surface and ideally doesn't suffer from contact deflection, but with a plotter you are dragging a tip across a surface. Delta aren't known for their rigidity.

Have you done any testing yet to see what is possible with your current setup?

I'm inclined to think it's a mechanical issue either in the extruder or Z axis.

@luca-Massimiliano said in Definition of movements:

parallel lines 0.01mm apart

I would suspect that you'd lose enough in mechanical backlash to make that level of precision nearly impossible. I think it will depend a lot more on the rigidity of your printer than any other limitation. The Duet will try and move the printer in accordance with the resolution of your gcode file and within the mm per step resolution.

@meki05 said in Calculating average temperature using 2 pt1000 sensors:

Error in start-up file macro line 78: Unknown sensor type name "mavg".

@meki05 said in Calculating average temperature using 2 pt1000 sensors:

M308 S4 Y"mavg" A"Average Bed Temp" S"1:2"

mavg is not a valid type of sensor for the Y parameter.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m308-set-or-report-sensor-parameters

You can create the sensors independently and take the average as you are doing and use that in other calculations, but you can't feed that back into the config as another sensor itself. You'd have to use some custom logic in daemon.g to deal with that average value as needed.

@thomasvanderwal said in Duet 2 v1.02 not responding:

Calibration is now the problem. After setting the trigger height and z0 I wanted to Run Delta calibration. This is going well. But the mesh compansation is not going well : Error: G29: Probe was not triggered during probing move
The nozzle even goes besides the bed? I have in config.g : M557 R95 S10. The bed is 20cm in diameter,

As this thread is now well over 100 posts and does not match the description and initial issue, I think you'd have better luck starting a new thread for your delta calibration issue. You're more likely to get some helpful delta users to lend a hand with calibration.

Have you set M669 S1 T1 in config.g first?