the OBD is the computer in your car for sensors but has turned into a massive repository for anything CAN (car network) related. Some newer cars store radio station presets, seat positions, and even dimmer settings in the OBD alongside their battery-backed RAM. some models of BMW even store the unlock codes for their pricy radios in the OBD tables.
hardware like onstar is stored in a dedicated metal box usually under the glove compartment in most cars. it includes a harness for the OBD data, and a small modem usually mated with a riser. That modem also controls any wireless features and of course cellular transmissions. if you dont like your car phoning home, you can pull the riser or clip the antenna leads, but this will likely also affect wifi. Bluetooth pairing is generally part of the head unit in older cars, but if you have onstar this is commonly being added to the daughterboard for wifi.
as for processing? absolutely. sensor samples are sometimes taken thousands of times per second for things like airbag state and seatbelt pretensors. i guess if you counted up the bits and bytes over the CAM as your datapoint, then yeah its 25GB of data...but its not meaningful...unless youre in the process of a crash.
onstar is always my biggest gripe. anything that can remotely stop my car or unlock my doors makes me a little too paranoid, and ive never once pressed that stupid button expecting to speak to anyone who can help do anything meaningful.
but what about emergencies? onstar uses data triggers from the OBD/CAM to sense airbags in the deploy state, and that apparently triggers an automatic dial out to onstar whether you like it or not. If youre removing or replacing airbags, that means you have to disconnect onstar first or youll wind up with firetrucks and ambulances outside your garage. Speaking from experience.
Quite a bit of this data is already at your fingertips! open source OBD readers exist for linux. I use this one regularly to pull and reset codes for older mercedes: https://samhobbs.co.uk/2015/04/scantool-obdii-car-diagnostic...
the OBD is the computer in your car for sensors but has turned into a massive repository for anything CAN (car network) related. Some newer cars store radio station presets, seat positions, and even dimmer settings in the OBD alongside their battery-backed RAM. some models of BMW even store the unlock codes for their pricy radios in the OBD tables.
hardware like onstar is stored in a dedicated metal box usually under the glove compartment in most cars. it includes a harness for the OBD data, and a small modem usually mated with a riser. That modem also controls any wireless features and of course cellular transmissions. if you dont like your car phoning home, you can pull the riser or clip the antenna leads, but this will likely also affect wifi. Bluetooth pairing is generally part of the head unit in older cars, but if you have onstar this is commonly being added to the daughterboard for wifi.
as for processing? absolutely. sensor samples are sometimes taken thousands of times per second for things like airbag state and seatbelt pretensors. i guess if you counted up the bits and bytes over the CAM as your datapoint, then yeah its 25GB of data...but its not meaningful...unless youre in the process of a crash.
onstar is always my biggest gripe. anything that can remotely stop my car or unlock my doors makes me a little too paranoid, and ive never once pressed that stupid button expecting to speak to anyone who can help do anything meaningful.
but what about emergencies? onstar uses data triggers from the OBD/CAM to sense airbags in the deploy state, and that apparently triggers an automatic dial out to onstar whether you like it or not. If youre removing or replacing airbags, that means you have to disconnect onstar first or youll wind up with firetrucks and ambulances outside your garage. Speaking from experience.