Main Scenario; Alternative Scenario: Control, Maintenance, Supervision - Scaime eNod4-F ETHERNET Software User Manual

o Set IP (remanent or not). Allows the assignment of IP parameters (IP address, subnet mask, default
gateway) for a node. Remanent means that parameters will keep their values after a power cycle, in
non-remanent that they will be recovered to their previous values.
o Set Name Of Station (remanent or not). Allows the allocation of the name of the station for a node.
Used in remanent, this service disables the option "use rotary switches for name of the station"; to
reactivate it you can use eNodView.
o Set Reset Factory Settings: Allows the reset of all settings (application and networks) from eNod4 to
their default values. It places the IP settings to (0.0.0.0, 0.0.0.0, 0.0.0.0), turns the current name of
the station into an empty field and disables the option to use rotary switches for name of the
station.
RPC (Remote Procedure Call): Allows the management of connections (called AR (Application relation) and
-
CR (Communication relation)) for the exchange of cyclic data (IO Data) between the IO-Controller (PLC) and
the Device-IO (eNod4). Allows also acyclic exchanges (called read/write Records).
- Profinet IO Data: Cyclic PROFINET IO data, these carrying data also contain status informations on the
transported data. Compared with other communication standards based on Ethernet, useful cyclic data goes
through fewer layers before reaching their destination. For example the IP network layer is not crossed by
cyclic data (IO Data).
Alarms: PROFINET IO alarms are sent by a node whenever a significant event occurs. eNod4 sends an alarm on
-
every appearance and disappearance of diagnostic that reports an application error. Error types
corresponding to eNod4 diagnostics are described in the appendix and in the GSDML file. This file can be
imported into the engineering software used for the network monitoring.
MRP (Media Redundancy Protocol): This Protocol allows ring topology. eNod4 acts as a MRP client and is not
-
able to act as manager. At least one manager (MRP Manager) is required on the network if the ring topology
is desired.

7.4 Main scenario

The main scenario applies to PROFINET IO network; it can be used to diagnose possibly encountered problems on the
network.
1. PROFINET IO network is powered on.
2. IO-Devices emit LLDP frames to inform all nodes on the subnet of their presence and identity.
3. Network nodes resolve the IP addresses of the stations with which they wish to communicate in
peer-to-peer using the ARP protocol.
4. With DCP services, IO-Controller identifies IO-Devices involved in its application. It configures
their IP settings. ARP tables are updated consequently.
5. Using RPC, the IO-Controller opens and configures cyclic connections (AR) for data exchange
with IO-Devices and if needed reads and writes application parameters.
6. Cyclic data exchanges begin between IO-Devices and the IO-Controller in both directions.
7. The application of IO-Controller operates with the data provided by IO-Devices and supplies
data to IO-Devices to advance the process of the application.

7.5 Alternative scenario: control, maintenance, supervision

On point 4 of the main scenario:
4 A. If the network manager wants to control, maintain or supervise the network
4. A.1. The network manager Ping the eNod4.
4. A.2. The network manager consults the network information base of the eNod4 with
SNMP V1.
32/113
User manual SCAIME:
NU-Soft-eNod4F-ETH-E-0716_235709-C.doc