Updated rusEFI calibration via CAN (markdown)
This commit is contained in:
parent
e66b414d56
commit
00053b6df6
|
@ -2,7 +2,9 @@
|
||||||
|
|
||||||
With all the electromagnetic interference around the gasoline engine due to sparking CAN physical layer provides the level of reliability above RS232 and USB physical layers.
|
With all the electromagnetic interference around the gasoline engine due to sparking CAN physical layer provides the level of reliability above RS232 and USB physical layers.
|
||||||
|
|
||||||
[ISO 15765-2](PDFs/ISO-15765-2-2004.pdf), or ISO-TP (Transport Layer), helps us exchange up to 4096 packets into which we wrap TS protocol. See also [wikipedia](https://en.wikipedia.org/wiki/ISO_15765-2) https://github.com/rusefi/rusefi/tree/master/java_console/io/src/main/java/com/rusefi/io/can folder has java implementation of ISO-TP packet encoding/decoding.
|
[ISO 15765-2](PDFs/ISO-15765-2-2004.pdf), or ISO-TP (Transport Layer), helps us exchange up to 4096 packets into which we wrap TS protocol. See also [wikipedia](https://en.wikipedia.org/wiki/ISO_15765-2)
|
||||||
|
|
||||||
|
https://github.com/rusefi/rusefi/tree/master/java_console/io/src/main/java/com/rusefi/io/can folder has java implementation of ISO-TP packet encoding/decoding.
|
||||||
|
|
||||||
There is no standard way of communicating with CAN bus on Windows. At the moment rusEFI is focusing on [PCAN by Peak System](https://www.peak-system.com/) and ELM327 options of the Windows side of CAN.
|
There is no standard way of communicating with CAN bus on Windows. At the moment rusEFI is focusing on [PCAN by Peak System](https://www.peak-system.com/) and ELM327 options of the Windows side of CAN.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue