Thanks heaps guys. Glad you agree those PIDs are definitely at least for MAF. If FC43 is for the MAP sensor FC2C must also be cause the graphs look almost identical, but they are inverted compared to the MAF on a graph. What does the E represent in that equation Antus? And would you think it’s possible the Snap-on scan tool would use the formula ([22001001]*3600 / ([22FC1201]*820) = X L/H?
Because using that is dead on what my cluster says while in “engineering” mode on my VY
Thankyou for the help, these are pretty much the only PIDS I haven’t nailed down yet, other than the all the bitmapped ones
PCM Logger 21 - Testing
-
- Posts: 4
- Joined: Thu Apr 07, 2016 3:58 am
- cars: VY calais
- antus
- Site Admin
- Posts: 8253
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Logger 21 - Testing
That formula does not look like anything i'd expect. I got the equation here https://pastebin.com/76jgpGiF but I dont know what E is. I think maybe N is the result, and E is the raw value? You'd need to play around a bit to figure it out.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 4
- Joined: Thu Apr 07, 2016 3:58 am
- cars: VY calais
Re: PCM Logger 21 - Testing
I found that formula on a page with a lot of calculated PIDs. It’s MAF g/s * 3600 (3600 changes g/s to grams an hour) \ AFR * 820 ( 820 being density of fuel I think). And FC12 is AFR commanded but with more decimal places.
Oh wow, that link has great explanations, thankyou for that
Oh wow, that link has great explanations, thankyou for that
Re: PCM Logger 21 - Testing
Yes, Wow antus, Thanks
-
- Posts: 35
- Joined: Thu Apr 28, 2022 5:49 am
- cars: 1984 Volvo 244
Re: PCM Logger 21 - Testing
HA! I got it to replicate the error, but I think I know why it did it to me. If PCMLogger is running and I plug in the dongle, it seems to 50% of the time do it even though it says 'connected'. If I shut down the software and restart, it seems fine. This doesn't seem to be much of a debug log, but that's what was there.
Code: Select all
[04:53:51:474] PCM Logger
[04:53:51:474] Friday, December 09 2022 @04:53:51:47
[04:53:51:474] Initializing OBDX Pro on COM5
[04:53:51:931] Device Found: OBDX Pro VT
[04:53:51:931] Switched to DVI protocol
[04:53:51:946] XPro: 32 0C 03 4F 42 44 58 20 50 72 6F 20 56 54 76
[04:53:51:946] XPro: 32 03 01 00 66 63
[04:53:51:946] Firmware version: v1.02
[04:53:51:946] XPro: 32 03 00 01 2D 9C
[04:53:51:946] Hardware version: v3.01
[04:53:51:946] XPro: 32 0D 04 06 6B FF 50 55 52 85 48 87 21 59 59 2E
[04:53:51:946] Unique Serial: 066BFF505552854887215959
[04:53:51:962] XPro: 41 02 01 01 BA
[04:53:51:962] OBD Protocol Set to VPW
[04:53:51:962] XPro: 43 03 00 F0 01 C8
[04:53:51:962] Filter set and enabled
[04:53:51:962] XPro: 41 02 02 01 B9
[04:53:51:962] Network enabled
[04:53:51:962] Device Successfully Initialized and Ready
[04:53:51:962] ValidDeviceSelectedAsync started.
[04:53:51:977] XPro: 20 01 00 DE
[04:53:51:977] TX: 6C 10 F0 3C 0A
[04:53:52:072] ValidDeviceSelectedAsync ended.