I recently changed the firmware version from 2.05 to 3.4.6 and I am having a lot of difficulties' getting the same outputs to trigger with the same commands. I am trying to trigger the FAN4 output using M42 P24 S1 and I am getting an error stating that the P value is too high. With firmware 2.05 this command would trigger correctly. I have made a new config file. Could this be because the new expansion board is not being recognized. How would I know if my duet board is recognizing the expansion board? How does the pin callout work with the new firmware? Is it different then what was used in firmware 2.05? I am using the duex5 expansion board and the main board is the duet 2 Wi-Fi.

Is there a number I can call to get support with this problem?

@Phaedrux When I send that command I immediately lose connection. The only way for me to regain connection is if I turn the machine off and on.

Nothing has changed recently and I don't get any errors when I attempt to home the printer. I have to physically move the gantry to satisfy the homing sensors.

@droftarts I tried disconnecting them one at a time and I also tried commenting them out of the config.g and still nothing worked.

I pressed the reset button on the board and it was working. When I power cycled the board, it stopped working. I pressed the reset button again and that didn't work.

@droftarts I checked all 4 fuses with a multimeter and was able to get continuity across them.

Hi,

I have a Duet 2 and a Duex5 in a 3 axis machine and its been working perfectly fine for the past year until yesterday. I can not seem to move the machine in any direction. It seems unlikely that all three motors have stopped working at the same time. I read some of the other forums with similar issues and did some basic trouble shooting based on some of the responses. I entered some commands that can be seen below M906, M122, M913, and M584. I also moved the gantry to satisfy the homing routine and tried to send a command to force move it G91 G1 S2 X10 F1000. There was still no movement.

How can I tell if the drives on the board are bad?

I also attached my config file at the bottom

In the diagnostics there was one line that stood out to me "Movement lock held by null". Could this be the problem?

9:32:36 AM M584
Driver assignments: X0 Y1 Z2 E3:4:5:6:7:8:9, 3 axes visible


9:32:24 AM  M913
Motor current % of normal - X:100, Y:100, Z:100, E: 100 : 100: 100: 100 : 100: 100: 100


