Duet 3 + Tool board intermittent error

evomotors

Update. E3d Volcano nozzle, BLTouch pin, and BMG extruder body also destroyed.

Veti

i am not a big fan of the bltouch. especially for the reason, that if the probe does not deploy it does not recognize it.

i prefer this simple design. https://www.thingiverse.com/thing:3303618 works just like a bltouch, but has some advantages.
unless deployed its triggered. meaning if it does not deploy probing will stop.
its optical/mechanical, not prone to interference like the bltouch
its cheap and has a very good repeatability.

Phaedrux

@evomotors Sorry to hear you've had such misfortune. Did it still produce the original error message?

A Former User

@evomotors said

It happen again for no reason.

This is wrong, there is a reason you just haven't found what that reason is yet

I'm not getting any support for this issue and will strongly suggest not to buy the duet tool boards on my 2500+ members forum.

From looking at this thread I would say that you have 100 % been receiving support.

Please let me know how to return this buggy piece of hardware and get my money back.

You appear to be blaming the hardware without any concrete proof of it being at fault.

Whining like a little girl, stamping your feet after spitting your dummy out, screaming you don't recommend something just because you don't know how to carry out in-depth and logical diagnostics isn't really doing to endear you to anyone

Might I suggest that you take up another form of additive manufacturing, much simpler it only uses three components.

Its called knitting, you only need two needles and a ball of yarn.

T3P3Tony

@evomotors while the Toolboard is designed to be ok up to 85C, and that limit it the electrolytic capacitors and not the processor it might be the temp that's causing the issue. If you would be ok for us to exchange the Toolboard and you can run a series of tests (without actually probing the bed to avoid further damage) then we can see if the issue is reproducible.

evomotors

@T3P3Tony said in Duet 3 + Tool board intermittent error:

@evomotors while the Toolboard is designed to be ok up to 85C, and that limit it the electrolytic capacitors and not the processor it might be the temp that's causing the issue. If you would be ok for us to exchange the Toolboard and you can run a series of tests (without actually probing the bed to avoid further damage) then we can see if the issue is reproducible.

I have 3 ball-screws and 3 independent motors and probe 3 points and center before each print. So when it happened last time, the DWC reported that probe is already triggered and aborted further probing, but it started the print.

Is there any configuration I can use not to start the print on leveling error?

Are you suspecting that one or more capacitors on my tool-board may not handling enclosure temperature? Or what is the reason to exchange the board?

T3P3Tony

@evomotors

I am not suspecting the capacitors - just pointing out that the temperature should be ok as far as CAN bu stability. I was suggesting swapping the toolboard to see if either we could reproduce a problem with that specific toolboard - or if you could reproduce the problem with a new toolboard.

dc42

@evomotors said in Duet 3 + Tool board intermittent error:

I have 3 ball-screws and 3 independent motors and probe 3 points and center before each print. So when it happened last time, the DWC reported that probe is already triggered and aborted further probing, but it started the print.
Is there any configuration I can use not to start the print on leveling error?

Yes. I assume you are using G32 in your slicer start GCode to perform levelling. In your bed.g file, after each G30 line add the following lines:

if result != 0
  abort "Print cancelled due to probing error"

evomotors

@T3P3Tony said in Duet 3 + Tool board intermittent error:

@evomotors

I am not suspecting the capacitors - just pointing out that the temperature should be ok as far as CAN bu stability. I was suggesting swapping the toolboard to see if either we could reproduce a problem with that specific toolboard - or if you could reproduce the problem with a new toolboard.

I agree replace the board and or to perform any tests you want me to do.

dc42

@evomotors said in Duet 3 + Tool board intermittent error:

I agree replace the board and or to perform any tests you want me to do.

Thanks, we'll get you a new tool board ASAP. Which reseller did you buy it from?

evomotors

@dc42 said in Duet 3 + Tool board intermittent error:

Which reseller did you buy it from?

Filastruder

dc42

Thanks, I've asked Tim at Filastruder to send you another one.

I've added a check in the for coming 3.2beta version of RepRapFirmware that the tool board acknowledges the Z probe configuration before it start a probing move. However, I still need to find out why the tool board either lost communication or reset.

