openTCS 4.20.0 released
gradlew cloneProject fails
Got a positive feedback from JayMcGee via private message. I'm closing this ticket.
Hello JayMcGee, with openTCS-Example-4.18.0-src we reorganized some *.gradle files and unfortunately this one slipped through. We have just release openTCS-Example-4.18.1-src which should fix this problem. Can you confirm that the new release solves the problem for you too, so that we can close this ticket?
openTCS 4.18.0 released
openTCS 4.17.0 released
openTCS 4.16.1 released
openTCS 4.16.0 released
openTCS 4.14.0 released
Hello Marco, JDK8 is definitely recommended since we are still developing on JDK8 at the moment. Regarding your problem with the vehicle position, can you please create another ticket describing the problem more in detail? Not sure if I completely understood the problem.
Hello Marco, thanks for reporting. We're looking into the problem. Using Java 8 we didn't experience the reported issue yet. Is Java 9 a special requirement in your use case? If it's not, you could switch to Java 8 in the meantime.
Thanks for reporting the issue. It probably will be fixed with the next release version of openTCS.
Dynamic re-routing of vehicles is indeed not possible at the moment but it's a feature we are aware may be desired in cases of locked paths for example. To realize this, adjustments to at least the DefaultDispatcher and DefaultRouter may be necessary. Keep in mind that dynamic re-routing also yield to some special cases that need to be taken care of (e.g. clearing a vehicle's order buffer if it already received a command to use a now locked path).
Did you have a look at the developer's guide in the openTCS distribution's documentation? Chapter 4.3 (link) describes how to develop vehicle drivers. Basically you have two options: Implementing VehicleCommAdapter or extending BasicVehicleCommadapter. See the abstract class BasicVehicleCommAdapter and its methods connectVehicle()/disconnectVehicle(). These would be the entry/exit point for your TCP communication, for example. Also see the network application framework Netty. In the past we had good...