Wireshark-dev: Re: [Wireshark-dev] XML Parsing in Wireshark
From: Andreas Stuckert <info@xxxxxxxxx>
Date: Sun, 10 May 2009 20:44:02 +0000 (UTC)
Anders Broman <a.broman@...> writes:

> 
> Hi,
> Have you checked out the existing plugin ..\plugins\sercosiii
> Regards
> Anders
> 
> -----Ursprungligt meddelande-----
> Från: wireshark-dev-bounces@...
> [mailto:wireshark-dev-bounces@...] För Andreas Stuckert
> Skickat: den 10 maj 2009 10:12
> Till: wireshark-dev@...
> Ämne: [Wireshark-dev] XML Parsing in Wireshark
> 
> Hi ! 
> for my project, we have to use a XML parser to read a SercosIII
> Configuration interface file to get information to dissect sercosIII data
> frames in detail. The written Plugin should be released in a further version
> of Wireshark
> 
> There for I have some Questions:
> - I found no XML Parsing Lib in the Source code. Only several parts of
> parsing code to desect XML in frames. Is there no lib for this? Also I found
> no Good news to this Topic in the mailing list.
> - If there is no Lib, which can I use? It is Important that it is no
> proprietary software the Sercosiii plugin feature should be released soon in
> the official Version
>  
> Can you answer to my questions please because the dead line of my project
> comes quickly?
> I am a newbie in developing open source software. I would be glad for
> getting some usefull hints.
> 
> Regards Andreas Stuckert
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@...?subject=unsubscribe
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@...>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@...?subject=unsubscribe
> 
> 


Hello Anders

Yes we did. Sercosiii is dissected in parts but not complete. After CP2 State 
there is no dissection in Detail. To dissect in CP3 or higher you must have the 
configuration of the system. There was a previous implementation but this was 
checked in but it didn’t make it to get in to the official version because the 
Code was not good enough.
There are two ways to get the configuration.

1. Capture the startup of the system and learn the communication offsets by 
listing the traffic during CP0 to CP2
2. Give Wireshark a Sercos Configuration File that contents the communication 
parameters

My friend is doing the first point
My task is to do the second one

Regards Andreas