Search Results

A tanker loses 35 gallons during an overnight stop. The driver returns to a normal route, fuel card activity looks legitimate, and the only visible sign is a lower-than-expected fuel level the following morning. This fuel theft prevention example shows why periodic fuel reports alone are not enough. Fleet operators need a system that identifies the drain event, verifies its context, and gives the operations team time to respond. For commercial fleets, fuel theft is not one problem with one cause. It can involve siphoning from a parked vehicle, unauthorized refueling, fuel-card misuse, tank manipulation, or gradual losses hidden inside normal consumption variation. The practical objective is not simply to install a sensor. It is to create an evidence-based operating process that turns fuel data into accountable action. The fuel theft prevention example: from loss to proof Consider a regional fleet operating 80 diesel trucks. Each vehicle makes scheduled deliveries, parks at a mix of company yards and unsecured customer locations, and has a typical fuel consumption range that varies by load, traffic, idling, and route profile. The fleet has historically reviewed fuel purchases and monthly consumption, but it cannot reliably separate operational variance from theft. The operator installs continuous tank-level monitoring on higher-risk vehicles, paired with GPS tracking, ignition status, and geofencing. The fuel sensor measures changes in the tank independently of fuel-card transactions. The telematics platform receives the readings alongside vehicle location, motion, and operating state. At 2:14 a.m., a parked truck records a rapid 28-gallon fuel-level decrease over seven minutes. The ignition is off, vehicle speed is zero, and there is no authorized refueling event. The location is outside the company's secured yard geofence. Rather than waiting for an exception report the next day, the system classifies the event as a suspected drain and sends an alert to the designated control team. The alert alone does not prove theft. It creates a high-priority event that can be reviewed against the full operating context. The operator checks the tank-level graph, GPS position, ignition state, prior fuel quantity, and the vehicle's planned stop. The pattern is inconsistent with normal use, sensor noise, or a fuel fill. It is logged, escalated according to policy, and compared with any available camera footage or driver report. That is the difference between a useful system and a generic alarm. The fleet has a time-stamped record of what changed, where it occurred, and under what vehicle conditions. Why tank-level data needs vehicle context A fuel-level decrease is not automatically theft. Fuel expands and contracts with temperature, a vehicle may be parked on an incline, and raw readings can shift during movement. A poorly configured alerting rule can create false positives, which reduces trust in the system and causes teams to ignore legitimate warnings. Reliable prevention depends on correlating several signals. Tank-level change identifies the potential loss. Ignition status and speed help distinguish a drain from consumption during operation. GPS location identifies whether the event happened at an approved depot, a fuel station, or an unplanned stop. Time of day, driver assignment, route schedule, and fuel-card data add operational context. A practical rule might trigger only when a fuel decrease exceeds a defined volume within a short period while the vehicle is stationary and ignition-off. The threshold should be tailored to the tank size, sensor resolution, vehicle type, and normal operating conditions. A 10-gallon threshold may make sense for one light commercial application but be too sensitive or too high for another. This is also why installation quality matters. The sensor must be selected and calibrated for the tank design and fuel type, mounted securely, and validated through controlled fills and drains. For fleets with diverse vehicle classes, one configuration should not be assumed to fit every asset. Build a response workflow, not just an alert Fuel theft prevention fails when alerts arrive without clear ownership. A fleet manager may receive a notification after hours, but if there is no escalation process, the event becomes another dashboard entry rather than an operational control. The response should match the risk level. For a suspected active siphoning event, the fleet may notify the driver or security team, verify vehicle location, and direct the driver not to approach an unsafe situation. For a historical event discovered after the fact, the process may focus on evidence preservation, route review, claim documentation, and pattern analysis. A well-defined workflow should specify four elements: Who receives real-time suspected-drain alerts and during which hours. What evidence must be checked before an event is classified as likely theft. Which actions are appropriate for the driver, dispatcher, security team, and fleet manager. How confirmed incidents are documented and used to adjust routes, parking policies, or security controls. The objective is not to create a punitive environment for drivers. It is to protect drivers, equipment, and operating margin while ensuring that genuine anomalies receive a consistent investigation. Use data to identify risk patterns One incident may be isolated. Repeated suspected drains in the same location, time window, or route segment indicate a control gap. Over several weeks, fleet managers can use event data to identify where the risk is concentrated. For example, an operator may find that losses occur primarily at three unsecured overnight parking locations. The appropriate action might be to change parking arrangements, add site lighting or access controls, revise route timing, or require parking within a defined geofence. If events follow a particular vehicle group rather than a location, the investigation may shift toward tank hardware, assignment procedures, or unauthorized access. This approach produces a more accurate business case than estimating fuel theft from aggregate monthly variance. The fleet can measure suspected drain volume, confirmed losses, response time, repeat locations, and loss reduction after controls are introduced. Those metrics are useful for internal operations and for telematics service providers building a value proposition for fleet customers. Select technology for deployment reality A fuel monitoring project must work in field conditions, not only in a demonstration. Commercial vehicles experience vibration, dust, temperature changes, variable power conditions, and inconsistent mobile coverage. Hardware selection should account for sensor accuracy, enclosure durability, installation method, connectivity, integration options, and the diagnostic tools available to installers. For some fleets, wired tank-level sensing is appropriate because it provides continuous measurement and supports detailed analysis. For other assets, a wireless fuel sensor may reduce installation time and avoid additional cabling. The correct choice depends on the tank construction, deployment scale, maintenance model, and required reporting precision. The telematics device also needs enough input capability and firmware flexibility to support the intended logic. GPS location, ignition detection, digital inputs, CANBUS data where available, and configurable event rules all affect the quality of the final solution. A system that cannot connect fuel events to vehicle state will provide less useful evidence. For B2B providers, platform integration is equally important. Device data should be available through the fleet management environment used by dispatchers and customers, with event definitions that can be adapted by market, vehicle class, and operating policy. ERM Telematics supports this kind of modular deployment model through connected hardware designed for fleet and asset-control applications. Balance prevention with operational practicality The strongest fuel-control policy is rarely the most restrictive one. Requiring every driver to park only at a central depot may reduce risk but can add route miles, delay deliveries, and reduce hours-of-service flexibility. Similarly, setting very aggressive alert thresholds may overwhelm the control team with exceptions. The better approach is targeted control. Apply higher monitoring sensitivity to high-value vehicles, remote routes, recurring theft locations, or overnight stops. Use different rules for long-haul tractors, construction equipment, refrigerated vehicles, and local delivery vans. Review alert outcomes regularly, then refine thresholds based on verified events rather than assumptions. Driver communication also matters. Drivers should understand that fuel monitoring protects the operation and helps resolve disputes with factual data. When an incident occurs, a clear process prevents drivers from being blamed for losses they did not cause and gives managers a consistent basis for investigation. Turn the first event into a stronger fleet control The value of a fuel theft system is not limited to catching a single drain. Each verified event improves the fleet's understanding of exposure, whether that means a vulnerable parking location, an installation issue, an unapproved refueling practice, or a gap in overnight security. Start with a defined set of high-risk vehicles, validate sensor readings under real operating conditions, and establish response ownership before expanding deployment. A properly engineered system makes fuel loss visible when it happens, but its greater value is the operational discipline that follows: better evidence, faster decisions, and fewer opportunities for theft to remain hidden.

