VisiCan Data Displays — Master Knowledgebase

1. General Product Info, Compatibility & Hardware Specs

Q: What are the general specs, enclosure materials, and surface finishes of VisiCan Data Displays?

Enclosure Material: VisiCan display enclosures are manufactured using high-temperature, vibration-resistant ABS plastic designed for automotive interior environments.
Surface Finish: Outer and front surfaces feature a matte black acrylic finish to minimize windshield reflection. Pre-paint manufacturing marks may be visible on hidden interior/rear casing areas.
Exceptions: Standard Golf Mk8 / 8R models feature a High-Gloss (Piano Black) front trim bezel matching OEM interior dashboard trim, while the rear/interior casing uses a matte black finish.

Q: Does VisiCan work on modified or tuned vehicles, and is external sensor installation required?

Tuned & Stock Support: Yes. VisiCan Displays support both stock vehicles and Stage 2+ modified or track-prepared cars.
No External Sensors Required: VisiCan queries live engine data directly from factory sensors over OBD2/CAN-Bus (e.g., ECU, TCU). External sensors are not required unless monitoring non-OBD auxiliary signals (such as ethanol content or custom analog pressure sensors).

Q: Are VentMount displays shipped as complete air vent assemblies, and do they require cutting or modifying factory vents?

Housing Design: VisiCan VentMounts are provided as ABS plastic housing units designed to replace internal vent louver fins. Complete factory vent assemblies are not included.
Reversibility: Installation requires no cutting, drilling, or permanent modification (except on specific platforms like Seat Ibiza if internal pass-through holes are required for cable clearance). The installation is fully reversible to OEM vent condition.

Q: How long does installation take, and are power tools required?

Installation Duration: The vast majority of our customers complete self-installation independently within 30–45 minutes.
Tools Needed: No drills, soldering irons, or power tools are required; basic hand skills and standard plastic trim removal tools are sufficient.

Q: Are VentMount housing options available for all vehicle models (e.g., Audi A4 B6, Peugeot 207 RC, Citroën DS3, BMW Z4)?

Platform Availability: Dedicated VentMount housings are not manufactured for Audi A4 B6, Peugeot 207 RC, Citroën DS3, or BMW E89 Z4 platforms.
Alternative Universal Options: Universal DIY standalone models (e.g., D72 round housing, 72x38 compact casing, or 82x56 universal casing running matching Peugeot/Citroën ECU firmware) are available for dashboard, air vent cavity, or steering column mounting.
Custom Tooling Policy: New VentMount models require a minimum of 10 pre-orders/committed requests before production tooling, ECU communication firmware, and housing development begin.

Q: Can 1st–3rd Generation or DashMount (Console Type) displays be converted into VentMount configurations by swapping outer housings?

Hardware Incompatibility: No. DashMount and VentMount units (as well as 1st–3rd Generation vs. 4th/5th Generation displays) use completely different internal printed circuit boards (PCBs), processor architectures, and button layouts. Casing swaps alone cannot convert DashMount or older-generation units into VentMount models.
4th Generation DashMount Exception: 2024 production 4th Gen DashMount units can be converted to VentMount configurations by sending the functional display to VisiCan for complete housing and internal re-assembly under standard after-sales pricing.

2. Communication Protocols, Refresh Rates & Vehicle-Specific Behavior

Q: How fast is the VisiCan data refresh rate across different vehicle protocols and platforms?

Internal Refresh Rate: Screen updates refresh in less than 1 ms. To maintain CAN-Bus stability, VisiCan applies a safety delay of 8–15 ms between consecutive ECU queries.
Pre-2012 VAG (KWP Protocol): Queries measuring blocks (4 values per block) returned within ~35 ms.
2012+ VAG (UDS Protocol): ECU responses are nearly instantaneous; the 8–15 ms safety delay yields effective query speeds of 8–15 ms per request.
PSA, Hyundai, Honda, Renault: Response times range from 35 ms to 180 ms depending on ECU data block sizes.
BMW / MINI (OBD2 Gateway vs. PT-CAN Direct): OBD2 queries via the gateway (ZGW) respond in ~35 ms (~30 queries/sec). Direct PT-CAN bus hardwiring bypasses the gateway bottleneck, achieving instant responses subject to the 8–15 ms safety delay (exceeding standard OBD loggers like MHD).

