
Encoder Troubleshooting & FAQ
Why is my Encoder Not Working?
Has your encoder failed during installation or operation? Has it stopped functioning and lacking any signal? If so, keep reading! Often, we do not have time to send a sensor back for complete analysis or even time to call an expert. That is why we have compiled some expert troubleshooting tips to get your encoder back up and running.
|
POSITAL Technical Chatbot
Finding the Root Cause
Encoder Failure: Finding the Root-Cause
An encoder is made up of several components that could cause a failure; therefore the origin of the problem may be harder to guess. Please find here below a systematic approach designed to help you work out which part of the encoder might be faulty.
LED: Self-Diagnosed Encoder Failure
Some of our sensors present diagnostic LEDs on the back of their connection cap or connector. They provide information regarding the device status. Check out what the blinking pattern means to understand the origin of the error.
1. Encoder Mechanical Failure
| Test | Result | Interpretation |
|---|---|---|
| Inspect the device for external signs of damage | No obvious sign of damage | N.A |
| Clear traces of damage | This is most likely the issue | |
| Can the shaft be manually moved? | Yes, without applying to much torque | N.A |
2. Encoder Power Supply Failure
| Test | Result | Interpretation/Action |
|---|---|---|
| Measure voltage and current on your power supply | Within the values specified on the product datasheet | N.A |
| Voltage and/or current lower than expected | Adjust the power supply | |
| Voltage and/or current higher than specified values | The encoder is probably damaged | |
3. Encoder Connection Issues
| Test | Result | Interpretation/Action |
|---|---|---|
| Try to ping the encoder | The encoder can be pinged | The encoder is connected to the network |
| The encoder cannot be pinged | The encoder cannot be found on the network. Check physical communication medium and configuration. | |
| Compare the actual pin assignment against the datasheet | The pin assignment is as expected | N.A |
4. Incorrect Output Data
| Test | Result | Interpretation/Action |
|---|---|---|
| Check the coupling with the moving part | Coupling correctly tightened | N.A |
| Coupling was too loose | Tighten the coupling and test the output data again | |
| Compare the actual resolution against the expected one | They are the same | N.A |
5. Configuration
| Parameter | Common Failures | Interpretation/Action |
|---|---|---|
| IP address / Node ID | Check if the IP address or Node ID on the encoder is the same as configured on the network | Configuration Tool |
| Duplicates | It can happen that some IP addresses, Node ID or Device Names appear twice on the network | Make sure the device does not have duplicates on the network |
| DHCP/BOOTP | This parameter can prevent the software from seeing the IP address |
FAQ

Q: What can I do when during the transmission of the position value, occasional malfunction? Occurs?
A: The CAN bus can be temporary in the bus off state also. Check if the last bus node has switched on the terminal resistor. If the last bus node is an encoder, the terminal resistor is in the connection cap.
Q: What to do when the encoder doesn’t transmit the bits for the limit switches?
A: The limit switch functionality must be activated once. Please follow the description you can find at 4.5. chapter in the manual.
Q: What to do in case of too many ERROR – frames?
A: The bus load is too high in that case. Check if all bus nodes have the same baud rate. If one node has another baud rate error frames are produced automatically.
Remark: The changing of baud rate and node number are only valid after a new power up, NMT Reset or the store parameters command.
Q: What to do when the encoder doesn’t respond - bus is active but the installed encoder transmits no boot-up message?
A: Steps to follow: 1. switch of the PLC. 2. remove the connection cap of the encoder. 3. check the turn-switch for the baud rate. 4. assemble the connection cap.
5. power on

Q: Why after switching from "Free Run" to "Run" a comparison error appears (different VendorIDs)? How to solve that?
A: Delete TwinCAT cache (xml file): Windows XP: C:\Documents and Settings\Username\ApplicationData\Beckhoff\TwinCAT\TwinCAT\Io Windows 7: C:\Users\ Username \AppData\Roaming\Beckhoff\TwinCAT\TwinCAT\Io
Q: I am using Omron PLC, how can I set up the preset value?
A: There are two ways of setting the preset values.
You can use the blocks as usual. On request we provide ESI files with Backup Flags.
When launching the project with this ESI file, the flag should appear on the main menu.
You must perform the following steps:
1. Transfer the preset value from the encoder to the PLC. 2. Change the preset value. 3. Transfer the preset value from the PLC to the encoder.
Q: What can cause: TwinCAT don't find during "Scan Boxes"
A: Check if the network card is supported from TwinCAT
During the installation of TwinCAT under Windows 7 are admin rights necessary. User admin rights are not enough. Start TwinCAT with admin rights. Install the driver for the network card.

