@graybilldustin I'm glad you have it working, but I'd still recommend that you use the probe to set the Z=0 point if you plan to use a bed mesh. Doing it that way will avoid a lot of potential problems with the mesh having an offset from the bed especially if you make sure the probe point you choose aligns with one of the points in the bed mesh.

@dc42 yeah it is only ever the bottom sensor that exhibits that behavior. I am fairly confident my connector crimps are good as I have tried to shake/shimmy the harness around while heated and attempted to recreate the readings but they were stable. I just hate that the problem is so inconsistent and hard to replicate. I will start by replacing the sensor and double checking my connections on both sides and see if that fixes the issue.

@Dizzwold you need to connect the button between the ioX.in and ground pins, not between ioX.in and +3.3V.

@Phaedrux, thanks, you got me on the right track. M671 command was incorrectly formatted.

@drjacobs said in Sensorless Homing Core XY:

Are there other variables that should be adjusted besides feed rate and motor current percentage?

Stall sensitivity in the M915 command Minimum speed for stall detection in the M915 command Driver mode during homing (stealthChop for TMC2209 drivers, spreadCycle for other drivers used on Duets)

@jay_s_uk I go to bury myself deep underground
checking wiring I have found out I was looking the board upsidedown and I wired the heaters to "always on fans" pin
I feel ashamed 😞

so sorry guys now everything seems working

@Phaedrux i wll try with your settings and follow up

Man, it would be great to put our heads together and test our way to better quality.

@curieos I found the answer to my own question. https://docs.duet3d.com/User_manual/Reference/Gcodes#m563-define-or-remove-a-tool I can use the L parameter to set which drive to map filament to.

@p8blr The usual culprit which fits your description of events is extruder jerk being too low. Given that in any G1 move the axes travel and extruder travel have to be synchronised, then it's fair to say that if extruder jerk is too low, it will affect the X and Y axes as well. Conversely, if extruder jerk is high then in order to keep X, Y and E synchronised, it will effectively be overridden by the axes jerk values. Therefore, it is safe to set extruder jerk to a "silly high" number where it cannot interfere with any G1 Xn Yn En move. The only time extruder jerk could potentially come into affect (other than when it is set low and pressure advance is being used) is for extruder only moves which don't involve a reversal of direction (I can't think of any such moves).

@chrishamm

26/08/2023, 10:01:07 M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2023-07-21 14:11:38

Sorry, but the issue still persists?

I'd just made some changes to my config.g and clicked Run Config File.

Screen Shot 2023-08-26 at 09.54.25.png

If I click Restart MainBoard there's no problem?

Dizzwold

@Phaedrux @chrishamm

I've just updated to 3.4.6.

M401 and M402 now work as they should.

When I type M98 P"config.g" I still get the following response and have to manually press stop on the paneldue;
Connection lost, attempting to reconnect...

Maybe this is a bug similar to the following thread;
https://forum.duet3d.com/topic/33139/further-connection-issues?_=1692864007271

Dizzwold

I actually figured out a solution. I made an additional trigger function and turned off all the tools and rest the machine with the command M999.

@Threepwood It's been a while, when I worked with curve discussion.
My take on this is: you have to adjust the coordinates (y-axis) to be zero where the highest speed without underextrusion is.
Otherwise you'll always see underextrusion where it should be perfect.

example: from 1-3mm/s no underextrusion
put the value for 4mm/s in the first line of the spreadsheet ; 5mm/s in the second and so forth

The resulting curve will have no correction at 3mm/s.
Then switch off the extrusion correction below 3mm (macro, daemon.g? )

@Threepwood Thanks for the replies, heading out, but I will check what you suggested tomorrow. I did watch the video and at least I know what it is called now.

@deckingman, thank you. I have my fault detection set at 15 degrees. I did increase it to 15 seconds as well but since that did nothing, I went back to the default setting. I will play with both of those and dead time if the problem should return.

@Phaedrux it seems that I have some setting in the prusa slicer messed up. The Cura sliced it and it travels correctly

@jens55 Yes, I think it needs to be done in the slicer somehow, or a post process script.

With mixing hot ends, one can use the new filament to purge out the old. So when changing from one colour to another, I used to advance the tool change command within the gcode file so it actually changed tools "n" mm of filament before it would otherwise do. This meant that I could actually print multi-colour objects without using any sort of purge tower. To accomplish that, I had to write a little python script which would read through the gcode file, find the tool change commands, go back through the file and calculate the new position by summing the "E" values backwards from the original tool change point, then delete the tool change commands and re-insert them at the new points. But it gets complicated because the new change point might be inside a long XY move so I also has to segment such moves into two parts.

One would need to do something similar in order to pre-heat a tool by changing it's standby temperature at some point in time before it becomes active. That point in time might well be part way through a long G1 move so it would have to be segmented in order to insert the new standby temperature command.

There was some talk at one point about the firmware being able to run two or more parallel gcode streams but I don't know what the status of that is. That would be handy for such situations. One stream could contain just the G1 moves, the other could contain the tool heating/change commands.