Ryan Campbell

Sorry it took so long to respond but I did finally get a chance to dig around for that project and upload it to GitHub. I tested it before I left the office today and it is working with a couple of Turck devices on my desk. Here's a link to my testing branch

Sorry it took so long to respond but I did finally get a chance to dig around for that project and upload it to GitHub. I tested it before I left the office today and it is working with a couple of Turck devices on my desk. Here's a link to my testing branch

Sorry it took so long to respond but I did finally get a chance to dig around for that project and upload it to GitHub. I tested it before I left the office today and it is working with a couple of Turck devices on my desk. Here's a link to my testing branch

Hey Bisl, This was a few years ago so my memory is a bit fuzzy and I don't remember where I put that code. But I was never able to get the default code to work. What I learned though was that basically, some devices will always respond on the default UDP port regardless of claims; in my case it was a Turck FEN20. Proper Unicast UDP should allow port binding, which is why it's frustrating. So I ended up writing a connection manager that was basically a dictionary of connection objects using the built-in...

I'm having this exact same problem but setting the port to anything other than 0x08AE results in the connection timing out. Is the port supposed to be set after ForwardOpen or only after RegisterSession? Do I maybe have to do something with windows firewall?