Firmware 1.20 released
-
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.
-
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.
ummm not a clue.. just hit the home Z.. there shouldn't be any reason you can't home Z pretty much any time you want… at least none I can think of.
-
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.
ummm not a clue.. just hit the home Z.. there shouldn't be any reason you can't home Z pretty much any time you want… at least none I can think of.
Just edited my post - read it again.
-
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.
ummm not a clue.. just hit the home Z.. there shouldn't be any reason you can't home Z pretty much any time you want… at least none I can think of.
Odd. Perhaps it depends on what type of Z homing switch you have configured. I use the nozzle to probe the bed so my Z homing files move the head to the centre of the bed. Maybe that;s why DWC won't let me home Z without first having homed X and Y.
Anyway, it's you M84 commands that are resetting all the homing status (including Z because it cuts power to all motors). So take them out.
-
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.
Good catch! He doesn't have M84 at the end of homez.g, which is why Z is remaining homed.
The motor currents are reduced to the idle value after 30 seconds of printer inactivity. By default this is 30% of normal, which on most non-delta printers is sufficient to hold position. Whereas M84 cuts the current completely, so the motors are flagged as not homed because it is quite likely that they will not be in the same position when you apply power again.
-
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.
ummm not a clue.. just hit the home Z.. there shouldn't be any reason you can't home Z pretty much any time you want… at least none I can think of.
Odd. Perhaps it depends on what type of Z homing switch you have configured. I use the nozzle to probe the bed so my Z homing files move the head to the centre of the bed. Maybe that;s why DWC won't let me home Z without first having homed X and Y.
Anyway, it's you M84 commands that are resetting all the homing status (including Z because it cuts power to all motors). So take them out.
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.
Good catch! He doesn't have M84 at the end of homez.g, which is why Z is remaining homed.
The motor currents are reduced to the idle value after 30 seconds of printer inactivity. By default this is 30% of normal, which on most non-delta printers is sufficient to hold position. Whereas M84 cuts the current completely, so the motors are flagged as not homed because it is quite likely that they will not be in the same position when you apply power again.
Sweet!! man you guys are awesome!!! I'll check it out in a bit!! Thanks.
-
That worked!!!!!! thanks a bunch again guys!!!
(printing up a few more mounts/parts today on the old i3 clone, hoping tomorrow to be doing test cube prints on this Core XY at the latest ) -
I'm not sure wich number you're after so I copied the entire response:
…
17:34:17.154 : Last reset 00:07:46 ago, cause: power up
17:34:17.154 : Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 8620 bytes (slot 2)
17:34:17.154 : Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
17:34:17.155 : Stack: 000bfb1f 01c8a8c0 fffffff9 00ffffff 20087ebc 20070fe8 01c8a8c0 20087ebc 000a6221 000a6220 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 0000012c 2007aea8 75207369 01c8a8c0 2007376c 000a5b1d 2001376c
...Thanks, that should help me to track the problem down.
I have taken a look at your stack trace, but unfortunately you appear to be using an older build of 1.20.1RC for the Duet 06/085 than the one I have symbols for.
Please can you try the version of RepRapFirmware.bin at https://www.dropbox.com/s/ozuw60nflckpq6c/RepRapFirmware.bin?dl=0. Assuming it keeps restarting in the same way when the Ethernet cable is connected, after letting it do that a couple of times please remove the Ethernet cable, then send M122 via USB and post the output from it here. Also please post your config.g file.
PS - I think the problem may be occurring in the DHCP code. If you are setting the IP address in M552 to zero in order to use DHCP, please try setting a static IP address and see if that resolves the problem.
-
hey, likely nothing but, was just studying and trying to figure out a few things in the firmware, so I just copy pasted into a test editor. just noticed this 1st line in the Config file-
Configuration file for Duet WiFi (firmware version 1.17)
shouldn't that be 1.2X now that I've upgraded? or is that just the "base" and the versions are built on top of it? -
I have taken a look at your stack trace, but unfortunately you appear to be using an older build of 1.20.1RC for the Duet 06/085 than the one I have symbols for.
Please can you try the version of RepRapFirmware.bin at https://www.dropbox.com/s/ozuw60nflckpq … e.bin?dl=0. Assuming it keeps restarting in the same way when the Ethernet cable is connected, after letting it do that a couple of times please remove the Ethernet cable, then send M122 via USB and post the output from it here. Also please post your config.g file.
PS - I think the problem may be occurring in the DHCP code. If you are setting the IP address in M52 to zero in order to use DHCP, please try setting a static IP address and see if that resolves the problem.
I'll get to this later today. In the mean time, I have another peculiarity turning up on my PanelDue console on my other printer when I start it up. A customized TronXY X5S core XY. It says:
[c]
ts Connected
ts Error: M304: Invalid bed heater index '649'
ts HTTP is enabled on port 80 FTP is
enabled on port 21 TEL
ts Wifi module is connected to access point
<name>, IP address 192.168.200.72
[/c]I've gone through my config.g where M304 appears and config-override.g
relevant snippet from config.g
[[language]] ; Heaters M304 H0 P649.2 I2.550 D1569.0 ; Use PID on bed heater using these process parameters ; M301 H1 P11.6 I0.124 D41.4 ; Use PID on hotend using these process parameters M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0 M143 H0 S120 ; Set temperature limit for heater 0 to 120C M305 P1 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1 M143 H1 S270 ; Set temperature limit for heater 1 to 270C ```config-override.g:[[language]]
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
M301 H0 P649.2 I2.550 D1569.0
M307 H1 A266.1 C89.1 D4.1 S1.00 V0.0 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0This appears wether or not I include the "H0" parameter in the command. Bug, or me getting it wrong? "ts" and "<name>" are placeholders for time stamp and SSID for the WIFI.</name></name> -
M304 is for the bed heater and defaults to using heater 0. Do you get the same thing if you use M301 H0 Pnnn Innn Dnnn?
