-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No 'aasx-spec' document found in .aasx #281
Comments
Hi @yucef428 , which version of aasx package explorer did you use to create you aasx package: lbr_iiwa.aasx? |
I was using version 3. Can I change the version of the file, or do I have to recreate it? |
You have to download an older version of the aasx explorer (https://github.com/admin-shell-io/aasx-package-explorer/releases/tag/v2023-02-03.alpha) and recreate your aasx-package with it. |
Alternatively, you can use the newest components of BaSyx supporting V3 found here: |
i can't pull it frome docker hub ? |
You can take a look at the example provided here: https://github.com/eclipse-basyx/basyx-java-server-sdk/tree/main/examples |
When I try to pull a server from Docker Hub and implement my AASX, I get this error message: "No 'aasx-spec' document found in .aasx."
![help](https://private-user-images.githubusercontent.com/168128784/328352479-320f2e52-3097-43c2-b557-c56ff7614bbf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU3NzY1NzksIm5iZiI6MTcyNTc3NjI3OSwicGF0aCI6Ii8xNjgxMjg3ODQvMzI4MzUyNDc5LTMyMGYyZTUyLTMwOTctNDNjMi1iNTU3LWM1NmZmNzYxNGJiZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwOFQwNjE3NTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05MjU4ZTVlZDA3YzRkNGVmZDBmMWUwMGM1YjcxNzU0NTZlYzdkNTUxMmQzZDlmMzc0MTY4ZjI3ZWQ1MDlkNDAzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.SViLZo7dFeLeAk-5GHKDHp_AmsiLRF_4PILheIgFkqA)
The text was updated successfully, but these errors were encountered: