Over the past several years I have had different 3D printers and controllers, Melzi, MKS... I have used Marlin and repetier firmware, all with success and generally I have always been able to print what I needed.

My latest is a TronXY X5SA Pro, I really like the mechanics of this printer, it's solid and works well. The stock controller was not terrible, but I wanted better ( to me anyway ). I replaced the controller with a Duet WiFi and 5" paneldue display.

For the most part the new setup just worked. Had to change my way of thinking from what I did in the past, but it was not a big deal.

For what issues I did have questions about, folks on this forum provided quick and useful help and made things that much easier.

So thanks to the developers of this hardware and firmware and to the folks that helped me and the many others I see in the forum.

Joel

OK, I think I got it, was not hard to figure out. Seems M584 is order driven. I just changed Z2:4 to Z4:2 and it seem to be working.

Joel

@Phaedrux I'm on 3.1.1. Fortunately this is not a huge issue, got into the habit of just cycling power between prints. Things are back up before the bed cools down much.

I'll try the straws, I'm not sure what else either.

@Phaedrux Probe offset is correct I think. When I set M208 X-2, that puts the nozzle on the edge of the table when I move to X0. The center of the probe is 35mm to the left of that, so I set G31 X-35.

These settings work fine for the first run, just after that is weird.

My mesh level works without issue.

I use simplify3D, the end script is,
G91
G0 Z10
G90
G0 X0 Y0
G4 S10
G91
G0 E -100
G90
M106 S0 ; turn off cooling fan
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
M84 ; disable motors

Homeall.g attached

homeall.g

Hi,

Three runs is intentional, it seems to zero in closer each time.

I "believe" it only needs the one G28 at the beginning of each run.

Just to make sure I explained myself correctly,

I run the leveling routine the first time after things are powered up and the bed is up to temperature. This works fine, it goes back and forth the three times and finishes. When that's done, I do the mesh level which also finishes fine. I bring the nozzle up to temperature and do the Z offset. When that's all done, I prime the nozzle and do the print.

I got into the habit of re doing the above steps between prints. It's the second print that the leveling routine goes off the bed unless I power cycle the printer.

The home position gets reset, so I'm not sure what went off the correct path.

Hi,

On my printer ( TronXY ) I've set bed.g up do do leveling at the lead screws ( Y position ). It all works perfect except if I run it again after a print completes. I might do this because a print was being pesky coming off the build table.

On my printer, at the X home position the sensor is off the table, so there's an offset to get it where I want. When I do a bed level a second time, the sensor goes off the build table and I get a nozzle crash.

On the second run of the level routine, everything does re-home as it did for the first run.

If I turn off the printer and start fresh, it all works fine again.

Any thoughts? is there something I missed?

I've attached my bed.g and config.g

Thanks
Joel

config.g bed.g

Not sure I think this will work. If I make the daemon.g file, does this override the internal filament checking? Is there an opportunity to clear the status before the internal mechanism triggers. Perhaps remove the filament sensor from config.g and just implement something in the daemon.g file.

The other issue, though this would greatly reduce the odds is, if you are just polling the sensor, it is possible to trigger, go away and trigger again at the instant you double check.

To be bullet proof, you need to check if filament out goes away after a flag is set and before the timer expires. How well this works depends on if these events are interrupt driven or polled. If polled, how often that loop is.

I will look and see if I can find documentation to look deeper into your idea.

Thanks

I am on 3.1.1

It's a simple micro switch type. I've opened it up and it's fully closed when the filament is in. Not at all on the edge of being opened or closed.

Hi,

I was doing a long print the other day ( 5 hours ) and at least 10 times I found my printer paused with a filament out message. A couple times I was there to see it happen. None of the times did the sensor indicate filament out.

So, is there a way or could it be implemented in a future release to have a per pin de glitch timeout setting? Something where the pin has to be asserted/asserted# continuously for a settable amount of time before the pin function is triggered.

Joel.

Yep, that didn't register. But, I still think a better way then would be, if a home command is executed, only clear the "homed" flags IF the homing failed.

For now, I did add a return macro which is working fine.

@deckingman said in Z crash but not into nozzle:

@Joel Suggest you read my post again for the reason. But I'm only guessing. I'm just an end user like you and trying to help.