Hello there

Based on recent publications, a lot of peoples are going at it with various ESP32 1.75 inch screen, i started mine around 2 years ago with TFT screen and some ESP32 WROOM. I went to the 1.75 inch screen route and since i've been trying to develop this.

I'm aware of this already existing same kind of project that, i swear lmao, learned existence only today (https://github.com/Mr-Mika/M-Gauge/**)**

What i tried to do differently based on the other projets it the ability to wire physical sensors as well for older cars where the CANBUS / OBD data doesn't contains as much informations as recent vehicules.

On my case, it's my AP1 S2000 which doesn't provide oil pressure / temperature from the ECU.

So, i started working on a breadboard, doing at the beginning hand made code (now almost fully assisted with GPT) to create something that could be incorporated on any vehicule, and also provide the ability to wire sensors directly to the board

I went also a different to try and create my own custom PCB (still tweaking the board at the moment) to be able to have something the most "out of the box" possible :

• 8 screens fully customizable
• 4 values per screen
• Unit, Threshold and Threshold color per value customizable
• 2 Physical Sensor input
• OBD2 Bluetooth BLE Dongle support (i'm going to add CANBUS capabilities also) (both will be supported / compatible)
• OBD Values discover and assigned to specific values that can be renamed and customized as well
• Smartphone application to manager each parameters per ESP Unit
• Gauges data exportable with history data (only physical sensor for now but easily addable for each values)

I'm adding also some picture and videos of what i've done so far

The code is sitting on gitlab for now, i also wanna go opensource but i want to know if people would be interested

Side not, i'm clearly not confortable with PCB conception, i've went the AI route with my own breadbord conception as a baseline, i think there's clearly more to refined / polish on this side

For physical sensors, i also want to add more conversion table for different brand and type of sensors, right now i'm only using it for oil pressure, but the idea is to support more sensors

What's your thoughs ? I'm aware there's lot of similar projets going around and i found out about them really recently

Hi all,

We just released a new CANsub firmware (02.05.01) that adds a 'dashboard view' to webCAN, our free browser-based GUI that runs on the CANsub.

This lets you build powerful custom dashboards for real-time visualization - with zero installation or backend required (everything runs in the browser).

You can read more about this in the CANsub Intro - if you get a few min to check it out I'd be very interested in any thoughts/ideas/feedback, e.g. what you think would be useful for your use cases.

As with the CANsub in general, we make it easy to create new dashboards via AI agents (if you want). I e.g. used this in my AI CAN sniffer article to create a quick Hyundai i10 dashboard to show the OBD2 vs. proprietary CAN signals, you can find a clip of the dashboard in the showcase 1 example.

Happy to hear your inputs!

Martin, co-owner at CSS Electronics

I could not find published CAN information for the Alfa Romeo Giulietta 940, so I worked from captures on my own 2011 car, starting from fmntf's fiatcan work on the Fiat Doblò and karolkrupa's alfa-blue-me for the 159. A Raspberry Pi Zero W now takes the place of the dead Blue&Me module, node 4021.

What the captures settled:

• B-CAN at 50 kbit/s, 29-bit identifiers, ID = topic<<16 | node. Body Computer 4000, cluster 4003, radio 4005.
• **PROXI:** about a second after the bus wakes, the Body Computer sends `1E114000#`. On my car, nodes `400A`, `4003` and `401A` answered within milliseconds with the same six-byte value. A silent node gets three retries; a mismatch makes the odometer blink. The Pi uses the value read from that car. The public code reads it from a setting that is covered by tests but has not yet been run in the car.
• The Body Computer's PROXI record `2023` had to list the telematic unit as present. I read and saved the original record before changing it with the documented script and keeping an undo file, then ran the alignment with the Pi answering diagnostics as the telematic ECU. This changes the car's configuration and is not a generic value to copy.
• **Source handshake:** MEDIA makes the radio send 06314005#0C…; the node has about 100 ms to answer …84 on 06314021. Unprompted answers are ignored.
• **Wheel buttons:** frame 06354000 from the Body Computer, one bit per button, same layout fiatcan documents for the Doblò.
• **Track text:** the Doblò's format and 6-bit character set work on the Giulietta's radio.
• The body-B-CAN pair on OBD pins 1 and 9 carried body traffic but no `18DA…` diagnostic frames during a PROXI alignment on my car. It is usable for body traffic; I used the module connector for the complete Blue&Me captures.

One rule in the software: it transmits only frames first recorded on this car, each tied to a capture file and timestamp. A fresh install is listen-only.

Write-up with the frame tables, timing and wiring:

https://duzgun.org/blog/giulietta-blue-me/

Corrections welcome, especially from anyone with another 940

When you want to record what a car is doing over time, there are two common starting points. One is to listen passively to the CAN bus and record every frame. The other is to actively poll the ECU with diagnostic requests, usually the standardized OBD-II PIDs or a manufacturer's UDS reads. Both get you data, but they fail in different ways.

Passive sniffing is read-only in principle, so it does not ask any module for anything. You see the real traffic at the real rate, with accurate timestamps, and you can catch short events that a polling loop would miss. The downside is that raw frames mean nothing until you decode them. Without a database file or a lot of reverse engineering, you are staring at hex and guessing which bytes are RPM, throttle position, or a fault flag. Decoding also depends on the bus speed, the gateway's filtering, and whether the manufacturer even sends the signal you want on the bus you can reach.

Polling is the opposite trade. The standard PIDs are documented, so the answers are easy to interpret, and most cars respond to them without any special setup. The costs are speed and coverage. Each request and response takes time, so your sample rate is limited and you get a snapshot rather than a continuous signal. The standard only defines a small set of parameters, so anything manufacturer specific needs UDS reads, which require knowing the addresses and data identifiers, and those vary a lot between makers and even between model years. Active requests also add load to the diagnostic channel and can interfere with other tools or sessions if you are not careful about who else is talking.

A common middle ground is to use passive capture to understand timing and relationships, then use polling or UDS to label the values with known names. Whether that combination is practical depends heavily on the vehicle, so I would not assume results from one platform carry over to another.

For people who have done both: which problems did you hit first, decoding the passive data or getting reliable answers from polling? I am curious whether the gateway filtering was the bigger blocker or the lack of documentation.

Hi all! I'm looking for testers for OBDash, my first app. It turns an Android phone, tablet or head unit into a live car dashboard.

You don't need a car or an OBD adapter to help. The app has a demo mode with simulated data, so you can install it and try every skin from your couch.

How to join:

1. Join the tester group: https://groups.google.com/g/obdash-testers

2. The app is in Google's review right now. As soon as it's approved, I'll email the group the Play Store opt-in link.

3. Install it and keep it installed for 14 days.

It's free for testers. Drop a comment with your own app's tester link and I'll join yours too.

Thanks!

Hi. Does anyone have account on mhhauto forum and could help me to contact few users from there? I would send you links to users and a message (containing my phone number) that I would love you to send them. Its about scam company that I wanted to sue and I saw there are more victims and those people lost money on this company too. Anyone willing to help? Thank you.