Q: Does VisiCan work on vehicles without standard OBD ports or cars running Standalone ECUs?

Standalone ECU Support: On builds without standard OBD diagnostic ports that utilize Standalone ECUs (e.g., ECUMaster EMU Black), live parameters can be monitored instantaneously if the ECU provides CAN-Bus output and matching VisiCan firmware is flashed.
K-Line Exception: Apart from CAN-Bus communication, a dedicated K-Line communication firmware solution is available exclusively for legacy VAG 1.8T ME7.5 engine control units.

Q: How do protocol handoffs affect display performance when navigating between specific feature pages on VAG platforms (e.g., VAG KWP Platforms)?

Protocol Switching Handoff: Accessing specialized feature pages (e.g., switching between ECU engine data and DQ250/DQ500 DSG transmission data, opening DTC listings, or exiting OFF mode) forces the display to terminate one diagnostic session and initialize another with a different control unit.
Momentary Delays: During protocol switching, live data experiences a brief pause (up to 10–20 seconds on pre-2012 KWP builds; brief momentary pauses on UDS builds). Repeatedly pressing buttons during this handoff resets connection timers and prolongs the delay.

Q: What protocol requirements and wiring retrofits exist for BMW E-Series models (pre-2008)?

CAN-Bus Verification: Pre-2008 BMW E-Series vehicles (e.g., E60, E90, E92) use K-Line diagnostics on OBD Pins 7/9 and lack CAN-Bus lines at Pins 6 and 14. VisiCan displays require CAN-Bus communication and will not operate on K-Line alone (CAN lines became standard at the OBD port starting late 2007/2008).
PT-CAN Retrofit: Full functionality can be achieved by tapping into the vehicle's Powertrain CAN-Bus (PT-CAN at the ECU/ABS module or main harness) and hardwiring CAN High and Low to OBD Pins 6 and 14 along with a switched +12V feed (Pin 1), provided the DME supports CAN-Bus diagnostics.

Q: How does high-speed PT-CAN bus hardwiring work on BMW F-Series (F20/F30) models, and how do simultaneous scanner tools co-exist?

PT-CAN Wiring Pinout (FEM Module):
- Blue Wire (CAN High): A173-9B Pin 19 (Blue/Red wire).
- Green Wire (CAN Low): A173-9B Pin 18 (Red wire).
- Red Wire (+12V Switched): A173-8B Pin 20 (Grey/Green wire).
- Black Wire (Ground): A173-8B Pin 24 (Brown wire).
Simultaneous Diagnostic Sessions: Vehicle ECUs support only one active diagnostic session at a time. When hardwired to PT-CAN, external diagnostic tools (e.g., ISTA, MHD) plugged into the OBD port will collide with VisiCan unless VisiCan is placed into hardware Programming Mode (button combination) or OFF Mode during the diagnostic session.

Q: How does high-speed PT-CAN bus hardwiring work on BMW G-Series (G20/G22) models, and how do simultaneous scanner tools co-exist?

PT-CAN Wiring Pinout (BDC Module):
- Blue Wire (CAN High): A258-8B Pin 48 (Yellow/White wire).
- Green Wire (CAN Low): A258-8B Pin 47 (Yellow/Black wire).
- Red Wire (+12V Switched): Switched +12V fuse output in BDC fuse box.
- Black Wire (Ground): Chassis ground (Brown wire bolted to chassis).
Simultaneous Diagnostic Sessions: Vehicle ECUs support only one active diagnostic session at a time. When hardwired to PT-CAN, external diagnostic tools (e.g., ISTA, MHD) plugged into the OBD port will collide with VisiCan unless VisiCan is placed into hardware Programming Mode (button combination) or OFF Mode during the diagnostic session.

Q: How do engine swaps affect VisiCan firmware compatibility (e.g., Golf Mk7 1.2 TSI to 1.4 TSI swap)?

