How nisystemsengineering/labview-modbus-api works
This is a LabVIEW Modbus library providing master and slave communication over serial and Ethernet. Users create a master or slave instance, issue Modbus operations, and communicate with industrial devices or gateways. The tree identifies API, network, transmission-unit, and data-model layers, but no source excerpts were provided; internal connections below are therefore dashed and unverified. Major protocol and device-model capabilities are represented without asserting specific call paths.
Main entry points: Master Master Operations · Slave Slave Operations · Network Master Master Network · Network Slave Slave Network
Components 13
Public API
- Instance Creation
API/Wrapper/Create Modbus Instance.vi - Master Operations
API/Master - Slave Operations
API/Slave
Protocol Handling
- Transmission Units
Transmission Data Unit - Protocol Data Unit
Modbus Data Unit/Construct PDU.vi - Master Functions
Master Function Definition
Network Communication
- Master Network
Network Protocol/Network Master - Slave Network
Network Protocol/Network Slave - Serial Transport
Network Protocol/Serial Shared Components - TCP Transport
Network Protocol/TCP Shared Components
Device Model
- Device Data Model
Data Model/Device Data Model.lvclass - Standard Model
Data Model/Standard Data Model/Standard Data Model.lvclass
Other components
- LabVIEW User
Connections 15
- LabVIEW User → Instance Creation: creates instance
- LabVIEW User → Master Operations: issues operations
- LabVIEW User → Slave Operations: uses slave API
- Master Operations → Master Network: communicates through
- Slave Operations → Slave Network: communicates through
- Master Network → Serial Transport: uses serial
- Master Network → TCP Transport: uses Ethernet
- Slave Network → Serial Transport: uses serial
- Slave Network → TCP Transport: uses Ethernet
- Master Operations → Transmission Units: transfers protocol data
- Slave Operations → Transmission Units: transfers protocol data
- Transmission Units → Protocol Data Unit: carries protocol data
- Master Operations → Master Functions: supports functions
- Slave Operations → Device Data Model: accesses device model
- Device Data Model → Standard Model: provides standard model