@Snyggis-0 See the 'Alarm' tab here https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_1XD#configuration-examples which has an example for connecting the alarm to a 1XD board (I need to copy and update these examples to the 6XD page, thanks for the reminder!).
You set up the Duet pin you connected the alarm wire to with M950 (see https://docs.duet3d.com/User_manual/Reference/Gcodes#m950-create-heater-fan-spindle-led-strip-or-gpioservo-pin) You define a trigger (see https://docs.duet3d.com/User_manual/Reference/Gcodes#m581-configure-external-trigger) that checks that input for a signal. You define a macro (see https://docs.duet3d.com/en/User_manual/Tuning/Macros#triggers) that runs when the trigger detects the signal. This can do whatever you want, but usually in the event of an external driver error, you want the machine to pause to see if it recovers position. You may want the motion to stop (rather than pause, which may move the axes to a 'safe' position), in which case you could raise a driver error event with M957 (see https://docs.duet3d.com/User_manual/Reference/Gcodes#m957-raise-event, and for the effect of this see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events)It doesn't look like the driver has an alarm reset, so I'm not sure what action needs to be taken to clear the alarm.
Ian