You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have got recently a new machine that has extensions not only in vocabulary of the probe (as in your Okuma example), but also in components.
Please see attached probe file.
<x:Wire> is the culprit of hanging when XmlReader tries to parse the document.
Actually, the parse hangs forever, and I am afraid it is a bug in .NET generated assembly, as it cannot skip unknown element correctly.
I really dislike that black magic of XmlSerializer and personally prefer an explicit approach you used with DeviceStreams.
Yes, it needs to be rewritten to not use the XmlSerializer. I have ran into similar issues a few times. It should be possible to use source generation based on the SysML model to generate the majority of the code needed. I'll add this to the ToDo list.
Hi Patrick!
Long time since our last talk :)
We have got recently a new machine that has extensions not only in vocabulary of the probe (as in your Okuma example), but also in components.
Please see attached probe file.
<x:Wire> is the culprit of hanging when XmlReader tries to parse the document.
Actually, the parse hangs forever, and I am afraid it is a bug in .NET generated assembly, as it cannot skip unknown element correctly.
I really dislike that black magic of XmlSerializer and personally prefer an explicit approach you used with DeviceStreams.
Any ideas?
Best wishes,
Sergii Gulyk.
Probe-Sodick-VN600Q.txt
The text was updated successfully, but these errors were encountered: