When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Dash logic has tried to add stuff for me before (i.e. AEM 30-0333 CAN data) but it never worked right... I suspect it's possible if I could tell them exactly what I needed
Maybe HPT would be so kind as to tell me what address alcohol % is on an E40
If you see it displayed properly on a scanner channel, just select "add channel", sort the list of available channels by "number", then type the name "ethenol" and it will show you the PID for that channel name. It has to be the same 82 as the E38.. uh, I think it has to be
LOL. I'm sure you know this since you're light years ahead of me on HPT stuff
Looked into the PID thing a little more this morning... Seems that SAE has standardized some PIDS to be common across all cars and 82 is the standard for ethenol %. There are no "rules" to non standardized PIDS other than adhering to the CAN frame layer which excludes content, and vehicle manufacturers can have as many custom, non documented ones as they like. Not sure how the custom PID numbers and SAE numbers don't get "tangled up" but maybe PIDS 0-1000 are reserved for SAE, 6000-8000 custom, etc. There has to be some regulatory body or agency controlling PID numbers and maybe they dole them out in blocks to vehicle manufacturers like MAC addresses are doled out to manufacturers of devices connected to the internet .. ??????
Prior to SAE 82 PID, GM probably supported eth % through a custom for their use only and HPT figured it out. The biggest problem with interpreting custom PIDs is knowing the format of the response. Is 50.0% alcohol represented by the response "50.0" (4 bytes of ASCII) or 1F4 (1 byte of HEX * 100)/....
So in order to get Dash Logic to show the data you would need to know the response format, maybe someone at HPT will share that with you.
The 0311 gauges have been tested and verified to operate across a large spectrum of vehicles. The unit can only read for instance what a smog station can read, not what a dealer can through a factory scanner. Our instructions also state that our unit may not support every PID on your vehicle. The gauge can query the vehicle for a list of the available PIDs and display the ones which are supported by the gauge. If you scroll and cannot find it in the list, the PID is not supported.
WTF? I read that 4 times and I don't even know what it means.
Maybe by "smog station" he means DMV or some other emissions checkpoint that only uses SAE PIDs. You might have an earlier OS in your E38 than mine and 0x52 might not be supported basically putting you in the exact situation as Carson (stopped trying to spell Shpenxel correctly).
If eth % shows properly in the HPT scanner, it would be good info if you can see what PID number HPT is using for eth. Gotta hunch it's not 0x53 and 6020 like the E40.
End result is you're **** out of luck. sorry
right click "add channel"
then click on the "sort by ID" icon on the top of the channel list
Then type "Ethenol" and see what number PID is using
This also explains why you can't add a channel to the scanner unless connected to the car or setting up a "virtual" vehicle because it needs to poll the car in real time to see what PIDs it's capable of
So it seems this new OBD gauge is screwing up the CAN. Thought it was only when downloading a tune but the scanner hangs when the gauge is connected. The suck part is I attached the CAN wires on the gauge to the CAN wires on back of the WB gauge inside the back of the pillar cover and had to rip it out and run separate CAN wires to keep WB working while scanning.
I'm officially in the "This gauge sucks" camp. Turns out I had 3 DTCs active in the ECM and this gauge showed "none". Worse yet, I wasted 3 days tuning my VE map when fuel/airflow was altered because of the DTCs and now the map is screwed up after clearing them
That's pretty disappointing; who would have thought it would cause so many issues. Going to move to a dashlogic or some other multigauge?
On a side note, I'm joining the 30-0333 wideband club, but I'm waiting for the pins to come in so that I can wire it to the dashlogic before I install it (I also emailed the dashlogic folks to see about reading it over CAN and they just told me that "Sorry this isn't how dashlogic works" when I asked if they'd add support so we shouldn't hold our breath).
I'll just keep the gauge so there's not a blank hole in that top pillar location. Over my 10k build budget already and not spending any more till holidays are over so no dash logic, gauges, etc.. The 30-0333 is nice and should work out well, good luck with it.
That's pretty disappointing; who would have thought it would cause so many issues. Going to move to a dashlogic or some other multigauge?
On a side note, I'm joining the 30-0333 wideband club, but I'm waiting for the pins to come in so that I can wire it to the dashlogic before I install it (I also emailed the dashlogic folks to see about reading it over CAN and they just told me that "Sorry this isn't how dashlogic works" when I asked if they'd add support so we shouldn't hold our breath).
They tried once already for me and weren't able to get it working. Sent me some beta firmware to try but it didn't work.
Wish they'd figure it out--I would have sent them my spare -0333 if it had helped but they stopped responding to me
The 0-5V output on that WB is very accurate. I've logged it on top of the CAN one and it was scary close, maybe .001 second delay.
One point--you HAVE to run the ground wire from the ground pin output to dash logic. It is it's own little circuit that doesn't share the power ground, so without it it won't work. Ask me how I know..
They tried once already for me and weren't able to get it working. Sent me some beta firmware to try but it didn't work.
Wish they'd figure it out--I would have sent them my spare -0333 if it had helped but they stopped responding to me
The 0-5V output on that WB is very accurate. I've logged it on top of the CAN one and it was scary close, maybe .001 second delay.
One point--you HAVE to run the ground wire from the ground pin output to dash logic. It is it's own little circuit that doesn't share the power ground, so without it it won't work. Ask me how I know..
Thanks for letting me know cause I was definitely just going to run the positive one lol
I just received the AEM 30-0333 and Im now waiting on the pins to wire it to my Dashlogic. Can anybody help with info I need to enter into the Dashlogic Utility to have it display my AFR correctly?
Anyone else having problems with the gauge? Besides the fact that it only displays 1/5th of the advertised PIDS, and I'm sure the ones that aren't being displayed are available...like simple ECT, I can't upload/download a tune or scan reliably with this gauge on the OBD chain. Had to put a switch on the +12v power to power it off when connected to HPT.
AEM tech support is useless and says something is wrong with my wiring and missing PIDS are simply "not available". I'm suspecting there's a design issue with the gauge since I bought it the 1st week it came outh
Might try hitting up a guy that goes by dr.mike on the HPTuners forum, he seems to know a lot about the inner workings of aem gauges. He wrote or modified the firmware on the -0333 version. It's worth a shot anyways
10-20-2016, 05:01 PM
