Quote:
Originally Posted by JasonACT
From the dump at the top of this page (post 481, if this post spills over) there's a dump of a MKI XR6 with this content:
0x070 20 20 20 20 10 20 20 20 20 20 81 0e 80 00 ff 00 ____._____..€.ÿ.
Position 0x07A controls features: Police Mode & RPM Alarm
(81 = those two are off, 85 = Police, 89 = RPM Alarm ... 8D = Police & RPM)
Position 0x07E & 0x07F are the RPM Alarm configuration (here they are not set, being FF 00). On my spare MKI G6E Cluster, I've coded these bytes as 69 4A and turned on the RPM Alarm and it goes off when you hit 5250rpm (you can hit 5249 as much as you like, it won't go off). The value for 6000rpm (as mentioned earlier) and what an FPV will have set in these positions is 78 4A. The 4A part is some weird config to do with timing and how low the RPM needs to go below the set limit to reset.
Sad news though, I'm sorry to say, but even though I can enable the RPM Alarm and set where it goes off, these config changes in the EEPROM do not alter any of the values you can read via an OBD2 tool.
So... These are not settable on a non-FPV MKI without disassembling the Cluster.
Even if you enable the alarm, the default set limit will not allow the alarm to go off.
Edit: I forgot to mention... No special checksum needs to be recalculated for changes in that particular area.
|
Ive come up with a bit of a work-around, not going to risk damaging my cluster, but with a bit of raspberry magic and socketcan, can trick the cluster into momentarily thinking the engine is past the limit, triggering the shift alarm, and then clearing the resulting fault code that is logged everytime you the alarm goes off.
Was driving for around with it going off at 1000 rpm, became quite annoying after the novelty wore off.
Havent gotten the light to light up though, just the sound.