Go to Parker.com
  • Sign in
Technologies
  • Aerospace
  • Climate Control
  • Electromechanical Group
  • Filtration
  • Fluid and Gas Handling
  • Hydraulics
  • IoT
  • Pneumatics
  • Process Control
  • Sealing and Shielding
Other Groups
  • Parker Indego
Blogs Forums Knowledge Bases
Parker Community
Parker Community
  • Technologies
    • Aerospace
    • Climate Control
    • Electromechanical Group
    • Filtration
    • Fluid and Gas Handling
    • Hydraulics
    • IoT
    • Pneumatics
    • Process Control
    • Sealing and Shielding
    Other Groups
    • Parker Indego
    Blogs Forums Knowledge Bases
  • User
  • Site
  • Search
  • User
Home Technologies Electromechanical Group Electromechanical - Industrial Electromechanical Industrial Knowledge Base ERES /ORES Relationship for Gemini GV Products
Electromechanical - Industrial
  • Technologies
  • Electromechanical Group
  • Electromechanical - Industrial
  • More
  • Cancel
Electromechanical - Industrial
Electromechanical Industrial Knowledge Base ERES /ORES Relationship for Gemini GV Products
  • Electromechanical – Industrial Support Forum
  • Electromechanical Industrial Knowledge Base
  • Members
  • Sub Groups
  • More
  • Cancel
  • New
