All -
This post is a request for general insight and previous experience.
I have a handful of drives I am interfacing to the latest version of DeltaV. The system will be communicating over Profibus DP using the DeltaV S-Series Profibus Master module. I will not have the complete system setup in front of me for a few months and want to get a head start on the configuration in explorer as well as the control module generation. Here are some notes on the setup. Please let me know if you have interfaced drives via Profibus in the past and would be willing to share insights.
1. Siemens G120 drives via Profibus DP. I have loaded the latest GSD files.
2. All control is via Profibus DP (no hardwired I/O or control). Plan to use Telegram 353 and "extend" the PZD variables to additionally include things like voltage, power, and other measurement variables and diagnostics. Any knowledge or experience with extending the telegram would be helpful. This understanding is admittedly more on the Siemens side.
3. I would like to implement the ability to change drive parameters from the Operate screens. This would likely require the PKW portion of the telegram. Any experience would be helpful.
4. I am also open to any contribution on how other users have structured their control modules to interact with a PID function. Typically when we set up PID control of a traditional control valve, we will place the AO block inside the same control module of the PID. I am thinking it would be beneficial to contain all of the drive control in a separate block due to the complexity of the communication and information coming back. Just want to get some comments and experiences if anyone has any.
Thanks, Brian
"2. All control is via Profibus DP (no hardwired I/O or control). Plan to use Telegram 353 and "extend" the PZD variables to additionally include things like voltage, power, and other measurement variables and diagnostics. Any knowledge or experience with extending the telegram would be helpful. This understanding is admittedly more on the Siemens side."
Should be no problem if you have assigned the correct interaface lenght and type. Just read and write the values...
If you would have siemene then you would see the different values in different places in the interafce DB.
"3. I would like to implement the ability to change drive parameters from the Operate screens. This would likely require the PKW portion of the telegram. Any experience would be helpful."
There is a document about that "MICROMASTER 4 (MM4), SINAMICS G120 (CU240S/D, DP/DP-F, PN/PN-F): Essentials for PROFIBUS and PKW-mechanism." ID: 8894584
(http://support.automation.siemens.com.edgekey.net/AR/llisapi.dll?certcountryid=0&certid=0&certofficeid=0&certtypeid=0&func=ll&idx0=M&nav0=index&nodeid0=10804924&objid=15274241&prodLstObjId=15274241&subtype=133000&lang=en&siteid=cseus&aktprim=0&objaction=csviewmlfbbeitraege&extranet=standard&viewreg=AR&display=p)
It´s tricky to change the parameters in runtime, Siemens have blocks in S7, so you have to make your own....
Niklas Flykt
Klinkmann Oy
Key Account Manager safety products
nikfly@gmail.com
In reply to Niklas Flykt:
Niklas -
Thanks for the response. I am running into one small gap in my understanding.
Let's say I am using Telegram 353 w/ PKW 4/4 and PZD 2/2 as a basis. When you configure the Profibus module in DeltaV explorer, you have the option to configure Profibus Signals based on their length, input/output, byte offset, etc.
Would you expect the PKW signals to take up bytes 0 through 3 and the PZD signals would be offset 4 and 6 respectively? I can provide screenshots if this will help.
Regards,
In reply to Brian Zakrajsek:
"Would you expect the PKW signals to take up bytes 0 through 3 and the PZD signals would be offset 4 and 6 respectively? I can provide screenshots if this will "
No i would expect to see WORD:s 16 bits, the slots have to exactly match the ones in the G120.
You can see how they are divided into groups.
http://cache.automation.siemens.com/dnl/TI/TI0MjIwNwAA_45287261_Tools/45287261_G120_STD_APP2_en.pdf see page 27
read this document: http://cache.automation.siemens.com/dnl/DQ/DQ4OTExAAAA_22078757_Tools/22078757_Function_block_to_control_MM4_via_PROFIBUS_DP_DOCU_v3_2_en.pdf page 127
Read the latest manual on your control unit and get the right GSD file (latest) otherwise you might get some problems.
Can´t remember if you already can use a 32 bit reference in Profibus ...?
You could also check the Control techniques standard blocks that are included in DV 11.3 (CMNDR-SK-DNET )