You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
The position update frequency is once every ten (10) seconds per cart
There are currently two carts being tracked on USF. One owned by CUTR and one owned by USF IT. Information provided in the file I sent was solely for CUTR’s cart but I can provide information for all carts. .... Generally, every cart/mote has a unique Device Address identifier (001a442e – plus leading zeros in the CUTR cart’s case), which could be used as UID for mapping, as these IDs are hardcoded into the mote directly. If you design your system around using the Dev Addr as UID, we could provide you with the IDs as they come online...
Steps to reproduce:
Look for USF Golf Cart info on the map Layer
Expected behavior:
Show either real-time or historical golf cart info
Observed behavior:
There is no USF Golf Cart info
The text was updated successfully, but these errors were encountered:
Summary:
We have a MQTT feed for USF Golf Cart info from OCCAM that we could somehow integrate into the Layer.
Here's a Word Doc with some info (minus credentials and endpoint info):
CUTR Golf Cart Tracker Access Information - public.docx
EDIT April 3, 2018 - More info on the feed:
Steps to reproduce:
Look for USF Golf Cart info on the map Layer
Expected behavior:
Show either real-time or historical golf cart info
Observed behavior:
There is no USF Golf Cart info
The text was updated successfully, but these errors were encountered: