Faulty Toolboard 1LC V1.1?

MartinNYHC

31/07/2021, 18:39:30 	M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2592, free system stack 2789 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.0%,117) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.8%,57) MAIN(running,92.1%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:00:51 ago, cause: power up
Last software reset data not available
Driver 0: position 0, 760.2 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 25486, writes 12, timeouts 0, DMA 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
Peak sync jitter 0/5, peak Rx sync delay 192, resyncs 0/0, no step interrupt scheduled
VIN: 24.0V
MCU temperature: min 25.9C, current 30.5C, max 30.5C
Ticks since heat task active 27, ADC conversions started 51022, completed 51021, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 32 ticks ago, loop time 0
CAN messages queued 297, send timeouts 0, received 367, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0

MartinNYHC

MartinNYHC

Oh yes, and i forgot to mention that there is also a Duet3 3HC expansion board.

Duet3 6HC -> Duet3 3HC expansion -> Duet 1LC

31/07/2021, 18:41:29 	M122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41)
Bootloader ID: not available
Never used RAM 159016, free system stack 4400 words
Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,118) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.3%,63) MAIN(running,91.4%,410) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:02:49 ago, cause: software
Last software reset at 1970-01-01 04:33, reason: HardFault, available RAM 159104, slot 2
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00000001 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20005ad8 Task MAIN Freestk 3093 ok
Stack: 00000000 00000000 200014d8 a5a5a5a5 00000003 00013325 a5a5a5a4 41000000 bf800000 00000000 e200c224 4112e83a 610a0114 3020e80e 010588c4 01288500 42ae4720 24430008 0a240c0b 79340290 3a36d584 41280000 40c9d979 3f3567d9 80000010 a5a5a5a5 a5a5a5a5
Driver 0: position 0, 80.0 steps/mm,  standstill, reads 955, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 80.0 steps/mm,  standstill, reads 956, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 957, writes 11 timeouts 0, SG min/max 0/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
Peak sync jitter -1/10, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN: 24.0V, V12: 12.2V
MCU temperature: min 26.6C, current 32.2C, max 32.2C
Ticks since heat task active 235, ADC conversions started 170164, completed 170163, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 240 ticks ago, loop time 0
CAN messages queued 594, send timeouts 0, received 1982, lost 0, free buffers 37, min 37, error reg 100000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

MartinNYHC

Just disconnected the 3HC expansion board and connected the 1LC directly to the main board. Result is the same.

tecno

@martinnyhc

Check all connections to/from 1LC

MartinNYHC

Did that several times. I'm debugging since the morning when I simply replaced the toolboard.

There are only two, power and CAN bus. That's the reason why I'm using it

tecno

@martinnyhc
Also using V1, had this problem = bad connection on CAN or the thermistor.

dc42

@martinnyhc if you send M308 S1 what response do you get?

Have you tried using the temp0 connector on the tool board instead of temp1?

MartinNYHC

31/07/2021, 19:34:26 	M308 S1
Sensor 1 type Thermistor using pin 121.temp1, reading 2000.0, last error: bad Vssa, T:100000.0 B:3950.0 C:0.00e+0 R:2200.0 L:-22 H:-1

dc42

@martinnyhc if you disconnect the thermistor from the tool board, do you still get the "bad VSSA" response to that command?

MartinNYHC

Yes, it's the same result.

And yes, I already tried temp1. I tried everything I could think of Tried to isolate the problem but unfortunately without success. Lucky me, that I have so many spare parts except a toolboard.

31/07/2021, 19:39:18 	M308 S1
Sensor 1 type Thermistor using pin 121.temp1, reading 2000.0, last error: bad Vssa, T:100000.0 B:3950.0 C:0.00e+0 R:2200.0 L:-22 H:-1

dc42

@martinnyhc the "bad VSSA" error even with no thermistors connected suggests a faulty tool board. Please send an email to warranty@duet3d.com.

MartinNYHC

Will do so. Thanks for our support.

tecno

@martinnyhc

Looking at the picture there is no CAN terminator or is there?

MartinNYHC

@tecno said in Faulty Toolboard 1LC V1.1?:

terminator

It is, but on the back

tecno

@martinnyhc

OK, just checking

dc42

@martinnyhc said in Faulty Toolboard 1LC V1.1?:

Will do so. Thanks for our support.

No problem, I'm sorry for the inconvenience.

Note to warranty processing: check F1 R32 R36 R47

MartinNYHC

@dc42 said in Faulty Toolboard 1LC V1.1?:

Note to warranty processing: check F1 R32 R36 R47

Sorry, but what does that mean?

T3P3Tony

@martinnyhc Just @dc42 letting us know things that should be tested on the board. Please email warranty@duet3d.com. with this thread and we will take it from there.

dc42

@martinnyhc said in Faulty Toolboard 1LC V1.1?:

@dc42 said in Faulty Toolboard 1LC V1.1?:

Note to warranty processing: check F1 R32 R36 R47

Sorry, but what does that mean?

That was for us, so that whoever checks your board knows what to look at.

However, there is a possibility that we may not need to replace your board. We made a change to the version 1.1 board that affects the Vssa reading a little, and I forgot to adjust the firmware accordingly. So your board might be close to the tolerance limit, allowing it to pass our test procedure but fail in your environment.

Do you have a multimeter? if so, then with power off, please measure the resistance of the green polyfuse on the board. It should be just a few ohms.