Clean install from duetpi - incompatible firmware version...
-
I haven't updated since last January... so to be safe, I choose to preserve my old SDCARD and start fresh.
- Loaded the latest duetpi, flashed it to the card
- enabled wifi, created /boot/sh
- booted (... worked! )
- apt update
- apt upgrade
- reboot
Ok... all up and happy. I then used the latest(?) RRF Config tool and sketched out an initial config.g file. This file is far from right... but is intended as a starter.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.0 on Sat Dec 26 2020 21:05:23 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M584 X0.0 Y0.1 Z0.3 E0.2 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 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 X460 Y395 Z250 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!^io0.in" ; configure active-high endstop for low end on X via pin !^io0.in M574 Y1 S1 P"!^io1.in" ; configure active-high endstop for low end on Y via pin !^io1.in ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S1 H1 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 M575 P1 S1 B57600 ; enable support for PanelDue
After a boot, I get a ton of errors... apparently from the firmware. The versions both seem to be 3.1.1.... so not sure why this is happening. Suggestions?
12/26/2020, 9:19:05 PM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0 running on Duet 3 MB6HC Board ID: 08DJM-956L2-G43S4-6J9FD-3SJ6K-TB6LG Used output buffers: 1 of 32 (4 max) === RTOS === Static ram: 152720 Dynamic ram: 149540 of which 88 recycled Exception stack ram used: 216 Never used ram: 90652 Tasks: NETWORK(ready,1984) HEAT(blocked,1200) CanReceiv(suspended,3808) CanSender(suspended,1476) CanClock(blocked,1424) TMC(blocked,212) MAIN(running,4156) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:03:29 ago, cause: software Last software reset at 2020-12-27 05:15, reason: User, spinning module LinuxInterface, available RAM 90652 bytes (slot 0) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 49.6, current 50.0, max 50.2 Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.3, current 11.4, max 11.4, under voltage events: 0 Driver 0: standstill, reads 52504, writes 14 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 52505, writes 14 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 52506, writes 14 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 52506, writes 14 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 52509, writes 11 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 52510, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-12-27 05:19:03 Slowest loop: 2.00ms; fastest: 0.08ms === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http* is ready with "M122" 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 lcd is idle in state(s) 0 spi is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.38ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 0 of 8 - Ethernet - State: 0 Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 781, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 1 Last transfer: 14ms ago RX/TX seq numbers: 6425/6427 SPI underruns 0, overruns 0 Number of disconnects: 1 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Trigger: Finishing macro config.g, started by system > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.17 12/26/2020, 9:15:50 PM Error: Bad command: Q0 @"Miscellaneous" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Custom settings are not defined" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Tools" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Fans" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Heaters" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Z-Probe" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Endstops" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Drives" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Axis Limits" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"executed by the firmware on start-up" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"General preferences" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"Configuration file for Duet 3 (firmware version 3)" 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"generated by RepRapFirmware Configuration Tool v3.2.0 on Sat Dec 26 2020 21:05:23 GMT-0800 (Pacific " 12/26/2020, 9:15:49 PM Error: Bad command: Q0 @"" 12/26/2020, 9:15:49 PM Connection established 12/26/2020, 9:15:35 PM Connection interrupted, attempting to reconnect... 12/26/2020, 9:15:35 PM Warning: Incompatible firmware, please upgrade as soon as possible 12/26/2020, 9:15:35 PM Emergency stop, attemping to reconnect... 12/26/2020, 9:15:04 PM Connected to duet3.local
-
You're still running version 3 on the duet, not version 3.1.1.
Have another go at updating it. You may have to use bossa -
try sending
M997
to upgrade the duet, or follow https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware - skip past apt and go with the windows or pi solution using usb.(i've wrapped the usb update from the pi up in a script, so all you need to do is connect the micro usb cable from the duet to the pi and run
wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash
or follow the link above)((also review https://duet3d.dozuki.com/Wiki/USB_ground_loops to be on the safe side))
-
Thank you. M997 did the trick.
-
This post is deleted!