VATS issue - 3800 L27 to L67 - $5B4 $5B5

[dan_t]

With both disabled it runs for 1sec and shuts down.

[RobertISaar]

have the BIN fully disassembled, along with the datastream inserted, i'll do some digging and see in what all scenarios that the "VATS FUEL ENABLE (L67 ONLY)" bit gets set/cleared.

[RobertISaar]

the byte in the datastream is a "summarized" byte, meaning status bits that are normally held elsewhere in the RAM are mirrored over into a single byte for easy datastream configuration. in this case, the real VATS fuel enable location is byte 90, bit 2.

the bit is only ever set at DAA5.
the bit is only ever cleared at DA7C.
the bit is only ever checked for set/cleared status(except for the mirroring) at A97A.

at A97A, it's discovered that byte 90 spawns another mirrored byte concerning VATS status. controls bit 1 of byte 2B9. 2B9 only ever seems to be stored to once, never read, so seems to be useless.

anyways, the actual code concerning the set/clear of the bit starts at DA56.



and i see the problem.... byte 8014 is checked for 0/non-0 status. the factory calibration is set to FF and the "VATS select" flag only controls a single bit, not all 8. so, change byte 0014 to 00 and VATS is entirely bypassed.

[RobertISaar]

and as usual with 5B XDFs, the MAF tables aren't 100% correct.... offset and scalar aren't dynamic, and the frequency values aren't 100% correct either.

this XDF has these fixes included, along with the corrected VATS select option(now at the top of the scalars list).

also, i'm fairly certain that no 5B BIN actually uses a checksum function, but there is one defined in the XDF header. it won't hurt anything to keep it there, but it doesn't actually accomplish anything.

[dan_t]

Umm how can I do that? And WOW you really you really know your stuff

[dan_t]

VATS enabled was set at 5.0 - I reset to 0.0 and still have the same issue. Also get a checksum error

[RobertISaar]

Umm how can I do that? And WOW you really you really know your stuff

VATS enabled was set at 5.0 - I reset to 0.0 and still have the same issue. Also get a checksum error

assuming you haven't, i would recommend starting over with a fresh copy of BCFN and the 5B4 XDF i uploaded. changes from anything else could upset some pretty sensitive code.

considering the previous "VATS Select" option was only setup to change a single bit and the value started at 255, 5 shouldn't be possible.

and where is the checksum error coming from?

[dan_t]

Error - one or more checksums could not be updated. Check for checksum addressing, etc, validity

I did start with the fresh bin. The same one I sent you. Would you be able to maybe edit the bin I sent you and upload it and see if that works?

And a mega THANK YOU SO MUCH for all of this!

[RobertISaar]

that kind of error generally only happens when you have a BIN of the wrong size selected... or perhaps if the file is set to "read only"?

i just tried it and it saved fine for me?

this is the stock BCFN file with ONLY the VATS select option set to "off".

[dan_t]

That test.bin still shows a value of 5.0 but it RUNS!!!!

Are you using TP V5 or V4? I'm using V4.

[RobertISaar]

that would be your answer. that XDF was made in TP V5, so it won't work correctly in V4. i thought flags/scalars still worked in V4 using a V5 definiton? i knew tables would display badly.

in any case, the existing V4 definition could be modified and usable in V4.

[dan_t]

Switching to V5 made everything display correctly. VATs is no longer an issue. Strangely its running very lean with this prom. BLMs of 150+ I'm wondering if the MAF I picked up from a Supercharged vehicle isn't correct for this prom. Airflow seems correct but lv8 is well down.

[RobertISaar]

unplug MAF to force backup mode, see if fueling improves?

[dan_t]

I will try that. It actually ran well with this maf and the NA prom.

[RobertISaar]

wonder if someone swapped the wrong MAF into the car you pulled it from?

are there part numbers on it?