firmware 3.0 and more

A Former User

paneldue and more
thanks, dc42 (are you the designer?)
the paneldue still not working. I have the same cable connected in their correct connectors when it stopped working. checked the voltage on the paneldue and it is there.
in the meantime I recreated the connection and foolishly downloaded firmware 3.0 (mine was 2.1 from two years ago). now the home all does not work! when I click home all it moves z down by 5.5 mm. other movements seem to work.

Phaedrux

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode

In RRF3 the paneldue must be enabled with M575 P1 B57600 S1 in config.g

Your homing files will also need an update to work with RRF3. Likely the difference between G1 S1 and G1 H1, or that you cannot move an axis before it's been homed causing an error.

Generating a new full config file set will give you an idea of what the new syntax looks like by comparison.

A Former User

@phaedrux
thanks. will try everything you suggested.

A Former User

@ooly
Phaedrux,
I have uploaded all updates as suggested. however, when trying to reconfigure my delta I am running on all kinds of problems.

homing all does not work because "failed to enable endstops". this in spite the fact I have "G1 H1 x....", in homedelta.g, which to my understanding activates the end switches.
in the RRF config tool, the endstops section is confusing to me and the problem, among others, revolves around the definition of X,Y,Z for delta printers. they can refer to the horizontal x and y together with height z; or they can be the height of the three towers. clearly these two interpretations are used in the configuration tools and in the settings. I had struggled with this problem two years ago when I built my delta, finally some how got it to work. now I forgot what I did and I am lost.

A Former User

@ooly
here is the homedelta.g:

G91 ; relative positioning
G1 H1 X235 Y235 Z235 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre

Phaedrux

Post your config.g as well please. I think something in your config.g isn't quite right.

Also the results of M122 and M98 P"config.g" sent in the gcode console.

You may also find these helpful.

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter
https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer

A Former User

@phaedrux
thanks for bearing with me.

I keep getting "failed to enable endstops" which means I cannot home anything and therefore I am locked out. is anything wrong with the homedelta.g above? how do I enable the endstops?

will post config.g later

A Former User

@ooly
here is my config.g

; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.1 on Sun Aug 29 2021 18:00:06 GMT+0300 (Eastern European Summer Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"oolys" ; set printer name
M665 R94.5 L215 B73 H216 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
; paneldue
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X800 Y800 Z800 E663.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z0 S1 ; set minimum Z

; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"null" ; configure active-high endstop for high end on Z via pin null

; Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z0.8 ; set Z probe trigger value, offset and trigger height
M557 R73 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; 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

M575 P1 B57600
M501
T0
; Custom settings are not defined

droftarts

@ooly said in firmware 3.0 and more:

M574 Z2 S1 P"null" ; configure active-high endstop for high end on Z via pin null

Where is the Z endstop plugged in? Most likely, change the above to
M574 Z2 S1 P"zstop"

Ian

A Former User

@droftarts
Ian, thanks.
I changed 574 as you suggested but I am still not there.

in a delta there are no endstops for the horizontal "x" and "y", only
z probe for the bottom, and of course three XYZ endstops for the three towers, all on the top side.
on the other end, in the delta config tool, there is a clear difference between x, y, to that of Z.
kindly explain. thanks.

droftarts

@ooly What is "still not there"?
You need an endstop on each of the three delta axes, X, Y and Z. These are not referring to 3-dimensional space (as they might in a Cartesian machine), it's referring to the three delta towers. X, Y and Z are just axis labels. So you need to have a 3 endstops defined with M574. Check endstops are assigned to the correct axis and working correctly by sending M119 while depressing each switch in turn.

The homedelta.g just homes these three axes at the maximum end. The M665 'H' parameter in config.g (or config_override.g) sets the homed height. The actual 'Z-probe' is used for the Delta auto calibration. See https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Setting_up_your_initial_delta_parameters

Ian

A Former User

@droftarts
I know and the three end switches are in place, but m119 brings back all at "max stop" when they are all midway.
my setting is m574 X2 S1 P"xstop" etc. tried x1 instead of x2 and it says x at "min stop"

droftarts

@ooly What does it say when you press the endstop and send M119? Most probably "not stopped". If so, it means you need to invert the logic of the endstop, as you have yours wired Normally Open, rather than Normally Closed.

Either change M574 to (note exclamation mark in pin definition):

M574 X2 S1 P"!xstop"                           ; configure active-high endstop for high end on X via pin !xstop
M574 Y2 S1 P"!ystop"                           ; configure active-high endstop for high end on Y via pin !ystop
M574 Z2 S1 P"!zstop"                           ; configure active-high endstop for high end on Z via pin !zstop

Or rewire your endstops to Normally Closed, which is preferred as they are less susceptible to interference. See https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Microswitch

Probably in your old RRF 2 config.g they were defined as M574 X2 Y2 Z2 S0, where S0 means they are inverted.

Ian

A Former User

ok, the ! did it. thanks
another problem: the status display is totally different from my old one in the 2.1 version. in the old one I could change the values of z. in this one I cannot so z is stuck at the top home value so I can't move it. is there a way to change z value in the status window? or alternatively return to the old window?

A Former User

@ooly
another problem: while commanding movements in the dashboard, speed is not constrained by the "max speed" setting in config.g.
how do I limit these movements? thanks

fcwilt

@ooly said in firmware 3.0 and more:

@ooly
another problem: while commanding movements in the dashboard, speed is not constrained by the "max speed" setting in config.g.
how do I limit these movements? thanks

With firmware 3.3 the M203 settings control the max speed of those movements.

Frederick

droftarts

@ooly said in firmware 3.0 and more:

another problem: the status display is totally different from my old one in the 2.1 version. in the old one I could change the values of z. in this one I cannot so z is stuck at the top home value so I can't move it. is there a way to change z value in the status window? or alternatively return to the old window?

If you mean change the jog amounts, right click on the number you want to change. See https://duet3d.dozuki.com/Wiki/Duet_Web_Control_v2_and_v3_(DWC)_Manual#Section_Adjusting_movement_amounts

another problem: while commanding movements in the dashboard, speed is not constrained by the "max speed" setting in config.g.
how do I limit these movements? thanks

I very much doubt that. You have your M203 set as:
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
18000 mm/min = 300mm/s. Are you saying it goes faster than that?!

Ian

droftarts

@ooly said in firmware 3.0 and more:

another problem: the status display is totally different from my old one in the 2.1 version. in the old one I could change the values of z. in this one I cannot so z is stuck at the top home value so I can't move it. is there a way to change z value in the status window? or alternatively return to the old window?

Ah, just worked out what you mean. In DWC v1 you could click on the X, Y or Z position and enter a new value for the axis to move to. I think this was removed as it was too easy to upset a print by accidentally clicking on it. You need to use the jog buttons, or send the gcode (ie G1 Z50) to move the nozzle to a specific location.

If you've upgraded to RRF 3.3, I don't think DWC 1 will work any more as the communication protocols have changed.

Ian

Phaedrux

@ooly said in firmware 3.0 and more:

@ooly
another problem: while commanding movements in the dashboard, speed is not constrained by the "max speed" setting in config.g.
how do I limit these movements? thanks

If you're talking about the displayed max speed while homing being higher than you'd expect that's a display anomaly due to the way delta kinematics speed is calculated.