Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect two FEN20s at the same time #21

Open
Fer-ro opened this issue Jul 29, 2020 · 9 comments
Open

Connect two FEN20s at the same time #21

Fer-ro opened this issue Jul 29, 2020 · 9 comments

Comments

@Fer-ro
Copy link

Fer-ro commented Jul 29, 2020

First of all, congratulations on this library, it is very good!
The thing is, I can't connect to two devices
FEN20s at the same time from a PC.
Error:
Only one usage of each socket address (protocol / network address / port) is normally permitted.

Is there any solution for this?

Regards!

@ekorudiawan
Copy link

same issue here when trying to connect two TS-SH controllers, is there any idea to solve?

@jaegenm
Copy link

jaegenm commented Sep 23, 2021

I am having a similar issue as well. I need to connect to multiple devices and send/receive implicit messages. If I change OriginatorUDPPort to anything other than 2222, T_O_IOData is all zeroes. Is there an example showing how to manage multiple device connections?

@jaegenm
Copy link

jaegenm commented Sep 23, 2021

Some additional info:
If I use a unique OriginatorUDPPort for every client object, I can call ForwardOpen for each one, and I can see the actual data in T_O packets in Wireshark. But I get all zeroes out of the T_O_IOData property for every client which I've set OriginatorUDPPort to anything other than 2222.

@ralftar
Copy link

ralftar commented Sep 26, 2021

Originally posted by @ralftar in #16 (comment):

If the library is published on nuget and PRs are welcome, I will contribute with a couple of PRs (including support for multiple implicit messaging devices, connection exception handling)


I have a feeling that this repository is stalled..? Being MIT licensed, some one can of course create a fork, and continue the work. But it requires long time commitment and resources. Also, I think it would be best if @rossmann-engineering, the original author, is still connected to the maintenance in some form.

@Bissetl
Copy link

Bissetl commented Apr 22, 2022

Did any solution to this ever come to light or is the issue still present? I am having the same problem with two AZ-KEP drives

@BLAGit-NP
Copy link

I am having the same problem with two Keyence Camra IV2 and CVX. They are able to communicate simultaneously in explicit mode. But, not in Implicit mode. When I change any .OriginatorUDPPort property from 2222 default, communication stops.

@BLAGit-NP
Copy link

Based on the source code, I suspect the target is not aware that it needs to communicate to a port other than the default.

@BLAGit-NP
Copy link

bool O_T_OwnerRedundant Only for Implicit Messaging True if Multiple Implicit connections are allowed (Standard: TRUE)
bool T_O_OwnerRedundant Only for Implicit Messaging True if Multiple Implicit connections are allowed (Standard: TRUE)

Both properties are True but do not work ...

@myarc-firmware
Copy link

I had the same issue and it looks like the answer is here: https://github.com/campbell-git/EEIP.NET/tree/testing

Since UDP only allows one port per connection, the above repository is a fork from the original, but has an ImplicitConnection which listens on port 2222 while individual clients are added to the listener so when the data arrives, the listener "routes" it to the appropriate place.

I managed to talk to 3 VFDs using Ethernet/IP using that library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants