9/20/2019 4:03 PM | |
Joined: 5/6/2019 Last visit: 9/18/2024 Posts: 78 Rating: (0) |
Hallo, This is about the standard telegram 5, status word byte order. I am running Sinamics S120 CU310 2PN with PLC -S7 1500 and using TIA 15 . I wanted to check the different STOP behaviour when running above the speed limit as given in SLS. I am using Starter for the configuration of Sinamics drive. As I understand (https://support.industry.siemens.com/cs/ww/en/view/51677403- section 6.13 under safety faults), for Stop C, when the speed is above the limit and when the safety is activated, the control request and the ramp down will be done by the drive. In my test scenario, I control the motor using the PLC, increased the speed above the limit in SLS , make the safety for SLS active. As expected, the velocity ramp down. I wanted to check the bit in the status word which tells who takes the control. As seen in the attached document I had configured address I17 for standard telegram. The I17 word changes from EF37 -EF33- EB33 - AB33 - AF33 -AF60 - AF40- AB40 - EB40. I wanted to know which bit corresponds to bit 9 in this word. Bit 9 gives the control requested information https://support.industry.siemens.com/cs/ww/en/view/99472695 pg 437. As per the watch window, when I took I17.1 - it gives the name "Control Requested". It adds more confusion. Please clarify. AttachmentTeleggram5_Status Word.pdf (537 Downloads) |
Last edited by: The Helping Hand at: 09/23/2019 17:01:33Optimized Links. |
|
9/20/2019 5:19 PM | |
Joined: 7/7/2010 Last visit: 9/23/2024 Posts: 15217 Rating: (2417) |
If the device operates according to profinet guidelines, I believe you can access bit 9 of the telegram 5 status word like this: CU310-2PN_StatusWord.%X9 where CU310-2PN_StatusWord is I17? Why an odd number? That's truly odd. Words for telegrams should be set on an even word boundary, like I16 or I18.
|
science guy |
|
9/23/2019 1:08 PM | |
Joined: 5/6/2019 Last visit: 9/18/2024 Posts: 78 Rating: (0) |
Thank you for the reply. I changed the address for standard telegram to even number I18. I didnt find a major change in the problems that I have. The default naming that comes from PLC is still 18.1 for ControlRequested bit, whereas I expect this to come at 19.1 . Please check my attached document. This was my understanding. Attachmentbyteorder.pdf (543 Downloads) |
9/23/2019 1:26 PM | |
Joined: 2/24/2015 Last visit: 1/25/2023 Posts: 306 Rating: (77) |
This is not due to Profibus telegrams, but to the fact that different systems can use different byte orders (Little endian / Big endian). |
Follow us on