Skip to content

MTConnectError not handled during probe #122

@Allan-VeTech

Description

@Allan-VeTech

If an MT Connect Error are received as response to probe a format error event are raised instead of the MT connect error event which hides the actual error data.

Format error. ContentType=MTConnect.Devices.IDevicesResponseDocument, ResponseDuration=0, Success=False  
        Message: There is an error in XML document (2, 2).  
        Message: <MTConnectError xmlns=''> was not expected.  

The real data received are:

<?xml version="1.0" encoding="UTF-8"?>
<MTConnectError xmlns:m="urn:mtconnect.org:MTConnectError:1.3" xmlns="urn:mtconnect.org:MTConnectError:1.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:mtconnect.org:MTConnectError:1.3 /schemas/MTConnectError_1.3.xsd">
  <Header creationTime="2025-11-17T08:43:50Z" sender="OKUMAOK-xxxxxxx" instanceId="xxxxxxxxxx" version="1.3.0.17" bufferSize="131072"/>
  <Errors>
    <Error errorCode="NO_DEVICE">Could not find the device 'OKUMA-XX.XXXXXX'</Error>
  </Errors>
</MTConnectError>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions