Dummy Telemetry Test Script
Note: This guide assumes that you have installed the GCS application, have it set up correctly, and know how to run it. If you haven’t done so, please refer to the Installation Guide and Running GCS Guide.
Purpose
Section titled “Purpose”The purpose of this script is to confirm that the communication between the GCS Integration Library and the GCS Application is working. The script will randomly generate dummy telemetry data and send it into the vehicle telemetry queues.
Pre-Script Checks
Section titled “Pre-Script Checks”- Under the User Interface Repository (GCS application), go to the
.envfile. - Ensure
DUMMY_DATA_ENABLED = falseandTEST_PUBLISHER = false. This will disable the GCS-side testing so it can recieve the dummy test data from the GCS Integration Library Repository.
Running the script
Section titled “Running the script”- Clone the GCS Integration Library Repository
- Go to
xbee-tel-update-testingbranch
git checkout xbee-tel-update-testing- Install serial library. This is not needed for the testing script, but is required for the repository to work with the Xbees.
pip install serial- Change directory to Communication folder
cd Communication- Run the test script
python3 xbee_tag_gcs.pyCheck Results
Section titled “Check Results”-
Run the GCS application if you want to see results on the UI. Otherwise, ensure RabbitMQ container is running.
-
Open docker desktop and click on RabbitMQ’s port link.
-
Log in with
username: adminpassword: admin. -
You should see each that vehicles’s telemetry queue is receiving the dummy telemetry data as shown below. If you ran the GCS application, the data should be displayed on the UI.