Got the replacement DueX5 unit today from filastruder and all is working just fine! Problem solved. Thank you for the support here.

No need for an apology, these things can happen. At this point I just hope it’s actually the X5. My duetWiFi seems to be working just fine though and has never given me a reason to doubt it.

Edit: The direct support and contact with the hardware designers is just top notch. Thank you.

Got the new ribbon cable tried it and still no luck. The cable looks just fine, exactly the same as the old one. I'll be contacting filastruder to start a warranty replacement on the X5.

@dc42 said in DuetWIFI not detecting DueX5:

Please confirm that you have a short cable between the negative sides of the VIN connectors on the Duet and the X5. Not a long cable between each VIN block and the PSU.

Confirmed.

https://imgur.com/a/qeaSJ

@t3p3tony said in DuetWIFI not detecting DueX5:

Not definitively but its more likely to be the Duex5. If it still does not work with the new ribbon cable then please contact Filastruder to swap the Duex5 under warranty.

Thank you for your input, I'll post back here this coming week with any updates.

@t3p3tony said in DuetWIFI not detecting DueX5:

Check the ribbon cable for continuity, and that there is a good ground between the Duex and the Duet on VIN.

I had 18 gauge wiring on the VIN and all checked out just fine but for sanity's sake i redid the VIN wiring with 16 gauge wire and everything there is definitely good to go with good connections to the terminals. After this I powered on to see if It fixed the issue but that wasn't the cause of the problem because the DuetWIFI still couldn't see the DueX5.

The ribbon cable looked good from what I could tell but its hard to judge a ribbon cable based on looks. I could have set up a probe to test each of the 50 connections for continuity but on removing the cable from the boards I broke the top plastic retainer on one side with my pliers. Its now in the trash bin next to my desk.

I went on ebay and found a 4" long, 50 pin, female/female IDE cable for around 7usd so I bought it and we can try again with a new cable this week when it arrives.

Not to jump too far ahead with this, but: What would be the next course of action if, when this new cable arrives, the DuetWIFI still cannot see the DueX5? Is there a way to tell which board is responsible for the non-detection?

I currently have a printer build in progress that is going to be using my existing (1 year old) DuetWIFI and a new DueX5 that i got from filastruder. Today I started some commissioning of the printer and got stuck right away when the DuetWIFI wouldnt detect the X5 right from the beginning.

I checked and rechecked my VIN wiring and made sure it was correct and I re-seated the 50 pin ribbon cable a couple different times to make sure it was in there. I then updated the firmware from 1.21RC3 to the actual 1.21 release and gave it another try - there it was! I saw the DuetWIFI mention the X5 in the M115 command.

...I restarted the DuetWIFI - the X5 disappeared from the M115 command

I restarted again - still gone

I've now wasted about 3 hours trying to get the X5 recognized again with no results.

Could anyone offer any help?
Thank you.

@burtoogle:

Hi, tbahre, looking at the Cura code, it appears to only report the filament used by extruder 1 and so I'm guessing you have a dual extruder machine and have sliced for extruder 2 only. Is that true?

Yes this is right as I’m using a e3d chimera. I’ve told cura to use extruder 2 (tool 1) since that’s the extruder I’m using right now (physically it’s the right hand nozzle).

Extruder 1 (tool 0, left hand nozzle) is empty and I’m not printing with it right now.

@burtoogle:

Thanks for the file. Yes, there's a problem in there as it reports the filament used at the top of the file as zero. I don't know why that is right now but will investigate. I am using a later version of Cura and the filament used is correct so perhaps there was a bug and it has been fixed?

Interesting! I see that now as well and checked my other files generated by cura and the same 0m value is there for filament. Is there a later version than cura 3.2.1? When I look on their website it says 3.2.1 dated February 18 is the latest.

Having layer and estimation problems myself. I posted thinking it was a problem with Cura but I'm not so sure:
https://www.duet3d.com/forum/thread.php?pid=40787#p40787
Also: https://www.duet3d.com/forum/thread.php?pid=40843#p40843