The SuperCom MODBUS Protocol Module implements the MODBUS protocol. It also supports custom function codes and data packets by implementing functions that communicate transparently.
A MODBUS client or server, created with the required SuperCom software, can control different type of connections. More...
Following a list of some functions of the SuperCom MODBUS Protocol Module.
|RS_MBGetConfig||Retrieve the protocol module configuration|
|RS_MBSetConfig||Change the protocol module configuration|
|RS_MBSetConfigStr*||Change the protocol module configuration. The difference to RS_MBSetConfig is: the values are stored in a string as "Name=Value;" pairs.|
|RS_MBReadCoil||Read values of a single coils|
|RS_MBReadCoils||Read the values of a sequence of coils|
|RS_MBReadCoilsStr*||Read the values of a sequence of coils and returns the coil values as a string, e.g. "01100100"|
|RS_MBReadInput||Read the values (bits) of one or more discrete Input bits|
|RS_MBReadInputRegisters||Read a sequence of Input Registers|
|RS_MBReadHoldingRegisters||Read a sequence of Holding Registers|
|RS_MBReadGeneralReference||Can read multiple groups & references|
|RS_MBWriteCoil||Set the value of a single coil|
|RS_MBWriteCoils||Set the value of a sequence of coil|
|RS_MBWriteCoilsStr*||Set the value of a sequence of coil. The difference to RS_MBWriteCoils is: the new coil values are provided as a string, e.g. "01100100"|
|RS_MBWriteRegister||Set the value of a single register|
|RS_MBWriteRegisters||Set the value of a sequence of registers|
|RS_MBHandleRequests||Handle Master requests - Simulate a MODBUS Server. This function is almost all that is necessary with the SuperCom software to create a server, that can even control multiple connections simultaneously (e.g. under TCP/IP). Specific samples are included.|
|RS_MBSetPLCMem||Defines and populates a memory area in order to simulate a PLC (simulation of a MODBUS Server). It can also be used to get a snapshot of the simulated PLC's memory.|
|RS_MBReadFIFOQueue||Read First-In-First-Out (FIFO) queue of holding registers. The function returns the count and the value of the registers in the queue.|
|RS_MBGetDeviceId||Read Device Identification and other device related information (e.g. vendor name, product code, version, revision number). It is using function code 43 (Hex 2B) and MEI Type 14 (Hex 0E).|
|RS_MBGetEventCounter||Provides a status word and an event count from the Modbus server's plc.|
|RS_MBGetEventLog||Provides a status word, an event count, a message count and event bytes from the Modbus server's plc.|
|RS_RXMODBUS||Receive a data packet according to the MODBUS protocol specification. Data packets received are handed over transparently. Using this function it is possible to receive custom requests (custom function codes e.g. FC43), build a MODBUS Server, a MODBUS to "other protocol" converter or gateway, etc.|
|RS_TXMODBUS||Transmit a data packet according to the MODBUS protocol specification. Using this function it is possible to transmit data packets transparently e.g. respond or transmit a custom requests (custom function codes e.g. FC43), support custom function codes, build a MODBUS Server, a MODBUS to "other protocol" converter or MODBUS Gateway (e.g. Serial to Ethernet), etc.|
* introduced with Version 4.5.
With the SuperCom MODBUS Protocol Module there is only one API to learn! The same functions and parameters used with serial, TCP/IP or ISDN type of connections.