- Posts: 1943
- Thank you received: 0
(SOLVED) BUG REPORT: Gmocappy Homing buttons in joint mode in Master
I thought the whole idea of JA was to better treat dual motor axis and fixes the homing issue that gentrivkins had.....
Maybe not the whole idea but that was a big selling factor.
Please Log in to join the conversation.
bevins wrote: WAIT..... So you cant home a complete dual motor axis in JA.
No, you absolutely can. But it might only make sense when a homing sequence is defined.
linuxcnc.org/docs/devel/html/config/ini-....html#_home_sequence
Homing joints individually perhaps ought to search for other joints sharing the same home sequence.
Please Log in to join the conversation.
andypugh wrote:
No, you absolutely can. But it might only make sense when a homing sequence is defined.bevins wrote: WAIT..... So you cant home a complete dual motor axis in JA.
Andy, From what I can see, you absolutely can't home a joint axis other than with a home all. Well, let me rephrase that, becasue I'm sure somebody like you can devise some devious method.:evil:
I'm only a noob so I don't know the difference but the only way I've been able to home my half built machine is with the home all button. I thought that was the way it was done! Anyway, there are pins to home a joint and a pin to home all but there are no pins in the axis definitions to home an individual axis. After getting stung with this bug, I think the LCNC developers have not quite caught up wit the Joint Axis environment as it seems that axis definitions need to be updated so there is a homing pin for each axis now you can no longer depend on (for example) allowing Joint 0 be the surrogate X axis.
Please Log in to join the conversation.
Please Log in to join the conversation.
rodw wrote: Andy, From what I can see, you absolutely can't home a joint axis other than with a home all.
This might be considered a feature... It does at least ensure that the tool is out of the way before moving the gantry.
It would be interesting to see what happens if you toggle the "halui.joint.N.home" input of both sides of the gantry at the same time. (whether it waits for each side to complete each stage as with home-all or whether it just individually-homes each side)
Please Log in to join the conversation.
I have an associate who has run a lot of commercial profile cutters and his view of the geometry based on every machine he had ever operated was a bit different to mine. (He picked a different corner for home). As a result, I can see that I will need to add a "Park" button that moves the gantry to X max for loading etc so homing won't actually get things out of the road. Thats why I have a XXYZ machine and most people seem to have a XYYZ gantry machine.
I might have a go at your idea before I bolt things together. Perhaps Joint homing should check if it is part of a Joint axis and either do nothing or home it mates at the same time. Anyway, clearly, there is more work before axes and joints are truly independent of each other.
Please Log in to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
- Posts: 4739
- Thank you received: 2
Please Log in to join the conversation.
I think todw's way is the correct one. I will at first step introduce a check if any axis letters are double, if so I will set the corresponding button insensitive. I can not hide it, because hiding a button leads to place changes of the resting button and the order has to be the same if you use hardware button around the screen.
At second step, I will try to find a way to start homing of two joints at the same time. I will make that in a separate branch and will then need a very brave gantry user to test the changes, as I have no gantry. If that works, I will need to find a way to reorder the relations between joints and axis, to avoid homing the wrong joint/axis.
The better way would be to allow homing an axis and linuxcnc knowing the relation between axis and joints, but that is out of my skill.
And that could also cause a lot of problems on non trivial kinematics.
All the mentioned will only take place, on trivial kinematics (I count gantry as such).
Norbert
Please Log in to join the conversation.
newbynobi wrote: Hallo @all,
I think todw's way is the correct one. I will at first step introduce a check if any axis letters are double, if so I will set the corresponding button insensitive. I can not hide it, because hiding a button leads to place changes of the resting button and the order has to be the same if you use hardware button around the screen.
At second step, I will try to find a way to start homing of two joints at the same time. I will make that in a separate branch and will then need a very brave gantry user to test the changes, as I have no gantry. If that works, I will need to find a way to reorder the relations between joints and axis, to avoid homing the wrong joint/axis.
The better way would be to allow homing an axis and linuxcnc knowing the relation between axis and joints, but that is out of my skill.
And that could also cause a lot of problems on non trivial kinematics.
All the mentioned will only take place, on trivial kinematics (I count gantry as such).
Norbert
This is closing the doors for people that might need to use the same axis letters on different joints that are not gantry related. I think a better option would be to provide a checkbox on settings screen called dual motor gantry then do whatever you need to do to disable the homing of the double drive letters.
My thoughts.....
Please Log in to join the conversation.
bevins wrote:
newbynobi wrote: Hallo @all,
This is closing the doors for people that might need to use the same axis letters on different joints that are not gantry related. I think a better option would be to provide a checkbox on settings screen called dual motor gantry then do whatever you need to do to disable the homing of the double drive letters.
My thoughts.....
Maybe not. Perhaps my approach is a bit simplistic.If the detection code also referred to the HOME_SEQUENCE setting for each affected axis joint to see if it is negative (which is how a Joint Axis should be set up), then this should not affect the situation Bevins raises. I'm like Norbert, I simply don't know enough to be conclusive on this stuff given I only have half a LinuxCNC controlled machine under my belt
Please Log in to join the conversation.
