Posts made by zombiRon

Here's where I've got to now, adding this at the beginning of config.g and making sure it's AFTER network/HTTP is started, but before the rest of the machine config.

If a PanelDueFirmware.bin is detected a request is pushed to the PanelDue and DWC if connected at the time to update.

If DWC is connected, it also shows progress and results in console.

M552 S1										; Enable network
M586 P0 S1									; Enable HTTP
M586 P1 S0									; Enable FTP
M586 P2 S1									; Enable Telnet
M38 "sys/PanelDueFirmware.bin"				; compute hash of file if exists
if result == 0
	M291 R"PanelDue Update" P"Update available, checksum is available on console, OK to flash?" S3"
	M997 S4									; flash PanelDue
	if result == 0
		G4 S6 								; wait for paneldue reboot
		M30 "0:/sys/PanelDueFirmware.bin"	 	; delete update file
		if result != 0
			echo "PanelDue update file could not be removed following successful flash"
		M291 R"PanelDue Update" P"Update successful, see console for details" S2 T0
	else
		M291 R"PanelDue Update" P"Update ERROR, see console for details" S2 T0

If an update is declined, the file will need to be removed manually as cancel will abort further processing of config.g.

I did consider deleting the file on cancel and then rebooting, but I thought that if I'd declined the updated due to HASH mismatch, then I'd prob want the machine to stay as it is so I can troubleshoot. If you'd rather it deleted and rebooted, add the following after the last M291 making sure of the same indentation.

		M30 "0:/sys/PanelDueFirmware.bin"
		M999

@LB it will just error if there's no update file, so you could check the return of that alone, but I think @OwenD was meaning elegant in that there's no ERROR output in the console.

M997 S4 
Error: M997: File 0:/sys/PanelDueFirmware.bin not found

@OwenD Just thought I'd offer my solution using M38 to check existence of the file and offer the user a chance to check the Hash??

M38 "0:/sys/PanelDueFirmware.bin"
if result == 0
    M291 R"PanelDue Upgrade" P"New firmware has been detected, hash has been output to the console. OK to update?" S3
    ; M997 etc...
elif result == 2
    echo "No PanelDue firmware detected"

That's fine, I'm using a mosquito hot end which prefers a longer barrel.

Thanks for the info.

My PT1000 has decided it no longer wants to give accurate readings, so time for a replacement, but it seems there's no one currently stocking these in the UK.

My original one came from Precision Piezo, but it's no longer listed on the site or at ooznest or E3D.

Anyone know of a supplier?
Failing that, what is everyone using if not PT1000 currently?

I've just been reading some of the feature requests on RRF github page and a found this...

https://github.com/Duet3D/RepRapFirmware/issues/416

When we get variable support in conditional G-Code, we could set retract and wipe distances and have the slicer just reference those. Then we can have RRF filament definitions for each filament and also the ability to update them during a job (which is my main reason for preferring firmware retraction)

As an example you could set the retraction distance to 99.99, a little post-processing script to swap E-99.99 for E{retractionDistance} this would look like this in...
PrusaSlicer: /usr/bin/sed -e '/E-99.99/E-{retractionDistance}/g'
Simplify3D: {REPLACE " E-99.99" " E-{retractionDistance}"}

This would work until the slicers are updated to allow direct variable references for these values.

Thinking about it further maybe we could do this now already by swapping E-99.99 for E-{tools[0].retraction.length}??

This does only work if using relative extrusion though.

mkudzia84 created this issue in Duet3D/RepRapFirmware

closed [Feature Request] Wipe option for a firmware retract #416

@dc42 you're on a roll today

@dc42 Excellent! Thanks very much!

@dc42 great, thank you. I never looked in the boards section, assumed it was for expansion / tool boards.

Now I can leave out all of the logic and just include a config if it exists, which means I can have a single SD image for both machines.

M98 P{"MACHINES/" ^ boards[0].uniqueId ^ ".g"}

@bearer any idea why it's deferred? Only thing I could think of is to allow the firmware recovery of the WiFi module with M997, but then this is just a simple ordering of commands in the file. I could understand that if the config was not guaranteed to be processed in any order but we have commands used in config.g which must be in a particular order already. Add to that if files were processed out of order; 3D printing wouldn't be possible.

