Teltonika FMC130 Advanced 4G LTE Cat 1 Tracker For Fleet

Product Information

Specifications

• Network Coverage: 4G (LTE Cat 1) with 3G (UMTS) and 2G (GSM) fallback compatibility
• Features: Internal GNSS, LTE antennas, configurable digital/analog/negative and impulse inputs, three DOUT outputs, Bluetooth connectivity, backup battery
• Compatibility: Developed on the existing Teltonika FMB platform
• Additional Features: Negative input for connecting accessories, Impulse Input for fuel flow meter data reading, programmable inputs, configurable DOUT scenarios

Product Usage Instructions

Set up your Development Environment
Install necessary tools including IDEs, Toolchains, SDKs for development and debugging applications for the device.

Set up your Hardware
Ensure all hardware components are correctly connected and powered up.

Setup your AWS Account and Permissions
Create an AWS account and set up necessary permissions for device communication.

Create Resources in AWS IoT
Create resources in AWS IoT to enable device communication with the platform.

Provide Device with Credentials
Configure the device with necessary credentials for authentication.

Checking Received Data and Sending Commands in AWS IoT Core
Monitor received data and send commands using the AWS IoT Core platform.

Debugging and Troubleshooting
If issues arise, refer to the debugging and troubleshooting sections in the manual for assistance.

FAQ

1. Q: What firmware version is required for MQTT solution evaluation?
   A: Firmware version 03.27.10.Rev.520 is required for MQTT solution evaluation. Contact your sales manager or Teltonika Helpdesk for firmware supporting MQTT.

2. Q: Where can I find firmware update information?
   A: Changes in firmware versions and update information can be found on the device wiki page: FMC130 firmware errata.

https://wiki.teltonika-gps.com/view/FMC130_Getting_Started_with_AWS_IoT_Core

Document Information

Glossary

• FMC130 (tracker) – GNSS tracking device manufactured by Teltonika Telematics.
• Wiki – Teltonika IoT knowledge base – Teltonika Wiki.
• FOTA – Firmware Over The Air.
• Configurator – Tool to configure Teltonika Telematics devices.
• Crowd support forum – knowledge base dedicated for Troubleshooting.

Revision History (Version, Date, Description of change)
Version  Date Description
v1.5         2023.02.14 Links updated
v1.4        2022.12.19 Minor information update
v1.3          2022.11.29 Page created

Overview

