Hello,
We are currently integrating Teltonika FMC150 trackers into our own fleet-management platform and would appreciate some technical guidance regarding CAN AutoScan, OEM profiles and future vehicle support.
Our first vehicle is:
• Vehicle: Ford Transit Custom
• Model year: 2025
• Market: United Kingdom
• Right-hand drive
• Tracker: Teltonika FMC150
• FMC150 firmware: 04.01.00 Rev:08
• Configurator: Teltonika Configurator 1.8.21_B.4.01_R.10
• LVCAN software version: 25-06-20
• LVCAN full version: FWVer 00020601 / BLVer 00000400
• Connection method: OBD-II breakout/splitter
• Permanent power: OBD pin 16
• Ground: OBD pin 4/5
• Vehicle data is transmitted securely to our own server using Codec 8 Extended over TCP/TLS.
Initially, we connected the FMC150 CAN1 input to the standard OBD-II CAN pins:
• Pin 6 – CAN High
• Pin 14 – CAN Low
The FMC150 detected the LVCAN adapter, and the Configurator displayed “OEM AutoScan Running”. However, we left the vehicle running for approximately 15–20 minutes on more than one occasion and AutoScan never completed or loaded an OEM profile.
While AutoScan was running, only Module ID 17B was visible. We did not receive decoded values such as engine RPM, vehicle mileage, fuel level, fuel consumption, engine work time or door status.
We then connected the FMC150 CAN2 input to the Ford network exposed on:
• OBD pin 3
• OBD pin 11
After connecting to pins 3/11, AutoScan completed almost immediately and the Configurator displayed:
“OEM File Loaded”
This appears to confirm that the correct network for this 2025 Transit Custom is available through OBD pins 3/11 rather than the standard diagnostic CAN network on pins 6/14.
Could you please confirm the following?
-
Is OBD pin 3 CAN High and pin 11 CAN Low for the supported 2025 UK Ford Transit Custom installation?
-
Is CAN2 the correct FMC150 channel to use for this vehicle, or should the network on pins 3/11 be connected to CAN1 instead?
-
Can pins 6/14 remain connected to CAN1 while pins 3/11 are connected to CAN2, or should only the working network on pins 3/11 be connected?
-
Which Ford Transit Custom OEM profile has AutoScan loaded?
-
Is there a profile number, vehicle number or OEM-file identifier that we can record for repeat installations on identical vehicles?
-
Where can we see the exact loaded profile identifier in Configurator, FOTA WEB or through an SMS/GPRS command?
-
Which CAN values are supported by this profile? We specifically need:
• Vehicle speed
• Engine RPM
• Total vehicle mileage
• Engine work time
• Fuel level
• Fuel consumed
• Fuel consumption
• Ignition status
• Acceleration-pedal position
• Engine load
• Engine temperature
• AdBlue level
• Door status
• Handbrake status
• Warning indicators
• Diagnostic or maintenance information, where available -
Do these values simply need to be enabled with Low priority under CAN I/O after the OEM file has loaded?
-
Will AutoScan and OEM-profile downloads continue to work without our own FOTA WEB account? We are a small UK integrator and have been advised that direct FOTA WEB access may not be available to us.
-
If AutoScan cannot identify a future vehicle, how can a smaller integrator obtain the correct supported OEM file? Is there a formal support process where we can provide the VIN, make, model, year and CAN logs?
-
Does Teltonika provide any supported way to create a custom CAN mapping for an unsupported vehicle, or does that require a different Teltonika device with manual CAN functionality?
Our objective is to commission several FMC150 units across our own vans and integrate all telemetry directly into our private SaaS platform. We are not using a third-party tracking platform.
The GPS, LTE, TCP/TLS and Codec 8 Extended connection to our server are already working. Our remaining concern is ensuring that CAN profiles and decoded vehicle data can be commissioned reliably on this Ford and on future vehicles without depending upon access that smaller integrators cannot obtain.
We can provide screenshots, the FMC150 configuration file, IMEI privately, LVCAN adapter ID, VIN and additional diagnostic information if required. We will not post the full IMEI or VIN publicly.
Thank you for your help.