Firmware 1.20 released
-
I have it on my list to investigate your report before the 1.20.1 release, however I need to get the prototype laser filament sensors completed and shipped first to avoid additional delay to production of filament sensors.
-
Just tried to upgrade from 1.19 to 1.20. I've uploaded DuetWifiFirmware.bin, but I cannot connect anymore to the printer via wireless. Any idea?
-
Adding some bits. I also tried connecting through USB but the serial device is not recognized by my linux machine (before upgrading used to work).
EDIT: i have tried the fallback procedure #2 described at https://duet3d.com/wiki/Updating_main_firmware but it still doesn't work. -
The USB interface code did not change between 1.19 and 1.20, so I don't understand why you can't access the Duet over USB any more. Do you have any evidence that the firmware update succeeded in other ways, e.g. because an attached PanelDue is working?
-
I don't own a PanelDue. I don't know how to debug this.
-
So as far as you know, the board isn't running at all. See https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond.
-
I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware
-
I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware
Works for me. Maybe it got fixed between your post and mine?
-
Works for me. Maybe it got fixed between your post and mine?
Weird…I still get a 404 when I try the link.
-
I just tried it again (using the link in deckingman's post above) and it works for me.
-
it also works for me with no issues (From the OP's original link)
-
do i have to redo my config file after the update?
-
do i have to redo my config file after the update?
Read the upgrade notes to see whether you need to make any changes.
-
Both of my Duets stopped printing any G-code file with brackets in it's name after 1.20 update. The files upload fine,it's just that the subsequent M32 command fails with "Gcode file not found". Same files worked fine in 1.19 and before, so it's probably something that was changed with 1.20.
Edit: Rechecked, it's definitely the firmware - already uploaded file prints on 1.19.2, gives error with 1.20 or later. Web interface version had no effect on the outcome.
-
It's because standard GCode uses brackets to enclose comments, therefore anything enclosed in brackets is stripped out. Workaround is to use double quotes around the filename in the GCode command. The beta PanelDue firmware already does this, and DWC will do so soon.
-
so, upgraded to 1.2 with help from here (thanks a bunch! :). ) everything seemed fine, but now getting an "error G28 failed to home" with X and Y end stops. Z seems to work fine. thing is it visually/mechanically seems to be homing fine. Setup on a CoreXY. here is a video if it helps figure what I'm doing wrong. what settings and such should I be looking at/for? Supposedly it was a beta version of the firmware issue and was fixed? but I never used a beta version.. just upgraded from 1.18 to 1.2
-
Is is definitely moving as far as the X and Y homing switches when you try to home all, or when you try to home just X or just Y? The movement in your video looks very short.
Please share your config.g and homing files.
-
I haven't tried to home all as the Y end stop isn't mounted yet so I trip it by hand myself. reason I didn't show it.
I saw the write up on the "home all" for CoreXY which is easy enough .. Short movements was just because I didn't want to waste peoples time watching it slide across, so I was just starting them rather close. - Config -g -[c]; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Oct 16 2017 05:23:05 GMT-0400 (EDT); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X350 Y350 Z350 S0 ; Set axis maxima
M667 S1 ; switch to CoreXY mode
; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches; Drives
M569 P0 S1 ; Drive 0 goes backwards (X axis)
M569 P1 S0 ; Drive 1 goes forwards (Y Axis)
M569 P2 S0 ; Drive 2 goes forwards (Z Axis)
M569 P3 S0 ; Drive 3 goes forwards (Extruder)
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z400 E97 ; Set steps per mm
M566 X700 Y700 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z400 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X900 Y900 Z900 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M143 S245 ; Set maximum heater temperature to 245C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M307 H1 A737.5 C231 D5.5 B0
M307 H0 A166.3 C515.3 D2.5 B0; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Network
M550 PLlama CoreXY ; Set machine name
M552 S1 ; Enable network
M587 SXXXX P######## ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off; custom tune Duet CPU temp
M912 P0 S-5.7; Custom settings are not configured[/c]
-
home X, Y and Z
[c]
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Mon Oct 16 2017 05:23:05 GMT-0400 (EDT); Lift Z relative to current position
G91
G1 Z5 F6000
G90; Move quickly to X axis endstop and stop there (first pass)
G1 X-400 F1800 S1; Go back a few mm
G91
G1 X5 F6000
G90; Move slowly to X axis endstop once more (second pass)
G1 X-235 F360 S1
M84–-------------------------------------------
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Mon Oct 16 2017 05:23:05 GMT-0400 (EDT); Lift Z relative to current position
G91
G1 Z5 F6000
G90; Move quickly to Y axis endstop and stop there (first pass)
G1 Y-400 F1800 S1; Go back a few mm
G91
G1 Y5 F6000
G90; Move slowly to X axis endstop once more (second pass)
G1 Y-215 F360 S1
M84
; homez.g
; called to home the Z axis
;
G91 ; relative mode
G1 Z4 F200 ; raise head 4mm to ensure it is above the switch trigger height
G90 ; back to absolute mode
G91 ; relative mode
G1 Z-400 S1 F250 ; move Z down until the switch triggers
G1 Z4 F200 ; raise head 4mm to ensure it is above the switch trigger height
G1 Z-200 S1 F50 ; move Z down until the switch triggers
G90 ; back to absolute mode
G92 Z0.15 ; tell the firmware that we are at Z=0.15mm
[/c] -
Something very strange going on here. How did you get the situation where Z was homed but X and Y were not? The reason I ask is that you can't home Z unless X and Y have already been homed. At least that's how it is and how it has always been on my CoreXY.
Edit. I think I know why. You have M84 at the end of all you homing files. This cuts the power to the motors and resets the state to be not homed (because without idle hold, they could easily be moved). Take out those M84 commands.
