thermistor noise
-
I am sitting here and waiving a giant white flag ..... I give up
I tried out my third printer - totally flat temperature. I tried out my last tool on the printer with the noise issue - same thing. I wrapped a bare copper wire around the thermistor line and then wrapped that in aluminum foil and connected the bare drain wire to io2 gnd on my 1LC tool board ..... no change.
I upgraded the firmware from 3.5.0 rc2 to rc3 with no change noted (although I didn't expect a change)I have a nagging feeling that maybe the issue is related to the 1LC tool board and data being transferred on the CAN bus (since the two Duet2 printers do not have the issue). Of course I have nothing to back up that feeling ....
-
To confirm. on this machine, you have multiple tools, all of which display flat temperature graphs at any set temperature when they are not moving, but have these small blips when moving?
Are there any can bus errors reported?
(you can use M122 Bnn to get the reports from the boards)
-
@T3P3Tony .... yes, that is correct.
I don't know how applicable the following section of M122 is. The last print job was about 12 hours ago and when I do M122 now I get the following for the CAN section:
=== CAN ===
Messages queued 1009613, received 5566617, lost 0, errs 1, boc 0
Longest wait 4ms for reply type 6013, peak Tx sync delay 455, free buffers 50 (min 48), ts 339389/339388/0
Tx timeouts 0,0,0,0,0,0 -
@jens55 please also send M122 Bnn where nn is the address of the tool that was used in tat print
-
@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 -
@jens55 thanks, doe snot look like CAN bus errors.
-
@T3P3Tony, does 'hiccups 29242' not indicate issues of some kind?
-
woops did not see the hiccups as was just looking at the CAN
-
@jens55 yes possibly. what steps/mm are you running your extruder at?
-
@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.000First extruder is an LGX, others are BMG clones
-
@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.
-
@T3P3Tony , from config.g: M350 E16:16:16:16 I1 which I am interpreting as 16 microstepping.
-
are you running .9 degree steppers on the extruders?
-
@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. -
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 (-;
-
@oliof .... 'mind goblin' ..... must remember that .... priceless
-
@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-104Depending on which comes first, M350 and M92, they influence each other
-
Microstepping - X:16(on), Y:16(on), Z:16(on), U:4(on), E:16(on):16(on):16(on):16(on)
-
@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 -
@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).gI see that I didn't update the comments on my M570 commands, please ignore
