Marc-X

I have for some time no wanted to write text to the E46 (low) cluster to advertise speedcameras (speedlimit and distance) using for example "GATSOHunter" and "RoadRunner"

My thought was to have the arrows flashing to draw your attention to the cluster, and then present the current speedlimit followed by the distance to the speedcamera (GATSO).

After some digging through the web I have understood that writing to the E46 (low) cluster is not possible... WRONG!!!

Now I have finally succeeded to do just that...

The clue is that it MIGHT not be possible to DIRECTLY write text to the alphanumeric display, but use it's pre-defined messages kind of...
There are afaik 3 different types of messages that can be displayed:

-Distances in meters or feet
-Speeds in km/h or mph
-Temperature in degrees Celsius or Farenheit

Maby it's possible to write "plain" text as well, this I don't know at the moment.

Today I logged the following _DISTANCE_ codes and tested to write them back to the cluster with success:

_HEX codes WITH checksum attached!_

7F 05 80 44 29 30 A7 <--- 300m
7F 05 80 44 29 25 B2 <--- 250m
...
7F 05 80 44 29 10 87 <--- 100m
7F 05 80 44 21 90 0F <--- 90m
7F 05 80 44 21 80 1F <--- 80m
7F 05 80 44 21 70 EF <--- 70m
7F 05 80 44 21 60 FF <--- 60m
7F 05 80 44 21 50 CF <--- 50m
...
7F 05 80 44 21 10 8F <--- 10m
7F 05 80 44 21 00 9F <--- 0m
7F 05 80 44 20 00 9E <--- CLEAR DISPLAY? (this was the last code logged from the GPS -> IKE

Here the GPS (7F) is the source and the IKE (80) is destination.
The first DATA byte, (the fourth byte in the string) seem to be the code for "distance display". That is the "m" is displayed after the data in the display.

The second DATA byte, (the fifth byte in the string) it is used to distinguish between 100's and 10's.

The third DATA byte, (the sixth byte in the string) is the actual distance data.

I have logged codes for speedlimits as well, but I have lost that log. I'm pretty sure that the format is very similar, but with another hexcode for the FIRST databyte to put the display in "speedmode" for example.

Will test "speeddata" tomorrow...



Kind regards

Marc in Norway

2k1Toaster

I dont have a BMW, but awesome job at getting something to display!

Subscribed.

__________________

Marc-X

... I'm in great need of some help from a VB coder now... Have to modify IBusComm a bit, but my VB skills are FAR from what is needed.

1. I want a routine that polls the GPS data from the IBus (the HEX code for this is known), and formats this for re-sending it to RR.

2. Make IBusComm Bi-Directional to send and receive messages to / from RR like: "SENDMSG;IBusComm;SPEEDLIMIT_90". I know there is a hack called IBusRR, but it has lost its ability to trigger RTS signals via the "ProcessEvents" module.

Anyone up for the job?


Kind regards

Marc in Norway

Marc-X

Hello World!

I have now tried to write speeds to the IKE directly. I have NOT succeded...
BUT... I have done something that's even BETTER !!! (for my goal that is...)

I can now manipulate the OBC directly to SET a speedlimit and ACTIVATE this limit if not activated before.

This means that I can, when approaching a GATSO, set the current speedlimit (stored in GATSO definition) to my OBC, and have it warn me with a PING and the current speed in the display in addition to the distance to the GATSO (from GATSOHunter / RR or similar) which can be written directly to the display. This means that you only have to send the speedlimit ONCE, send the distance continously and switch of the OBC speedlimit when GATSO Alert is canceled.

My goal now is:

FLASHING ARROWS IN CLUSTER whenever a GATSO is in close PROXIMITY -> OBC kicks in , Warning ping IF I'm over the speedlimit, -> the distance to the GATSO is diplayed and updated in the IKE.

Nice?

OK, now the codes

(REMEMBER, THESE CODES ARE FOR AN E46. THE CODES ARE TRIED ON MY 330d ONLY! EVERY OTHER CAR MIGHT DIE OR GET SOME KIND OF NASTY DISEASE IF THESE CODES ARE TRIED!!!)

Following example codes should be pretty easy to understand:

80 09 FF 24 09 00 32 31 30 20 cs SET SPEEDLIMIT TO "210"
80 09 FF 24 09 00 20 39 30 20 cs SET SPEEDLIMIT TO "90"
80 09 FF 24 09 00 20 35 30 20 cs SET SPEEDLIMIT TO "50"
80 09 FF 24 09 00 20 31 39 20 cs SET SPEEDLIMIT TO "19"
80 09 FF 24 09 00 20 31 30 20 cs SET SPEEDLIMIT TO "10"
80 09 FF 24 09 00 20 20 36 20 cs SET SPEEDLIMIT TO "6"
-----------------| speed |-----

FOURTH, FIFTH and SIXTH _DATA_ byte holds the speed.
30h = 0, 31h = 1, 32h = 2, 39h = 9 etc
20h = BLANK


3B 05 80 41 09 04 cs ACTIVATE SPEEDLIMIT in OBC
3B 05 80 41 09 08 cs DE-ACTIVITE SPEELIMIT in OBC



Kind regards

Marc in Tromsoe

krusha

what program are you using to send the ibus packets?

Enforcer

bus backwards

__________________