FMC130 is a small ADVANCED series device with 4G (LTE Cat 1) network coverage including 3G (UMTS), 2G (GSM) fallback compatibility. It comes equipped with internal GNSS, LTE antennas, configurable digital/analog/negative and impulse inputs, three DOUT outputs, Bluetooth connectivity, and backup battery.
FMC130 developed on the existing Teltonika FMB platform, therefore it keeps all of the functionalities from FMB130 and builds on top of them with its industry-leading connectivity coverage.
For starters, FMC130 features negative input which allows you to save precious integration time while connecting accessories like vehicle doors sensor, alarm buttons, seatbelt detection, and other similar sensors or accessories.
Additionally, the device has an integrated possibility to enable Impulse Input for precise fuel flow meter data reading. Impulse based fuel usage monitoring is much more accurate than a different type of fuel metering sensors and it makes the FMC130 a perfect solution for high fuel usage machines like cranes, construction vehicles, mining machines, agriculture equipment.
Programmable inputs, 3 different configurable DOUT scenarios (immobilizer, buzzer, alarm lights, door lock and other scenarios) together with 4G (LTE Cat

1. compatibility including the 3G (UMTS) and 2G (GSM) fallback compatibility make this one of our most flexible devices ever.
   Currently for MQTT solution evaluation firmware is required to be used – 03.27.10.Rev.520. For firmware supporting MQTT please contact your sales manager or contact directly via Teltonika Helpdesk.
   Changes in firmware versions and update information can be found in device wiki page: FMC130 firmware errata

Hardware Description

DataSheet
FMC130 device data sheet can be downloaded here: DataSheet

Standard Kit Contents
STANDARD PACKAGE CONTAINS

• 10 pcs. of FMC130 trackers
• 10 pcs. of Input/output power supply cables (0.9 m)
• Packaging box with Teltonika branding

Teltonika suggest standard order codes for the device purchase, by contacting us, we can create special order code which would fulfill user needs.
More ordering information at: Ordering

User Provided Items

• Power supply (10-30V).
• MicroUSB to USB A cable.

Set up your Development Environment

Tools Installation (IDEs, Toolchains, SDKs)
FMC130 comes with our created firmware, therefore no additional development or scripting is required for this unit to support AWS IoT. Only by using Teltonika Configurator FM Configurator versions, connection point of AWS IoT server is required.

Other software required to develop and debug applications for the device
For debugging situations, device internal logs can be downloaded OTA by using our FotaWEB platform or by using Teltonika Configurator.

Set up your hardware
All details about FMC130 can be located in our dedicated wiki page FMC130 Wiki

• Basic device startup instructions provided in FMC130 First Start.
• Device characteristics, power supply information: FMC130 General description
• FMC130 firmware change can be performed via FotaWEB (direct buyer gets access to this platform) or via device Configurator
• Device LED information: FMC130 LED Status
• USB driver download, datasheet and quick start guide downloads: FMC130 Downloads

Document Information

Glossary

• Wiki – Teltonika IoT knowledge base – https://wiki.teltonika-iot-group.com/.
• FOTA – Firmware Over The Air.
• Configurator – Tool to configure Teltonika Telematics devices.
• Crowd support forum – knowledge base dedicated for Troubleshooting.

For firmware supporting MQTT please contact your sales manager or contact directly via Teltonika Helpdesk.

Other software required to develop and debug applications for the device
For debugging situations, device internal logs can be downloaded OTA by using our FotaWEB platform or by using Teltonika Configurator.

Setup your AWS account and Permissions
Refer to the online AWS documentation at Set up your AWS Account. Follow the steps outlined in the sections below to create your account and a user and get started:

• Sign up for an AWS account
• Create a user and grant permissions
• Open the AWS IoT console

Pay special attention to the Notes.

Create Resources in AWS IoT
Refer to the online AWS documentation at Create AWS IoT Resources. Follow the steps outlined in these sections to provision resources for your device:

• Create an AWS IoT Policy
• Create a thing object

Pay special attention to the Notes.

Provide Device with credentials
Whole device, AWS IoT and testing information can be downloaded in PDF format here.
NOTE: MQTT will not work without uploaded TLS certificates.

AWS IoT Core Configuration

Setting up AWS IoT Core
When logged in the AWS console, click on Services on the top left hand side screen, to access IoT core.

NOTE: If you can’t see “Services” in the top left, click on “My account” in the top right and “AWS Management Console”
Select Manage, Security, Policies (Manage > Security > Policies) and press Create policy or Create buttons .

Figure 2. Accessing policy creation
In the Create Policy window, enter Policy name. In the Policy document tab for Policy Action (1) select “” and for Policy resource (2) enter “” and press create .

Figure 3. Creating a policy
Now, that you have created a policy, select Manage on the sidebar on the left side, then select All devices, Things (Manage>All devices>Things). And click on Create things .

Figure 4. Accessing Things
Afterwards select Create single thing and click Next.

Figure 5. Creating single thing
After creating a single thing, enter Thing’s name and in the Device Shadow tab select Unnamed shadow (classic). Then click Next.

Then when selecting Device certificate, select Auto-generate a new certificate and click Next.

Figure 7. Certificate configuration
Now, select the policy you have created before to attach it to the certificate and thing. After that click Create thing.

Then window with Certificate files and key files download options should pop out. It‘s recommended to download all files, because later some of them will not be available for download. The files that are required for usage with FMX devices are: Device certificate (1), private key(2), and Amazon Root CA 1 file(3), but it‘s recommended to download them all and store them in secured place.

Figure 9. Certificate and key download
Finding device data endpoint (server domain)
To receive server domain (in AWS endpoint) click on the side bar on the left Settings (AWS IoT->Settings). Or click on the side bar on left side Things, select the created thing, after it click Interact->View Settings. Whole path – (Things->YourThingName->Interact->ViewSettings). Page containing endpoint will open. Copy the whole endpoint address. Port for accessing this endpoint is 8883.

Configuring the device

Security and certificates

Using certificate, private key and root certificate. (Via Cable)
Find Certificate file ending with extension pem.crt (ending may be just .pem) Private key file and AmazoonRootCA1 file (no need to change filenames). These files should have been downloaded when creating Thing in AWS IoT Core.

Figure 17. Certificate, private key and root certificate
Upload the mentioned files in the Security tab in the Teltonika Configurator.

Figure 18. Uploading certificates and keys
After uploading certificates, go to System tab and in Data protocol section select – Codec JSON.

Figure 19. Choosing data protocol
Device GPRS configuration for AWS IoT Custom MQTT settings
In the GPRS tab, under Server Settings select:

1. Domain – Endpoint from the AWS, Port: 8883
2. Protocol – MQTT
3. TLS Encryption – TLS/DTLS

In the MQTT Settings section select:

1. MQTT Client Type – AWS IoT Custom
2. Device ID – enter device IMEI (optional)
3. Leave Data and Command Topics unchanged.

Save the configuration to the device .

Figure 27. GPRS Settings for MQTT AWS IoT
Checking received data and sending commands in the AWS IoT core
The data received from the device can be found in the MQTT test client, which can be found above “Manage” in the sidebar on the left .

Figure 28. MQTT test client location
To see incoming data, subscribe to topic – DeviceImei/data . Or subscribe to

to see all incoming outgoing data in the Topics.

Figure 29. MQTT test client
Incoming data is received in JSON format, for e.g.:

Figure 30. Received data format
To send SMS/GPRS commands to the device subscribe to a topic name – DeviceIMEI/commands, and, in the same MQTT test client window select Publish to a topic. Enter topic name – DeviceIMEI/commands. In the Message payload enter wanted GPRS/SMS command in following format and press Publish:

Figure 31. Sending Command in AWS IoT Core
The response to the command will be shown in the Data topic:

Debugging
In the situation when the issue with information upload appears, device internal logs can be taken directly from device configuration software (instructions), via Terminal.exe by connecting selecting device USB connection port, or by receiving internal logs via FotaWEB in task section.

Troubleshooting
The information can be submitted to Teltonika HelpDesk and Teltonika engineers will assist with troubleshooting. For a more detailed information regarding what information should be collected for debugging, please visit the dedicated page on Teltonika Wiki.
Alternatively, Teltonika has a Crowd Support Forum dedicated for troubleshooting, where engineers are actively solving problems.

Troubleshooting
The information can be submitted to Teltonika HelpDesk and Teltonika engineers will assist with troubleshooting. For a more detailed information regarding what information should be collected for debugging, please visit the dedicated page on Teltonika Wiki.
Alternatively, Teltonika has a Crowd Support Forum dedicated for troubleshooting, where engineers are actively solving problems.

Debugging
In the situation when the issue with information upload appears, device internal logs can be taken directly from device configuration software (instructions), via Terminal.exe by connecting selecting device USB connection port, or by receiving internal logs via FotaWEB in task section.

References

• FOTA WEB

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>