... | @@ -38,6 +38,7 @@ At least for a "off the shelf" container to run the whole demo virtually on your |
... | @@ -38,6 +38,7 @@ At least for a "off the shelf" container to run the whole demo virtually on your |
|
5. Implement the lookup of relevant AAS and submodels for the [Light Controller](implementation/Light-Controller-walkthrough#lightcontroller) and [Light Animator](implementation/Light-Animator-walkthrough#lightanimator) by looking up implementations of types of AAS and Submodels instead of relying on a naming convention I made up.
|
|
5. Implement the lookup of relevant AAS and submodels for the [Light Controller](implementation/Light-Controller-walkthrough#lightcontroller) and [Light Animator](implementation/Light-Animator-walkthrough#lightanimator) by looking up implementations of types of AAS and Submodels instead of relying on a naming convention I made up.
|
|
6. ~Reimplement the Demo using other frameworks - or at least evaluate their interoperability, especially after BaSyx v2 gets released.~
|
|
6. ~Reimplement the Demo using other frameworks - or at least evaluate their interoperability, especially after BaSyx v2 gets released.~
|
|
7. Find a way to upload the AAS created in [C#](follow-up/C-Sharp-Module) to the Java AAS Server so it will work like the other lights.
|
|
7. Find a way to upload the AAS created in [C#](follow-up/C-Sharp-Module) to the Java AAS Server so it will work like the other lights.
|
|
|
|
8. Properly debounce the switches on the [Demo Controller](/implementation/Demo-Controller-walkthrough). Currently some buttons get pressed "together" even when only one is pressed (especially the ones for stopping the light controller and update the lights). It could follow [these methods](http://www.ganssle.com/debouncing.htm).
|
|
|
|
|
|
# Sources for the diagrams
|
|
# Sources for the diagrams
|
|
|
|
|
... | | ... | |