Comments (24)
wsobel
commented on August 20, 2024
Will check into it now
from cppagent_dev.
hulinning2
commented on August 20, 2024
still not working for schema 1.5
I got this error on RC7
Cannot find assets
from cppagent_dev.
wsobel
commented on August 20, 2024
Do you have a debug log from the agent? It may be helpful to track down the issue.
…Sent from my iPad
On Oct 22, 2021, at 08:42, Linh Huynh ***@***.***> wrote:
still not working for schema 1.5
I got this error or RC7
Cannot find assets
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
from cppagent_dev.
hulinning2
commented on August 20, 2024
Here is the log.
I see a lot of errors.
from cppagent_dev.
wsobel
commented on August 20, 2024
Can you send me the adapter stream? There looks like a parsing error in for the cutting tool assets. I need to see what's happening.
This is probably unrelated
from cppagent_dev.
hulinning2
commented on August 20, 2024
Here is the output stream. I change the .xml to txt
view-source_localhost_5000_current.txt
from cppagent_dev.
wsobel
commented on August 20, 2024
i'll take a look after my next meeting.
from cppagent_dev.
wsobel
commented on August 20, 2024
ok. I was looking for the adapter stream coming into the agent. The log has a lot of errors when parsing the cutting tool data and we need to see what's happening.
from cppagent_dev.
wsobel
commented on August 20, 2024
found some issues...
from cppagent_dev.
wsobel
commented on August 20, 2024
The routing was working, but it was returning an error instead of an empty list.
from cppagent_dev.
wsobel
commented on August 20, 2024
Regarding the error log, the assets are being rejected by the parser. Can you send the output from the adapter before it gets to the agent? I need to see why the cutting tool assets are not being parsed correctly.
from cppagent_dev.
hulinning2
commented on August 20, 2024
Date:10/22/2021 Time:2:28:22 PM Information - Tool Asset = 2021-10-22T15:35:03.9965155Z|@asset@|123456.10|CuttingTool|--multiline--ABCD
AVAILABLE1310000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>
--multiline--ABCD
from cppagent_dev.
wsobel
commented on August 20, 2024
Did that parse with the old agent? It does not look like a cutting tool XML. The AVAILABLE1310000 is not XML.
The new XML parser is stricter about the content it receives where the old one would pass anything through. When you say CuttingTool it is using a validating parser to interpret the data.
I would be interested in if this worked, and if so, what the output was? and what is the result you want to get.
from cppagent_dev.
hulinning2
commented on August 20, 2024
It does not look like a cutting tool XML. The AVAILABLE1310000 is not XML. My mistake when copying the string
This is what adapter sending to agent for each tool. It does work with agent version 1.3.0.14 using schema 1.5
Of course, it also refers to extended schema for Cutting Tool
Date:10/22/2021 Time:4:06:58 PM Information - Tool Asset = 2021-10-22T19:53:15.9088053Z|@asset@|123456.10|CuttingTool|--multiline--ABCD
AVAILABLE1310000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>
--multiline--ABCD
from cppagent_dev.
wsobel
commented on August 20, 2024
I think the issue is the new parser is stricter meaning it verifies the entire structure and makes sure it is valid. If you change it from CuttingTool as the asset type to something else, it will just use the raw text. The validation is something in the new entity model to make sure we can represent things correctly. I assume the old parser just gave up and treated this as raw content.
If you wanted to try to create a real cutting tool model, that would be preferable. The assets fix is almost complete w/ CI/CD. It will now return an empty …/<Assets/> tag.
from cppagent_dev.
hulinning2
commented on August 20, 2024
I am really not sure how to create a real cutting model. Can you give some example or any document?
This what my cutting tool based on 1.5 spec.
from cppagent_dev.
hulinning2
commented on August 20, 2024
Will,
RC10, it recogized the command but returns zero records although it has 5 assets.
Thanks
from cppagent_dev.
wsobel
commented on August 20, 2024
Are you sure the assets were correct? Last time there were multiple errors in the information sent to the agent. Please attach the logs and the header from the response.
(Sent from mobile)
… On Oct 26, 2021, at 06:51, Linh Huynh ***@***.***> wrote:
Reopened #162.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
from cppagent_dev.
hulinning2
commented on August 20, 2024
Will,
There are still a lot of errors in the log. I would like to know if this new agent is fully compatible with older MTConnect spec 1.5 or not.
What should I do if it is not compatible with MTConnect spec 1.5?
My assets is working correctly with agent 1.5.x.x
this is the reponse
from cppagent_dev.
wsobel
commented on August 20, 2024
The issue last time was the cutting tools you were sending were not cutting tools. The new xml parser is stricter and makes sure the content follows the standard to its best ability.
Can you attach the data you are sending to the agent again and we can discuss. Once the data is correct, it will work as expected.
(Sent from mobile)
… On Oct 26, 2021, at 08:33, Linh Huynh ***@***.***> wrote:
Will,
There are still a lot of errors in the log. I would like to know if this new agent is fully compatible with older MTConnect spec 1.5 or not.
What should I do if it is not compatible with MTConnect spec 1.5?
My assets is working correctly with agent 1.5.x.x
agent.log
this is the reponse
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
from cppagent_dev.
hulinning2
commented on August 20, 2024
Here is one asset sending to agent:
Date:10/26/2021 Time:9:46:31 AM Information - Tool Asset = 2021-10-26T12:25:52.6009877Z|@asset@|123456.10|CuttingTool|--multiline--ABCD
AVAILABLE1310000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>000<x:ItemCutterStatus xmlns:x="okuma.com:OkumaToolAssets">AVAILABLE</x:ItemCutterStatus><x:ItemProgramToolGroup xmlns:x="okuma.com:OkumaToolAssets">0</x:ItemProgramToolGroup>
--multiline--ABCD
from cppagent_dev.
wsobel
commented on August 20, 2024
This is not a cutting tool asset model. I'm going to close this issue since it is not an agent bug and work with you directly to produce cutting tool assets.
from cppagent_dev.
wsobel
commented on August 20, 2024
Found an issue when parsing extended elements for cutting items.
from cppagent_dev.
wsobel
commented on August 20, 2024
Added fix to support the extended entities with an xmlns. Needed a few changes. Will be RC 11.
from cppagent_dev.
Related Issues (20)
- Support gzip files from directories
- Implement dynamic data validation based on schema version HOT 1
- Trouble Parsing data on latest release. HOT 11
- Update the JSON representation based on Agent WG issue 2807
- agent stops when devices.xml is changed HOT 19
- agent stops when devices.xml is changed using 2.0.0.12 RC17 HOT 7
- agent stops when devices.xml is changed using 2.0.0.12 RC18 HOT 2
- agent fails to reconnect if adapter configured by hostname and not IP HOT 4
- Agent stops when agent.cfg and devices.xml are changed from MTConnect spec 1.2 to 1.3 in RC21 release x86 HOT 3
- Agent stops when agent.cfg and devices.xml are changed from MTConnect spec 1.2 to 1.3 in RC22 release x86 HOT 3
- Agent stops when agent.cfg and devices.xml are changed from MTConnect spec 1.2 to 1.3 in RC23 for x86 HOT 3
- Docker Agent gives error when running with 'agent run', not with 'agent debug' HOT 5
- Agent cannot detect the new MTConnect spec that has been changed in the devices.xml file. RC4 for x86 HOT 5
- MQTT Sink / Source Username and Password Config HOT 4
- Configuration with MQTT sink throws "packet_id exhausted error" after few hours of running HOT 9
- Style sheet not displaying the values for specifications.
- QIF document addition removes XML nodes HOT 3
- Add dynamic device creation for agent adapter source HOT 1
- Unified MQTT Topic and Payload structure HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cppagent_dev.