Wife's car has been testing all of my patience(and consuming all of my time) lately, but I do have a patch put together. found some more interesting quirks along the way, like how the E-side doesn't bother generating a baro value, it just gets the value passed to it from the T-side. so now, when baro updates are allowed with the boost patch, they start with a MAP read on the E-side, get emulated into a 1BAR value, sent to the T-side, T-side uses the emulated 1BAR signal instead of the reading it would normally make of the MAP sensor and sends it back to the E-side.
in any case, new XDF has a new boost patch in it, existing ADX should still work since I didn't change any of that behavior. as always, test with caution, i ran it through a real basic simulator, it shouldn't crash a PCM at the very least and I'm hoping for a hell of a lot better results in terms of actually running an engine.
removed the flag for selecting 2/3BAR MAP sensor presence, if boost code is applied, it's expecting it. i would have to run some math to verify, but there are probably setting combinations that would allow the 1BAR as well, but that seems like a fringe application, if any.
I'm going to implement the non-boost high range spark table that's included with the boost patch into a new Rev3 patch at some point, just not at the moment. it's only a single byte difference, but it's 3AM already and i don't feel like typing more documentation or spreadsheet formulas than necessary at the moment.
if this version ends up working well, i'll try and round up all of my disassemblies and patch notes for this PCM and set them in an archive. anyone proficient with 6811 would be able to use them as a launching pad for their own level of weird if they wanted to and not be held back by my pace.
Reply With Quote
Bookmarks