Let’s Chime In: GM 29 bit CAN Chime Control

Posted On January 31, 2010 at 6:37 pm by / No Comments / CAN BUS

For those of you who like to leave there car keys in the ignition while the driver door is open or who don’t where a seat belt, you’ve heard the Chime and have probably cursed it many, many times.  Well I can help you defeat it or embrace it.

First you need to gear up.  You will need to connect to the GM Single Wire CAN bus.  This is on PIN 1 of the DLC (OBD II port).  SW CAN runs at 33,333 bps (standard rate).  So once you hooked up your device (see earlier posts for info on these), you should be able to communicate with the vehicle over SW CAN.

So now you just need to know the message, but first a crash course in GMLAN 29 bit ID.

The 29 bit ID is broken into three pieces.  The Priority, Parameter ID, and Source Address.  The priority is the first 3 bits of the ID.  Priority allows for more important messages to get greater access to the network in the case of high network congestion.  This leaves 26 bits reaming of the 29 bits.  These are divided evenly amongst the Parameter ID and the Source Address (i.e. 13 bits each).

The Parameter ID is essentially the ID for what will be sent in the data portion of the frame.  The Source Address is the node that sent the message.  So messages from the address 040 all come from the same node.  Cool huh!?

So let’s get to CHIME already…

Chime has a parameter ID of 0x0F.  This means that if you want to send Chime you must put 0x0F starting at the 26th most signifigant bit. For example 0x1001E060 would be a chime command (0xF) with priority 4 (0 is highest priority) and send from node 0x60. Its easier to explain when we see this in binary. 0x0F is #b0:0000 0000:1111.  So we put the whole ID together by taking the priority then parameter ID then source address.  This will give us #b1:0000 0000:0001 1110:0000 0110:0000 (where the parameter ID is in bold).

Ok now that we’ve finished with the ID, let’s look at the data.  The data portion is what is defining all of the characteristics of the Chime.  In other words will this be a long chime or a short one, a click sound or a ding sound, a one-time sound or multiple times?  There are 5 bytes that define all of these characteristics.  So you will see that you can do a lot.

The first four bits of the first byte (the most signifigant nible) defines the speaker that this sound will come out of.  For the front left speaker it is the most signifigant bit (or bit 7 of the byte). Next is the passenger (bit 6), then the rear driver side (bit 5), then rear passenger side (bit 4).  So if you wanted to make the sound in only the driver speaker then you would send 0x8X in the first byte (where X is irrelivent).

The second nibble of the first byte describes the type of sound it will be.  Either a beep or a click.  Experiment to find out what these are.

The second byte describes the intonation of the chime.  So you can adjust this on your own as well.

The third byte is the amound of repetitions you would like the sound to make.  So if you want the chime to happen three times. This should be set to 3.

The fourth byte describes the duty of the chime.  Experiment with this on your own.

Last byte is unknown currently.  But if you know send me an email, I’ll update this entry.

So if you would like to send chimes to your car, here you go.  If you want to cancel a chime, it should be good enough to have your software wait for a chime command and simply send one of its own with a really fast chime and a 0% duty cycle.  That should end the last chime command.

Good luck and as always click on the contact link above if you have questions!

Leave a Reply

Your email address will not be published. Required fields are marked *