Network settings
Network settings section describes the main settings of the node into network and how it is controlled by master
(*) This option is not always available(**) Generic slave configuration only
| Field | Description | Default value |
| Static Node Number | Univoque network node id is assigned to current slave in static way.Allowed values: 1 to 127.This number must be unique in the network. | Default value: 1 |
| Parametric Node Number (*) | Node number is specified at runtime.Define in your project an USINT PLC variable and bind in Node Number Var (USINT) box. | The value in the variable at PLC startup (1 to 127) will be used as current slave node id. |
| Node Guard Period (ms) | Enter a value > 0 to use node guarding as network control protocol (this requires Life time Factor > 0 too).Using this kind of configuration master sends a 0x700+$NODEID RTR message every Node Guard Period (ms) to slave node to get slave status.If 0 value is specified node guarding is not configured for this node. | Default value: 200 |
| Life time Factor | Enter a value > 0 to use node guarding as network control protocol (this requires Node Guard Period (ms) > 0 too).If master has no node guarding answer from slave node for Life time Factor consecutive times, master set node to missing status. If 0 value is specified node guarding is not configured for this node. | Default value: 3 |
| Boot time elapsed (ms) | At startup parametrization phase master sends NMT reset command to slave node.Slave node can take some time to reboot and be able to reply master requests.This is the time to wait for slave bootup. If slave is not booted up after this amount of time is considered missing. | Default value: 10000 |
| Wait boot-up message (**) | Bootup message should be sent by slave after each reboot by CANopen standard.If flag is checked, master notice that slave is online on the network when receive its bootup message. Some old/not CANopen standard compliant slaves do not send bootup message.In this case master polls the device id (0x1000.0) object until receive an answer from the slave (or specified boot time is elapsed and node is considered missing). | Default value: checked |
| Node heartbeat producer time (ms) | Heartbeat can be used as network control protocol.To use heartbeat instead of node guarding set Node Guard Period (ms) = 0 and Life time Factor = 0.This setting is mandatory to enable heartbeat network control protocol.N.B.: the other mandatory configuration to use heartbeat network control protocol is to configure Master heartbeat consumer time (ms) with a value greater than t.Enter a ms value t > 0 into thisfield. The slave will send an heartbeat message with its status to the master every t ms. | Default value: 0No heartbeat control protocol configured |
| Node heartbeat consumer time (ms) | This setting can be used by slave to detect master loss.To use heartbeat instead of node guarding set Node Guard Period (ms) = 0 and Life time Factor = 0.It is not mandatory for master configuration, can be left set to 0. To enable this feature put a value that is greater than master Heartbeat time (ms).N.B.: master Heartbeat time (ms) must be set greater than 0. | Default value: 0No heartbeat control protocol configured |
| Master heartbeat consumer time (ms) | Heartbeat can be used as network control protocol.To use heartbeat instead of node guarding set Node Guard Period (ms) = 0 and Life time Factor = 0.Node heartbeat producer time (ms) must be set with a value greater than 0.This setting is mandatory to enable heartbeat network control protocol.Enter a ms value t > 0 into thisfield. Master is expecting to receive an heartbeat message from current slave with its status every t ms.N.B.: this value must be set greater than Node heartbeat producer time (ms). | Default value: 0No heartbeat control protocol configured |
| Mandatory | This flag is used to configure the master behavior in case of slave missing or slave loss.Not mandatory slave, slave not available on the network at startup. Master configures other available nodes and enter operational.Not mandatory slave, slave available on the network at startup. Slave is lost after some time. Master detect slave loss. Master continues in operational states with other active nodes.Mandatory slave, slave not available on the network at startup. Master detect that mandatory slave is not available. Network configuration aborted. Master does not enter operational.Mandatory slave, slave available on the network at startup. Slave is lost after some time. Master detect that mandatory slave is no more available. Entire network is stopped. | Defaul value: unchecked Not mandatory slave |
| Identity Object Check (**) | It is possible to read from slave standard identity objects.Master can ask to slave these informations and check the values returned are the expected ones.If checked Device Info box is shown. Otherwise is hiddened. | Defaul value: uncheckedNo Device Info information are retrieved |