701display

Husky 701 Display – Owner’s Manual

Secondary display and virtual fuel computer for the Husqvarna 701 Enduro (Euro 5). It reads the motorcycle’s CAN bus through the OBD port and shows fuel, range, economy, gear, RPM, coolant temperature, ABS mode and side-stand state.

Safety: This is an experimental secondary display. It does not replace the factory dash or fuel warning light. Never operate or adjust it while riding. See the disclaimer in README.md and below.

Contents

  1. System overview
  2. What you need
  3. Wiring
  4. Installing the firmware
  5. Installing the Android app
  6. First-time setup
  7. Display screen reference
  8. Functions and settings
  9. Android app settings
  10. Versions and compatibility
  11. SD card logging (display build)
  12. Troubleshooting
  13. Disclaimer of Warranty and Limitation of Liability

1. System overview

There are two hardware options. Both run the same CAN/fuel logic and both broadcast live data over Bluetooth Low Energy (BLE) at about 20 Hz.

  Display build Headless build
Hardware Waveshare ESP32-S3-Touch-LCD-4.3B (800×480 touchscreen) Waveshare ESP32-S3-RS485-CAN (no screen)
PlatformIO env waveshare_esp32s3_43b waveshare_esp32s3_rs485_can
Shows data on Its own touchscreen and the Android app The Android app only
Touch settings Yes (fuel reset, off-road ABS, clock) No (use the app)
Real-time clock, SD logging Yes No

The Android app (a phone or motorcycle tablet) shows the same dashboard as the 4.3” screen and can change the same settings.

2. What you need

Parts list

Display version (for development)

Item Link
Waveshare ESP32-S3 4.3 Display https://www.amazon.com/dp/B0DD6VLH1Y
Sumitomo HM 090 OBD Connector set https://www.amazon.com/dp/B0FCLJP2ZY
Shielded, double twisted pair wiring https://www.amazon.com/dp/B0FHPGN8M7
CR927 battery https://www.amazon.com/dp/B0DDSW4SF7

Headless version (end user)

Item Link
Waveshare ESP32-S3 CAN control board https://www.amazon.com/waveshare-Industrial-Interfaces-Connecting-Protection/dp/B0FNCWZ3D1
Sumitomo HM 090 OBD Connector set https://www.amazon.com/dp/B0FCLJP2ZY
Shielded, double twisted pair wiring https://www.amazon.com/dp/B0FHPGN8M7

Back to Table of Contents

3. Wiring

Connect the ESP32 hardware to the OBD port:

  1. Power: switched 12 V (key-on) and ground, through the board’s supply input.
  2. CAN High / CAN Low: to the CAN pins of the OBD connector.

The 4 wires you need are the same 4 wires at the OBD port. The CAN bus runs at 500 kbps. Do not power the board from an always-on feed unless you accept the board staying on when the key is off. The CAN wires must be a twisted pair. I used shielded wire with 2 sets of twisted pairs for the wiring. Ground the shield at one end.

The OBD connector pinout and wiring diagram is shown below. This is for the headless version showing a simple harness (not the T harness).

image

You can make a T harness that leaves an OBD plug available for a scan tool or other devices to use. Optionally, you can simply connect the ESP32 as shown in the wiring diagram above.

The connector is a Sumitomo HM 090. You can find kits on Amazon or many other retailers.

Connecting third-party devices to the diagnostic bus carries risk. Double-check polarity and pin assignments before powering up. Use a voltmeter to confirm power and ground is around 12VDC (positive). A high-impedance (digital) voltmeter can also be used to confirm CAN hi and low by connecting the voltmeter leads to the 2 CAN wires. It should read about 2.5VDC positive. If it shows negative then the positive lead is on the CAN low wire.

Back to Table of Contents

4. Installing the firmware

