thermistor noise

T3P3Tony

@jens55 please also send M122 Bnn where nn is the address of the tool that was used in tat print

jens55

@T3P3Tony
Diagnostics for board 22:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-rc.3 (2024-01-24 17:55:14)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2504, free system stack 83 words
Tasks: Move(3,nWait 7,1.7%,75) HEAT(2,nWait 6,4.5%,91) CanAsync(5,nWait 4,0.0%,55) CanRecv(3,nWait 1,1.4%,65) CanClock(5,nWait 1,0.3%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,45.4%,53) MAIN(1,running,94.5%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,61.8%,112), total 209.5%
Owned mutexes:
Last reset 18:57:01 ago, cause: software
Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 1
Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task Freestk 129 bad marker
Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7
Driver 0: pos 0, 830.0 steps/mm, standstill, SG min 0, read errors 8, write errors 1, ifcnt 97, reads 64588, writes 24, timeouts 18, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 0 done 49866182
Moves scheduled 397888, completed 397888, in progress 0, hiccups 29242, segs 36, step errors 0, maxLate 2 maxPrep 492, maxOverdue 4104, maxInc 2537, mcErrs 0, gcmErrs 0, ebfmin -1.00 max 1.00
Peak sync jitter -1/4, peak Rx sync delay 276, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 20.8, current 24.5, max 45.3
MCU temperature: min 37.6C, current 37.9C, max 52.7C
Last sensors broadcast 0x00000004 found 1 192 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1398984, send timeouts 0, received 1831005, lost 0, errs 0, boc 0, free buffers 18, min 17, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 555, adv 35520/74673
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, contentions 0, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 4 to 4256us
Driver 0: ok

T3P3Tony

@jens55 thanks, doe snot look like CAN bus errors.

jens55

@T3P3Tony, does 'hiccups 29242' not indicate issues of some kind?

T3P3Tony

woops did not see the hiccups as was just looking at the CAN

T3P3Tony

@jens55 yes possibly. what steps/mm are you running your extruder at?

jens55

@T3P3Tony
M92 E25.3:51.875:51.875:51.875
Note that prints were done on the first 3 boards. The first tool uses a different extruder from the other two but blips showed up just as they did on the other tools.

The above was from config.g, below is what I get back from sending M92 to the printer:
m92
Steps/mm: X: 100.000, Y: 100.000, Z: 3200.000, U: 30.578, E: 404.800:830.000:830.000:830.000

First extruder is an LGX, others are BMG clones

T3P3Tony

@jens55 can you try using 16 microstepping with interpolation (it looks like you are using 256 microstepping?) that could well be the issue with the hiccups.

jens55

@T3P3Tony , from config.g: M350 E16:16:16:16 I1 which I am interpreting as 16 microstepping.

oliof

are you running .9 degree steppers on the extruders?

jens55

@oliof, I actually do not know the degrees/step for the two type of motors but the e-steps of the two kinds of motors are different while the temperature blips happen with both.
I don't quite get the connection between degrees/step or microstepping setting as it pertains to either the temperature blips or the hiccups.

oliof

it's just a mind goblin that's vexing me looking at possible "overload" sources on toolboards that may cause these blips. I have nothing to back this, so it's safe to ignore (-;

jens55

@oliof .... 'mind goblin' ..... must remember that .... priceless

T3P3Tony

@jens55 yeah lets address the source of the hiccups (likely to be too high microstepping) and then see if the blips are still there.

What does M350 report when run from the console?

See:
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#examples-104

Depending on which comes first, M350 and M92, they influence each other

jens55

@T3P3Tony

Microstepping - X:16(on), Y:16(on), Z:16(on), U:4(on), E:16(on):16(on):16(on):16(on)

T3P3Tony

@jens55 hmm ok, not sure how that can be the same and M92 be so different.

Sorry to be a pain but please post the full config.g and confirm that the output on the console is:
M350
Microstepping - X:16(on), Y:16(on), Z:16(on), U:4(on), E:16(on):16(on):16(on):16(on)

And
m92
Steps/mm: X: 100.000, Y: 100.000, Z: 3200.000, U: 30.578, E: 404.800:830.000:830.000:830.000

jens55

@T3P3Tony
For ease of calculation, the microstepping was applied after the M92 command. I believe this was arranged like that in the Jubilee config files and I kept a good portion of the example files including that section.

I can confirm the M350 and M92 outputs.

Here is my rather verbose config.g file:
config(2).g

I see that I didn't update the comments on my M570 commands, please ignore

oliof

@jens55 why does U only have 4x microsteps?

T3P3Tony

Ok so now I see. This config is made to calculate everything from first principles so hence the weird numbers you reported before:

M350 X1 Y1 Z1 U1 E1    ; Disable microstepping to simplify calculations
.....
M92 E25.3:51.875:51.875:51.875
.....
M350 E16:16:16:16 I1   ; 16x microstepping for Extruder axes. Use interpolation.

That together will give you:
25.316 = 404.8
51.87516=830

Which are what is reported by M92 when its running.

So scratch the idea that the microstepping is too high and that directly is causing hiccups.

Can you do the following:

First run a test print to see if you get hiccups, every time you send M122 Bnn the hiccup counter is reset. so if you send it multiple times, keep a record of each one.

Then generate a simple set of test print jobs that moves back and forward (e.g. between X10 and X100) for enough times that you would definitely see the blips if it was a print job. (I would use a text editor to cut and past the line in blocks)

Run with movement, the hot end at temperature, but no part cooling fan and no extrusion. Look for blips and also grab M122 and M122Bnn
Run with the movement, no part cooling, but extrusion (you can have filament not fitted to avoid having a bit of spaghetti to clear up and wasting filament). Look for blips and hiccups and also grab M122 and M122Bnn
Run test 2, but manually setting the part cooling fan to the levels used by your slicer, and looking to see if there are blips as its on and off, or from (say 80% to 100% or other combinations). Look for blips, hiccups and also grab M122 and M122Bnn

Thanks.

jens55

@oliof
U is the actuator that locks the tool to the carriage. It does not need to be accurate. In fact, the actuator connects to a clutch mechanism that puts a fixed pressure on things so the position of U only needs to be sort of in the ballpark to do it's job.