In our last newsletter we covered EFILive's history of data logging from our early days as a Scan Tool using B&B's Autotap hardware, to the release of FlashScan V1, our first integrated Scan and Tune Tool in 2004 and the advancements that FlashScan V2 delivered in more recent times. to view The Evolution of Data Logging - Part 1

External logging integration moved even further forward with Dyno integration in 2009. Initially testing our integration with the Mainline Dyno, EFILive allows tuners to log dyno data within the EFILive scan tool. Power figures, mixture data from gas analysers or any other device the Dyno PC is able to get inputs from can be viewed and logged in the EFILive data stream. EFILive is also able to send engine data back to the Dyno PC. Given customer feedback on this integration, and interest from a range of Dyno companies, the specification for adding such features is now included with all V8 software downloads, published in the pdf document 'EFILive FlashScan Serial Protocol.pdf' contained in the V8>Documents folder.

2011 saw EFILive's first expansion away from GM controllers with the release of 2006-09 5.9L and 6.7L Cummins support, and delivered new data logging challenges. Working in our favour was that comprehensive aftermarket data logging tools didn't exist, so any solution was going to be a great improvement on what was already (not) available. However, for existing customers who rely so heavily on our scan tool for tuning, what was delivered was substantially different to what they were used to. Sure, data was available but with fixed data streams and odd groupings (thanks to the ECM design constraints), logs were either incomplete to keep data return rates up, or were slow in rate numbers to cover all necessary PID groups. There were advantages - logging in groups meant that in many cases there was data consistency across logs, and these grouping certainly prevented new users from becoming overwhelmed with PID selections. At the end of the day, logging was a new concept for this market segment and was gratefully received.

Unhappy with Cummins data logging streams, EFILive set about to develop custom data streams. While it would have been easier to develop additional platform support, the reality was Cummins data logging just didn't live up to our standards. Late in 2012 EFILive is set to release their first custom data logging solution, EDA (Enhanced Data Acquisition) into beta. Logging more than double the PID's at 3 times the speed of other generic scan tools this advancement set the bar even higher, and is the envy of all other data logging systems, including earlier versions of our own software.

Further long term partnerships were forged in 2012 with EFILive integrating the Fleece Performance 14 Channel Datalogger, designed to capture data not monitored via the ECM into the EFILive data stream. The Fleece Datalogger can log individual cylinder temperatures, to allow monitoring of cylinder balance and airflow distribution to each cylinder, and various other temperatures (examples: between stages of boost on twins) Nitrous pressure, drive pressure, and other liquid temperatures (air to water inlet / outlet temps) can also be incorporated into the EFILive data logs.

While this should be the ending to our data logging story thus far, really it's just the beginning. EFILive has many creative ideas to further enhance our scan tool. The V8 software project will deliver better scan tool and tune tool integration, allow customers to customize options further, and the leading edge graphics will again set the standard. So going back to the comparison of EFILive and other products ask yourself this question "how would you ever tune your vehicle with the most important piece of the puzzle missing?"