Read & interpret
Specify the transport, device role, frame format, checksum, address and data types.
SOFTWARE SUPPORT / ENGINEERING
Define the device role, frame format, point mapping and response behavior before implementation.
Review the existing product functions first, then agree any changes against the selected hardware, firmware and application.
Explore software featuresCommand → Device response → Readback
IMPLEMENTATION SCOPE
Specify the transport, device role, frame format, checksum, address and data types.
Define the point list, units, scaling, timestamps and upstream message format.
Define write permissions, responses, timeouts and readback before enabling commands.
FROM REQUIREMENT TO ACCEPTANCE
Share the protocol document, request/response samples and access to a device or simulator.
Review native Modbus, DTU and PLC options before commissioning a custom driver.
Verify normal frames, invalid data, disconnection, recovery and the actual receiving system.
Custom development, compatibility, schedule and commercial terms are assessed for each project.
A serial tunnel forwards bytes; a protocol driver interprets them. The documented DNP3 function is serial-to-TCP frame forwarding, not a full DNP3 master or outstation. A new protocol role requires a separate implementation review.
DOCUMENTATION
START WITH YOUR APPLICATION
Share the model, interfaces, protocol documents and the result you need. We will review the implementation and acceptance scope with you.