NexDeck

From Makers Local 256
Jump to: navigation, search

Creator:
opticron
Status:
Research
Born On:
19:55, 10 March 2014 (CDT)
Last Updated:
18:36, 06 May 2017 (CDT)

Overview

This project encompasses single and double DIN stereo decks meant to interface with a smart phone and provide a customizable experience tailored to the wants or needs of the user.

Single DIN Unit

This unit utilizes tight integration with the smart phone to deliver audio and other services.

Features

  • Uses wireless charging to keep your phone topped up while being used as your headunit (no cables!)
  • FM reception using the vehicle's antenna (via BT or via microcontroller via BT)
  • Hands free calling operation via BT
  • Audio playback/control via BT
  • Auxiliary headphone jack or RCA input
  • Jog knob for volume
  • Dual momentary toggle switch for next/previous
  • Can integrate with a BT OBD2 reader for displaying car info
  • Can use the OBD2 integration with a WiFi/BT camera for backup cam
  • Google maps on your dash!

Pros

  • Lower cost
  • Wider options for devices
  • Smaller footprint
  • More space for controls
  • Less effort
  • If there is extra room, additional components could be installed.

Cons

  • No dedicated device/requires that the phone come out of your pocket
  • Storage restricted to on-phone
  • Requires phone/tablet at all times to work
    • May be possible to do dumb aux passthrough by default
  • Requires tight integration with the device (custom apps at the least)
  • Smaller screen for less mapping awesomeness
  • Lower quality audio for HQ sources

Parts List

  • Single DIN mounting hardware
  • BT A2DP/AVRCP/HFP receiver with custom wiring for the jog knob and toggle interface(Possible Solution)
  • Wired MIC for HFP
  • Microcontroller
  • Android compatible OBD2 BT device
  • BT module for microcontroller (RFCOMM connection only)
  • SPI/I2C/UART controlled stereo audio switch(Possible Solution)
  • SPI/I2C/UART controlled FM receiver(Possible Solution)
  • 4-6 channel output stereo audio amplifier(300 watt 4 channel)
  • Phone mount/charging hardware
    • Air Dock recommended for qi-compatible devices
    • 8-22v to 5v usb charger (3amp 15W)
  • Power conversion hardware for embedded devices

Work Required

Materials

  • Fitting the chosen mounting hardware into the single DIN enclosure

Electronics

  • Get power hooked up to everything
  • Get microcontroller wired to:
    • BT RFCOMM module
    • BT audio device
    • user controls
    • Audio switch
    • AMP (if applicable)
    • FM receiver (optional)

Android Software

  • Writing Android app for control/orchestration of the devices via BT

Microcontroller Software

  • BT RFCOMM interface
  • Control of the BT device
    • Needs to at least be able to put the device into pairing mode
  • Audio switch
  • Front controls
  • Amp
  • FM receiver

Double DIN Unit

This unit utilizes a much more loose integration with the smart phone and uses only standard interfaces to communicate with it.

Key Features

  • Uses wireless charging to keep the tablet topped up, tablet is necessarily integrated into the dash
  • FM reception using the vehicle's antenna (via USB or via microcontroller via USB)
  • Capable of reading USB storage peripherals
  • Hands free calling operation via BT
  • Audio playback/track information/control via BT
    • AVRCP1.5 features like browsing would be nice, but probably limited to 1.4/tag info for now
  • Auxiliary headphone jack or RCA input
  • Jog knob for volume (is there space for this?)
  • Dual momentary toggle for next/previous and FF/RWND (is there space for this?)
  • Can integrate with a BT OBD2 reader for displaying car info
  • Can use the OBD2 integration with a WiFi/BT camera for backup cam
  • Google maps on your dash!

Pros

  • More storage options
  • Dedicated unit for operation
  • Better integration into car
  • Able to interface and work properly with any smart phone that has BT
  • Larger screen for more mapping awesomeness
  • Higher quality audio for HQ sources (USB DAC)

Cons

  • Higher expense
  • Tied to specific tablet
  • More space
  • More initial work to get the tablet/OS where we want it

Parts List

  • Double DIN mounting hardware
  • Nexus 7 or other tablet supporting USB OTG/Host
  • Wired MIC for HFP
  • Microcontroller (connected via USB, ADK-compatible)
  • SPI/I2C/UART controlled stereo audio switch
  • SPI/I2C/UART controlled FM receiver
  • USB hub
  • USB extension cable (for front panel access)
  • 4-6 channel output stereo audio amplifier(300 Watt/4 Channel)
  • Tablet mounting hardware
  • Tablet wireless or USB charging hardware
  • Power conversion hardware for embedded devices

Work Required

Materials

  • Retrofitting the tablet into the mount

Electronics

  • Get power hooked up to everything
  • Get microcontroller wired to:
    • tablet
    • BT device (if BT sink can't happen)
    • user controls
    • Audio switch
    • AMP (if applicable)
    • FM receiver (optional)

Android Software

  • Getting the tablet OS into shape for talking to USB devices
    • Might need a custom OS with a special kernel
  • Writing Android app for control/orchestration of the USB devices
  • Getting BT audio sink mode working
    • This is a BIIIIG IF, otherwise use the same BT device as with the single DIN setup

Microcontroller Software

  • Tablet via ADK
  • Control of the BT device (if BT sink can't happen)
    • Needs to at least be able to put the device into pairing mode
  • Audio switch
  • Front controls
  • Amp
  • FM receiver

Non-Tablet Double DIN Unit

This unit utilizes a SBC with USB3 and is also a dash cam/reverse cam. This is basically Android Auto done right.

Key Features

  • FM reception using the vehicle's antenna (via USB)
  • Capable of reading USB storage peripherals
  • Hands free calling operation via BT
  • Audio playback/track information/control via BT
  • Auxiliary headphone jack or RCA input
  • Jog knob for volume (is there space for this?)
  • Dual momentary toggle for next/previous and FF/RWND (is there space for this?)
  • Can integrate with a BT OBD2 reader for displaying car info
  • Can use the OBD2 integration for backup cam
  • Google maps on your dash!

Pros

  • More storage options
  • Dedicated unit for operation
  • Better integration into car
  • Able to interface and work properly with any smart phone that has BT
  • Larger screen for more mapping awesomeness

Cons

  • More space
  • More initial work to get the OS where we want it

Parts List

Work Required

Materials

  • Retrofitting the screen into the mount
    • It's slightly to large to fit through the double din mount, so either have it spaced out a bit or put it in the double din adapter piece

Electronics

  • Get power hooked up to everything
  • Get cams and other peripherals hooked up via USB hubs

Android Software

  • Get Android 7.x running on the SBC
  • Enable Android Auto audio routing tweaks
  • Enable HFP client
  • Enable A2DP client
  • Make sure cameras, hubs, radio module, etc. play nice with OS and that there is adequate bandwidth
Retrieved from "https://256.makerslocal.org/wiki/index.php?title=NexDeck&oldid=21272"