Same-Family VAG Engine Swaps: Swapping engines within compatible 4-cylinder VAG TSI platforms while retaining the factory ECU (e.g., 1.2 TSI to 1.4 TSI) requires no firmware changes; existing VisiCan firmware remains fully compatible.
Different ECU/Protocol: Replacing the factory ECU with a different ECU type or protocol requires purchasing and flashing a matching ECU communication firmware license.

Q: Why do VisiCan coolant or oil temperature readings differ from factory instrument cluster gauges?

Cluster Gauge Buffering: Factory dashboard gauges use heavily buffered algorithms (holding a fixed center reading, e.g., 90°C, across an actual operating window of 75°C–105°C) to prevent driver alarm.
Real-Time Data: VisiCan reads and displays the exact, unbuffered engine coolant and oil temperature directly from the ECU via OBD2/CAN-Bus. Live values match factory diagnostic tools (e.g., ODIS, VCDS, ISTA).

Q: Why does AFR remain at maximum or MAP/Boost values appear static (e.g., Peugeot/Citroën 1.6 THP engines)?

Wideband O2 / AFR Capping: If the upstream wideband O2 sensor is degraded, disconnected, or operating in Open Loop, the THP ECU outputs an out-of-range raw value (e.g., 65.35 / 65.535). VisiCan caps displayable AFR at 21.5. This indicates a vehicle sensor/tune fault, not a gauge defect.
Static MAP / Boost: Certain custom ECU tunes isolate manifold pressure PID streams over OBD2. If diagnostic tools confirm the sensor is operational, VisiCan engineering can update firmware to query secondary MAP memory block addresses.

3. Wiring, Pinouts, Power Protection & Hardware Troubleshooting

Q: What do the wiring connections and pins on the VisiCan OBD harness correspond to?

Pin 1: Switched Ignition Power (+12V) — Connects to Red wire. Unused on BMW F and G Series models; wire end remains insulated and disconnected inside harness.
Pin 5: Signal Ground — Connects to Black wire.
Pin 6: CAN-Bus High — Connects to Blue wire.
Pin 14: CAN-Bus Low — Connects to Green wire.
Pin 16: Permanent Constant Battery Power (+12V) — Unused on VAG models; lead remains un-terminated and insulated inside the harness splice.
Auxiliary Leads: White, purple, and orange leads should remain insulated and disconnected unless using specific add-on modules. Yellow wire on the splice section is reserved for Flex Fuel signal input.

Q: What causes vehicle startup lockouts, protection modes, or CAN-Bus fault codes on VAG models following display installation?

Exposed Constant Battery Lead (+12V Pin 16): On VAG harnesses, OBD Pin 1 supplies switched power while the red lead from Pin 16 is un-terminated and insulated inside the cable. If this wire becomes un-insulated during cable routing or footwell contact, short-circuiting against chassis metal or ground leads will cause the vehicle's CAN Gateway to enter protection mode, log multiple DTCs, or lock out starting.
Troubleshooting:
1. Inspect lever-lock and mid-harness splice connectors for exposed red wiring.
2. Disconnect the mainboard display unit from the mid-harness connector, leaving only the OBD plug attached, to verify if vehicle power normalizes.
3. Insulate unused leads with heat-shrink tubing and clear stored vehicle codes.

Q: Why does a portable OBD diagnostic scanner (e.g., OBDeleven) power on when plugged into a vehicle port while the VisiCan display fails to boot?

Power Pin Differences: Portable diagnostic tools draw permanent constant power directly from OBD Pin 16. VisiCan displays draw switched ignition power from OBD Pin 1 (or via inline lever-lock leads) to automatically power down when ignition turns off and prevent battery drain.
Troubleshooting: If scanners power on but VisiCan does not, verify the vehicle's Pin 1 switched ignition fuse in the fuse box or check that inline white lever-lock terminal leads on the VisiCan harness are firmly seated.

Q: What should be checked if a newly installed VisiCan display fails to power on?

No Power Check Steps:
- Lever-Lock Terminal: Inspect the white inline lever-lock connector (5–10 cm behind the OBD plug) and verify both red power wires are securely clamped.
- Mid-Harness Connectors: Ensure 4-pin mid-harness and 8-pin mainboard connectors are fully latched.
- OBD Socket Pins: Ensure vehicle OBD socket pin receivers are not stretched or loose to maintain firm contact.

