You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when we, the energy informatics group of the Fraunhofer IOSB-AST, built an AASX file together with a project partner, based on the IDTA 02006-2-0_Template_Digital Nameplate given via http://smt-repo.admin-shell-io.com/, we get the error “Error! Server responded with: Error: Error status: 409”, even though there is guaranteed no network issue, as it works with different files at any given time. We reviewed the generated files multiple times via different programs like the Package Explorer. The errors seems to based on some serialization error, even though all the needed concept descriptions are given.
This stops us from using BaSyx as our AAS framework for the continuous development of an energy market data space. We could also review the files individually.
The text was updated successfully, but these errors were encountered:
we are using a BaSyx Setup based on the provided docker example, using aas-env., aas-reg, aas-disc., and aas-web-ui all based on Version 2. Therefore, I assume we are using the V2 already.
aaronzi
transferred this issue from eclipse-basyx/basyx-java-sdk
Nov 24, 2024
Hello,
when we, the energy informatics group of the Fraunhofer IOSB-AST, built an AASX file together with a project partner, based on the IDTA 02006-2-0_Template_Digital Nameplate given via http://smt-repo.admin-shell-io.com/, we get the error “Error! Server responded with: Error: Error status: 409”, even though there is guaranteed no network issue, as it works with different files at any given time. We reviewed the generated files multiple times via different programs like the Package Explorer. The errors seems to based on some serialization error, even though all the needed concept descriptions are given.
This stops us from using BaSyx as our AAS framework for the continuous development of an energy market data space. We could also review the files individually.
The text was updated successfully, but these errors were encountered: