Technical Data - V5

Owned by Yuriy Zavgorodniy
Last updated: 2024-03-26
Protocol Technical Data
FeatureDescription
Maximum number of input data5760 bytes
Maximum number of output data5760 bytes
Acyclic communication

Read/Write Register:

  • Max. 125 Registers per Read Telegram (FC 3,4,23)
  • Max. 121 Registers per Write Telegram (FC 23),
  • Max. 123 Registers per Write Telegram (FC 16)

Read/Write Coil:

  • Max. 2000 Coils per Read Telegram (FC 1, 2)
  • Max. 1968 Coils per Write Telegram (FC 15)
Modbus Function Codes1, 2, 3, 4, 5, 6, 7, 15, 16, 23
Supported Operation Modes

ModbusTCP Server

  • I/O Mode
  • Message Mode

ModbusTCP Client

  • I/O Mode (Command Table)
  • Message Mode
Supported Protocols
  • MODBUS APPLICATION PROTOCOL SPECIFICATION,  V1.1a, June 4, 2004,
  • MODBUS MESSAGING ON TCP/IP IMPLEMENTATION GUIDE,  V1.0a, June 4, 2004
Baud rates10 and 100 MBit/s
Data transport layerEthernet II, IEEE 802.3


Restrictions

  • only standard function codes implemented
Firmware Functions

The real-time protocol stack is fully integrated into a netX firmware for specific use case in order to provide a common set of netX firmware functions accross different protocol variants:

Firmware VariantsUse Case AUse Case BUse Case C
Use Case summary

netX90 COM CPU firmware for small footprint, low cost and function optimized slave devices

  • no external SPI / SQI Flash required for COM CPU
  • no external SDRAM required for COM CPU

same as Use Case A, but netX90 APP CPU

  • uses external SPI Flash
  • may use external SDRAM

full featured firmware for highest function requirements

  • external SDRAM is required for COM CPU
  • external SPI Flash is required for COM CPU
netX support
  • netX90
  • netX90 with ext FLASH
  • netX90 with ext SDRAM and ext FLASH
FW structure

Host Interface

Dual Port Memory interface with following channels:

  • Channel 0 - Real-Time Ethernet Protocol API
    • exchange cyclic IO data
    • use acyclic protocol services
  • Channel 1 - Network Services
    • Socket API - Enables opening a communication socket using the integrated TCP/IP stack resources, i.e. same MAC address
    • Ethernet (NDIS) API - Enables sending and receiving Ethernet frames using a separate MAC address, i.e. application host with its own TCP/IP stack
    • Web API - Enables forwarding specific URL (HTTP GET/POST) requests to user applications, e.g. to build custom webpage contents
Diagnosis InterfacenetX Diagnostic and Remote Access
Integrated Flash File SystemN/AN/APower-fail safe flash file system on external SPI flash is used
Remanent Data Storage

Power-fail safe storage of up to 16KB of protocol remanent data in netX90 internal flash

Power-fail safe storage of protocol remanent data in dedicated partition in extenal SPI flash. Size and position of remanent storage area shall be configured in FDL.
Device Data

device production data (Serial number, MAC address, production data etc.) shall be stored in FDL in netX90 internal flash

Firmware Transfer


 to internal netX90 flash ...
  • via integrated web server
  • via Host Interface (DPM, SPM)

(warning) Note:

due to limited size (max. 380KB) of FW udate are in internal flash, only following files can be transfered:

  • individual firmware files (i.e. comfw.nxi or appfw.nai) if the size of the a file is less that 380KB
  • max. 380KB big FWUPDATE.zip file with predefined structure
 to the host application...
  • via integrated webserver and Web API  (DPM Channel 1)
  • host application need to handle storage of the frimware in external SPI flash
to netX flash file system located on external SPI Flash
Firmware Update

Firmware check and installation supported through calling the Maintenance Firmware

(star) Note: netX90 Use Case C firmware requires  Maintenance Firmware v1.3.0.0 or later.

  • from internal netX90 flash
  • from external SPI flash
  • from Flash File System located on external SPI Flash
Configurationby sending packets to the firmware

by sending packets to the firmware

or by using Communication Studio configuration database file from local flash file system

Integrated Basic Webserver

The basic web server has the following features:

  • \netx  - Provides a graphical user interface to other functions (diag, firmware, reset, etc.)      
  • \netx\diag  - Provides information on the netX device (current uptime, MAC address, device   number, serial number, etc.
  • \netx\firmware  - Enables uploading a new firmware update file to netX flash
  • \netx\reset  - Initiates a netX reset cycle, i.e. to install a newly uploaded firmware
  • \  - URL requests are forwarded to the user application via DPM (web interface API)
Webserver extensionN/A

Basic web server is extended with functions that provide access to the content files on a local Flash file system (SQI Flash).

  • \netx\files  - Enables streaming of custom web content according to media types (i.e. txt, js, xhtml, jpeg, json, etc.) located in the Flash file system
Tag List Options

Firmware supports certain modification of the functionality via Tag List, in particular:

  • Webserver port number or deactivation
  • Activation of Ethernet Interface in DPM Channel1
  • DDP Mode (Device Data Provider) after startup
  • Enable / Disable Uart Diagnostic interface
  • Enable / Disable netIDENT
  • Open Ports without IP address
  • Enable PHY without configuration
HW Sync SignalN/A
Protocol Specific LED Indicators

Network specific status indicators with COM0 / COM1 LEDs:

  • RUN
  • ERR
Secure Bootsupported by Open Modbus/TCP V5.2.0.0 and later, see Support of Secure Boot with netX90 for more details
Limitations
  • FW functions are limited by available internal RAM / Flash
  • COM firmware size is limited to 500KB
  • FW functions are limited by available internal RAM / Flash