Originally Posted by servion
I doubt its your injectors. Uberdata is buggy as hell. What version are you using? Are you burning chips or are you using the ostrich?
If you're burning chips, use the latest version of uberdata 1.7. Are you datalogging to see the exact areas of the map you are trying to modify? If you just go by the column headings, chances are that you are making changes to the wrong portions of the map. The uberdata load columns don't correspond correctly to the load values it takes to reach that column. IMO, its impossible to tune uberdata correctly without datalogging. I won't touch it (especailly at altitudes other than sea level) without datalogging first.
Thanks alot for your advice.
I am using the 1.7 version of uberdata, so I don't think that is the problem. I also made a basemap in Crome and it did the same thing, so I don't think it is software related.
I am using datalogging that came with the wideband sensor that shows throttle position and rpm. I partial throttle tuned at 10 in/hg and then at 0 in/hg according to my boost gauge and everything was smooth and running well, but it went super rich on me the next day.
I am burning chips with the Moates Burn 1. I will pick up some more chips and see if the chip is bad. I really need to figure this out because the blue box is really crappy and slow.
But, I do need to upgrade my injectors if I plan on 10 psi. Anything over 550cc would be overkill with the Greddy setup at 10 psi.