Thread: Arduino Modular Engine Sensors Unit (~$50)

My project now has a menu system and can talk to an emulated TD5 Ecu.

I've got an MSB ECU here with topside switch failure that I'll be bench testing against once the econoseal connector for the black plug arrives in the post.

Assuming all goes well there, I've got a little bit of K-line sniffing to do to get my code handling fault reading/clearing, then it's time to build out on stripboard for the car.

Here's a photo (although caught the displays mid refresh) of the system reading a few PID's from the emulator (running on an Arduino Uno with LCD screen):

Datalogging to micro SD card now working.

I'm building a cut down version for a friend, he just wants one display with a button to rotate around 4 analogue sensors, Boost, EGT, Fuel Pressure, Oil Pressure.

Parts come to about £20 GBP, Sensors if bought from Ali Express cost about £40 all in. I priced the same from a commercial provider and sensors alone come to £180 (for no better quality I might add).

I'm still waiting on some parts to arrive so that I can get the ECU hooked up on the bench.

Originally Posted by BennehBoy

Datalogging to micro SD card now working.

....

Sounds good!

How hard is it to set it up to a clock of some type, recording date and time.

Makes it a lot easier to keep a track of the log data in the long run.

This is the only annoying aspect of the 1Gauge I fitted to the D1.(I'm not worried about ECU interface and so on).

what I have to do now with my logs:
I download the (many multiples of)log files saved to it's SD card.
I sift through the very short files. They may only be a few mins or so, and I'm not that pedantic. Anything less than 10Kb I delete.
The remaining files are sorted by file name, and collated into one large file(command copy *.csv <filename>.csv) this produces one large csv file for the month.

Thanks to a member here for the tip .. I then edit and adjust the time values column to continue on for each logging session. So if log0001 has a time value of 200 sec max, then log0002 continues from 200 and beyond.
If this isn't done, it's impossible to see the entire log in one session as a graph, as it loops back to the previous logs start time.

I adjust the time value on the X-scale of my log viewing software so that it displays the time in a readable format .. ie. 3 days 12 hrs 31sec ... not 269012 sec(which is meaningless to a human! )

Having a clock interface that can keep track of time would be handy(for the log data).


.. anyhow, just a suggestion.

Originally Posted by AK83

Sounds good!

How hard is it to set it up to a clock of some type, recording date and time.

It's fairly straightforward, a real time clock (RTC) module needs to be included in the solution, I had considered doing this and/or hooking up to GPS which also provides time. The output could then be combined with a mapping service like Google to show performance information at any given geographical location.

Originally Posted by AK83

Makes it a lot easier to keep a track of the log data in the long run.

This is the only annoying aspect of the 1Gauge I fitted to the D1.(I'm not worried about ECU interface and so on).

what I have to do now with my logs:
I download the (many multiples of)log files saved to it's SD card.
I sift through the very short files. They may only be a few mins or so, and I'm not that pedantic. Anything less than 10Kb I delete.
The remaining files are sorted by file name, and collated into one large file(command copy *.csv <filename>.csv) this produces one large csv file for the month.

Thanks to a member here for the tip .. I then edit and adjust the time values column to continue on for each logging session. So if log0001 has a time value of 200 sec max, then log0002 continues from 200 and beyond.
If this isn't done, it's impossible to see the entire log in one session as a graph, as it loops back to the previous logs start time.

I adjust the time value on the X-scale of my log viewing software so that it displays the time in a readable format .. ie. 3 days 12 hrs 31sec ... not 269012 sec(which is meaningless to a human! )

Having a clock interface that can keep track of time would be handy(for the log data).


.. anyhow, just a suggestion.

Alternatively the data could be exposed via bluetooth and an Android app used (it looks fairly simple to build an android app to do this, the device's GPS could then be used).