TO_speed axis or Sina_Speed????
Created by: IfNotTrueThenFalseElseStupid at: 10/22/2018 11:26 AM (11 Replies)
Rating 
Thanks 2
| 10/22/2018 11:26 AM | |
|
Posts: 15 Rating:
|
Hello I would be grateful for some help regarding best solution for me. Im using a CPU 1512SP F-1 PN communicating with two G120 with CU240E-2 PN. I would like to use the safety integrated function STO "PROFIsafe telegram 30" for both inverters. The two sinamics modules will control different pumps regulation speed depending on pressure in a PID loop. Technology object "speedaxis" or DriveLib "Sina_speed"? Which way is the best? considering im also using the integrated STO Profisafe and constantly regulating the speed/velocity. Kind regards Björn |
| 10/22/2018 1:24 PM | |
Joined: 10/11/2006 Last visit: 3/13/2025 Posts: 5997 Rating:
|
Hello, this is really up to you. There is almost no difference. The only difference is using telegram 1 and SINA_SPEED FB or using technology object and programming with PLC open commands (MC_Power,...). Anyway you can use the PROFIsafe telegram additionally to your standard telegram. By the way: There are ready-to-use safety function blocks to communicate with the safety telegrams: https://support.industry.siemens.com/cs/ww/en/view/109485794 |
|
With best regards, |
|
This contribution was helpful to
|
|
| 10/22/2018 3:13 PM | |
|
Posts: 15 Rating:
|
If i want to reduce cycle time and get the most out of the CPU, which one is the least demanding? Or which one is more operation dependable? I have my PID regulators updating a new output value to my pumps every 100ms. Above that I also have about 8 regulator controlling valves etc. Also i want to expand the telegram to communicate what the pumps are emit in power. Do you know if this is possible? Thank you for a fast reply :) |
| 10/22/2018 3:24 PM | |
|
Joined: 10/11/2006 Last visit: 3/13/2025 Posts: 5997 Rating:
|
Hi, if you want to save performance on the PLC side and want to add additional data to the telegram I would recommend to use the SINA_SPEED block (so no technology object) and add supplementary data to the telegram. This can be read out by system function GETIO(_PART). Please see this post if you are interested on how to program the cyclic communication: https://support.industry.siemens.com/tf/ww/en/posts/telegrams-adaptive/201376/?page=0&pageSize=10 |
|
With best regards, |
|
| 10/22/2018 3:38 PM | |
Joined: 9/21/2012 Last visit: 3/13/2025 Posts: 4324 Rating:
|
Or you can use the internal PID of the G120. |
| 10/22/2018 4:07 PM | |
|
Posts: 15 Rating:
|
Thank you,, but where can I find this telegram library? |
| 10/22/2018 4:15 PM | |
|
Joined: 10/11/2006 Last visit: 3/13/2025 Posts: 5997 Rating:
|
Hello, what are you talking about now exactly? What do you want to do now and what is unclear? |
|
With best regards, |
|
| 10/22/2018 4:28 PM | |
|
Posts: 15 Rating:
|
In your PDF "cyclic communication" it referees to: "Hint: There are system-UDTs with structures of the telegrams (data type: PD_TELx) or predefined UDTs for download in SIOS." But where can i find this? Ive tried to google it and search on siemens website but unable to find it. ? |
| 10/22/2018 4:40 PM | |
|
Joined: 10/11/2006 Last visit: 3/13/2025 Posts: 5997 Rating:
|
Hi, ok, now I know. There are system UDTs available for all telegrams that can be used with any technology object (e.g. Tel 3, 5, 105,...). You will not see them by autocompletion. You need to type them as: PD_TEL3 or PD_TEL105 for example, then you get the telegram structure. There is also an additional telegram library available in SIOS for some telegrams that are not implemented as system UDTs: https://support.industry.siemens.com/cs/ww/en/view/82841762 (in this case you need to copy the UDT from the library to the PLC datatypes and then you can create a variable of this type) But you can also type the structure manually. This is also possible if you do not find the suitable UDT for your application. |
|
With best regards, |
|
This contribution was helpful to
|
|
| 10/22/2018 4:47 PM | |
|
Posts: 15 Rating:
|
Thank you very much :) |
Follow us on