| ... | ... | @@ -29,7 +29,8 @@ I'll be part of this Group for a while. If you have any question, to which you c |
|
|
|
|
|
|
|
This is a unsorted list of future projects for this Demo.
|
|
|
|
|
|
|
|
1. Porting to [BaSyx v2](https://wiki.eclipse.org/BaSyx_/_Releases_and_Features#Java_Release_2.0) once it gets released. I've provided a branch with a blind port, but since there is [no AAS Server yet](https://github.com/eclipse-basyx/basyx-java-components/issues/25) it can't be tested.
|
|
|
|
1. Porting to [BaSyx v2](https://wiki.eclipse.org/BaSyx_/_Releases_and_Features#Java_Release_2.0) once it gets released. I've provided a branch with a blind port, but since there is [no AAS Server yet](https://github.com/eclipse-basyx/basyx-java-components/issues/25) it can't be tested.
|
|
|
|
The Changes I've made are pretty much self explanatory, see [here](https://gitlab.hrz.tu-chemnitz.de/vws-demo/vws-spielwiese/-/compare/main...basyx-v2?from_project_id=10357). Mostly renaming and the odd method requiring a list instead of just a bare String.
|
|
|
|
2. Implementing the [BaSyx Submodel API](https://app.swaggerhub.com/apis/BaSyx/basyx_submodel_http_rest_api/v1) on an ESP32. This would eliminate the need for a way more poweful machine like the Raspberry Pi, especially, if pushing the relevant AAS and registering can be done, too. This might bring the cost of integration of existing gear into a I4.0 environment down by an order of magnitude.
|
|
|
|
3. Containerizing the components. I've worked extensively using environment variables here, so it should be quite suited for docker images.
|
|
|
|
At least for a "off the shelf" container to run the whole demo virtually on your local machine I can see good use.
|
| ... | ... | |
