Replies: 1 comment 1 reply
-
This isn't directly supported, but I think you can still make it work. You would probably have to make your own version Unfortunately, I don't know if this will work and I'm unable to try it out. I've been working on a full rewrite (albeit very slowly), so I apologize if you need to dig into those Packet classes. That code is a bit of a mess and I'm working on making it much easier to implement custom functionality. Right now, those classes handle (poorly) both the EtherNet/IP and CIP portions thru subclassing, which can be really confusing and hard to debug. In the new version, something like this should be fairly straightforward to implement, but I have a long way to go and it will be a while before it's ready. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to control an Invertek drive. According to the product documentation, pages 13-14, I need to connect to an application path of:
20 04 24 01 2C 01 2C 06
The 20 04 and 24 01 are standard class code and instance values. The 2C 01 and 2C 06 are O->T and T->O application paths. According to The CIP Networks Library Volume 1, section 3-5.5.1.10, this requires indicating O->T and T->O connection types. For this application, those are POINT2POINT.
As far as I can tell, pycomm3 doesn't (yet) support application connections or paths. Any suggestions on where to start and/or how to approach adding this functionality?
Beta Was this translation helpful? Give feedback.
All reactions