SMART 450 CDI 2003 ID List

Hello everyone,

Does anyone have an ID list for the Smart 450 CDI from the year 2003?

I would be grateful for any identification label.

Thank you in advance.

Welcome, even after the introduction "I am a beggar, a generous gift!".

What productive insights have you already uncovered that you would like to share with us?

Best regards, Rainer.

CAN-Diagnose wrote:

Welcome, even after the introduction "I am a beggar, a generous gift!". What productive insights have you already uncovered that you would like to share with us? Best regards, Rainer

I'm sorry, I didn't realize things were taken so seriously here.

Okay, I'm Flo, I'm from the Westerwald region, and I drive a 2003 Smart CDI. Since I was frustrated again about having a vehicle without a proper OBD interface, I decided to connect to the CAN-Bus.

I used the MCP2515 and a Raspberry Pi to sniff the CAN bus traffic with Wireshark.
0th byte 1st byte ... 7th byte
Now I have discovered:

0x210 = 2nd byte = Boost pressure (unknown resolution)

0x310 = 4th byte = Speed (engine, unknown resolution, stops at 124).
0x300 = 2nd byte = speed (?)
0x23A = 2nd byte = unknown, but interesting (probably related to speed).

0x080 = Wheel speed?

Since I'd like to build my own live display, I need the following items, among other things:

Speed.
Speed on bicycle - 200 km/h.
Temperature in Celsius.
Fuel tank capacity in liters.
Boost pressure in bar minus atmospheric pressure.
Temperature, intercooler.
Last in percentage.

PS: Here, My gift

LG
Flo.

First of all, welcome.

See if you can manage with the data. I'm not entirely sure, as they are actually designed for a roadster, but maybe they will fit anyway.

ID 0x080h, Bytes 0 and 1 -> Front wheel speed, 0-32767 RPM, resolution 0.5.
ID 0x080h, Bytes 2 and 3 -> Left wheel speed, 0-32767 RPM, resolution 0.5.
ID 0x080h, Bytes 4 and 5 -> Wheel speed, right, 0-32767 revolutions per minute, resolution 0.5.
ID 0x080h, Bytes 6 and 7 -> Wheel speed, high byte (most significant) and low byte (least significant), range 0-32767 RPM, resolution 0.5.

ID 0x190h Byte 2 -> Motor speed 0 - 6375 1/min with a resolution of 25.
ID 0x190h Byte 5 -> Engine temperature: -40 to 214 °C, resolution of 1.

ID 0x515 Byte 0 -> Outside temperature -40 to -80°C, resolution 1.
ID 0x515 Byte 7 -> Tank level 0 - 48 liters, resolution 0.5.

postmann wrote:

First of all, welcome. See if you can manage with the data. I'm not entirely sure, as they are actually designed for a roadster, but maybe they will fit anyway. ID 0x080h, Bytes 0 and 1 -> Front wheel speed, 0-32767 RPM, resolution 0.5. ID 0x080h, Bytes 2 and 3 -> Left wheel speed, 0-32767 RPM, resolution 0.5. ID 0x080h, Bytes 4 and 5 -> Wheel speed, right, 0-32767 revolutions per minute, resolution 0.5. ID 0x080h, Bytes 6 and 7 -> Wheel speed, high byte (most significant) and low byte (least significant), range 0-32767 RPM, resolution 0.5. ID 0x190h Byte 2 -> Motor speed 0 - 6375 1/min with a resolution of 25. ID 0x190h Byte 5 -> Engine temperature: -40 to 214 °C, resolution of 1. ID 0x515 Byte 0 -> Outside temperature -40 to -80°C, resolution 1. ID 0x515 Byte 7 -> Tank content 0 - 48l with a resolution of 0.5

Thank you very much.

I found the speed in PID 300. The first and second bytes, when combined, represent the speed.

News:

Found something else: Smart CDI 2003 4two.

ID 0x210

