Modifying integration parameters - Metasys - LIT-12013150 - System Integration - Modbus Vendor Integration - 10.1 - 9.0.7

Network Engine Commissioning for Modbus Vendor Integration Application Note

Product
Building Automation Systems > Utilities and Integrations > Modbus Vendor Integration
Document type
Application Note
Document number
LIT-12013150
Version
10.1
9.0.7
Revision date
2021-03-03

About this task

Note: The steps in this section apply to each Modbus integration object. Repeat these steps for each additional Modbus integration object.

Procedure

  1. Use the Launcher to log on to the network engine's SMP. If you need to install the Launcher, refer to Launcher Installation Instructions (LIT-12011783).
  2. Drag the Modbus integration object from the navigation panel to the display panel.
  3. Click the Hardware tab, and then click Edit.
  4. Click the browse button next to Vendor Configuration Data to open the Modify List dialog box. Figure 1 shows the default values for both an RTU and a TCP integration.
    Figure 1. Default parameters in an RTU integration (Left) and TCP integration (Right)

  5. In the Modify List dialog box, modify the default parameters as necessary for your integration. The system automatically saves any changes. See Table 1 for a list of parameter values.
    Table 1. VND integration parameters

    Parameter

    Value

    [1] 1

    Represents the serial communication port.

    [2]1

    Represents the baud rate (1200, 2400, 4800, 9600, 19200, 38400, 76800, or 115200).

    [3]1

    Represents the number of data bits (fixed to 8).

    [4]1

    Represents the parity (N = None, E = Even, O = Odd).

    [5]1

    Represents the number of stop bits (1 or 2).

    [6]1

    Represents the port type. See Table 1 for more information.

    [7]

    Represents whether to capture a log file of the Modbus packet exchanges on the USB drive to display the traffic on an RS-232 communication port on NxE (Y = enable log; N = disable log; A = advanced log, including detailed error descriptions).

    If the parameter is set to Y:
    • For the NCE25, NAE35, NAE45, NAE55, NIE29, NIE39, NIE49, NIE59, diagnostic messages are received and can be captured by the use of a serial terminal program.
    • For the SNE and SNC, diagnostic messages are received and can be captured by the use of a serial terminal program.
    • For the NAE85, log files are captured at the USB port.
      Note: For NAE85s only, if you use a USB drive, insert the drive before you enable log capture, and remove the USB drive after you disable the log.

    [8]

    Represents the communication port that logs Modbus traffic when parameter 7 is set to Y or A. The default port is 0, which means there is no capture to the serial port.

    [9]

    The parameter is not used as the capture to USB is disabled for all models except an NAE85. For NAE85s, this parameter represents the USB drive to which the log file is saved when parameter 7 is set to Y.

    [10]

    Represents the polling strategy. If set to Y, the points are always polled by the driver. If set to N, the points are only polled if requested. This parameter is used to increase communication performance.

    If the parameter is set to N, you must enter an amount of time in the Temporary Status Item Expiration Time field. The Temporary Status Item Expiration Time is the amount of time after which a point is declared not polled. This time must be greater than any other time set for processes or trends. For example, if trends are set to a sample interval of 600 seconds, the Temporary Status Item Expiration Time might be 1000 seconds.

    If the parameter is set to Y, you do not need to specify the Temporary Status Item Expiration Time.

    [11]

    Represents the offline management strategy. If set to Y, a device that does not respond to a Modbus message is declared offline, and no other message is sent to that device until the next polling cycle. When a device is offline, a single message is sent for the configured number of retries. If set to N, all Modbus messages are sent to the device for the configured number of retries, even if it does not respond.

    Note: NAE85 models support only Ethernet TCP communication and do not support RTU.
    Table 2. Serial ports reference for SERIAL communication
    Identifier Available for Connection Port type

    0 2

    All models - None
    1

    All models

    RS-232C (A)

    RS232

    SNExxxxx

    USB-to-RS232 adapter

    RS232

    SNCxxxxx

    USB-to-RS232 adapter

    RS232

    2

    NxE3xxx

    RS-232C (B)

    RS232

    NxE4xxx

    RS-232C (B)

    RS232

    NxE5xxx

    RS-232C (B)

    RS232

    SNExxxxx

    USB-to-RS232 adapter

    RS232

    SNCxxxxx

    USB-to-RS232 adapter

    RS232

    3

    NxE3xxx

    FC Bus

    RS485

    NxE4xxx

    FC Bus

    RS485

    NxE5xxx

    FC Bus A

    RS485

    SNExxxxx

    FC Bus A

    RS485

    SNCxxxxx

    FC Bus

    RS485

    4

    NCE251x 3

    FC Bus

    RS485

    NIE291x3

    FC Bus

    RS485

    NxE55xx

    FC Bus B

    RS485

    SNE2xxxx

    FC Bus B

    RS485

  6. Click OK to close the Modify List dialog box.
1 This parameter is not used in TCP communication.
2 Used to temporarily disable serial communication
3 Only usable when no N2 communication trunk is inserted