I have a problem where a MySQL connection is not able to connect to my server, but weirdly enough it has worked before. However, I have before had strange issues where I just could not get it to connect for longer periods and then after troubleshooting for a certain amount of time it would, without any clear causes as to why, fix it.
My block looks like this with connection_ID as 1, but other values also do not work. I don't have any other networking running on the PLC. IP and login info has been censored but has been tested to work and uses the specified authentication explained on the page.
The problem is, when changing the connect tag to TRUE, the status goes to 16#0002 and stays there forever. In the TCP connect region of the client function, the status code rapidly changes between 16#0000, 16#7001 and 16#7002 which I think should just mean that it's connecting and then succeeds, right?
I use a physical PLC 1214C connected through ethernet on port X1.
Wow, while writing this I tried it again after like 2 hours and it connected straight away. So I guess it doesn't really have any priority any more, but still keep the post up because this issue has returned to me several times now.
Thanks so much for reading and helping! It's a great extension overall
I have a problem where a MySQL connection is not able to connect to my server, but weirdly enough it has worked before. However, I have before had strange issues where I just could not get it to connect for longer periods and then after troubleshooting for a certain amount of time it would, without any clear causes as to why, fix it.
My block looks like this with connection_ID as 1, but other values also do not work. I don't have any other networking running on the PLC. IP and login info has been censored but has been tested to work and uses the specified authentication explained on the page.
The problem is, when changing the connect tag to TRUE, the status goes to 16#0002 and stays there forever. In the TCP connect region of the client function, the status code rapidly changes between 16#0000, 16#7001 and 16#7002 which I think should just mean that it's connecting and then succeeds, right?
I use a physical PLC 1214C connected through ethernet on port X1.
Wow, while writing this I tried it again after like 2 hours and it connected straight away. So I guess it doesn't really have any priority any more, but still keep the post up because this issue has returned to me several times now.
Thanks so much for reading and helping! It's a great extension overall