Homing additional axis and missing A axis



  • I am able to home U and V. Homing W to min end stop doesn't appear to work. It will not go into negative. Any suggestions to firmware changes.
    Also A axis doesn't show up in the web console or the LCD – what do I need to change to get that to work?



  • will not home A axis either. Just freezes/reboots if I try to do a movement with of A or W with S1



  • M114 detects the limit switches for both W and A axis. W and A axis move correctly when just issuing G1 commands, but will not home. Issuing the G1 command with S1 produces no motion/ also a firmware crash. Enabling debug doesn't show any additional information, just prints the debug for the move, but doesn't perform the move. Please help.


  • administrators

    Can you confirm that you are using a DueX2 or DueX5 expansion board?

    Please use M119 or the Machine Properties page of DWC to check that all the homing switches are working. Perhaps you have already done that, but you said M114.

    What G1 command exactly are you sending that gives a firmware crash, and which firmware version are you using? Do G1 S2 commands work properly with the W and A axes?



  • M119 yes, I mix those up – it detects the the limit switches. And machine properties show proper hits at limit switch 5 and 6.
    I remapped Z to drive 11 (I added an external 4 amp driver) -- limit switches though work in the same sequence.
    X - 0, Y-1, Z-2, Y-3, U-4,V-5, W-6
    G1 S2 moves the W and A but doesn't stop at the limit switch.
    What should
    M119 returns this
    Endstops - X: at min stop, Y: at min stop, Z: not stopped, U: at max stop, V: at max stop, W: at min stop, A: at max stop, Z probe: not stopped

    This is my homing script for W
    should home to min:

    G91
    G1 W -600 F3000 S1
    G1 W 4 F600
    G1 W -10 S2
    G90

    causes a crash -- first command S1 triggers a crash.
    S2 works fine, but it doesn't home just tries to keep moving through the limit switch hit.

    Thank you

    Yakov



  • oh, and yes I am using DueX5 – LEDs for the limit switches turn on/off correctly as expected


  • administrators

    OK, I've worked out what the problem is. I'll need to do a new beta firmware release to fix it. I'll try to get that done today or tomorrow.



  • As, you know I have Y mapping added to my firmware and the 11th stepper. So I'll need to merge that into the new firmware. So far everything is working out well, just ran into this and was really weird. I stayed up way too late trying to figure out what was wrong. U and V home, but W and A don't.
    I'll need to tweak the web firmware to add A axis to the web interface I guess. Probably the LCD firmware too –
    FYI LCD home V and home W trigger home U, not a big deal -- they do the right thing in the web interface.

    So far dual idex is working out -- kinematics work fine. I'll work on connecting the thermistors extruders, heaters, fans etc to the duet. All the wires are organized, just wanted to get the cool homing working 😉 with each extruder going to it's corner.

    Yakov


  • administrators

    I've run some tests:

    • DWC 1.17+2 (and probably earlier versions too) displays axes ABC but doesn't handle them correctly. I've asked chrishamm to look at this.
    • The problem with homing using endstops 5-9 is as I suspected. I've done a quick fix and I am about to test it. Until RRF 1.20, endstops 5-9 will have higher latency than endstops 0-5. I hope this won't cause problems for you.

    Which Duet do you have: WiFi or Ethernet?



  • @dc42:

    I've run some tests:

    • DWC 1.17+2 (and probably earlier versions too) displays axes ABC but doesn't handle them correctly. I've asked chrishamm to look at this.
    • The problem with homing using endstops 5-9 is as I suspected. I've done a quick fix and I am about to test it. Until RRF 1.20, endstops 5-9 will have higher latency than endstops 0-5. I hope this won't cause problems for you.

    Which Duet do you have: WiFi or Ethernet?

    latency wouldn't be an issue as long as they home – I can home slowly if it helps with latency issues. Likely by the time I'm further along in the build -- have the heated bed and all other parts done -- you'll have 1.20 out...I'm moving quick with the build, but the wiring is painfully slow, as there is a lot of them, and getting all the wires neatly out through cable chains to the duet was fairly difficult, it's finally done now, so I hope to connect all the thermistors, fans etc -- I've gone through over 200 feet of wire sleeving and about 8 30m spools of silicone wire. None of the runs are especially long, but just there is a lot of things to wire up.
    I'm curious find you where the bug was? I was looking through the firmware source and I'm not seeing it. I'm a programmer by trade, and fact that I couldn't figure it is bugging me.
    PS -- my duet is Ethernet -- all my printers are hard wired.

    Yakov


Locked
 

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