Thanks, I'm glad the mystery was solved! Your report prompted me to review the heater setup code, whereupon I discovered bug involving named heaters. So it wasn't all wasted time!

Please calm down, both of you. serkanozgur reported in his original post that he had already tried 3 different USB cables and 3 different computers - which is much more thorough than I expect from first-time users. Calvin pointed out that some USB cables are for charging only, and also pointed out issues with certain PCs that might be relevant. You have both written good posts, and there is no need to attack each other. At least one of you doesn't have English has his/her native language, and allowances should be made for that.

I will moderate any further posts in this thread that are not strictly technical in content (or are apologies).

Please ask Ultibots for a replacement Duet under warranty. They have been in touch with us and we will approve it.

I had the same problem with the instructions. You have to do two things.

Create a directory (folder) called www at the top level on the flash card. This will be at the same level as the sys directory where all the other installer files go.

Unzip the file. This will probably create a folder called "DuetWebControl-1.19" . Copy the contents of that folder (not the folder) into your new /www folder.

The /www directory will then contain /www/css, /www/fonts, /www/js, and some gzip files.

I hope this helps, and the confusion is not your fault 🙂

Ha. So I changed nothing, rebooted the PC, erased and reset the Duet and ta-da, SAM-BA is running. Maybe it just needed 20 erases to work? Thanks again for the quick responses.

OKAY So I ended up adding the M400 and then for fun said screw it and got rid of all the M300. Works like a charm now! Also dialed back the additional retraction to 2mm. So at least the heater safety issue seems to be resolved

@MJAussie360:

…Instead, I got "Could not establish a connection to the Duet firmware! Please check your settings and try again"
I tried to go through Pronterface to check and it threw this error "WiFi module started Error: Failed to initialise WiFi module, code -10" Then it reverted to this error "Received opcode 0000013e length 0 data" constantly

For anyone else getting this error, it means that the version numbers of DuetWiFiFirmware and DuetWiFiServer are out of step. You can comment out the M552 S1 command in config.g to prevent the wifi module starting up. Then run M115 to check the version number of DuetWiFiFirmware. If that shows 1.19 then copy DuetWiFiServer-1.19.bin into /sys and rename it DuetWiFiServer.bin. Then you can run M997 S1 to install it.

It worked. It works.
Only confusing that there are several manuals for update firmware on the internet

Thank you for the assistance.

Thanks for the confirmation.

Please mark the thread as solved then.

I updated the .cproject file recently to change the name of the generated file to RepRapFirmware-RADDS for the RADDS build instead of just RepRapFirmware. It looks like you haven't picked up that change.

Eclipse often gives a heap of semantic errors, usually when you have just changed the active build configuration. They usually go away when you compile or re-index.

@chrishamm:

What board are you using and can you confirm that this bug is still present in David's new 1.19 release?

You can update the web interface by uploading the DWC zip file on the Settings page too. Recent DWC versions automatically unpack and upload the compressed files.

Thanks for the hint, I had no idea you can upload zip-file. But at any rate, I did solve it originally by being persistent and I had a backup plan of taking out sd card, but I do think the bug may need attention. And yes, I can confirm it's still present in 1.19, except for I didn't have enough patience to finally upload over ftp this time and fell back to uploading .zip file (thanks again). Though I did have uploads of various size, language.xml.gz is 62126, I had 60448 and 59576 uploads instead. My board is according to DWC "Duet WiFi 1.0". The rest of components are all "1.19". If there's more detailed information about the board available somewhere, let me know where to find it. It's relatively early board, I don't remember exact days, but not experimental or something.

I also tried turning debugging on (M111 S1), I suspected maybe some error accessing sd card or some such, but nothing was obviously wrong on the wire.

Let me know if I can be of more help diagnosing it.

I'm closing this thread now. Anyone still using a 1.19 beta or RC, please update to the 1.19 release and report any related issues in the thread about that release.

see my follow up, at the end of the firmware update the hot end comes on and everything over heats, just re upgraded to 1.19 and it did the same again but flicking the power switch and all is well again.

@dc42:

It probably means that you didn't send the M587 command to store the SSID and password details correctly. You can send M587 with no parameters to get a list of SSIDS that have been stored.

Instead of send the M587 command from a macro, you can also use a terminal emulator. Under Windows I use YAT, https://sourceforge.net/projects/y-a-terminal/. You can't use Pronterface, Repetier etc. because they will convert the lower case characters in your password to uppercase.

Thanks to all, it's back again.
Thank you for your patient.
It is necessary to use YAT

@DjDemonD:

Search the forum Im hosting sam-ba the link is in one of the other threads.

Thanks!

Sounds like he/she is trying to install the driver for the Duet on a Win 7 machine and the driver isn't working. Without the driver he/she can't connect through Ponterface to enable wifi.

Thanks everybody! I'm going to carefully read the link Dougal sent, and get that working.

How old is your Duet, and which country are you in?