projekteg

1.8 does work, there were reported timing issues, but it's not really an uberdata 1.8 issue, it's more of an obd -> obd1 thing and has been reported with other versions of uberdata as well as all other rom editors. i honestly still use 1.7beta, the 'un'official realease of 1.7 b/c the fuel maps were still 8 bit just like all previous versions so it's easier to use older maps. it just so happens that most of my maps have the 8 bit fuel maps, so it's just more convenient. if i'm tuning a car from scratch, i use 1.8 and all of the newer features coming out are directed towards 1.8, so i would reccomend using it, but if you converted from obd2 to obd1, keep on eye on your timing.

93turbo16

There were some problems with 1.7 being rather lean. I had it happen on a basemap. J. Davis informed me about this, and sure enough, did the exact same basemap on 1.7 as I did on 1.66 and went out for a drive and it was a lot leaner. So ever since I have stuck with 1.70 and 1.66. I have uced 1.8 and it works great, just not use for me to use it, untill the ostrich gets here. 1.66 is tuned enough for me :P

projekteg

i think you're a little confused with the versions, 1.66 and 1.7beta still had the 8 bit fuel maps. the rich/lean conditions began with 1.70 when the fuel maps were changed to 16 bit instead of 8 bit, which is what honda uses also. that's why if i'm sending someone a basemap that i won't be present to monitor/tune, i always use 1.7beta b/c the 8 bit maps are tried and true.