+- BlueWave Studio forum (https://bluewavestudio.io/community)
+-- Forum: OpenAuto Pro (https://bluewavestudio.io/community/forum-86.html)
+--- Forum: OBD-II (https://bluewavestudio.io/community/forum-103.html)
+--- Thread: OBD Support -- direct CAN instead? (/thread-1890.html)
OBD Support -- direct CAN instead? - lordloki - 08-16-2020
Is there any interest in / ability to use direct information from the CAN instead of OBDII?
Or any easy way to translate this? I already get can signals that I use for my interface mapping -- (and though I have an ELM adapater, it would be great to just grab it directly using the pican2 that I use instead of having to get the same information in two places).
Thanks for the awesome work as always.
lordloki
RE: OBD Support -- direct CAN instead? - peetereczek - 08-16-2020
(08-16-2020, 06:56 AM)lordloki Wrote: Is there any interest in / ability to use direct information from the CAN instead of OBDII?
Or any easy way to translate this? I already get can signals that I use for my interface mapping -- (and though I have an ELM adapater, it would be great to just grab it directly using the pican2 that I use instead of having to get the same information in two places).
Thanks for the awesome work as always.
lordloki
Following, same here. I'd love to use pican2 instead of additional ELM device in OBD socket
RE: OBD Support -- direct CAN instead? - Daniel_BlueWave - 08-16-2020
Like already we informed about OBD and Elm:
Can bus is kind of interface, like Ethernet, UART, etc. Obd is a protocol - higher layer. There are several variants of Obd protocol and implementing them is huge effort. ELM327 provides abstraction layer independent on car and chosen Obd standard. You talk with Elm327 the same way no matter what car is actually connected. Currently we do not have plans to implement Obd protocol standards directly in OpenAuto Pro. We prefer stick to the Elm327
Similar situation is for direct CAN messages - most of them is car brand specyfic.