MTConnectStreams_1.2 violation of enumeration constraint

[BASA6850]

I want to add the value "PROGRAM_STOPPED" for execution events in MTConnectStreams_1.2.
Therefore I added the lines as showed in the attached pics.

After restarting the service I still get this error message:
'PROGRAM_STOPPED' violates enumeration constraint of 'READY INTERRUPTED ACTIVE STOPPED FEED_HOLD UNAVAILABLE'.The element '{urn:mtconnect.org:MTConnectStreams:1.2}Execution' with value 'PROGRAM_STOPPED' failed to parse.'.

How can I solve this problem?

[wsobel]

The first problem is you are using version 1.2 of the schema. PROGRAM_STOPPED did not exist in 1.2. It was added in 1.3.

You should be using 2.2 (latest) unless there is a good reason to use a legacy version.

You can set schema version in there Devices.xml file or in the agent.cfg SchemaVersion= configuration variable.

Some more info would also be helpful.

[BASA6850]

Hello @wsobel,
thank you for your response.

The agent runs on a virtual machine as a Windows service. There we have this configuration file.

In the folder "Schemas" I replaced the 1.2 files with the 2.2 files.

I uninstalled the existing Windows service and installed it again. After that I can see the MTConnectStreams_2.2.xsd schema.

Should this be enough for replacing schema version?

[wsobel]

You can have all the schemas in that directory. The agent will search for a matching schemas using the SchemaVersion in the cfg file or the version in the namespace from the Devices.xml.

When it locates the matching version, it sets the namespace and schema version to the location of the schema files on disk or uses the public https link.

[wsobel]

Since I can't see the header, I'm not sure what you're pulling in.

[BASA6850]

@wsobel
Is this the Devices.xml?
mazak - original.txt
mazak.txt
I replaced 1.2 with 2.2 in the header.
Do I need to install the windows service again? After restarting the service I can not see the changes I made in the mazak file.

If I want to define the schema in the cfg file how do I add the SchemaVersion correctly?