MORE articles

16/07/2026
FUEL CONTROL: WHAT SOLUTION TO CHOOSE?

15/07/2026
E-MOBILITY IN LATIN AMERICA: CHALLENGES, OPPORTUNITIES, AND TELEMATICS SOLUTIONS

14/07/2026
SMART CAN DATA READING WITH WIALON & TELTONIKA
HOW TO READ CAN BUS DATA FROM NON-STANDARD VEHICLES: E-BIKES, E-MOPEDS, AND MORE
6 minutes
23/07/2026
E-bikes, e-mopeds, e-forklifts, electric street sweepers, and other light electric vehicles are moving from niche pilot projects to real business cases. According to McKinsey, the micromobility market is projected to more than double by 2030, while the electric utility vehicle market is expected to grow by about 98% by 2034, based on Fortune Business Insight report. The opportunities to implement telematics for data-driven decision-making, operational cost control, and proactive maintenance are clear – but so is the challenge: how to support new, fast-growing vehicle niches when each of them may use different CAN data protocols?

THE CHALLENGE OF READING CAN DATA FROM DIFFERENT VEHICLE PROTOCOLS
In classic fleet management, especially in heavy-duty trucks, data access is often more predictable. Standards such as FMS were introduced to provide a dedicated gateway with access to selected fleet-management parameters, including fuel level, fuel consumption, engine speed, odometer, and other useful data.
With e-micromobility, the situation is much more fragmented. One e-bike may use a Bosch motor and battery management system (BMS), while a cargo e-bike may rely on Ananda components, an e-moped may use Askoll technology, and an e-kickscooter may rely on Bafang or another supplier. Each vehicle can have its own CAN protocol, CAN IDs, baud rate, and CAN type, whether Standard 11-bit, PGN 16-bit, or Extended 29-bit.
Even forklifts, city cleaning e-vehicles, electric airport ground service equipment, and vehicles based on more common industrial protocols, such as J1939, are not always plug-and-play when it comes to reading CAN data. Some machinery or utility vehicles use proprietary parameter group numbers (PGNs) or may keep specific data behind gateways. As a result, reading CAN data from e-micromobility and e-utility vehicles often requires a more flexible integration approach than simply supporting a specific standard such as FMS, J1939, or OBD-II.
WHAT CAN BUS DATA IS AVAILABLE FROM E-BIKES, E-MOPEDS, AND ELECTRIC MACHINERY?
The value of CAN bus data depends on the vehicle type and the parameters made available through the CAN network. While manufacturers may implement CAN communication differently and expose different sets of parameters, many electric vehicles and machines can provide operational, battery, diagnostic, and status data through the CAN network, supporting fleet visibility, maintenance, and business decision-making.
The examples below illustrate the types of CAN data that may be available across e-bikes, e-mopeds, e-scooters, electric utility vehicles, and electric machinery. Actual data availability depends on the vehicle platform and CAN protocol implementation.
Data category | Example CAN parameters | Business value |
Movement and usage | · speed · odometer · trip distance · riding mode · assist mode | Helps understand vehicle utilisation, usage patterns, and rider behaviour. |
Battery performance | · state of charge (SoC · state of health (SoH) · power consumption · remaining range | Supports battery monitoring, charging planning, range visibility, and service decisions.
|
Powertrain data | · motor temperature · controller temperature · motor RPM · throttle position · regenerative braking activity | Helps identify abnormal performance, overheating risks, and potential maintenance needs. |
Diagnostics | · fault codes · warning indicators · brake status · system states | Helps identify malfunctions early, streamline troubleshooting, and reduce unplanned downtime. |
Equipment-specific data | · forklift height · load weight · hydraulic system status · actuator positions · pressure values | Provides deeper visibility into how the machine is being used, not only where it is located. |
Safety and readiness | · brake status · handbrake status · operating mode · safety interlocks | Helps confirm the vehicle or machine is safe to operate and ready for use at a given moment. |
CAN-based commands | · lock/unlock · speed limit · mode change · system-specific actions | Can support sharing, rental, delivery, and remote-control use cases when the vehicle protocol allows it. |
Vehicle CAN parameters presented above can support a variety of real-world fleet solutions. In dense urban areas, e-micromobility has become a core part of daily transportation via sharing services of electric vehicles and last-mile logistics. In industrial and municipal environments, telematics solutions for electric utilities can be applied for efficient e-forklift monitoring and e-cleaning fleet management – and in some settings, the stakes of getting this right go well beyond convenience.
Business impact example: in mission-critical environments such as airports, unexpected equipment downtime can quickly cascade into flight delays, and delay themselves carry a significant financial cost. EUROCONTROL estimates tactical delay costs for commercial passenger flights at around €166 per minute at the gate, €182 per minute while taxiing, and €212 per minute en route. Even 15–30 minutes of delay can run into thousands of euros, underscoring why early fault detection and proactive maintenance matter.
WHAT IF THE VEHICLE USES AN UNKNOWN CAN PROTOCOL?
In some projects, CAN protocol documentation is available from the vehicle OEM, battery supplier, and motor or controller manufacturer. In this case, CAN messages can be decoded using the documented CAN IDs, byte positions, scaling factors, and other protocol details. However, documentation is not always available. This is often the case with niche e-mobility platforms, private-label vehicles, low-cost electric utility vehicles, or equipment sourced through multiple suppliers.
When the CAN protocol is unknown or undocumented, reverse engineering can be used to identify valuable CAN parameters. Engineers use specialised CAN analysis equipment and software to monitor and record CAN traffic while observing the vehicle under different operating conditions, such as accelerating, braking, charging the battery, or activating specific vehicle functions. By comparing changes in CAN messages with actual vehicle behaviour, they can identify which CAN messages correspond to specific vehicle parameters and gradually build a CAN parameter map without official documentation.
Once the required CAN data is identified, it can be used for telematics integration, fleet monitoring, diagnostics, proactive maintenance, or remote-control use cases. If you have a project involving a vehicle without protocol documentation, contact your Teltonika sales manager or reach out to us through the contact page.
SOLUTION: FTC305 AND FTM305 WITH MANUAL CAN
Once the required CAN parameters are known, either from official documentation or reverse engineering, the next step is implementation. Traditionally, supporting a new vehicle protocol may require firmware development before data can be read from the vehicle.
FTC305 and FTM305 address this challenge with manual CAN functionality. Instead of waiting for dedicated protocol implementation, users can configure custom CAN messages directly on the device according to the available vehicle protocol.
This approach allows our clients to work with a wider range of e-bikes, e-mopeds, utility vehicles, and electric machinery, including platforms that are not included in standard supported vehicle lists.
Once configured, FTC305 and FTM305 can read vehicle-specific parameters such as battery status, range, temperatures, operating hours, fault codes, and other custom CAN data. The same approach can also be used for CAN-based commands, enabling functions such as lock/unlock actions, speed limitation, operating mode changes, and other control systems.
With support for up to 70 manual CAN messages and up to 10 manual CAN commands (soon to be expanded to 70 CAN commands), FTC305 and FTM305 provide a flexible way to integrate different CAN protocols without requiring dedicated firmware development for every new vehicle model.
Watch the video below to see how to configure Manual CAN messages and Manual CAN commands.
WHY CHOOSE FTC305 AND FTM305 FOR E-MOBILITY AND E-MACHINERY?
FTC305 and FTM305 are part of Teltonika's new-generation FT platform, purpose-built to meet the demands of electric micromobility and e-utility fleets.
One of their key advantages is a wide operating voltage range of 10 V to 97 V, allowing the trackers to cover a broad spectrum of electric vehicles – from e-bikes and e-scooters to forklifts and utility machinery – without the need for external voltage converters. This simplifies installation, reduces costs, and frees up valuable space inside the vehicle.

Space is especially critical in electric two-wheelers, where compartments are small and every millimetre counts. That's why one of the core goals for our R&D team was to design the smallest possible form factor, so the tracker fits seamlessly into tight installation spaces without compromising functionality.
For projects that demand even more flexibility, FTC305 is also available in a no-casing version – a more compact variant designed for OEM in-factory integration. It uses external GNSS and LTE antennas, available in different size options to support your specific installation needs, for improved signal performance. It also features a larger back-up battery – 1,200 mAh, compared to 380 mAh in the standard version. For use cases that require even longer autonomy, an option to add a higher-capacity battery is also available, ensuring reliable operation even during extended power loss.
READY TO GET STARTED?
Whether you are managing a fleet of e-bikes, deploying electric forklifts, or building your own e-mobility solution, FTC305 and FTM305 are ready to support your next project. Contact your Teltonika sales manager or reach out through our contact page to discuss your specific use case.