My Dreamforce session on DIY Telematics for OBD-II with a Raspberry Pi.
What if your car was connected to the Cloud, and had been logging sensor data for the past 30 days? What if it could automatically file a Case with your local dealership with the Diagnostic Trouble Codes from your car and all that log data attached? What if the Service department could give you a call to schedule an appointment to get it fixed, so you don’t even have to remember to call them? Since they have all the automotive log information they need to diagnose the problem before you even show up, they can even tell you what’s wrong over the phone and quote you an estimate for the repair.
Here’s a Raspberry Pi DIY project that does just that.
More info at: http://gersic.com/ive-connected-my-car-to-salesforce-com/
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Monitor your car from the cloud! DIY Telematics and the Internet of Things
1. Monitor Your Car from the Cloud
DIY Telematics and the Internet of Things
Tom Gersic, Salesforce.com
Director, Mobile Services Delivery
@tomgersic
2. Safe harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results
expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be
deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other
financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of
our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to
larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is
included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent
fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor
Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently
available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions
based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these
forward-looking statements.
21. OBD-II Modes
•
$01. Show current data
•
$02. Show freeze frame data
•
$03. Show stored Diagnostic Trouble Codes
•
$04. Clear Diagnostic Trouble Codes and stored values
•
$05. Test results, oxygen sensor monitoring (non CAN only)
•
$06. Test results, other component/system monitoring (Test results, oxygen sensor monitoring for CAN
only)
•
$07. Show pending Diagnostic Trouble Codes (detected during current or last driving cycle)
•
$08. Control operation of on-board component/system
•
$09. Request vehicle information
•
$0A. Permanent DTC's (Cleared DTC's)
23. Commands
tgersic-ltm:dev tgersic$ screen /dev/tty.OBDII-LCASPP 115200
>ATI (Print the ID)
ELM327 v1.5
>ATZ (restart the device)
ok
>ATL1 (turn linefeeds on)
ok
>ATH1 (turn headers on)
ok
>ATS1 (turn spaces on)
ok
>ATSP0 (set protocol to Auto)
ok
>03 (get stored trouble codes)
87 F1 12 43 04 44 00 00 00 00 15
43 is a response for a mode 03 query
24. Commands
tgersic-ltm:dev tgersic$ screen /dev/tty.OBDII-LCASPP 115200
>ATI (Print the ID)
ELM327 v1.5
>010C (“01” is mode 01 for realtime data. “0C” is for RPM.
84 F1 12 41 0C 0A EC CA
0x0AEC is 2796 quarter RPMs, so 699 RPM (idling)
41 is a response for a mode 03 query
0C is the command it’s responding to
Story time – heavy machinery, serial connectors, mobile devices, and a check engine light
http://www.flickr.com/photos/peerlawther/8155662027/
If it isn’t flashing, you’re probably just poluting the environment – loose gas cap, failing sensor, leaking something, etc.
Flashing means you have a severe problem
Controller Area Network
Engine Control Module
Body Control Module
VIN available, realtime sensor info, etc.
The Good:
-Low Power
On board UART
If you can get past having to write C that isn’t quite ANSI compliant, very simple to use
The Bad
-Not enough processing power to handle SSL/TLS, so need an intermediary btw Arduino and SFDC
-Can’t use both SSD and WiFi at the same time
UART – serial communications
TTL level UART is the simplest form of UART
1 = 5V, 0 = 0V