Modbus TCP / RTU
Holding and input registers, coils and discrete inputs, register bits, selectable word order for 32/64-bit values, RTU over TCP and serial.
Native drivers for the controllers found on most shop floors, available in all three products. Browsable protocols open as a tree, related addresses are read together, and every value carries a quality code.
Holding and input registers, coils and discrete inputs, register bits, selectable word order for 32/64-bit values, RTU over TCP and serial.
S7-200, S7-300, S7-400, S7-1200, S7-1500 and LOGO!: data blocks, markers, inputs, outputs and S7 strings, read in optimised multi-item requests.
Q, L, FX5 and iQ-R: data, file and link registers, bit devices, timers and counters, read in blocks.
CS, CJ, CP, NJ and NX series: DM, CIO, work, holding, auxiliary, timer, counter and EM areas over UDP or TCP.
ControlLogix, CompactLogix, GuardLogix and Micro800 with symbolic tag access: controller and program tags, arrays, UDT members and strings, with tag browsing.
CNC status, axis positions, spindle speed and load, feed, alarms, macro variables, parameters, diagnosis, PMC areas and program numbers over Ethernet.
CODESYS V2/V3 network variable lists over UDP: receive and send lists, arrays and strings, multicast and a watchdog for stale data.
Polling or subscriptions, address-space browsing, None / Sign / SignAndEncrypt with automatic client certificate and trust management.
OPC DA servers on the same PC or over DCOM, with server discovery, cache or device reads and browsing.
Machine data collection: status, program, parts, cycle times, tool changes, spindle and positions, macro variables.
Samples, events and conditions from any MTConnect agent, with quality and browsing of all data items.
Signal generators for tests and demos; virtual variables for operator entries such as work orders and planned stops.
OPC UA, OPC DA, Logix, NVL, Haas and MTConnect open as a tree; select the values and add them in bulk.
An AI assistant knows the address syntax of every driver and can create and test devices and tags over MCP.
Prepare hundreds of tags in a spreadsheet and import them; export for documentation or another site.
Good, uncertain, stale or bad: screens, history, alarms and OPC UA clients see the same quality code.
Tell us which device and protocol you need; the driver framework is designed for adding new protocols.