TimothyMoulder
Member
Hi all!
Does anyone have any experience with Giddings and Lewis MMC motion controllers, programming with PicPro? I'm having alot of trouble fathoming the ladder scan on this thing, and how it interacts with the User Defined Function Blocks.
According to the sparse documentation, a UDFB is scanned whenever it is encountered in ladder, regardless of whether it's ENable input is connected or active. That seems pretty counter-intuitive right there, since it seems to indicate that you can have a UDFB free-floating in the ladder and serving as it's very own little program.
However, it will not transfer parameters into the UDFB unless the ENable input is active. There is no mention of transferring value OUT of the UDFB at all. In the free-floating example, does this mean outputs can be turned on in the UDFB, but never surface in the hardware?
Any thoughts or input would be helpful.
Thanks!
TM
Does anyone have any experience with Giddings and Lewis MMC motion controllers, programming with PicPro? I'm having alot of trouble fathoming the ladder scan on this thing, and how it interacts with the User Defined Function Blocks.
According to the sparse documentation, a UDFB is scanned whenever it is encountered in ladder, regardless of whether it's ENable input is connected or active. That seems pretty counter-intuitive right there, since it seems to indicate that you can have a UDFB free-floating in the ladder and serving as it's very own little program.
However, it will not transfer parameters into the UDFB unless the ENable input is active. There is no mention of transferring value OUT of the UDFB at all. In the free-floating example, does this mean outputs can be turned on in the UDFB, but never surface in the hardware?
Any thoughts or input would be helpful.
Thanks!
TM