Group Actions
Engagement
  • Author Author: dougw
  • Date Created: Date Created
  • Views 1223 views
  • Likes 3 likes
  • Comments 5 comments
Related
Recommended

Vehicle Simulator Project - update

dougw

blog entry #3

 

see also blog #1 Vehicle Simulator - VTR / RTR   and blog #2 Vehicle Simulator Project

 

This update shows the Car Cape running on a Beaglebone Black.

Both vehicle simulator and vehicle recorder systems have been built and they communicate with each other fine over the CAN bus.

We are still having a devil of a time sorting out OBDII communications with a real vehicle. This is the main reason for such a long delay since our last posting, however I figured we need to post at least an update.

So far there are 6 screens to display sensor data from the sensors on the Car Cape.

We have not spent much time on these as the OBDII interface has been taking so much time.

Here are some screen shots to give some idea of what they look like:

image

image

image

This screen shows location coordinates when the GPS finds enough satellites. Right now it is still showing UTC time.

image

This is a little warm because I have some bright lights shining directly on the module.

image

image

We are still sorting out some of the analog channels...

image

The LCD updates "instantly" in response to the keypad scroll buttons because it is interfaced via SPI.

The following video demonstrates how quickly the LCD repaints after each scroll button push:

Here is a picture showing the OBDII breakout module connected to the Vehicle Simulator/Recorder module:

image

Here is a picture showing the card stack making up the vehicle simulator/recorder module:

image

Right now we are analyzing commercial OBDII readers like the one shown above to determine how to handle vehicle communications properly.

 

Quick update:

We have started using one of these CAN bus interfaces to help analyze what is going on with the CAN / OBD2 bus:

image

This module is helping significantly at this stage to get us over an impasse.

The 2 BBB modules communicate with each other.

The 2 BBBs can communicate fine with the USB-CAN module above.

The commercial reader can also communicate fine with the USB-CAN module.

The commercial reader does not communicate with either BBB.

It seems they somehow think the frames are invalid.

Unfortunately my software partner is away for a month starting today, and the rig is at his place, so further updates will be delayed for a month.

Parents

  • Hi Doug,

     

    Wow, this is looking great. Congratulations to you and your colleague, this is an incredible project. Definitely a very feature packed board. What are the white connectors for, on the right side of the board, and the ones on the left side?

  • in reply to shabaz

    Hi Shabaz,

    The 2 pin connector on the left allows a jumper to disable write protection of the cape ID EEPROM. It is only really needed when first programming the standard cape EEPROM which identifies the functionality of the cape.

    The other "white" connector on the left is the BBB ethernet connector - I will post a angle view to show the module stack up.

    The 8 pin connector on the right is the CAN bus interface - it goes to an OBDII breakout module (both male and female OBDII connectors) that includes a 5 V power supply for the BBB when it is mobile. I will post a picture of it in its unpackaged form.

Comment
  • in reply to shabaz

    Hi Shabaz,

    The 2 pin connector on the left allows a jumper to disable write protection of the cape ID EEPROM. It is only really needed when first programming the standard cape EEPROM which identifies the functionality of the cape.

    The other "white" connector on the left is the BBB ethernet connector - I will post a angle view to show the module stack up.

    The 8 pin connector on the right is the CAN bus interface - it goes to an OBDII breakout module (both male and female OBDII connectors) that includes a 5 V power supply for the BBB when it is mobile. I will post a picture of it in its unpackaged form.

Children
No Data