Totally my fault. For the first time followed my own advice - RTFM - there was a manual but it did not work as the tutorial does not work correct with version 3.
Can we get a warning on the tutorial "Independent Z motors and endstop switches" that it does not work with 3.0 and can be easyer done by M584 Z2:3 | M574 Z1 S1 P"zstop+whatever_pin" no other changes needet. That would have saved me a day of grief.
If any one is wondering why the heck the nice tutorial "Independent Z motors and endstop switches" is not working even after exchanging the "S" parameter with "H" and calling those endstops in the config.g names.
You realy should check your homeall.g and homez.g. As I found out you have to configure your your additional axis again in homez.g and homeall.g that means after splitting the axis into two, you put in steps per mm, axis min and max, corresponding endstop, microstepping, acceleration and jerk.
After "M584 Z2 U3 P4" the U-axis has no configuration at all everything from config.g is gone maybe even worse everything is set to default. Steps per mm is 80, axis length 0:200, microstepping is 16, motor current is 0 and so on.
I don't know if it is meant to work that way but I will share my homez.g as a starting point here anyways it might help with some problems.
; homez.g
; called to home the Z axis
;
G91 ; relative positioning
M584 Z2:3 P3 ; combine axes and hide U
G1 H2 Z5 F1000 ; lift Z relative to current position
M584 Z2 U3 P4 ; split Z motor control to Z and U for it to work we have to show U (param P4) in the UI
M574 Z1 S1 P"^zstop" ; configure active-low endstop for low end on Z via pin zstop
M574 U1 S1 P"^e0stop" ; configure active-low endstop for low end on Z via pin zstop
M92 U400 ; set steps per mm
M566 U24 ; set maximum instantaneous speed changes (mm/min)
M203 U600 ; set maximum speeds (mm/min)
M201 U100 ; set accelerations (mm/s^2)
M906 U600 ; set motor currents (mA) and motor idle factor in per cent
M208 U0:350 ; set axis maxima
G1 H3 Z-355 U-355 F1000 ; Move Z and U down until the switches triggers
G1 H2 Z5 U5 F1000 ; Move Z and U UP 5mm
G1 H3 Z-355 U-355 F100 ; Move slow Z and U down until the switches triggers
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
G92 U0 ; set U position to axis minimum (you may want to adjust this)
M584 Z2:3 P3 ; back to combined axes and hidden U
M574 Z1 S1 P"^zstop" ; configure active-low endstop for low end on Z via pin zstop
M574 U1 S1 P"^e0stop" ; configure active-low endstop for low end on Z via pin zstop
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
; G1 H1 Z-355 F3600 ; move Z down until the endstop is triggered
; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning
A lot of people are falling into this trap - you need to read the release notes. To save you time, the release notes will tell you that unless you need to deploy and retract a probe, you need to delete any deploy probe and retract probe files that you have in you .sys directory.
Nice idea but I have no probe nor any probe files in sys.
But:
Important! On a CoreXY machine, if upgrading from a version prior to 1.19beta9, you need to reverse the Y motor direction in the M569 command. Similarly for CoreXYU machines.
I missed it because it it so obvious that an axis will have to be turned around after an firmware upgrade.
Will try after my Print is finished.
In firmware 1.19 I can not home anymore. The printer runs into the end stop trying to go on.
it does not even stop after traveling 300mm
Going back to 1.18.2 fixes it and it works again.
;Home X
G91
G1 Z4 F200 ;move bed down
G1 X300 F3000 S1 ; go 300mm to hit endstop
G1 X-4 F600 ;back off 4mm
G1 X10 S1
G1 Z-4 F200
G90
G92 X252 ; as homing to max set position
;Home Y
G91
G1 Z4 F200
G1 Y300 F3000 S1
G1 Y-4 F600
G1 Y10 S1
G1 Z-4 F200
G90
G92 Y218
Sincerly
Sven
No need to disconnect and reconnect the PanelDue, it has a reset button.
My case does not have an hole never needed an Reset button on my other duet so I removed it to save some work.
Please update your PanelDue firmware to latest version. It includes a workaround for a C library bug that caused that kind of freeze.
I did the update from 1.14 to 1.15b3 and it works now.
Thanks
Do you have the IR sensor with through hole optical components, or with SMD optical components?
The new one with SMD. So no way to extend the range ?
Thanks a lot for your help
Sven
I use aluminium tape to block them. I had never had a problem triggering an other one they are about 350 mm apart on my delta.
Panel Due worked fine until I connected the the Mini height sensor.
Now the screen is frozen heater temp says "ovf" does not react on touch. Works fine on USB and (yes I know your not supposed to do it) after disconnecting it from the running duetwifi board and reconnecting it.
Duet webinterface works fine from start and I did not change any settings after connecting the probe.
[[language]]
M122
Diagnostics
Used output buffers: 2 of 32 (3 max)
Platform Diagnostics:
Memory usage:
Program static ram used: 19280
Dynamic ram used: 82816
Recycled dynamic ram: 304
Current stack ram used: 2768
Maximum stack ram used: 3600
Never used ram: 25072
Last reset 00:15:04 ago, cause: external
Error status: 1
Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 29.5, current 34.8, max 39.1
Supply voltage: min 24.6, current 24.7, max 25.0, under voltage events: 0, over voltage events: 0
Slowest main loop (seconds): 0.003113; fastest: 0.000040
Move Diagnostics:
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Heat Diagnostics:
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
GCodes Diagnostics:
Move available? no
Stack pointer: 0 of 5
macro is idle
http is ready with "M122"
telnet is idle
serial is idle
aux is idle
file is idle
Network Diagnostics:
WiFiServer is running
SPI underruns 0, overruns 0
Webserver Diagnostics:
HTTP sessions: 1 of 8
M575 P1 B57600 S1 is Still set in config.g.
And is there a way to get higher measurement range on the new probe with SMD IR led like an firmware update? Given a pin out of the ISP port and the hex file I could upload it myself.
Sincerely
Sven