Duet 6HC + 3HC + 3HC one expansion does not connect

MaracMB

Flashed the bootloader on the one that works. It now connects CAN immediateley. And DIAG led flashing. As it should. Out of the box.
The second one i guess just has bootloader corrupt out of the box as suspected. No diagnostic indication, just sitting there.

I am NOT paying 124 eur for Atmel ICE. This is absurd. I'll just RMA it. Indefinetly if it need to be. Shame on you Duet3d!
No usb cable supplied, corrupt bootloader, not even basic 1 eur straight through CAN cables... just a shame at this price.

deckingman

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

@deckingman you can have 17 extruders but this duet 3 is still an overpriced, out of the box underequipped, non working... thing.
Serials are practically sequential. and one works, one does not. so it's either bad distributor or vendor that does not do QC.

Don't have pop at me pal - I'm not affiliated to Duet - just an end user like you but trying to help. Best of luck.

MaracMB

@maracmb sorry if you took it that way. I know you're not affiliated. I know you tried to help, and that is greatly appreciated.

jay_s_uk

@maracmb what firmware version are you currently running?

MaracMB

@jay_s_uk latest beta. 3.4. beta7 but that does not matter. The board, even new, never blinked DIAG led - it does not even boot i guess It acts totally differently now that new bootloader is flashed.
and since I can not connect the other non connectable 3HC via CAN, i can't easily flash bootloader on it unless i buy a 125 euro programmer for it. It's real bummer. The only good thing is that i bought complete movement set, one expasion was an easy fix, so in time i finnish building XY plane (for that i only need 6HC and 3HC) the replaced board will arrive and i'll connect Z towers then. Hopefully.
And i am pretty sure I am not the only one that got the bad bootloaders. So people that just can't get it connected: it's not the firmware, didn' even got to that, it's basic bootloader.

jay_s_uk

@maracmb i found that bad bootloader stuff for me and my very early 3HC came in some time around 3.2
It may be worth going back to 3.1.1 on the 6HC and seeing what happens then.
What voltage are you powering them from?
I also found it worked with 12v but not 24v

MaracMB

@jay_s_uk run it on 24 but i can try 12v... i could revert, but the DIAG led should at least do something whatever firmware it has. or not? funny thing is, the board that works has serial ending 71, and the one that does not has 69.
Anyways, not doing this because it should work. does not. I'll RMA it. This is why i bought original not cloned.

JA

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

it only connects to second of my two 3HC expansion boards. The first one in row does not connect but second one does

I have the same board configuration (MB6HC + EXP3HC + EXP3HC). I had a problem where address number 1 never worked but address number 2 worked fine.

It was a problem with my CAN cables, you should try changing the boar order, put your first expansion in the second position to check if the board actually works.

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

Flashed the bootloader on the one that works .......The second one ........ No diagnostic indication

I think that even if your CAN cables are wrong the diagnostic led should blink.
Try uploading a new bootloader after changing the board order.

MaracMB

@ja cabels are well made. Swapped them. No change. Reordered and also used only that one board. No change. Shuffled addresses. No change.

Since DIAG led is not lighting up even a bit, yes, i would have to load a bootloader. That can be done via CAN bus, or, if for some strange reason you get your bootloader *ucked up out of the box, theoretically with Atmel ICE. Which is a 125 eur device that you then use one time on a 125 eur board.
But yeah. Agree 100%

MaracMB

@dc42 i ask for warranty approval.

JA

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

cabels are well made.

Since the board doesn't come with CAN cables, you had to make them. It could be that your cables are not well made.

When i had my cables wrong i saw this behaviour, the second board on the CAN network worked but the first one didn't.
The CAN cables were crossing the signal, and because the second device on the network has passed from 2 cables, it had the signal crossed twice, this is the same as having the cables straight, so the second device on the network worked fine.

It doesn't mather the CAN address you asing to that board, if you use the correct adderss when sending comands.

dc42

@maracmb if the DIAG LED is not lighting up at all, that indicates that the bootloader hasn't passed the clock startup phase. What we think is happening is that some boards are sensitive to temperature and/or supply voltage in such a way that under certain conditions, the clock does not stabilise in the time allowed by older versions of the bootloader. When this happens, the board repeats the startup process.

If you are ever able to get the board to start up (perhaps by leaving it powered up for a long time, or trying a 12V supply instead of a 24V supply), then you can upgrade the bootloader to fix this, which is what you have done with your other board. If you are not able to get the board to start up, then please email warranty@duet3d.com with a link to this thread and we will arrange for the board to be replaced.

MaracMB

@dc42 thank you. I've let it sit there on 12 volts for 2 hours. then 2 hours on 10 volts. it was 2 hours on 24 volts before so... sadly, no luck with booting. The other one with a newest bootloader is ticking like expected. Thanks again.

MaracMB

@dc42 DOLD mechatronics sent another 3HC board. It now connected and updated instantly. Under a minute job after i got replacement.
Now to figure out this M669 for quad markforged kinematics matrix stuff.. not sure if excited or scared down to the bones.

Maybe see ya in another thread I think i'll make something like this for my signature when 1s, -1s and 0s are in place

M669 K1 X1:1:0:0:0:0:0:0:0:0:0 Y1:-1:0:-1:0:0:0:0:0:0:0 Z0:0:1:0:0:0:0:0:0:0:0 U0:0:0:1:0:0:0:0:0:0:0 V0:0:0:1:0:0:0:0:0:0:0 W0:0:0:1:0:0:0:0:0:0:0 A0:0:0:1:0:0:0:0:0:0:0

Thanks for warranty.

dc42

@maracmb you might like to check which bootloader version is installed on the replacement board.