Topics created by mwolter

@dc42 Since you're in the process of developing 3.2.0, wanted to see if this "command buffer" for the console was in the works.

@OwenD said in M117 and Conditional GCode Statements:

Not sure if there's something screwy going on with caching in DWC here, but the same command sometimes works and sometimes doesn't

DWC doesn't display a message if it was exactly the same as the previous one.

@mwolter Thanks, I can reproduce it now. Will be fixed in the upcoming DWC 2.1.6.

@phaedrux omg, I just noticed this reply 😧

ok, so this means I can not hide or remove one completely? (since it shows the one and only installed fan twice)

@Phaedrux Thank you!

@invertmast Thanks, I will give that a try (30mm checking). Already increased it to 6mm but maybe that’s not enough. Unfortunately I have the earlier version that doesn’t report the AGC but I believe the sensor is very close to the magnet.

Thank you so much for this.

Took some getting used to it, but it works very well! Now I just need to figure out how to format the email I made it send.

@dc42 Wanted to check on this also. Since you're looking into the filament sensor code, would it be possible to add an additional S parameter to M591 to monitor filament movement during all filament moves?

@mwolter said in Conditional Gcode: Test if key exists?:

echo sensors.filamentMonitors[0].calibrated = null

That works, thanks!

@dc42
I think I have found the issue. The values in G31 are being cleared if M558 is run again. This is also what is causing the issue I'm experiencing with the mesh probing grid.

In my original post, you'll find the z probe parameters in config.g.

In bed.g, I have the following command to increase the dive height in case the bed was extremely out of level. This often happens when the power is turned off, one of the two lead screws has a little less resistance and the bed lowers on that side.

M558 P9 H5 F120 T24000

But this instance of M558 didn't clear G31.

In bed.g, after the initial tramming run, the following was ran to lower the dive height and additional tramming is done, similar to your example conditional delta leveling script.

M558 P9 C"^zprobe.in" H2 F120 T24000

This instance used to lower the dive height resets G31. Please see the screenshot below.

Screen Shot 2020-03-08 at 6.16.22 PM.jpg

Rerunning M558 on RRF2 to increase the dive height did not do this. I have since moved the following commands to a new macro bltouch_config.g located in the /sys folder. This macro is run in config.g at powerup and if the dive height needs to be reset.

M558 P9 C"^zprobe.in" H2 F120 T24000 ; ; G31 - +Z Nozzle closer to bed, -Z Nozzle further from bed ; G31 X0 Y-28.58 Z2.75 P500 M557 X23:303 Y11:301 P10

After making this change G29 is now properly probing the mesh grid with the z probe offset and taking into account with the BLTouch pin is 28mm in front of the nozzle.

@dc42 my mistake. Had my synchronous & asynchronous inverted!

@Danal what I’m thinking is if the nozzle comes down and touches the endstop, it will set Z0 at that height, then if the probe is deployed and touches a shelf that is at the same height as the switch’s trigger height, the difference between the two would be the probe offset. This would calculate the distance between the nozzle and probe for every print or every power on of the printer so the probe z offset would always be accurate. If you changed a nozzle or something on the hotend, the offset would automatically be updated so the nozzle doesn’t crash into the bed.

@Hornetrider said in Canceling Print Difference Between DWC and PanelDue:

so, an empty cancel.g should keep heaters on?
or should heaters be selected by T0 & T1 within cancel.g?

Yes, an empty cancel.g should keep heaters on.

When I pause/cancel on my delta printer running RRF3, the heaters are left on. Here's the full contents of my cancel.g file (just a single comment):

; called when a print is cancelled after a pause.

Preferably use a fan to blow air along the lines of output mosfets on both sides of the PCB. But unless you are using more than about 3A peak current or a high current bed heater, you probably don't need fan cooling at all.

@mwolter said in Slice Thermistor or PT1000 and Duet 3:

@dc42 Thank you for updating the wiki with the PT1000 info.

Am I correct in assuming the Duet 3 v1.0 still doesn’t work well with the Slice Engineering thermistor?

That combination should be usable, however you will get poor resolution and accuracy at the low and high ends of the temperature range. Also at low temperatures, the Duet may not be able to tell that the thermistor is connected. These limitations are not unique to Duet, they apply to other controller boards (i.e. all of them) that read thermistors using the 10 or 12 bit ADCs in the main microcontroller.

Thank you @bearer and @gtj0. Sounds like it should work well. 👍

Great, thank you.

I use this in slicer PE start gcode
G10 P0 R100 S[first_layer_temperature] ; set temp and standby temp