00 ·01 ·02 ·03 ·

Home/Documentation / Pulse / Getting Started

- Pulse · getting started

Pulse getting started.

Connect your phone directly to the vehicle CAN bus through a WiCAN or SLCAN adapter, without an in-car MCU.

PULSE · GETTING STARTED · REV SEP 22, 2026SCROLL ↓

PULSE STANDALONE · REV SEP 22, 2026◆WICAN USB FIRMWARE v5.0+◆VCU+ v2.0.19-BETA.6 ON CAN2/CAN3◆BLE → REALDASH 66 ONLY◆iOS: NO USB CAN PATH◆INFO@DYNAMLABS.COM◆PULSE STANDALONE · REV SEP 22, 2026◆WICAN USB FIRMWARE v5.0+◆VCU+ v2.0.19-BETA.6 ON CAN2/CAN3◆BLE → REALDASH 66 ONLY◆iOS: NO USB CAN PATH◆INFO@DYNAMLABS.COM◆

← BACK TO DOCUMENTATION·URL/documentation/pulse/getting-startedPULSE OVERVIEW DOCS LIBRARY →

/ 00

- Pulse · getting started

Pick a row in the connection matrix, then follow that path.

- REVISION

Sep 22, 2026

DOCUMENT DATE

- DONGLE FW

v5.0+

WICAN-FW USB BUILD

- VCU+ FW

v2.0.19-beta.6

BROADCAST ON CAN2/CAN3

- DONGLE UI

192.168.80.1

AP MODE

01What you need 02Connection matrix 03Prep the WiCAN USB dongle 04Install Pulse 05First launch: setup wizard 06Provision the BLE auth key 07Pick your dongle and verify 08Hardwired: USB SLCAN 09WiFi TCP 10Troubleshooting 11Support

/ 01

- What you need

Standalone mode needs nothing in the car beyond the VCU+ and the CAN adapter your phone talks to.

—A Dynam VCU+ running firmware v2.0.19-beta.6 or newer, broadcasting on CAN2 or CAN3, wired to your adapter

/ 02

- Connection matrix

Pick the hardware, then the matching Vehicle Link source in Pulse.

HARDWARE	PULSE SOURCE	ANDROID	IOS	NOTES
MeatPi WiCAN USB	WICAN (BLE) · RealDash 66	YES	YES	Recommended for mobile. In the dongle web UI, enable BLE and set `Protocol = RealDash 66`. BLE does not work with slcan. Dynam firmware v5.0+; BLE key (below).
MeatPi WiCAN USB	TCP · REALDASH 66 or TCP · SLCAN (WiFi)	YES	YES	Supported on Android and iOS, same dongle. Check `Protocol` in the dongle web UI (`slcan` or RealDash 66) and pick the matching Pulse source; set `Port type = TCP`. No BLE key. Your phone joins the dongle *`WiCAN_` Wi-Fi**, which usually has no internet. (setup)
CANable 2.0 / SLCAN USB	USB · SLCAN	YES	NO	Hardwired in-car (Android head unit or USB OTG). Wire CAN, plug USB, select the source. No dongle firmware or BLE key.

NOTE · IOS HAS NO USB CAN PATH

iOS does not support USB CAN adapters. Apple does not expose USB serial for third-party CAN hardware, so USB · SLCAN never appears on iPhone or iPad. On iOS, use WiCAN BLE or WiFi TCP (TCP · REALDASH 66 or TCP · SLCAN).

Each row has a section: dongle prep, install, BLE setup, WiFi TCP, and USB SLCAN.

/ 03

- Prep the MeatPi WiCAN USB dongle

Dongles ship without firmware. Flash the v5.0+ build before the app wizard can connect.

INFO · DO THIS BEFORE INSTALLING PULSE

Use this section for WiCAN BLE or WiFi TCP on the MeatPi WiCAN USB.

NOTE · FIRMWARE SOURCE

Dynam’s WiCAN USB firmware (v5.0) is a GPLv3 fork of Meatpi WiCAN. Source for this build: github.com/dynamlabs/wican-fw (tag v5.0).

NOTE · DEFAULT DONGLE WI-FI PASSWORD

Fresh MeatPi dongles broadcast WiCAN_* with factory Wi-Fi password @meatpi#. Join that network, then open http://192.168.80.1/ in a browser. Change the password in the web UI after setup (below).

Use this path if the dongle has no firmware (factory blank), or if there is no WiCAN_* Wi-Fi and http://192.168.80.1/ does not load.

