pcmhacking.net

igot the above listed PCMS in a massive ebay sale for cheap and i only wanted one or two of them, so if you want it its yours for good i don't want it back

so the spark mod only works in PE mode ??

whats the point of it rather than adjusting the usual spark table ?

(please excuse my ignorance i have little knowledge of MAF systems)

It uses the mass air flow rate variable instead of the cylinder air mass one.
The cylinder air mass is used in too many places to change easily, and would result in diminished resolution due to it being 8 bits

yep sounds good I'll pm you my address then

The existing spark tables work fine out of pe mode as cylair isn't maxed out, pe mode typically isn't enabled below 40% tps and 500cylair, the 190 g/s start value of the table isn't in range anywhere near those values, so it would be a waste of CPU processing time having it on all the time. But if you want the table enabled earlier you could enable pe earlier, if your reaching the 190 figure out of pe then your going to need to enable it anyway as that's a lot of airflow. Based on the vt i tested with 190 was around the ballpark when cylair is maxed. Im happy to be told otherwise if my logic is incorrect.

I just checked all locations for LPG spark tables for vx & vy calibrations and here they are;

$BDa & $BDb @ 57AF to 5F73
$06a @ 57AF to 5F89
$06b & $06c @ 57AF to 5FAB

I'm not sure why & how they can be different sizes but that's what I found!

If 202 is sending you a vx PCM I'll send a vy, even though I'm 90% sure there identical pcb's!

Again awesome work & seems like a good work around!

OK cool, also if you have loom pcm plugs I don't mind paying so I can make a dedicated bench one

The Excel spreadsheet is going to take a little longer than I thought.
Due to the way the last few tables need to be done it is not as simple as I'd hoped. Hopefully over the weekend will be able to sort it out.

yoda69

yeh i thought that might be the case, no dramas

dont mean to step on any toes but I was very bored today and thought id take a crack. after 3 hours of head bashing I came up with this: basically what I did was make the dec1 value capped at 65535 which is FFFF and the dec2 value becomes whatever it needs to be so that the last value in that set is as close to but not exceeding 255. seems to work ok... let me know if I am barking up the right tree.

you will still get an error if you try to go over 510g/s as that is all F's and itll bug out.

No problem from me. I spent sometime on it earlier today as well, took me a while to work out what I'd done originally.
I've sent a copy through to The1 to have a go at breaking it before I posted it up.
Key fixes:
1. Ensure first value of table is greater than last value of previous table.
2. Fix max maf value to 510g/s.
3. Fix maf graphs of before and after
Has a couple of macros to work through with a number of loops, so can be a little slow. Will post it up when I can get the kids of the computer, will also be interested to have a look at yours and see if I can "pinch" any ideas for improvement.
Yoda69

EDIT: Managed to get on when they got sidetracked.

looks good as long as there's some way at the end of the day to alter the maf tables.

Hopefully the video above explained the use of the spark table to everyone?