-
Hi everyone,
As you all know, Coffee (Dean) passed away a couple of years ago. I am Dean's ex-wife's husband and happen to have spent my career in tech. Over the years, I occasionally helped Dean with various tech issues.
When he passed, I worked with his kids to gather the necessary credentials to keep this site running. Since then (and for however long they worked with Coffee), Woodschick and Dirtdame have been maintaining the site and covering the costs. Without their hard work and financial support, CafeHusky would have been lost.
Over the past couple of weeks, I’ve been working to migrate the site to a free cloud compute instance so that Woodschick and Dirtdame no longer have to fund it. At the same time, I’ve updated the site to a current version of XenForo (the discussion software it runs on). The previous version was outdated and no longer supported.
Unfortunately, the new software version doesn’t support importing the old site’s styles, so for now, you’ll see the XenForo default style. This may change over time.
Coffee didn’t document the work he did on the site, so I’ve been digging through the old setup to understand how everything was running. There may still be things I’ve missed. One known issue is that email functionality is not yet working on the new site, but I hope to resolve this over time.
Thanks for your patience and support!
449/511 communication with ECU
- Thread starter R. Stephen
- Start date
domrvt
Husqvarna
AA Class
Accessing my ECU and reading a battery voltage.
https://www.dropbox.com/s/vknwn6y9qeiksng/Selection_747_.jpg
Dangermouse449
Husqvarna
Pro Class
Thank you anyone. You've proved what I had assumed that the authentication and the secret key(s) I "dug out" are the same for all 449 and 511 engines for huskies and CCM bikes as well. So our community definitely have the know-how to access our ECUs and we are waiting for somebody who can program a preferable mobile diagnostic app with a simple user interface using the command sequences I had published.
I've noticed you were using Python for sending these commands, so may be you have or know somebody who has the skill to do this. Last summer I've been playing some time to develop graphical python apps for Android platform (based on kivy). Although Android native development platform is Java, but I don't like that language so much, and I had successes in this cross-platform Python development. But finally I had not enough time to continue and make our ECU's diagnostic App. However If there is nobody for such a task maybe in next summer I will have some time to continue and make that App. But it will definitely steal my time from riding
I wrote an email to TuneECU guys but is has not been answered.
Normann
Husqvarna
AA Class
Dangermouse449
Husqvarna
Pro Class
Great efforts!
Very well done!
Would you mind to share the first data bytes for initialization (on K-Line)?
E.g. recorded with you raspberry scope or another logic analyzer.
I try to use an Attiny with open collector circuitry to communicate, but I don't get an answer from the ECU.
BR
Florian
Hi Florian (tMh2),
glad to assist you.
If you begin so low level you should download the following documents (about Keyword Protocol 2000 - Part 2 - Data Link Layer), e.g. from the following link: http://www.alfa145.co.uk/obd/14230-2s.pdf
In this document please find the "Fast initialisation" section. KMSK16 ECU running this protocol needs this initialisation sequence (25ms +/- 1 ms logical low, which if I remember well was 12V high, but please try it), then wait for an other 25 ms (in default logical high), then send the StartCommunication service request sequence:
0x81 0x12 0xF1 0x81 0x05
As I explained in my earlier post 0x81 means you will use physical address (0x80), plus, length of message value is placed into the first byte of header (0x01). 0x12 is the magical and non-standard address of ECU i had found. 0xF1 is the source address of tester (it is standard in BMW or even all OBD2 testers). The next 0x81 is the StartCommunication command. 0x05 is the calculated checksum.
Please be aware that (if I remember well) the bit order in the bytes are "reverse", so low bits go first. All other commands you can find in my earlier post. Naturally you should always repeat the header bytes and also the checksum at the and of sequences. You should always send keep-alive sequences in 4-5 sec at last, failing which ECU drops communication.
It's why I use ELM327 since it is very cheap and provides such convenience functions. But you should be successful with your circuit if you program these basic functions of ELM327 on you microcontroller.
I wish you all the best and please don't hesitate to "ping" me if you need further assistance.
So, cross our fingers, but I hope that within the foreseeable future we can have a cheap but full-featured diagnostic app for our bikes.
Hi Alain,
I'm here -- have been waiting for your notification impatiently but was not brave enough to push you
Thank you for your time and development. I'm gladly test your beta version. I've sent a contact message for you on tuneecu.comI've not tested flashing the ECU yet, but i can read the map from the ECU.
If an USB cable is used it must be a KKL 409.1 cable (not an USB ELM327), in the future the remapping can be done only with the KKL cable.
Dangermouse449
Husqvarna
Pro Class
Meeou,
We may have some files you would like if you are able to get the upload function working.