Electromechanical - Industrial requires membership for participation - click to join
  • Electromechanical Knowledge Base & Frequently Asked Questions
  • Motion and Machine Controllers+
  • General Technology Information+
  • Virtual Engineer+
  • Visualization and Human Machine Interface (HMI)+
  • Servo Drives and Servo Drive/Controllers-
    • Aries Drive (Discontinued)+
    • Compax3+
    • Dynaserv (Discontinued)+
    • Gemini (Legacy)-
      • 24 Volt Keep Alive
      • Analog input on GV6, GV6K, GT6, GT6K
      • Audible Noise in Stepper Motors
      • Cable breakout modules for the Gemini
      • Can I run the MX80L using a Gemini Drive?
      • Can the Gemini Products take a DC voltage supply?
      • Changing Motor direction on the GV6 or GT6
      • Chopping frequency of the Gemini drive.
      • Connector Part Numbers
      • Controller to GV Cables
      • Currently Released Gemini Drive Products
      • Daisy chaining GVs and GTs
      • Digital Notch Filters
      • Does the Gemini drive have a test mode?
      • Downloading the OS to my Gem6K locks up.
      • Encoder Motors Work with Gemini Resolver units
      • ERES /ORES Relationship for Gemini GV Products
      • GC-SDA Fault output is not really the fault output
      • GEM-VM50 screw-terminal breakout dimensions
      • Gem6K (GV6K & GT6K) Family Letter of Volatility
      • Gemini MaxPlus (MPM) Resolver Option 1 Connection
      • Gemini - Downloading in
      • Gemini - MaxPlus (MPM) Encoder Option 1 Connection
      • Gemini - MaxPlus (MPM) Encoder Option 5 Connection
      • Gemini Analog Input Deadband
      • Gemini Analog Output A now dithers
      • Gemini GV - Resolver to Encoder Signal Conversion
      • Gemini GV6 & GT6 RS232 Daisy-Chaining ERRLVL
      • Gemini Maximum Frequency Input and Output
      • Gemini OS Download Failures
      • Gemini Step & Direction Inputs
      • Gemini Update Rates.
      • Gemini Variable Resolution
      • Gemini: 400LXR Tuning
      • Gemini: ASCII or Binary?
      • Gemini: VIDEO: express basics training: How to Connect Ethernet (includes Win7)
      • Getting the letter a with a ~ over it in Motion Planner Terminal
      • GFB-KIT Pinout
      • GV Cable Diameters.
      • GV6K & GT6K cannot Follow Analog Onboard Input
      • GV6K Tuning in Position Mode with Motion Planner
      • Hall State Checking on Gemini Products
      • Hall-less Startup on Gemini
      • I cannot communicate with my GEM-6K.
      • Limits on Gemini
      • MS cable option vs. GS cable option
      • OS 1.70 Additions
      • Replacing the Gemini GC-SDA
      • RESET command in STARTP program
      • Resolution of the Gemini command signal.
      • RS232 Troubleshooting for the Geminis
      • Step & Direction Output
      • TASX Bit 1 -- Motor Temperature Fault
      • TASX Bit 10 - Bridge Fault (Hardware)
      • TASX Bit 11 -- Bridge Over-Temp Fault (Software)
      • TASX Bit 12 -- Over-Voltage Fault
      • TASX Bit 17 -- Stall Detected
      • TASX Bit 18 -- Override mode
      • TASX Bit 19 -- Foldback Active
      • TASX Bit 2 -- Low Voltage Fault
      • TASX Bit 20 -- Power Dissipation Circuit Active
      • TASX Bit 21 -- Bad Hall State Detected
      • TASX Bit 22 -- Unrecognized Hardware Detected
      • TASX Bit 23 -- User Fault Input Active
      • TASX Bit 24 -- Keep Alive Circuit Active
      • TASX Bit 25 -- Power Dissipation Circuit Fault
      • TASX Bit 28 -- Motor Configuration Warning
      • TASX Bit 29 -- ORES Failure
      • TASX Bit 3 -- Drive Temperature Fault
      • TASX Bit 30 -- Motor Thermal Model
      • TASX Bit 31 -- Commanded Torque Limit Hit
      • TASX Bit 5 -- Encoder/Resolver Failed
      • TASX Bit 7 -- Motor Configuration Error
      • TASX Bit 8 -- Incoming Pulses
      • TASX Bit 9 -- Velocity Error Limit Exceeded
      • The GV and Linear Motors
      • Tuning a GV6K GV6 or GV in Position Mode
      • Tuning GV or GV6 drives with large inertia loads.
      • Tuning the Gemini in Position Mode
      • Tuning the Gemini in Position Mode.
      • Tuning the Gemini in Torque Mode.
      • Tuning the Gemini in Velocity Mode.
      • Using Gemini with Empire Magnetics Step Motors
      • VIDEO: Basics Training: GV or GT drives
      • VIDEO: Basics training: GV6 or GT6 drive controllers
      • VIDEO: Basics training: GV6K or GT6K drive controllers
      • What are Q and D currents?
      • What does the Error Log contain?
      • What drives can work with a DC brushed motor?
      • What happens in Keep Alive mode?
      • What motors with what Gemini drive?
      • What recognitions does the Gemini GV have?
      • What replaces the Gemini GT stepper drive?
      • What replaces the Gemini GT6 stepper drive/controller?
      • What replaces the Gemini GT6K stepper drive/controller?
      • What replaces the Gemini GV6K servo drive controller?
      • Which Motors Work with GV-L Drives? GV-U Drives?
      • Which rotation is considered positive for GV6K?
      • Why doesn't my Drive I/O cable tighten down securely when using the jackscrews?
      • Why will my PAD and PED not update on the Gemini?
      • Z channel output from the Gemini?
    • IPA Drive/Controller+
    • P Series+
    • PSD - High Performance Servo Drive+
    • ViX (Legacy)+
  • Stepper Drives and Stepper Drive/Controller+
  • Gearheads+
  • AC/DC Industrial Drives+
  • Servo Motors+
  • Step Motors+
  • Linear and Rotary Positioners+
  • Electric Cylinders+
  • T-Slot Aluminum Framing+
  • C3 + Xpress + ETH+
  • How can I stay updated on Parker electromechanical and drives product news?
  • Legacy (Discontinued)+
  • Other+
  • Memorandum: Information on EPA ban of Persistent bioaccumulative toxin (PBT)
Wiki Actions
  • Share
  • More
  • Cancel
Community Quick Links
  • Home
  • Technologies
    • Aerospace
      • Supplier Resource Center
    • Climate Control
    • Electromechanical Group
      • Electromechanical - Industrial
      • Electromechanical – Mobile
    • Filtration
    • Fluid and Gas Handling
    • Hydraulics
    • IoT
      • Mobile IoT
    • Pneumatics
      • Pneumatic Industrial
      • Pneumatics Mobile
    • Process Control
    • Sealing and Shielding
  • Other Groups
    • Parker Indego
      • Parker Indego Instructors
      • Parker Indego Therapists
      • Parker Indego Distributors
  • Community Blogs
  • Community Forums
  • Community Knowledge Bases
