Taking/putting up screenshots is not the problem (see below), there is nothing to "figure out" to do that. Here's the situation:
My last datalog covers about 18 minutes of riding, as noted it is about 2MB in size. The latter factor alone makes it difficult to do much with on a limited speed Internet connection that I'm blessed with using.
I could put up 6,108 screen shots- that is how many frames there are from my most recent datalog. I doubt the forum admin would appreciate 6K more posts in this thread.Doing that is like critiquing a film after watching a handful of frames vs watching the film.
The proper venue for that type of file is the MS Extra forum. MSL and tune files (MSQ) can be uploaded and members use MegaLog Viewer to look them over. I'm not to the point where I need to have these reviewed by others yet, I still have tuning to perform. I choose not to waste their time until something comes along I cannot figure out.
Attached is frame 3,050, about halfway through the ride. The white line is RPM, the red MAP, the yellow AFR, and the green head (coolant) temperature. The AFR varied in the first few seconds of running from about 12 to 13 and then remained around 14.6~14.8 (average of 14.7) the remainder of the logging regardless of what the engine was doing. There is an adjustable averaging lag in the software, however based upon other datalogs I've reviewed I should see more variation than what was present. This lead me to believe the wideband controller and/or sensor was a problem. I read a detailed posting about the BPSX controller on the DIY EFI forum and they pointed out a problem of inconsistency existing in original and replacement controllers. I'm waiting on the Spartan2 controller to get here for further testing.
View attachment 41521
Well thanks; despite the interesting signal which I have no idea what it is. The units and divisions of graph are basically illegible.
). The Spartan 2 calibration sequence is very easy. I created a dash in Tuner Studio that only showed the AFR reading, and then recorded it with my phone. You have to capture the reading from the sensor after it is powered on for the first 5 then the second 5 seconds. Using the spreadsheet the vendor provided, I got corrected readings of 10.42 and 19.80 for 0 and 5 volts respectively (initial specs were 10.0 and 20.0 so the controller was not off by much). I have updated the wiring diagrams for the Spartan 2 controller.
) is another day.
stick with the name brand USB to RS-232 vendors and preferably the FTDI chip sets. 
