Hello,
We have recently purchased the Teltonika FMM003 OBD tracker for a fleet telemetry research project in South Korea. We are testing it on various Korean vehicles (both Internal Combustion Engine (ICE) and Electric Vehicles (EV)).
Although the FMM003 supports a wide range of OBD2 and I/O parameters, we are currently receiving very limited data during our tests. Since we are in the early R&D phase, our primary goal is to gather as much data as possible (regardless of whether the values are active/valid or not for a specific vehicle) so we can analyze what is available.
Additionally, to detect transient states like regenerative braking in EVs (which might not expose direct pedal states on standard OBD2), we want to implement a high-frequency data acquisition setup:
- Logging/Data gathering interval: 1 second
- Server sending interval (via LTE): 1 minute
We would highly appreciate your guidance on how to configure the I/O and OBD2 tabs in the Teltonika Configurator to achieve this safely without overloading the device.
Specifically, we have the following questions:
1. Priority Settings:
If we want to collect all available parameters in every record, should we set the Priority of all targets to “Low”? If we set them to “High” or “Panic”, we assume it will cause immediate GPRS connections for every tiny change, leading to network overload, battery drain, and buffer overflow. Is this correct?
2. Event Only:
To ensure we receive all data points at every single log interval (without missing fields when values don’t change), should we set “Event Only” to “No” for all parameters?
3. Operand & Averaging Constant:
Is it correct to keep the Operand as “Monitoring”? Also, for highly dynamic values like pedal positions or speed to detect regenerative braking, should we set the “Averaging Constant” to “1” to avoid any delay or filtering?
4. Low Level / High Level:
For simple periodic monitoring (where we don’t need threshold-based alarms), should we just leave the “Low Level” and “High Level” values at “0” (default)?
5. Data Acquisition Frequency:
Is the device stable enough to handle a 1-second record generation (Min Period = 1s or 1000ms) and a 1-minute server upload (Send Period = 60s)?
Are there any hardware limitations (such as RAM buffer limits, flash memory writes, or CAN bus load) we should be aware of when logging dozens of OBD2 parameters at a 1-second interval? What are the best-practice limits for the minimum period on the FMM003?
6. Obtaining OEM/Custom OBD2 Data for Korean Vehicles:
Since standard OBD2 PIDs on Hyundai/Kia ICEs and EVs are quite limited, does the FMM003 support reading OEM CAN/OBD parameters for Korean vehicles? If so, do we need to configure Custom OBD PIDs, or is there a specific database/firmware we should use?
Thank you in advance for your support. As we are new to Teltonika hardware, your detailed guide will be extremely helpful for our project.
Best regards