Q: Why is the stat LED flashing at 4 Hz (4 flashes per seconds) after I replaced a rotary encoder in the machine? Now the controller cannot start the application.
A: Start the BOOTP/DHCP server to set the IP-Address and deactivate BOOTP.
Q: How to solve Error message "Invalid identifier"?
A: Check that the major revision of the encoder uses the same number as the EDS file. Check the website.
Q: Why stat LED is flashing with 4 Hz?
A: After replacing a rotary encoder in the machine, the controller cannot start the application. Additionally, the Stat LED is flashing at 4 Hz. Start the BOOTP server to set the IP address and deactivate BOOTP as a solution.
Q: How many encoders can work with one Rockwell PLC?
A: One encoder represents a traffic of only 100 Ethernet packets per second. The PLCs can manage 6,000-20,000 Ethernet packets/s. Rockwell has got two tools:
a. EtherNet/IP Capacity Tool. b. Integrated Architecture Builder (overdressed for analysis).
Q: What is the fastest possible cycle time (RPI) on our EtherNet/IP encoder?
A: 1ms.
Q: What is the default IP address of the encoder?
A: 192.168.0.250
Q: Why can’t I deactivate BOOTP?
A: 1. Firewall must not block Port 67 and 68. 2. Deactivate WLAN and all other network cards.
Q: Why after power-up the programmed parameters are lost?
Use the save command to save all programmed parameters in the non-volatile memory (NVM). Only Preset is saved automatically in the NVM.

Q: Why can’t we set the Preset value more than one time?
A: The Preset value will be saved in the flash of the encoder. This flash has only written cycles of 100000 times. If the register 14+15 is in use to set the Preset value it could be that thousands of cycles will be safe in the flash and the lifetime of the encoder decreases significantly. So, we fixed it that it is not possible to save the same preset value for more than one time. The next preset value must be different but can be used in the next but one. I.e. Preset value is 0. Then set in the first time 0, in the second 1, in the next one 0, ...
Q: How to solve physical zero-point problems?
A: You can set only the Preset value. The offset value is only the result.
If you would like to set the encoder position to the half of physical resolution you must do the following steps:
1.Set preset value to a value so that the offset value is zero. 2. Rotate the shaft i.e. to 16777216. 3. Set the Preset value to the wished value.
Q: With which PLC can the encoder work too?
A: SEND/RECEIVE is an easy open protocol, that can be used by different PLC's like Siemens (S7-1200), Hima, ...
Q: What are the minimum sensors update time?
A: The internal sensor updates time amounts ~2 ms. Temporary the update time was between Version 4.2 and 4.5 only 10 ms. But this fast transmission time is only possible with UDP. According to the basic of TCP-IP and the network traffic this product cannot guarantee real time applications.

Q: What masters can cause problems with the Profibus network (bus error, no answer from the encoder)?
A: 1. SIEMENS S5-95U. 2. Master Interface SIEMENS IM 308-B. 3. Softing PROFIboard. 4. Allen Bradley 1785 PFB/B. 4. Mitsubishi A1SJ 71PB92D. 6. Possible cause: The masters do not support the full diagnostic data length (57 bytes).
Q: Why when PLC and master are switched on, bus is active, but there is no answer from the encoder?
A: First, the state of LEDs in the connection cap should be checked (cp. section 6.3). Possibly this can give hints to the cause of the problem. Both LEDs are dark:
Check power supply!
If it is possible the maximum number of diagnostic data per slave should be increased in the master. If this is not possible the encoder can either be used as a „class 1“encoder (diagnostic data length 16 bytes) or one of the manufacturer-specific versions (FRABA 2.1 or 2.2) can be used with reduced diagnostics (cp. 5.1.5).
Use COM PROFIBUS Version 3.3, choose one of the manufacturer-specific FRABA-versions (FRABA 2.1 or 2.2) and activate the reduced diagnostics. If COM PROFIBUS V5.0 is to be used the configuration of the FRABA encoder is only possible with a modified GSD file (slave key „Max_Diag_Data_Len“has to be changed).
Both LEDs are bright: Encoder is ready but receives no configuration or parameter telegrams. Check the address setting in the connection cap. Check the connection of the bus lines (BUS IN / BUS OUT). Check the hardware configuration in your software tool. Red LED bright, green LED flashing: Parameter error! Check parameters, e.g. the rules for setting the total measuring range (cp. 4.1.6)
Q: Is this variant backward compatible?
A: This is always designed to be fully backward compatible with all previous generations.
Q: When replacing the encoder, is needed to change the configuration and settings on the PLC side? It is not necessary to do anything on the PLC side, if the software is well written regarding the preset value. If not, it might be necessary to send a preset command from the PLC, but this depends on the machine software. In this case, please refer to machine manufacturer.

