Firmware downgrade

[Meltex]

@Phaedrux said in Firmware downgrade:

make sure you remove any M82 commands

Unfortunately, Cura puts M82 anyway:

And, before upgrading it worked without issues.

[Phaedrux]

Yes it will start with an M82 regardless, but will add the M83 as well after the start gcode.

;FLAVOR:RepRap
;TIME:11752
;Filament used: 24.7369m
;Layer height: 0.2
;MINX:115.035
;MINY:60.6
;MINZ:0.2
;MAXX:188.995
;MAXY:213
;MAXZ:38
;Generated with Cura_SteamEngine 4.7.1
T0
M190 S50
M104 S210
M109 S210
M82 ;absolute extrusion mode
M98 P"0:/sys/PrimeNozzle.g"
M98 P"0:/sys/StartGCode.g"
M83 ;relative extrusion mode
G10
;LAYER_COUNT:190
;LAYER:0
M107
G0 F3600 X115.806 Y62.782 Z0.2
;TYPE:SKIRT
G11
G1 F1800 X116.063 Y62.396 E0.02314

In your prime_extruder file you should specify if you want to be in relative or absolute extrusion mode.

prime_extruder.g

G92 E0                ; Zero extruder
G0 X30 Y0 F12000
G0 Z0.3 F9000         ; Move down

G1 X230 E30 F500       ; Extrude 30mm offilament over 200mm X axis
G1 X240 F500           ; Move 10mm without extracting
G92 E0                ; Reset extruder
G1 Z1 F9000

It looks to be formatted for absolute, and has the G92 E resets, so it should work either way.

Regardless, getting back to the tool boards. Did you confirm that they were also running 3.2?

You can then check the installed firmware versions with M122, M122 B1, M122 B2, etc.

[Meltex]

@Phaedrux said in Firmware downgrade:

Regardless, getting back to the tool boards. Did you confirm that they were also running 3.2?

Confirm.

[Phaedrux]

Would you be able to capture a M122 for the mainboard and tool board after experiencing the print problems? And to share that gcode file.

[Meltex]

@Phaedrux said in Firmware downgrade:

Would you be able to capture a M122 for the mainboard and tool board after experiencing the print problems? And to share that gcode file.

Need some time. I'm reinstalling the software on RPi right now.

[Meltex]

@Phaedrux said in Firmware downgrade:

Would you be able to capture a M122 for the mainboard and tool board after experiencing the print problems?

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D8-3SN6T-1AAYV
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63740 of which 92 recycled
Never used RAM 145212, free system stack 128 words
Tasks: Linux(ready,77) HEAT(blocked,296) CanReceiv(blocked,834) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,19) MAIN(running,671) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:05:17 ago, cause: power up
Last software reset at 2021-01-22 21:45, reason: User, GCodes spinning, available RAM 147812, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 29.1, current 34.4, max 36.4
Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: position 52000, standstill, reads 532, writes 27 timeouts 0, SG min/max 0/1023
Driver 1: position -50400, standstill, reads 531, writes 28 timeouts 0, SG min/max 0/1023
Driver 2: position 12253, standstill, reads 526, writes 33 timeouts 0, SG min/max 0/941
Driver 3: position 0, standstill, reads 526, writes 33 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 526, writes 33 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 526, writes 33 timeouts 0, SG min/max 0/703
Date/time: 2021-01-22 22:01:36
Slowest loop: 165.12ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 105941ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 420, completed moves 420, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 5], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1449, send timeouts 0, received 3694, lost 0, longest wait 2ms for reply type 6049, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 10985/10985
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 13.87
Maximum length of RX/TX data transfers: 2792/1512

M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4032, free system stack 52 words
HEAT 90 CanAsync 89 CanRecv 83 TMC 54 MAIN 218 AIN 64
Last reset 00:06:26 ago, cause: power up
Last software reset data not available
Driver 0: position 1900, 415.0 steps/mm, standstill, SG min/max 0/304, read errors 0, write errors 0, ifcnt 15, reads 62126, writes 15, timeouts 0, DMA errors 0
Moves scheduled 145, completed 145, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 40.9C, current 46.9C, max 48.4C
Ticks since heat task active 212, ADC conversions started 384990, completed 384989, timed out 0
Last sensors broadcast 0x00000002 found 1 215 ticks ago, loop time 0
CAN messages queued 4534, send timeouts 0, received 3665, lost 0, free buffers 36

Nothing was extruded at all. My priming script was off. V350_20mmTestCube_repaired.gcode

[Phaedrux]

And when sliced with absolute extrusion it works fine?

[Meltex]

@Phaedrux said in Firmware downgrade:

And when sliced with absolute extrusion it works fine?

