Eurika!

Project related announcements. Milestones, etc...
Post Reply
User avatar
linuxkidd
Site Admin
Posts: 345
Joined: 2005 Jul 22 15:48
Location: Anywhere, USA
Contact:

Eurika!

Post by linuxkidd » 2005 Jul 31 18:26

Well, this weekend marks one HUGE step forward for this project.

MadMax was kind enough to loan me a CAN232 for the weekend. ( Yes, we still need to purchase a CANUSB! ).

Between he and I, we've cracked into the CANBus.

Image

I'm now working on a Perl/MySQL solution for data logging.
If you can read this, the light is still red.

User avatar
tonyt
Site Admin
Posts: 51
Joined: 2005 Jul 22 21:44

Post by tonyt » 2005 Jul 31 20:06

Wish I knew Perl I'd help you with the software...
Share what you learn....

User avatar
codekey
CAN? Tin or aluminum?
Posts: 34
Joined: 2005 Jul 26 05:14
Location: Irvine, CA

Re: Eurika!

Post by codekey » 2005 Aug 01 01:15

linuxkidd wrote:Well, this weekend marks one HUGE step forward for this project.

MadMax was kind enough to loan me a CAN232 for the weekend. ( Yes, we still need to purchase a CANUSB! ).

Between he and I, we've cracked into the CANBus.

Image

I'm now working on a Perl/MySQL solution for data logging.
You guys figure out how to sort out that data? As in what is the ID and how many bytes?

User avatar
Mad Max
Yes, we CAN hack!
Posts: 77
Joined: 2005 Jul 25 20:14
Location: Virginia Beach, VA
Contact:

Re: Eurika!

Post by Mad Max » 2005 Aug 01 02:48

You guys figure out how to sort out that data? As in what is the ID and how many bytes?
That is going to be this weeks work. I am going to start working on breaking down some of the raw data off the port via software. Just have to write the parser for it.

Guest

Post by Guest » 2005 Aug 01 11:42

THAT is awesome!
I would like to understand more about what I am seeing, is this the raw data that the ECU is reading/sending?
Please help a non geek!

User avatar
codekey
CAN? Tin or aluminum?
Posts: 34
Joined: 2005 Jul 26 05:14
Location: Irvine, CA

Post by codekey » 2005 Aug 01 13:35

Anonymous wrote:THAT is awesome!
I would like to understand more about what I am seeing, is this the raw data that the ECU is reading/sending?
Please help a non geek!
The first three characters is the CAN ID, the next character is the data length.

CAN ID 0x11D, data length = 5, 0x00, 0x00, 0x00, 0x00, 0x28

User avatar
Mad Max
Yes, we CAN hack!
Posts: 77
Joined: 2005 Jul 25 20:14
Location: Virginia Beach, VA
Contact:

Data Format

Post by Mad Max » 2005 Aug 01 13:57

CAN ID 0x11D, data length = 5, 0x00, 0x00, 0x00, 0x00, 0x28
Question for you ... I have been looking at the various Frames for CAN.

Would it be a good guess, since you decoded the first line to assume that the CAN-B Bus is using the 11 Bit ID?

Do you break everything in the message in Byte boundaries or do you have to turn everything into Bit format and delineate from there?
[/quote]

User avatar
linuxkidd
Site Admin
Posts: 345
Joined: 2005 Jul 22 15:48
Location: Anywhere, USA
Contact:

Re: Data Format

Post by linuxkidd » 2005 Aug 01 17:43

Mad Max wrote: Do you break everything in the message in Byte boundaries or do you have to turn everything into Bit format and delineate from there?
They are all 11bit ID's .. ( can't mix and match on the same bus ). And the data parsed out is actual Hex values for the information going across. No breaking it down to binary.
If you can read this, the light is still red.

Post Reply