The Distributed Control System reference design is a hardware and software platform for developing HART-enabled analog input and output modules (or nodes). DCS Modules are assembled from several existing reference designs:

• EVAL-ADICUP3029 is the processor board that implements a MODBUS slave and controls the analog input / output boards.
• EVAL-CN0416-ARDZ provides robust RS485 connectivity between one or more nodes and a host computer
• EVAL-CN0414-ARDZ provides four group-isolated voltage inputs and four HART enabled current inputs.
• EVAL-CN0418-ARDZ provides four group-isolated voltage or HART-enabled current outputs

The reference design provides software connectivity using the MODBUS protocol. Modbus is a ubiquitous, open, industrial communication protocol for which there are numerous open-source and commercial software libraries and utilities. It is a serial master-slave protocol where the master uses a set of standard commands to read and write registers on the slave device, and CRC error detection ensures data integrity. Reading a slave register can give information about the state and inputs of the slave and writing registers can change the state or outputs of the slave. The mapping of Modbus registers to application-specific functions is dependent on the end application, and the DCS reference design provides convenient access to all of the functionality of the analog input and output boards.

Several options for communicating with the hardware are provided or demonstrated:

• A command-line interface, requiring only a terminal program on the host PC and no additional software, useful for initial board bringup and debug.
• An open-source Modbus debug tool
• A set of command-line utilities (Windows only)
• Example applications in Python, using an open-source Modbus library

The following is a list of items needed in order to replicate this demo.

• Hardware
  • EVAL-ADICUP3029
  • EVAL-CN0414-ARDZ and/or EVAL-CN0418-ARDZ, up to 4 boards total, in any configuration
  • EVAL-CN0416-ARDZ (not needed for direct USB connection to a single node)
  • Additional EVAL-CN0416-ARDZ, ADALM-UARTJTAG, and 2×5, 100mil cable such as AMP A3AAH-1006G or:
    • other RS485 host adapter
  • Mirco USB to USB cable
  • PC or Laptop with a USB port
• Software
  • ADuCM3029_demo_cn0435 demo application
  • CrossCore Embedded Studio (2.8.0 or higher)
  • ADuCM302x DFP (3.2.0 or higher)
  • ADICUP3029 BSP (1.1.0 or higher)
  • Serial Terminal Program (Required for running in CLI mode only)
    • Such as Putty or Tera Term
  • Python 3.6 (only required for modifying example applications)

Block diagrams for PLC / single-node DCS and multi-node DCS systems are shown below. These systems differ slightly in their allowable configurations:

• A Single-node system can operate with either half-duplex or full-duplex RS-485. Termination must be enabled at both ends of the RS-485 line(s).
• Modbus address conflict is not a concern in a single-node system (but the address must be known to the host.)
• A Multi-node system can only operate in half-duplex mode.
• In a Multi-node system, termination must be enabled at the ends of the RS-485 line, which is most often the host RS485 adapter and most distant node.
• Each node in a multi-node system must be set to a different address.

An ADALM-UARTJTAG board and a spare CN0416 can function as a convenient USB Virtual COM port to RS-485 adapter. Any RS485 adapter should work, if another is available. Isolated / Non-Isolated depends on the application and difference in ground potential between the host and nodes. Full-duplex operation is only supported in the PLC/single-node DCS configuration, as both TX and RX signals are driven continuously. Both single-node and multi-node configurations can use half-duplex.

The CP2103 device must be programmed as follows to control the DE signal on the CN0416. Configure Silicon Labs Xpress Configurator as follows to program the device:

Once the CP2103 is programmed, unplug from the host computer and connect P1 on the ADALM-UARTJTAG to P11 on the CN0416 with a 2×5-socket, 100mil cable such as AMP A3AAH-1006G. Be sure to connect with proper polarity - pin 1 on the ADALM-UARTJTAG must correspond to pin 1 on the CN0416.

Configuration for each node is similar, noting that each node must be set to a different address (via S1 on the CN0416) and the most distant node must have its termination enabled (via S6 or S7 on CN0416.)

(Full-duplex only valid in a single-node system.)

The CLI program does not need the EVAL-CN0416-ARDZ board and is not affected by it's presence either. Furthermore, the PLC/ single-node DCS configuration can also operate with a direct connection, useful for testing out individual nodes quickly.

There are four types of standard registers in the MODBUS slave:

Each of these registers have a 16-bit address and a 16-bit value.