A rental vehicle can change hands several times a week, travel far beyond its expected route, and return with damage or fuel discrepancies that no employee witnessed. That operating reality makes telematics for rental fleets more than a vehicle-location tool. It is an operational control layer that gives rental businesses verifiable data between checkout and return. For fleet operators, mobility providers, and telematics service partners, the commercial question is straightforward: can the system reduce loss, shorten turnaround time, and create a better rental experience without adding friction at the counter? The answer depends on device reliability, integration quality, the events being captured, and the workflows built around the data. Why rental fleets require a different telematics strategy A long-term corporate fleet typically has known drivers, predictable routes, and established maintenance cycles. Rental fleets have rotating users, variable trip duration, mixed vehicle classes, and a high volume of check-in and check-out activity. A solution designed only for periodic fleet reporting will not provide enough control. Rental operations need real-time visibility at the moments where cost and risk increase: when a vehicle leaves an approved service area, when it is not returned on time, when fuel falls sharply, when a collision-level impact occurs, or when a vehicle is moved after hours. The most useful platform does not merely collect positions. It turns exceptions into actions for branch teams, call centers, security personnel, and maintenance staff. This is also why installation method matters. A hardwired unit may be appropriate for a large, permanent fleet where deep vehicle data and tamper resistance are priorities. A plug-and-play device can be better for rapid deployment, pilot programs, or vehicles that rotate between locations. The right choice depends on the rental model, vehicle warranty requirements, expected contract life, and the level of CANBUS data required. Telematics for rental fleets: the operating use cases Faster check-out, check-in, and vehicle recovery At pickup, the system can confirm that a vehicle is present, connected, and at an expected fuel or battery level. At return, current mileage, trip distance, ignition status, location, and diagnostic information create a factual record that supports inspection and billing workflows. When a customer fails to return a vehicle, location history and live tracking reduce the time spent making calls and searching manually. Geofences can notify the operator when a vehicle crosses a border, enters a restricted area, reaches a port, or leaves a defined operating zone. These alerts need thoughtful configuration. A geofence that is too broad provides little value; one that is too narrow can flood teams with exceptions that do not require intervention. For high-risk cases, recovery performance depends on more than GPS accuracy. The installed device must maintain reliable cellular connectivity, continue recording relevant events during signal interruptions, and resist casual tampering. In some markets, an approved immobilization workflow may add another control point. It should only be used with clear legal review, customer terms, and safeguards that prevent activation while the vehicle is in motion. Fuel, charging, and mileage accountability Fuel disputes remain a familiar cost center for traditional rental fleets. Telematics can compare reported fuel level, mileage, refueling activity, and consumption trends against the condition recorded at dispatch. Where vehicle data is available through CANBUS, operators can access a more detailed picture of fuel level, odometer values, warning indicators, and engine status than GPS-only tracking can provide. The same principle applies to electric rentals. State of charge, charging events, driving range indicators, and battery-related alerts can help staff prepare vehicles before the next reservation. An EV fleet should not be managed as if it were simply a gasoline fleet with a different fuel gauge. Charging availability, dwell time, battery health data, and charging behavior affect vehicle readiness and customer satisfaction. Data should support fair decisions, not automatic assumptions. Fuel level can vary with terrain, vehicle angle, and sensor characteristics. Charging data can be affected by station connectivity. A well-designed process uses telematics as evidence alongside inspection records and customer communication. Damage response and safer vehicle use Harsh braking, high-speed operation, sharp cornering, crash-level impacts, and towing movement are relevant events in rental operations. They can help identify vehicles requiring inspection before the next rental, support incident reconstruction, and improve response time after a serious event. Event recording is particularly valuable when paired with configurable thresholds and, where appropriate, video evidence. A threshold that is appropriate for a compact passenger car may not be appropriate for a cargo van, pickup, motorcycle, or specialty vehicle. Device configuration needs to reflect vehicle type and rental use case rather than applying one rule set across the entire fleet. There is a commercial balance to maintain. Monitoring should support safety, asset protection, and contractual compliance without creating an unnecessarily intrusive customer experience. Rental businesses must establish transparent data policies, retention periods, consent practices, and access controls that align with applicable privacy requirements. Maintenance readiness and asset utilization A vehicle that appears available in the booking system but has a warning light, low battery charge, overdue service interval, or unresolved impact event is not truly ready for rental. Telematics helps operations teams identify these exceptions before a customer reaches the counter. Mileage accumulation, engine hours, diagnostic trouble codes, and maintenance triggers can inform preventive service planning. For partners integrating with rental management platforms, this data can also improve fleet allocation. Vehicles can be moved based on actual utilization, local demand, condition, and return patterns instead of scheduled assumptions alone. The financial value often comes from small operational gains repeated across hundreds or thousands of vehicles: fewer manual checks, fewer missed services, quicker recovery from exceptions, and less idle inventory. Measuring those gains requires a baseline. Before deployment, operators should define current recovery time, turnaround time, fuel loss, damage-related downtime, and utilization by branch. What to evaluate in a rental telematics deployment A rental fleet is not a place for devices selected on price alone. The lowest unit cost can become expensive if installation failures, inconsistent data, unsupported networks, or weak integration create operational workarounds. Start with hardware fit. The device should support the vehicle power environment, expected temperature range, local cellular networks, and installation approach. For concealed installations, size, antenna design, backup battery options, and tamper alerts are practical considerations. For mixed fleets, broad protocol support and adaptable wiring options reduce complexity. Then evaluate the data path. A rental operator or service provider needs secure access to location, trips, events, diagnostics, and device health through an API or a platform that can integrate with reservation, billing, CRM, maintenance, and security systems. Data that remains isolated in a separate portal may still help investigations, but it delivers less value to daily operations. Scalability deserves equal attention. A deployment that works for 50 vehicles must also support thousands of units across branches, states, and countries. Consider SIM management, firmware update procedures, device provisioning, technical support coverage, and how configuration templates will be maintained across vehicle classes. Global deployments should also account for regional network availability and local regulatory conditions. Finally, test the operational workflow, not just the device. Run a controlled pilot with actual branch users. Validate that alerts reach the right team, recovery procedures are documented, inspection teams understand event records, and vehicle data matches real-world conditions. A pilot should produce clear decisions about device configuration, integration requirements, and deployment economics. Building a solution that partners can scale For telematics service providers and mobility solution companies, rental is an opportunity to deliver a specialized service rather than generic tracking. The strongest offering combines field-proven hardware, vehicle-data capability, flexible integrations, and a defined operating model for theft, late return, fuel, charging, and maintenance exceptions. Customization can be decisive. A car-sharing operation may prioritize remote access and short-trip visibility. A commercial van rental provider may require driver behavior, cargo-area protection, and extensive diagnostic data. A premium rental company may focus on cross-border alerts, theft recovery, and discreet installation. One device profile rarely fits all three. ERM Telematics supports this model with configurable connected-vehicle hardware, CANBUS expertise, and deployment options designed for partners building rental and mobility services across different markets. The engineering objective is not simply to report where a vehicle has been. It is to provide dependable field data that enables a faster, more controlled response while the vehicle is still in service. The most effective rental telematics program is usually not the one with the longest feature list. It is the one that gives each team a clear next action when a vehicle is late, at risk, not ready, or operating outside the terms of its rental.

