Maestro issue updating from 3.3 to 3.4
I updated my Maestro from 3.2.2 to 3.3 the other day and it all went perfectly.
I updated from 3.3 to 3.4 today by uploading the Duet2and3Firmware-3.4.0.zip via the webUI and it hung on installing firmware update. I left it for a good 20 mins but no response from the webUI. Rebooted and I'm now unable to ping the board. I tried going back to the 3.3 firmware and still no response.
I noticed that there is no DuetMaestroIAP.bin file in the 3.4 release. Could this have caused an issue whilst installing the 3.4 firmware?
Any tips on getting this sorted?
How did you update to 3.3? Did you upload the full zip file?
As far as I can see there hasn't been a Duet2_SDiap32_Maestro.bin file in any of the 3.4 beta releases. Is that file present in your firmware folder?
Also note the change from the bin files going in the sys folder to now having a dedicated firmware folder starting with 3.3
Yes by uploading the full zip.
There is a Duet2_SDiap32_Maestro.bin file in the final 3.4 release today but no DuetMaestroIAP.bin.
I've tried booting with 3.4 firmware along with both of the above, former from 3.4 and latter from 3.3. I've also tried booting with 3.3 with all the bin files in the firmware folder and second copies of Duet2_SDiap32_Maestro.bin and DuetMaestroIAP.bin in the sys folder. I'm unable to ping the board at all now.
Can you try doing a Bossa flash to 3.4 over USB?
Having never done this before, how do I erase the firmware on a Maestro - using a jumper or is there a button?
Also is this my only option at this point as opening my printed housing to access the board is a real pita.
If you're unable to reach DWC over the network then USB is your only option.
You could use a serial terminal application like YAT to see if it will respond to commands line M115, otherwise reflashing the firmware directly is your only way forward.
Yes the Maestro has a firmware erase jumper
YAT is working via USB:
HTTP is enabled on port 80<LF>FTP is disabled<LF>TELNET is disabled<LF>Warning: the height map was loaded when the current Z=0 datum was not determined by probing. This may result in a height offset.<LF>Warning: Heater 0 predicted maximum temperature at full power is 182°C<LF>Warning: Heater 1 predicted maximum temperature at full p M115 FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.4.0 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2022-03-15 18:58:04<LF>ok<LF>
Ok, so it's at least got the firmware on it. That's a good sign.
Can you put the SD card in your PC and check the files there?
Replace the files in the www folder with the ones from the 3.4 DWC zip file.
Yep tried that, still no network connection.
This is my config.g:
; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 3 Pro" ; set printer name ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S0 ; physical drive 2 goes backwards M569 P3 S0 ; physical drive 3 goes backwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E405.00 ; set steps per mm M350 X32 Y32 E128 I1 ; set steps per mm for the extruder to x128 and X and Y to x32 M566 X800.00 Y800.00 Z60.00 E3000.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z900.00 E6000.00 ; set maximum speeds (mm/min) M201 X6000.00 Y6000.00 Z200.00 E5000.00 ; set accelerations (mm/s^2) M204 P600 T2000 ; set accelerations (mm/s^2) for print and travel moves M906 X750 Y750 Z750 E900 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z-0.5 S1 ; set axis minima M208 X235 Y235 Z228 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M558 C"^zprobe.in" P9 H3 F150 T8000 ; Set Z probe type to bltouch and the dive height + speeds M950 S0 C"zprobe.mod" ; Servo/gpio 0 is Z probe MOD pin G31 P500 X-50 Y-16 Z2.65 ; Set Z probe trigger value, offset and trigger height M557 X15:200 Y15:200 S20 ; define mesh grid G29 S1 ; Load height map ; Heaters M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 R2200 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" Q100 T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; map heated bed to heater 0 M143 H0 S80 ; set temperature limit for heater 0 to 80C ;M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M307 H0 A157.0 C482.1 D1.5 S1.00 V24.0 B0 ; disable bang-bang mode for the bed heater and set PWM limit (values copied from auto tune - M303 H0 S60) M308 S1 P"e0temp" Y"thermistor" T98801 B4185 R2200 ; 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 S250 ; set temperature limit for heater 1 to 250C ;M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M307 H1 A393.1 C130.5 D3.6 S1.00 V24.2 B0 ; disable bang-bang mode for heater and set PWM limit (values copied from auto tune - M303 H1 S210) ; Fans M950 F0 C"fan0" Q140 ; create fan 0 on pin fan0 and set its frequency M106 P0 C"Part" S0.4 H1 T195 ; set fan 0 name and value. Thermostatic control is turned on M950 F1 C"fan1" Q100 ; create fan 1 on pin fan1 and set its frequency M106 P1 C"Hotend" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on M950 F2 C"fan2" Q600 ; create fan 2 on pin fan2 and set its frequency M106 P2 C"LEDs" S0.1 H-1 ; set fan 2 name and value. Thermostatic control is turned off ; Tools M563 P0 S"Hotend" 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 M563 F2 ; Define LEDs tool ; Pressure Advance M572 D0 S0.30 ; Custom settings ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool ; BLTouch startup G4 S2 ; Pause a couple seconds M280 P0 S160 ; Clear any alarms G4 S2 ; Pause a couple seconds M402 ; retract pin just in case
With USB terminal connected and the ethernet cable connected, send M552, what does it reply with?
If it returns with an IP address, can you try pinging that IP from your PC?
Do the lights on the ethernet port light up with activity at all?
Do the lights on the switch/router port it's connected to light up?
M552 Network is enabled, configured IP address: 0.0.0.0, actual IP address: 192.168.1.15
No response from ping and all lights I would expect are on or flashing with activity.
I'll try Fallback procedure #1 from the link you provided and reflash 3.4 or go back to 3.3.
@iata said in Maestro issue updating from 3.3 to 3.4:
And this is the IP you're pinging?
And you're using http://192.168.1.15 to reach it?
I wouldn't try messing with the firmware just yet, as it appears to be working, but there should be no harm in trying. Remember to swap out for the DWC files for the firmware version you choose.