The Discreet Output Coils are registers that control a single output wire that has a binary value (high or low). Reading this register returns the output value of the bit and writing to it will update the coil with either low value, for writing 0, or high value, for writing anything else. The Discreet Input Contacts are registers that represent the value of a single input logic wire. The register can be only read and it is 0 if the wire is logic low and 0XFFFF if the wire is logic high. The DCS reference design does not have any functions that would map to Discreet Output Coils or Discreet Input Contacts. The Analog Input Registers represent an analog value, usually from an analog wire. This register can be only read and returns a 16-bit value. The Output Holding Registers are registers that control an analog output or a state of the slave. Reading this register returns the state of a process or an output and writing to it may change them or start a process.

Each register can be accessed using a function code:

Because the DCS reference design may contain any combination of up to four input or output boards, as a MODBUS slave, it contains two type of MODBUS registers: common and board specific.

The common registers are 5 read-only registers and 2 read-write registers. In standard MODBUS terminology that translates to 5 analog input registers and 2 holding registers:

The board type bit is “0” for CN0414 and “1” for CN0418.

The update rate is stored as:

  Update rate MSW = ((Actual update rate * 10000) & 0xFFFF0000) >> 16;
  Update rate LSW = ((Actual update rate * 10000) & 0x0000FFFF) >> 0;

So the equation used to retrieve the update rate is:

Or in code form:

  Actual update rate = (((Update rate MSW << 16) & 0xFFFF0000) | Update rate LSW) / 10000;

The register map is configured dynamically after power-up. Adding a board to the system adds a number of board specific registers: 50 analog input registers and 7 output holding registers for each EVAL-CN0414-ARDZ, and 30 analog input registers and 10 output holding registers for each EVAL-CN0418-ARDZ.

As stated before, adding an EVAL-CN0414-ARDZ adds 57 registers to the device: 50 analog input registers and 7 output holding registers. The analog input registers are: 16 for ADC input values, 4 for ADC input open wire detection flags and 50 for HART receive buffer. The output holding registers are: 1 for ADC output coding, 1 for ADC filter options, 1 for ADC postfilter options, 1 for ADC output data rate options, 1 for ADC open wire detection enable, 1 for HART command zero and 1 for HART channel select. The output holding registers are: 16 for the channel registers, 4 for Open Wire Detection and 30 for the HART input buffer. Adding an EVAL-CN0418-ARDZ adds 40 registers: 30 analog input registers and 10 output holding registers. There are 30 HART input registers as analog input registers. The output holding registers are: 4 for channel ranges (one for each channel), 4 for the channels output (one for each channel), 1 for the HART active channel and 1 for the HART command zero.

Address = (ADC_CS_address << 12) + (MODBUS_slave_address << 8) + Address_offset;

Register map for the EVAL-CN0414-ARDZ:

Register map for the EVAL-CN0418-ARDZ:

The software can be set up to work in CLI debug mode or in MODBUS mode. To set this make sure the relevant define in the config.h file is uncommented and the other one is commented:

//#define CLI_INTEFACE
//#define MODBUS_INTERFACE

There are two interfaces available for this application: a Command Line Interface (CLI) used mainly for debugging a single PLC node and a MODBUS interface used for PLC/DCS operation for single and multiple nodes.

The CLI is implemented through UART and must be connected to a computer via USB cable. A serial terminal program must run on the host PC to display data and control the application.

The MODBUS is connected through the EVAL-CN0416-ARDZ UART to RS485 adapter and must communicate with a MODBUS master on the RS485 line.

Typing help or h after initial calibration sequence will display the list of commands and their short versions. The CLI mode has a board command menu which is only used to select the board. Each board present in the system has it's own command set based on the type.

Bellow is the short command list for the board menu:

The specific commands for each of the types of boards is described in they respective wiki pages:

• EVAL-CN0414-ARDZ specific commands
• EVAL-CN0418-ARDZ specific commands

The Modbus protocol is not human-readable; as such, a Modbus master program is required to interact with the design. QModMaster is a free and open-source implementation of a Modbus master GUI application. This program is useful for board bringup and debug, and during application development. QModMaster is avalable at QModMaster on SourceForge

QModMaster is used to demonstrate several basic register operations below.

