http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1430
------- Comment #37 from PeterJohansson73@xxxxxxxxx 2007-10-04 06:38 GMT -------
(In reply to comment #35)
> The 'E88A4' part in details view only contains 2 bytes, but marks all bytes,
> why not move those 2 bytes into the EtherCAT protocol part (or AMS, Mailbox,
> etc)? E88A4 is also not very descriptive...
> ---
> Since many EtherCAT frames contains many frames, and there are usually many
> ethernet frames en a capture, I find lines with 'Info' fields like:
> NPWR#4099[4]@502, BRD[2]@130, APRD#5[2]@130, APRD#4[2]@130, APRD#3[2]@130,
> APRD#2[2]@130, APRD#1[2]@130
> More useful than lines with 'Info' fields like:
> 7 Cmds, SumLen 16, 'FPWR'...
> Since with the latter one has to look at details view to find out what is going
> on (test with the dump on the Wiki, and try to find find out what goes on in
> packets 23 - 32).
> ---
> What is still lacking in both (and a big challenge) is trying to track node
> state (address assignment), CANopen conversations, EEPROM reads, etc. Probably
> far beyond what wireshark should do since one has to have a full capture from
> power on to do a proper analysis, and also keeps state for all nodes (I has
> done some python hacks that analyzes XML dumps from wireshark, but still very
> rudimentary). Better leave that...
> ---
> Summary:
> I don't have any knowledge of ams, ecatmb, ioraw or nv protocols, and hence
> can't test them.
> I would like to get more info in the 'Info' field for multi-telegram packets,
> but my version is not optimal either (just realized that node addressing is
> decimal, and memory addressing is hexadecimal in my Info field, confusing at
> best :-( ...)
> OK for me to commit it, but if nobody else does, I will probably hack the Info
> field the next time I need to do some serious EtherCAT debugging...
I will see what I can do about the E88A4 marked bytes in the packet bytes view
pane as well as a better descriptive name for it.
I see your point on the 'Info' fields and agree, but I cannot find time to
address that right now.
Btw, I found why packet-ams.h did not recompile when changing packet-ams.h. It
was simply a missing dependency in the makefile. I looked through some of the
other plugins and all the ones I went through suffer from the same problem. The
are missing dependencies to the header files. Is this by design perhaps?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