I noticed in another post M552 commands are deferred since you mentioned it, but in them posts they were interlaced with G4 wait commands, so how does it know to defer them too? This would lead to inconsistent behaviour.

If it's by design then it must have a reason; hardware implementation, some blocking I/O or a race condition?? I wonder if the WiFi module has direct access to the SDCard, this would make sense.

It appears that the WiFi module doesn't actually become active until config.g has been processed. Which means that I can't select config based on which duet device is running. I was hoping the MAC address being unique would be a good identifier.

Is there any other unique identifier I can query during config.g?

here is the example code I've been trying

; config.g - Configuration file for Duet WiFi
; executed by the firmware on start-up

; General preferences common to all machines
M81
M575 P1 S1 B115200
G90	
M98 P"startNetwork.g"
M400
while true
	if iterations == 30
		break
	G4 S1
	echo network.interfaces[0].mac
if { network.interfaces[0].mac ^ "M" } == { "a5:a5:a5:a5:a5:a5" ^ "M" }
	echo "Network device not enabled"
elif { network.interfaces[0].mac ^ "M" } == { "bc:00:00:00:00:00" ^ "M" }
	M98 P"MACHINES/3DPrinter.g"
elif { network.interfaces[0].mac ^ "M" } == { "b4:00:00:00:00:00" ^ "M" }
	M98 P"MACHINES/CNC.g"
else
	M552 S-1
	G4 S5
	M552 S0
	G4 S1
	M587
	echo "Please Configure WiFi Access Point with"
	echo "    M587 S""SSID"" P""p4ssW0rd"""
M501

startNetwork.g looks like this

M552 S1								; Enable network
M586 P0 S1							; Enable HTTP
M586 P1 S0							; Enable FTP
M586 P2 S1							; Enable Telnet

Originally the network start code was inline in config.g but I moved it into another file hoping it would allow the WiFi module to be triggered while it switched files.

You can see with the 30 second delay the WiFi module doesn't come alive until after no matter how long it waits, I've had it wait 5 minutes and still nothing.

Am I right in thinking the processing of config.g is before the main program loop and communication with the module happens after?

@dc42 Wow that was fast!
Thanks, I tried many combinations to force the type to be cast, not sure how I missed that one, sorry.

Re: Invitation to share your conditional GCode scripts

Hi, really quick couple of questions...

Should I be able to do this? if not can it be implemented please?

T{ state.previousTool } P0

Also, when I query the mac address of the interface the returned value is not a string, and so it fails evaluation in an if statement like so

if network.interfaces[0].mac == "a5:a5:a5:a5:a5:a5"

or is the output from this used elsewhere so the "type" must be retained??

@Phaedrux Replacement board arrived today, straight forward swap out of the clone, once I jumped through the firmware v2 --> v3.0 --> v3.1.1 hoops, all working perfectly. Thanks for your assistance in resolving this.

@Phaedrux I had a look into that page, here's the output of M122 following the startup message

RepRapFirmware for Duet 2 WiFi/Ethernet Version 3.1.1 dated 2020-05-19b2
Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
M122

=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0

And here is what happens when I try to access a file one the Card, in this case I just tried to flash the WiFi module as an example

M997 S1 
Error: M997: File DuetWiFiServer.bin not found

The board appears to be getting worse, the window of usefulness is shrinking, I suspect something is dying.

Following the troubleshooting steps you linked, I have verified the SDCard socket is getting warm, but the WiFi module is very warm (48C), MCU just warm, this is after only a minute or two of power up.

These tests were performed with USB connected only, no external power, and with 2 SDCards, one of which was supplied with the board.

What next?

(serial no obscured)

@Phaedrux Any news on this please?

@Phaedrux ok...

@Phaedrux I bought it from ooznest on 12 may, here is config.g as requested, if I'm missing something obvious please point me in the right direction.

; Configuration file for Duet WiFi
; executed by the firmware on start-up

; General preferences
;M912 P0 S-13						; Correct MCU Temp (HotEnd - MCU at room temp)
G90									; Send absolute coordinates...
M83									; ...but relative extruder moves
M669 K1								; Select CoreXY mode
M404 N1.75 D0.4						; Set Filament diameter and nozzle size