Q: What should be done if the VisiCan display enters a continuous restart loop (boot loop)?

Boot Loop Resolution: Boot loops occur when invalid parameter configurations are saved or corrupt EEPROM memory access occurs due to low battery voltage during boot. Hold Button 4 while turning on ignition to force-boot into the Settings Menu. Cycle through menu pages to the final page using Button 4 to save and auto-sanitize memory.

Q: What are the vehicle-specific power supply requirements for VisiCan Data Displays?

VAG, Renault, Peugeot, etc. (European Platforms): OBD ports on these vehicles include switched +12V power on Pin 1. Standard VisiCan OBD harnesses draw power automatically via Pin 1, switching the display ON and OFF with ignition automatically.
BMW E-Series LCI, F-Series, and G-Series: OBD ports on these vehicles do not feature switched +12V ignition power; they provide 24/7 permanent battery power. VisiCan detects ignition state via CAN-Bus data (F-Series) or battery voltage level monitoring (G-Series). When ignition turns off, the display enters a low-power Sleep Mode and disables side buttons.
Honda Civic 10th Gen, Civic Type R FK2 / FK8, Hyundai i20N, etc. (Asian Platforms): OBD ports on these vehicles lack switched +12V power and provide 24/7 constant battery power. Operating VisiCan on these platforms requires running a fused +12V switched ignition lead from the internal fuse box directly to the inline lever-lock terminal on the VisiCan OBD harness.

Q: What causes screen dimming, power shutoff during long drives, or temporary darkening in direct sunlight?

Thermal Protection Fuse (55°C–60°C): VisiCan displays feature an electronic thermal fuse system. When motherboard temperatures reach 55°C–60°C (caused by ambient heat build-up or hot air blowing), brightness automatically reduces. If heating continues, power shuts off temporarily to prevent circuit damage. Use brightness levels 1–2 steps below maximum during extreme heat.
Localized Solar Darkening: Concentrated solar heat on display panels causes temporary LCD darkening. Panels are rated up to 120°C and normalize once cabin temperatures cool.
Hardware Solder/Flex Cable Fault: If a screen dims/goes dark after 1–2 minutes at normal ambient temperatures and only recovers when physical finger pressure is applied to the panel, this indicates a hardware failure (flex cable detachment or cold solder joint) requiring bench repair.

Q: What are the differences between standard and heavy-duty industrial OBD harnesses?

Standard OBD Harness: Standard plastic OBD connector housing with integrated Flex Fuel sensor leads.
Heavy-Duty Industrial OBD Harness (Additional Price): Enlarged, high-impact industrial plastic connector designed to withstand extreme foot strikes or workshop tool impacts. Because the housing is rigid, severe impacts will not break the connector, but may transfer force to the vehicle's factory OBD port housing.

4. Auxiliary Systems: Flex Fuel, External Sensors & Hardware Control

Q: How is an aftermarket Flex Fuel (ethanol) sensor installed and wired to a VisiCan Display?

Sensor Compatibility: Requires an aftermarket ethanol sensor (e.g., GM, Continental, Bosch) with a 50–150 Hz frequency output.
Sensor Wiring & Pull-Up Resistor:
1. Install sensor in the fuel line; supply switched +12V power (from an external vehicle fuse circuit) and chassis ground.
2. Connect a 2200 Ohm (2.2 kΩ), 1/4-Watt resistor between the switched +12V power wire and the sensor's signal output wire.
3. Connect the sensor's signal output wire to the yellow wire on the VisiCan OBD harness splice section.
Circuit Protection Warning: Never draw +12V power for the ethanol sensor directly from the VisiCan OBD harness. Tapping harness power can overload the factory OBD fuse or interfere with ECU power supply lines.

Q: How do external analog inputs work for non-OBD parameters (e.g., External Oil Pressure/Temperature Sensor Connection)?

Analog Input Channels: VisiCan displays feature 4 external I/O channels. Channels 3 and 4 support 0–14.4V analog signals (compatible with 0–10V industrial pressure sensors and NTC temperature sensors, such as Bosch 0261230482 dual temp/pressure sensors).
Display Location: Live analog readings are displayed under the dedicated Sensor Page in the VisiCan menu.

