@droftarts that seems to have fixed this issue, thank you

@ctilley79 it's because the data was inconsistent that it took so long - it ran for the maximum 25 cycles (the minimum is 5). Inconsistent data can be caused by noise in the temperature reading, or by a change in the ambient temperature as the tuning is being done - for example, if the printer is enclosed and the bed is heating the machine and its chamber.

As @jay_s_uk says, use the values it reported despite the warning.

@dc42 Thank you for your great work!!!

@dc42 said in Strange type conversion error RRF3.5.0b4:

@OwenD I think the issue is that RRF doesn't know the time until DWC connects and passes the time to the Duet. I suggest you add a check that state.time isn't null before using it.

Nailed it!
I'll use state.upTime instead.

@RogerPodacter i understand a bit more. on a new boot up, my homeall.g runs Y gantry backwards, and does not properly hold U axis in place. i have better results if i home each axis individually. but still not fully proper operation. it seems like when the axis are in a non-homed state things go crazy, but once the axis are home (by individually homing them), the behavior is better. but still Y runs backwards.

M122

6/10/2023, 11:51:05 AM M122 B0 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: J6RFD-NR6KL-K65J0-409NN-LK02Z-7M5YU Used output buffers: 1 of 40 (36 max) Error in macro line 7 while starting up: in file macro line 7 column 16: M669: array too long, max length = 3 === RTOS === Static ram: 102996 Dynamic ram: 125840 of which 104 recycled Never used RAM 9900, free system stack 140 words Tasks: NETWORK(1,ready,17.9%,211) HEAT(3,nWait,0.1%,333) Move(4,nWait,0.0%,293) CanReceiv(6,nWait,0.1%,682) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,nWait,1.2%,74) MAIN(1,running,76.9%,688) IDLE(0,ready,2.9%,29) AIN(4,delaying,0.8%,266), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:28:20 ago, cause: software Last software reset at 2023-06-10 11:22, reason: User, Gcodes spinning, available RAM 9900, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 1700555, completed 1700555, timed out 0, errs 0 MCU temperature: min 40.7, current 43.6, max 45.1 Supply voltage: min 23.4, current 24.1, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/1684/1568, gc cycles 2377 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 23461, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 23461, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 47, reads 23461, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 23463, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 23459, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 23459, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 49, reads 23458, writes 18, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2023-06-10 11:51:05 Cache data hit count 2946444234 Slowest loop: 34.31ms; fastest: 0.11ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 34.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 15, maxWait 209667ms, bed compensation in use: mesh, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 7, completed 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP is ready with "M122 B0" 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 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000005 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 15358, received 95213, lost 0, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 284, free buffers 18 (min 17), ts 8502/8501/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 7.68ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is providing access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta3 MAC address ea:68:e7:e5:63:f4 Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 40124 WiFi IP address 192.168.1.10 Connected clients 1 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0

3HC

6/10/2023, 11:51:45 AM M122 B1 Diagnostics for board 1: Duet EXP3HC rev 1.02 or later firmware version 3.5.0-beta.4 (2023-06-08 16:24:05) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 156280, free system stack 182 words Tasks: Move(3,nWait,0.0%,182) HEAT(2,nWait,0.0%,90) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,79) CanClock(5,nWait,0.0%,70) TMC(2,nWait,5.9%,103) MAIN(1,running,92.7%,419) IDLE(0,ready,0.0%,40) AIN(2,delaying,1.3%,265), total 100.0% Last reset 00:28:59 ago, cause: software Last software reset data not available Driver 0: pos 0, 690.0 steps/mm, standstill, SG min n/a, mspos 8, reads 26111, writes 18 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 690.0 steps/mm, standstill, SG min n/a, mspos 8, reads 26112, writes 18 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm, standstill, SG min n/a, mspos 8, reads 26118, writes 13 timeouts 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00, ebfmax 0.00 Peak sync jitter -9/10, peak Rx sync delay 183, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 23.8, current 24.3, max 24.7 V12 voltage: min 12.3, current 12.3, max 12.3 MCU temperature: min 31.8C, current 32.2C, max 32.7C Last sensors broadcast 0x00003000 found 2 13 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 27864, send timeouts 0, received 29571, lost 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

1LC

