Archie
Member
I have always used mapping to buffer IO to avoid random program hiccups caused by changing inputs in the middle of a program scan.
Now I am doing an integrated motion project that has 2 axes in a motion group. I do not map/buffer the axes, but use them directly in commands such as MAM. I have not found anything saying whether it is necessary to map since the Axes are not the actual IO tag of the Kinetix 5500 drive.
Twice I have seen the machine on startup go to a 0 position when it was instructed to go to a position such as 200mm. I am not sure whether to blame this on lack of mapping of the motion axes or something else.
Do the Axes synchronize with the program scan or is it necessary to buffer them?
Now I am doing an integrated motion project that has 2 axes in a motion group. I do not map/buffer the axes, but use them directly in commands such as MAM. I have not found anything saying whether it is necessary to map since the Axes are not the actual IO tag of the Kinetix 5500 drive.
Twice I have seen the machine on startup go to a 0 position when it was instructed to go to a position such as 200mm. I am not sure whether to blame this on lack of mapping of the motion axes or something else.
Do the Axes synchronize with the program scan or is it necessary to buffer them?