SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Profinet encoder telegram 81

1/25/2022 11:14 PM	Rate (0)
DavidBrown Posts: 975 Rating: (9)	I have a Sick Profinet encoder , absolute multiturn AFM60A-S1NB018x12. The IO interface of the encoder is of telegram 81 type. The encoder is Profinet RT, not IRT. In my plc I want to use the encoder as an external encoder TO-object. As the encoder is not IRT, but RT I suppose I will have to use a datablock connection to the encoder, I mean I cannot connect the encoder directly to the external encoder object, but only by using a datablock based on telegram 81. In the preinterpolator task I copied the IO-part of telegram 81 in and out to and from the datablock. However I do not see any position values apear already in the datablock and the external encode object. What els do I have to do to see actual position values from the encoder? Or what bits in the telegram do I have to set?
DavidBrown Posts: 975 Rating: (9)
Suggestion To thank Quote Answer

1/26/2022 11:09 AM	Rate (0)
daviso Bronze Member Joined: 11/4/2011 Last visit: 12/22/2025 Posts: 279 Rating: (29)	Hi, at the moment I do not really see the need to do the DB connection. If your encoder really provides PROFIdrive telegram 81, you should be able to connect the TO directly to the encoder. It does not matter if the encoder is used with RT or RT for connecting the TO to this, IRT would only bring the deterministic timing to the communication, but nothing more. But if you're doing the TO to DB connection, then using OB MC-PreInterpolator to provide the IO data to the DB (and vice versa) is the wrong way. You need to use OB MC-PreServo to read the input data and provide them to the DB, and OB MC-PostServo to provide the output data from the DB to the encoder (or more precise: from the DB to the process image of the outputs, which is then written to the device automatically after OB MC-PostServo is processed, if you assigned the encoder correctly to process image part of MC-Servo OB). Regards, daviso

Suggestion To thank Quote Answer

1/26/2022 12:12 PM	Rate (0)
DavidBrown Posts: 975 Rating: (9)	Ok about the MC postservo for writing data to the encoder. But for data from the encoder can I not use preinterpolator as well as preservo? I tried to connect the encoder directly to the external encoder TO, but it gave 'configuration error'.
DavidBrown Posts: 975 Rating: (9)
Suggestion To thank Quote Answer

1/26/2022 12:34 PM	Rate (0)
daviso Bronze Member Joined: 11/4/2011 Last visit: 12/22/2025 Posts: 279 Rating: (29)	No, MC-PreServo is the right OB for processing the input data from the encoder to the DB. What configuration error did you have? Which error number and which error text was shown in the diagnostic buffer? Regards, daviso

Suggestion To thank Quote Answer

1/29/2022 4:16 PM	Rate (0)
Marko Bursic Posts: 1410 Rating: (154)	https://cdn.sick.com/media/docs/9/99/099/operating_instructions_afs_afm60_profinet_absolute_encoder_en_im0047099.pdf instructions for TO_ExternalEncoder Attachment operating_instructions_afs_afm60_profinet_absolute_encoder_en_im0047099.pdf (1852 Downloads)
Marko Bursic Posts: 1410 Rating: (154)	Last edited by: Jen_Moderator at: 01/31/2022 10:35:32 Added PDF as an attachment.
Suggestion To thank Quote Answer

Share this page:

Share this page on...