ozber.blogg.se

Ecu diagnostics menu
Ecu diagnostics menu








  1. #ECU DIAGNOSTICS MENU HOW TO#
  2. #ECU DIAGNOSTICS MENU PRO#
  3. #ECU DIAGNOSTICS MENU PC#
  4. #ECU DIAGNOSTICS MENU SERIES#
  5. #ECU DIAGNOSTICS MENU WINDOWS#

#ECU DIAGNOSTICS MENU WINDOWS#

If MS Windows is your thing then you could replace this Mac/Parallels/Windows/Easimap configuration with a PC/Windows/Easimap setup. I then to run Easimap inside that Windows virtual machine.

#ECU DIAGNOSTICS MENU PRO#

MacBook Pro Laptop: I used a MacBook as the host to run the Easimap Software but, that actually only runs on Windows… So in order to get around that small niggle, I used the Parallels Virtual Machine software to run Windows on the Mac as a “Virtual Machine Host”. The MBE 985, PiCAN and ECU are now three devices on the CAN bus. Another way of putting it is to say that the Easimap and Raspberry Pi are “in parallel” with each other on the same bus and both able to see the communications to the car at the same time. It allows the Easimap/MBE985 combo to connect to the ECU but also allows the Raspberry Pi/ PiCAN to “see” the communication between Easimap and the ECU – In the Internet world we would say that it allows the Raspberry Pi to “sniff” the CANbus traffic. OBD Y-Cable: In my setup I used this Y-cable to connect everything together. So this interface is doing some reasonably serious processing! OBD Y-Cable OBD Y-Cable It also has a 4Mb Flash chip on the board. The interface is using a 25Mhz Infineon processor that has a CAN bus interface built in. As you can see from the picture below, the MBE 985 is a reasonably complicated interface – more than you might expect in a CAN bus to USB interface. We were wondering if there was much translation going on between what we had seen on the USB interface and what was being sent to the CAN bus. Easimap sends commands to the car and receives data back by communicating through the MBE985 over USB which then sends the communications over the CAN bus.įor those of a curious nature, I pulled my MBE 985 apart to see what made it tick.

#ECU DIAGNOSTICS MENU PC#

MBE985: This is an interface device that converts CANbus data into a USB format that a Windows PC can access using Easimap. Easimap runs on Windows but in this test I was running Windows in a Virtual Machine on a MacBook Pro. Easimap can graphically show ECU data in real-time. For unlocked ECU’s (not the standard Caterham one) it can also extract/load Maps, and download/upload ECU images (the whole software and data setup of the ECU). We’ll be talking about Wireshark in a future post as it soon became apparent that Wireshark wasn’t properly able to decode the CAN bus communications from my car, but more on that in the next post! Easimap Easimap – MBE ECU Windows Diagnostic ApplicationĮasimap: A windows application from SBD that can interface with a 9A4 ECU and extract data. Tshark allows you to capture and view packets just like Wireshark but without the graphical interface. I used tshark because I was running my Raspberry Pi with no graphical user interface, just remote command line access using ssh from my MacBook. Tshark is the command line version of Wireshark (built from the same source code) and is what I used in this test setup. It runs on Windows, MacOS and Linux and can decode, or dissect as its known, hundreds of different network protocols and is immensely useful in today’s world of computing. Wireshark/Tshark: Wireshark is a Network Protocol Analyzer or packet sniffer application that can intercept packets on a network and decode them into a human readable form. If you have a Pi4 and want it to be powered from the CANbus then you’ll need the PiCAN3. The PiCAN2 SMPS (switched mode power supply) can also provide power from the CANbus to the PI. PiCAN: Is an interface card that plugs on top of the Raspberry Pi. PiCAN PiCAN3 sitting on top of a Raspberry Pi 4 The Raspberry Pi is running Linux and can interface to the PiCAN to extract CAN bus frames. Raspberry Pi: This is a Raspberry Pi 4, but anything from a Raspberry Pi 2 onwards is probably ok. So what is all that doing? Firsly, lets give a quick run-down on all the bits and pieces: Raspberry Pi Raspberry Pi 4 Raspberry Pi with PiCAN2, MacBook running Windows and Easimap+MBE985, connected to car through OBD Y-Cable The Raspberry Pi and PiCAN are propped against the front left of the laptop. Here’s a schematic view of the setup… Caterham ECU Diagnostic Test SetupĪnd then this is what it looked like in real life, Easimap is running in the top left corner on the screen of the MacBook. There are many ways of doing this but I settled on the following approach from my box of bits and pieces.

#ECU DIAGNOSTICS MENU SERIES#

If you’re looking for a post about “How to…” set all this up then that will be coming at the end of this series of posts in a “How to set up a Raspberry Pi to talk to a Caterham” postĪfter a bit of research over the years I’d already purchased a few bits and pieces to connect to a CAN bus. We need a test rig to do some experiments with.

#ECU DIAGNOSTICS MENU HOW TO#

How are we going to figure out how to talk the right communications protocols to the car to get at its internal data? Ok, so we have an OBD port/connector on our cars that connects directly to the ECU.










Ecu diagnostics menu