<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for Benjames</title><link href="https://forge.codesys.com/u/bsuijdendorp/activity/" rel="alternate"/><id>https://forge.codesys.com/u/bsuijdendorp/activity/</id><updated>2022-10-04T14:34:21.555000Z</updated><subtitle>Recent activity for Benjames</subtitle><entry><title>Benjames modified a comment on discussion Codesys V2.3 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6" rel="alternate"/><published>2022-10-04T14:34:21.555000Z</published><updated>2022-10-04T14:34:21.555000Z</updated><author><name>Benjames</name><uri>https://forge.codesys.com/u/bsuijdendorp/profile/</uri></author><id>https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6</id><summary type="html">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...</summary></entry><entry><title>Benjames modified a comment on discussion Codesys V2.3 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6" rel="alternate"/><published>2022-10-04T14:33:17.228000Z</published><updated>2022-10-04T14:33:17.228000Z</updated><author><name>Benjames</name><uri>https://forge.codesys.com/u/bsuijdendorp/profile/</uri></author><id>https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6</id><summary type="html">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...</summary></entry><entry><title>Benjames posted a comment on discussion Codesys V2.3 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6" rel="alternate"/><published>2022-10-04T14:29:45.702000Z</published><updated>2022-10-04T14:29:45.702000Z</updated><author><name>Benjames</name><uri>https://forge.codesys.com/u/bsuijdendorp/profile/</uri></author><id>https://forge.codesys.com/forge/talk/CODESYS-V2/thread/03832adeaf/?limit=25#cea6</id><summary type="html">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...</summary></entry></feed>