2nd Z Endstop Missing in RRF Config Tool

PuterPro

I've been working hard to grasp e/t I need to make my CR-10S conversion work the 1st time I power up.

I know I'm dreaming, LOL!

I have a BLTouch coming now so I can do independant Z and map the bed. I'm pretty sure I've got a handle on the basics now, but I ran into an oddity when using the RRF Cong Tool that threw me.

I mapped my motors for Zb to be on E1, but when I went to Endstops, I only find X, Y, & Z with no place to put an endstop for a 2nd Z .

Do I have to define it manually in the config.g file after the RRF tool is done? No problem, I think I can do that, modifying M574 but ...

Am I missing something here?

Also - The resulting config.g doesn't' have a definition for the U Axis. I thought it would configure the 2nd Z as an independent axis. Do I have to assign U axis manually via M584?

I assume like this: M584 X0 Y1 Z2:4 U

In https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

It gives this for that scenario: M584 X0 Y1 Z2:4 ; two Z motors connected to driver outputs Z and E1

Do we not assign the U Axis? If not how do I reference an Endstop for it ...??

OK, I apologize for being dense but what I think I know doesn't jib with the RRF Tool's output.

Here's the current config.g:

; Configuration file for Duet Maestro (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Feb 11 2019 16:00:58 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 P"CR-10S Duet" ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards for Geared Extruder
M569 P4 S1 ; Drive 4 goes forwards
M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E410.00:400.00 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:12.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z600.00 E1200.00:600.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y250.00 Z16.60 E166.00:16.60 ; Set accelerations (mm/s^2)
M906 X700.00 Y700.00 Z700.00 E700.00:700.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z320 S0 ; Set axis maxima

; Endstops
M574 Z1 S0 ; Set active low and disabled endstops
M574 X1 Y1 S1 ; Set active high endstops

; Z-Probe
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:195 Y15:195 S20 ; Define mesh grid

; Heaters
M305 P0 T100000 B4388 C7.060000e-8 R2200 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4388 C7.060000e-8 R2200 ; Set thermistor + ADC parameters for heater 1
M143 H1 S305 ; Set temperature limit for heater 1 to 305C

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; 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

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings
G29 S1 ; Enable automatic bed mesh compensation
M572 D0 S0.10 ; Enable pressure-advance of 0.10 seconds

; Miscellaneous
M501 ; Load saved parameters from non-volatile memory

aidar

@puterpro said in 2nd Z Endstop Missing in RRF Config Tool:

In https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors
It gives this for that scenario: M584 X0 Y1 Z2:4 ; two Z motors connected to driver outputs Z and E1
Do we not assign the U Axis? If not how do I reference an Endstop for it ...??

If you use probe, then you dont need U axis and endstops. Probe will be your endstop.

PuterPro

@aidar Ah-HA! Like the CR-10 Pro!

Cool and so bloody obvious! (As are most problems in the rear view mirror ...!)

Thanks SO much! I'd put off in-depth reading on the probe and Mesh leveling since I didn't have one, got some reading to do. My probe just arrived.

Now to get the power sorted out ... LOL

PuterPro

So after pondering this I still have Q's -

If the BLTouch is chosen, why does the RRF Config tool also configure endstops.
Not so sure I'd want to reply on a BLTouch for all Z homing what if it fails or the pin sticks etc. I I have MUCH more faith in Microswitches, they're a simple, proven, pretty much bullet proof tech.
Can the switches be configured as a "backup" to the probe, say adjusted out of the way of normal operation but trigger in a runaway axis situation (probe fails)? Kind of emergency stop sorta thing.
Never did get an answer to the defining the U axis question.

Phaedrux

1a. The configurator isn't perfect. It's basically just a working starting point. For most situations it does just fine provided the right things are checked in the right way, but it can be easy to tell it to do something you don't actually want. Manual editing of the config.g file to fine tune things and implement more advanced configurations will be needed.

1b. The BLTouch is quite reliable. Once it's configured and working it's a very simple mechanism in and of itself. Not much to fail.

Yes you can have a microswitch wired up and used as a backup emergency stop if you want. You can set it to function as an estop, since it technically isn't going to be functioning as an endstop at that point, which is really just active during a homing move (G1 S1). As a general trigger though it can be active at any time, and you can wire multiple switches together to trigger all of the axis if you wish. https://duet3d.dozuki.com/Wiki/Connecting_an_Emergency_Stop

However, the firmware is quite good at obeying the axis limits if they are set correctly. A safer and simpler approach the protect against the failure of a probe or switch during a homing move (which is really the only time when you're actively trying to go towards an axis limit) is to adjust the motor current down during a homing move so that even if the probe or endstop fails, the motor won't have enough force to damage anything. You can use a M915 command in the homing files to scale the current to a percentage before the move, and then return to normal after the moves are complete.

I think my answer to #1 above covers this? The configurator might not give you exactly what you want, so you'll have to do some manual configuration for advanced things like independent leveling. Defining the U axis and endstops and then recombining them will be done in the homing files or bed.g.

PuterPro

@phaedrux said in 2nd Z Endstop Missing in RRF Config Tool:

1a. The configurator isn't perfect. It's basically just a working starting point. Manual editing of the config.g file ... will be needed.

Thanks a lot!! Makes a whole lot more sense.

1b. The BLTouch is quite reliable. Once it's configured and working it's a very simple mechanism in and of itself. Not much to fail.

Good to know, but I've seen people have them fail in various forums, and I doubt it's as reliable as a mechanical switch, so I'll stick with "mildly paranoid" a good attitude towards any electronics, particularly DIY setups, LOL.

Yes you can have a microswitch wired up and used as a backup emergency stop if you want. ... As a general trigger though it can be active at any time, and you can wire multiple switches together to trigger all of the axis if you wish. https://duet3d.dozuki.com/Wiki/Connecting_an_Emergency_Stop

Recall seeing that now, but haven't had time to read my way through ALL the good data on the Wiki, thx for the reference, I'll check it.

However, ... A safer and simpler approach the protect against the failure of a probe or switch during a homing move (which is really the only time when you're actively trying to go towards an axis limit) is to adjust the motor current down during a homing move so that even if the probe or endstop fails, the motor won't have enough force to damage anything. You can use a M915 command in the homing files to scale the current to a percentage before the move, and then return to normal after the moves are complete.

EXACTLY what I was looking for, that you can limit current is perfect.

Defining the U axis and endstops and then recombining them will be done in the homing files or bed.g.

*OK, got it, I think I know how to do it, if not ... *

Thx again!