Duet2 Firmware Upgrade Issue
-
Evening all
I've recently gotten back into 3D Printing and decided to build a new printer out of parts laying around. I have a Duet2 that I'm planning on using for the control board, however when I've tried to upgrade it to the latest firmware I'm getting this error:
M997: Firmware binary "0:/firmware/Duet2CombinedFirmware.bin" is not valid for this electronics
This is the board and firmware I'm running. When I try to install my RepRap firmware onto it it's displaying the above error message.
The main reason I'm trying to update it is because I'm getting this error message when trying to move the motors (One will move at a time, but both can't at the same time) (CoreXY Build)
Any support would be great!
-
What firmware were you updating from? And how did you go about updating? Did you upload the full release zip file? Have you also updated the DWC files to match?
The error message you're showing probably doesn't have anything to do with firmware though, it's telling you that you may have an issue with the wiring for your driver 1 stepper motor. So double check that wiring, especially the crimps.
To trouble shoot further you can swap that motor with another driver and see if the problem follows or stays with the driver.
-
@Phaedrux How do I go about updating the DWC Files?
-
Generally the best way to update the firmware on a standalone board is to upload the main release zip file in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.1/Duet2and3Firmware-3.5.1.zip
This will update everything that is needed.
-
@Phaedrux Alright I've checked all the wiring is correct and I've updated the firmware. Both motors are moving the correct direction now but when the axis are homing I'm now getting a issue with Driver 2
'Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected'
There's nothing grounding on the board and I can't figure out what else it could be, the motors maybe?
-
What are the motor specs?
What current have you set them to?
How fast are you trying to move them?
Can you share your config.g and the results of sending M122 and M98 P"config.g" in the gcode console?
If you swap the motors to other drivers does the problem follow the motor or the driver? -
@Phaedrux said in Duet2 Firmware Upgrade Issue:
M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6JKDA-3SN6Q-TST39
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 67932 of which 0 recycled
Never used RAM 21956, free system stack 184 words
Tasks: NETWORK(1,ready,27.9%,220) HEAT(3,nWait 5,0.0%,330) Move(4,nWait 5,0.0%,359) MAIN(1,running,72.0%,761) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:27:25 ago, cause: software
Last software reset at 2024-04-19 22:48, reason: User, Gcodes spinning, available RAM 21812, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 35.4, current 36.7, max 37.3
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-04-19 23:15:40
Cache data hit count 4294967295
Slowest loop: 15.20ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 13.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 6.92ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
Socket states: 5 2 2 2 2 2M98 "config.g"
Error: M98: No P or R parameterNema 17 Specs:
Motor Type: Bipolar Stepper.
Step Angle: 1.8°
Holding Torque: 26Ncm(36.8oz.in)
Rated Current/phase: 0.4A.
Phase Resistance: 30ohms.
Inductance: 37mH+/-20%(1KHz)Config.g:
config (1).g -
@Bewaren said in Duet2 Firmware Upgrade Issue:
M98 "config.g"
Error: M98: No P or R parameterThe command is M98 P"config.g"
Please try running it again. -
@Bewaren said in Duet2 Firmware Upgrade Issue:
Nema 17 Specs:
Motor Type: Bipolar Stepper.
Step Angle: 1.8°
Holding Torque: 26Ncm(36.8oz.in)
Rated Current/phase: 0.4A.
Phase Resistance: 30ohms.
Inductance: 37mH+/-20%(1KHz)Does it have a model number?
Are your motors getting very hot?
-
@Bewaren M98
P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled -
@Phaedrux Motors are cold to the touch
Motors model number is:
JK42HS40-1704-13A -
try increasing your motor current set in M906 to 1200
-
@Phaedrux Tried this and still getting the same error message
-
@Phaedrux It's also now giving me this error, not sure if it's possibly related?
20/04/2024, 18:20:07 Error: in file macro line 7: G1: Failed to enable endstops
-
@Bewaren said in Duet2 Firmware Upgrade Issue:
20/04/2024, 18:20:07 Error: in file macro line 7: G1: Failed to enable endstops
Sounds like your homing files are trying to use an endstop that doesn't exist. Post your homing files.
-
@Bewaren said in Duet2 Firmware Upgrade Issue:
@Phaedrux Tried this and still getting the same error message
Phase disconnected means that either the wiring isn't good, or the driver is internally damaged. I'd replace the wiring, particularly the crimps.
Are you still getting expected movement from the motors?
-
@Phaedrux Unfortunately I've checked the wires already and have replaced them all, the motors are moving as expected however when it's homing multiple axis at once (X and Y) it seems to encounter an issue and starts skipping on the belt.
I'm assuming it's a issue with the driver then?
If so I assume there's nothing I can really do to repair it? I'm running two Z motors and a X and Y so won't have a free one once I add the extruder also
Thanks again for the help!
-
@Phaedrux Yeah it's just clicked it'll be my Z axis, I've not set the bed up as of yet so don't even have those motors connected
-
Are you getting the driver warning from the driver that the Z axis is connected to?
-
@Phaedrux I don't have anything connected to the Z axis drivers currently