Common analog input registers read
Reading these registers with 2 EVAL-CN0414-ARDZ and 2 EVAL-CN0418-ARDZ connected to the system it can be seen that 4 boards are found at address “0000”.
The next address read “0001” indication that the board is a EVAL-CN0418-ARDZ and has address 0;
The second address reads “0003” indication that the board is EVAL-CN0418-ARDZ and has the address 1;
The third register read “0004” indicating that the board is EVAL-CN0414-ARDZ and has address 2;
And the last register reads “0006” for EVAL-CN0414-ARDZ and address 3.
ADC channels of one of the input boards with MODBUS
The second read shows the input channels data for the last input board found. This is done by reading 16 analog input registers fount at address 0x3105.
ADC change the output code
This is an example on how to change the ADC output code of the third board (input board with address 3) by writing the output holding register at the address 0x3100.

We recommend not opening the project directly, but rather import it into CrossCore Embedded Studios and make a local copy in your workspace.

The source code and include files of the ADuCM3029_demo_cn0435 can be found here:

The official tool we promote for use with the EVAL-ADICUP3029 is CrossCore Embedded Studio. For more information on downloading the tools and a quick start guide on how to use the tool basics, please check out the Tools Overview page.

For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to import existing projects into your workspace section.

For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to configure the debug session section.

The application controls a dynamic system that can be physically different every time it is run. to do this it has two parts:

1. The system initialization.
2. The system main process.

After getting parameters of the system supplied by the user in code the program initializes the software modules common to all the boards: I2C, UART, SPI, microcontroller power, software UART and the AD5700 HART modem. If the MODBUS interface is used, the update timer for the input boards is also initialized in this stage as a common module. If, by comparison, the CLI is used, each input board present initializes its own version of the update timer driver.

After these initializations the system runs a board discovery routine. By using the presence of I2C EEPROM memory and testing the SPI configuration, all boards in the system are discovered and labeled as either CN0414 or CN0418. If the MODBUS interface is used, the system also scans for its MODBUS slave address and maps and initializes MODBUS registers.

After board discovery, if the CLI is used, no board is set as active and the system manager loads the main menu process. If the MODBUS is used, the system activates the first board it discovers.

If the CLI is used, no board is active after the initialization and the system stands by to receive commands. If the user sets one of the boards to be active, the program loads the commands and process specific to that board and starts sunning them until the application is stopped or the “exit” command is called.

If the MODBUS interface is used the first board discovered is the active board. If it is a CN0414 the program runs its process until all channels are updated. If it is a CN0418 the program runs its process only once. After this the system deactivates the board and activates the next board discovered until all the boards have been active and updated. The system than cycles back from the beginning.

Meanwhile the system scans the MODBUS channel for commands and if one is found that is addressed to this node it executes it and sends back a response.

The process and commands for each type of boards is described in the appropriate application page:

• EVAL-CN0414-ARDZ
• EVAL-CN0418-ARDZ

User DCS programs running on the host will be highly application-specific, and written in any number of languages. This section presents several example applications and utilities written in Python that perform basic functions such as reading and writing analog voltages, detecting the configuration of a node, and changing the data rate of an analog input channel.

The following utility functions are demonstrated using the single-node configuration described above. It may be connected to the host either directly via USB (no RS485 interface) or over a USB to RS485 bridge. Minimalmodbus is an open-source (Apache license) Modbus RTU and Modbus ASCII implementation for Python, and is used in these examples. Similar libraries exist for other languages.

For example, consider an instrument (slave) with Modbus RTU and address number 1 to which we are to communicate via a serial port with the name COM12. The instrument stores the actual configuration in registers 0 to 4. To read data from the instrument:

read_common_analog_input_registers.py

"""Read common analog input registers to determine PLC/DCS configuration."""
 
import minimalmodbus
 
# declare an instrument object with port name, slave address as input arguments
INSTRUMENT = minimalmodbus.Instrument('COM12', 1)
 
# read 5 registers starting from address 0 by using function code 4
COMMON_ANALOG_INPUT_REGISTERS = INSTRUMENT.read_registers(
    registeraddress=0, numberOfRegisters=5, functioncode=4)
 
# result a list with 5 elements in decimal format
print(COMMON_ANALOG_INPUT_REGISTERS)

[4, 1, 3, 4, 6] 

In this example, after we run the above piece of code it results that we have 4 boards connected. Two of this boards are EVAL-CN0414-ARDZ and other two are EVAL-CN0418-ARDZ. The EVAL-CN0414-ARDZ boards have address 0b10 and 0b11 while EVAL-CN0418-ARDZ boards have address 0b00 and 0b01.

