I think my Duet and/or Duex5 is/are dying
-
@bpislife Firmware is as per my OP. No jitters or movement issues other than when the 8 second delay problem manifests itself (once every 3 or 4 weeks).
-
@dc42 said in I think my Duet and/or Duex5 is/are dying:
Can you pin down which module is holding it up? For example, if you comment out the M552 S1 command in config.g, does it start up at normal speed (as indicated by the hot end fan)?
You could also try connecting a PC terminal emulator via USB as soon as you restart the Duet, in case it is trying to send a message to USB. Take the usual precautions against USB ground loops.
Thanks - I'll give those suggestions a go.
-
I've just tried commenting out M552 to disable the network and it makes no difference to the slow initialisation (as indicated audibly by the hot end fan). I've also pulled out the daughter boards - I have PT 100 daughter board on the duet and a thermocouple daughter board on the Duex5 (but with nothing connected to it). They make no difference either. I can't tell if any of that makes any difference to the slow movement as that only happens once every 3 or 4 weeks and the printer is behaving itself right now.
Could you expand on what is meant by connecting a PC terminal emulator via USB?
The other thing I forgot to mention which might be relevant, is that it always does a sort of double blip of the hot end fan. That is to say, when power is first applied, the fan will run for between about 2 and 8 seconds, then it stops for about a second, then it does second run for maybe a second or two before stopping. Is that normal?
-
Hi Ian,
No the double blip is not normal. It sounds like it is resetting twice. After power up, what does M122 report as the reset reason?
By chance, today I was debugging a startup issue in our new automatic test equipment firmware, and I found that the order in which things were initialised was causing the watchdog timer to time out. The same issue potentially affects RRF, so I've applied the fix to RRF too. It will be in RRF 2.02RC4. So please try it when I release it. Although this could fix the startup issues, it's not connected with the slow running issue - that one is related to the I2C errors.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Hi David,
The M122 immediately after start is linked in my OP. It's the first one entitled "first boot m122". I appreciate that if you are on your tablet, you'll not be able to scroll up to see it so here it is again. 0_1541180301298_first boot M122.txt
TBH, it's done that "double blip" thing for as long as I can remember but usually, the fan just runs for about a second or two each time. It's just lately that the fan can run for much longer - up to 8 seconds.
I'll try 2.02 RC4 when you release it and let you know if that improves anything.
Many thanks
-
@deckingman said in I think my Duet and/or Duex5 is/are dying:
Could you expand on what is meant by connecting a PC terminal emulator via USB?
I meant connect the Duet USB port to a PC and use a terminal emulator program (e.g. YAT) on the PC to connect to the Duet. Just like the way we suggest communicating with a Duet WiFi to set up the SSID and password.
-
@deckingman said in I think my Duet and/or Duex5 is/are dying:
Aren't those jump wires too thin?
I had some issues with my PC memory from time to time. After some months if a move the cabinet then the memory had issues.
I solve that by cleaning all contacts and reinsert the memory. My hypothesis is that it oxidized a thin layer around the connection and when I moved the PC it reallocate slightly the connections causing the issue.
Maybe the ribbon cable connection have this issue. Try cleaning them with some proper product (not sure the name in English, here is "contact cleaner").
-
@brunofporto said in I think my Duet and/or Duex5 is/are dying:
@deckingman said in I think my Duet and/or Duex5 is/are dying:
Aren't those jump wires too thin?
They are good for at least 20Amps, so 480 watts@24V. Given that I only use a 200Watt PSU for entire printer and the Duex only has 5 extruders and a few fans connected to it, I'd say they are more than adequate.
-
Those brown wires are good for 20A? generally 20A means at least 14ga. Those don't look like 14ga wires.
I don't think that's your problem, but I wouldn't put 20A through what looks like 20ga wires.
-
@elmoret. Assuming by brown wires you mean the solid copper links, then I thought they were 2.5mm but they might be 1.5mm. So conservatively they are good for 20Amps - could be 27 amps if they are 2.5mm. https://www.stroma.com/news/current-carrying-capacity-for-cables
I've no idea what the US equivalent of that is but over here in the UK it's what we use for out house wiring. We call it it twin and earth and those links came out of the main insulated twin cores (not the solid earth which is thinner).
Edit. Just measured them with my digital calipers and they are 1.5mm, so good for 20Amps as I stated.
-
They look like brown, insulated wires. If they're bare copper then I agree the diameter is suitable.
I definitely wouldn't use bare exposed copper wires like that, too much risk of short, but again unrelated to the problem you're posting about.
-
@elmoret Just out of curiosity,have we met? Have I done or said something to offend you?
-
We have met, and I'm not offended, just trying to help.
-
Hi,
Have you tried a different power supply?
Frederick
-
@fcwilt said in I think my Duet and/or Duex5 is/are dying:
Hi,
Have you tried a different power supply?
Frederick
Interesting thought. Although I've never seen anything other than normal voltage, even when I've been throwing my 4.5 Kg mass around at 300 + mm/sec for hours on end. So I'm struggling to see how it could be a PSU issue but I do have another, bigger, fan cooled (and therefore noisy) one that I can try.
-
I think bare copper wire can easier get covered with patina. The get "darker" over time, maybe this makes the connection not perfect?
-
@dragonn said in I think my Duet and/or Duex5 is/are dying:
I think bare copper wire can easier get covered with patina. The get "darker" over time, maybe this makes the connection not perfect?
But there is no way of getting around that. Even if the links were insulated between the terminal blocks, the insulation still has to be stripped back where they go into the block. It has to be bare copper to make a contact. In theory, the screws make an airtight seal on the copper where it makes contact which prevent oxidisation. In any case, as per my post of 1st November 20:20, I checked for signs of oxidation where the screws bite into the copper and there is none.
-
@deckingman I thought about your problems and I have no good ideas, but maybe these thoughts help:
The sudden, seldom problem:
- power shortage or current peak. Caused by mains power or by a household appliance that produces EMC. (My experience: a switch has already once killed a lamp). Maybe too short to be in the protocol.
The regular problem:
- measuring temperaturs of the components and finding elements too hot or too cold, with a laser pointered temperature gauge. But then comparable information of a 100% working Duet would be valuable to decide. (My experience: the plug on my laptop gets warm when the contact is not good.)
-
@joergs5 Thanks for taking the time but maybe something got lost in translation.
The "sudden seldom" problem is something related to I2C errors. It's only happened 3 times in the last 4 weeks or so. Also, it's only ever happened after homing but never in the middle of a print. I guess it could be something related to the mains supply but I have an extensive computer network including a NAS and media server, numerous switches and so forth, all running on the same circuit and no other devices have shown any unusual behaviour.
The "regular problem" is simply some sort of delay in the boot up time. It happens every time the Duet is powered up or reset after editing config g. In the former case (power up) everything is at ambient temperature.
-
@deckingman Yes I missed and misunderstood some of your information.
At least you don't have damaged prints from your "sudden seldom" print. It's difficult to analyze a non-reproducible error.
In case of a delay error I would have thought of a reason like waiting for a component like Wifi, sensor or protocol feedback. Maybe a functionality in firmware and waiting for timeout (or delay, waiting e.g. for fan speed up) because it is not present or not behaving as expected. I don't know the debugger/profiler possibilites of the Eclipse development environment enough, but there should be a tool to analyze your startup exactly.
