I'm in the same boat. I don't understand the argument that manufacturers are using telematics as a loophole, since it seems that the 2013 law specifically says that while many uses of telematics are not covered by the law, those that are "necessary to diagnose and repair a customer's vehicle" ARE still covered.
> With the exception of telematics diagnostic and repair information that is provided to dealers, necessary to diagnose and repair a customer’s vehicle and not otherwise available to an independent repair facility [...] nothing in this chapter shall apply to telematics services [...].
So, are manufacturers doing things like including telematics that they claim "aren't necessary" but in reality are pretty important? If so, then independent repair shops are at a disadvantage, but the solution should be to force those signals to be available through the physical port.
Or is it a matter of independent repair shops not being able to compete with the dealerships who can get telematics to do things like email you when it is detected that your oil is low?
As far as I can tell, the 2013 law doesn't actually define "telematics" or "telematics data". This intiative does define the latter to be data that the car collects and phones home, and which the car itself may not store at all (but the "remote receiving point", as the law calls it, does store).
It seems to me that you can't reasonably require access via the physical port on the car to data that is not actually present in the car's systems. Or am I missing something?
Location: Worcester, MA
Remote: Yes (although willing to travel into Boston occasionally)
Willing to Relocate: No
Technologies:
Résumé/CV: See https://markhildreth.me/
Email: See https://markhildreth.me/
Over 10 years experience with various tech, industries, and positions, including time:
* As a sole developer, tech lead, team lead, and project manager.
* Working locally or fully remote.
* Developing for the desktop, web and mobile.
* Working on a technology I hadn't used before.
Recently been working on embedded development and Rust open source software. I enjoy working with a team to create something substantial, but just bad at personal networking so having trouble finding the right team :)
As others have stated, start with an Arduino. Have fun.
But I would recommend as a next step is to find a component that is more complex than an LED or Switch and with relatively good Arduino libraries (e.g., a 2x16 LCD screen) and try to write your own driver for it (e.g., a library that does all of the handling of the IO pins), using the data sheet of the component to figure out how to use the IO pins. Feel free to look at the Arduino library source code (or libraries for other languages).
I have done the same, using Rust and a Feather M0[1] and am now finding it easier to look at the datasheet of the more complicated ATSAMD21[2] microprocessor.
I noticed that some past postings did not include remote options for OneCodex, and I don't see anything on the Careers page. Is this offering only open to those in (or willing to relocate to) San Francisco?
> With the exception of telematics diagnostic and repair information that is provided to dealers, necessary to diagnose and repair a customer’s vehicle and not otherwise available to an independent repair facility [...] nothing in this chapter shall apply to telematics services [...].
So, are manufacturers doing things like including telematics that they claim "aren't necessary" but in reality are pretty important? If so, then independent repair shops are at a disadvantage, but the solution should be to force those signals to be available through the physical port.
Or is it a matter of independent repair shops not being able to compete with the dealerships who can get telematics to do things like email you when it is detected that your oil is low?