KRISPYGAUGE Support & Setup

KrispyGauge is compatible with all Haltech Elite, Nexus, and Rebel series ECUs that broadcast over the Haltech CAN protocol, including:

• Haltech Elite series (Elite 550, 750, 1000, 1500, 2000, 2500)
• Haltech Nexus series (Nexus R3, R5, R3 Sport, S2, S3, Universal)
• Haltech Rebel series (Rebel LS, Rebel JZ)

Other Haltech models may work if they support the standard Haltech CAN broadcast — check your ECU documentation. Plenty of non-Haltech ECUs are supported too — see the next question, or the supported ECU reference for every signal we decode from each one.

Yes. KrispyGauge decodes Haltech, Link, MaxxECU, Holley, Megasquirt, AEM Infinity, Ecumaster EMU Black, Emtron, rusEFI, Syvecs, OBD2 and NMEA 2000 (marine). Select your ECU type in the Web UI settings before configuring anything else.

It also reads standalone modules that share the bus with your ECU and add channels it does not provide:

• Haltech WB1 / WB2 wideband controllers
• Haltech TCA-2 / TCA-4 / TCA-8 thermocouple amplifiers
• AEM 30-2224 eight-channel thermocouple module
• AEM 30-2226 CSM6 six-channel sensor module
• TurboLamik TCU for gearbox data

Every signal we decode from each one is listed in the supported ECU reference. Syvecs is listed as unverified — the decode is inferred rather than confirmed against a device, so check a known value before relying on it. If you have questions about a specific ECU, reach out at [email protected].

Work through the following checklist:

1. CAN wiring — confirm CAN H and CAN L are correctly connected and not reversed.
2. CAN broadcast — verify Haltech CAN Broadcast is enabled in Haltech NSP.
3. Termination — the CAN bus requires 120 Ω termination at both ends. Most Haltech ECUs terminate the bus themselves; KrispyGauge has a software-based 120 Ω termination you can enable in the Web UI settings if your network topology needs it.
4. ECU running — the Haltech ECU must be powered and in its run state to broadcast CAN data.

It's a good idea to back up your gauge configuration regularly — especially if you have extensive customisations, custom channels, warning thresholds, or keypad mappings set up.

• Backup — connect to the KrispyGauge hotspot, open http://4.3.2.1, and navigate to Advanced → Backup. Save the file to your phone or computer.
• Restore — go to Advanced → Restore and upload your saved backup file to return to that configuration.

Keep a copy of your backup somewhere safe — it can save a lot of time if you ever need to factory reset or recover from a failed firmware update.

This is entirely optional — the gauge works fine with its default WiFi name and default password. However, if you plan to leave WiFi on for extended periods, we recommend setting a unique password to prevent unattended access to your gauge configuration.

You can change the WiFi name (SSID) and password under Advanced → Wireless Access Point. Keep the password simple enough to type on a phone but not something obvious.

Our general recommendation is to turn WiFi off when it's not in use using the Auto-Enable WiFi setting — that way you don't need to worry about a password at all. But if you prefer to leave WiFi on, a basic password is a good idea.

Yes — once you've completed your initial setup, it's recommended to disable Auto-Enable WiFi in the gauge configuration (Web UI → Settings → WiFi).

Leaving the WiFi hotspot on permanently has two downsides:

• Performance — running the WiFi radio continuously draws extra processing overhead. Disabling it when not needed keeps the gauge running at its best.
• Security — an always-on hotspot means anyone within range could connect and alter your gauge settings, channel configurations, or warning thresholds without your knowledge.

With Auto-Enable WiFi off, you can still access the Web UI anytime by manually enabling WiFi from the gauge menu (Menu → WiFi → Enable). Turn it on when you need to make changes, then turn it back off when you're done.

A factory reset can be performed in two ways:

1. Via Web UI — connect to http://4.3.2.1, navigate to Advanced → Reset, and confirm.
2. On the gauge — from the main menu, hold the Info button for 3 seconds to open the Reset menu, then confirm the factory reset.

All custom channels, warning thresholds, and keypad configurations will be cleared and restored to defaults.

• Confirm you are connected to Krispy_XXXX — not your home, Haltech, or mobile network.
• On Android, disable mobile data so the OS doesn't route traffic over cellular when WiFi has no internet.
• Use http:// — not https://. The Web UI does not use HTTPS.
• Try a different browser. Chrome or Firefox are recommended.
• If the gauge recently suffered a failed firmware update, use USB Recovery to restore it.

No. KrispyGauge does not join external networks — it runs its own dedicated WiFi hotspot (Krispy_XXXX) solely for configuration. To access the Web UI you must connect your phone or laptop directly to the KrispyGauge hotspot, then open http://4.3.2.1.

Home WiFi, Haltech WiFi, and other existing networks cannot be used to reach the Web UI.

KrispyGauge presents itself to your Haltech ECU as a native CAN Keypad device over the CAN bus. Configure keypad button functions in Haltech NSP exactly as you would for a physical Haltech CAN Keypad — KrispyGauge responds identically.

Up to 8 keypad buttons with custom labels can be configured via Web UI → Keypad. Tapping a button on the gauge touchscreen sends the corresponding CAN keypad command to the ECU. No separate keypad hardware is required.

KrispyGauge is designed for interior cockpit installation in a standard 52mm gauge pod. It is not waterproof and is not rated for direct water exposure. Protect the unit from high-pressure washing, water ingress, or prolonged moisture. For motorsport applications in open cockpits, use a gauge pod with a protective visor or cover.

A Marine version is currently in development for exposed and high-moisture environments. If you have a special application or requirement, contact us — we may be able to provide an experimental unit for testing.

Every KrispyGauge is individually tested on a real running Haltech Nexus R3 before it leaves the factory — so if your gauge isn't receiving CAN data, the issue is almost certainly in the installation rather than the gauge itself. Work through these checks:

• CAN H / CAN L polarity — this is the most common cause. CAN H (Yellow) must connect to CAN H on the ECU, and CAN L (Green) must connect to CAN L. Swapping them will prevent communication entirely.
• Termination resistor — try switching the gauge's software 120Ω termination on or off in the Web UI settings, depending on your network topology and whether your ECU already terminates the bus. See the note in the Wiring section above.
• Haltech CAN broadcast — confirm it is enabled in Haltech NSP under ECU Settings → CAN Bus.
• Wiring continuity — check for broken, shorted, or incorrectly crimped wires between the gauge connector and the CAN bus tap point.

If you've worked through all of the above and still have issues, contact us at [email protected].

Yes — a barebones open source community firmware is coming soon. It's designed for savvy individuals and vibe coders who want to go deeper: make key changes to the codebase, adapt the gauge to a different platform or CAN protocol, build entirely custom gauge faces, or tailor the experience exactly to their needs.

Whether you want to add support for a new ECU, rework the UI, or build something entirely new on top of the KrispyGauge hardware — the community firmware will give you the foundation to do it.

Stay tuned — more details will be announced soon. In the meantime, reach out at [email protected] if you're keen to get involved early.

Absolutely — we love hearing from the community. Submit your idea using the Feature Request page. Just provide a title, a brief description, and your email and we'll review it.

Reach out at [email protected]. Include your order number and a detailed description of your issue for the fastest response.

There are also a number of additional troubleshooting steps and methods available — get in touch and we can walk you through them.