Advanced Settings
The Advanced tab contains low-level hardware configurations for the WiCAN Pro. Most users will not need to change these settings from their defaults, but they are available for specific tuning and debugging purposes.
Configuration Options
| Setting | Description |
|---|---|
| Motion Threshold | Controls the sensitivity of the WiCAN Pro's internal IMU (Inertial Measurement Unit). This slider ranges from 1 to 32, which the device calculates into milli-g (mg) of acceleration (e.g., a setting of 8 equals 31.2 mg). This determines how much physical movement or vibration is required to trigger motion-based wakeups or alerts. |
| ELM327 UDP Log | An advanced debugging tool that broadcasts raw ELM327 traffic over UDP. |
!WARNINGELM327 UDP Log Enabled
UDP logging requires significant processing power and can impact the overall performance of the WiCAN Pro. You should leave this Disabled unless you are actively debugging OBD2 communication issues.
Motion Settings
The WiCAN Pro has a built-in motion sensor (an ICM-42670 accelerometer). Its job is simple: notice when the car physically moves — driving off, being towed, a firm bump — and report that to the Poll on Motion Detection setting on the Automate tab, which can then resume polling even when the voltage is low.
The sensor watches for motion on its own, in hardware, without keeping the WiCAN's main processor busy — so it costs almost nothing in power. When it detects motion, the WiCAN counts as "moving" and stays that way until about 3 seconds pass with no further motion.
The base settings are likely universally usable, but further testing needed. These settings exist for fine-tuning if motion detection triggers too easily (e.g. from vibration) or not easily enough for your car and mounting position.
| Setting | What it does |
|---|---|
| Motion Threshold | How hard a movement has to be to count as motion, shown in mg (thousandths of the force of gravity). Slide it lower and small nudges or vibration will trigger it; slide it higher and only bigger, more deliberate movement will. The default (~31 mg) is a gentle-but-real movement. |
| WOM Sources | Which directions of movement are watched: X, Y, and Z (sideways, forward/back, up/down — depending on how the WiCAN sits in your OBD port). All three on (the default) catches the most movement, but also gives vibration more chances to cause a false trigger. |
| Accelerometer ODR | How often the sensor takes a measurement, from about 1.5 times per second (default) up to 1600 times per second. Slower saves a little power but reacts to motion more slowly; faster reacts quicker. |
| Accelerometer Averaging | How many measurements get averaged together before being checked against the threshold. More averaging (default 32x) smooths out vibration and noise — fewer false triggers — at the cost of reacting slightly slower to real motion. |
| WOM Interrupt Duration | How many measurements in a row have to be over the threshold before motion counts (default: fourth in a row). Higher filters out brief one-off jolts; lower reacts faster but false-triggers more easily. |
| WOM Combination | With several directions enabled: Any enabled axis (default) means movement in just one direction is enough. All enabled axes means every enabled direction has to see movement at the same time — much stricter, much less prone to false triggers. |
| WOM Reference | What each new measurement is compared to. Previous sample (default) compares against the measurement just before it — so it reacts to change, and works no matter how the WiCAN is oriented in your car. Initial sample compares everything against one fixed reading taken at startup instead. You will almost ALWAYS want to use Previous sample otherwise if you part at a slightly differnt incline from when the wican was plugged in you will continue to trigger "motion". |
| Read IMU State | A test button: shows the sensor's live readings and how many times each direction has triggered. Handy for checking the sensor responds at all, and for seeing whether your threshold is set about right — press it, wiggle the car door or lean on the car, press again, and see if the counters went up. |
!NOTEThis section only tunes detection. Motion detection does not wake the WiCAN from sleep and does not put it to sleep — it is currently only used for Poll on Motion Detection in the Automate tab.