Next, if we want to read all analog input channels from one EVAL-CN0414-ARDZ we can use the following:

read_adc_analog_input_registers.py

"""Read analog input registers to determine ADC channels code."""
 
import minimalmodbus
 
# declare an instrument object with port name, slave address as input arguments
INSTRUMENT = minimalmodbus.Instrument('COM12', 1)
 
# read 16 registers starting from address 12549 by using function code 4
ADC_CHANNELS_CODES = INSTRUMENT.read_registers(
    registeraddress=12549, numberOfRegisters=16, functioncode=4)
 
# result a list with 16 elements in decimal format
print(ADC_CHANNELS_CODES)

[127, 65158, 127, 65514, 127, 65194, 127, 64995, 127, 65285, 127, 65244, 127, 65292, 127, 65278]

In this example, after we run the above piece of code it results a list of 16 elements in decimal format. First 8 values corespond to voltage channels and last to current channels.

Next, if we want to change the output code of one EVAL-CN0414-ARDZ ADC to be unipolar instead of bipolar we can use the following:

set_adc_output_code.py

"""Read and write one output holding register to change ADC output code."""
 
import minimalmodbus
 
# declare an instrument object with port name, slave address as input arguments
INSTRUMENT = minimalmodbus.Instrument('COM12', 1)
 
# read a single register from address 12544 by using function code 3
INITIAL_ADC_OUTPUT_CODE = INSTRUMENT.read_register(
    registeraddress=12544, functioncode=3)
 
# result an integer
print(INITIAL_ADC_OUTPUT_CODE)
 
# wrie a single register from address 12544 by using function code 6
INSTRUMENT.write_register(registeraddress=12544, value=1, functioncode=6)
 
# read a single register from address 12544 by using function code 3
FINAL_ADC_OUTPUT_CODE = INSTRUMENT.read_register(
    registeraddress=12544, functioncode=3)
 
# result an integer
print(FINAL_ADC_OUTPUT_CODE)

0
1

In this example, after we run the above piece of code it results an integer which coresponds to ADC coding format. The default value 0, indicate that the ADC is set to bipolar coding format, while a value of 1 will indicate an unipolar coding format.

Next, if we want to change the output code of one EVAL-CN0418-ARDZ DAC channel we can use the following:

set_dac_output_voltage.py

"""Read and write one output holding register to change DAC channel voltage."""
 
import minimalmodbus
 
# declare an instrument object with port name, slave address as input arguments
INSTRUMENT = minimalmodbus.Instrument('COM12', 1)
 
# read a single register from address 4356 by using function code 3
INITIAL_DAC_CHANNEL_1_CODE = INSTRUMENT.read_register(
    registeraddress=4356, functioncode=3)
 
# result an integer
print(INITIAL_DAC_CHANNEL_1_CODE)
 
# wrie a single register from address 4356 by using function code 6
INSTRUMENT.write_register(registeraddress=4356, value=65535, functioncode=6)
 
# read a single register from address 4356 by using function code 3
FINAL_DAC_CHANNEL_1_CODE = INSTRUMENT.read_register(
    registeraddress=4356, functioncode=3)
 
# result an integer
print(FINAL_DAC_CHANNEL_1_CODE)

0
65535

In this example, after we run the above piece of code it results an integer which coresponds to DAC channel 1 output code. Depending on channel configuration this output code will corespond to a voltage or a current value. In this example the DAC channel output code is by default 0V because the default channel range is set to 0V to 5V. The 65535 value will corespond in this case to a 5V output.

Next, if we want to determine the system configuration we can run the following script from the attached archive.

detect_configuration.zip

For a PLC configuration the script output will look similarly like this:

Welcome! Use 'CTRL+C' to go back from the current menu or exit!

Available devices:
1 -> Silicon Labs CP210x USB to UART Bridge (COM12)
2 -> Intel(R) Active Management Technology - SOL (COM3)

Enter detected device index, or press ENTER to use COM12:
No boards at MODBUS address: 1 No communication with the instrument (no answer)

