Log In | Register
Skip to main content
Topic: Our Experience with UltraGauge Blue (Read 362 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.
Our Experience with UltraGauge Blue
After reading several threads on this forum about OBD-II scanners, I was attracted to the idea of monitoring transmission fluid temperature (TFT) and oil pressure (misguided notion; see below), as well as the ability to read codes and set alarms.  Also, many OBD-II scanners are relatively inexpensive, making for a low bar to entry.

This post is to share our recent experience with the UltraGauge Blue OBD-II scanner ($79.95).  UltraGauge Blue connects via Bluetooth to an IOS or Android device to support gauges, trouble codes, alarms, and custom programming (the latter at your own risk).

There are many scanners to choose from, the most popular with RVers seem to be ScanGauge and UltraGauge.  We chose UltraGauge because

  • We liked the idea of a Bluetooth interface to a smartphone. We did not want another permanent, single-purpose display device in the cab.
  • We have abundant programming and IT talent in the form of my wife, Sue, so we figured that the programming interface wouldn’t be a problem.
  • Comments on this forum that the ScanGauge can be difficult for some people to read effectively eliminated it for us.

UltraGauge Blue is only sold direct from ultra-gauge.com.  The process was easy and the product arrived 3 days later in good condition in a package hardly larger than the scanner itself, which is very small. Product documentation is available as a PDF on their website (http://www.ultra-gauge.com/blue/utragauge-blue-user-manual.pdf).  Though not perfect, the documentation is far better than average for tech gear.  Kudos.

Of some concern: I always try to acquire some familiarity of a company—*people*—I am sending money to, especially when it’s a tech product.  I had no success with Ultra-Gauge.com.  No address.  No ‘About Us’ on the website.  No name attached to their responses on the Support forum.  I speculate that the company is very small.  A better investigator than I will no doubt turn up useful information, but Ultra-Gauge should make this information easy to find and present it proudly.   :(

Installation was easy.  Install the UltraGauge app on my phone (iPhone 6 Plus).  Install the scanner in the OBD-II port under the steering column.  Pair the two via Bluetooth.  The install instructions in the manual are clear.  UltraGuage then retrieved my VIN and other basic information, which I then uploaded to ultra-gauge.com, which then downloaded updated vehicle information and some Ford “custom gauges.”  Finally, I modified the Fuel Tank Size value to reflect my LD (2011, 27’ MB).  The app to website communication (upload/download) took longer than expected but completed without a problem. 

Of the generic instruments and gauges supported by the 2011 E450 (Triton V10), all worked straightaway.  And that’s where the easy part ends. 

None of the Ford custom gauges worked, including both TFT gauges.  Why two?  Why did neither work?  We still don’t know. 

This is where my faithful, live-in software architect and IT expert, Sue, took up the cause and after some slogging around the Internet found the correct OBD code (PID) and values for the TFT.  Here are the values she used to create a custom TFT gauge (in the “Custom Gauge” feature of the app).

Warning: Custom programming can create unexpected problems.  See Sue’s comments, below.

Description  --  These values are user defined and can be anything
       Name:  TFT
       Descr: Trans Temp2
Command (0-9, A-F) 
      Cmd: 07E003221E1C
Response Options
      Rsp Bit Offset (0-255):  0
      Number of Rsp bits (1-32):  16
Response signed (checked=signed)
      First units
            First unit:  F
            Multiply:  9.00
            Divide:  80.00
            Add:  32.00
      Second units
            Multiply:  1.00
            Divide:  1.00
            Add:  0.00
      Limits
            Min:  0.00
            Max:  300.0

Sue here.   My turn.   :)

Given that Sidra is a 2011 E450, I began researching CAN (Controller Area Network) protocols for all vehicles (generic codes) and Ford specific codes. There are ways to interrogate ECMs (electronic control modules) for pre-CAN vehicles (model years as late as 2002), but I did not study those codes. As Jim noted, there are ample warnings issued by manufacturers and users alike that faulty coding can create serious problems for your vehicle. You are dually warned. As a basic precaution, I do not make any modifications while our engine is running. I also have avoided changing the behavior of our systems. We are simply monitoring the state of Sidra where we are both interested and able.

Setting the parameters for a custom gauge is pretty easy, once you know what values the parameters should hold. There are scores of codes for monitoring various attributes that are tracked by the ECM; unfortunately, most of the Ford codes I found are applicable to diesel or lighter duty vehicles (I tried a lot of them).

To add a custom gauge to an UltraGauge Blue dashboard, navigate to the Custom Gauges setup (Settings > Custom Gauges > + to add a custom gauge.). At this point you are given the option to enter the parameters in one of three formats: UG MX MGauge, X-Gauge TM, or UltraGauge. Since the X-Gauge format was most prevalent in various online forums, I chose to use that format. It’s quite simple to fill in the required fields. Once you have entered all of the information and saved the gauge, there is a ‘test’ option in the title bar for the custom gauge page. For a custom gauge to be used, the gauge must pass verification (testing). If a custom gauge passes the test, a ‘V’ (for valid) will be displayed in the main custom gauges page in the Valid column. If the test fails, or if a test has yet to be performed, an ‘N’ will be displayed. Make sure your custom gauge has a V. If not, a 0 value is displayed for your gauge on your dashboard.

After trying various transmission temperature parameter settings, I finally found one that passed verification. We were pleased. That didn’t last long because the reported temperature never went over 100° F. Well, in the Limits parameter section, the default limit was used (guess what that was… yes, 100). So, after changing that value to 300, we had a functional gauge. I would suggest that if you use a format other than the UltraGauge format, you verify all of the parametric values in the native format.

As an aside, Jim mentioned that all of the provided Ford custom gauges did not work. I tested each, and each of them failed verification. Perhaps they will work for others, but I wouldn’t count on it.

If anyone is interested, I can provide information as to how to transform ScanGauge parameter values into UltraGauge values, but I’ll hold off unless there is interest.

Jim here, again.

While Sue worked on the TFT gauge, I looked into what turned out to be my misapprehension that oil pressure in our E450 can be monitored via an OBD-II device.  Here’s what many of you already know.  Ford Triton V10 engines come with an oil pressure sensor that is really just a switch.  When the engine is started, if the pressure goes to or over 6 psi, the needle in the dash gauge swings to a middle position, and, as far as the computer is concerned, everything is hunky dory.  If oil pressure fails to get to 6 psi, or falls below 6 psi, the dash gauge needle goes to the far left and an idiot light illuminates.  Ford defends this choice by claiming that vehicle operators don’t know how to interpret oil pressure readings and too often mistake a normal condition for a problem, which delivers them to the Ford service department, costing everyone time and money.  So, without a real pressure sensor, there’s no way to get real data on the OBD-II port or otherwise.  An option is to replace the switch with an analog pressure sensor and add a dedicated analogue gauge to the cab. 

About all those Ford custom gauges that didn’t work, we opened a support ticket and more than a week later got a response asking for all our log data.  Because we weren’t interested in any of the custom gauges, we let it drop. 

Since we installed UltraGuage we have driven nearly 2000 miles. How are we using the UltraGauge?  Are we getting the value we hoped for?

It may sound silly, and perhaps it is, but we primarily use it as a second dashboard that is placed between us where it is easy for both driver and passenger to monitor.  See below for a screen capture.  I’m surprised by how much I like the precision and clarity of the digital display.  It’s easier for me to read than the dashboard and provides much better information.  We know precisely how much fuel we have, what the engine coolant temp is, what the TFT is, and how these values change in various road conditions, speeds, and ambient temperatures.  Monitoring TFT is new to me and I’m still learning what normal is for various conditions.  I understand that it is appropriate to alarm at 235 degrees Fahrenheit.

We are also playing with other screens for things like trip information and fuel efficiency.  We haven’t yet set up any alarms.

Custom screens are easy to build, though it took a bit of trial and error to get the hang of it.  It’s also easy to change colors, modify label text, and change size.  That said, the app’s user interface has lots of quirks.  There is no evidence that it’s been touched by a professional User Experience designer. 

For basic information on OBD-II PIDs (Parameter IDs), see OBD-II PIDs - Wikipedia

Jim and Sue
Jim & Sue
Formerly owned: 2011 27' MB, Sidra
Re: Our Experience with UltraGauge Blue
Reply #1 –

Excellent information, Jim & Sue! I'm sure it will be helpful to others.

I've been using the UltraGauge MX for some years now--an older model with a display. Interestingly, it reads the Ford transmission temperature natively, without any need for custom programming. I wonder why they didn't build this capability into the Bluetooth version?

Side note: When I switched to towing a trailer with a 2017 Ford F-150 pickup, I was pleased to see that the transmission temperature was displayed on the dashboard's LCD screen... but only as an uncalibrated analog gauge. However, by using the FORScan utility I was able to tweak the truck's parameters to display the actual temperature above the analog gauge. In the attached screenshot, it's the righthand gauge. I had to buy a cheap Windows tablet to run FORScan, but the ninety bucks was worth it to me. (I also modified a few other user experience-type settings, such as annoyingly beeping the horn when I locked the truck.)

It's unclear from FORScan's website, which is of the "written by engineers for engineers" type, to what extent the software will work with Ford's E-series vans, but for those with a mind to experiment, it might be worth a try. In addition to a Windows computer, a Bluetooth OBDII dongle is required; I used the ScanTool OBDLink MX Bluetooth.

Getting back to the ScanGauge, I installed it on my pickup's dashboard in an unused spot (not many of those!) to the left of the steering wheel. Although I no long need it to read the transmission temperature, I figure I might want to read or reset trouble codes someday, so it's good to have it available.

As an Amazon Associate Lazy Daze Owners' Group earns from qualifying purchases.
Andy Baird
2021 Ford Ranger towing 2019 Airstream 19CB
Previously: 1985 LD Twin/King "Gertie"; 2003 LD Midbath "Skylark"
Re: Our Experience with UltraGauge Blue
Reply #2 –
Time for me to weigh in on this.  In 2016, I changed from a ScanGauge to an UltraGauge (several reasons, none essential).  Mine  had the self-display like Andy's and came with two pre-programmed Ford Trans temperature gauges.  Neither worked.  HOWEVER - I had downloaded and programmed a trans temp gauge for the ScanGauge years ago, and I still had those codes.  There were some differences, but lots of similarities, to the UltraGauge trans temp gauge coding, which was programmable. 

So, working with one of the trans temp gauges on the UltraGauge, I copied all the settings so I could return to them if needed.  I then substituted the ScanGauge settings, one at a time, for the settings that were different.  The third or fourth one I changed worked.

Beats me why the ones supplied did not work.  My recollection from 2 years ago is that I had to change one of the numbers in a string from a 0 to a 1.  At any rate, I am quite pleased with the UltraGauge, and my old ScanGauge is in my Subaru.

Ken F in OR
'08 MB
Re: Our Experience with UltraGauge Blue
Reply #3 –
Great post.   I bought the scangauge and added the TFT parameters.  If I recall there was some trial and error work to find a code that works (and one dropped 0 in the scale factor that provided 'interesting' results).   It appears that when reporting fuel used/remaining it calculates that from the fuel consumption data.   Mine is off somewhat when running the generator,  I can't depend that refueling will stop at the same exact level each time and so can only roughly guess at the generators hourly consumption under various circumstances.
YMMV
Joel
Joel & Terry Wiley
dog Zeke
2013  31 IB   Orwan   / 2011 CRV Tow'd LWEROVE
Re: Our Experience with UltraGauge Blue
Reply #4 –
Joel, the generator fuel usage does not pass through the Ford fuel pump, so neither the ScanGauge nor the UltraGauge will "know" that that fuel has been used.  An accurate determination of the fuel remaining is based on:
1) You entering the right tank capacity
2) You calibrating the mileage setting
3) You calibrating the fuel consumption
4) How much fuel is pumped out of the tank.
5) You telling the unit when you refill.

It is not using the fuel gauge for this.

Both my ScanGauge and my UltraGauge were extremely accurate once I had done these calibrations.  In my 60 gallon tank, if it said I had 20 gallons remaining, I would pump less than half a gallon off of 40 gallons - it was that close.

As long as the rig is refilled on approximately level pads, you can use that fill data to calculate generator fuel consumption, by comparing the predicted fill amount to the actual fill amount, and the hours of generator usage.  This will STILL be an approximation, as the generator fuel consumption will vary with amount of load on it, but it should be fairly close.

Ken F in OR
'08 MB
 
Re: Our Experience with UltraGauge Blue
Reply #5 –
Ken,
I am reasonably satisfied with the numbers the scangauge has given me over the last 4 years.
I average around 8mpg overall in all conditions.  This included 10-11 mpg between Bishop CA and San Bernardino south on US395 with a 2-reef tail wind and 6 on the way back in headwinds.   The only time it has been way off is when the pump stops early and I end up a gallon or two short of full.

A swag based on scangauge refills and mainly using the generator for the micro or A/C seems to be about 1/3 gal/hr on the generator.  Does that seem high or low to others?
Joel & Terry Wiley
dog Zeke
2013  31 IB   Orwan   / 2011 CRV Tow'd LWEROVE