FAQ

1.
Q: Why don’t I get back position values in G1_XIST2 (Telegram 81-84)?
A: According to the encoder profile it is necessary to set Bit 10 to “1” in STW2 and Bit 13 in G1_STW1. See the next hardcopy. Or an error is given and is not confirmed.

2.
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.

3.
Q: What is to do if one encoder must be replaced by a new one?
A: See answer 2 or set the device name according to chapter 6.3.

4.
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.

5.
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.

6.
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.

7.
Q: When using the D410 the error “Synchronization error between Profibus and Profinet” popped up. What can we do?
A: Both systems have to use the same cycle time. If the Profinet cycle time is 1ms then Profibus must use the same one. See the next screenshot for 1ms settings.

8.
Q: What is the difference between Encoder Profile 4.0 and 4.1?
A:
Profile 4.0.
G_XIST1: Position value, left aligned.
GSDML: GSDML-V2.2-POSITAL-xxx-20100808
MAP Parameter: Must be reconfigured after changing the telegram.

Profile 4.1.
G_XIST1: Counter value, right aligned.
GSDML: GSDML-V2.2-POSITAL-xxx20110801
MAP Parameter: Remain when the telegram is changed.

9.
Q: What is the difference between Encoder Profile 4.1 and 4.2?
A:

10.
Q: How to solve position jump after power-up?
A: If the encoder is according to the type of label i.e. 1216 for revolution and resolution then it is important to use in Encoder profile 4.1 the related DAP and not i.e. the DAP 1213.

11.
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.

12.
Q: Which PLCs work with our Profinet encoders?
A: Normally all PLCs that support Profinet IO. If you want to use IRT, then make sure your PLC supports Profinet V2.2 version or higher. Here are some known PLCs that are proven to have worked with our encoders: S7-31x PN, S7-1200, D410 PN, D445 PN. 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 get a new configuration from HW-Config, then it will work again without problems. After a power cycle, the position values will be refreshed automatically.

13.
Q: Why doesn't the Posital BOOT/P Configuration Tool find my Profinet encoder?
A: The tool must be working in the same IP address range as the encoder.

Note: If the encoder IP address is set as 0.0.0.0, then the encoder uses 192.168.0.253.

14.
Q: Is Telegram 860 isochronous and works class 3 or 4?
A: Yes, it is isochronous. But since it does not integrate control bits there is no Sign-of-Life functionality available.

15.
Q: How to do the configuration of IRT on a Beckhoff PLC?
A: In any case, the current status is that Beckhoff Profinet PLC is IRT-capable.

This function is then also available in the encoder route under OCD encoder - API - Subterm1 with the text: Autoconfig IRT TOP. The port on the EL6632 terminal with which the encoder exchanges data and the cable length to the encoder must then be defined in subterm 2.

When the application is then activated, all participants run in OP (operation mode) and the PnBoxDiag displays 2 as hoped. The encoder and the terminal are then in good status.

16.
Q: Does the encoder support MRP (Media Redundancy Protocol)?
A: Yes, our new generation (EIC1B) supports MRP. However, the former versions (EIB1B and EIA1B) do not.

17.
Q: What can cause problems with Device Name in the application?
A: The Device Names must be identical in encoder properties and "Assign device name" under Edit Ethernet Node. Details are available in the manual.

18.
Q: What are the differences between Step 7 V5.5 and V11 (TIA Portal)?
A: In principle, all PLCs without Simotion versions support both. The function blocks are replaced with names. But the functionalities should be the same.
Here are the links to German and other languages: View

19.
Q: When is the round axis enabled?
A: Whenever the scaling function is enabled and the multiturn resolution is not set as a binary value.

20.
Q: Sometimes the IP address and Device Name will be lost after a power up. What to do?
A:

• Check if the flag "Assign IP address via IO controller" is set (see manual page 31)

• Under Edit Ethernet Node it is possible to reset the encoder to manufacturer settings (see manual page 32). After this the IP address and Device Name should appear again.

• Check during configuration if the IP address and Device Name were sucessfully set. Specifically, if you try to use the same IP address or Device Name, you should get an error message.

• Set back the PLC IP address to the old one, set the the encoder back to factory setting - see FAQ 12.

• Download our tool OCD-IpConfig1V4.exe (in Tools, under Downloads, on the product page) and set the IP address to 0.0.0.0.

• Preset to 0

• Preset to another value (<>0)

• If using Simotion Scout, it is the easiest solution for these telegrams (simpler program)

• If using TIA Portal, it gets a bit more complicated.

• Increments per revolution and Number of revolutions: according to your encoder

• Fine resolution set to 0 (see the screenshot)