The Open Commissioning Assistant is a portable Desktop Application to connect external systems via plugins and make the data available to Unity. Enabling a dotnet environment with full support for dependencies and nuget packages.
- Assistant
- Plugin for PlcSimAdvanced
- Plugin for OfficeLite
- Plugin for RobotStudio
More plugins available on request (RoboticsSuite, SimitSharedMemory, Modbus ...)
.NET Desktop Runtime 10.0.x- Plugins may require additional dependencies
Plugins enable the Assistant to connect to external systems such as PLCs, Robot controllers and other control data sources, making this data available for Unity.
Typical use cases:
- Cyclic communication with PLCs
- Cyclic communication with Robot controllers
- Acyclic data handling
- Create a folder named
Pluginsin the directory of theOC.Assistant.exe. - Move the unpacked plugin folder into the
Pluginsfolder. - Start the
OC.Assistant.exeapplication. - The Assistant will search for
*.pluginfiles and load compatible assemblies.
- Create a new instance of a plugin using the
+button. - Configure the plugin instance with required settings.
- When starting, the plugin variables become available for use in Unity.
TwinCAT can be used to act as a co-simulation for simulating behaviour models in realtime and making device data available for the Unity project.
We welcome contributions from everyone and appreciate your effort to improve this project. We have some basic rules and guidelines that make the contributing process easier for everyone involved.
- For non-trivial changes, please open an issue first to discuss your proposed changes.
- Fork the repo and create your feature branch.
- Follow the code style conventions and guidelines throughout working on your contribution.
- Create a pull request with a clear title and description.
After your pull request is reviewed and merged.
Note
All contributions will be licensed under the project's license.
Please follow these naming conventions in your code:
| Type | Rule |
|---|---|
| Private field | _lowerCamelCase |
| Public field | UpperCamelCase |
| Protected field | UpperCamelCase |
| Internal field | UpperCamelCase |
| Property | UpperCamelCase |
| Method | UpperCamelCase |
| Class | UpperCamelCase |
| Interface | IUpperCamelCase |
| Local variable | lowerCamelCase |
| Parameter | lowerCamelCase |
| Constant | UPPER_SNAKE_CASE |
- Keep changes focused: Submit one pull request per bug fix or feature. This makes it easier to review and merge your contributions.
- Discuss major changes: For large or complex changes, please open an issue to discuss with maintainers before starting work.
- Commit message format: Use the semantic-release commit message format.
- Write clear code: Prioritize readability and maintainability.
- Be consistent: Follow existing coding styles and patterns in the project.
- Include tests: It is recommended to add or update tests to cover your changes.
- Document your work: Update relevant documentation, including code comments and user guides.
We appreciate your contributions and look forward to collaborating with you to improve this project!