AutomationDirect Logo Productivity Series Frequently Asked Questions



Product Selected: Productivity Series
Category Selected: High-speed count / Pulse out

Press "Ctrl-F" to search for specific words in this FAQ.

Question: How do I create a "Jog" function with the new P3-HSO module?
Answer: Use 2 VMOV instructions boxes. Set one for a positive "Move Direction" and set the other for negative. You can use a common tag for "Velocity" and "Ramp Rate", or use constants.

Have your Jog pushbuttons wired into standard inputs of the P3 system, and use them as the logic to enable the respective VMOV box.
FAQ ID: 1395
Question: What is meant by "Delay Registration Action by" in the VMOV and SMOV boxes? Is this a time delay?
Answer: You can substitute the words "Inhibit" or "Offset" in place of "Delay". This is not time-based, merely a distance before the "Decel to a Stop" takes effect. You can use it to decrease your overall Registration time, since if only "Decel to a Stop" is checked, then decel will immediately start at the Registration input. This could slow your motion down. By using both boxes, the motion can continue at the steady velocity, until it reaches the value set in "Delay Registration by", then the decel will take place. The user must determine what acceptable values are for his system, the instructions cannot prevent overshoot if values are too small are entered into the instructions.
FAQ ID: 1397
Question: How do I create a "follower" or "slave" function/application with the P3-HSI and HSO modules?
Answer: Very easily! There are 2 main ways to do this: using both an HSI and an HSO module, OR, just using an HSO module with another signal source (analog perhaps).
1)With HSI and HSO module: In Hardware Config for the HSI module, when you get to "Channel x Setup", the tag you create for the entry "Current Velocity" ("MyMasterVelocity" for example)will be the incoming master velocity signal. This will be the tag used in the VMOV instruction in the ladder.Continue with the HSI and HSO configuration, compile and save your project.
Now, in the ladder, use the VMOV box, and in the Velocity entry, use the tag from above "MyMasterVelocity" and fill out the rest of the entries in the box. When enabled, assuming the Scaling of HSI and HSO are even, the VMOV will output pulses in direct relation to the value of "MyMasterVelocity".
2)If just using an HSO module, setup the module in Hardware Config, compile and save project. Again, the VMOV box will be used, and the master velocity signal ( analog, calculated, external comms, etc) will be the tag used in "Velocity" of the VMOV box. You will need to match up the ratio between the two, either using the Scaling setup of the HSO, and/or a SCALE instruction in the ladder for your master signal.
FAQ ID: 1398
Question: Can I use a P3-HSI module to read the SureServo line-driver encoder output?
Answer: Yes! The P3-HSI can accept both differential (line-driver) or single-ended (sink/source) as input signals. There is a wiring diagram in the P3-HSI insert for line driver signals.

  1. OA(servo) to 1A (HSI)
  2. /OA to 1A-
  3. OB to 1B
  4. /OB to 1B-
FAQ ID: 1399
Question: Can I use a SureServo drive with the P3-HSO module?
Answer: Yes. There is an HSO-to-SureServo wiring diagram in the P3-HSO insert.
    By default, the SureServo is programmed for Pt mode (think "Pulse Train").
  1. Follow the Quick Start Guide in Appendix A of the SureServo manual. When you have finished the initial section "Spin the Motor", go to the "Position Mode" section.
  2. Follow the procedures in the "Pt Mode" sub-section.
    You will need to set P2.15 and 2.16 to "0" at the end of this section, as Overtravels will need to be wired into the GP inputs of the HSO module. If you don't do this, you will get an ALE 14/15 alarm on the SureServo.
  3. Go to the P3 software, and select "Hardware Config". Either add or edit your HSO module, and assign your Overtravels and/or Home Sensor (if any are used), into the GP Input section of the Module Setup (use Status Tag names like "Ch1_Rev_Overtravel" or "Ch1HomeSensor", much easier to recognize in ladder later on)
  4. In the "Channel x Setup" tab, assign your tags as your application requires. Overtravels will be configured in the "Physical Limits" section, and the meaningful tag names make it easy to select your inputs. By default, the HSO is setup to deliver Pulse/Direction output signals, and that is what the SureServo is configured for as well.
  5. After the channels are configured as desired, click OK, exit the Hardare Config, and Compile and Save your project.
  6. Now, move to creating the ladder in the P3 software. Typically, the HOME, VMOV and SMOV would be the most used instructions. HOME instruction would usually be used in a linear application, with finite travel ( like a linear slide, or milling machine table). A rotary application like nip or feed rollers typically would not use a Home sensor.
  7. SMOV- This is a simple trapezoidal profile, can be used in Absolute mode ( like the previously mentioned linear slide) or in Relative mode ( like a feed to length, or nip roller application). The "Target" entry is your actual position in Absolute mode ( like moving to different numbers on a ruler - input a different number, the instruction delivers pulses in the proper direction to get to that number). In Relative mode, this would be the length of your feed.
  8. VMOV -Typically, this instruction will be used as your "JOG" feature (see FAQ 7 in this section).
FAQ ID: 1401