| ... | ... | @@ -2,9 +2,9 @@ |
|
|
|
This page is designed to document the design choices made while developing the communication adapter.
|
|
|
|
|
|
|
|
## Necessities
|
|
|
|
* The resources folder contains a kind of weird file: `META-INF/services/org.opentcs.customizations.kernel.KernelInjectionModule`, this file contains the Name of the Module class that we developed. This file **has** to exist otherwise your adapter will not run in the kernel.
|
|
|
|
* The resources folder contains a file: `META-INF/services/org.opentcs.customizations.kernel.KernelInjectionModule`, this file contains the Name of the Module class that we developed. This file **has** to exist otherwise your adapter will not run in the kernel.
|
|
|
|
|
|
|
|
*MoveITVehicleCommAdapter.java*
|
|
|
|
### MoveITVehicleCommAdapter.java
|
|
|
|
* This adapter connects with the robot. In order to connect with the robot, you have to go to OpenTCS Plantoverview and add two key value pairs at the Miscellaneous property of your robot. One has to be the key host with the IP-address of the robot and the second one has to be the key port with the port of the robot. If you connect a robot to OpenTCS it will search for those key value pairs, if it does not find them the robot is not able to be connected to OpenTCS.
|
|
|
|
* Every point in OpenTCS has to have a x and y value. These values are sent to the robot so it is able to travel to those coordinates.
|
|
|
|
|
| ... | ... | |