Q: How are VisiCan displays configured to control external hardware (e.g., Methanol Injection, Shiftlight LED/Buzzer)?

3.3V Logic Output Signal: The Programmable Alarm & Output Module triggers a 3.3V control signal on dedicated output leads based on real-time parameters (Boost, RPM, IAT, Throttle).
Hardware Interfacing (12V Loads): To trigger 12V relays, solenoids, or methanol pumps, an external relay/interface board must step up the 3.3V logic signal to a 12V / 0.75A (750mA) output.
Shiftlight LED Wiring & Setup:
- Wiring: Red to Switched +12V, Black to Ground, Orange wire to auxiliary Orange lead on VisiCan harness.
- Menu Setup: Under OUTPUT SETTINGS 1, assign parameter to RPM, set START@ warning RPM, FULL@ shift point RPM, and duty cycle D@ (50% for flashing; 90% for solid).
Safety Warning: Due to minor latency inherent in OBD2 queries, VisiCan does not recommend using OBD-triggered outputs for primary engine safety functions (e.g., primary methanol delivery on aggressive timing tunes).

5. Firmware Updates, USB/Wi-Fi Flashing & UI Configurations

Q: How are firmware updates requested, and what is VisiCan's custom firmware policy?

Standardization Policy: VisiCan firmware builds are standardized for quality control. Custom, user-exclusive, or one-off firmware modifications are not permitted, as changes affect all devices sharing that firmware model.
Free Updates (Under Warranty): Devices under the 2-year warranty receive free stability updates via email. Email info@visicaneu.com with contact details, vehicle specs, and a photo of the System Info screen (obtained by holding Button 3 during ignition start).
Out-of-Warranty / Feature Update Flashing Fee: Out-of-warranty updates or paid feature upgrades incur a standard service fee paid via corporate bank transfer prior to file delivery.

Q: How do I put a VisiCan display into Firmware Programming Mode (USB TTL vs. Wi-Fi Module)?

USB TTL Programmer Flashing (4th Gen / 5th Gen):
1. Turn off vehicle ignition completely.
2. Press and hold Button 1.
3. Turn ignition ON while holding Button 1. The device boots directly into Flashing Mode.
Wi-Fi Flashing / Programmer Mode:
1. Enable Programmer Mode in the Wi-Fi Module web interface.
2. Press and hold Button 1 and Button 2 simultaneously while turning on ignition. Screen remains dark, confirming hardware bootloader mode.

Q: How do I select, reconfigure, or save values displayed on the VisiCan main page layout?

Navigation & Saving:
1. Turn off ignition.
2. Press and hold Button 4 while turning on ignition to enter the Settings Menu.
3. Use side buttons: Button 1 (Back), Button 2 (Increase), Button 3 (Decrease), Button 4 (Next page / Save on final page).
4. Assign desired parameters to main page slots and cycle to the final page to save.
Cell Population Requirement: 4th and 5th Gen displays support up to 8 main page parameter cells. All 8 slots should be populated with active, valid ECU PIDs. Leaving cells blank or selecting unsupported PIDs introduces protocol timing delays.
Multi-PID Query Multipliers: Single parameter labels may query multiple ECU registers behind the scenes (e.g., KWx queries retard across all cylinders; AFR queries actual and target AFR). Displaying 8 parameters may generate 12–15 total ECU queries per cycle.

🎥 Settings Menu Navigation & Setup Guide Video:

Q: How do I adjust or disable screen brightness, color themes, and Auto Day/Night mode?

Direct Brightness Adjust (4th Gen): Press Button 3 on active gauge pages to toggle brightness levels. To save brightness settings to memory, change the screen page after adjusting.
Disabling Auto Day/Night Mode (5th Gen): Enter Configuration Menu (hold Button 4 at boot). Set Auto Day Night to 0 (Disabled). Cycle to the final page to save.
Recommended Brightness Settings: Set Day Brightness to 3–5, Night Brightness to 1–3, Auto Day/Night Switch threshold to 20–25 (up to 40 for tinted cabin glass), and Auto Brightness Min to 0.

