Unable to upgrade Duet 0.85 to 1.21RC3 from 1.19.2 using RepRapFirmware.bin. I tried utilizing DWC firmware update method first, and it appeared to transfer successfully and reboot, but it failed come back up. I tried erasing and utilizing the Bossac method. The new firmware transfers successfully via Bossac, but causes the Duet to reboot itself after 30 seconds or so repeatedly. (I can tell because the USB drops and reconnects about every 30 seconds.) Erased and Reflashed the firmware using Bossac back to 1.19.2 and the Duet is operating normally again.

Try deleting and re-typing the M906 line in config.g in case there is a hidden character in it.

I tried this several times with no change to the issue.

Are there any M906 or M584 commands in your homing files or in bed.g

No other M906 commands found in any config file.

When using 1.19.2, if you send M906 X1000 Y1000 Z1000 E1000 from the command console, are the motor currents OK after that?

This did set the proper current settings for the extruders and a M906 reported X:1000 Y:1000 Z:1000 E:1000:1000:1000:1000:1000:1000

2. Does it make any difference if you put the I60 parameter on the first M906 line instead of on a separate M906 line?

This made the difference. Once I placed the I60 command on the same line as the first M906 line, the E parameter was read and configured correctly.

So now I am working great on Firmware version 1.19.2 and my new config.g M906 line looks like this:
[c]M906 X1000 Y1000 Z1000 E1000 I60[/c]

Thank you for your help!

Updating my 0.85 Duet from 1.17.?? to 1.19.2, I can no longer run my extruder motors (3 of them).
Extruders were running great before the firmware update.
Config.g statement is M906 X1000 Y1000 Z1000 E1000.
Executing an M906 shows X:1000 Y:1000 Z:1000 E:0:0:0:0:0:0 from DWC.
Revert back to 1.17a and the extruders work again.
Executing an M906 after reverting back to 1.17 shows X:1000 Y:1000 Z:1000 E:1000:1000:1000:1000:1000:1000

Before reverting back to the previous firmware, I tried modifying my config.g file to M906 X800 Y800 Z800 E1000:1000:1000:1000:1000:1000, but running M906 from DWC only showed X:800 Y:800 Z:800 E0:0:0:0:0:0.

I have no idea why my extruder current settings would not configure correctly with the M906 command under v1.19.2.

Here is a copy of my Config.g File:
[c]; Configuration file for Rostock with Diamond from Perrydice

; Communication and general
M111 S0 ; Debug off
M550 PPerrydice_Delta ; Machine name and Netbios name (can be anything you like)
M551 P************ ; Machine password (used for FTP)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
;*** Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P0.0.0.0 ; IP address (0 = use DHCP)
M554 P192.168.1.1 ; Gateway
M553 P255.255.255.0 ; Netmask
M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Comms parameters for PanelDue

G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves

;Fans
;M106 I1 ;Invert fans
M106 P0 S0 ;Turn off Fan 0
M106 P1 S0 ;Turn off Fan 1

; Axis and motor configuration
M569 P0 S0 ; Drive 0 goes backward
M569 P1 S1 ; Drive 1 goes forward
M569 P2 S0 ; Drive 2 goes backward
M569 P3 S0 ; EDrive 0 goes backward
M569 P4 S0 ; EDrive 1 goes backward
M569 P5 S1 ; EDrive 2 goes forward
M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
M665 R140.93 L269 B130 H396 ; set delta radius, diagonal rod length, printable radius and homed height
M666 X-0.02 Y-0.02 Z0.04 ; put your endstop adjustments here, or let auto calibration find them
M92 X80 Y80 Z80 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E1000 ; Set motor currents (mA)
M906 I60 : Set motor Idle current
M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
M566 X1300 Y1300 Z1300 E1300 ; Maximum instant speed changes mm/minute
M207 S5.0 F2400 ; 5mm retraction at 2400mm.min (40mm/sec) for the all three extruders to prevent the Diamond Head ooze!

;PID Settings
;For manual adjustments: if it overshoots a lot and oscillates, either the integral gain needs to be increased or all gains should be reduced.
;Too much overshoot? Increase D, decrease P.
;Response too damped? Increase P. Ramps up quickly to a value below target temperature (0-160 fast)
;and then slows down as it approaches target (160-170 slow, 170-180 really slow, etc)
;temperature? Try increasing the I constant.
;M301 H0 P-24 I0.80 D105 T0.50 S1.0 ; PID settings for Print Bed (-P means bang bang setting and not PID)
;M301 H1 P08 I0.20 D109 T0.50 S1.0 ; PID settings for Heater 1 (Diamond Hot)
M307 H0 A70.0 C590.1 D12.5 B1 ; Set Heated Bed temperature control
M307 H1 A243.8 C195.4 D4.5 S1.00 B0 ; Set Hotend temperature control

; Thermistors
;*** If you have a Duet board stickered "4.7K", change R1000 to R4700 to the following M305 commands
M305 P0 T100000 B4286 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4375 R4700 H30 L0 ; Put your own H and/or L values here to set the 1st nozzle thermistor ADC correction
M570 S280 ; Hot end may be a little slow to heat up so allow it 280 seconds

; Tool definitions
M92 E146.27:146.27:146.27 ; Set steps/mm for extruders

M563 P0 D0:1:2 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M567 P0 E1.0:0.0:0.0 ; Set mixing to extruder 1 at 100%
M568 P0 S1 ; Turn on mixing S= (1 = on, 0=off)