Option A – Web installer (no tools)

  1. Connect the ESP32 to your computer by USB.
  2. Open https://jroal.github.io/701display/installer.html in Chrome or Edge.
  3. Follow the prompts to select the serial port and flash.

Option B – PlatformIO

  1. Install VS Code and the PlatformIO extension, then open the project folder.
  2. Select the environment for your board and upload:

    Board Command
    Display (4.3B) pio run -e waveshare_esp32s3_43b -t upload
    Headless pio run -e waveshare_esp32s3_rs485_can -t upload

    In VS Code you can also use Terminal → Run Task → Build/Upload Headless Hardware.

  3. Do not use the waveshare_esp32s3_43b_capture environment for normal use. It is a diagnostic build that records every CAN frame.

Back to Table of Contents

5. Installing the Android app

On first launch, allow the Bluetooth (“Nearby devices”) permission when asked. If you enable the fuel-range overlay, you will also be asked for the “display over other apps” permission.

Back to Table of Contents

6. First-time setup

  1. Wire and flash the ESP32 (sections 3 and 4).
  2. Key the bike ON. The ESP32 powers up and starts reading the CAN bus. The CAN indicator turns green when valid bike data is arriving.
  3. Set the clock (display build): tap the date/time and set it (section 8.3). This is used for log file names and timestamps.
  4. Fill the tank, then press Reset (section 8.1). The fuel gauge is an estimate, so it must be calibrated at every fill-up.
  5. Pair the app: open the Android app. It scans for a display named Husky701-XXXXXX. If more than one is nearby, open Settings (gear icon) and pick yours under “701 display to connect to”. You should always select your specific ESP32 to connect to otherwise you risk connecting to another nearby ESP32. Start by letting it connect to any while your bike is the only one with the ESP32 on it in the area (within 200 feet or so). Then find which one it connected to and select that in the list. Once selected it will always look for only that ESP32.
  6. Confirm the app’s top-left status reads BLE: connected.

Back to Table of Contents

7. Display screen reference

The 4.3” display and the Android app show the same layout.

Element Location Meaning
Fuel bar and E 1/4 1/2 3/4 F scale Top left Estimated fuel remaining as a percent of the 13 L usable capacity. The percent is shown inside the bar.
FUEL: x.xx gal Top right Estimated fuel remaining in US gallons.
Reset button Top centre Tap after filling the tank (section 8.1).
Date / time Top right, under FUEL Real-time clock (display build). Tap to set.
TEMP: xx F Left, middle Engine coolant temperature in °F.
GEAR: n Right, middle Current gear (N = neutral).
RPM bar and xxxx RPM Centre Engine speed. Bar colour: green below 8000, yellow 8000–9000, red above 9000. Scale ends at 10,000.
ECON: x.x Lower left Fuel economy in MPG.
RANGE: xx mi Lower right Estimated remaining range (fuel left × economy). Shows -- until economy is known.
STAND: UP / DOWN / – Bottom left (upper line) Side stand. DOWN is red, UP is green, -- means unknown.
ABS: ON / OFF-Road Bottom left ABS mode reported by the bike. See the note below.
Off-road ABS switch Bottom centre Requests off-road ABS mode (section 8.2).
CAN Bottom right Green = receiving bike CAN data. Yellow = no data. On the display build, tap it to see versions.
BLE status (app only) Top left of the app Search/connection state of the Bluetooth link.

ABS note: The display shows only ABS: ON or ABS: OFF-Road. When the rider switches ABS completely off with the button, the bike does not broadcast that state in a way the display can read, so it will still show ON (or OFF-Road). Always refer to the bike’s factory ABS indicator to ensure ABS state.

The Android app allows for selecting English or metric units.

Back to Table of Contents

8. Functions and settings

8.1 Fuel gauge, economy and range

The bike has no direct fuel-level signal on CAN, so the display estimates it:

The distance estimate has several factors leading to uncertainty and error. This makes the MPG and range estimates also have error. I have found these estimates tend to be to the lower side (less MPG and range than actual). This is better than error the other way.

