Fernando B

Thanks for the PR. I don't how I feel about just adding commas, and rewording one sentence. This is the type of PR I would normally accept for a complete...

I know we've been down this road many many times about UDTs in many issues opened in the past. https://github.com/dmroeder/pylogix/issues/45 https://github.com/dmroeder/pylogix/issues/6 and prob many more... @dmroeder would you suggest that...

> I will be happy to pass the byte array because I already know the structure of my UDT. > I attempted to read a UDT and just send it...

> I worry about the function of write tag. It is safety? If you write to a tag, and you don't know what you're doing, then no, it is not...

Yeah if the limitations of L71 don't allow that many connections then you have to get clever. Another option would be to modify the plc code if you own it,...

@KaloyanR In regards to the timeout use a try catch. https://docs.python.org/3/tutorial/errors.html

@KaloyanR np. Normally you'd want to handle the exception. Print to the console or log, or something else. I guess if the IP doesn't exist, there's nothing to do hence...

I'm all for a connection keep alive option for pylogix as well, I think we've had a fair share of the same question around connection timeout. I think we can...

The quick and dirty way would be to create one connection object per plc, and do not call close, if you have a cleanup function like ctrl + c sigint...

When you're using the `with` context the connection should be closed after going out of scope, so comm.Close() isn't needed. I don't see any other item that stands out as...