Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for specifying non standard EtherNet/IP port number
See original GitHub issueIssue Description
Add support for being able to add port number to IP address in Controller connect method.
Current Behavior
Port number is set to 44818 and cannot be changed.
Expected Behavior
Optionally specify port after IP address in connect method.
e.g. plc.connect('192.168.1.100:5000');
Possible Solution (Optional)
Parse connect IP address string and check for port number. Use port number passed for eip connect. Default to 44818 if no port provided (no change to current operation).
Context
Mapping different ports on a WAN to different PLCs on a LAN.
Steps to Reproduce (for bugs only)
Your Environment
- Package version (Use
npm list- e.g. 1.0.6): - Node Version (Use
node --version- e.g. 9.8.0): - Operating System and version:
- Controller Type (eg 1756-L83E/B):
- Controller Firmware (eg 30.11):
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
They believe correctly.
just FYI there’s many other PLCs with Ethernet/IP support that allow changing the port. Version 2.4 (April 2019) of Koyo Click PLCs now support Ethernet/IP and support changing the port.