; Network
M550 P"Duet3D"						; Set machine name
M575 P1 S1 B57600					; Configure Speed for PanelDue
;M98 PCONFIGNETWORK.g				; Configure WiFi Access
M552 S1								; Enable network
M586 P0 S1							; Enable HTTP
M586 P1 S0							; Enable FTP
M586 P2 S1							; Enable Telnet

; Drives
M569 P0 S0							; Drive 0 goes backwards
M569 P1 S1							; Drive 1 goes forwards
M569 P2 S1							; Drive 2 goes forwards
M569 P3 S1							; Drive 3 goes forwards
M350 X16 Y16 Z16 I1					; Configure microstepping for motion
M350 E16 I1							; Configure microstepping for extruder
M92 X200.00 Y200.00 Z1600.00 E830.00		; Set steps per mm
M203 X12000.00 Y12000.00 Z1200.00 E12000.00	; Set maximum speeds (mm/min)
M566 X800.0 Y800.0 Z120.0 E3000.0			; Set maximum instantaneous speed changes (jerk in mm/min)
M201 X1800.0 Y1800.0 Z240.0 E3000.0			; Set accelerations (mm/s^2)
M204 P1200 T1800						; Set printing and travel accelerations
M906 X1600.00 Y1600.00 E1600.00 I20		; Set motor current (mA) and motor idle factor in per cent
M906 Z1330.00 I20						; Set motor current (mA) and motor idle factor in per cent
M913 X60 Y60 Z40 E40					; Set motor current (%) of rated
M917 X20 Y20 Z10 E20					; Set motor standstill current (%) of rated
M84 S5									; Set idle timeout
M569 P2 F5								; adjust CHOPCONF for Z motor
M569 P0:1 F5							; adjust CHOPCONF for X Y motors

; Axis Limits
M208 X-56.4 Y-9 Z0 S1					; Set axis minima
M208 X211 Y286 Z200 S0					; Set axis maxima

; Endstops & Motor Stall
M574 Z2 S3					; Set endstops controlled by motor load detection + direction
M574 X1 Y1 S3				; Set endstops controlled by motor load detection - direction
M915 P0:1 H400 S2 F0 R0			; Stall Detection for X Y Axis
M915 P2 H400 S3 F0 R0			; Stall Detection for Z Axis
M915 P3 H400 S3 F0 R0			; Stall Detection for Extruders

; Z-Probe
M558 K0 P8 C"!zprobe.in" R0.5 H5 F600 T6000 S0.03 B0 A1	; Set Z probe type
G31 P1000 K0 X0 Y0 Z-0.04								; Set Z probe offsets
M557 X5:195 Y5:195 S19:19								; Define mesh grid

; Sensors
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 A"Bed"			; define temp sensor for Bed Core
M308 S1 P"e0_temp" Y"pt1000" A"Mosquito" 			            ; define temp sensor for Extruder
M308 S2 P"e1_temp" Y"thermistor" T100000 B3950 A"Bed Surface"	; define temp sensor for Bed Surface
M308 S3 P"mcu-temp" Y"mcu-temp" A"MCU"							; define temp sensor for MCU

; Heaters
M950 H0 T0 C"bed_heat"			; define bed heater
M950 H1 T1 C"e0_heat"			; define extruder heater
M143 H0 S140					; Set temperature limit for heater 0 to 140C
M143 H1 S300					; Set temperature limit for heater 1 to 300C
M140 H0							; set default Bed heater

; Fans
M950 F0 C"fan_0" Q100				; define FAN for Part cooling
M950 F1 C"fan_1" Q100				; define FAN for Extruder cooling
M950 F2 C"fan_2" Q90				; define FAN for Stepper cooling
M106 P0 C"Part Cooling" H-1					; Set fan 0 Part cooling fan
M106 P1 C"Mosquito" X1.0 H1 T45				; Set fan 1 Hotend cooling fan, above 45C
M106 P2 C"Stepper" H3 L0 X1 B0.3 T30		; Set fan 2 Stepper Driver cooling fan based on MCU temp

