Let me start by saying thank you very much for creating such a great tool! It has come in quite handy in the past and I have been unable to find any other open-source implementations that provide this functionality,
It is with this in mind that I lay out the following flaws which, if fixed, I believe would greatly improve the future usability of your already fantastic work:
Discovery of object classes - that are present in a deviceThe program uses the GetAttributesAll service which is not required to be implemented. A class that is present may but does not support the GetAttributesAll service will return "Service Not Supported". If an object is truly not present the message router would return an error of "Path Destination Unknown". In such instances it would be nice to still have the class appear in the list during auto-discovery.
Class Attributes - The program does not support the addition of class based attributes. Per the EIP spec the class itself may define attributes to describe it self, much like static members of a class. One of the most important of these is the object's major/minor revision number, which may change how the object may be implemented.
Hex display of Class/Instance/Attribute Ids - The vast majority of documentation displays these identifiers in hex notation. The option to display these items in hex would keep me from constantly having to translate.
Class Sorting - When I auto-discover a device the order in which the object's classes attach theselves to the node in the browser seems entirely random. It would be much more helpful to have these items listed in order of class Id. For example:
Concerning discovery, I think Codesys in it's free version don't accept this service, so it's a test device for me (otherwise my wago plc cannot be used, service is supported).
For static class Attributs the explorer trys to get them using a Get_Attributes_All and displays them from #1 to #7, but right if this service is not implemented the values don't appears in the properties grid, and you cannot query it one by one. Should be corrected also in a near future. Maybe I will always puts them in the tree from 1 to 7, or at least #1.
Hex or decimal could be a settings parameter yes. I don't have any documentation with hex but if it exist why not!
For the class after auto-discover, the order depends on the list given by the remote device, but sure a clean order will be better, and quite simple to implement.
In French Attribute is without e !
Thank you.
Bye.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Let me start by saying thank you very much for creating such a great tool! It has come in quite handy in the past and I have been unable to find any other open-source implementations that provide this functionality,
It is with this in mind that I lay out the following flaws which, if fixed, I believe would greatly improve the future usability of your already fantastic work:
Discovery of object classes - that are present in a deviceThe program uses the GetAttributesAll service which is not required to be implemented. A class that is present may but does not support the GetAttributesAll service will return "Service Not Supported". If an object is truly not present the message router would return an error of "Path Destination Unknown". In such instances it would be nice to still have the class appear in the list during auto-discovery.
Class Attributes - The program does not support the addition of class based attributes. Per the EIP spec the class itself may define attributes to describe it self, much like static members of a class. One of the most important of these is the object's major/minor revision number, which may change how the object may be implemented.
Hex display of Class/Instance/Attribute Ids - The vast majority of documentation displays these identifiers in hex notation. The option to display these items in hex would keep me from constantly having to translate.
Class Sorting - When I auto-discover a device the order in which the object's classes attach theselves to the node in the browser seems entirely random. It would be much more helpful to have these items listed in order of class Id. For example:
PS Finally, and I promise you this is just me being nit-picky, the word attribute is spelled with an 'e' at the end.
Again, thank you VERY much for the great tool you have developed. I look forward to its continual improvement!
Hi,
Concerning discovery, I think Codesys in it's free version don't accept this service, so it's a test device for me (otherwise my wago plc cannot be used, service is supported).
For static class Attributs the explorer trys to get them using a Get_Attributes_All and displays them from #1 to #7, but right if this service is not implemented the values don't appears in the properties grid, and you cannot query it one by one. Should be corrected also in a near future. Maybe I will always puts them in the tree from 1 to 7, or at least #1.
Hex or decimal could be a settings parameter yes. I don't have any documentation with hex but if it exist why not!
For the class after auto-discover, the order depends on the list given by the remote device, but sure a clean order will be better, and quite simple to implement.
In French Attribute is without e !
Thank you.
Bye.
Thanks for the update. The changes are great. I'll post some followup on other issues in a separate thread.