Go Down

Topic: Bike interface OBD (Read 67217 times) previous topic - next topic

JOTTDUINO

I'm getting little by little that starts working. Once you request the data from the sensors by sending the code, do you stay in a loop sending that code and reading or just reading over and over?

Cheers.

o5i_

You need to send the request everytime.. but make sure you have 1-2 ms delay between answere and new request. I got a stable maximum speed working at 135ms per transaction.. on some bikes you can use ecueditor to flash the code using a different baudrate (50000) wich increases the speed to 55ms.. cheerz..

JOTTDUINO

#137
Jan 19, 2018, 01:03 pm Last Edit: Jan 19, 2018, 05:14 pm by JOTTDUINO
Ok, this is what I have after requesting the sensors data. I receive:

----------------------------------------------
80 12 F1 2 21 8 AE
----------------------------------------------
80 12 F1 2 21 8 AE
----------------------------------------------
80 F1 12 34 61 8 5 16 55 A0 16 50 A0 FF FF FF FF 0 0 39 AC 53 52 AD 0 FF 0 FF 66 2B FF 0 0 0 0 0 0 0 0 FF FF 40 40 40 40 FF FE FF 6B 1F 30 4 4 0 FF FF B1 80 12 F1 2 21 8

Can anyone confirm if is OK?
I doubting about the beginning 80 12 F1 2 21 8 AE and then at the end of the long message appears again but without the AE

YES!! I think I'm getting there,the only value is not 100% correct is the battery voltage and I dont get the speed either. Anybody knows?

TriB

Can anyone confirm if is OK?
Yes, that´s fine. You can be sure, when the Service ID is responded as SID + 0x40.
Then the request was right and the response will be valid.

Otherwise you are getting something like that:
0x80 0xF1 0x12 0x02 0x7F 0x21 0x10 as an Error. The second value might give you an idea what went wrong. But that seems to differ from ECU manufacturer to manufacturer.

Battery is quite complicated, I guessed a lot and don´t think it is the right value. It seems to be the loading voltage from the generator.

CapFirepants

Hey Guys
I've been reading through this post with great interest. I would like to adapt the software from 05i to work with a Honda CB500F 2013 Model. Has anybody tested this with a Honda bike, perhaps even with the same one I have?

TriB

Hello Cap,

as far as I know, the hardware and init-sequence will be the same.
But the protocol is quite different! No format within the message header, ect.

The ECU Hacking Forum is not very helpful about it. There is just one unanswered thread about this topic.
And maybe this one.

Good luck!

CapFirepants

Hello Cap,

as far as I know, the hardware and init-sequence will be the same.
But the protocol is quite different! No format within the message header, ect.

The ECU Hacking Forum is not very helpful about it. There is just one unanswered thread about this topic.
And maybe this one.

Good luck!
Thank you.
Ive done some more searching and found this link: https://lunarflow.com/index.php?topic=15.0, which in turn links to this: http://projects.gonzos.net/ctx-obd/ looks to me like it could be the same protocol my 500f uses. Would you care to take a look and tell me what you think?

TriB

links to this: http://projects.gonzos.net/ctx-obd/
Yeahr, cool! That looks nice!

I´d say, with this information you can easily realize that.
The Honda data tables.pdf will show you which value is what and how it has to be calculated.
The schematic can be made easier using an L9637D.
It will convert the single K-Line to serial Rx & Tx. No need for two separate converter.

You can take OSi´s work as a base. It fits better then mine, which is optimized to respond with a single value, not a data table.

CapFirepants

Alright! I've ordered some L9637Ds and will start looking for a solution when they arrive. I'll post again, either if I need some help or if I get it working.

CapFirepants

Yeahr, cool! That looks nice!

I´d say, with this information you can easily realize that.
The Honda data tables.pdf will show you which value is what and how it has to be calculated.
The schematic can be made easier using an L9637D.
It will convert the single K-Line to serial Rx & Tx. No need for two separate converter.

You can take OSi´s work as a base. It fits better then mine, which is optimized to respond with a single value, not a data table.
So the chip arrived today. Wasnt aware that its smd, dont have a board for it so I soldered some cables to the pins. Doesnt look nice but works I guess, at least for testing. Ill check to get some kind of pcb made or so when Im done.

@Trib: I've just noticed you list a Ceramic-Capacitor 10 nF 50 V/DC. I only have an electrolytic 3.3 uf 50v as the smallest size. Would it be ok to use that one instead?

What I really want is the gear, so I thought maybe starting with your code and working my way from there. I've pulled it but it seems to be in 4 different .ino files. Im a bit confused, do I need to merge them or something? Sorry for all the novice questions.

TriB

@Trib: I've just noticed you list a Ceramic-Capacitor 10 nF 50 V/DC. I only have an electrolytic 3.3 uf 50v as the smallest size. Would it be ok to use that one instead?

What I really want is the gear, so I thought maybe starting with your code and working my way from there. I've pulled it but it seems to be in 4 different .ino files. Im a bit confused, do I need to merge them or something? Sorry for all the novice questions.
Oh yes, it is really tiny! There are some SOIC boards, to make the implementation easier.

I didn´t calculate if you would still fit into the specification of L9637D. The costs are small and a capacitor is sent within a day. So I would go for sure and get a 10nF.

The *.ino files are belonging together. If you copy all of them into the same folder, just open one of them and the others will be opened in the Arduino IDE in seperate Tabs.
The IDE handle them internally as one code file.

gsustek

#146
May 10, 2018, 10:20 am Last Edit: May 10, 2018, 10:30 am by gsustek
Hello, awese work! I have Honda VFR 1200 X and wanna to rewrite flash ECU. Is it generaly  k-line interface enough for that and what kind of software should i use(ecuflash)?

TriB

I have Honda VFR 1200 X and wanna to rewrite flash ECU. Is it generaly  k-line interface enough for that and what kind of software should i use(ecuflash)?
Theoretically it would be possible to rewrite the mapping through K-Line.
Practically, there are some security layer, which will prevent you from doing that!

Also I don´t expect any expensive software to work with a self created adapter. The ecuflash-guys spent weeks or even years of work into their flashing tool and for sure, they won´t give it away for free.

For Suzuki there is a big community, which disassembled the ECU code and created an open source software, where you can easily flash the mapping or the whole software.
Kawasaki secured their ECU with an unique seller-code, which has to be purchase as an official seller.
I guess that Honda did something similar, due to the fact, they also use Denso Ecu´s.

Even owning a Suzuki and some self created adapters, I wont mess up my ECU without deep knowledge of mapping and stuff!

gsustek

Wise words:-)

So that is the state of ( opensource ) motorcycle ECU knowledge/physical accomplishment:-)

Thank you so much.

Go Up