NMT_REQUEST

NMT_REQUEST stands for “Network Management (NMT) Request” in the context of the CANopen (Controller Area Network Open) protocol. NMT is a part of the CANopen communication profile that is used for network management tasks, such as starting, stopping, and resetting nodes on the CANopen network.

NMT_REQUEST refers to a type of CANopen message that is used to send network management commands from one node (e.g., a master device) to another node (e.g., a slave device) on the CANopen network. These commands are used to control the state and behavior of the nodes in the network.

The NMT_REQUEST message typically contains information such as the command code, node ID of the target node, and additional data (if required) to specify the desired network management action.

Inputs

INTERFACE_ID: This input represents the identifier of the interface used in the CANopen network. In CANopen protocol, systems that use multiple interfaces can specify which interface to operate on using the INTERFACE_ID input.

NODE_ID: This input represents the identifier of the target node. In CANopen network, each device (sensor, actuator, controller, etc.) has a unique identifier, and the NODE_ID input determines which node the network management command will be directed to.

CMD: This input represents the network management command to be executed. For example, commands such as “Start Node”, “Stop Node”, “Reset Node” can be specified using the CMD input.

TIME_INTERVAL: This input represents a time-related parameter and can be used for waiting or timing purposes for a specific duration. For example, if the network management command needs to be sent after a certain time interval, the TIME_INTERVAL input can be used to specify that time interval.

EVENT_INPUT: This input represents the status of an object or an event. For example, in case of detecting an error condition or when an event occurs, the EVENT_INPUT input can be triggered and used to initiate the appropriate network management command.

Outputs

ERROR: This output represents the error condition of the function block. For example, in case of incorrect input or communication error, the ERROR output may become active.

STATE: This output represents the current state of the function block. For example, in case of successful completion of a network management command, the STATE output may represent a specific state such as “Started”, “Stopped”, or “Reset”.