Community Forums

Johndale · 12-02-2015, 03:19 PM

Quote:

Originally Posted by Insane938

Crap! Too late. Already ordered. Since your coach is newer than mine, I'm sure it won't work on mine either. Already ordered, so will have to see it I can stop it.

Well that makes two of us having a sell on HUD.
😂

Insane938 · 12-10-2015, 10:38 AM

OK. Got that cheap Bluetooth OBDII reader. Hooked it to my phone using Torque app from Google Store. There is a lot of information available from my "challenged" ECU. It does support engine RPM, coolant temp, and speed. Too small to drive with. Next step... a cheap android tablet.

dpinvidic · 12-10-2015, 11:13 AM

Quote:

Originally Posted by Insane938

OK. Got that cheap Bluetooth OBDII reader. Hooked it to my phone using Torque app from Google Store. There is a lot of information available from my "challenged" ECU. It does support engine RPM, coolant temp, and speed. Too small to drive with. Next step... a cheap android tablet.

Be careful, My Samsung Android tablet would not work with my connect to the reader with the torque app, yet my android phone does. So just buy a tablet that can be returned if you find you can't get it to work.

Dan

dpinvidic · 12-10-2015, 11:25 AM

Quote:

Originally Posted by USMCDevilDog

I have a J1708 6-pin connector and I took a look at the Scangauge D. It has many nice features. Therefore, if I got an adapter for my 6-pin to the OBDII female, then any of the OBDII scanners should work the same as the Scangauge D. Correct??????

This won't work. There are two points to consider in these diesel applications.
1. The electrical interface - voltage levels and connector pin assignments.(can be handled with your adapter)

2. Data format (Protocol). This is different. There is a "Data Packet" that is sent over the can bus. Part of the packet contains a PID (Parameter ID).
Basically it contains the address of who sent it, and what the value is.

The data packet for "RPM" would actually contain different binary data when comparing a ODBII and J1708 packet. So the "scanner" need to know which protocol it is getting. ODBII don't know about heavy trucks.

Regards,

Dan

Insane938 · 12-30-2015, 08:28 AM

Well, I got a 9" KIngpad tablet through Ebay. Works great with my veepeak VP11 reader. Now, I just have to work out where and how to mount it. That will probably be a while as I don't enjoy working at 10 degrees, and I'm too cheap to run the furnace. LOL

peggwn · 06-09-2016, 07:58 PM

Insane938 - My understanding is that OBD1 was designed specifically for California vehicles and is probably not used much any more; OBD2 is more widely used.

Insane938 · 06-10-2016, 10:32 AM

Quote:

Originally Posted by peggwn

Insane938 - My understanding is that OBD1 was designed specifically for California vehicles and is probably not used much any more; OBD2 is more widely used.

peggwn;
As far as I can tell, that is absolutely true. It was, however adopted nationally. In 1999 (in my understanding), ODBII was the law. However, this covered only cars and light trucks. The Ford F53, and the GM Workhorse chassis were considered to be heavy duty trucks, and were exempt from this regulation, (although some did have it installed), until either 2005 or 2008, depending on which website you cite. OBDII has many times the available information compared to the older OBDI spec.

peggwn · 06-11-2016, 08:04 AM

Thanks, Insane938, for the further clarification. When our coach gets back from the shop (for brakes) I'll be checking her out for the ODBII location. I would like to get a Bluetooth version and utilize an iPad we don't used otherwise. Can you enlighten us as to the availability of codes and solutions available for us F53 and especially Workhorse chassis?

peggwn · 06-11-2016, 09:27 AM

Does anyone know if any of the manufacturers of the older chassis provide any information about what data exactly is available using an OBDII? We have a 2000 Workhorse P=32 (see signature) and I'd rather not invest a lot of time and energy trying to figure that out. Thanks, all.

69Stang · 06-12-2016, 06:45 AM

Quote:

Originally Posted by peggwn

Does anyone know if any of the manufacturers of the older chassis provide any information about what data exactly is available using an OBDII? We have a 2000 Workhorse P=32 (see signature) and I'd rather not invest a lot of time and energy trying to figure that out. Thanks, all.

You can buy a cheap OBDII Reader (like $12) that will transmit to your phone. For example I have one that stays plugged in to the OBDII and I use the Torque app (free) on my phone. It will run a report that shows what data it will display. Not perfect though, I have yet to figure out to display transmission temp on my P32 chassis.

olddog49 · 06-12-2016, 12:18 PM

I'd give a "heads up" display a shot. Can not be any worst than trying to read gauges you can't see. I had a 2010 Chager that had gauges that were black on white. Very easy to read. Tried finding ford gauges to MH that were black on white, either I can't find them or unavailable. Just to reduce the glare would be a major improvement . Window tints doesn't work since it throws a double image, dash cover help little since it reduces the shine off the top of the dash. If there is a solution to this problem, I'd sure like to know it.

peggwn · 06-13-2016, 08:20 AM

I have seen a non-reflective sheet (at least I believe that is what it is) simply applies to a windshield to enhance the HUD's display. BTW, the double image is caused by the integral lamination in the windshield; the reflective sheet prevents the dual images.