Bosch vehicle accelerometers

[AndreyB]

Two types of 4 wire OEM CAN bus accelerometers are https://github.com/rusefi/rusefi_documentation/blob/master/OEM-Docs/Bosch/yaw_rate_sensor_yrs_3.pdf and https://github.com/rusefi/rusefi_documentation/blob/master/OEM-Docs/Bosch/Data%20Sheet_68903691_Acceleration_Sensor_MM5.10.pdf

Let's see what's the cheapest option to wire longitudinal accel on a rusEFI vehicle!

As of today I've received some data https://github.com/rusefi/rusefi/issues/2225#issuecomment-931635265 from 0265005693 which does not exactly match yrs_3 format with four offset 0x8000 fields.

Also just ordered f037000002 which at least looks like MM5.10 we shall see what kind of data it would send me!

[AndreyB]

I also have a couple of six-wire Bosch sensors for which I do not have pinout. Those could very well end up being analog?

image.png (76.29 KiB) Viewed 15596 times

[blundar]

My 1992 (!!) R32 skyline has an accelerometer as part of the ATTESA all wheel drive system. Apparently, they're somewhat problematic. Not surprising they pre-date the solid state MEMS units these things are using!

[puff]

don't they need calibration each time before work (pretty much the same as with copters, when you have to make magic acrobatics with your drone before you actually fly)

[AndreyB]

don't they need calibration each time before work

https://github.com/rusefi/rusefi_documentation/blob/master/OEM-Docs/Bosch/Data%20Sheet_68903691_Acceleration_Sensor_MM5.10.pdf has nothing about calibration, you just power and it starts to send data out.

[AndreyB]

MM5.10 box mold 1275100853
I would like to thank Mitch Minton for telling me that F037000002 specifically matches Acceleration Sensor MM5.10 datasheet

open question if can-am 0265005955 or Mercedes 0009059101 send out same exact information anyone willing to donate $30 towards a 0009059101 sensor?

Log file https://rusefi.com/online/view.php?log=359

image.png (133.88 KiB) Viewed 15417 times

mm5.10-on-the-left-yaw3-on-the-right-same-4-pin-plug.jpg (321.1 KiB) Viewed 15407 times

[AndreyB]

Kirby says Housing : TE 1-967640-1, pins 144969-1, seal 967056-1 and plug 967067-2.

PS: "FOV" points at Front of vehicle, that's how you are installing those.

image.png (273.99 KiB) Viewed 15391 times

[Dron_Gus]

Subaru 27542AG011, Bosch 0 265 005 627
Silent after power on. While replies (ACKs) on other messages on CAN bus at 500K.
Seems need some magic kick to power on?
Consumes 100..110mA@12V.

1_YWqE_EMxE.jpg (149.09 KiB) Viewed 14751 times

[nmstec]

Subaru 27542AG011, Bosch 0 265 005 627
Silent after power on. While replies (ACKs) on other messages on CAN bus at 500K.
Seems need some magic kick to power on?
Consumes 100..110mA@12V.
1_YWqE_EMxE.jpg

https://www.bosch-motorsport.com/media/downloads/yaw_rate_sensor_yrs_3.pdf

Please get a databus log, and I'll see if I can find you a wakeup address/packet. It's usually Single byte packet with 0x01 for wake, and 0x00 for sleep

[nmstec]

MM5.10 box mold 1275100853
I would like to thank Mitch Minton for telling me that F037000002 specifically matches Acceleration Sensor MM5.10 datasheet

open question if can-am 0265005955 or Mercedes 0009059101 send out same exact information anyone willing to donate $30 towards a 0009059101 sensor?

Log file https://rusefi.com/online/view.php?log=359



image.png

mm5.10-on-the-left-yaw3-on-the-right-same-4-pin-plug.jpg

We have two can-ams in stock. Can Probe their buttholes.

[Dron_Gus]

https://www.bosch-motorsport.com/media/downloads/yaw_rate_sensor_yrs_3.pdf

Please get a databus log, and I'll see if I can find you a wakeup address/packet. It's usually Single byte packet with 0x01 for wake, and 0x00 for sleep

Unfortunately I have only this sensor from scrapyard. Not the whole car. So I can not get bus dump.
BTW this is from 2003-2008 subaru legacy/outback.

[nmstec]

Found the info. Page 294: https://www.bosch-motorsport.com/media/downloads/catalogs/printkatalog_2020.pdf

Please note:
CAN ID0 0x0170 (Rx) is used for synchronization and configuration of the sensor (SYNC). Make sure that the CAN ID 0x170 is not
used in your can network by any other device.

[Dron_Gus]

Found the info. Page 294: https://www.bosch-motorsport.com/media/downloads/catalogs/printkatalog_2020.pdf

Please note:
CAN ID0 0x0170 (Rx) is used for synchronization and configuration of the sensor (SYNC). Make sure that the CAN ID 0x170 is not
used in your can network by any other device.

Thanks for hint! On other doc I found that 0x070 is also used for Sync/Config. Few moments later:

Code: Select all

 (000.000246)  can0  RX - -  576   [8]  1E 76 4C 88 12 00 00 00
 (000.100267)  can0  RX - -  070   [8]  03 00 7E 00 04 00 00 79
 (000.099625)  can0  RX - -  070   [8]  01 00 7E 00 04 00 00 7B
 (000.100130)  can0  RX - -  070   [8]  03 00 7E 00 04 00 00 79
 (000.100516)  can0  RX - -  070   [8]  03 00 7E 00 04 00 00 79
 (000.099855)  can0  RX - -  070   [8]  03 00 7E 00 04 00 00 79
 (000.100355)  can0  RX - -  070   [8]  01 00 7E 00 04 00 00 7B
 (000.099753)  can0  RX - -  070   [8]  03 00 7E 00 04 00 00 79
 (000.100136)  can0  RX - -  070   [8]  01 00 7E 00 04 00 00 7B

This is sensor reply if I feed it with 070#0100 (cangen can0 -I 075 -g 100 -D 0100 -L 2 -x).
Still playing with data in 0x070 packet. Reply data and length depend on bits set in 0x070 payload.

[AndreyB]

Acceleration Sensor MM7.10

CAN ID 04 0x7DC, RX1 0x7DF and RX2 0x7D4 are used for configuration of the sensor (SYNC). Make sure that the CAN ID 04
0x7DC, RX1 0x7DF and RX2 0x7D4 are not used in your CAN
network by any other device.
CAN DBC file on request

https://www.bosch-motorsport.com/content/downloads/Raceparts/Resources/pdf/Data%20Sheet_336362635_Acceleration_Sensor_MM7.10.pdf