Connect separate fields and facilities
Review coverage, equipment identity and the path into your chosen platform.
Read the guideApplication guides
Asset Tracking IoT Hardware
Specify the asset, reporting interval, cellular region, mounting and customer-server endpoint. SunGene then selects a long-standby tracker and documents the configuration for a pilot.
GPS / GLONASSLTE Cat.1 / Cat.MWi-Fi scanBluetooth 5.0MQTT / TCP / UDP
Hardware in this guide
Product-family photos. See each product page for specifications and options.
Typical Use Cases
- Container and trailer status
- Generator and construction-equipment location
- Rental and returnable asset tracking
- Unpowered field-equipment visibility
Measured Parameters
- GPS / GLONASS location and movement events
- Reporting, sleep and retry profile
- Battery and offline status
- Optional door, tamper or BLE accessory events
Primary Hardware
- Long-standby GPS asset tracker
- Regional LTE Cat.1 or Cat.M configuration
- Three Li-FeS2 AA primary cells
- Screw / bolt or optional magnetic mounting
Tracking reusable containers
Illustration: warehouse tracking installation with a rugged tracker on a reusable logistics container. Tracker, mounting, reporting interval, regional cellular profile, optional sensors and documented server handoff are confirmed before quotation.
See where the system fits
Keep remote measurement points supplied
Size field power around the final equipment load, seasonal sunlight and visit interval.
Read the guideDefault asset-tracking data path
The standard configuration uses one long-standby cellular tracker. A fixed gateway is considered only for a separately defined BLE aggregation or closed-site collection project.
LTE Cat.1 / Cat.M · MQTT / TCP / UDP
Data destination
Customer-owned tracking server or third-party asset-management platform
Default Data Handoff
- MQTT, TCP or UDP customer-server handoff
- Wi-Fi scan data for compatible indoor workflows
- Nano-SIM / eSIM, APN and region review
- Payload, acknowledgement and store-and-forward alignment
What SunGene Prepares
- Destination-specific LTE Cat.1 or Cat.M tracker configuration
- Mounting, reporting and optional sensor selection
- Documented MQTT, TCP or UDP payload and customer-server handoff
- Pilot quotation with runtime assumptions and acceptance points
What the Customer Provides
- Asset type, movement and mounting surface
- Target country, operator and SIM preference
- Reporting interval, event rules and runtime target
- Customer endpoint, payload and security requirement
Hardware reference
Product-family photos; the model and enclosure may vary.
Related Pages
Related selection guides
FAQ
What does SunGene need to quote the asset tracker?
Share the asset type, destination country, operator or SIM preference, mounting surface, reporting interval, optional event inputs and customer-server endpoint. We then confirm the tracker, regional cellular configuration, mounting, reporting profile and documented data-handoff requirements.
Does a cellular asset tracker need an edge gateway or RTU?
Not in the default architecture. The tracker uses LTE Cat.1 or Cat.M and sends MQTT, TCP or UDP data directly to the customer-owned tracking server or third-party platform. A fixed gateway is considered only for a separately defined BLE aggregation or closed-site collection project.
Can this connect to our existing tracking platform?
Yes, when the platform accepts the selected MQTT, TCP or UDP device profile. The server endpoint, payload, acknowledgement, security, APN and store-and-forward behaviour are confirmed before the pilot.
Does SunGene operate the tracking platform?
SunGene can provide agreed software, platform connections and data integration alongside equipment supply and farm BOM planning. We define functions, account ownership, recurring fees, testing and maintenance in the quotation. Local teams carry out onsite construction; SunGene can help coordinate them.