a problem with Flex-6C controller

[kcab]

When i am using PCI Flex-6C，Finding home functions does not work as the PCI 7344 do, The controller stops axis 1 and axis 2 during the finding home sequences when the axis 3 encountered home switch first.

[MarcoPolo5]

kcab,

The PCI Flex-6C uses the ValueMotion driver whereas the PCI-7344 uses the FlexMotion driver. The two drivers are not interchangeable. You mentioned that all axes stop when you axis 3 encounters a home switch. This should not happen with either driver. Is it a true home switch? Or is it a limit switch? They are not the same. You will not be able to home with this function if you do not have a home switch installed and only have limit switches.

Please give me some more details as to what you are seeing. Are you using LabVIEW? What versions of the drivers are you using? Is it a servo or stepper system? How is the function used in your program? How are you loading all three axes to home at the same time? Good luck with your project.

[kcab]

thank you for your reversion.
I am using FlexMotion5.11 and LabVIEW6.1,the MAX version is 2.2,i am sure the home switch and limit switches are well conneted.
I mentioned that all the axes before axis 3(axis 2 and axis 1) stop when you axis 3 encounters a home switch during the home searching. axis 1 stop when axis 2 enconters a home switch while axis 3 still moving. the stopped axes are still in finding home sequences (I mean the axis status is moving not completed),but they are really stopped,so the stopped axis could not find the home switch.

So I post the VI I am using with the above problem.

if I specify the finding home order (axis 1 the first,axis 2 the second, axis 3 the third,
)and perform the next axis to move whem the axis before has completed the home finding ,everything is ok,but it will take much more time.

[MarcoPolo5]

kcab,

Your vi has a problem with dataflow - and that might be the root of your homing issue. However, even if it is not, it will allow you to run your code in 'highlight execution' mode to debug where the problem is coming from. I striped down your code really quick to give an example of how you should use the error cluster to specify data flow in your program - I included a screen shot of the vi without any of the vi settings etc. to illustrate how to use the error cluster to specify data flow. You will notice that the error cluster is wired between vi's and when you run in 'highlight execution' mode, the program will follow the path of the error cluster. With cleaner code, you should be able to follow the debugging and find which vi or setting is causing this problem. None of the settings I saw however, would lead to this behavior. Please let me know what you find out - and let me know if you are still unable to find the root of the problem. Good luck with your project!