two independent X at the same time.
i got two problems that i could not solve:
1. pair UV always stops with joint following error. i've read manuals and tried to change parameters that can be responsible for this mistake but failed.
and one thing i noticed that i do not understand: one can't just define AXIS_0, 1, 6 and 7. all of them (XYZABCUV) have to be described, from 0 to 7 explicitly. that makes emc2 to load every even the most simple ngc file for a half of a minute. but in hal file i can define only that axes that are needed (0,1,6,7). so emc uses 8! axes and maybe somewhere there the PC "loses" its ability to count all of them? maybe i use a wrong word (english is not my native).
2. after redesigning the schema one pair of axis (XY) wherever it is switched works fine. but UV never makes even a single step before joint error. but GUI shows that movements occur. is there something that i could miss?
conf files:
unas.ltd.at.tut.by/9.ini
unas.ltd.at.tut.by/9.hal
Please Log in or Create an account to join the conversation.
- step4linux
- Offline
- Premium Member
- Posts: 115
- Thank you received: 5
Please Log in or Create an account to join the conversation.
why did you say that all axes have to be linear? maybe this can affect.
the file is edited now.
Please Log in or Create an account to join the conversation.
1. pair UV always stops with joint following error. i've read manuals and tried to change parameters that can be responsible for this mistake but failed.
and one thing i noticed that i do not understand: one can't just define AXIS_0, 1, 6 and 7. all of them (XYZABCUV) have to be described, from 0 to 7 explicitly. that makes emc2 to load every even the most simple ngc file for a half of a minute. but in hal file i can define only that axes that are needed (0,1,6,7). so emc uses 8! axes and maybe somewhere there the PC "loses" its ability to count all of them? maybe i use a wrong word (english is not my native).
As I think you have found by now, you were re-using the y- signals twice of U and V, which won't give the result you want.
You don't necessarily have to fully describe the unused axes in the INI file, I think you can leave them blank as long as the header line exists.
The fixed mapping between Axis-X and Joint-0 etc will be removed in a future version of emc2.
Please Log in or Create an account to join the conversation.
i lost it, cannot reproduce it on home PC, but if i just edit ini file to use all that 8 axes, it even at this stage gives joint folowing error.
Please Log in or Create an account to join the conversation.
- step4linux
- Offline
- Premium Member
- Posts: 115
- Thank you received: 5
Gelar wrote:i lost it, cannot reproduce it on home PC, but if i just edit ini file to use all that 8 axes, it even at this stage gives joint folowing error.
I assume you got the following errors because the axis are not in the hal file.
It is not enough to have it in the ini file.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
unas.ltd.at.tut.by/9.hal
and
unas.ltd.at.tut.by/9.ini
Please Log in or Create an account to join the conversation.
- step4linux
- Offline
- Premium Member
- Posts: 115
- Thank you received: 5
net upos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net upos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
...
net uenable axis.2.amp-enable-out => stepgen.2.enable
net vpos-cmd axis.3.motor-pos-cmd => stepgen.3.position-cmd
net vpos-fb stepgen.3.position-fb => axis.3.motor-pos-fb
...
net venable axis.3.amp-enable-out => stepgen.3.enable
look carefully at the numbers. stepgen.3 is stepgen number 3, this is ok.
But axis.3 is AXIS_3 and this is axis A !
so I would try:
net upos-cmd axis.6.motor-pos-cmd => stepgen.2.position-cmd
net upos-fb stepgen.2.position-fb => axis.6.motor-pos-fb
net uenable axis.6.amp-enable-out => stepgen.2.enable
net vpos-cmd axis.7.motor-pos-cmd => stepgen.3.position-cmd
net vpos-fb stepgen.3.position-fb => axis.7.motor-pos-fb
net venable axis.7.amp-enable-out => stepgen.3.enable
Note also:
If you skip axis in the hal file you always have the risk of follower errors.
In axis GUI you always see all axis in the "manual" menu.
If you accidentally select a non-existing axis and hit the +- buttons you have a follower error.
Could be there is a method to remove not used axis from menu, but so far I have not found it.
To avoid the confusing numbering and the risk of follower errors , I always include all axis in hal, which are defined in ini.
Gerd
EDIT: added lines for enable axes
Please Log in or Create an account to join the conversation.