Boards found at MODBUS address: 2
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         4
0002 (0x0002)  Second board data        6
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
Analog input board at address: 10
Analog input board at address: 11
No boards at MODBUS address: 3 No communication with the instrument (no answer)
No boards at MODBUS address: 4 No communication with the instrument (no answer)
No boards at MODBUS address: 5 No communication with the instrument (no answer)
No boards at MODBUS address: 6 No communication with the instrument (no answer)
No boards at MODBUS address: 7 No communication with the instrument (no answer)
No boards at MODBUS address: 8 No communication with the instrument (no answer)
No boards at MODBUS address: 9 No communication with the instrument (no answer)
No boards at MODBUS address: 10 No communication with the instrument (no answer)
No boards at MODBUS address: 11 No communication with the instrument (no answer)
No boards at MODBUS address: 12 No communication with the instrument (no answer)
No boards at MODBUS address: 13 No communication with the instrument (no answer)
No boards at MODBUS address: 14 No communication with the instrument (no answer)
No boards at MODBUS address: 15 No communication with the instrument (no answer)
No boards at MODBUS address: 16 No communication with the instrument (no answer)

For a DCS configuration the script output will look similarly like this:

Welcome! Use 'CTRL+C' to go back from the current menu or exit!

Available devices:
1 -> Silicon Labs CP210x USB to UART Bridge (COM12)
2 -> Intel(R) Active Management Technology - SOL (COM3)

Enter detected device index, or press ENTER to use COM12:

Boards found at MODBUS address: 1
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         1
0002 (0x0002)  Second board data        3
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
Analog output board at address: 00
Analog output board at address: 01

Boards found at MODBUS address: 2
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         4
0002 (0x0002)  Second board data        6
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
Analog input board at address: 10
Analog input board at address: 11
No boards at MODBUS address: 3 No communication with the instrument (no answer)
No boards at MODBUS address: 4 No communication with the instrument (no answer)
No boards at MODBUS address: 5 No communication with the instrument (no answer)
No boards at MODBUS address: 6 No communication with the instrument (no answer)
No boards at MODBUS address: 7 No communication with the instrument (no answer)
No boards at MODBUS address: 8 No communication with the instrument (no answer)
No boards at MODBUS address: 9 No communication with the instrument (no answer)
No boards at MODBUS address: 10 No communication with the instrument (no answer)
No boards at MODBUS address: 11 No communication with the instrument (no answer)
No boards at MODBUS address: 12 No communication with the instrument (no answer)
No boards at MODBUS address: 13 No communication with the instrument (no answer)
No boards at MODBUS address: 14 No communication with the instrument (no answer)
No boards at MODBUS address: 15 No communication with the instrument (no answer)
No boards at MODBUS address: 16 No communication with the instrument (no answer)

Next, if we want to check or change the system registers we can run the following script from the attached archive.

read_or_write_registers.zip

Depending on the system configuration, one or more DCS nodes will be detected. After the user selects a valid DCS node, a menu will appear which contain all available system options. Now, depending on the node configuration, not all option will be valid, even if they are shown. For example, if a DCS node doesn't contain CN0414 analog input board(s), any option which refers to CN0414 will do nothing.

Welcome! Use 'CTRL+C' to go back from the current menu or exit!

Available devices:
1 -> Silicon Labs CP210x USB to UART Bridge (COM12)
2 -> Intel(R) Active Management Technology - SOL (COM3)

Enter detected device index, or press ENTER to use COM12:
Enter MODBUS timeout (0.05[s] to inf), or press ENTER to use 0.1[s] timeout:

Boards found at MODBUS address: 1
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         1
0002 (0x0002)  Second board data        3
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
analog output board at address: 00
analog output board at address: 01

Boards found at MODBUS address: 2
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         4
0002 (0x0002)  Second board data        6
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
analog input board at address: 10
analog input board at address: 11
No boards at MODBUS address: 3 No communication with the instrument (no answer)
No boards at MODBUS address: 4 No communication with the instrument (no answer)
No boards at MODBUS address: 5 No communication with the instrument (no answer)
No boards at MODBUS address: 6 No communication with the instrument (no answer)
No boards at MODBUS address: 7 No communication with the instrument (no answer)
No boards at MODBUS address: 8 No communication with the instrument (no answer)
No boards at MODBUS address: 9 No communication with the instrument (no answer)
No boards at MODBUS address: 10 No communication with the instrument (no answer)
No boards at MODBUS address: 11 No communication with the instrument (no answer)
No boards at MODBUS address: 12 No communication with the instrument (no answer)
No boards at MODBUS address: 13 No communication with the instrument (no answer)
No boards at MODBUS address: 14 No communication with the instrument (no answer)
No boards at MODBUS address: 15 No communication with the instrument (no answer)
No boards at MODBUS address: 16 No communication with the instrument (no answer)

