Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
While working with codesys v2.3 to send data to a wireless modem, we created an application that receives serial data from codesys.
The AT commands come through appropriately and we respond to them: see code snippet and codesys settings.
After we reply with β\r\nβCONNECTβ\r\nβ, we stop hearing anything from codesys, until the timeout time (30s) is reached. Then codesys starts spewing a few unicode characters (such as β??\u0005\0\u0001\0?\u0001B???\0β - can't read in c#) before it breaks with expected (and readable in c#) β+++β.
The question we have is twofold:
What should we implement or change to have codesys send the data after the connect reply?
What do those terminating unicode characters mean?
Hello,
While working with codesys v2.3 to send data to a wireless modem, we created an application that receives serial data from codesys.
The AT commands come through appropriately and we respond to them: see code snippet and codesys settings.
After we reply with β\r\nβCONNECTβ\r\nβ, we stop hearing anything from codesys, until the timeout time (30s) is reached. Then codesys starts spewing a few unicode characters (such as β??\u0005\0\u0001\0?\u0001B???\0β - can't read in c#) before it breaks with expected (and readable in c#) β+++β.
The question we have is twofold:
What should we implement or change to have codesys send the data after the connect reply?
What do those terminating unicode characters mean?
Last edit: Benjames 2022-10-04