; Tools
M563 P0 S"Mosquito" D0 H1 F0	; Define tool 0
G10 P0 X0 Y0 Z0					; Set tool 0 axis offsets
G10 P0 R140 S200				; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S23 R24 P"M913 X0 Y0 G91 G1 Z5 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Miscellaneous
M671 X190:100:10 Y30:183:30 P0.5	; bed adjust locations and screw pitch 0.5 for G32 assistant
;M207 S1.5 F900						; Flex3drive G5 extruder
M207 S1.4 F4800						; Default retraction settings
M81									; Enable ATX buttons in DWC
M501								; Load saved parameters from non-volatile memory

I think I've got a faulty Duet2 WiFi.
I've been running a Chinese clone for a couple of years and it's been great.

When you released the conditional G-Code feature in 3.01 I decided to pay the entry fee and buy a genuine Duet so that I could participate in the forum and be a part of the community.

So far though, this genuine board has not been an easy swap. Electrically all the connections were a 10 min board swap, but the behaviour of the board has had me double checking all the connections, rewiring, rewriting the config thinking that there may be some nuances I'd missed.

Tonight I decided to connect via USB and run the debug commands to see what it had to say. It runs fine for probably half an hour (from cold) then starts with this bad-checksum error from the panelDue. It then continues with unable to read the SD card as you can see from the code snippet below. Give it an hour to cool down and it'll run fine for another half hour. It's taken a couple of months to troubleshoot this, partly because I keep losing interest when it misbehaves for no "apparent" reason or error, debug over usb-serial was holding what I needed.

I finally gave in and switched back in the chinese clone and without any changes to config or wiring, the board fired straight up with the SD card the genuine board said was unusable (I had tried 3 different cards during this time so it's not just a faulty card) and proceeded to print.

Could you authorise a return so I can go back to ooznest and get a replacement board please?

Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux(bad-csum): M408 S0 R13
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Aux: M408 S0 R11
Daemon: skip
Read 0 1 58500736
Error: Cannot read file, error code 1
Aux: M408 S0 R12
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R13
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R14
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R15
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R16
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R17
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R18
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R19
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R20
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R21
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R22
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R23
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R24
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R25
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R26
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R27
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R28
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R29
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R30
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R31
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R32
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R33
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R34
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R35
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R36
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R37
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R38
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R39
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R40
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M292 P1
Aux: M408 S0 R41
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S1
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R43
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R44
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R45
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R46
Read 0 1 24576
MWarning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R47                                                                                                   M11Read 0 1 24576                                                                                                 M112Warning: Failed to open 0:/sys/daemon.g to read, error code 1

USB: M112
Emergency Stop! Reset the controller to continue.
ok
Aux: M408 S1
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R50
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R51
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R52
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
Aux: M408 S0 R53
Read 0 1 24576
Warning: Failed to open 0:/sys/daemon.g to read, error code 1
HTTP: M999
Aux: M408 S0 R54
Read 0 1 24576
[Disconnected]
[Connected]
M122 
RepRapFirmware for Duet 2 WiFi/Ethernet Version 3.1.1 dated 2020-05-19b2
Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SD-6J9D2-3SN6M-9UJHG
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 92268 of which 20 recycled
Exception stack ram used: 272
Never used ram: 10532
Tasks: NETWORK(ready,1884) HEAT(blocked,1476) MAIN(running,2580) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:00:09 ago, cause: software
Last software reset at 2020-06-19 01:21, reason: User, spinning module GCodes, available RAM 7708 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04417000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 34.9, current 35.1, max 35.1
Supply voltage: min 24.2, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 888068
Slowest loop: 5.45ms; fastest: 0.13ms
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: 12.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with "M122" 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.18ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok
[Disconnected]
[Connected]

RepRapFirmware for Duet 2 WiFi/Ethernet Version 3.1.1 dated 2020-05-19b2
Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
Warning: VIN under-voltage event (9.5V)
[Disconnected]
[Connected]

RepRapFirmware for Duet 2 WiFi/Ethernet Version 3.1.1 dated 2020-05-19b2
Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
[Disconnected]
[Connected]

RepRapFirmware for Duet 2 WiFi/Ethernet Version 3.1.1 dated 2020-05-19b2
Cannot initialise SD card 0: Card is unusable
WiFi is disabled.
RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.
[Disconnected]
[Connected]