Enter MODBUS address from this list [1, 2], or press ENTER to use MODBUS address 1:
Enter commands delay (0[s] to inf), or press ENTER to use 0.1[s] delay:

Test options:
1 - Read common analog input registers.
2 - Read common output holding registers.
3 - Read analog input registers.
4 - Read output holding registers.
5 - Write output holding register.
q - Quit.

Enter test option:

The following section presents several example top-level DCS applications. Like the utilities, these are based on Minimalmodbus.

This application provides a simple way to control a DCS system and also to detect HART devices by using the HART protocol.

The HART protocol is proprietary, customers implementing a full HART stack should refer to https://fieldcommgroup.org This reference design provides a basic implementation of “command zero” that can be used to verify connectivity with HART instruments. CN0267 is a Complete 4 mA to 20 mA Loop Powered Field Instrument with HART Interface that can be used to test the DCS HART functionality. This application allows to:

• detect sistem configuration;
• configure and read ADC channels;
• configure and write DAC channels;
• configure HART modems and send HART command zero.

dcs_cn0435.zip

Welcome! Use 'CTRL+C' to go back from the current menu or exit!

Available devices:
1 -> Silicon Labs CP210x USB to UART Bridge (COM12)
2 -> Intel(R) Active Management Technology - SOL (COM3)

Enter detected device index, or press ENTER to use COM12:
Enter MODBUS timeout (0.05[s] to inf), or press ENTER to use 0.1[s] timeout:

Boards found at MODBUS address: 1
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         1
0002 (0x0002)  Second board data        3
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
analog output board at address: 00
analog output board at address: 01

Boards found at MODBUS address: 2
Address        Name                 Value
-------------  -----------------  -------
0000 (0x0000)  Detected boards          2
0001 (0x0001)  First board data         4
0002 (0x0002)  Second board data        6
0003 (0x0003)  Third board data     65535
0004 (0x0004)  Fourth board data    65535
analog input board at address: 10
analog input board at address: 11
No boards at MODBUS address: 3 No communication with the instrument (no answer)
No boards at MODBUS address: 4 No communication with the instrument (no answer)
No boards at MODBUS address: 5 No communication with the instrument (no answer)
No boards at MODBUS address: 6 No communication with the instrument (no answer)
No boards at MODBUS address: 7 No communication with the instrument (no answer)
No boards at MODBUS address: 8 No communication with the instrument (no answer)
No boards at MODBUS address: 9 No communication with the instrument (no answer)
No boards at MODBUS address: 10 No communication with the instrument (no answer)
No boards at MODBUS address: 11 No communication with the instrument (no answer)
No boards at MODBUS address: 12 No communication with the instrument (no answer)
No boards at MODBUS address: 13 No communication with the instrument (no answer)
No boards at MODBUS address: 14 No communication with the instrument (no answer)
No boards at MODBUS address: 15 No communication with the instrument (no answer)
No boards at MODBUS address: 16 No communication with the instrument (no answer)

Enter MODBUS address from this list [1, 2], or press ENTER to use MODBUS address 1:
Enter commands delay (0[s] to inf), or press ENTER to use 0.1[s] delay:

Use CTRL+C to end a process or switch between nodes.
CN0414                                 CN0418                        CN0435
-------------------------------------  ----------------------------  ----------------------------------------
1 - Read device voltage channel        e - Set DAC channel 1 output  o - Read common analog input registers
2 - Read device current channel        f - Set DAC channel 2 output  p - Read common output holding registers
3 - Read board voltage channels        g - Set DAC channel 3 output  r - Read analog input registers
4 - Read board current channels        h - Set DAC channel 4 output  s - Read output holding registers
5 - Read instrument voltage channels   i - Set DAC channel 1 range   t - Detect system configuration
6 - Read instrument current channels   j - Set DAC channel 2 range
7 - Set ADC output code                k - Set DAC channel 3 range
8 - Set ADC filter                     l - Set DAC channel 4 range
9 - Set ADC postfilter                 m - Send HART command zero
a - Set ADC output data rate           n - Select HART channel
b - Set ADC open wire detection state
c - Send HART command zero
d - Select HART channel                                              q - Quit

Enter Option:

End of Document