Topics created by jrsphoto

@Phaedrux Thank you, how did I forget this? Anyway, I updated the post.

-John

@dc42 They indeed are Dave. I believe I got them from MaterHackers.

Glad you figured it out. Occasionally the wifi server firmware update appears to complete successfully but it actually did not and there's no indication from the module that this happened. Sending M997 S1 again manually to reflash usually solves it by flashing again successfully, but it is annoying when it happens unexpectedly during a firmware update, especially when wifi is your only means of communication with the Duet. USB or PanelDue are the only option to reflash.

@jrsphoto said in Trying to figure out dual-z motors with independent drivers:

Its it best if my G30 probing locations are equidistant from X center? Just wondering as with my probe on the left side of the extruder, I can probe the far left edge of my bed.

If the bed is flat, it doesn't matter. In theory the probe points can be anywhere you like, but the more area of the bed that the probe points enclose, the better.

@jrsphoto The ability to set negative numbers with M208 allows the firmware to know exactly how far off the bed the carriages can move. This is important if you have an offset probe, because you may need to probe a point close to the edge, which causes the nozzle (which is usually the reference point) to be off the bed. The firmware will know if it's possible for the probe to reach that point, because of the M208 settings. Perhaps it's best to think of M208 as showing the 'bounds' of the machine, while the numbers show where the bed actually is relative to the homing positions.

When printing, it's the job of the slicer to generate code that keeps the printer within the boundaries of the bed. There are some exceptions (eg delta printers have a 'print radius' in config.g), so setting up the slicer correctly also helps. There's also M564 S0, which will allow movement outside the boundaries set by M208.

Also, the machine can't know that it's not supposed to go beyond 0. Many people have (including myself, and everyone who uses a Delta printer) have the origin (X0 Y0) at the centre of the bed.

Ian

Well that's another thing. If you think you're getting noticeable deflection, that would mean there is enough play that correcting the deflection should be ok, but yes, there should be enough compliance built into the x gantry to prevent binding.

I would have thought that with the dual rails like that you wouldn't have had noticeable deflection to begin with.

L O L.. ok I feel stupid. You were 100% correct. I've been printing PETG lately and it does not like to be squished, so I've got a slight Z-offset in my slicer for this. I had forgot about that when I printed this.

Thanks @garyd9

@dc42 said in Duet 2 wifi - Reprap 3 MPU fan thermal control:

I have my electronics cooling fan set up to monitor both the driver and MCU temperatures, with a temperature range of 45:55. That way, the fan will start to spin if the MCU temperature exceeds 45C, and it will be full on if either MCU temperature exceeds 55C or there is a driver overheat warning.

@dc42 can you please share the code. Thanks a lot.

@dc42 i thought there was not a 3.3 since i used the complete Zip to update. I did standalone the dwc to 3.3 and worked great. Thank you

One possibility is that you are probing too fast. When the Z probe triggers, RRF stops the Z axis abruptly. If it can't stop fast enough then it will overshoot and skip Z motor steps. Then the Z axis is lower than RRF thinks it is, so the next G30 triggers early and RRF interprets this as a higher trigger height. So try reducing the probing speed (M558 F parameter) and see whether that gives more consistent results.

Another possibility is that the BLTouch is heating up and its trigger height is changing; or that something else is heating up and the height of the print head above the bed really is changing. But that's not likely unless you are running this test while the hot end or bed is heating up.

Ideally, yes. You should set the gcode flavour to RepRapFirmware. This usually tells the slicer to use the gcode syntax particular to your firmware.

I don't use S3D, but maybe this will help.
https://forum.simplify3d.com/viewtopic.php?t=1944

If you're using recent firmware for the Duet, it will accept the common Marlin gcodes as well as the RepRap versions.

@phaedrux said in New to Duet - issues with my extruder / part cooling fan.:

C 2

Your correct phaedrux. I'll try this tomorrow and report back 😉