Sinamics DCM telegram 352 offset problem for PZD 3-6

Good afternoon, dear experts!

We have a configuration with one CPU 314 2DP and Sinamics DCM 6RA8025-6DV62-0AA0. We need to connect them via Profibus DP. The task is to receive some extra data from the Sinamics DCM comparing to the Standard Telegram 1 PZD-2/2, so we have chosen telegram 352 PZD-6/6. Telegram 1 PZD-2/2 functioned OK, and we both successfully sent control word and setpoint and received status word and speed. But after changing to the telegram 352 PZD-6/6 a problem occurred. We still can send and receive PZD1 and PZD2, but we are unable to do that with PZD3-6. Our analysis of the situation showed that the problem is in the source and offset (see attached screenshots) of the PZD3-6 of the telegram 352. They are equaled to 65535 instead of M for the source and 4 to 10 for the offset. The same problem is for the bus address PZD receive (r2074). It is equaled to one for the PZD1-2 and 65535 - for the PZD3-6. All parameters in the Starter Expert list, which are responsible for this (r2074, r2075), are read-only. The question is how to change the sources and offsets for the PZD3-6? Thank you very much.

Best regards,

Vladislav Petrov.

Hello.

Have you changed telegram configuration also in HWConfig of CPU314?

Dear KSN,

Yes, we have changed the configuration of the telegrams in HWConfig of CPU314 (see attached screenshots - page 1). We even tried another configuration in this config (see attached screenshots - page 2). But everything was in vain.

Best regards,

Vladislav Petrov.

In Starter you have configured telegrams for two drive objects:

1. Drive - PZD 6/6

2. CU - PZD 2/2

You should make the same configuration in HWConfig. Look at screens.

Or you should select zero telegram lengths in Starter for CU.

Dear KSN,

        We are sincerely thankful for your advice. It was really useful, and we solved the problem. Thank you again.

Best regards,

Vladislav Petrov.