A disputed collision can become an operations problem within minutes. Without clear footage, a fleet may face avoidable claims costs, vehicle downtime, driver frustration, and hours of manual investigation. A fleet dash camera review should therefore assess more than image quality. The right system must produce usable evidence, identify meaningful driving events, operate reliably in commercial vehicles, and fit the wider telematics environment. For fleet operators and solution providers, the objective is not simply to place a camera on every windshield. It is to build a dependable video evidence capability that supports safety, accountability, and faster decisions at scale. What a Fleet Dash Camera Review Should Measure Consumer camera specifications can look impressive while delivering limited operational value. A commercial review should begin with the conditions in which footage will actually be used: night driving, glare, rain, vibration, sudden impacts, long operating hours, and inconsistent network coverage. Video resolution matters, but it is only one part of evidence quality. A higher-resolution camera may help identify a license plate or road sign, yet poor low-light performance, narrow dynamic range, or an unsuitable lens angle can still make critical details unreadable. Review daytime and nighttime samples from the same vehicle class and route type. Look closely at exposure when a vehicle leaves a dark area into direct sunlight, approaches headlights at night, or travels through tunnels. The field of view also requires a practical trade-off. A wider lens captures more of the road environment but can distort objects near the edge of the frame. A narrower view may provide better detail ahead but miss events developing beside the vehicle. For urban delivery fleets, side activity and vulnerable road users may justify broader coverage. For long-haul operations, forward visibility and distance detail may carry more weight. Time, date, location, and speed data must be accurately associated with the recording. If video and telematics data cannot be correlated confidently, the fleet still has a recording but not necessarily defensible event evidence. Select the Camera Architecture for the Risk Profile A forward-facing camera is often the baseline for collision reconstruction, false-claim defense, and road-risk monitoring. It can show traffic conditions, lane position, following distance, and the sequence leading to a harsh event. For many fleets, this configuration provides the strongest starting return because it addresses the most common liability and safety use cases. Dual-facing systems add a driver-facing view. They can support coaching around distraction, fatigue indicators, seat belt use, and mobile-device handling, depending on the system's analytics and operating policies. However, inward-facing video changes the privacy conversation. Fleets need a documented purpose, clear driver communication, access controls, retention rules, and local legal review before deployment. Multi-channel systems may be appropriate for school transportation, transit, waste collection, construction, high-value cargo, and specialized vehicles. Additional views can cover cargo areas, side blind spots, rear access points, or work zones. The benefit is broader situational evidence. The cost is greater installation complexity, higher storage demand, and more video for teams to manage. The best configuration depends on the loss exposure being addressed. A van fleet focused on third-party claims may prioritize forward video and event metadata. A service fleet with repeated backing incidents may need rear coverage. A security-sensitive operation may require video tied to door activity, unauthorized movement alerts, or asset tracking. Event Detection, Storage, and Connectivity A camera must capture the right moments without creating a review queue full of irrelevant clips. This is where event logic becomes central to a fleet dash camera review. Common triggers include impact, harsh braking, rapid acceleration, sharp cornering, speeding, panic button activation, and geofence events. Sensitivity settings should not be treated as permanent defaults. A calibration that works for passenger cars can generate excessive alerts on a box truck, a vehicle operating on rough roads, or a utility fleet traveling off-pavement. During a pilot, compare triggered events against actual driving conditions and adjust thresholds by vehicle type and duty cycle. Pre-event and post-event recording are equally important. A clip that begins only at the point of impact may fail to show who created the risk. Fleets should verify how much footage is retained before and after a trigger, how clips are protected from overwrite, and whether manual recording is available when a driver observes a developing incident. Local storage protects footage when cellular coverage is unavailable. Cloud upload enables remote review and faster response, but it also introduces data-plan costs and upload prioritization decisions. A well-designed deployment can upload short, high-priority event clips immediately while retaining continuous recording locally for later retrieval. Full-time cloud streaming may be justified for a limited set of high-risk applications, but it is rarely the most economical default for every vehicle. Installation Quality Is a System Requirement Camera performance depends on installation discipline. A poorly positioned lens can capture glare from the dashboard, lose a critical traffic lane, or be obstructed by mirrors and windshield-mounted equipment. In commercial fleets, installers must also account for vehicle vibration, heat, cold, dust, driver access, and serviceability. Hardwired power is generally preferable to removable power connections for permanent fleet use. It reduces accidental disconnection and supports controlled ignition behavior. The installation should also address low-voltage protection, cable routing, tamper resistance, and safe attachment methods that fit the vehicle model. For mixed fleets, standardization is valuable but should not become rigidity. A light-duty van, heavy truck, bus, and off-road machine may need different brackets, harnesses, protection ratings, and camera placements. Fleet partners should ask whether the provider can support these variations without turning each installation into a custom field project. Integration Determines Operational Value Video is more useful when it is part of the same operational workflow as vehicle location, driver identification, diagnostic information, and dispatch activity. A camera platform that operates in isolation often forces supervisors to search across separate systems after an event. Evaluate how the solution associates footage with GPS tracks, ignition status, mileage, geofences, and vehicle events. Where available, CANBUS data can add context such as speed, braking status, turn-signal activity, or warning conditions. The value is not merely more data. It is a clearer explanation of what happened and what action should follow. For telematics service providers and fleet technology partners, integration options deserve early technical review. Confirm data formats, API availability, event payloads, clip retrieval methods, user permissions, and support for existing fleet platforms. ERM Telematics approaches event recording as part of a broader connected-vehicle architecture, where camera evidence can complement tracking, diagnostics, and operational alerts. Data governance should be assessed with the same seriousness as hardware. Define who can view live or recorded video, how access is logged, how long footage is retained, and how recordings are handled after an incident. A system that protects drivers and the business must also prevent inappropriate internal access. Compare Total Deployment Cost, Not Device Price The camera purchase price is visible. The recurring and operational costs are often where fleet economics change. Build the comparison around hardware, installation labor, cellular usage, cloud storage, platform licenses, replacement units, support effort, and time spent reviewing alerts. A lower-cost device can become expensive if it produces unreliable footage, requires frequent physical retrieval, or creates an unmanageable volume of false events. Conversely, premium analytics may not justify their cost for a fleet that only needs collision evidence and basic coaching. The right specification follows the business case, not the longest feature list. When estimating return, use actual fleet loss categories. These may include disputed claims, preventable collisions, unsafe driving behavior, unauthorized vehicle use, cargo incidents, and time spent on investigations. A credible model should also account for the fact that not every captured event produces direct savings. The system earns value when its evidence changes an outcome or prevents a repeat event. Run a Controlled Fleet Pilot Before a wide rollout, test the selected camera system across representative vehicles, routes, drivers, and operating conditions. A pilot should last long enough to capture normal operations, poor weather where relevant, parking activity, nighttime driving, and real network gaps. Use a defined scorecard that measures the factors that matter to the operation: Footage clarity during day, night, glare, and weather events Accuracy and relevance of triggered video events Upload timing, retrieval speed, and cellular data consumption Installation time, vehicle fitment, and hardware stability Integration quality with the existing telematics and fleet workflow Include safety leaders, operations managers, IT teams, legal stakeholders, and a driver representative in the review. Each group sees a different risk. Operations may focus on retrieval speed, while drivers may identify privacy or usability concerns that could affect adoption. Resolving these issues during a pilot is less costly than correcting them after hundreds or thousands of units are deployed. A strong camera deployment does not ask a fleet to choose between safety, operational control, and driver fairness. It creates a consistent evidence process: capture the event, add the vehicle context, review it quickly, and apply the result to claims handling, coaching, or policy improvement. That is the standard worth using when selecting a fleet video system.

