AEM 30-0334-type direct OBDII wideband for older vehicles. Any takers ?

[Car_Junkie]

Hi, Dr. Mike. Ifyou still have these available I am very interested! (May get 2)

I PM'd you. Please let me know ASAP!

[54inches]

Where are we at with this? Gen3 P59 Silverado needing a fix. I have done all the tricks and just want to get this channel working.

[lsxjunkie]

Hi, Dr. Mike. Ifyou still have these available I am very interested! (May get 2)

I PM'd you. Please let me know ASAP!

Ive tried to get with him. Haven't heard anything lately. He had one for me but I got busy with school and forgot about it. Now I'm really needing one.

[54inches]

Calling Dr. Mike!

[dr.mike]

Sorry, all. Been dealing with some medical issues. I hope to be back to it, soon.

[dr.mike]

OK. Sorry again about the extended absence. I had multiple eye surgeries, on both eyes. They are letting me get back to work, now.

[lsxjunkie]

OK. Sorry again about the extended absence. I had multiple eye surgeries, on both eyes. They are letting me get back to work, now.

I hope you are doing better man. Im still wanting to get the adapter for my Gen 3 TA. I know I delayed on doing it earlier but I was slammed with school and life at that time. Looking forward to hearing from you.

[justintyler]

with a gen 3 truck i installed my x series 30-0334 and it reads an afr, when adding it to my channels on my mpvi3 scanner after re-polling for new pids i am not able to even receive that correct ?wb eq ratio 1 (sae)? as an available pid?

[Alvin]

Gotta know when to give up guys.. Seems like vaporware.

[dr.mike]

Gotta know when to give up guys.. Seems like vaporware.

Close... I had eye surgeries on both eyes, over the last year ( vitrectomies and cataract lenses ), . I am "mostly recovered". But, it is, still, difficult for me to do programming work. It is hard to explain. I can "see". But, it's just not right, unless I am looking directly at it.

. The project is still technically, "open". But, it is, somewhat , superfluous, due to the changes in the MPVI3 licensing, that allows direct connection of the AEM widebands, via CANBus, without need of the "advanced features" option. The direct connection, like that, is, actually better than the J1850 interface, provided by the adapter box.

There are a few test units, out there. But, I have not been able to do firmware updates, since the eye issues.

If you are diabetic, TAKE CARE OF YOUR EYES !

[Gordon-0]

What happened with this project?
I've got an 05 F150, 02 Jeep Wrangler, and 2012 GMC that I'd like to be able to log O2 data for.

[blindsquirrel]

Attachment 150482

[Gordon-0]

thank you blind squirrel for the passive aggressive post... I wasn't sure if anything had changed in the 7 months since that was written.

[blindsquirrel]

thank you blind squirrel for the passive aggressive post... I wasn't sure if anything had changed in the 7 months since that was written.

Exactly what part of it was 'passive'? Or is that just a stand-in label for 'something I do not like'?

[Gordon-0]

Bro, who hurt you? I'm just asking if anyone has heard anything regarding updates on this project since it's something that I would be really interested in purchasing if it ever came to market. Idk why you have such an attitude about it but I guess that's your business not mine.

[Sedlaj1]

As some here know ( as they were involved ), the AEM 30-0334 OBDII enabled wideband was, originally, a project, developed here, on this forum. Basically, it was a partial re-programming of the AEM 30-0300 wideband?s CAN interface to conform to the OBDII standard communications. This allowed the modified 30-0300?s and, later, the proper 30-0334s, to interface, directly, with the HPTuners MPVI/MPVI2 scanners, via the OBDII pass-thru cable. And there was much rejoicing.


But, there was one small(ish) issue. As the 30-0300 was, originally, designed to use its CAN interface for the AEMNet protocol, it did not include the hardware required to interface with vehicles that did not have CAN based ECUs. i.e. most vehicles, prior to 2007.

This left tuners of 1996-2007 OBDII vehicles, which used the J1850 ( VPW and PWM ) interfaces, to fend for themselves, in getting wideband data into the scanners. Either using the Pro version, with the ProLink CAN (which is ideal ), serial data, or, the old AC/EGR analog wiring tricks, each of which have their own issues; and, make dual-channel widebands very difficult to log.

So, having done most of the technical legwork, I am testing the waters here to see how many people would actually be interested in a 30-0334-like solution for the pre-CAN vehicles; specifically, earlier GM, Ford, and Chrysler products that use the J1850 variants, on the OBDII bus.



This would be an extra piece of hardware (as the 30-0300 does not have a J1850 interface) that would take the place of the pass-thru connector cable, used by the 30-0334. It would look like this ( as I already have the housings ) but, with terminals to connect the CAN wires from the wideband(s).

Attachment 112698

It would have the screw-terminals on one side, for the 30-0300 or 30-0310 CANH and CANL wires; and, would allow multiple widebands to be attached and logged, together. I will, probably add a cold-start safety function, as an option, to prevent thermal shock to the sensor?s ceramic elements. i.e. it would not start heating up the sensors until after the engine is stated.

That, pretty much, covers it; a J1850-enabled OBDII adapter for the AEM 30-0300 and 30-0310 widebands.

Looking at the current chip market, it looks like the pricing would be in the $70 to $80 range, depending on the demand volume. But, you do save the cost difference between the 30-0334 and the 30-0300/0310.

So, sharks? how many are up for a direct OBDII cable wideband adapter for the pre-CAN vehicles ( 1996-2007 ) ? This would, obviously, take a bit to get debugged and into production.

'cause I can never "just leave well enough alone."

[Sedlaj1]

Interested sir

[Isaak]

Interested!