The TeamViewer IoT Starter Kit contains a built-in GPS receiver.
What you will need
Make sure that you have prepared the following points:
- Your TeamViewer credentials.
- Make sure that the WiFi antenna is connected to the edge device (see Setup the Starter Kit).
- The edge device is set up with a TeamViewer IoT Agent and TeamViewer Edge Management is enabled.
- Access the Edge Device via Remote Terminal.
- Access the edge device remotely (Access the Edge Device via Remote Terminal).
- Install the needed dependencies for python. In the terminal type in the following commands and press return:
sudo apt-get update
sudo apt-get install -y python3-pip
- Download the Starter Kit configuration package. In the terminal type in the following commands and press return:
wget -q https://download.teamviewer-iot.com/teamviewer-iot-kit/v2.0.1/teamviewer_iot_kit-2.0.1-py3-none-any.whl
sudo -H pip3 install teamviewer_iot_kit-2.0.1-py3-none-any.whl
- Configure the location receiver. In the terminal type in the following command and press return.
sudo teamviewer-iot-kit -e location_receiver
- To log in to the IoT Management Console, open https://teamviewer-iot.com and use your TeamViewer account credentials.
- Check that you enabled the GPS. From the left menu select Inventory and on the right side from the drop-down-menu select Metrics.
After the GPS receiver has been enabled you can visualize its data with a widget.
- The GPS data is NMEA 0183 formatted and packed into a JSON object called NMEA 0183: TPV. In the “Metrics” tab you will find the data in the raw format as well as dedicated metrics for each parameter.
- The location receiver provides the NMEA 0183: SKY object as well which is not presented in the Starter Kit. From that object, two metrics are being calculated and presented separately with the names In View and Used.
The table represents all the available parameters/metrics and their descriptions of the location receiver.
|Time||No||string||Time/date stamp in ISO8601 format, UTC. May have a fractional part of up to .001sec precision. May be absent if the mode is not 2 or 3.|
|NMEA 0183: TPV||Yes||string||NMEA 0183 formatted JSON data of the TPV class.|
|Mode||Yes||numeric||NMEA mode: %d, 0=no mode value yet seen, 1=no fix, 2=2D, 3=3D.|
|Estimated timestamp error||No||numeric||Estimated timestamp error in seconds. Present if time is present.|
|Latitude||No||numeric||Latitude in degrees: +/- signifies North/South. Present when the mode is 2 or 3.|
|Estimated latitude error||No||numeric||Latitude error estimate in meters. Present if the mode is 2 or 3 and DOPs can be calculated from the satellite view.|
|Longitude||No||numeric||Longitude in degrees: +/- signifies East/West. Present when the mode is 2 or 3.|
|Estimated longitude error||No||numeric||Longitude error estimate in meters. Present if the mode is 2D or 3D and DOPs can be calculated from the satellite view.|
|Altitude||No||numeric||Altitude in meters. Present if the mode is 3.|
|Estimated vertical error||No||numeric||Estimated vertical error in meters. Present if the mode is 3 and DOPs can be calculated from the satellite view.|
|Speed||No||numeric||Speed over ground, meters per second.|
|Estimated speed error||No||numeric||Estimated speed error in meters per second. Present for consecutive 2D or 3D fixes.|
|Climb||No||numeric||Climb (positive) or sink (negative) rate, meters per second.|
|Estimated vertical error||No||numeric||Estimated climb error in meters per second. Present if consecutive 3D fixes.|
|Track||No||numeric||Course over ground, degrees from true north.|
|In View||No||numeric||Number of satellites which are in view of the location receiver.|
|Used||No||numeric||Number of satellites to which the location receiver is locked.|