Further simplification
This commit is contained in:
parent
a8a4291eae
commit
b459fb5caf
|
@ -31,15 +31,15 @@ Coolant temperature | 864 | `D - 40` |
|
|||
Engine oil temperature | 864 | `C - 40` |
|
||||
|
||||
Below is a table with a few more data channels that might be useful for more
|
||||
detailed analysis. When adding more channels, be aware that it might negatively
|
||||
affect the update rate of the more essential channels, due to limited Bluetooth
|
||||
bandwidth. However, the communication protocol in RaceChrono is smart enough to
|
||||
optimize Bluetooth usage if multiple channels share the same CAN ID. As a
|
||||
general rule, if a new channel has the same CAN ID as an existing channel (such
|
||||
as "Throttle position" using the same CAN ID 320 as "Accelerator position"),
|
||||
then adding it should not affect the update rates. Adding a channel based on
|
||||
a new CAN ID (such as "Wheel speed FL") will likely affect the update rates of
|
||||
all other channels.
|
||||
detailed analysis. When adding more channels, be aware that it will increase
|
||||
the file size of your data logs, and might negatively affect the update rate of
|
||||
the more essential channels, due to limited Bluetooth bandwidth. However, the
|
||||
communication protocol in RaceChrono is smart enough to optimize Bluetooth usage
|
||||
if multiple channels share the same CAN ID. As a general rule, if a new channel
|
||||
has the same CAN ID as an existing channel (such as "Throttle position" using
|
||||
the same CAN ID 320 as "Accelerator position"), then adding it should not affect
|
||||
the update rates. Adding a channel based on a new CAN ID (such as "Wheel speed
|
||||
FL") will likely affect the update rates of all other channels.
|
||||
|
||||
Channel name | CAN ID | Equation | Notes
|
||||
------------ | --- | -------- | -----
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 191 KiB |
Binary file not shown.
Before Width: | Height: | Size: 147 KiB |
Loading…
Reference in New Issue