Full pin diagram and tool screenshots: MeatPi — USB flash (WiCAN USB).

01
Download wican-fw_usb_v50.bin (v5.0) on your computer.
02
On the MeatPi WiCAN USB board, locate the boot / flash pins (see the USB diagram in the MeatPi link above).
03
Short those pins (jumper wire, tweezers, or test clip).
04
While the pins are shorted, plug the dongle into your computer with a USB data cable.
05
Open the Espressif Flash Download Tool (Windows) or esptool (macOS / Linux). Install a USB-serial driver if the port does not appear (the WiCAN USB uses a USB–serial bridge).
06
Select the correct serial port. Click ERASE first if you are recovering a failed flash or the device will not boot.
07
Load wican-fw_usb_v50.bin, flash, then disconnect USB, remove the short, and power the dongle normally.
08
Join the WiCAN_* access point (Wi-Fi password @meatpi#) and confirm http://192.168.80.1/ loads. Continue with Configure BLE and CAN below.

- / 03.3

Configure BLE and CAN

After firmware is flashed.

WARNING · BLE REQUIRES REALDASH 66

Pulse WICAN (BLE) only speaks RealDash 66 over GATT. In the dongle web UI, set Protocol = RealDash 66 before using BLE. slcan will not work for BLE. Use it for WiFi TCP or USB · SLCAN on other adapters.

01
On a phone or laptop (still on dongle Wi-Fi or LAN), open http://192.168.80.1/ if you are not already there.
02
In the web UI, enable BLE.
03
Set Protocol = RealDash 66 (not slcan).
04
Wire the CAN harness to the dongle and confirm the VCU+ (firmware v2.0.19-beta.6+) is broadcasting on CAN2 or CAN3.
05
Change the default Wi-Fi password (factory default @meatpi#) in the web UI after setup.

WARNING · SECURITY

Pulse authenticates over BLE with the HMAC key from /ble_key, not the BLE PIN field in the web UI. Ignore the PIN. Rotate the BLE key on http://192.168.80.1/ble_key when you need to (for example after sharing the dongle Wi-Fi), then re-provision in Pulse.

TIP

Your phone only needs the dongle Wi-Fi when fetching the BLE key in Pulse, unless you scan the QR in the app.

NOTE

Skip this entire prep section if you are using a CANable 2.0 USB adapter only.

/ 04

- Install Pulse

Pulse is distributed through internal testing on Apple and Google platforms. You need an invite from Dynam Labs before the app appears on your device.

- IOS · TESTFLIGHT

01
Accept the TestFlight email invite sent to your Apple ID.
02
On iPhone or iPad, install the TestFlight app from the App Store if you do not already have it.
03
Open the invite link and tap Install for Pulse.
04
Internal testers must already be on the Dynam Labs App Store Connect team. If you do not receive an invite, ask your Dynam Labs contact to add your Apple ID.

On iOS, WiCAN BLE and WiFi TCP (TCP · REALDASH 66 or TCP · SLCAN) work. See the connection matrix.

External TestFlight (wider audience) requires a short Apple beta review and is separate from internal testing.

- ANDROID · GOOGLE PLAY INTERNAL TESTING

01
Accept the email or Google Groups invite to the internal testing program. Use the same Google account on your phone as the one that received the invite.
02
Open the opt-in link from the invite email (or play.google.com/apps/internaltest/…). Tap Accept invitation / Become a tester on the web page. The app will not appear until you finish this step. After that, search by package ID (step 4), not by name alone.
03
Enable Play Store developer mode:
- —Open the Google Play Store app on your phone (same Google account).
- —Tap your profile icon → Settings.
- —Expand About and tap Play Store version seven times until you see "You are now a developer!"
- —Go back to Settings → expand General → Developer options.
- —Turn on Internal app sharing and confirm when prompted. Google’s label is "Internal app sharing", next to the internal testing setup. Many devices will not install a test build until it is on.
04
In the Play Store app, search for com.dynamlabs.pulse (the package ID). Searching for "Pulse" alone often does not surface internal test builds. Open the listing and tap Install or Update.
05
Alternatively, open the Play Store listing link from the invite, or go to Play Store → Account → Manage apps & devices → Testing and find Pulse under your testing apps.
06
If you see "App not available" or "Item not found", confirm you finished steps 2 and 3 with the correct Google account, then search again for com.dynamlabs.pulse. Try Force stop and Clear storage on the Play Store app, reopen the opt-in link, and repeat from step 3. Signing out and back into your Google account on the phone also helps.

Internal testing installs come from the Play Store. You do not need to sideload an APK unless Dynam Labs explicitly sends you one for a special build.

/ 05

- First launch: setup wizard

On first open, Pulse launches the setup wizard.

Welcome

Vehicle name

Theme and appearance

Units

Vehicle link: how to connect to the car

On the Vehicle link step, tap WICAN BLE SETUP → GUIDED to open the WiCAN-specific wizard (dongle prep checklist, BLE key, device pick, and link verify). That guided flow sets the source to WICAN (BLE) and protocol RealDash 66 automatically.

You can tap SKIP SETUP at any time to reach the cluster and finish later under Settings → Vehicle Link or Settings → SETUP → WICAN BLE → SETUP WIZARD.

/ 06

- Provision the BLE auth key

Pulse uses app-layer authentication (HMAC challenge over GATT) before CAN data flows. You need to copy the dongle’s BLE key into Pulse once per dongle. This happens in the guided WiCAN wizard on first launch, or later via Settings → Vehicle Link → BLE KEY → PROVISION.

METHOD	WHEN TO USE
Scan QR	Open `http://192.168.80.1/ble_key` on the dongle (any device on the dongle network), then scan the QR in Pulse. Your phone does not need to join the dongle Wi-Fi for this path.
Fetch from dongle	Join the `WiCAN_` Wi-Fi network (password `@meatpi#`* unless you changed it), then tap FETCH KEY FROM DONGLE in the wizard or Settings → Vehicle Link → BLE KEY → PROVISION. Pulse reads `http://192.168.80.1/ble_key.json`.
Manual entry	Paste 32 hex characters or a `wican://ble-key/…` URI from the dongle key page.

After fetching the key over Wi-Fi, disconnect every device from the dongle Wi-Fi before scanning for BLE in Pulse.

INFO

Keys are stored in secure storage on your device, keyed by the dongle’s WiC_* advertisement name.

/ 07

- Pick your dongle and verify

The dongle runs either its Wi-Fi access point or a BLE link, never both. Clear Wi-Fi before you scan.

- BLE AND WI-FI

WARNING · BLE AND WI-FI

01
Before scanning or connecting in Pulse, disconnect every device from the dongle’s WiCAN_* Wi-Fi, including your phone and laptop. While any client is on that Wi-Fi, the dongle often will not show up in the BLE scan.
02
After Pulse connects over BLE, the dongle turns off its Wi-Fi access point. http://192.168.80.1/ stays unreachable until you power-cycle the dongle and stay off BLE while you configure it.

- CONNECT IN PULSE

01
Disconnect all devices from the dongle Wi-Fi (see the warning above).
02
If iOS or Android shows a system Bluetooth pairing prompt, dismiss it. Pulse handles the GATT connection and authentication. Pairing through the OS will not work.
03
In the wizard or Settings → Vehicle Link → DEVICE, scan for devices named WiC_* and select yours.
04
Wait for the link status to show CONNECTED · ACTIVE. CAN frames are flowing.
05
Fine-tune reconnect behavior in Settings → Vehicle Link.

Pulse remembers your dongle by name and reconnects when you walk back into range or reopen the app. On iOS, peripheral UUIDs rotate between sessions. The WiC_* name is the stable identity.

While WICAN BLE is selected, Android shows a low-priority Pulse CAN bridge notification to keep BLE alive with the screen locked.

/ 08

- Hardwired setup: CANable 2.0 / USB SLCAN

Use a CANable 2.0 or any SLCAN-compatible USB adapter for a fixed, wired CAN link. Android only.

This path fits an in-car install where the host stays put: an Android head unit or a dash-mounted tablet with USB OTG, the adapter wired to the VCU harness, and Pulse full-screen. See the connection matrix.

TIP · SHIPS WITH SLCAN

Unlike the MeatPi WiCAN USB, there is no adapter firmware or web UI to configure. Adapters such as the CANable 2.0 ship with slcan firmware. Wire CAN, plug USB, then select USB · SLCAN in Pulse.

On a dedicated head unit, accept always allow for Pulse so the link comes up on boot.

01
Permanently wire the adapter to the VCU CAN bus. Bitrate is usually 500 kbps. Pulse prompts when you connect.
02
Plug the USB cable into the Android head unit or phone (USB OTG). Route and strain-relief the cable so it survives vibration and heat in the cabin.
03
In Pulse, open Settings → Vehicle Link → SOURCE and pick USB · SLCAN (on first launch you can also choose this from the setup wizard’s Vehicle link step).
04
Select the device from the list (canable, usbmodem, or similar). Grant USB permission when Android prompts. The USB serial line speed is 115200, which is separate from the CAN bitrate.

/ 09

- WiFi TCP

WiFi TCP works on Android and iOS without BLE key provisioning. The same MeatPi WiCAN USB dongle can use either protocol over Wi-Fi.

WARNING · INTERNET WHILE ON DONGLE WI-FI

While Pulse is connected over the dongle’s Wi-Fi, your phone is on a local network with no route to the internet. You lose cellular data offload, maps, and app updates. BLE keeps your phone on its normal Wi-Fi or mobile data while CAN flows in the background.

DONGLE WEB UI · PROTOCOL	PULSE SOURCE	NOTES
slcan + `Port type = TCP`	TCP · SLCAN	Common on a fresh dongle. Valid for WiFi TCP, not for BLE.
RealDash 66	TCP · REALDASH 66 or WICAN (BLE)	Required for BLE, and used for RealDash over Wi-Fi.

The Pulse source must match the dongle. If they disagree, you connect but see no CAN frames.

Use it for a bench check, or when BLE is unavailable.

01
Complete Prep the MeatPi WiCAN USB dongle above (firmware v5.0+, CAN wired, VCU+ broadcasting). Open the dongle web UI and note Protocol and Port type. For WiFi TCP, Port type must be TCP.
02
Join the dongle Wi-Fi (WiCAN_* in AP mode, password @meatpi# unless changed), or connect to the same LAN as the dongle in station mode.
03
In Pulse, open Settings → Vehicle Link → SOURCE and pick TCP · SLCAN or TCP · REALDASH 66 to match the dongle Protocol from step 1.
04
Set the endpoint to 192.168.80.1:3333 in AP mode (the port matches the dongle web UI). In station mode, use the IP from the dongle Status page. The port is often 3333, sometimes 23 or 35000, depending on firmware.
05
Confirm CONNECTED · ACTIVE.

When you are done, disconnect from dongle Wi-Fi to restore normal internet on your phone.

/ 10

- Troubleshooting

Start here when the link will not come up.

SYMPTOM	WHAT TO TRY
No USB · SLCAN on iPhone / iPad	iOS has no USB CAN support. Use WiCAN BLE or WiFi TCP (matrix).
No `WiC_*` devices in scan	Disconnect all devices from the dongle *`WiCAN_` Wi-Fi**, then scan again
Dongle Wi-Fi or web UI missing after BLE	Wi-Fi stays off while BLE is connected. Disconnect BLE in Pulse, then power-cycle the dongle.
BLE scan blocked	Provision the BLE key first
BLE auth failed	Rotate or re-copy the key on `http://192.168.80.1/ble_key`, then re-provision in Pulse (Settings → Vehicle Link → BLE KEY)
Connected but no CAN frames	Confirm Dynam Labs dongle firmware v5.0+, VCU+ firmware v2.0.19-beta.6+, and protocol matches your Pulse source: BLE → dongle `Protocol = RealDash 66`; WiFi TCP → TCP · REALDASH 66 or TCP · SLCAN to match the web UI; CAN wiring; VCU traffic on CAN2/CAN3
Could not fetch key from dongle	Join `WiCAN_` Wi-Fi (password `@meatpi#`*), open `http://192.168.80.1/ble_key` in a browser, then try fetch or manual entry
No `WiCAN_*` Wi-Fi / web UI dead	Factory-fresh unit. Short boot pins and USB-flash `wican-fw_usb_v50.bin` (see Factory-fresh dongle above) or follow MeatPi USB flash
Play Store says app not available	Finish opt-in + developer mode (step 3), then search Play Store for `com.dynamlabs.pulse`. Clear Play Store storage if it still fails.
TestFlight invite missing	Confirm your Apple ID is on the Dynam Labs App Store Connect team

/ 11

- Support

For general technical support, contact your point-of-sale.

- / DOCUMENTATION

dynamlabs.com/documentation

Manuals for VCU+ and Pulse.

- / CONTACT

Talk to us

Questions, invites, and setup help.

- / EMAIL

info@dynamlabs.com

Written support and RMA requests.

Pulse getting started.

Release notes.