Yes. I stopped printing after 2 successful layers.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D8-3SN6T-1AAYV
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63740 of which 92 recycled
Never used RAM 145212, free system stack 128 words
Tasks: Linux(ready,83) HEAT(blocked,296) CanReceiv(blocked,834) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,19) MAIN(running,705) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:05:12 ago, cause: power up
Last software reset at 2021-01-22 22:12, reason: User, GCodes spinning, available RAM 145212, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 27.9, current 34.7, max 35.1
Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: position 52000, standstill, reads 31010, writes 27 timeouts 0, SG min/max 0/1023
Driver 1: position -50400, standstill, reads 31011, writes 27 timeouts 0, SG min/max 0/1023
Driver 2: position 12453, standstill, reads 31006, writes 32 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 31006, writes 32 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 31006, writes 32 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 31006, writes 32 timeouts 0, SG min/max 0/1023
Date/time: 2021-01-22 22:17:38
Slowest loop: 164.33ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 107133ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 671, completed moves 671, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1655, send timeouts 0, received 3629, lost 0, longest wait 2ms for reply type 6049, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 10758/10758
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 9.49
Maximum length of RX/TX data transfers: 2816/1480

M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4032, free system stack 50 words
HEAT 90 CanAsync 89 CanRecv 83 TMC 54 MAIN 218 AIN 64
Last reset 00:06:01 ago, cause: power up
Last software reset data not available
Driver 0: position 60224, 415.0 steps/mm, standstill, SG min/max 0/304, read errors 0, write errors 0, ifcnt 14, reads 49787, writes 14, timeouts 0, DMA errors 0
Moves scheduled 374, completed 374, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 48.8C, current 52.6C, max 54.6C
Ticks since heat task active 32, ADC conversions started 360855, completed 360854, timed out 0
Last sensors broadcast 0x00000002 found 1 35 ticks ago, loop time 0
CAN messages queued 4238, send timeouts 0, received 3670, lost 0, free buffers 36

[Meltex]

V350_20mmTestCube_repaired_no_relative.gcode

[Phaedrux]

Can you share these macros?

; Velocity, acceleration, and current settings are in these macros

M98 P"/macros/Drive/xy_fullcurrent.g"
M98 P"/macros/Drive/z_fullcurrent.g"
M98 P"/macros/Drive/e_fullcurrent.g"

[Meltex]

@Phaedrux z_fullcurrent.g xy_fullcurrent.g e_fullcurrent.g

[Phaedrux]

Thanks.

Very strange.

Will take a look.

[Meltex]

Just found out another thing. In spite of successful print, if I start printing the same job right after finished one the first layer becomes a mess. But if I restart printer by switching the power off an on the model is being printed with no issues.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9D8-3SN6T-1AAYV
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63740 of which 168 recycled
Never used RAM 145136, free system stack 126 words
Tasks: Linux(ready,83) HEAT(blocked,296) CanReceiv(blocked,809) CanSender(blocked,335) CanClock(blocked,352) TMC(blocked,19) MAIN(running,717) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:28:13 ago, cause: power up
Last software reset at 2021-01-22 22:12, reason: User, GCodes spinning, available RAM 145212, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 27.3, current 37.9, max 38.0
Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
Driver 0: position 52000, standstill, reads 14513, writes 31 timeouts 0, SG min/max 0/1023
Driver 1: position -50400, standstill, reads 14512, writes 32 timeouts 0, SG min/max 0/1023
Driver 2: position 12153, standstill, reads 14498, writes 46 timeouts 0, SG min/max 0/1021
Driver 3: position 0, standstill, reads 14498, writes 46 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 14498, writes 46 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 14499, writes 46 timeouts 0, SG min/max 0/1023
Date/time: 2021-01-23 19:26:43
Slowest loop: 175.45ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 134829ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4010, completed moves 4010, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 235551, send timeouts 0, received 63653, lost 0, longest wait 2ms for reply type 6031, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 1465/1465
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 48.83
Maximum length of RX/TX data transfers: 2880/1684

M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 4032, free system stack 50 words
HEAT 86 CanAsync 89 CanRecv 83 TMC 54 MAIN 218 AIN 64
Last reset 01:28:35 ago, cause: power up
Last software reset data not available
Driver 0: position 2810351, 415.0 steps/mm, standstill, SG min/max 0/112, read errors 0, write errors 0, ifcnt 16, reads 36525, writes 16, timeouts 0, DMA errors 0
Moves scheduled 214161, completed 214161, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 56.6C, current 70.4C, max 74.8C
Ticks since heat task active 1, ADC conversions started 5294991, completed 5294990, timed out 0
Last sensors broadcast 0x00000002 found 1 5 ticks ago, loop time 0
CAN messages queued 63941, send timeouts 0, received 262230, lost 0, free buffers 36

[deckingman]

@dc42 said in Firmware downgrade:

What issues are you having? Right now I can't think of any issues present in firmware 3.2 that are not also present in earlier versions.

Is that some sort of bad joke? This is new in 3.2 as I have repeatedly pointed out.

https://forum.duet3d.com/topic/20756/error-homing-failed-after-upgrade-to-rrf3-2/23