CAN INTERFACE ERM’s CANbus Interface technology is designed for advanced vehicle diagnostic applications. It offers sophisticated event based tools to monitor, enquire, analyze and transmit information about the vehicle’s systems and sensors in real-time. The multi-protocol supported CAN Interface, enables a deep understanding of the numerous scenarios in a vehicle’s day to day activities. ERM’s CAN Interface technology offer two main tools: Rule Engine - enables the fleet manager to set multi-dimensional CAN parameters rules, on which violation will trigger an event and send the relevant information in real-time to the fleet manager server resulting in considerably better controlling of the fleet’s operation and performances. Multi-Dimensional Histograms - enable deep analysis of particular situations during the vehicle's life. Featured Solutions CANbus Read Explore ECU Alerts Explore OBD Explore Other Technologies VEHICLE LOCATION Read more WIRELESS CONNECT Read more CAN INTERFACE Read more SECURITY & CYBER Read more FUEL MONITORING Read more SEGMENT Read more DRIVING BEHAVIOR Read more

eEye ADAS DMS AI-Powered Camera eCom Identification Tag/Remote Control eCom Tag is a specially designed, cost-effective, coin size, two-way communication active Tag and Proximity Remote control used in various applications such as driver identification, remote control and tagging. eCom Tag uses ERM’s eCom Technology for complex Tag-Receiver applications and is using Standard Short-Range Low Energy wireless communication protocols to communicate with ERM’s relevant devices. The device comes with variety of options for cellular communication technology to choose from: 2G (GPRS), 3G (UMTS), 4G (LTE - with selected band width and CAT implementations: CAT-M1, CAT1, CAT4) modules Wi-Fi hot spot with the ability to support up to 8 concurrent users. In addition, as an option, the technology can be configured to act as a client instead of host, in order to connect with third-party Wi-Fi hotspot. The device comes with two way standard short range RF communication module. Which can be used to transmit data between the device and a mobile phone/tablet or read data from variety of external sensors and tags. 3D high sensitivity accelerometer and gyro supported with the Safety technology for Driving Behavior analysis and BlackBox feature. The technology can identify 20 maneuver types in 3 levels. The functionality offers event based driving behavior alerts. The device comes with the CAN Engine technology providing CANBUS interface to various protocols such as CANBUS, OBD2, FMSJ1939, up to 12 parameters including Odometer Used for drivers’ identification and management, and supports Black and White Lists. The ID variant includes two proximity remote controls (eCom Tags) and support various identification types. Additional Tags can be added at any time. ERM’s patented RF technology (eConnect) is designed to allow tracking of connectivity jammed vehicles (cellular and GPS), by enabling alternative communication between vehicles. The Variant offers 433Mhz or 915Mhz frequency, per request. External GPS and cellular antennas plugs. used to enhance The communication capability of vehicles in Which The communication of The internal antennas is limited, such as in armored vehicles Voice communication support with the driver includes an external speaker and dedicated microphone. This variant kit offers an option to use ERM's keypad or a push button for quick dialing and manual call answer/disconnect. Product Details Explore comprehensive specifications, features, and implementation capabilities Download Product Brochure (PDF) What's Included in the Package StarLink Device Wiring Harness Proximity Keyfob Quick Start Guide Features Implementation Areas Technical Specifications Small coin size active tag with changeable colored silicone cover Two-Way communication Panic button / one-click arm / disarm functionality Internal movement sensor Battery operation: 12-18 months Up to 20M radius reception distance Cargo Safety Monitors cargo movement and alerts for security risks. Self-Powered Asset Tracks delivery assets using self-powered tracking devices. Asset Tracking & Monitoring Tracks the location and status of valuable mobile assets. Communication Two-Way Standard Short Range 2.4Ghz wireless low energy. Embedded antenna Sensors Movement sensor Battery Intenral, 3.2v 240mA Dimensions 3.4cm x 4.1cm x 1.5cm for 433Mhz variant4.0cm x 4.9cm x 1.4cm for 2.4Ghz variant Explore More Solutions Related Products Discover our complete range of tracking and telematics solutions StarLINK Tracker Modular Tracking Device More eEye AI Powered ADAS & DMS Camera More StarLINK One Motorcycle Tracking Solutions More IoTLINK Pack Wireless IoT Tracker/Transmitter More View All Products Implementation Industries Trusted across diverse industries for reliable tracking and fleet management Fleet & Transportation Construction & Heavy Equipment Industrial & Manufacturing Agriculture Public Safety Cold Chain & Sensitive Cargo Energy, Utilities & Mining Asset Tracking & Security Articles & Case Studies Real-world success stories from customers who trust StarLink for their tracking needs Case Study: StarLINK Tracker – Optimizing Fleet Efficiency with Precision Tracking Automatically recognizes the rider's proximity keyfob to enable seamless arming and disarming. Read full case study ERM present Anti-Theft Vehicle Tracking Solution StarLink eConnect improves stolen vehicle recovery rates with unique jamming mitigation techniques... Read full case study Case Study: StarLINK Tracker – Optimizing Fleet Efficiency with Precision Tracking Automatically recognizes the rider's proximity keyfob to enable seamless arming and disarming. Read full case study

Connected Car ERM offers a solution for connected cars. By using various communication methods together, the Connected Car solution enables the vehicle to communicate wirelessly or wired with various third-party devices such as tablets, smart phones, cameras and sensors. The connected car solution also provides the vehicles the ability to communicate and be controlled and monitored remotely by a cloud application. ERM's connected car solution enables any type of vehicle to: Provide wireless communication to various wireless sensors Provide wide band connectivity for multimedia streaming Provide vehicle to vehicle communication for various applications Provide automated safety notifications and security alerts Control internal mechanisms such as: doors, windows, ignition, on-dashboard indicators etc. Recommended Products Tracking Devices Starlink Tracker Explore Additional Solutions Jamming Explore Logistics Explore Other Technologies DRIVING BEHAVIOR Read More WIRELESS CONNECT Read More VEHICLE LOCATION Read More SECURITY AND CYBER Read More CAN INTERFACE Read More SEGMENT Read More FUEL MONITORING Read More