http://www.canhack.org/gallery/v/ArtistSong/
We have Data Display!!
We have Data Display!!
If you can read this, the light is still red.
What we figured out yesterday ( We = TonyT, MadMax, and myself )...
Worked... I just had to put a pause between sending the text to the CAN controller, and retrieving the ^M from CAN232.
I'll post the code here in just a tic... ( along with the updated can_logger-web ).
Worked... I just had to put a pause between sending the text to the CAN controller, and retrieving the ^M from CAN232.
I'll post the code here in just a tic... ( along with the updated can_logger-web ).
If you can read this, the light is still red.
-
05MagnumRT
- What's hacking?
- Posts: 23
- Joined: 2005 Jul 28 16:03
- Location: Dallas (Frisco), TX
Thanks!! One small step for... Ah hell, who am I kidd'n... This rocks!
Ok, back to deciding more CAN Bus data...
Make sure you guys check out what I'm parsing through on http://www.canhack.org/can_logger !!
Ok, back to deciding more CAN Bus data...
Make sure you guys check out what I'm parsing through on http://www.canhack.org/can_logger !!
If you can read this, the light is still red.
-
05MagnumRT
- What's hacking?
- Posts: 23
- Joined: 2005 Jul 28 16:03
- Location: Dallas (Frisco), TX
I was playing with the can logger a little bit, and I quickly noticed that there is a huge amount of repetative traffic, as evidenced by the number of messages compared to the number of unique messages for each ID.
I'm wondering if you still remember what the car was doing for each of those test data sets, maybe documenting that would be a good idea (as well as for all the future data dumps that are done). We could then pick on an ID and see across test files what kind of activity changes there are. For example, if a particular ID has very few changes through logs dealing with radio mode / station / track changes and climate control changes, but shows many different messages during engine start up, then that would point to a system like the SKREEM or diagnostics run at start up.
Sorry if you guys are beyond this thought stage, I'm just blathering while really looking at some of the data for the first time...
I'm wondering if you still remember what the car was doing for each of those test data sets, maybe documenting that would be a good idea (as well as for all the future data dumps that are done). We could then pick on an ID and see across test files what kind of activity changes there are. For example, if a particular ID has very few changes through logs dealing with radio mode / station / track changes and climate control changes, but shows many different messages during engine start up, then that would point to a system like the SKREEM or diagnostics run at start up.
Sorry if you guys are beyond this thought stage, I'm just blathering while really looking at some of the data for the first time...
I agree. The way the database is setup, it is very easy to pull this kind of data & check for changes across multiple runs. That's what's great about all this being thrown into MySQL... The data is there, just a matter of how you request it.
So, what I see so far is I need to put in an option to narrow it down to distinct data.
Maybe something along the lines of:
Time :: Line for first packet state
--Repeats X times
Time of Change :: Line for new packet state
--Repeats X times
Time of next Change :: Line of next packet state
This will of course repeat for each change ( even if it goes back to a state it was before. )
Will look into this tonight..
Any more suggestions?
So, what I see so far is I need to put in an option to narrow it down to distinct data.
Maybe something along the lines of:
Time :: Line for first packet state
--Repeats X times
Time of Change :: Line for new packet state
--Repeats X times
Time of next Change :: Line of next packet state
This will of course repeat for each change ( even if it goes back to a state it was before. )
Will look into this tonight..
Any more suggestions?
If you can read this, the light is still red.