9:32:01 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996AL-K65SW-6JKD8-3S06L-9U7QZ
Used output buffers: 3 of 24 (8 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93580 of which 484 recycled
Exception stack ram used: 544
Never used ram: 10752
Tasks: NETWORK(ready,628) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:25:49 ago, cause: power up
Last software reset at 2024-10-22 14:04, reason: User, spinning module GCodes, available RAM 10800 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 27.0, current 40.7, max 40.9
Supply voltage: min 24.1, current 24.2, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/0
Driver 1: ok, SG min/max 0/0
Driver 2: ok, SG min/max 0/0
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 2024-10-23 09:32:00
Cache data hit count 4294967295
Slowest loop: 18.27ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 156, MaxWait: 87765ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 11, completed moves: 11, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 69.22ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is providing access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address e2:98:06:a4:3a:77
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24840
WiFi IP address 11.22.33.44
Connected clients 1
Socket states: 0 0 0 0 0 0 0 0


9:31:53 AM  M906
Motor current (mA) - X:1600, Y:1600, Z:1600, E:0:0:0:0:0:0:0, idle factor 30%  

CONFIG:

;Configuration file for Duet WiFi (firmware version 2.05.1)				
;Sigma Z1024				
;Version	1.06	12/27/2022		
;__________________________________________________________________________________________				
				
;__________DISABLE ALL FANS__________				
M106 P0 I-1				
M106 P1 I-1				
M106 P2 I-1				
M106 P3 I-1				
M106 P4 I-1				
M106 P5 I-1				
M106 P6 I-1				
M106 P7 I-1				
				
;__________TURN OFF ALL FAN OUTPUTS__________				
M42 P20 S0				
M42 P21 S0				
M42 P22 S0				
M42 P23 S0				
M42 P24 S0				
M42 P25 S0				
M42 P26 S0				
M42 P27 S0				
				
;__________DISABLE ALL HEATERS__________				
M307 H0 A-1 C-1 D-1				
M307 H1 A-1 C-1 D-1				
M307 H2 A-1 C-1 D-1				
M307 H3 A-1 C-1 D-1				
M307 H4 A-1 C-1 D-1				
M307 H5 A-1 C-1 D-1				
M307 H6 A-1 C-1 D-1				
M307 H7 A-1 C-1 D-1				
				
;__________TURN OFF ALL HEATER OUTPUTS__________				
M42 P0 S0				
M42 P1 S0				
M42 P2 S0				
M42 P3 S0				
M42 P4 S0				
M42 P5 S0				
M42 P6 S0				
M42 P7 S0				
				
M42 P1 S1				;TURN WHITE LIGHT ON
				
;__________General preferences__________				
G90   				; Send absolute coordinates...
M83   				; ...but relative extruder moves
M555 P1 				; SET FIRMWARE COMPATABILITY TO REPRAP
M669 K1 X-1: -1:0:0 Y1:-1 :0:0 Z0:0:1:0 U0:0:0:1				;Select CoreXY mode
				
;__________DEVICE NAME__________				
M550 P"SONOTEK Z1024"				; SET DEVICE NAME
				
;__________Network__________				
M552 S0				;WIFI ON
G4 S1				;WAIT 1 SECOND
M552 S2				;ENABLE NETWORK AS HOST
;M552 S1                   				;ENABLE NETWORK AS CLIENT
G4 S1				;WAIT 1 SECOND
				
; __________Drives__________				
M569 P0 S1				;Drive 0 goes forwards
M569 P1 S1				;Drive 1 goes forwards
M569 P2 S0				;Drive 2 goes backwards
				
				
M92 X80 Y80 Z414.4				;SET STEPS PER MM 16X MICOR STEPS
M350 X16 Y16 Z16 I1				;SETP MICRO STEPPING
				
M566 X1000 Y1000 Z2000				;(jerk) Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z6000				;Set maximum speeds (mm/min)
M201 X1500 Y1500 Z1500				;Set max accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 I30				;Set motor currents (mA) and motor idle factor in per cent
M84 S5				;Set idle timeout
				
; __________Axis Limits__________				
M208 X0 Y0 Z40 S1				;Set axis minima
M208 X330 Y300 Z105 S0				;Set axis maxima
				
; __________Endstops__________				
M574 X2 Y2 Z2 S1				;Set active high endstops
				
; __________Tools__________				
M563 P0 S"TOOL 0" D0				;DEFINE TOOL 0
G10 P0 X0 Y0 Z0				;SET TOOL 0 AXIS OFFSET
				
				
				
				
				
;__________BED__________				
M140 H-1				;DISABLE BED HEAT
				
;__________ESTOP I/O__________				
M581 E0 T0 S1 C0				;WHEN DRIVE 0 HOME SENSOR IF LOW EXECUTE E-STOP
				
;__________DOOR I/O__________				
M581 E1 T1 S1 C0				;WHEN DRIVE 6 HOME SENSOR IS LOW EXECUTE PAUSE
M582 T1				;CHECK PAUSE TRIGGER
				
;__________EXHAUST CHECK__________				
M581 E2 T2 S1 C0				;CHECK EXHAUST SWITCH AT ALL TIME IF OPEN RUNTRIGGER2.G
M582 T2				;CHECK EXHAUST TRIGGER
;__________ENABLE COLD EXTRUDE__________				
M302 P1				;ALLOW COLD EXTRUDE
				
;__________ALARMS__________				
M581 E3 T3 S1 C1				;GENERATOR ALARM 1
;M581 E4 T4 S1 C1				;GENERATOR ALARM 2

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.

@deckingman Would these pins be the ones labeled E_2stop, E_3stop etc.? If so these are the ones I currently have them wired into. What are the appropriate names of these pins? based on your response it seems as if I have the wrong name for the physical pin.

@deckingman Both of these suggestions are already done. I think my problem is that my expansion Duex5 is not monitoring the inputs or I have a problem with my code monitoring inputs. I am trying to monitor inputs on the expansion board so that if the inputs are not met then the move motors will not be triggered.

I am not using these outputs for actual fans I am using the fan pins as general outputs for different tools. It is turning on the pins for fans 4-7 on the duex 5 expansion board.

Hi,

I have an expansion board Duex5 that I am using with my Duet2 WIFI board and I am not sure if I am calling the pins correctly. On the expansion board I am using pins E2-Stop, E3-stop and E4-stop as general inputs. I am trying to set it up so that if the condition is not met then the program will not run a path. Once the conditions are met the machine can run a path. If at any point a condition changes state during a path I would like the machine to pause or even just have a screen popup. I know to call the message M581 is used. I noticed on your diagram with the pins there are a few different names to call them out. What are the names I should be using? I have used all of the names that I can see but it doesn't seem to be calling them correctly. Is there a way that I can see what I being triggered with the pin names?

Firmware: 3.4.6
Config:
42aa476b-00e0-4dc2-acc8-f7e0ff02e980-config.g

Hi,
I added a physical E-Stop to the system that will cut power to the board and my expansion board. After the power is cut, I want the fans to remain off. Right now they are turning back on when power is restored and the emergency stop is disengaged. Is there a command that will allow me to turn them off and remain off or even reset them to their initial state. I saw the command M911 is to configure auto save on loss of power. Would this be appropriate in this situation?

I am using firmware 3.4.6 and here is the config file
f905920d-4d54-4cba-be09-73d3b5addd86-config.g