104 - Network proof of concept && best practices

10 Posts
5 Users
0 Likes
50 Views
(@j.becker@pcvue.de)
Posts: 0
New Member Guest
 

Hi guys,

I would like to discuss following configuration:
We have one network-card. A lot of 104-devices (350 I think). As we are speaking here about a wind-power-plant per device, the device (plants) belong to different end-customers. So to manage the plant the easiest way per end-customer, we decided to separate the devices into several 104-networks (to start, stop , AA-Architect-templating).

After the customer decided to do the same with Cimway and got problems, because in Cimway one network is also one process (one .exe), I am wondering how it works with the rest of the communication in PcVue, especially with 104.

The help says:
A IEC 60870-5-104 Network object in the Supervisor's configuration, represents and provides access to the physical connection to an IEC 60870-5-104 network.

But more that a Server-List is not configured on network-level.

So should a network really be a "network-card". What does it mean internally in PcVue to run a 104-network? an own communication channel?

Thank you in advance.

 
Posted : 29/11/2016 4:56 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hi Johannes,

I am not really aware of this protocol therefore maybe I will say a mistake.
But I would say 1 Network = 1 independent communication channel (or interface) meaning a different socket.

Nico

 
Posted : 30/11/2016 9:29 am
f.cubattoli
(@f-cubattoliarcinfo-com)
Posts: 167
Reputable Member
 

Hello!

As far as I remember, to "speak" IEC-104, PcVue needs to use 1 socket for each IEC-104 device.

I think the meaning of "network" in PcVue is strongly related to the protocol used (for example in BACnet, 1 network means 1 UDP socket in LISTENING, instead with IEC104 it's PcVue that estabilish the connection with the device using 1 socket for each).

I think in IEC104 the "Network" is only a logical grouping that does not affect the behaviour of the stack layer, but only Cesar or Jacques can confirm.

Hope it helps,

 
Posted : 01/12/2016 7:06 am
(@admin_doc72)
Posts: 493
Member Admin
 

I think the key to answering this question would be to have a clear and common definition of what is a "Communication Channel". I am not sure that everybody is on the same line on that. The term "Communication Channel" is heavily used in the international price list but only mentioned once in the online help.

My understanding is:

  • Cimway: 1 channel = 1 network
  • OPC/OPC XML: 1 channel = unlimited number of servers
  • BACnet: 1 channel = 1 interface (?)
  • LON: 1 channel = 1 network
  • IEC104: 1 channel = unlimited number of networks
  • DNP3: 1 channel = unlimited number of networks
  • IEC61850: n/a
  • SNMP: n/a

Can anybody help to complete the table?

 
Posted : 01/12/2016 2:18 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

What I know. In the Sales point of view, 1 Communication channel = 1 Protocol.

In technical point of view

Cimway: 1 channel = 1 network
[NICO] YES

OPC/OPC XML: 1 channel = unlimited number of servers
[NICO] YES

BACnet: 1 channel = 1 interface (?)
[NICO] NO. Today you can have only 1 interface but this is a technical issue. That's why, on a BACnet architecture we can't have 1 StandBy server for more than 1 Association.
Soon we will be able having "unlimited" interfaces.

LON: 1 channel = 1 network
[NICO] NO. 1 channel = unlimited number of networks

IEC104: 1 channel = unlimited number of networks
DNP3: 1 channel = unlimited number of networks

IEC61850: n/a
[NICO] NO. 1 channel = unlimited number of networks

SNMP: n/a
[NICO] I don't know ...

 
Posted : 01/12/2016 3:02 pm
f.martin
(@f-martinarcinfo-com)
Posts: 148
Member Admin
 

Here is the answer from Alain Faisant regarding the sales aspect:

* Cimway: 1 "Generic channel" per network
* OPC/OPC XML: Supposed to be 1 "Generic channel", but not sure that it is correctly checked by PcVue
* BACnet: "Dedicated channel"
* LON: Supposed to be 1 "Generic channel", but not sure that it is correctly checked by PcVue
* IEC104: "Dedicated channel"
* DNP3: "Dedicated channel"
* IEC61850: "Dedicated channel"
* SNMP: "Dedicated channel"

For the technical aspects (how many threads, sockets, ... per network, device, ...), as Filippo already said it, you have to ask the developper (and share the answer).

 
Posted : 02/12/2016 4:35 pm
(@admin_doc72)
Posts: 493
Member Admin
 

Thanks, Florent.

I think it could be worth putting that table into a dedicated thread.

 
Posted : 02/12/2016 6:38 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hmmm somebody knows the difference between "Generic channel" and "Dedicated channel" ?

Nico

 
Posted : 06/12/2016 10:46 am
f.martin
(@f-martinarcinfo-com)
Posts: 148
Member Admin
 

It's easy, just have a look into the intranet, in the license information, the Data Acquisition Drivers panel:
- Dedicated Channel = Named options (SNMP, BACnet, IEC61850, IEC104, DNP3, KNX, LON)
- Generic Channel = Comm Channels (Cimway, OPC, DDE, ...)

 
Posted : 06/12/2016 2:10 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

hehe thank you Florent but it was not really the sense of my question.
Apart the wording what is the difference in PcVue? Even theoriticaly (I mean if the expected treatment is not done...)

 
Posted : 06/12/2016 2:19 pm