Verify CE 65 encoder compatibility
Before installation, confirm that the encoder is compatible with your DeviceNet network and controller. Verify the voltage requirements (typically 10–30 VDC) and ensure the resolution and update rate meet your application’s needs. Check the mechanical dimensions against your mounting space. This initial verification prevents costly rework later.
Mount the encoder with elastic coupling
The encoder must be connected to the drive shaft using an elastic coupling. This component is not optional; it is the primary mechanism that compensates for axial and radial deviations between the motor shaft and the encoder input shaft. Mounting the encoder directly without this compensation will transmit mechanical stress into the encoder’s internal bearings, leading to premature wear and signal errors.
The installation process requires precise alignment and secure fastening. Follow the sequence below to ensure the encoder is mounted correctly according to TR-Electronic specifications.
Connect SSI output wiring
The encoder primarily uses DeviceNet for communication, but some variants may support SSI (Synchronous Serial Interface) or other digital outputs depending on the specific model configuration. Always consult the specific model’s datasheet to confirm the available output types.
If your application requires SSI, follow these wiring guidelines:
- Shielded Cable: Use a shielded twisted-pair cable for data lines to minimize electromagnetic interference (EMI). Ground the shield at one end only (typically the controller side) to prevent ground loops.
- Power Supply: Connect the encoder’s power supply (V+ and GND) according to the voltage specifications (10–30 VDC). Ensure the power supply is stable and filtered.
- Data Lines: Connect the SSI data output (A+ and A-, or similar differential pairs) to the controller’s SSI input. Ensure correct polarity and termination if required by the controller.
- Clock Signal: If using SSI, connect the clock signal lines properly. The encoder generates the clock, so ensure the controller is configured to receive rather than send the clock.
- Grounding: Connect the encoder’s housing ground to the machine ground to reduce noise. Verify that the ground connection is low-resistance.
Configure controller parameters
After physical installation and wiring, configure the DeviceNet parameters in your controller. The encoder typically uses standard DeviceNet objects for position and status data.
- Node ID: Assign a unique DeviceNet node ID to the encoder. Ensure no other device on the network shares this ID.
- Baud Rate: Set the baud rate to match the rest of the DeviceNet network (e.g., 125 kbps, 250 kbps, 500 kbps). Mismatched baud rates will prevent communication.
- IODD File: Load the correct IODD (I/O Device Description) file for the encoder into your controller’s configuration software. This file defines the data structures and parameters available from the encoder.
- Parameter Settings: Configure the encoder’s internal parameters, such as resolution, direction, and reset position, via the DeviceNet network. These settings are often stored in non-volatile memory.
- Test Communication: Use a DeviceNet scanner or your controller’s diagnostics to verify that the encoder is online and transmitting data correctly. Check for any error codes or communication faults.
Troubleshooting communication issues
If the encoder is not communicating or providing accurate data, follow these steps to diagnose the issue:
- Check Power: Verify that the encoder is receiving the correct voltage (10–30 VDC). Use a multimeter to check the voltage at the encoder’s power terminals.
- Inspect Wiring: Check all connections for loose wires, damaged cables, or incorrect pinouts. Ensure the shield is properly grounded.
- Verify DeviceNet Settings: Confirm that the node ID and baud rate match the network configuration. Check that the IODD file is correctly loaded in the controller.
- Check for Errors: Use the encoder’s LED indicators or diagnostic software to check for error codes. Common errors include over-temperature, over-voltage, or communication timeouts.
- Test with a Known Good Controller: If possible, connect the encoder to a different controller or DeviceNet scanner to isolate whether the issue is with the encoder or the controller.
- Review Mechanical Installation: Ensure the encoder is securely mounted and the coupling is properly aligned. Mechanical issues can cause signal jitter or loss.

No comments yet. Be the first to share your thoughts!