SOFTWARE SUPPORT / ENGINEERING

Custom protocol development

Define the device role, frame format, point mapping and response behavior before implementation.

Turn a protocol document into a working connection.

Review the existing product functions first, then agree any changes against the selected hardware, firmware and application.

Explore software features
FIELD DEVICERead → Map → ReportEDGE GATEWAY → YOUR APPLICATION

Command → Device response → Readback

IMPLEMENTATION SCOPE

Define the work around the application.

01

Read & interpret

Specify the transport, device role, frame format, checksum, address and data types.

02

Map & exchange

Define the point list, units, scaling, timestamps and upstream message format.

03

Control & confirm

Define write permissions, responses, timeouts and readback before enabling commands.

FROM REQUIREMENT TO ACCEPTANCE

A reviewable delivery at each step.

01

Bring the original specification

Share the protocol document, request/response samples and access to a device or simulator.

02

Check existing support first

Review native Modbus, DTU and PLC options before commissioning a custom driver.

03

Test both ends

Verify normal frames, invalid data, disconnection, recovery and the actual receiving system.

What to include in the handover

Custom development, compatibility, schedule and commercial terms are assessed for each project.

Protocol roles matter.

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

Check the details before you choose.

START WITH YOUR APPLICATION

Tell us what needs to connect.

Share the model, interfaces, protocol documents and the result you need. We will review the implementation and acceptance scope with you.

Discuss your project
WhatsApp