PROFIBUS link-type

[Simon Berg]

Hello

I've written some capturing tools and a basic Wireshark dissector for
the PROFIBUS protocol. Since it's delivered directly over a RS485-link,
it needs a separate link-type. Since I haven't been able to find a
suitable type among the existing ones, I'd like to request one being
allocated.

The format is the full packets as described in IEC 61158 (61158-4-3 more
precisely).
For a more accessible description look at
http://profibus.felser.ch/en/

BTW Is there a working archive for this list? The one I've found is
empty.

simon

[Simon Berg]

I wanted to bump this since I didn't get a reply, maybe due too an
unclear subject-line.
If there's something missing in or wrong with my request please let me
know.

simon

Post by Simon Berg
Hello
I've written some capturing tools and a basic Wireshark dissector for
the PROFIBUS protocol. Since it's delivered directly over a RS485-link,
it needs a separate link-type. Since I haven't been able to find a
suitable type among the existing ones, I'd like to request one being
allocated.
The format is the full packets as described in IEC 61158 (61158-4-3 more
precisely).
For a more accessible description look at
http://profibus.felser.ch/en/
BTW Is there a working archive for this list? The one I've found is
empty.
simon

[Guy Harris]

Post by Simon Berg
I've written some capturing tools and a basic Wireshark dissector for
the PROFIBUS protocol. Since it's delivered directly over a RS485-link,
it needs a separate link-type. Since I haven't been able to find a
suitable type among the existing ones, I'd like to request one being
allocated.
The format is the full packets as described in IEC 61158 (61158-4-3 more
precisely).

So "full" presumably means that:

the first octet of a packet is the start delimiter for the packet (the start delimiter appears not to have a single standard value for all packets, so it appears that it can't be elided without loss of information);

it also includes the end delimiter for asynchronous transmission, and all the octets between the delimiters, including the FCS octet, exactly as they appear on the wire.

[Guy Harris]

Given a valid octet-stream, all the data going over the wire would be
part of a packet.

OK, {LINKTYPE,DLT}_PROFIBUS_DL (_DL to emphasize that this is at the data link layer - if somebody wants, in the future, to provide something less than the full data link layer set of octets, another name could be used for that) have been assigned the value 257.

[Simon Berg]

Post by Guy Harris

Given a valid octet-stream, all the data going over the wire would be
part of a packet.

OK, {LINKTYPE,DLT}_PROFIBUS_DL (_DL to emphasize that this is at the data link layer - if somebody wants, in the future, to provide something less than the full data link layer set of octets, another name could be used for that) have been assigned the value 257.

Thanks!

If someone is interested I have written a tool (pblog) that will capture
PROFIBUS data from a serial device and write it as PCAPNG.
Works on Linux. I'm doing some tricks to get the high speeds so it
probably won't work on anything else out of the box.
You can get it from
https://github.com/fluffware/pbsniffer.git

simon