Follow Us
  • Follow Parker Hannifin on social media

Follow Parker Hannifin on social media:

ERES /ORES Relationship for Gemini GV Products

Print Friendly and PDF
When selecting resolution values for motors used with Gemini servo drives or drive/controllers, it is important to understand the relationship between the encoder input signal resolution, set through the ERES command, and the encoder output signal resolution, set by the ORES command. Most of the time, these commands will be left at their default settings, but if modifications are desired, the following facts can be helpful in setting vales for these commands. REMEMBER TO ALSO READ THE COMMAND DESCRIPTIONS FOR BOTH OF THESE COMMANDS BEFORE CHANGING ANY VALUES.

The ERES command defines what the Gemini drive sees as the actual post-quadrature resolution of the encoder. In other words, ERES defines how many encoder pulses recieved by the Gemini unit is considered one complete revolution of the motor. The ORES command, on the other hand, defines the resolution of the encoder output pulses sent from the Gemini unit to the controller. Adjusting the value of the ORES command enables the Gemini unit to convert each incoming encoder pulse to a higher, equivalent, or smaller increment than the actual encoder resolution coming into the Gemini unit. A common reason for modifying the the ORES value is typically for converting the counts from a high resolution encoder to a more useable resolution for commanding moves (like setting a 20000 count/rev encoder to 3600 counts/rev, so as to more easily command moves in 1/10 degree increments).
Both the ERES and ORES values are automatically set upon download of the Gemini Motor Configuration file when performing the Gemini hardware setup (see the Gemini Hardware Installation Guide), but can be configured to any value within the range specified in the Command Description for ERES and ORES.

When the ORES value equals the ERES value, the actual native encoder counts are passed, unaltered, directly through the Gemini to the controller. When ORES is set to value higher or lower than the ERES value, the Gemini converts the incoming encoder pulses to "pseudo" counts, which are then output to the controller - as defined by the ERES/ORES ratio.

Note that setting the ORES value to a larger value than the ERES value does NOT increase the resolution of the encoder. In this situation, ORES simply acts as a multiplier. For example, if the ERES value is entered as 2 counts per revolution, and ORES is set to 5 counts to the controller, then every time that the encoder sends one pulse to the Gemini drive (each time an encoder pulse is detected by the Gemini drive from the encoder), the drive will output a "burst" of 10 "pseudo" counts to the controller; four encoder counts will appear as 10 "pseudo" counts at the controller, etc. In this case, ORES is simply scaling the encoder counts coming into the Gemini before they are output to the controller - nothing more. Additionally, if the encoder is somehow stopped between even multiples of counts, the ORES will not give partial counts to the controller. In the example above (ERES=2, ORES=5), if the encoder were somehow stopped at one encoder count, querying the encoder count at the controller would not come back with a response of 2.5 counts. The encoder count response that the controller will display will continually fluctuate between 0 and 5 counts.
  • Share
  • History
  • More
  • Cancel
  • Sign in to reply
Related
Follow Us
  • Follow Parker Hannifin on social media

Follow Parker Hannifin on social media:

Parker Hannifin Parker Hannifin

  • Products
  • About Parker
  • Investors
  • Community
  • Careers

Global Operations Global Operations

  • Divisions
  • Sales Companies
  • Worldwide Locations
  • Distribution Network
  • ParkerStore™ Network

Company Information Company Information

  • Newsroom
  • Event Calendar
  • Working with Parker
  • Product Brands
  • History

Global Support Center Global Support Center

  • Support
  • CAD
  • Where to Buy
  • Contact Parker
  • Manage Online Orders
© Parker Hannifin Corp 2023
  • Site Map
  • Safety
  • Privacy Policies
  • Terms and Conditions
  • Community Terms of Use
ENGINEERING YOUR SUCCESS.