EMU-1 Custom Gauge Tool

EMU-1 Custom Gauge Tool

We're pleased to announce that the new beta version of the Toolkit supporting the custom gauge tool is now available.  
This is beta firmware.  Only download this version of Toolkit if you are happy to be part of the EMU-1 and Toolkit beta testing programme.  Features in this version of Toolkit may not work with other Actisense devices.


You will also need the latest beta NGT-1 firmware to use this Toolkit, which can be downloaded here:

To use the custom gauge tool, please follow these steps:

  1. Upgrade the EMU-1 firmware to v.1.015 by selecting it in the CAN Device List and clicking 'Upgrade Firmware' on the ribbon menu.
  2. Open the custom gauge tool from the ribbon menu along the top row of Toolkit
  3. Select 'Create New'
  4. Name your gauge
  5. Select the required parameter (for example; engine temperature or engine oil pressure)
  6. Select the required unit of measurement (for example; degrees C or F)
  7. Operate your gauge from minimum to maximum, measuring the voltage on the back of the gauge at regular intervals and enter this value in the 'Input' column. 
  8. Plot the observed measurement against the value shown on the from of the gauge.  The more points that are measured, the more accurate the results will be.
  9. Click Save
  10. Close the custom gauge manager.

You will find your new gauge at the bottom of the drop down menu under the 'Gauge' column. (Where the existing VDO and Faria gauges are located).

UPDATE (28/08/18): 
A bug has been discovered by our engineers that prevents the user from entering a new negative value in the 'output' column.  This is most affected when entering values for degrees C (as it's the most likely to see a negative value).

As a workaround for this, simply change the 'deg C' drop down option to 'deg K'.  Enter 270 in the 'output' column anywhere you need a negative value.  Change the drop down option back to 'deg C'.  You will now see an editable negative value.

The bug simply prevents the negative value being entered as a new value.  This will of course be fixed for the full release and highlights the importance of beta testing.