In opentcs-Integration-Example after 6.xx version ，why delete the openTCS-Contrib-Communication-TCP、and openTCS-Example-CommAdapter-Vehicle

[chengqi-wjs]

Do these documents not need anymore? or how to connect with the real Vehicle

[swltr]

@chengqi-wjs Since the VDA5050 driver can now be seen as a reference for a vehicle driver implementation, the example driver that was previously part of the integration example project did not really serve any purpose any more, so it was removed. My suggestion is to use the VDA5050 driver, if your vehicle speaks VDA5050, or to implement your own vehicle driver with the VDA5050 driver as a reference.

[chengqi-wjs]

How should I use the VDA5050 driver you mentioned? If I use the integrated sample version, can I do simulation communication by using a script to simulate a car? Also, how can I connect it to a real car.

[swltr]

Please check the README/documentation at https://github.com/openTCS/opentcs-commadapter-vda5050.

[chengqi-wjs]

openTCS integration project example. Can this sample integration package drive the simulation vehicle in opentcs with vda5050? Is there anything else to configure? Regarding its MQTT connection, my current situation is that the broker can be connected, but the vehicle connection is not yet possible.

[chengqi-wjs]

@chengqi-wjs Since the VDA5050 driver can now be seen as a reference for a vehicle driver implementation, the example driver that was previously part of the integration example project did not really serve any purpose any more, so it was removed. My suggestion is to use the VDA5050 driver, if your vehicle speaks VDA5050, or to implement your own vehicle driver with the VDA5050 driver as a reference.

@swltr Can this sample integration package drive the simulation vehicle in opentcs with vda5050? Is there anything else to configure? Regarding its MQTT connection, my current situation is that the broker can be connected, but the vehicle connection is not yet possible.

[martingr]

I'm not sure what you mean with "simulation vehicle". The VDA5050 driver can be connected to a real vehicle or a simulated/emulated vehicle. As long as the other side speaks VDA5050, the VDA5050 driver doesn't care whether it is a real vehicle or not. As for the configuration, you have to set at least the required properties mentioned at 1 or 2 (depending on the VDA5050 version you want to use).

[freekevinCode]

Add the required configurations to the vehicle at the time of modeling