M563 P1 D0:1:2 H1 ; Define tool 1
G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M567 P1 E0.0:1.0:0.0 ; Set mixing to extruder 2 at 100%
M568 P1 S1 ; Turn on mixing S= (1 = on, 0=off)

M563 P2 D0:1:2 H1 ; Define tool 2
G10 P2 S0 R0 ; Set tool 2 operating and standby temperatures
M567 P2 E0.0:0.0:1.0 ; Set mixing to extruder 3 at 100%
M568 P2 S1 ; Turn on mixing S= (1 = on, 0=off)

; Z probe and compensation definition
M558 P4 X0 Y0 Z0 H3 ; Z probe is a switch and is not used for homing any axes
G31 X0 Y0 Z-.05 P500 ; Set the zprobe height and threshold (put your own values here)
;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
M208 S1 Z-0.2 ; set minimum Z
M557 R150 S25 ; Probe Grid setup

;Select tool and begin
T0 ; select first hot end
[/c]

I use Slic3r because it's easy to setup for my Rostock Max 2/Duet .8.5 with Diamond print head for multi extrusion, and does a great job of slicing my prints. And it's free! I tried Cura, but it was a little too complicated for me to set up, and there didn't seem to be much support for my type of machine.

@Jackal:

@goldentuna:

where is this interface.js file - how do I find it .. that needs to be edited?

https://github.com/chrishamm/DuetWebControl
Download the project, edit the file then build with the build.sh script and upload to your DuetWifi.

Thanks Jackal! I only have the Duet .85, so I wasn't sure how to update that file for the Duet WIFI.

I use this cheap network camera ($20.00)

https://www.amazon.com/ELP-Megapixel-Camera-Hidden-Network/dp/B00KA4M4WS/ref=sr_1_23?s=electronics&ie=UTF8&qid=1486167105&sr=1-23&keywords=ip+camera

And created the info in this post to make it work great in Duet Web Control.

https://duet3d.com/forum/thread.php?id=815#p7924

I had an issue where my TOP 201 Network Webcam utilized the following URI to display a "snapshot" of what it was looking at:
"http://ipofcamera/webcapture.jpg?command=snap&channel=0"
But the image would not display when setting a "Webcam Update Interval" of anything greater than "0". I found that the TOP 201 does not like adding an additional "&" sign to the URI, which is what the interface.js script was doing.
I modified the following code in interface.js from:

[[language]]
var newURL = settings.webcamURL;
		if (newURL.indexOf("?") == -1) {
			newURL += "?dummy=" + Math.random();
		} else {
			newURL += "&dummy=" + Math.random();
		}
		$("#img_webcam").attr("src", newURL);

```to:

[[language]]
var newURL = settings.webcamURL;
if (newURL.indexOf("?") != -1) {
newURL += "?dummy=" + Math.random();
} else {
newURL += "&dummy=" + Math.random();
}
$("#img_webcam").attr("src", newURL);

The change is in the if statement replacing the "==" to a "!=".

Hope this helps someone else with this issue.

The problem with webcam images is that the target URI has to be different every time a new photo is requested. I saw the other day that JQuery does it a bit different and that they use &= <random>instead of &dummy=<random>. Are you able to open http://localip/webcapture.jpg?command=snap&channel=0&=346345234 or does it give you an empty image as well?

For MJPEG sources I'm planning to allowing a static image URL by setting the update interval to 0. This will be implemented in DWC 1.14a.</random></random>

Hi and thanks for responding so quickly. Anything that appends another "&" cause no image to be displayed. If another character is used such as a ";", the camera ignores it and displays the image.

Are you able to open http://localip/webcapture.jpg?command=snap&channel=0&_=346345234 or does it give you an empty image as well?

No image is displayed.

Thanks For the update! I updated to 1.17a and DWC 1.14-RC1. Everything tests ok regarding my printer, but the Webcam issue related to appending the "&" parameter to update the cached image is still causing no image to be displayed in DWC\Print Status. "ERR_EMPTY_RESPONSE".

http://localip/webcapture.jpg?command=snap&channel=0 Works in any browser and displays a static image.

http://localip/webcapture.jpg?command=snap&channel=0& Fails in any browser with "Failed to load resource: net::ERR_EMPTY_RESPONSE"

http://localip/webcapture.jpg?command=snap&channel=0&dummy=VARIOUS NUMBERS causes "Failed to load resource: net::ERR_EMPTY_RESPONSE" in DWC. Everything after "=0" is what DWC adds to the URL provided above to create a new URL and refresh the image.

If we could change the "&" parameter to just about anything else, it seems to work. But my webcam doesn't like the additional "&".
I have an ELP IP 1881 IP Camera if that helps at all. (I think it also goes by TOP201)

@lignumaqua:

It appears they use a "?$variable" to update the URL and prevent the caching. So far, this does look like it works in a separate browser tab. But anytime I add the additional "&" to the URL, it fails with net::ERR_EMPTY_RESPONSE and no image is displayed in the DWC or in a separate browser tab.

Interesting. Seems the camera treats the second ? as if it were another query separator. I think we'd have to test that solution with other cameras as they may reject it as a non-standard URL.

As a matter of interest, what does your camera do if you use a semi-colon ; instead of the ampersand? Both & and ; are, in theory, valid data separators

I tried many different characters (;:"?[{}]) after the working URL of "http://192.168.1.128/webcapture.jpg?command=snap&channel=0" and any character other than "&" is ignored and allows the image to populate. As soon as I add a "&", it fails with the "ERR_EMPTY_RESPONSE" in both DWC and in browser windows.