Hello,
My WinCC_OA is OPC UA server. when I publish datapoint on OPC UA, and read it from an OPC client (ex: UA expert), the namespace structure looks the following:
DPT.DP.DPE
I would like to get rid of the DPT part and publish only DP.DPE on OPC UA server namespace.....but
1) without using CNS
2) without using DP aliases
Thanks in advance for your help,
Cheers,
Lionel.
OPC UA namespace structure Vs Datapoint Structure
- lwallet
- Posts:19
- Joined: Mon Oct 23, 2017 3:50 pm
OPC UA namespace structure Vs Datapoint Structure
- RudiKreiner
- Posts:198
- Joined: Mon May 16, 2011 2:10 pm
Re: OPC UA namespace structure Vs Datapoint Structure
We wanted to do the same thing, but the only way that we found to do it was to use the DP aliases, but it looks like you don't want to do that for some reason.
I don't understand why ETM implemented it this way because DP.DPE is a sufficient and unique definition.
If it a problem not only for us, then maybe they could consider creating a config setting to switch to that definition.
That would put the choice into the user's hands, and not occupy the aliases which may be used for something else.
If the only reason is that you fear the work involved, it really is not that difficult.
You just need to add this entry to the OPC UA server section of your config file
nodeIdType = 1
and run an initialization script to set the aliases to the dp names like this:
main()
{
dyn_string dps:
dpGet(dps, "_DpGroup00014_Public.");
set_aliases(dps);
dpGet(dps, "_DpGroup00015_Public.");
set_aliases(dps);
}
void set_aliases(dyn_string dps)
{
for (int i = 1; i
I don't understand why ETM implemented it this way because DP.DPE is a sufficient and unique definition.
If it a problem not only for us, then maybe they could consider creating a config setting to switch to that definition.
That would put the choice into the user's hands, and not occupy the aliases which may be used for something else.
If the only reason is that you fear the work involved, it really is not that difficult.
You just need to add this entry to the OPC UA server section of your config file
nodeIdType = 1
and run an initialization script to set the aliases to the dp names like this:
main()
{
dyn_string dps:
dpGet(dps, "_DpGroup00014_Public.");
set_aliases(dps);
dpGet(dps, "_DpGroup00015_Public.");
set_aliases(dps);
}
void set_aliases(dyn_string dps)
{
for (int i = 1; i
- lwallet
- Posts:19
- Joined: Mon Oct 23, 2017 3:50 pm
Re: OPC UA namespace structure Vs Datapoint Structure
Thanks Rudi,
Yes, as you mentionned, "DP.DPE" is unique, so, there is not need to add the DPT in the OPC UA namespace!
Many thanks for the proposed workaround, but I guess this is not the purpose of using Aliases. Well, at least I would like to use Aliases for other purposes....and using CNS is really a pain!
I thought it would have a config entry to remove the "DPT" prefix, but I did not find anything like this...As you suggest, it sounds good to add it in the possible [opcuasrv] entries. I would make users life simpler!
Thanks again for the comments,
Cheers,
Lionel.
Yes, as you mentionned, "DP.DPE" is unique, so, there is not need to add the DPT in the OPC UA namespace!
Many thanks for the proposed workaround, but I guess this is not the purpose of using Aliases. Well, at least I would like to use Aliases for other purposes....and using CNS is really a pain!
I thought it would have a config entry to remove the "DPT" prefix, but I did not find anything like this...As you suggest, it sounds good to add it in the possible [opcuasrv] entries. I would make users life simpler!
Thanks again for the comments,
Cheers,
Lionel.
- alug
- Posts:42
- Joined: Mon Oct 18, 2010 11:00 am
Re: OPC UA namespace structure Vs Datapoint Structure
Hallo,
our intention was that we want to have the same same via OPC UA as in WinCC OA PARA.
The old OPC DA has the config entry to read the same, because old OPC DA was different from the beginning.
It would be no big deal to make the config Entry working also for OPC UA and truncate the DPT
if set accordingly.
Can you send this issue with a description why you need it to the product center
Than we can care about it
best regards
Andreas
our intention was that we want to have the same same via OPC UA as in WinCC OA PARA.
The old OPC DA has the config entry to read the same, because old OPC DA was different from the beginning.
It would be no big deal to make the config Entry working also for OPC UA and truncate the DPT
if set accordingly.
Can you send this issue with a description why you need it to the product center
Than we can care about it
best regards
Andreas