Page 26 of 28
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Thu Nov 26, 2009 1:27 am
by tpsretard
the aem tunner is actually GeMs software.
www.gems.co.uk
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Thu Nov 26, 2009 6:40 am
by Fred
Ben, bullet points :
- go to git hub
- go to aarons repo
- click fork this
- setup git on your machine
- do git pull <private repo name>
- make sure you have your ssh key setup still the same
- do something useful locally, commit it, and push it
- if that fails trouble shoot things here or wherever
Enjoy :-)
Fred.
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Sun Nov 29, 2009 7:44 pm
by BenFenner
Forking worked.
http://github.com/BenFenner/freeems-tuner
Fred wrote:
- go to git hub
- go to aarons repo
- click fork this
- setup git on your machine
- do git pull <private repo name>
- make sure you have your ssh key setup still the same
- do something useful locally, commit it, and push it
- if that fails trouble shoot things here or wherever
Stuck on bold step above.
I'm entering this into git:
Code: Select all
git pull http://github.com/BenFenner/freemes-tuner
It is not working. I'm sure I've got something very simple very wrong. Hints?
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Sun Nov 29, 2009 9:33 pm
by sry_not4sale
BenFenner wrote:
I'm entering this into git:
Code: Select all
git pull http://github.com/BenFenner/freemes-tuner
It is not working. I'm sure I've got something very simple very wrong. Hints?
You need to clone the repo locally (not pull), which will require your ssh keys to be correct. Also, you need to use the git url for the repo which is slightly different (appears on the project page when you are logged in to github).
Code: Select all
git clone git@github.com:BenFenner/freeems-tuner directoryname
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Sun Nov 29, 2009 11:32 pm
by BenFenner
Aaron it looks like I'm in business after that little bit of help. Thanks. Now if only I can remember how to commit. =P
After running the tuner it's become quite obvious that it would be real nice to have a real ECU for it connect to. Either that or some fake/pretend "test" ECU connection. Because working with an empty table with only one cell is pretty limited.
Anyway I'm going to test committing and stuff later. And then get to work on something.
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Sun Nov 29, 2009 11:53 pm
by sry_not4sale
Umm I have been using Fred's datalogs and the File comms plug in (which will read binary from a logfile once connected).
There is also the fake ecu plug in (it's called Test) that will try to respond to any commands you send it. That could be extended to include the latest table code
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Mon Nov 30, 2009 3:28 am
by BenFenner
You should send me along one of those data logs if you think it'll be of help.
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Mon Nov 30, 2009 3:36 am
by sry_not4sale
What do you want to get into?
Because your first job could be working on the Test comms adaptor?
The data log isn't too helpful at the moment, just makes the data logging stuff move around, and makes a map appear
I'll forward you the data log via email now
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Mon Nov 30, 2009 4:22 am
by BenFenner
Working on Test comms adapter sounds fine to me. Tell me what it does now (I think I have a vague idea), and what you'd like me to make it do in the future.
Re: FreeEMS-Tuner Development Diary - Comments
Posted: Mon Nov 30, 2009 4:26 am
by sry_not4sale
Currently, once connected it simply replies to any packets sent to it with an appropriate response.
Responses are created either manually or dynamically, but need to be set up for request packets you want to respond too.
Adding a response to the get table from memory button would be a good start, sending map data back to the tuner.
My current work revolves around implementing testing, and then refactoring the table code (using the tests to make sure I don't alter any current behavior or introduce bugs).