evomotors

@dc42 said in Duet 3 + Tool board intermittent error:

Thanks, I've asked Tim at Filastruder to send you another one.

I've added a check in the for coming 3.2beta version of RepRapFirmware that the tool board acknowledges the Z probe configuration before it start a probing move. However, I still need to find out why the tool board either lost communication or reset.

I wonder how they know where to send? Are they found me by email?

T3P3Tony

@evomotors Not sure, Tim may be in contact if you used a different email

elmoret

@evomotors said in Duet 3 + Tool board intermittent error:

@dc42 said in Duet 3 + Tool board intermittent error:

Thanks, I've asked Tim at Filastruder to send you another one.

I've added a check in the for coming 3.2beta version of RepRapFirmware that the tool board acknowledges the Z probe configuration before it start a probing move. However, I still need to find out why the tool board either lost communication or reset.

I wonder how they know where to send? Are they found me by email?

Yes, looked up your order history by forum email. Replacement on the way tomorrow.

evomotors

@elmoret said in Duet 3 + Tool board intermittent error:

Yes, looked up your order history by forum email. Replacement on the way tomorrow.

Already got FedEx notification about shipment.
What and how do you want me to test?

dc42

@evomotors said in Duet 3 + Tool board intermittent error:

What and how do you want me to test?

Can you think of a way to test whether the issue occurs with the new board, without risking damage to your machine if it does?

What I would like to determine is:

Whether the new board resolves the issue.
If it doesn't, what is causing the board to reset. I will probably have to send you new tool board firmware in order to diagnose this.

The 3.2beta1 firmware that we expect to release very soon has an additional check that prevents probing from starting unless the main board has confirmation of the proibe configuration from the tool board. This should protect against the worst consequences of the problem if it occurs again; but obviously it's better not to rely on that.

evomotors

@dc42 said in Duet 3 + Tool board intermittent error:

Can you think of a way to test whether the issue occurs with the new board, without risking damage to your machine if it does?
What I would like to determine is:

Whether the new board resolves the issue.
If it doesn't, what is causing the board to reset. I will probably have to send you new tool board firmware in order to diagnose this.

The 3.2beta1 firmware that we expect to release very soon has an additional check that prevents probing from starting unless the main board has confirmation of the proibe configuration from the tool board. This should protect against the worst consequences of the problem if it occurs again; but obviously it's better not to rely on that.

I can try to heat-up the chamber to 70, check processor temperature, try to level. I added if condition after each G30 in bed.g per your recommendation. Should save me from another accident.

evomotors

M122 B121
Diagnostics for board 121:
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)
Never used RAM 8.4Kb, max stack 652b
HEAT 1040 CanAsync 1396 CanRecv 1380 TMC 156 AIN 524 MAIN 2284
Last reset 13:29:51 ago, cause: software
Driver 0: standstill, SG min/max 0/272, read errors 0, write errors 1, ifcount 119, reads 49507, writes 21, timeouts 1, DMA errors 0, failedOp 0x80
Moves scheduled 483088, completed 483088, hiccups 4661
VIN: 24.2V
MCU temperature: min 46.5C, current 60.4C, max 66.8C
Ticks since heat task active 85, ADC conversions started 48585415, completed 48585414, timed out 0
Last sensors broadcast 00000002 found 1 89 ticks ago
Free CAN buffers: 36
NVM user row b1d088a9 fffff8bb 20002a18 b
TSENS 001790 GAIN 014ffc OFFS 00273f CAL 1f2a

do I need to be worry about these?

hiccups 4661
write errors 1
timeouts 1
failedOp 0x80

Driver 0: standstill, SG min/max 0/272, read errors 0, write errors 1, ifcount 119, reads 49507, writes 21, timeouts 1, DMA errors 0, failedOp 0x80
Moves scheduled 483088, completed 483088, hiccups 4661

dc42

It's common to get 1 write error and 1 timeout when the board starts up.

Hiccups are normally caused by the step rate being higher than the board can handle; however the 3.1.0 tool board firmware has an unusually low maximum step rate, which has been improved since then.