| ... | ... | @@ -20,6 +20,6 @@ This page is designed to document the design choices made while developing the c |
|
|
|
* Since we had a limited time frame we were not able to dive into every single method of the communication adapter. We commented in the Javadoc which methods we did not use or which we think are not used.
|
|
|
|
* In OpenTCS you are able to abort a Transport order. However if you do this we did not implement the proper method to handle this yet. Therefore the robot is not able to accept new incoming Transport orders, because it's state is set to `Executing`. If you want to solve this issue you have to implement a method called `abortAssignedOrder` which is called in the `VehicleController`.
|
|
|
|
* ROS and OpenTCS have different states for the robot. We do send the state from the robot back to OpenTCS however we still need to parse it somewhere to meet the requirements of OpenTCS.
|
|
|
|
* Since the limited time frame we had we decided to go for a working product instead of the most secure product. Therefore we recommend to Implement secure sockets, this way our protocol can not be spoofed.
|
|
|
|
* Since the limited time frame we had we decided to go for a working product instead of the most secure product. Therefore we recommend to Implement secure sockets, this way our protocol cannot be spoofed.
|
|
|
|
|
|
|
|
[home](https://git.fhict.nl/I312980/move-it/wikis/home) |
|
|
\ No newline at end of file |
