Topics created by msugar

Can you move the motors to different drivers, change the config, and test again?

Your firmware is pretty ancient at this point. There may be more useful error messages in newer firmware. If there were errors witht he drivers I would expect them to say something.

As I replied to your other thread, the pin names can be found here: https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/DueX2_and_DueX5#pin-names

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.

@msugar said in Calling Separate Trigger Files:

What are the appropriate names of these pins?

https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/DueX2_and_DueX5#pin-names

M950 is used to define the pin that M42 would control.

https://docs.duet3d.com/User_manual/Reference/Gcodes#m950-create-heater-fan-spindle-or-gpioservo-pin

https://docs.duet3d.com/User_manual/Reference/Gcodes#m42-switch-io-pin

@msugar the last time we saw this error was some time ago, and it was caused by a particular antivirus program requesting very long filenames from the Duet because it assumed that the Duet might support OCSP (which it doesn't).

We changed the HTTP server in RRF 3.x some time ago to automatically return failure of the filename was longer than is sensible on a Duet. So upgrading to RRF 3.4.6 would get rid of the messages. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3 for an overview of the upgrade process.