Duet2 stoped working

kewlrunnins

after a few changes in the direction of travel on the config file my Duet2 stoped loading all my configs. Reloaded the old config and no change. the usb and ethernet work. I did get a few messages "no SD card. After formatting the card with the SD formatter and placing the files back on it started reading the card but now I get can't read files.
All the LED's are correct. The following is with nothing plugged in.

=== Diagnostics ===
<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet Ethernet 1.02 or later
<LF>Board ID: 08DGM-917NK-F23T0-6J1FG-3S86T-1ZBDD
<LF>Used output buffers: 1 of 24 (1 max)
<LF>=== RTOS ===
<LF>Static ram: 30516
<LF>Dynamic ram: 91488 of which 100 recycled
<LF>Exception stack ram used: 304
<LF>Never used ram: 8664
<LF>Tasks: NETWORK(ready,1984) HEAT(blocked,1340) MAIN(running,3700) IDLE(ready,156)
<LF>Owned mutexes:
<LF>=== Platform ===
<LF>Last reset 00:02:35 ago, cause: power up
<LF>Last software reset at 2020-01-15 20:51, reason: User, spinning module GCodes, available RAM 8616 bytes (slot 2)
<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
<LF>Error status: 0
<LF>Free file entries: 10
<LF>SD card 0 detected, interface speed: 20.0MBytes/sec
<LF>SD card longest block write time: 0.0ms, max retries 0
<LF>MCU temperature: min 23.4, current 29.6, max 29.8
<LF>Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0,
po[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

SIam

have you tried a new sd card ?

kewlrunnins

@SIam
I have and when I do my Ethernet card stops working. the smallest card I have is 64gb.
it seams to load some of the information like my IP address. But its not controlling anything, before it stoped working correctly it would move all three axis slow when given a single axis command. I have a corexy setup. the controller is about a week old.
you can get in with web control just it will not update with the correct number of print heads or movement.

kewlrunnins

generated by RepRapFirmware Configuration Tool v2.1.7 on Wed Jan 15 2020 19:20:11 GMT-0500 (EST)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Leap Frog" ; set printer name

M667 S1 ; select CoreXY mode

; Network
M552 P192.168.1.14 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.1.14 ; set gateway
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M569 P4 S1 ; physical drive 4 goes forwards
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X256 Y256 Z256 I0 ; configure microstepping without interpolation
M350 E16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z4000.00 E420.00:420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X2200 Y1344 Z2200 E1344:1344 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X200 Y230 Z270 S0 ; set axis maxima

; Endstops
M574 X1 S0 P"xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S0 P"ystop" ; configure active-low endstop for low end on Y via pin ystop
M574 Z2 S0 P"zstop" ; configure active-low endstop for high end on Z via pin zstop

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:190 Y15:195 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M308 S2 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e0temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M143 H2 S280 ; set temperature limit for heater 2 to 280C
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501 ; load saved parameters from non-volatile memory

@kewlrunnins said in Duet2 stoped working:

it seams to load some of the information

Try running the config and see if it complain about syntax?

M98 Pconfig.gcode

kewlrunnins

I have ran the config around 14 times to try and work out this problem and it hasn't reported anything on M98. I was testing each stepper driver using the same work Bench stepper motor. All the end switches have been disabled and I just have one motor and the duetpannel with a 4 wire connector. found the Z works correctly, Y reported motor phase A and B may be disconnected reported by driver 2. Got the same thing on X MOT.

Veti

@kewlrunnins said in Duet2 stoped working:

M350 X256 Y256 Z256 I0 ; configure microstepping without interpolation

you are overloading you cpu. unless there is a very specific reason you should got with x16 and interpolation for all your axis.

M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M308 S2 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e0temp

your thermistors configuraiton is wrong. replace the Beta (B4138) with the correct value for your thermistor.

kewlrunnins

@Veti
The steps were changed to 16 after uploading the config to the forum. I havent setup the thermisters yet Since controller has not made it into the printer. It’s still on the bench for programming as I update the printer hardware as well. After changing the steps to 16 I still have a MOT problem and other unexplained issues.

elmoret

Hi, could you do what @bearer requests, please?

Run:

M98 Pconfig.gcode

And provide a screenshot of the result. This bit from M122:

<LF>SD card 0 detected, interface speed: 20.0MBytes/sec
<LF>SD card longest block write time: 0.0ms, max retries 0

Indicates that the board can see the SD card and read it, so I doubt the problem is with the board's ability to read the SD card.

droftarts

@kewlrunnins said in Duet2 stoped working:

M552 P192.168.1.14 S1 ; enable network and set IP address
M554 P192.168.1.14 ; set gateway

Sorry you're having problems with your Duet 2 Ethernet. I noticed this in your config; the IP address and gateway address have been set the same. What this might be doing is causing the Duet to get stuck in a loop, though generally you only need the gateway address if you're needing to connect outside the network (ie to the internet) which the Duet doesn't normally do. However, this could have consequences to both the ethernet and the SD card, any you may need it depending on your router. Try commenting out the gateway address with a semicolon before it; you shouldn't actually need to set it. Connect directly to the ip address. If that doesn't work, set it to the correct gateway address, which I'd guess was 192.168.1.1.

Let me know if that resolves the problem. I'm going to test here to see if it causes a similar issue.

Ian

droftarts

@kewlrunnins Sorry, I think my post above is a red herring! I asked @dc42, who says the gateway address isn't used at the moment, and my testing can't replicate your problem.

Is there any evidence of anything getting hot - main processor, SD card connector, Ethernet port? The MCU temperature should be reported in the DWC, though can be quite inaccurate. If it goes up quickly from cold, that would signify a problem. Touching the other components with your finger 30 seconds or so after turning on should show if they are getting hot, without being so hot they hurt! But be careful!

If reading the SD card is intermittent, and nothing else seems to be the cause, it probably means there is a bad solder joint at the back of the SD card socket. I can confirm we will authorise a warranty replacement.

Please contact your supplier for a warranty replacement, referencing this thread. If you bought direct from Duet3D, please see our warranty process here (warranty form at the bottom) https://www.duet3d.com/warranty

Ian

This post is deleted!

kewlrunnins

nothing is running hot and the gateway was changed with no luck. all attempts of resets and config changes have failed.

@elmoret said in Duet2 stoped working:

Hi, could you do what @bearer requests, please?

Run:

M98 Pconfig.gcode

And provide a screenshot of the result.

this will help confirm there are no syntax errors in your config, please do it