I do have my Z motors wired to the Mainboard but I have the Z-probe wired to a tool board, and all of the motors driven by the tool boards are using sensorless homing.
Thanks for the clarification @DC42
So I have a large scale toolchanger and I have been trying to get all of my tool selection gcode tweaked to work really well, and now when I tested a tool selection, the machine goes through the tpre0.g as it should but then it doesnt actually change the state of tool 0 to active, and if I send another T0, it reruns the tpre0.g ... not sure whats happening here.
Well this is definitely going to be a game changer for me, I will have to do some testing on one of my other test rigs to play around with this.
Thanks a million @OwenD, I am constantly amazed on how helpful the Duet Community is and i hope one day I know enough to be able to help others out as you have helped me.
Ok, that is some interesting stuff... daemon.g is available in 3.1.1 or would I have to go to RC11 as it states in the last post? and in your statement it has a simple if statement, i'm guessing the daemon.g is being constantly queried causing the if statement to act as a loop?
In the current object model, is there a way to loop a section of gcode to continue during the duration of the print? I have a prototype pellet fed extruder with a Duet 3 6HC and a 3HC expansion all up to date running 3.1.1 and my pelllets feed was being controlled by a capacitive sensor, which has gone bad on me. I have another coming but i would like to continue printing in the mean time. I figured there would be a way to implement a while loop in the prints gcode to activate my air solenoid with M42, wait a small amount of time, deactivate the solenoid, then wait another amount of time, then repeat that while the print is going.
I am having trouble finding much information on the current object model and have little experience in this type of logic. Any help would be appreciated.