Home

Awesome

FoDiMoCo - Ford display module (FDIM) controller Build Status

Configurator

What's this all about

Long story short. FoDiMoCo is easy-to-build DIY controller for your Ford USA vehicle that enables top dash display to show some useful information when stock head unit is removed. Initial name of the project was can-clock, as all I wanted is to have clock on dash display. Later it evolved, but name is still in the code.

This README is yet unfinished, nearest plans are to give more details on configuration and finalize messages description.

If you're too far away from the subject, there is introductory presentation I made on one of DIY meetups

Or enjoy video presentation of the project

Ford Dash display controller

Hackaday.io project page

If you don't want to read this long text but just want to get info on building your own FDIM controller, there are steps you need to build your own FoDiMoCo:

  1. Enjoy nice display photos and get feature overview
  2. Buy parts
  3. Order or make PCB
  4. Solder
  5. Flash
  6. Configure
  7. Plug into the car

If you like this project and want to support it, here is PayPal donate button. Project is non-profit, but I still need to buy parts to improve it and continue RnD.

Table of Contents

Overview

When this controller is plugged in, your dash display looks like that

Module itself looks like that (one of hardware variants)

FoDiMoCo is tested on Ford Escapes (including Hybrid) and Mercury Mariners 2008-2012. Should work on other Fords of the same generation, including Mustang, Fiesta, F-150, but it's not yet verified due to lack of test vehicles.

FoDiMoCo is built on Arduino and components that could be found on AliExpress and/or your local DIY electronics store, so it should be easy to reproduce. PCB is available for order at Dirt Cheap PCBs.

Functionality

Hardware options

Plugging into your vehicle options

Hardware

Parts list

And depending on mount type, choose one of the following options

Schematics

Schematics are more or less self-explanatory. Per components:

SPI protocol is used to control CAN interface. SPI CS line is wired to Arduino pin 10. CAN messages received trigger interrupt bound to Arduino pin 7.

I2C protocol is used to interact with Real-Time Clock module.

Voltage regulator is used despite the fact that Arduino Pro Micro can handle power voltage up to 12 volts. Real vehicle voltage with engine running can be up to 14 volts, so usage of separate voltage regulator gives more guarantees.

PCB

PCB is 2-layered with 3 inter-layer drills. DirtCheap PCB make them for you, other manufacturers may require extra wires soldering. Exact components placement is shown below in Soldering section.

Plugging into car

There are 2 possible options to mount the module in the car:

If you do care on your battery current, it's also possible to get power for the module from ACC power line, which powers down the module when vehicle is off and powers it up when it's on and running. This installation option can be done easier when installed behind FDIM display, as additional wires can be hidded inside your dash.

Behind FDIM

Into OBD

With separate ACC power wire

TBD

Soldering step-by-step

Take PCB

Place pin headers on breadboard to simplify soldering

Put PCB over pins and solder it

Solder angled pins for RTC as shown if needed

Rotate PCB and solder angled pins for power connection

Bend power regulator pins and solder it as follows

Rotate PCB and solder Arduino Pro Micro. Check that proper PCB pins are soldered to proper Arduino in/outs

Solder MCP2515 CAN board - start with side pins, then solder others. Soldering is better than socket here to improve vibration stability

Plug RTC module if needed. Fully assembled module looks like that

Solder CAN and power wires to pass-through connection as follows

Other side of connector

Fully assembled unit with pass-through connector

If ELM327 enclosure option is preferred, solder to ELM327 pins as per section above

CAN bus operation

Ford CAN buses: MS CAN and HS CAN

By design Ford vehicles use two CAN buses - more standard HS CAN (high speed, 500 kbit/s) and Ford-specific MS CAN (medium speed, 125 kbit/s). Newer Fords have even more buses, but since I don't own one - I can't tell anything on this subject.

FDIM display and most of less critical devices resides on MS CAN. It is possible to get access to MS CAN even from standard cheap ELM327 scanner by adding simple switch (modified ELM327 scanners with switch are already available on eBay or AliExpress). For more info refer to FORScan forum.

On the image below one can see OBD2 socket pinout for MS CAN bus.

Messages for FDIM

This section contains brief description of MS CAN messages used for FDIM display control and/or getting basic vehicle telemetry data to display on FDIM. All the information is obtained from open sources or by reverse engineering of MS CAN protocol using vehicles available for the author. No Ford official documentation was used in the process, so exact meaning of message formats may be slightly inaccurate, incomplete or inapplicable for specific vehicle models. Information listed below is used to control FDIM modules on Ford Escapes 2008-2010 and Mercury Mariners 2009-2010, both hybrid and non-hybrid. It is theoretically possible to use those messages on Ford Mustangs 2008-2010, F-150s 2009-2010 and Fiestas 2010.

