mtconnect / adapter

MTConnect adapter framework
90 stars 76 forks source link

Best practices advice for devices.xml file #15

Open JorgeCorvallis opened 5 years ago

JorgeCorvallis commented 5 years ago

I just had an " issue" with the agent where I had to switch to SchemaVersion = 1.3 in the config.cfg file in order for it top display any data

This brings up my question: I "assume" this is related to my device/xml file setup section see JPEG [RED SQUARE] ? More important - these references seem to be pointing to an online location now? Is that the proper way of doing this or should these references be located on site ? - I'm not necessary locking for a solution here - I'm just trying to understand how this usually is implemented .. As this agent will be installed in a location with XXX machines from different machine builders I would assume the company IT department would want all agent(s) to pull from the same reference location (Locally I assume) Am I on the right path here with my thinking or am I missing something ? :-) = I assume the Company IT department will provide the link(s) to the actual reference locations /schemas to be used. image

wsobel commented 5 years ago

If you consult the readme or look at the docs on github, you can specify the schema location for the files as well as style sheets. The example cfg file shows how to configure these items and the schema files are shipped with. The schema files are also hosted online of people wish to use them. A custom schema file can also be associated with any of the documents to provide extended type in your own namespace.

Best Will

(Sent from mobile)

On May 4, 2019, at 09:06, JorgeCorvallis notifications@github.com wrote:

I just had an " issue" with the agent where I had to switch to SchemaVersion = 1.3 in the config.cfg file in order for it top display any data

This brings up my question: I "assume" this is related to my device/xml file setup section see JPEG [RED SQUARE] ? More important - these references seem to be pointing to an online location now? Is that the proper way of doing this or should these references be located on site ?

  • I'm not necessary locking for a solution here - I'm just trying to understand how this usually is implemented .. As this agent will be installed in a location with XXX machines from different machine builders I would assume the company IT department would want all agent(s) to pull from the same reference location (Locally I assume) Am I on the right path here with my thinking or am I missing something ? :-) = I assume the Company IT department will provide the link(s) to the actual reference locations /schemas to be used.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.