Per this comment it seems the issue with Japanese text might be in this adapter.
I see there are many references to ASCIIEncoding in MTCAdapter.cs. If I run the adapter as is with the japanese test text the agent will display this message in the XML stream:
<Fault dataItemId="systemCondition" timestamp="2026-01-07T23:26:19.8203954Z" sequence="80" nativeCode="1111" type="SYSTEM">????????????</Fault>.
If I change all the ASCIIEncodings to UTF8Encodings I get the following output:
<Fault dataItemId="systemCondition" timestamp="2026-01-07T23:16:17.1481955Z" sequence="80" nativeCode="1111" type="SYSTEM">ストロークエンド軸あり</Fault>
The text is formatted in HTML escape sequences but they are the correct values. I'm unsure why changing the ASCIIEncoings to UTF8Encodings isn't enough.
The whole line I send from the adapter to the agent is "2026-01-07T22:32:50.8567651Z|systemCondition|FAULT|1111|||ストロークエンド軸あり".
Per this comment it seems the issue with Japanese text might be in this adapter.
I see there are many references to ASCIIEncoding in MTCAdapter.cs. If I run the adapter as is with the japanese test text the agent will display this message in the XML stream:
<Fault dataItemId="systemCondition" timestamp="2026-01-07T23:26:19.8203954Z" sequence="80" nativeCode="1111" type="SYSTEM">????????????</Fault>.If I change all the ASCIIEncodings to UTF8Encodings I get the following output:
<Fault dataItemId="systemCondition" timestamp="2026-01-07T23:16:17.1481955Z" sequence="80" nativeCode="1111" type="SYSTEM">ストロークエンド軸あり</Fault>The text is formatted in HTML escape sequences but they are the correct values. I'm unsure why changing the ASCIIEncoings to UTF8Encodings isn't enough.
The whole line I send from the adapter to the agent is "2026-01-07T22:32:50.8567651Z|systemCondition|FAULT|1111|||ストロークエンド軸あり".