Limit manual travel on IDEX depending on the U axis position
-
@droftarts Hi Ian,
Have you had a chance to have a chat with @dc42 yet? -
@semi55 I have highlighted it. He’s rather busy with RRF 3.6 at the moment!
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts ok thank you very much!
-
@dc42 Have you already had a chance to look into this topic? Please let me know if you need any additional information; I’ll be happy to provide any necessary feedback.
Thank you very much!
-
@semi55 He's still busy with 3.6! To reiterate the question for @dc42 :
User wants to hide the U axis on an IDEX, so his users don't jog it and get unexpected movement. Seems fair, but:
- If he hides U with M584 P3, when U is mapped to X, and X is moved, there's no movement. This seems like a bug, as I thought M584 P# only hid the axes in DWC. I have not reproduced this. Is this expected behaviour with hidden axes that are mapped? As far as I'm aware M584 P should only hide the axis/axes homing and jog controls in DWC, but it seems to affect axis movement. I always thought it was odd that you had to unhide axes to home them, though again I haven't really experimented with it.
- Alternatively, to keep U and X in sync without extra movement (again, I haven't tested if this is the case, but he reports it), DWC could send an M400 after each time a U move is sent, maybe? Or would this cause problems with stuttering movement if a jog button was pressed multiple times?
Ian
