SDS EFI PC Data Logging
 

We've had a number of people ask about the optional PC data logging feature.

In a nutshell, this allows you to connect your SDS ECU to a Windows device to view sensor data in real-time and log the data graphically or in text format. Data is stored in the PC memory.

You can also store and print your programmed values using the Fetch Values Button which can be valuable for tuning as you make changes.

Here's a short video showing the screen captures while running our O-200 recently to give you an idea of what it looks like. Unfortunately we had some frame rate and formatting issues with the screen capture software making the video not as clear as in real life. Will try to resolve those next time when we make a tutorial on using the feature. https://vimeo.com/228761104

That is kinda cool.
What is the dial on the top left, and how does the knock sensor work (assuming you can say).

Tim

Top left is RPM, next to that is air/fuel ratio from the wideband.

We have not had time to carry out experiments with the knock sensor on this engine. Typically they don't work very well on engines with individual cylinder/ heads as on Contis and Lycs (maybe with one per head) but we thought we try some different sensor locations and see how it would work. On liquid cooled engines these can work well.

When the sensitivity is set up properly, the knock sensor will pull back timing from your programmed mapping until the knocking stops. It will then try to re-advance timing until knocking occurs again. Ideally, it will keep timing optimized just short of the knock threshold.

Nice. What is the TP gauge on the bottom left?


Tim

Throttle position 0-64.

Ok, among all the things I thought of, I was not even close.


Tim

Screenshot
 

Just finished some recent engine testing. Here's a screenshot of the short run so people can see more clearly than on the video perhaps.



After the run is done, you can drag a vertical cursor across the lower horizontal axis which is time. In the lower left of the screen, you'll get a numerical readout of the selected parameters at that time in the run.

The color key up top shows what each parameter is.

RPM is displayed on the left vertical axis (red trace), AFR on the right vertical (green trace).

You can turn off any parameter to de-clutter the screen if desired.

You use the Fetch Values button to pull the values out of the ECU which you can review or print in a compact format.

You can also log in text instead of this graphical format to see every single data piece in great detail.

This run shows a slow opening of the throttle to WOT with the engine under propeller load. It reached approximately 2400 rpm here. Notice the AFR got quite rich above about 2100 rpm. We'd then go in with the programmer and reduce the rpm fuel values there to lean the engine back towards best power (about 12 to 1 AFR).

The lean spike when the throttle is closed is due to a fuel cut being set at fully closed throttle, just done here to check the wideband O2 sensor calibration.

You can see where the data logging can be highly useful for tweaking the values or spotting an issue with the programmed values.

Nice!
 

This is very cool! I look forward to using this on my project. I use Racepac and Superflow data in my day job frequently and know the value.

And a public thank you for answering my email questions.

Split Screen
 

Some people have asked if you can split the gauge and graphical logging screens.

The answer is yes. Here's an example:

We were working with a long-time customer to get the PC data logging to work on his 8" Insignia NS-P08W7100-C tablet running Windows 10. Seems to work well with baud rate adjusted down a bit from Win XP/7/ 8 versions.





This opens up some possibilities with cockpit display of ECU information and is more convenient for logging than a laptop. Used a simple USD adapter to mate the 2 systems.