Tiza Group

Home / Tools / DNP3 and Modbus decoder

DNP3 and Modbus decoder with polling time

Paste the frame in hexadecimal and choose the protocol. The tool marks each field on the octets, checks the CRCs and draws the network with the polling cycle of the slaves.

Example cases
DNP3 and Modbus decoder with polling time
ALearn

E1Frame

Octets separated by spaces, with or without 0x, or all together.

E2Polling
bit/s
ms

Estimate: equipment figure.

ms

Use a decimal point. The calculation runs in your browser and updates as you type.

CRC and length

—

Function

—

Polling cycle

—

Octets of the frame

—

The network, the polling cycle and the frame octet by octet
Above, the master polls each slave in its turn; in red, the one that does not answer. Below, each octet of the frame with the name of its field; in red, what does not add up.

Decoded fields

OctetsFieldValueReading

What it is for

During the commissioning of a SCADA or a gateway you need to read DNP3 and Modbus frames captured on the serial port or the network. This tool splits each field, checks the CRCs and computes how long the master takes to go through all its slaves.

IEC 60870-5-104 frames are read in the IEC 104 APDU decoder.

How it is decoded

Source: MODBUS over Serial Line V1.02; MODBUS Application Protocol V1.1b3

Modbus

RTU: slave · function · data · CRC-16 (0xA001, initial 0xFFFF, low octet first); TCP: transaction · protocol 0 · length · unit · function · data

A function with the highest bit set to 1 is an exception: the next octet gives the cause.

Source: DNP Users Group, A DNP3 Protocol Primer

DNP3

0x05 0x64 · LEN · CTRL · destination · source · CRC; data in blocks of 16 octets + CRC (polynomial 0x3D65)

Without the CRCs, what remains is the transport octet (FIN, FIR, sequence), the application control, the function code, the IIN in responses and the object headers: group, variation, qualifier and range.

Source: MODBUS over Serial Line V1.02, 2.5.1

Polling cycle

t = Σ (request + t3.5 + slave response time + response frame + t3.5) + failed · (request + t3.5 + timeout) · (1 + retries)

A Modbus RTU character has 11 bits; above 19 200 bit/s the silence t3.5 is fixed at 1.75 ms.

Limits

  • In DNP3 it decodes the most common groups; an unknown object is shown as octets.
  • It does not join the fragments of a long DNP3 response split across several frames.
  • It does not decode Modbus ASCII or DNP3 over TCP with its network header.
  • It does not replace the protocol analyser of the commissioning. The example frames are our own.

Frequently asked questions

How do I know whether a Modbus frame is a request or a response?

In a read, the response starts with the count of the octets that follow; the request carries address and quantity. The tool deduces it, but you can force it with the «Direction» field.

Why does a DNP3 frame have CRCs in the middle?

Because the link layer adds a CRC after the header and another every 16 data octets. The tool checks them one by one and removes them before reading the application.

How long does a Modbus polling cycle take?

The sum of each request, the silence, the response time of the slave and its response frame. A slave that does not answer costs the full timeout, multiplied by the retries: that is usually what lengthens the cycle most.

Related guides

Other tools

All tools
WhatsApp