Erroneous Emergency Stop, and very slow bed compensation travel

gsport

Thanks for the help with this.

Sorted the slow travel, thanks.

Bit confused by the firmware upgrade process.
I only bought this board about two months ago, so to find that the firmware is "quite old" and the upgrade process either incredibly complex or incredibly confusingly documented is pretty annoying.

The link you gave leads me to think that my best option is to go with 1.19.2, this link has a section on that, but then says if upgrading from 1.18.2 or earlier (which I obviously am) see notes for upgrading to 1.19.0… then under that section it sends me to another webpage for more important notes on getting to 1.19.0 (presumably).

This is very confusing and daunting.

Do I need to fully upgrade to 1.19.0 following these earlier instructions and then do all the instructions for 1.19.2

And would asking for a link to the firmwares in question be asking too much? Is there a clearer set of instructions somewhere maybe?

George

dc42

You can upgrade directly to 1.19.2 using the same procedure as for upgrading to 1.19. The upgrade from 1.18 series to 1.19 series firmware on the Duet WiFi is unfortunately complicated, it's usually much simpler.

See "Where to get Duet firmware and tools" on the wiki for the links, and "Updating main firmware" for the instructions.

gsport

Unfortunately ~~this is proving~~ proved to be a pain in the neck.

Took SD card out of board (while off)
Pasted new files from 1.19.2 firmware into position as outlined here https://duet3d.com/wiki/Upgrading_to_DuetWiFiFirmware_1.19 for 1.19.
Moved SD card back and followed instructions there to install new firmwares.

Obviously at this point I then had no way of knowing what was going on in terms of rebooting so left it 15 minutes then turned off, connected by USB and turned on again then fired up Pronterface.

Tried to follow next step of sending the command "M98 P/macros/SetNetwork" but I think I hit the Pronterface auto capitalisation problem as it then told me it couldnt find that macro file…
Also tried going in using YAT but I cant install YAT as there is a hang on the net framework installation that it wants installed..

Finally found another thread where reference was made to editing marco files using notepad++ so wondered if the format of windows generated text files was off so redid them using that and bingo..

Pretty annoyed by this whole process and the quality of the instructions to be honest. If boards sent out within the last 2 months are multiple firmwares out of date, then clearer update instructions that dont require burrowing down through multiple webpages would be nice...

Will keep you updated on whether the original issue returns

gsport

So now I cant run auto bed compensation (just probing the four corners to check for level) because it comes up with:-

JavaScript Error

A JavaScript error has occurred so the web interface has closed the connection to your board…. please contact the author..

Message: Uncaught TypeError: Cannot read properly 'getExtension' of null
URL: http://192.168.0.41/js/dwc.js
Line: 12:71278
Error object: {}

Help please!

dc42

Is this problem reproducible?

Please report your main firmware version and DWC version, as displayed on the Settings->General page.

gsport

I cant get anything except the error so yes its reproducible

It probes the corners OK but then instead of popping up the window with the results it gives the above error.

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19.2 (2017-09-01)
WiFi Server Version: 1.19.2
Web Interface Version: 1.19

dc42

Please upgrade to DWC 1.19.3 available here https://github.com/dc42/RepRapFirmware/blob/dev/Release/Duet-WiFi/Edge/DuetWebControl-1.19.3.zip (follow the link, then press Download) and see if the problem still occurs.

gsport

So I updated that by changing the existing www folder to wwwold and creating a new www folder with these files in.

Now when the auto bed compensation runs, the pop-up window does appear and no java error message, but the display itself is a messed up large black cross of background and no image or data displayed, pressing "top view" button or using any mouse controls have no effect. "Close" works though.

Possibly related, when I put the SD card in the PC's card reader to put these files onto it, the PC came up with "there's a problem with this drive" and wanted to scan and fix it.

George

dc42

If your PC thinks there is a problem with the SD card, I suggest you let it fix the card. Better still, copy the files off it, reformat the card, and copy the files back on.

gsport

Fixing errors it didn't find any. Reformatted card still doing it!

Reinstalled Java which seems to have sorted it.