Duet Wifi upgrade to 1.19 failed and I cannot access my printer.
-
I was trying to upgrade my d300vs duetwifi to ver. 1.19 I followed all of the steps and got to the point in pronterface to set up my access point which gave me an ip address. Typing the IP address in the browser however fails to bring up the web interface. I do not know what to do at this point and do not want to screw up my chip anymore. Please help!
-
have you tried with prontface? other option, think remember there is a reset procedure, not sure
-
I suspect you have inconsistent WiFi server and main firmware versions. I suggest you upgrade to RRF 2.02 and WiFi server 1.22 or 1.23beta1. You will need to copy the new Duet2CombinedFirmware.bin file to /sys on the SD card and rename it DuetWiFiFirmware.bin. Also copy the latest iap4e.bin file to /sys, also the DuetWiFiServer.bin file. Send M997 from Pronterface to install the main firmware, then M997 S1 to install the WiFi firmware. With luck this will get the web interface working and you should immediately install the new DWC version.
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 -
This post is deleted! -
@dc42 so I found the files renamed duet2combinedfirmware.bin to DuetWiFiFirmware.bin copied in the other 2 files from that folder replacing the previous ones and now am receiving this error when sending the command:
M997
SENDING:M997
M997: Firmware binary "Duet2CombinedFirmware.bin" not found -
See fallback procedure #1
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
-
@phaedrux said in Duet Wifi upgrade to 1.19 failed and I cannot access my printer.:
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
thank you for the response but now I am receiving this error:
M997 S0
SENDING:M997 S0
[ERROR] Can't read from printer (disconnected?) (OS Error 6): Device not configured
[ERROR] Can't write to printer (disconnected?) (SerialException): write failed: [Errno 6] Device not configured -
Move on to Fallback #3
-
@phaedrux It says I need a windows or linux PC... Does that mean a Mac will not work?
-
If you read down further there is an alternative for Mac
-
@phaedrux thank you I will try this, just to check though, will this procedure erase the firmware for my specific printer? and if so how would I back that up?
-
If you mean the configuration files, I don't think it will wipe the SD card, but I think it's always a good idea to make a backup of the card before doing anything like this. Just put the card in your computer and copy the folders over.
-
@phaedrux so it says i need to do this: bossac --port=COMxx -b -U -e -w -v path\DuetWiFiFirmware.bin -R
Replace COMxx in the above by the COM port number (e.g. COM3) and replace path\DuetWiFiFirmware.bin to the path and name of the firmware file to install but as far as I know Macs doesn't use COM port numbers? Sorry I have no idea what I am doing and this is very frustrating and I appreciate you helping me out. -
If you got Bossa 1.8 you should be able to use the GUI application and won't need the command line,
If you use the interactive version, you must check boxes Erase all, Lock, and Boot from Flash before pressing Write.
The Duet should show up in the Serial Port drop down menu after clicking the refresh button in Bossa 1.8. What it's called exactly varies, but if it's the only thing you have plugged into USB there shouldn't be a lot of choices.
-
also when I open this 'Bosac' in terminal it just shows me this:
Last login: Thu Feb 7 22:47:56 on ttys000
Benjamins-MacBook-Pro:~ condensedcloud$ /Volumes/BOSSA/bossac ; exit;
bossac: you must specify at least one option
Try 'bossac -h' or 'bossac --help' for more information
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.[Process completed]
and then doesn't let me type anything -
It says interactive Boss doesn't work on high DPI screens and I get this error: BOSSA cannot be opened because of a problem. Check with the developer to make sure BOSSA works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X.
-
Yeah take a step back. You don't need to use the command line.
Get Bossa 1.8 from here: https://github.com/shumatech/BOSSA/releases/tag/1.8
Install it to the applications folder.
Run it. Security might complain, but open it anyway.
Connect the duet to your computer, follow the erase procedure.
Point Bossa 1.8 at the firmware file
Select the Duet in the serial port drop down.
Check the Erase all, lock, and boot from flash buttons,
Then click Write and wait. -
I'm using Bossa 1.8 on my Retina display Macbook Pro right now, so it should work. 1.9 does not work for me but 1.8 does.
-
@phaedrux well, I installed it. It opened up for a second but then when I went to click the port it closed itself and now whenever I try to open it, it just closes itself immediately without opening anything. Just pops up in the dock and disappears immediately. Tried reinstalling it and restarting my computer.
-
What version of OSX?
If you go into Settings > Security & Privacy to you see a warning at the bottom saying it was blocked from starting?
-
el capitan 10.11.6 it's an old AF macbook pro. no security blocks
-
Alright, that may be an issue.
Is there any way you can get a Windows PC to update from?
-
If you want to pursue the command line option this would help you find the port of the duet: https://learn.adafruit.com/welcome-to-circuitpython/advanced-serial-console-on-mac-and-linux
ls /dev/tty.* -
@phaedrux I do not have access to a windows computer, I also just tried Bossa on a different macbook running High Sierra 10.13.6 and had the same problem. Do I need to track down a windows computer? I might be able to figure something out over the course of the next week.
-
Bossac isn't allowing me to put it in the Bin folder for 1.19 and 1.18 says the file is damaged and I need to eject installer so this command line terminal situation also does not seem to be panning out
