There are a few things here that jump out at me.
- Port 8? Do you mean port 80? Either way, those ports are lower than 1024 and that’s a problem.
Take a look at this post for why this matters: Groov EPIC and RIO firewall tips
If it is port 80, then you have another problem, and that is EPIC listens for inbound traffic on port 80 and internally redirects it to port 443. This way no matter what a user puts into their ULR, either http, or https, the EPIC will hear and only reply on https.
A user cant change this port 80 behavior.
If you can configure your data logger to use a port higher than 1024, things will be a lot smoother for you. - You cant run your datalogger software on the EPIC. What you need to do is understand what the ‘simple string’ is that the software sends to the logger and program the EPIC to send that string and listen for the reply. You can create strings in PAC Control, or by something like Python, I think you can do it in Codesys, but I am not a Codesys guy.
- You are getting the -10065 error for 2 possible reasons.
a. The comm handle on the EPIC does not know how to reach the IP address, so you get a no route to host.
This gets back to my question from a few days ago. If you have a static IP in the EPIC, you need a static gateway and DNS.
b. Your last post said the datalogger uses port 8, but your comm handle seems to be using port 44818.
c. The -50 error is because there is nothing listening on any port on the laptop and so their is no connection with any service within the timeout period. The datalogger is the only thing listening in this setup, so only the correct IP and port of the datalogger will respond to the simple string.