Byte [0] = Turbocharger intercooler temperature * 0.5 (assumption).
Byte [1] = Turbocharger boost pressure (Engine OFF = FE [Hex]; Engine idling = 00 [Hex])
I'm not sure whether it's related to the EGR valve or the turbocharger boost pressure. I have no idea what the minimum and maximum values of the sensor are. When I press the accelerator, the value increases and then decreases again, but I can't quite figure out why it's at 254 when the engine is off.

ID 0x515

Byte [6!!! not 7] = Tank capacity * 0.5

ID 0x090

0th byte.
"If 24 (brake pressed), if 20 (brake not pressed)."

ID 0x300

6th byte.
Clutch.
1-2-3 Locking sequence: 3 = Locked.
0 = Open.

3rd byte = Transmission.
Gang_Extension_Number___Gang is inside_Re-election
N____00_______01_________-----------
R____112______119________07
1____16_______17_________-----------
2____33_______34_________35
3____50_______51_________52
4____67_______68_________69
5____84_______85_________86
6 ____ 101 ______ 102 ________ ---

If you tap twice in the reverse direction now, it will behave like this:

For example, if you are in 4th gear and press the button twice to shift down, the displayed decimal number applies to the subsequent gear plus 2. So, for 2nd gear, the numbers would be 36.35, and then 34 (indicating the gear is engaged). If you press the button twice to shift up from 4th gear, you reach 6th gear with the decimal sequence: 100.101, then 102. I have no idea how 3x behaves.

ID 0x220 (speedometer)

0th byte:
03 = Standard (lights off)
23 (alternating with 03) = Left turn signal.
13 (alternating with 03) = Right turn signal.
43 = Turn on the light (starting with the parking light).
63 (alternating with 43) = Left turn signal.
53 (alternating with 43) = Right turn signal.

3rd, 4th, and 5th bytes = kilometer reading.

2nd byte, 6th, 7th = no idea.

As the programmer can immediately see, the solution is likely:

Bit 5 = 0x20 Left turn signal.
Bit 4 = 0x10: Right turn signal.
Bit 6 = 0x40 Light.

and bits 0-3 were always the same (0011 = 3) and still need to be investigated, as does bit 7.

alex wrote:

As the programmer can immediately see, it is probably: Bit 5 = 0x20 Left turn signal. Bit 4 = 0x10: Right turn signal. Bit 6 = 0x40 Light. and bits 0-3 were always the same (0011=3) and still need to be investigated, as does bit 7

.

Why doesn't anyone tell me anything?

Did I do that, or was it not understood, or was it a joke?

Since there are corresponding indicator lights in the instrument cluster for turn signals (left, right) and dipped headlights, bit 7 could potentially represent the high beam indicator, and bits 0-3 could also represent various 'indicator lights' in the instrument cluster.

alex wrote:

Am I doing that, or was that not understood, or was it a joke? Since there are corresponding control indicators in the speedometer for turn signals (left, right) and low beam, bit 7 could represent the high beam, and bits 0-3 could also represent various "control lamps" in the speedometer.

I seem to have misunderstood. It sounded like you already knew which frame and ID were used for the turn signals, etc.

No, it seems you haven't quite grasped the concepts of bits, bytes, hexadecimal, etc. yet, which is why I wanted to decode the data you collected for you.

alex wrote:

No, it seems you haven't quite grasped the concepts of bits, bytes, hexadecimal, etc. yet, that's why I wanted to decode the data you collected for you accordingly.

Ah okay, I apologize for my reaction.

I wanted to make it a bit clearer for those who are not as familiar with the topic, or to illustrate the behavior in question.

Yes, you are absolutely right. "The 0x03 values don't always appear. This morning, my test program didn't run because the 0x03 value had suddenly disappeared. It seems that this value only appears on a "smart" device that has just been initialized and is running only with the ignition on."

I will provide further updates.

As I said, I believe that the lower bits might simply be assigned to other indicator lights in the dashboard, such as the battery, ignition, oil pressure, etc.