Haltech Elite 1500 OBD Reader
 

One of the few things I really wanted to do was to connect to OBD reader to display the data on to my Android tablet.

I found some android head units and decided to go that route instead. I went with Anroid headunit by Atoto, which comes with Torque app already installed.

For OBD dongle, I bought OBDLink MX, but found out the Atoto headunit was not compatible with this dongle. Luckily, Atoto sent me their own version of the OBD reader that did work, although likely with slower data refresh rate...

Elite 1500 has two CAN ports. I had to wire into Main CAN port with CAN to OBD cable since Auxilary port is taken up by wideband.

Now I have multiple guages on my headunit and no need for gauge pods.

My Gauges on screen so far:
Coolant Temp
Fuel Pressure
AFR
Intake Air Temp
Intake Pressure
Boost Level
Voltage

So far so good.
https://cimg0.ibsrv.net/gimg/www.rx7...6b55d3ead9.jpg
https://cimg9.ibsrv.net/gimg/www.rx7...79249bde58.jpg



​​​​

whats the lag like?

this seems like a lot of work to simply see the gauges.

why not just get an $80 windows tablet and show the Haltech software on the tablet?
and there would be zero lag.

Lag is definitely there, perhaps aboit .5 sec lag. I would not recommend it for any quages that you would rely on for instant response.

As for Windows tablet, Windows is great for diagnosis, but it would be cumbersome having to deal with windows, wait for Haltech software to Connect to ECU.

This setup starts up almost instantly once you turn on the car.

While that Haltech CAN gauge is cool, it's also expensive at $349 given it's just a display. I don't like the idea of having a windows based tablet actively running ESP for display only reasons given the idea of ESP being live to the ECU as a touch screen interface just seems sketchy to me personally.

I'm wondering if the lag would maybe be less severe if using the Haltech CAN to OBDII cable (P/N: HT-135000) between the ECU and the Bluetooth device, but I don't have any experience with such things.

I wouldn't use it to actively monitor wideband O2, boost or anything insanely time critical but it seems like this could allow for a relatively inexpensive way to keep an eye on some of the more general parameters that you otherwise would have to have an excessive number of gauges or a racecar to monitor without a laptop.

Skeese

I am using the Haltech CAN to OBD2 cable. I had to chop off the CAN connector end (4 wires) and hard wire into the Main Connector. CAN High, CAN Low, 12volt, ground.

Elite 1500 comes with 2 CAN connections. One is part of the 30 or so pin main connector, another is Auxiliary Port. Since I had Wideband connected to Aux CAN port, I wired the OBD2 cable to main.

I now have the OBDlink MX dongle to my Tablet, it seems slightly faster, but still not Instant. App is OBDLink
https://cimg6.ibsrv.net/gimg/www.rx7...852999f562.png


Overall, it is fast enough to monitor your Temperatures, Fuel Pressure, and few others. Inexpensive but very effective solution, if you already have Haltech Elite...



​​​​​
​​​

There is a guy on Fabebook that does a CAN gauge as well but for the eleite only.

Is 150 AUD. but I cant find it (FB is blocked from work)

Being can based will be more reactive.

Sorry, I misinterpreted what was said about how the head unit wasn't compatible with the bluetooth device you had so you used theirs. Makes sense now.

Skeese

Found it.

www.facebook.com. eliteautodisplays


https://www.facebook.com/eliteautodisplays/

That thing is tiny

Correct :)

I have Torque on my phone and displaying several different things, but EGT won't display. I'm wondering if it's even possible since it's going through CAN. I would imagine, but it won't come up on any of the EGT choices.

how do you enable it? I have been having issues of it connecting to the ECU but I can connect to the bluetooth adapter no problem. is there a setting that turns this on? I am using torque app as well.

What do you mean you've been having issues connecting it to the ECU? I assume you have the OBD cable from Haltech plugged into either the AUX or main connector.

I have a similar issue. I am able to connect to my OBD2 scanner via Wi-Fi but it seems like whichever diagnostic/OBD2 reader app I use does not communicate with the Haltech ECU. The app connects fine to the reader via ELM but it always gets hung up with the connection profile. I tried connecting the adapter to both the auxiliary CAN port and the CAN port on the main connector. I get the same issue on both ports.

Did you guys enable/assign those connectors for the OBDII cable? The highlighted dropdown boxes are where you select which one you want assigned.

https://cimg4.ibsrv.net/gimg/www.rx7...b0ad7c4a19.jpg
https://cimg5.ibsrv.net/gimg/www.rx7...008a80f027.jpg

correct

this is what I was looking for, I'll give it a try and go again but I don't have a vehicle CAN its just an FC with a racecar harness the haltech is my only CAN setup so if I select the vehicle CAN and enable OBD2 will the bluetooth OBD2 reader get the data then? It sounds like the bluetooth adapter isn't allowed access to the CAN ECU data which got me thinking I need to turn a setting on for this to function.

No you'd want to select Haltech CAN. I have a Haltech harness and the Vehicle CAN connector is the one that comes off the harness the Main Connector is the one on the ECU.

I have my EGT sensors using the vehicle can as you have yours setup, wouldn't let me do both on the same CAN port. I have the haltech harness itself. I have to use main connectors on the haltech can and the OBD2 can is listed as AUX but I am plugged directly into the ECU through the ports on the front cover (USB, USB printer, CAN DTM4pin).

but it works now, thank you!

My EGT sensors don't show on my OBDII, and I just realized it's because the EGT sensors are going through the other CAN connector. I wonder if it would work if they were all going through the CAN hub together.

Are you able to monitor things you wouldn't normally be able to, like EGT sensors (or more specifically, dual EGT sensors), or coolant pressure, etc? I was looking at OBDLink on Amazon and it said you can monitor more things, but I'm not sure how, based on the response from Haltech below. But if so, I'll try to make it work.

After speaking with Nik at Haltech support, this isn't the reason.

"Hello Eric,

The ECU does not send out all data channels via generic OBD-II, just some basic ones, so you won't get EGT there because that is not a generic OBD-II channel, and the only vehicles that have that are diesels and they use different PID's for OBD-II data compared to passenger vehicles. The channel to look for is catalyst temp, we broadcast the EGT there because it is the only channel we can hijack for this.


Air temp is sent out via generic OBD-II data though, so there is probably something in your app being goofy there.


Here are the generic OBD-II channels supported - https://support.haltech.com/portal/e...cle-can-systemCheers!"

I swapped out my Pioneer stereo for a Joying 8" android head unit (thanks Topolino!) and I've been tinkering with it to show the OBDII gauges on it. The Torque app and a cheap adapter work really well, aside from the coolant temp reading fairly slowly. Most if not all other gauges read really fast so I'm not sure what the issue is. I was able to get both EGT sensors on 'catalyst temp' PIDs, but I'm still looking for one to monitor oil pressure and I'm not sure it exists.

I bought an OBDLINK and tried using their app but I can't get the head unit to pair with the adapter. I paired with my phone and I noticed that coolant temp updates a bit faster than on Torque with the cheap adapter, but unless I can find a way to get them to pair, it doesn't really matter. Aside from that, the other readings seem to be the same speed.

If you haven't already done so, try deleting/removing any current Bluetooth connection(s) on the HU. Afterward, try pairing w the OBDlink app. It could be that your available "pairings" are already being consumed by other devices(?).

If the OBDlink app still doesn't pair w your HU, it could simply be incompatible w the Android platform.