0x50c - heartbeat

Description: Indicates the presence of ACM (Accessory Control Module) or headunit of the vehicle. FDIM display becomes inactive in the absence of the messages.

Rate: 10 Hz

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x50c30x010x020x00-----

0x3e8 - top line of FDIM module and heartbeat

Description: Sets sound source and indicates the presence of ACM (Accessory Control Module) together with 0x50c. FDIM display becomes inactive in the absence of the messages.

Rate: 1 Hz

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3e88source0x00volumeclock length?0x000x000x000x00

source can have the following values:

0x01 - AM

0x02 - FM1

0x03 - FM2

0x04 - PHON

0x05 - SYNC

0x06 - DVD

0x07 - AUX

0x08 - CD

0x09 - EMPTY

0x0A - SAT1

0x0B - SAT2

0x0C - SAT3

0x0D - PHON

0x0E - LINE

0x0F - 2 clocks if no text is printed, or one clock if text is present

volume value change displays volume bar

clock length have values only 0x00 or 0x04, possibly sets number of digits in current clock display

0x3ef - unknown

Description: Unknown. Sent on FDIM initialization and then with rate 1Hz with slightly different data

Rate: 1 Hz

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3ef80x320x320x320x320x030x000x00init

init value is 0x00 on 1st message sent and then 0x20 when module is activated

0x3f2 - clock

Description: Current time displayed. Time is given in binary-coded decimal format.

Rate: 20 Hz. Maybe possible to send less frequently.

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3f28hourminutedaymonthyearflags0x000x00

flags: 0x80 - time is adjusting (blink) 0xA0 - AM 0xC0 - PM 0xE0 - 24 hours 0xC0 - clock off

Special cases

Empty clock

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3f280xFF0xFF0xFF0xFF0xFF0x000x000x00

Examples

13:02

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3f280x130x020xFF0xFF0xFF0xF00x000x00

0x3f1 - unknown

Description: Unknown. Sent only once in FDIM start-up message sequence.

Rate: Not repeated

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3f180xF50x900x000x000x000x000x000x00

0x324 - text message

0x336 - text message

0x337 - text message

0x726 - TPMS request

0x72e - TPMS response

0x3b5 - TPMS broadcast

Description: Current tires pressure value given in psi. Present on newer vehicles (possibly 2010+), not present on hybrids. TPMS request-response protocol is more widely used to get tire pressure, but TPMS broadcast is easier to implement. Minimal pressure level is 25 psi, all values below are still shown as 25.

Rate: 1 Hz.

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3b58front leftfront rightrear leftrear right0x000x000x000x00

Example

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x3b580x250x190x220x230x000x000x000x00

0x423 - Speed, RPM, on/off status

Description: Speed in km/h, RPMs and engine temperature. Also indicates when vehicle is in off position.

Rate: Varies

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x4238speed1speed2rpm1rpm2temperature0x000x000x00

Speed (in km/h) = (speed1 * 256 + speed2) / 100 - 100

RPM = rpm1 * 256 + rpm2

Special cases

Vehicle off

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x42380xFF0xFE0xFF0xFE0xFE0x000x000x00

0x466 - GPS time data

Description: Current time obtained from GPS satellites, in GMT time zone

Rate: 1 Hz

Format

HeaderLengthdata byte 0data byte 1data byte 2data byte 3data byte 4data byte 5data byte 6data byte 7
0x4668hmins-dmony0x00

Hour = ( h >> 3 ) & 0x1F

Minute = ( min >> 2 ) & 0x3F

Second = ( s >> 2 ) & 0x3F

Day = ( d >> 2 ) & 0x3F

Month = ( mon >> 4 ) & 0x0F

Year = ( y >> 3 ) & 0x1F

Message sequences

Initialization

Heartbeat

Text output

TPMS request

Software

Source code structure

Flashing from Arduino IDE

Flashing from Platform IO/Atom

Flashing from Platform IO command line

Flashing on Mac OS X 10.15 Catalina

Since USB support for Arduino Leonardo/Spark Fun Pro Micro on Catalina is broken, I've prepared Vagrantfile to use VirtualBox to flash

default: avrdude done.  Thank you.
default: ========================= [SUCCESS] Took XXX seconds =========================

Configuration

Serial communication setup

Using WebUSB