6/10/2023, 11:52:13 AM M122 B20 Diagnostics for board 20: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4 (2023-06-08 16:22:30) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 1504, free system stack 142 words Tasks: Move(3,nWait,0.0%,175) HEAT(2,nWait,0.3%,97) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.0%,77) CanClock(5,nWait,0.0%,66) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,3.0%,57) MAIN(1,running,91.7%,346) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,142), total 100.0% Last reset 00:29:28 ago, cause: software Last software reset data not available Driver 0: pos 0, 690.0 steps/mm, standstill, SG min 0, read errors 0, write errors 3, ifcnt 43, reads 32422, writes 12, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00, ebfmax 0.00 Peak sync jitter -4/10, peak Rx sync delay 213, resyncs 0/0, no timer interrupt scheduled VIN voltage: min 23.7, current 24.2, max 24.6 MCU temperature: min 28.9C, current 29.2C, max 29.4C Last sensors broadcast 0x00000312 found 4 99 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 35394, send timeouts 0, received 30068, lost 0, free buffers 18, min 18, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0

EDIT: when jogging the carriage around manually, it occasionally stutters. I noticed this same behavior when i tried Beta 3 before i switched back to 3.4.2. on Beta 4 it seems this stutter behavior happens again.

@dc42
Ok goodie!

Yeah I know, I felt like a had a good enough grasp of what fields replaced the ones i allready had. Just wanted to make sure i had "structured" them right.

They've been deployed, tested and work like intended now👌

@PascalM thanks for confirming.

i was about to start a new topic. i recently upgrade to 3.5.0-Beta3 and now i have extruder issues. I use 2 toolboards 1LC on an IDEX machine. It appears that my extruder motor stops extruding during printing. it seems to happen right after a toolchange to select the new extruder. The toolchange does some fast extrude retraction.

Once this behavior happens i have to reboot the printer to restore back to normal behavior.

I am reverting back to firmware 3.4.2 for now. hopefully my issue is part of this fix in the Beta 4 next release.

@chernogorsky said in [3.5beta1] Movement issue on CNC/6xd + some minors:

M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.

We created an issue https://github.com/Duet3D/RepRapFirmware/issues/738 for this and it is in the process of being fixed.

T3P3 created this issue in Duet3D/RepRapFirmware closed M291 S2 not unblocking/Unblocking after timeout. #738

@pfn
You are correct.
I just tried it and T is allowed in M98 (and works fine).

@jay_s_uk Thanks! A simple fix indeed.

@CCS86 I was rather surprised about the "invalid base64 content", that appears to come from a G-code file (HTTP thumbnail response).

@hestiahuang thanks, this is now fixed ready for 3.5beta4.

@marvineer I doubt those two errors are related. Can you confirm that your machine is fully grounded, especially the hotend?

Thanks @marvineer and @dc42, I have fixes ready for DSF and RRF. The reason for the reset was identified by dc42 and the underlying problem was the fact that iterations, which is provided by DSF in SBC mode, wasn't populated before the set command was executed by RRF.

@dc42

It's fixed, turned out it was my cabling. I must have tweaked it somehow when I installed the filament runout sensor. Crimped a whole new set for the 8 pin and is all good now.

@dc42 - Thanks for adding your thoughts. First (in case you are busy) - we replaced the cable to the X endstop switch and the symptoms have gone away. So we are back in business.

But to your question - yes, the tool heaters showing a temperature of 2000C was part of our collection of symptoms. In the end we were able to make the problem occur consistently by setting the end stop to be an M581 T0 trigger and then activating the switch. This caused a machine halt that and also included the 2000C display. We're assuming that the 2000C is a byproduct of the halt and not part of the failure mechanism.

We were also able to cause the halt by commenting out all of the tool configuration (made us happy that this is in a separate macro) for both tools. We still forced the halt as expected.

I think this error started when I did upgrade firmware from 3.4.3 to 3.5.0beta3.
At first I didn't upgraded DuetWifiServer and then first time this error happened.
So I concluded that most likely problem was with old version od Wifi server so I upgraded to latest version.
And I did it twice because first time I was not sure if it finished correctly because error apared again.
I'm not home at the moment so I can't check if DuetWifiServer is 2.1beta4, It is 2.1 just not sure if it is beta4 or what.

Yestereday, in 3 hours got this error twice.
I'm using WiFi extender because signal was to weak for direct connecting to router if that have any importance.