Sounds about right....

For what it's worth, gauge seems to be working fine on 3.0c_B. There was a bit of a trick due to some error in one of the menus, but I can walk you through it when you get your car back.

I got it all installed and working, and its great so far.
With 3.0c_B firmware, you can even plumb it into the lighting signal so that it will automatically dim when you turn the lights on.
Sorry for grainy screenshot from this video




https://cimg6.ibsrv.net/gimg/www.mia...2750373746.png

I wish you could set the alerts from the MS inputs instead of the analog inputs, but Hendrik @ CANChecked said it would require a lot of work on the firmware.
Everything seems to be working great though.

thanks for hosting the latest firmware! I haven't heard back from Hendrik as of late, so I'm starting to doubt support will continue for me on this guy.


Also, anyone have issues where the "knob" for navigating menus becomes unresponsive?

No issues with the knob. What additional support are you waiting on?

A couple things:

• Fixing calculation of AFR in F
  • Thats why I'm so happy that someone posted the latest firmware
• Ability to correctly display oil pressure and oil temp values from the Megasquirt over CAN to the gauge - I think it needs some additional interpretation from the CAN Gauge side to show the correct values
  • Hendrik mention he had some ideas around an interface to customize the what the CAN gauge shows, but its far in his backlog

The knob suddenly stopped responding, so have to check if the wires / connectors shook loose on the board, nothing seems visually wrong with the connection by just looking at it. I really like this gauge and Hendrik seems like a cool dude, but I want to be able to display oil pressure / temp and other values over CAN from the Ms3, and I don't think I'll be able to do that in the capacity I want anytime soon. If you can use it out of the box, go for it.

hey all,

Just some info to share:
I was digging into why the CAN gauge has issues with leveraging CANBus to show additional inputs from the MS3 (ie oil temp and oil pressure), and I found an awesome explanation from another gauge vendor. Ideally the CAN gauge would have to be able to interpret incoming data and allow a way to configure / define that data into a proper reading. Not a knock against the Hendrik's work (still awesome imho), just additional info.

Unfortunately, due to how MegaSquirt handles analog sensors, it is more complicated to support things like oil pressure and oil temp. Most ECUs have dedicated channels in units for something like oil temp in degrees C or oil pressure in PSI. With MS, they used “generic sensor” which transmits data with out any meaning.

any news about oil pressure show in canchecked?

Getting USB to Serial bridge to work with Windows 10
 

I recently tried to update my firmware using a Windows 10 computer and could not get the comm port to work. The driver that I finally found that would work was from Silicon Labs CP210x Universal Windows Driver v11.0.0. I installed it and had no problems.

Tip: Make sure that your serial->USB adapter uses an FTDI chip (if it's not explicitly written on the packaging, plug it in, fire up Device Manager and verify that it's using an FTDI driver).

Windows has always support FTDI drivers, including them in the OS or automatically downloading the driver, and FTDI serial-FTDI adapters are recommended for professional use because of it.
At a previous job, one of our customers sourced a lot of their own components for fleet rollout and none of their initial installations were functional due to their "bean-counter" purchasing the much-cheaper Prolific serial->USB adapters despite the explicit recommendation in our installation manual to use one with an FTDI chip.
That explicitly-written note saved our arse - their bean-counter got away with it too because he was just asked to source 500 serial->USB adapters, he was an accountant, not an engineer.

There are 2 other main serial->USB adapter chips, these are made by Prolific and Silicon Labs.

Most of the cheap adapters are made in China from an early-copied Prolific chip.
Prolific got annoyed about this and changed their design and driver accordingly so the knock-offs no longer work in Windows without you manually installing an older Prolific driver (from Windows 2000 I think).

Silicon Labs drivers have always needed to be installed manually in Windows for some reason (maybe they haven't paid MS to include them?) and you need to find the correct version which is annoying.

Bottom Line: Only buy FTDI serial->USB adapters, otherwise you're going to need to jump through a few hoops to get them working.

bringing this form the dead...
debating between the DIYAutoTune or the
VADPro (reseller, changed the label)
same price point, but the VADPro seems to have more inputs. have all the issues mentioned in this thread been fixed?
long therm, will this be even supported?
https://cimg3.ibsrv.net/gimg/www.mia...d2e758c40d.jpg