Refuel the motorcycle and press Reset every time you refuel; otherwise the gauge will be inaccurate. Always fill the tank all the way full before clicking reset. On the Android app, the Reset button works the same way as long as it has an active BLE connection (BLE connected and green at the top, it is disabled while not connected).

Starting with version 6 (1.2.0) of the Android app (and associated ESP32 firmware and BLE protocol) the user can add fuel to the remaining fuel. This is done by clicking the remaining fuel label (top right). An add fuel dialog appears where the user can select the amount to add to the tank. Once selected, click the add button. This is useful when you carry additional fuel that you add to the tank on the ride. It is best to run the fuel down more than the fuel can capacity you will add. For instance, if you have a 1 gallon gas can make sure there is more than 1 gallon of open volume in the tank (meaning the remaining fuel is less than 2.4 gallons) before adding the fuel.

8.2 Off-road ABS

Toggle Off-road ABS to have the bike start in off-road ABS mode at the next key-on.

  1. Turn the “Off-road ABS” switch ON. A message tells you the mode takes effect on the next key cycle.
  2. Turn the ignition OFF, wait a few seconds, then key back ON.
  3. The ABS indicator at the bottom left of the display should show ABS: OFF-Road.
  4. To return to normal ABS, turn the “Off-road ABS” switch OFF and key-cycle again. When you key back ON the ABS indicator should now show ON.

The ABS module looks for this off-road mode request for a few seconds at startup. If it does not see the off-road mode request within a few seconds, the ABS will work normally (on-road mode) until key OFF. If the ABS does see the off-road mode request, it will switch to off-road mode and stay there until the next key cycle.

How it works and safety rules:

ABS mode switching demo: https://youtu.be/ZTQ_GDK-LSc

8.3 Setting the date and time (ESP32 with display only)

Tap the date/time on the display. A Set date & time panel appears with +/− steppers for year, month, day, hour and minute. Tap Set to save to the real-time clock, or Cancel. An “Invalid date or time” message appears if the values are not a real date. The clock requires a coin cell backup battery installed on the board: it is needed to keep the ESP32 clock running while power is off, and the data logs depend on that clock for their timestamps and file names. Without the battery the clock must be set again after each power loss.

The Android app does not show the clock.

8.4 About / version information (ESP32 with display only)

Tap the CAN label (bottom right). The About dialog shows the firmware version and build, and the BLE protocol version. Tap the close button to dismiss.

Back to Table of Contents

9. Android app settings

Tap the gear icon at the top right to open Settings:

Setting Description
Keep display ON while using Keeps the phone/tablet screen awake while the app is open.
Show fuel range over other apps Shows a small floating fuel-range window while the app is in the background (for example while using navigation). Android will ask for the “display over other apps” permission the first time.
Units Sets English or Metric units.
About Opens a dialog listing the app version, the BLE protocol range the app supports, and, when connected, the display’s firmware version, build (43b or headless) and BLE protocol version.
701 display to connect to Choose Any (first one found) or a specific display (Husky701-XXXXXX, with address and signal strength). The choice is remembered. A saved display that is out of range is shown as “Not in range”.

Use this app as the only display for the headless build, and as the place to read its versions.

Video demonstration of Android app settings: https://youtu.be/zHuzSz7Xirc

Back to Table of Contents

10. Versions and compatibility

Three versions are tracked so the parts work together:

The Android app accepts protocol versions 1 to 2. If the ESP32 firmware reports a protocol version the app does not support, update the app (or the firmware) so the versions are compatible. If you have issues you can check the About dialogs after updating either side.

Back to Table of Contents

11. SD card logging (ESP32 with display only)

If you are using the ESP32 with the display you can also capture data and error logs to a microSD card:

This feature is primarily used for development and troubleshooting. The headless ESP32 has no SD card slot or data logging capability.

