I now have my duet installed and running after the firmware re-load. I still have to tweak a couple of settings and reconnect the power off feature, but other than that all is good.
Thank you all for all of your help and suggestions.
Posts made by snake2155
-
RE: Help Unable To Connect in Any Way
-
RE: Help Unable To Connect in Any Way
I erased and reloaded the firmware to v2.03 using Bossa. The weird part is that it would not show up until after the erase. After loading firmware I was able to connect via wireless and did not have to reconfigure. Tomorrow I will reinstall the board and check function and if all is well I will change status as solved.
Could someone explain to me why tthe firmware needed to be reloaded and why I did not have to reconfigure my wifi settings.
Thanks.
-
RE: Help Unable To Connect in Any Way
Hello
All connections are currently disconnected from my Duet, so no chance of that.
Thanks -
Help Unable To Connect in Any Way
Hello
I have a Duet Wifi v1.04b that I purchased 5 months ago in preperation to a new printer build. I am using this along with a PanelDue 5. One week ago I connected to it via the usb port and configured the wifi with no issues and everything worked great. On calibration print #4 I noticed the paneldue read 0 degrees celcius for both the hot end and bed. I was not overly concerned with this as I was controlling the printer via wifi. On print # 5 the printer shut down in mid print. I had lost my 3.3v output between pin3 and ps on that controls my mains SSR. I then wired my power supply directly to the Duet and powered thing up. I am unable to connect via wifi, control actions via PanelDue, or connect by USB.
I then removed all connections and attempted to connect by USB with no luck using YAT, and device manager does not see the Duet ( as duet, bossa or unknown device ). Currently I have the following leds 5v - red, 3.3v - green, usb - red, and diag - red.
I purchased this unit from Filastruder and was informed that I need an Administrators approval for a warranty return. I am hoping that I am overlooking some corrective action, but I tried everything in the troubleshooting guide except erasing the firmware. I do not feel comfortable doing that without an Administrators instruction to do so.Any ideas?