What features would you request for Carloop 3.0?

alanm 2017-04-24 23:04:56 UTC #21

There might be something in the works (in the next 2 months) that you will really really like in that case!

egarl004 2017-04-24 23:16:58 UTC #22

awwwwwwwww yeahhhhhhhh.... apparently I needed 20 characters to respond

elhajj33 2017-05-16 04:59:53 UTC #23

i would love to see elm327 support to read data from vehicles with older protocols

SinusoidDelta 2017-05-17 05:55:03 UTC #24

I think 3.0 should feature a j2534 or "layer one" pass thru device. J2534 was intended to unify access to embedded protocols:

ISO9141
ISO14230 (KWP2000)
J1850
CAN (ISO11898)
ISO15765
SAE J2610
J1939 (since 2005)

Some resource info:

cyclin_al1 2017-05-29 04:33:22 UTC #25

@SinusoidDelta, I took a list at all the protocols you listed, and it is all possible. However, the Carloop hardware has to be able to work for all the hardware protocols. The rest are communications protocols running on top of that hardware. Any communication protocol can be coded into the firmware as long as you have the right hardware underneath.

In your list, there are only 4 hardware protocols.
1) CANbus, which is already done by Carloop
2) K-Line (the hardware layer for ISO9141, KWP & KWP2000), which I am working on a CarloopRetro to do this; a schematic is already on GitHub. However, I am only managing 30 minutes a month (I do not work for Carloop), so it will be a long time coming.
3) Off-Road
4) Heavy machinery

@elhajj33, you can code firmware to emulate the elm327 on CANbus for Carloop. As mentioned above, you need to have the hardware layer to be able to emulate the elm327 on other protocols. However, once you have the hardware, you can code firmware to do whatever you want, which could be much more than the limited functions of elm327. Don't get me wrong, elm327 emulation is something I would love to see as it is extremely useful, but Carloop allows for much more than that.