Regards
Jerry

Jerry,

Thank for your support, but my settup is not as in the manuals. With the settings from the manual I could not get it working. Difference is that in the configuration screen of the measuring input I select 'local measuring' but also in the configuration data in the expert list I have to fill in the log adress (as it should be in for global measuring) On Sinamics level I only set p488 to the measuring input and not 680 of the CU (as for global measuring). Fact is that in my Profibus telegram I have put encoder 3 on the place of encoder 1 (you can only transfer 2 encoders to Simotion, and I don't use Sinamics encoder 1 (motor encoder) in Simotion, but I need Sinamics encoder 3 in Simotion as value for my external encoder object where I have the measuring input).
I only use the non-cyclic enabling of the measuring input (as for local measuring) but the enable is my example connected constantly to a true value, so I can see my countervalue raising whithout explictly acknowledging a handshake.
Question was, will this in fact work correctly towards the measured values, and do I have to fill in the compensation times as for global measuring inputs? Also, if I would define it as global, is that possible, because I have no explicit telegram 391 but one based on it (only the acknowledgebit has been added)?
Change filetype of upload from jpg to rar to unpack it.
Thank You

Difference is that in the configuration screen of the measuring input I select 'local measuring' but also in the configuration data in the expert list I have to fill in the log address (as it should be in for global measuring)

--> HW--Address is not relevant for global measuring inputs

I'm not sure if this would work?!?! alternative: 3rd encoder as PROFIBUS encoder with PROFIdrive

counterMeasuredValue is for "cyclic measuring" and "cyclic measuring" is only for global measuring inputsI guess, that you use cyclic measuring with local measuring inputs --- don't do this!Note (see Manual Output Cams and Measuring Inputs)Cyclic measurement is only possible with global measuring inputs at the inputs TM17 High Feature, SIMOTION D onboard and C240 (B1-B4).

No!

Normally not for local measuring inputsIf measurements have to be performed with "very high" accuracy or the dead times caused by the filter time constant and delay times from the transmission line, BERO, converter, contacts, etc. cannot be ignored, it is recommended a machine-specific determination of the dead times that really occur, through measurements or series of measurements. Measurements with velocitydependent displaced measuring results is anindication the dead times have not been compensated or incorrectly compensated.The procedure for "empirical/metrological determination" of dead times is similar to the procedure for determining the dead times for the output cams (see Output Cam and Measuring Input Function Manual, Chapter "Determining actuation times for output cams (dead time compensation)")

Don't change 39x to free telegram and use global measuring inputs! I you switch to 39x, select with cu.p728 an input, select with cu.p680 an measuring input and then proceed a HW config adjustment, a fastIO config is generated (= internal configuration information that SIMOTION knows, here you have assigned a global measuring input for the drive --- this also works with CUs/CX32)
If you change then to free telegram, global measuring won't work (... or might work until you make a HW adjustment and switch OFF/ON) .If you need additional parameter in the telegram use telegram extension for this!

about telegr. 39x, see FAQ:
http://support.automation.siemens.com/WW/view/de/29063656

Regards
Jerry