Q: How can I get notifications on my assets’ activity?
A: We recommend using ZAlerts, which can be configured to track and report asset activity. ZAlerts cause an alert window to pop up in Ground Traffic Control along with an email sent to a configurable list of contacts.
Q: Who do I contact if I need access to Ground Traffic Control?
A: Only users with Admin rights can add new users to Ground Traffic Control. Contact your administrator to assist you in creating a Ground Traffic Control user profile.
Q: Can multiple users log in to Ground Traffic Control with the same email/password combination?
A: Yes, but having more than one person use the same combination to log in introduces security risks to your Ground Traffic Control account.
Q: Can I integrate Ground Traffic Control into my company’s active directory?
A: Not at this time.
Q: Is it a problem if the API user in my account does not have a unique email associated to it?
Q: How do I use expiry for oil changes, maintenance, license renewals, etc.?
- Set up the kinds of expiry types you want to use in Manage > Asset Expiry (see Manage Asset Expiry Types help)
- Assign the expiry to assets using the Expiry button in Manage > Assets (see Assets help)
- View the expiry report under Assets > Asset Expiry Report (see Asset Expiry Report help)
Q: How do I use asset attributes?
A: Asset attributes allow you to fine-tune your reports by various asset characteristics (type of vehicle, year, region, etc.). The Admin Attributes help page will guide you through the details, but broadly:
- Define the attributes you want to use in Manage > Attributes.
- Apply the attributes to your assets in Manage > Asset Attributes.
- (Optional) Create filters for reports in Manage > Attribute Filters.
Q: Why does the Trip Report not match up with other reports such as the Fuel Path?
A: The reason for the discrepancy is that while the Fuel Path report provides the distance traveled and fuel used for the data points found between the start and end of the timeframe specified, the Trip Report operates by comparing the data gathered at the end of each trip (a trip is engine on to engine off).
This has two major implications:
- If the vehicle is currently moving, the data since the engine was turned on will not appear in the Trip Report until the engine is turned off.
- Because the Trip Report compares the ending values for odometer and fuel counter to derive its per-trip mileage and fuel use, it needs two trips to provide that information: the ending values for the trip being calculated and the trip previous. As such, it does not calculate the data for the first trip in the timeframe specified. This can be fixed by moving the start of the timeframe on the report back far enough to include the most recent trip prior to the actual timeframe being reviewed.
In general, we recommend using the Fuel Path when looking at fuel for the current day or a specific short time period, and use the Trip Report when retrieving data for a broad range of time, such as the past month.
Path Data FAQs
What are Cold Starts?
Cold starts are an indication of a GPS Unit rebooting due to a loss of constant or ground power. Cold starts in path data may also appear as incorrect mileage (usually too low), engine hours, or idle hours in Ground Traffic Control data. To check cold starts, run Path Data for the selected asset and, on the “events” tab, choose “cold start.”
Note: Cold starts in path data will always occur when a GPS Unit first receives constant power. GPS Units should never cold start while in motion. If they do, it is usually an indication of a loose constant power or ground cable.
Note: Zonar requires “clean” engine power off events. Loss of constant power or ground during a trip may possibly lead to incomplete path data, erroneous mileage, engine hours, and/or idle data in Ground Traffic Control.
Normal cold starts occur:
- After a new installation
- With a replacement GPS Unit
- During a Master Kill switch operation
- Following an OTA (Over The Air) firmware update
Abnormal cold starts occur:
- With an improper 4-pin power cable install:
- Poor or loose ground (black lead)
- Poor or loose constant power connection (red lead)
- Constant power supply isn’t truly constant
- 4-pin power connector pins are damaged and are not making a good consistent connection
- Intentional disconnection of the 4-pin power cabling, fuses, or connectors (the cold start will occur on the re-connection)
- With data type cables (9-pin, Backbone, Light Duty):
- Broken, loose, misconnected, or intermittent constant power lead
- Broken, loose, misconnected, or intermittent ground lead
- Constant power supply isn’t truly constant
- Intentional disconnection of the data/power cabling, fuses, or connectors (the cold start will occur on the re-connection)
Why is my path data in straight lines instead of following the road?
- GPS power/data cables were not connected in proper sequence.
The 4-pin power connector at the back of the GPS Unit should be the first cable disconnected and the last cable reconnected. Also, the Zonar Light Duty cable (OBDII) connector must only be connected to the vehicle when the engine is running.
Solution: With the engine off, disconnect the 4-pin power cable at the back of the GPS Unit. Wait at least 30 seconds, then reconnect the 4-pin connector. Start the engine and ensure that the Status-Cellular/GSM-GPS LEDs all turn solid in color.
For Light Duty (OBDII) cables: in addition to the above steps, start the engine, remove the OBDII connector from the vehicle, and wait at least 30 seconds before reconnecting the OBDII connector.
- Faulty switched power/white lead (especially likely if power-of or power-on events mark the endpoints of the straight line).
Solution: Repair the switched power/white wire lead.
Note: Looking for power-on or power-off events at a speed greater than 0 in the path report CSV export is one method to find this condition.
- Faulty constant power/red lead (especially likely if a cold start event marks the end of this straight line).
Solution: Repair the constant power/red lead or ground lead.
Note: Looking for cold start events at a speed greater than 0 in the path report CSV export is one method to find this condition, especially when trying to sort “good” from “bad” cold starts at sites that use Master Kill switches.
- The GPS Unit’s antenna installation is not optimized (clear, unobstructed view of the sky), or the GPS Unit’s signal is degraded (e.g. pinched, frayed, degraded GPS Unit antenna cable).
Solution: Optimize the GPS Unit’s antenna installation.
- There is a mismatch between the equipment and the GPS Unit’s antenna.
Solution: Configure the unit properly.
The Path data shows frequent Power Off/Power On events.
The cause of frequently cycling power-on or power-off events in the path report data typically depends on the vehicle’s cabling.
- 4-Pin Power Cable:This issue may occur when the switched/white power lead is connected to the vehicle’s alternator or other “pulsing” energy source. If this is the case, move the switched/white power lead away from the vehicle’s alternator to a different true-ignition power source on the vehicle.
- Light Duty (OBDII) Cable: The firmware likely needs to be updated. Contact Zonar (877-843-3847) for further assistance.
- JBus/ECM Cabling:This issue may be caused by “noise” on the vehicle’s network. Contact Zonar (877-843-3847) for further assistance.