c2f1022858
Device: Add network mutex support
2025-10-24 12:12:36 -04:00
c5ba2d8d32
Communication: Add missing CAN error types
2025-02-04 15:15:44 +00:00
9ef01e2d3d
Optional: nonstd to std
2022-07-22 01:27:39 -04:00
f37669139f
MSVC: Resolve warnings
2022-02-21 21:36:20 -05:00
2d6004bed1
CANPacket: Remove unused byte from datastream
2021-11-16 20:04:12 -05:00
ed5132e852
CANPacket: Ensure correct padding when padding by the DLC
2021-05-25 22:19:03 -04:00
76b6ecbf04
CANPacket: Fix invalid length check
...
This case is already checked above, and further
was invalid since the length had already been
translated to the numeric (0-64) value.
2021-05-25 17:23:41 -04:00
21bc4eeff2
Message: Create a type system so non-frame data can be represented
...
This change breaks existing code, hence the version bump, but it's
going to be much less error prone going forward.
2021-05-22 01:58:36 -04:00
21e93d1f73
CAN: Honor the specified dlcOnWire for transmit
2021-05-21 17:38:00 -04:00
98bd7e9c55
add decoding of transmitted, error, and description fields for CAN packets
2020-02-19 09:36:28 -05:00
50dba62a89
Event refactor builds on Windows
2019-06-24 17:59:45 -04:00
255e1e2b90
Added more error logging
2019-06-13 16:01:35 -04:00
519e64fb17
Added error checking to functions called from Communication
2019-06-13 16:01:35 -04:00
7cf0ec5f4f
Rename timestampMultiplier to timestampResolution
...
We've also decided to leave it out of the message structures since, for most uses going forward, it will not be needed.
Anyone who wants the timestamp resolution can always make the inexpensive device call to get it.
2019-05-06 12:32:04 -04:00
5a6a1c990a
Support CAN FD Error State Indicator
2019-04-17 17:03:38 -04:00
37b83e0506
Automatically pad CAN FD messages out
2019-04-17 16:50:11 -04:00
c94ace87f9
Timestamp information for CAN frames
2019-01-03 17:08:47 -05:00
d37d5bb23e
Support Ethernet and Broad-R Reach TX and RX
2018-12-21 20:32:27 -05:00
Jonathan Schwartz
Kyle Schwarz
Paul Hollinsky
Jeffrey Quesnelle
EricLiu2000