Z endstop at high end should set Z position to maximum



  • Z endstop at high end should set Z position to maximum and not to zero after homing.



  • This post is deleted!


  • In 3D printer mode, the bed is usually regarded as Z=0 and the uppermost travel is regarded as maximum Z, a positive number.

    In CNC mode, upper Z travel is generally regarded as Z=0; all Z travel is represented by negative numbers. "Work Coordinate Systems" are often used to set Z=0=topofstock... and Z travel continues to be negative numbers.

    Anyway... Please post your config.g file.


  • administrators

    @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    Z endstop at high end should set Z position to maximum and not to zero after homing.

    It does if you have declared your Z endstop to be at the high end in your M574 command, unless you have overridden that using a G92 command in your homez.g or homeall.g file. https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_to_a_Z_max_endstop_switch



  • Hi,

    the bug is in the configuration tool, that generates a homing macro that always sets Z position to low end after homing independent whether Z stop is at low or high end. I want to change X and Y to high end later. We will see whether the same bug is in there.



  • The G92 command used to be commented out by default? But I experienced an issue where the config tool didn't generate a setup for Z limit switch when no Z probe was selected, this caused the Z position to be incorrect when homing.

    Post your config.g and homing macros so we can see whats going on to help



  • Thanks,

    then this might solve today. Actually I am integrating a Z Probe mechanism. I have three switches on the bed and want to probe the tool itself. The reason is that I have a 43mm mount where I want to mount a laser, an extruder or even a mill. Maybe you can point me to the direction (link) and save me a lot of time figuring this out.



  • You've been asked to post your actual config twice, and you don't seem to want to, that's fine, but that means you're wasting our time.



  • Sorry,

    I am building up the machine. Since I do not get emails when a post arrives I look once a while here. Here is my latest config.

    ; Configuration file for Duet Maestro (firmware version 1.21)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Sun Jul 28 2019 21:29:09 GMT+0200 (Central European Summer Time)

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

    M667 S1 ; Select CoreXY mode

    ; Network
    M550 P"My Printer" ; Set machine name
    M551 P"7072560" ; Set password
    M552 P192.168.1.10 S1 ; Enable network and set IP address
    M553 P255.255.0.0 ; Set netmask
    M554 P0.0.0.0 ; Set gateway
    M586 P0 S1 ; Enable HTTP
    M586 P1 S1 ; Enable FTP
    M586 P2 S1 ; Enable Telnet

    ; Drives
    M569 P0 S0 ; Physical drive 0 goes backwards
    M569 P1 S1 ; Physical drive 1 goes forwards
    M569 P6 S0 ; Physical drive 6 goes backwards
    M569 P3 S1 ; Physical drive 3 goes forwards
    M569 P4 S1 ; Physical drive 4 goes forwards
    M569 P5 S1 ; Physical drive 5 goes forwards
    M584 X0 Y1 Z6 E3:4:5 ; Apply custom drive mapping
    M350 X8 Y8 Z8 E8:8:8 I0 ; Configure microstepping without interpolation
    M92 X160.00 Y160.00 Z1600.00 E635.69:635.69:635.69 ; Set steps per mm
    M566 X900.00 Y900.00 Z90.00 E120.00:120.00:120.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z300.00 E1200.00:1200.00:1200.00 ; Set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z1.00 E250.00:250.00:250.00 ; Set accelerations (mm/s^2)
    M906 X800.00 Y800.00 Z800.00 E800.00:800.00:800.00 ; Set motor currents (mA)
    M84 S0 ; Disable motor idle current reduction

    ; Axis Limits
    M208 X0 Y0 Z-155 S1 ; Set axis minima
    M208 X200 Y160 Z0 S0 ; Set axis maxima

    ; Endstops
    M574 X1 Y1 Z2 S0 ; Set active low and disabled endstops

    ; Z-Probe
    M558 P5 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds
    G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
    M557 X0:200 Y0:160 S20 ; Define mesh grid

    ; Heaters
    M305 P0 X503 R ; Configure PT1000 for heater 0
    M143 H0 S90 ; Set temperature limit for heater 0 to 90C

    ; Fans

    ; Tools
    M563 P0 D0 ; 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
    M563 P1 D1 ; Define tool 1
    G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets
    G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
    M563 P2 D2 ; Define tool 2
    G10 P2 X0 Y0 Z0 ; Set tool 2 axis offsets
    G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C

    ; Automatic saving after power loss is not enabled

    ; Custom settings
    M555 P2 ; Set output to look like Marlin

    ; Miscellaneous
    T0 ; Select first tool

    I thought this board was ready to use. OK, I got this with 2.02RC5(RTOS) (2018-11-28b1) flashed. Should I go back to a release version? I cannot waste time to do software testing. I wanted a board ready to work, Now I connected the bed heater and a PT1000 and got an error that the termister is shorted. I meassure 1.1V at the input what is appropriate with a PT1000 and a 2.2k pullup resistor. It is the C-input. The bed input I did not find on the Maestro.



  • @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    ; Axis Limits
    M208 X0 Y0 Z-155 S1 ; Set axis minima
    M208 X200 Y160 Z0 S0 ; Set axis maxima

    Your Z axis minima and maxima don't make any sense, so when you home to zmax you wont get a correct z position.



  • @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    I got this with 2.02RC5(RTOS) (2018-11-28b1) flashed

    Update to 2.03 by uploading this zip file as is on the settings page: https://github.com/dc42/RepRapFirmware/releases/download/2.03/Duet2Firmware-2.03.zip

    Release notes etc here for reference:
    https://github.com/dc42/RepRapFirmware/releases/tag/2.03

    @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    I cannot waste time to do software testing.

    People who don't have time to do it right the first time must find time to do it right the second time.



  • @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    I thought this board was ready to use. .............................

    It is ready to use. And the first thing it does when you power it up is read the configuration from the SD card. Unfortunately that's the only way that the board can "know" what sort of printer you have and how it is configured. If that information is incorrect, it will misbehave.



  • I think he was refering to the board shipping with release candidate firmware as opposed to a stable release.



  • Thanks,

    I thought of problems of the RC either and will try the release today. Last time I looked, this seemed to be the latest version. The problem is, that this is too complex to know everything at the beginning. I can do root cause analysis on aircraft electronic failures, but I am an absolute beginner on Duett. So please guide me.

    Concerning the Z Axis settings: This was my latest setup. It has the advantage of setting the Z value to zero manually. The config tool does not set to maximum in any configuration I tried. Is the source code available? I will fix it myself if no one does.

    It is to early to tweak the config files by hand. I still have to do some improvements on the hardware.



  • Flashed 2.03

    PT1000 on C gives approx 1.1V and Error shorted sensor. Disconnecting the sensor gives a different error. Seems I am on the right port.



  • Deleting the malicious line from homez.g and homeall.g does the trick. DC42 mentioned somewhere that the firmware sets the value correct upon hitting the end stop. So no need to mess it up.

    The PT1000 does not work on the bed thermistor input either. It tells a short when connected and an open circuit when disconnected. I measure a slightly different voltage. Does someone save a few Cents by not using 0.1% resistors or does the CPU have such a bad reference voltage?



  • @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    Deleting the malicious line from homez.g and homeall.g does the trick.

    What did you delete from the homing files?
    Did you correct the z axis minima and maxima?



  • Is this on a meastro or wifi board?



  • Oh sorry, I need some practice on reporting here. It is a Maestro board. Now with the latest release software. Just for completeness.

    ; homez.g
    ; called to home the Z axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Mon Jul 29 2019 18:46:55 GMT+0200 (Central European Summer Time)
    G91 ; relative positioning
    G1 Z5 F6000 S2 ; lift Z relative to current position
    G1 S1 Z165 F1800 ; move Z up until the endstop is triggered
    ;G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

    ; Uncomment the following lines to lift Z after probing
    ;G91 ; relative positioning
    ;G1 S2 Z5 F100 ; lift Z relative to current position
    ;G90 ; absolute positioning

    I set back the range to positive values from zero like it was before I started trying different configuration.

    I have the three Z stepper on three external TB6600 (modified the opto-coupler of this garbage to make it work) and a 74HC245 as driver (the only suitable chip conrad had in stock) together with a fancy circuitry for synchronization at the Z stop I developed. But this was a mistake either. The board can do this better. I read today. So I will change this to the internal drive and use a TB6600 for the extruder. Or better the add on board. We will see. I hope I will find the article about Z axis synchronization with Z probing again. It looked like it was made for me.



  • @thomas_rudloff said in Z endstop at high end should set Z position to maximum:

    Thanks,

    I thought of problems of the RC either and will try the release today. Last time I looked, this seemed to be the latest version. The problem is, that this is too complex to know everything at the beginning. I can do root cause analysis on aircraft electronic failures, but I am an absolute beginner on Duett. So please guide me.

    Concerning the Z Axis settings: This was my latest setup. It has the advantage of setting the Z value to zero manually. The config tool does not set to maximum in any configuration I tried. Is the source code available? I will fix it myself if no one does.

    It is to early to tweak the config files by hand. I still have to do some improvements on the hardware.

    Just picked this one up as it sounds similar to the issue I was having (feel free to look at my numerous posts vis a vis upgrading my board/ firmware/ gcode #basically-a-new-printer) and really must say... oh. my. god.

    Between the wikis and the forums, this place is an absolute treasure trove of information! The folks here have cultivated/ created/ generated one of the best open-source resources (personally) I've ever seen. The participation from people a) willing to help and b) able to help is outstanding; without having to wait 3 weeks for the 1 guy who doesn't have his arse facing the sky to send a semi-helpful reply.

    1. remember this is open-source and has multiple applications and many many many more methods of doing so;

    2. remember you're free to chose another platform (if you're struggling with duet, go have fun with octoprint...);

    3. ask nicely and show some humility - coming here (where resides some clever folks from my observations) throwing the bosses weekly buzzwords like RCA isn't going to win you any favours and either is banging the drum about aircraft electronics like it's going to impress anyone

    ... fortunately, the people with the noodles are so nice they continue to help regardless

    e_p
    just-another-newcomer-seeking-help, CEng RAeS
    [... Avionics, hehe 😮 ]


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.