Moderator: Freon
realwomble wrote:Guys,
I've ported Mikes code to native windows APIS, anc have it talking to the ECU now.
I'm working on generic handling of *all* supported parameters, and a generic way of describing different ECU versions (where locations can change).
It'll be written in such a way to make it easy to add "dashboard" like function as well.
Once that is done, I'll post it all up here.
For graphing, I was planning to investigate using PERL to parse the log and drive EXCEL. Years back I know it was simple ot use PERL and one of the included modules to "drive" excel - build a sheet, configure chart etc. I've had no tgime to investigate this, so is someone else has time...
Thanks,
Tom
cdvma wrote:
Windows APIs = BAD
We should keep this as much ANSI C as possible and for each system, if required, make an abstraction layer for the serial interface so that the communications are platform specific but the logic and data handling is not. This will be much more benneficial. I say first do the abstraction layer and then worry about getting the data.
In order for this system to be pretty, a GUI is going to be needed as well. Pick, again, a x-platform graphics API. There are a few out there...
west_minist wrote:I work in the IT Field. I am a Network Engineer.
I can tell you that modularity really works. I agree w/ cdvma.
I think we should have 3 mods. Interface, Logger & GUI. It would be like protocol analyser in computer networks. Eg, Ethereal http://www.ethereal.com
I personal think the logger with need more work due to different subaru CPU's out there.
Thats my 2 cents worth.
./openECU.sh -render console, csvlog -param RPM MAP EGT KNK -file ~/logs/myLog.csv
ll wrote:We're all duplicating one another's work here
Return to Data Logging Software
Users browsing this forum: No registered users and 1 guest