Faulty Toolboard 1LC V1.1?

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.

MartinNYHC

@dc42 It measures 0.9 ohms.

dc42

@martinnyhc, please can you install just the tool board firmware (not the other binaries) from https://www.dropbox.com/sh/ja08b7qdzsl8kjc/AAAwUbkN2XJvurq5CuQTgx5Wa?dl=0 and then get a M122 report from that board. I've added extra diagnostics so that I can tell whether it is a tolerance issue or a fault.

MartinNYHC

@dc42

31/07/2021, 20:59:38 	M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.4beta1+ (2021-07-31 19:12:33)
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:01:13 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 36493, 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 1/4, peak Rx sync delay 192, resyncs 0/0, no step interrupt scheduled
VIN: 24.0V
MCU temperature: min 31.7C, current 35.6C, max 35.6C
Ticks since heat task active 39, ADC conversions started 73034, completed 73033, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 44 ticks ago, loop time 0, Vref 42954 Vssa 41196
CAN messages queued 451, send timeouts 0, received 528, 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

But still the same heater error.

dc42

@martinnyhc thanks, from your M122 report I can see that your tool board is definitely faulty. Looks like either the green PTC fuse isn't properly soldered, or resistor R47 next to it isn't properly soldered. Warranty replacement.

MartinNYHC

If you say that Sent an email as you suggested.

A Former User

@martinnyhc
@dc42
I think I have the same problem.
Can you please help me

Cheers Richard

Phaedrux

@gruna-studio I suggest you start your own new thread with your issue and include as much information as possible. Posting to other peoples threads saying you have the same problem is not a productive way to troubleshoot.

A Former User

@phaedrux
Already done 2 days ago, no one has replied.
Problem solved by chaning toolboard...
thanks

Phaedrux

@gruna-studio This one? https://forum.duet3d.com/topic/27666/tool-not-picking-up?_=1646967812005 I think I missed it.

A Former User

@phaedrux yes
No worries
I can imagine there is lots of work