MotionBasic_2011分解.ppt

Lets take a look at a few miscellaneous tips when programming GSV and SSVs. ? * Here is a basic programming example using a SSV and the ConfigUpdateInProcess bit in a sequence. In step 70 we are performing a SSV and then moving to step 80. This rung is only scanned once because of this move block. In this rung we can have multiple SSVs issued before moving to the next step. In step 80 we wait for the config update in process bit to go low before issuing the homing command. It is important to wait for this bit before acting on those values. Remember you only have to wait for the config update in process bit if the parameter also exists in the drive. * * Explain that the parameters for a Virtual Axis are a small subset of the parameters for a physical axis. * * * * * Suggest that the Dynamics should be set so that the maximums of the slave axes will not be violated. * * The destination for GSV instructions and source for SSV instructions must be a tag. The data type of the destination and source tags must match the data type of the parameter you are getting or setting. For example, the data type for destination axis03_currentconversionconstant is a real and the data type for source home_active is a DINT. We will discuss where to find the data type for attributes in an upcoming slide if you are unsure when you begin to program. * Note: Discussion of merging multi-axis coordinated motion instructions is not addressed in this session, only identified here to make user aware of capabilities * * * * * Miscellaneous Motion InstructionsMotion Change Dynamics (MCD): (Confidential – For Internal Use Only) Copyright ? 2010 Rockwell Automation, Inc. All rights reserved. * Miscellaneous Motion InstructionsMotion Change Dynamics (MCD): (Confidential – For Internal Use Only) Copyright ? 2010 Rockwell Automation, Inc. All rights reserved. * Miscellaneous Motion InstructionsMotion Change Dynamics (MCD): (Confidential – For Internal Use Only) Copyright ? 2010 Rockwell Au