Hi
Right now we are working with OPC-UA but we will need to convert to S7+ at some time. Im now trying to estimate the work hours that it will take
I was wondering if I could get some examples of how the adress line for a siemens S7+ tag will actually look like ?, including when the data comes from within a software unit in the PLC
The OPC Item Path for symbolic access ends up looking something like this:
ns=1;s=[S7_1500]PLC.Blocks.Data_block_1.testLINT
ns=1;s=[S7_1500]PLC.Blocks.Data_block_1.testLDT.myInt
not sure what you mean by this, unless you're talking about within a UDT, in which case the 2nd address shows that.
A software unit is a way in a siemens PLC to divide up the program further
each software unit has its own namespace so you can have several blocks with the same name in the PLC, the namespace name thus needs to become a part of the adress
for OPC UA it looks like this:
nsu=http://www.siemens.com/simatic-s7-opcua;s="***NAMESPACE***.DB_ControlModules"."M008StopConditions"."bCmdBypass"
In the example addresses I posted "Data_block_1" is the name of a data block, "testLDT" is the name of a UDT instance.
The beginning "PLC" is the PLC/program name, it would be "PLC_1" for the program in your screenshot.
yes but software units means that there must be something in between them like this:
PLC_1.Unit_1.Blocks.Data_block_1
1 Like
Oh, I see what you mean, I didn't read close enough the first time.
I have no idea if this is supported or what it looks like if it is. We'll have to test it out and get back to you. I've never seen the software units before.
1 Like
We plan to support this with the new driver. We had to update our TIA Portal in order to test this. The current plan is for the item paths to look something like this:
ns=1;s=[1500ss]PLC.Blocks."unit1.Unit_Block".Tag1
ns=1;s=[1500ss]PLC.Blocks."unit2.Unit_Block".Tag1
This is subject to change until we actually release, but this looks promising to me.
3 Likes