Q: What post-flashing configuration settings must be verified on 5th Generation displays after updating firmware?

A: Hold Button 4 at startup to enter the Configuration Menu and verify:

Invert.C: Set to 0 or 1 (toggle if screen colors appear inverted).
Rotation: Set to 2 or 4 (depending on physical screen mounting orientation).
Can Debug Mode: Must be set to 0.
Save and exit on the final page to re-initialize configuration EEPROM.

Q: What causes a solid white screen or corrupt/missing parameter labels, and how is it resolved?

Solid White Screen: Flashing incompatible firmware, UI themes, or boot logos across unsupported generations (e.g., 5th Gen background bitmaps flashed to 4th Gen hardware) causes white screen errors. Reflash the matching firmware version using the USB programming interface and PC.
Corrupt/Blank Parameter Labels: Vehicle voltage drops, battery drain, or jump-starting can corrupt activation settings in EEPROM. Re-flashing the display with matching firmware restores factory activation parameters.

Q: How do I generate and upload custom startup boot logos or custom UI graphics?

Generating Boot Logos: Visit https://www.visicaneu.com/WebTools.html, select Boot Logo Tool, choose the matching format for your VisiCan hardware, upload image, click Generate HEX, and download the .hex asset file.
Uploading Assets: Upload generated files using the Wi-Fi Module web interface or USB programming interface. (Factory boot logos are intentionally left-aligned; full-screen custom graphics replace factory logos entirely).
USB Graphics Flashing: Direct USB loading of custom UI themes/graphics requires firmware version April 2026 or newer.

Q: Troubleshooting PC USB driver connection errors.

PC COM Port Not Detected:
1. Inspect 6-pin USB extension lead connections in footwell.
2. Disconnect extension lead and plug USB TTL programmer directly into computer USB port.
3. Verify Silicon Labs / FTDI CP2102 drivers in Windows Device Manager.
4. Launch Flashing Tool at https://www.visicaneu.com/WebTools.html, select active COM port, select binary .hex file, and click Flash Firmware.

Q: Troubleshooting Wi-Fi Module OTA updates and web interface connection errors.

Wi-Fi Module Locked in Boot Mode / Blank Web Page:
1. Connect PC/mobile device to Wi-Fi Access Point and open web interface.
2. Toggle Programmer OFF and cycle vehicle ignition.
3. Execute RTC SYNC 3–4 times consecutively until time updates.
4. If web page remains blank, click UI UPDATE (OTA) and wait 30–45 seconds.

NOTE: Unless explicitly instructed by support, do not click Clear Flash or Format Flash, and do not fill storage beyond 75% capacity.

6. Software Add-on Modules, Diagnostic Functions (DTC) & Output Controls

Q: Which software add-on modules are available, how are they licensed, and do firmware updates automatically unlock them?

Available Modules:
1. 5th Generation Graphics / Boost Page: Adds circular gauge graphics, modern layout themes, and a dedicated boost meter screen.
2. Programmable Alarm & Output Module: Enables customizable alarm thresholds and external output triggers.
3. DTC Listing & Clearing Module: Enables diagnostic fault code reading and clearing for engine control units (ECU).
Licensing Policy: Base firmware updates do not automatically activate unpurchased add-on modules. Optional modules must be purchased individually or bundled during hardware order build.

Q: How does the Diagnostic Trouble Code (DTC) reading, mapping, and clearing feature work?

ECU Isolation & Inquiry: The DTC module connects directly to the Engine Control Unit (ECU) to query registered engine fault codes. Transmission (TCU), Airbag, ABS, or body control modules are not listed on standard queries.
Fault Code Screen Output: Upon querying, the display reports the total count of detected codes (e.g., CHECKING DTC(S) 04 FOUND) followed by the raw decimal DTC listing (e.g., 7900, 2937, 5671, 4201).
Clearing Stored Fault Codes: Pressing Button 3 while on Page 1 dispatches an immediate clear command to the vehicle ECU. On standard setups, this purges stored ECU fault codes; on newer vehicle protocols/models, this command clears stored fault codes across all vehicle control modules.
Raw Numeric DTCs on 2012+ VAG UDS Vehicles: On 2012+ VAG UDS ECUs, VisiCan reads raw decimal fault codes directly from ECU memory registers. Because OEM databases (ODIS, VCDS) rely on multi-gigabyte lookup tables to translate numbers to P/U-codes, VisiCan displays the raw decimal code (e.g., 04675).
Cross-Referencing Raw DTCs: Users can search online using the format VAG DTC [number] (e.g., searching VAG DTC 4675 identifies 4675 - Please Check Fault Codes in Control Module for ABS Brakes / U1017).

