Topics created by westech

@jay_s_uk Thanks will do.

@dc42 said in G-code trouble, filament completely retracts:

@Bridge-Of-Don said in G-code trouble, filament completely retracts:

We are using 'AstroPrint' as a method of slicing and it appears to use 'CURA

It's a feature of Cura that even if you set it to use relative extrusion, it switches back to absolute extrusion before running code that you supplied in the slicer configuration. So, unless this has been changed, you will need to include M83 in your slicer end gcode.

Been away for a short while and nobody else seems willing, but I found that there is an option to set the 'Start' & 'End' code within AstroPrint (and I guess CURA?) so it will always use those bespoke settings for our printer.

This seems to have cured the issue as simply added the M83 command , and whilst there tidied/edited a few of the deafult settings to make for a cleaner start and stop.

Our bespoke ending code now looks like this
G4 ; Wait
M220 S100 ; Reset Speed factor override percentage to default (100%)
M221 S100 ; Reset Extrude factor override percentage to default (100%)
G91 ; Set coordinates to relative
M83 ; RELATIVE extrusion mode
G1 F1800 E-3 ; Retract filament 3 mm to prevent oozing
G1 F3000 Z20 ; Move Z Axis up 20 mm to allow filament ooze freely
(although this still gets a string, which we can live with) 😊
G90 ; Set coordinates to absolute
G1 X0 Y280 F1000 ; Move extruder to the back for easy print removal
M84 ; Disable stepper motors
; End of GCode
M82 ;absolute extrusion mode
M104 S0
;End of Gcode

@westech Thanks Jay, Everything is working. I have both duets onliner and my klipper. All by hostnames.

I think there was a problem on the DUET. Like I said sometimes it will show up as "Duet-WiFi" and some time by the printer name.

My second Duet is a Mellow Fly E3 V1.1. It always comes up as "enderfly" never "Duet-WiFi."

@westech you can delete individual SSIDs using M588.

When you run M552 S1 the WiFi module scans for available access points and connects to the strongest one that it finds that is also in the list returned by M567.

@westech Did you see my first post? You can fix your problem easily without changing slicer.

@deckingman Wow, thank you.

@westech Increasing the Z offset gets it closer to the bed, decreasing is farther away. I added this as a comment the the G31, so I wouldn't forget.

@westech All in config.g. You already have one extruder drive and one tool defined in config.g as well as the M584 that you need to modify.

@mikeabuilder Thanks Mike!

The mounting option is up to you. The sensor only needs to be mounted when doing a measurement, so it does not need to be permanent. The important thing for mounting during a measurement is that it is rigid. That could be achieved with tape since the sensor is so light. If you have a spot to mount it with a printed mount and screws, that's all the better, but not critical for a good measurement.

@stephen6309 said in Weird retraction problem. How is my end G-code?:

@fcwilt M83 is for relative extruder mode. 🙂

Thanks for catching my typo.

Frederick

@westech said in Easy question: Z-offset/trigger Height:

@fcwilt Thanks, that's why I was confused. my Z is Z2.08. So if I change it to Z2.18 I will be .1mm closer to the bed.

Yes.

When the probe triggers the logical Z position is set to the Z Trigger Height parameter value. That doesn't mean that logical position matches the physical position, though that is the goal.

So if the Z Trigger Height parameter is 5, the logical Z position is set to 5 and the firmware "believes" that to move to Z = 0 it needs to move closer to the bed by 5mm. If after moving 5mm there is a gap between the tip of the nozzle and the bed that 5 value was too small. If before moving 5mm the tip of the nozzle touches the bed that 5 value was too large.

Frederick

@westech

mesh.g goes into the SYS folder.

All of my printers have a Z endstop sensor and a Z probe.

I use the endstop sensor for homing and the probe for set the Z=0 Datum, bed leveling and mesh creation.

Frederick

@dc42 Understood! Thanks!

i was searching for possibility to deactivate servo, to prevent damage (overheat) it in my case, and finally I have found a solution. You have to set "!" in front of pin name and then again any M280. "!" changes polarity of output and next M280 command results in sending unreliable data to servo so it deactivates.
Like in example bellow.

Of course then before any M280 command you should put M950.

M950 S1 C"pinname"
M280 P1 S180
M950 S1 C"!pinname"
M280 P1 S180

@westech said in Looking for M420 (load stored Mesh) workaround.:

Maybe G28 operates differently from Marlin:

Well I don't know Marlin but in RRF G28 does not automatically disable mesh compensation.

You can disable mesh compensation with G29 S2.

So you could put a G29 S2 into your homing files if you want Marlin-like behavior.

Frederick

he mechanical endstop I don't want to move. If I moved it up, then physically I could never reach the bed