Commits (5)
-
Andre Hartmann authored
Change-Id: I12f20c93b50159c18216690edf58dcdc78ebe50a Reviewed-by:
Alex Blasche <alexander.blasche@theqtcompany.com> Reviewed-by:
Denis Shienkov <denis.shienkov@gmail.com>
c2856128 -
Andre Hartmann authored
That's totally valid, compatible to cansend, and also stated in the help: '{payload} has 0..8 (0..64 CAN FD) ASCII hex-value pairs'. Syntax: canbusutil <plugin> <device> 123# Change-Id: I4bd3aade2041cd7b4b1eae9779747b0a0f9dc379 Reviewed-by:
Denis Shienkov <denis.shienkov@gmail.com> Reviewed-by:
Alex Blasche <alexander.blasche@theqtcompany.com>
88f5821f -
Andre Hartmann authored
Appearently, CanBusUtil was inspired by SocketCANs cansend, and this does interpret all input as hexadecimal. Further, the data byte following the hash mark '#' were already used in hex, so let's be consequent. Change-Id: I21324eb540ae2792f747dbae49865973d182d2d9 Reviewed-by:
Denis Shienkov <denis.shienkov@gmail.com> Reviewed-by:
Alex Blasche <alexander.blasche@theqtcompany.com>
a2d50ccf -
Alex Blasche authored
Task-number: QTBUG-53277 Change-Id: I24d019696e73171154c8c29a5f76d9fc1737645c Reviewed-by:
André Hartmann <aha_1980@gmx.de> Reviewed-by:
Denis Shienkov <denis.shienkov@gmail.com> Reviewed-by:
Karsten Heimrich <karsten.heimrich@theqtcompany.com>
a2be52c1 -
Karsten Heimrich authored
Use a properly set or calculated value, do not sporadically calculate it inside a sending function. The only place the caluculation shall happen is in setupEnvironment(). Task-number: QTBUG-53767 Change-Id: Id40fd3406bee404b9d44c8ad43a5160622eda2de Reviewed-by:
Alex Blasche <alexander.blasche@theqtcompany.com>
40be986e
Showing