Quote: Originally Posted by
MMAfiaV 
haha was worth a shot

I did manage to pull some Binary and C programming from global OBD2 by the way just in case if you guys cared.
The issue is not software ... the issue is mechanical ... let me explain ...
The "source code" as you refer to it for "global OBD2" as far as emissions requirements is concerned will vary engine size to engine size. And all auto makers have different fuel mapping strategies based on displacement size of the engine. Because of this, they also all have different HEX mode identifiers for various functions for the particular ECU you're working with. It truly is vehicle manufacturer specific. You might be able to read Global OBD2 Emissions data, as those mode requests are unified, but they won't give you access to map the fuel curve logic. Plus, Emissions OBD2 logic does not incorporate fuel table threshold limits. So, you would have much work on your hands to do once you start adjusting the default fuel mapping strategy and keeping it within OBD2 Emissions spec.
__________________
perk03z06
--------------------------
Windows XP PC
InTruckPC
P4 3.0 GHz Hyperthread CPU, 1Gb RAM, 120 Gb Hard Drive, DVD/CD-RW, Centrafuse XLE 1.47, 7" Xenarc, GPS, EV-DO via Samsung i730 ... more coming!