Back to Table of Contents

12. Troubleshooting

Symptom Check
CAN stays yellow Key is ON? CAN High/Low wired correctly and not swapped? ABS ECU working? Power and ground solid? Kill switch ON?
App says searching, never connects Bluetooth on? Nearby-devices permission granted? ESP32 powered (key ON and kill switch in run)? Close other apps connected to the display (only one BLE client at a time). Is the ESP32 device powered (LED ON)?
Wrong display chosen Settings → “701 display to connect to” → pick the right Husky701-XXXXXX.
Fuel gauge wrong Press Reset only at a full tank. Re-fill and reset to recalibrate.
Off-road ABS does not engage Turn the switch on, then key off, wait a few seconds, and then key back on. The bike must be stopped. If an ABS dongle or Veridian Cruise with ABS add-on is already sending the request, the display deliberately does not send; enable it through the other device instead.
ABS shows ON after switching ABS off with the button Expected, see the ABS note in section 7.
No SD logs Card inserted before power-up? Reboot with the card in. Clock set?
Time is wrong Tap the date/time on the display and set it.
Version mismatch Compare the app and display About dialogs. Update whichever is older.

For more detail, see the README, the BLE protocol and the changelog. Github repo is here: https://github.com/jroal/701display.

Back to Table of Contents

13. Disclaimer of Warranty and Limitation of Liability

IMPORTANT: READ BEFORE USING THIS HARDWARE, FIRMWARE, OR APPLICATION.

  1. Provided “As-Is” Without Warranty

    The Husky Display project—including all hardware schematics, firmware binaries, source code, Android applications, and documentation—is provided strictly on an “AS IS” and “AS AVAILABLE” basis, without warranties or conditions of any kind, either express or implied. This includes, but is not limited to, implied warranties of merchantability, fitness for a particular purpose, accuracy, or non-infringement.

  2. Informational Use Only & Primary Instrumentation

    • Not an OEM Replacement: This system is designed solely as an experimental, secondary telemetry aid and virtual fuel computer. It does NOT replace your motorcycle’s original factory instrumentation, speedometer, low-fuel warning light, or primary diagnostic displays.

    • Telemetry Accuracy: All calculated metrics—including but not limited to vehicle speed, engine RPM, remaining fuel volume, fuel consumption rates, estimated range, and gear selection—are approximations derived from empirical data and CAN bus telemetry. Do not rely on this product for critical navigation, speed limit compliance, or fuel management. Always monitor your motorcycle’s factory dash and physical fuel level.

  3. Rider Responsibility & Traffic Safety

    • Safe Operation: The operator of the motorcycle assumes sole responsibility for safe riding, attention to road conditions, and adherence to all local traffic laws.

    • Distraction Hazard: Interacting with, configuring, or looking at display screens, phones, or handlebar mounts while riding can cause severe distraction, accidents, bodily injury, or death. Never adjust settings or attempt to operate the application while the motorcycle is in motion.

  4. Vehicle Electrical & Engine Interfacing

    • User Assumption of Risk: Connecting third-party devices or custom T-harnesses to your motorcycle’s diagnostic (OBD2/Euro 5) CAN bus carries inherent risks, including potential electrical short circuits, battery drain, ECU communication faults, or voiding of vehicle manufacturer warranties.

    • No Liability for Vehicle Damage: The developers, contributors, and copyright holders of this project shall not be held liable for any damage to your motorcycle, electronic control units (ECU), electrical harness, or connected peripherals resulting from the installation or use of this hardware or software.

  5. Limitation of Liability

    To the maximum extent permitted by applicable law, in no event shall the authors, developers, or project contributors be liable for any direct, indirect, incidental, special, exemplary, punitive, or consequential damages (including, but not limited to, loss of use, personal injury, wrongful death, property damage, vehicle repair costs, or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this product, even if advised of the possibility of such damage.

Back to Table of Contents