Software - Testing and Simulation
Modsak tests a devices handling of the Modbus protocol. Software developers can use Modsak to simulate the environment (Modbus masters, slaves and bridges) in which their software has to operate. System integrators can plug Modsak into a system temporarily to replace Modbus components they don't yet have; or when components refuse to talk to each other Modsak can be used to try out different configuration settings.
Modbus, Modbus TCP
Can be configured to run in one of four modes: Manual master mode (user can send individual requests to a Modbus slave); Automatic master mode (continually polls (sends read and write requests to) a Modbus slave); Slave mode (simulates a Modbus device); Monitor mode (relays messages between a Modbus master and a Modbus slave); In Monitor mode Modsak can be used as a gateway; Support for coils, discrete inputs, input registers and holding registers, using commands 1, 2, 3, 4, 5, 6, 7, 8, 11, 15, 16, 17, 22 and 23; Supports network and serial (RS232/RS422/RS485) interfaces using the Modbus TCP, RTU and ASCII protocol variants
Runs on any system that supports Java 1.4 or later - including Windows, Linux, Solaris and AIX; All known extensions of the Modbus protocol for handling 32-bit and 64-bit integers and floating-point numbers are supported; Can transfer a mix of integers and floats in a single message; Flexible address mapping allows separate or overlaid address spaces (for coils, discrete inputs, input registers, and holding registers) with arbitrary bases; Registers are individually configurable for type (integer or float), size (8/16/32/64-bit), and radix (binary, octal, decimal, or hex)