Q: Why doesn’t the neighboring detection work?
A: The encoder supports the LLDP protocol. But it is necessary to use the newest version of Step7, TIA or Simotion Scout. The flag “Device replacement without replacement medium” must be active in the Properties window under General.
Q: In the application we are using a single-turn encoder. Can this be replaced by a multiturn encoder too and what is to be done?
A: There is nothing to do. A multi-turn can substitute a single turn automatically.
Q: How to solve encoder position values freeze?
A: Power the encoder down and up again.
Explanations: Sometimes, when the Step7 HW-Config transmits new configurations to other devices, the encoder can get synchronization problems with the internal timers. As the configuration does not change parameters for the encoder, the PLC doesn't send the configuration to the encoder. That can lead to position value freeze. If the encoder gets a new configuration from HW-Config, then it will work again without problems. After a power cycle, the positon values will be refreshed automatically.
Q: Why can’t I set the preset value or the other parameters?
A: Only if class 3 or 4 is activated is it possible to set the parameters. If necessary, it is important to use class 4 or to activate the class 4 functionalities in the Hardware Manager.
Q: What is the easiest way to set the preset value?
A: Use Telegram 86, 87, 88, 100, 101 or 860. See chapter 3.11.7.2 about Preset setting.
Q: What is the difference between Encoder Profile 4.0 and 4.1?G_XIST1: Position value, left aligned.GSDML: GSDML-V2.2-POSITAL-xxx-20100808MAP Parameter: Must be reconfigured after changing the telegram.G_XIST1: Counter value, right aligned.GSDML: GSDML-V2.2-POSITAL-xxx20110801MAP Parameter: Remain when the telegram is changed.

Q: Round Axis
A: In TWK encoder is no round axis integrated. If the customer sets e.g. number of turns to 24, then the encoder autonomously sets internal next higher 2^n number of turns available in the measuring range. The mismatch to the configured setup in the config tool and encoder will be detected by checksum issues. Explanation of behavior see in the manual on page 44 or chapter 6.1.2 Description of the Absolute Encoder Parameter.
Q: On which resolution velocity calculation is based on?
A: The velocity is always based on the raw value and not on the scaled one and additional always based on 12 bit Single-Turn resolution, even when a 13-bit resolution type as single-turn is used!! For low speed you need to consider linearity of 0.2% per revolution and quantization issue of the resolution. Monitoring of both channels is based on position value and velocity calculated on one of both. Integration time takes a real position value difference at logging time. Each 1 ms a new velocity value is calculated. Example: integration time 1 s. That means the encoder stores 1000 position values and is calculating a position difference between 1 sec.
Q: Why there are Just 0 Values as Process Value?
A: The same behavior as above can be also observed when the wrong device class is selected like TIA instead of NON-TIA from the device type. Please check type label information and selected device type in the project tool.
Q: How to use Profisafe Encoder with Draw Wire?
A: It is strongly not recommended to use a standard Profisafe encoder together with a drawer wire sensor. Root cause for this restriction: The torque needed to drive the encoder shaft is quite high and the spring inside the draw sensor may be blocked. This failure case is not allowed for a safety device.
Q: What is the capability of ABB SM560 safety PLC? This type of PLC just supports 16-bit data safety consistency and NON-TIA version shall be used.