Q: How are VisiCan Programmable Alarm thresholds calculated for target/specified ECU parameters (e.g., HPF, BTR)?

Delta Deviation Calculation: For parameters with ECU-generated target/specified values (e.g., High-Pressure Fuel Rail Pressure - HPF, Target Boost - BTR), alarm limits (WARN@ and ALARM@) calculate the absolute delta (difference) between ECU target and live actual readings.
Trigger States:
- WARN@ State: Parameter text turns orange when deviation exceeds configured WARN@ offset threshold.
- ALARM@ State: Parameter text turns red and screen border flashes when deviation exceeds ALARM@ threshold.

7. Trade-in, Warranty, Service Returns & Business Policies

Q: What are VisiCan's warranty coverage terms, exclusion criteria, and support policies for second-hand units?

Warranty Terms: VisiCan Displays include a 2-year manufacturer warranty covering manufacturing defects.
Exclusions: Liquid damage, physical housing/screen damage, cracking/breaking of plastic enclosure, unauthorized disassembling/opening, chemical degradation, or forced connector installation despite physical keying are excluded from warranty coverage.
Second-Hand Support: Warranty remains valid for second-hand units within the original 2-year period regardless of owner transfer. Free email technical support and firmware updates are provided. Owners can purchase new ECU communication firmware for vehicle transfers. VisiCan does not offer remote flashing, intervene in second-hand buyer/seller disputes, confirm third-party compatibility, or share previous owner details.

Q: How does the Trade-in / Upgrade Program work when upgrading to a 5th Generation display or new vehicle platform?

Trade-in Credit Procedure: Customers upgrading to a new-generation display can send their functional, invoiced, under-warranty VisiCan display via tracked courier under trade-in terms. Upon bench inspection of the returned unit, a trade-in credit refund is issued.
Harness Compatibility: Harnesses and USB programming cables remain cross-compatible across generations and can be retained during platform updates.

Q: What is the process and cost for re-fitting a VisiCan display for a different vehicle chassis or ECU type?

Same Chassis / Different ECU (e.g., Golf Mk7 1.4 TSI to Golf Mk7 GTI 2.0 TSI): Physical housing remains unchanged. A new ECU communication firmware license must be purchased and flashed via PC.
Different Chassis / Platform Swap (e.g., BMW F30 to Cupra Formentor VZ or Audi S3 8Y to Golf Mk8): Requires sending the functional unit to VisiCan via tracked courier. VisiCan replaces physical housing components, screen mountings, and communication firmware according to standard after-sales component exchange rates (depending on display size and selected software add-on bundles). Component re-fitting does not reset or extend the original warranty duration.

Q: How are customer support, local installations, and payment errors handled?

Support Channels: VisiCan does not operate walk-in retail showrooms, customer reception offices, or live phone/video support. All technical service, warranty evaluations, and bench repairs are processed via tracked courier (Yurtiçi Kargo in Turkey; DHL/FedEx internationally). Technical assistance is provided exclusively via text ticketing and email (info@visicaneu.com). Installations are performed by the end-user or for a fee through our recommended partner workshop network.
Checkout Payment Errors (TRY Regulation): Domestic transactions in Turkey are regulated by BDDK and must be processed in Turkish Lira (TRY). If credit card errors occur at checkout, switch the website currency selector to TRY, empty the cart, re-add items, and complete checkout.
Promotional Discount Errors: If promotional codes are missed during checkout, VisiCan accounting issues partial card refunds to reflect verified campaign rates. Tax invoices (E-Invoice) require personal national-id or corporate tax numbers and can be billed separately from third-party workshop delivery destinations.