vehicle communication class should not create connection code from the ground up
We should abstract the communication and connection layer to a simple IO abstract object. Example:
- AbstractLink
- UdpLink
- TcpLink
- SerialLink
- FileLink
All classes share a simple logic:
- connect(QString): connect("udp:0.0.0.0:14550"/"serial:/dev/ttyUSB0:115200"/...)
- isOpen()
- newData(QByteArray)
- write(QByteArray)
Everything related to writeDatagrams, clients, serial timer latency and everything else should be provided and done by the classes and not by vehicle side.
Edited by patrick pereira