Getting Started with your Developer’s Kit
You should have the following components inside your Developer’s Kit box:
- 1 x Horizon GPS board
- 1 x Horizon ARTIC R2 board
- 1 x information card with your Argos ID (you’ll need this to register for airtime)
- 1 x micro USB cable
- 1 x picoblade cable assembly (to connect the two boards together)
You’ll need to purchase an antenna (we’ve suggested a good one) and provide power to the board if you want to take your tag outdoors, but before you do that you can start programming your tag straight out of the box.
The complete Horizon ARTIC R2 Developer’s technical manual should also be downloaded as a PDF so you’re ready to go.
2. Installing Tools
o talk to your tag you’ll need to install the Horizon Python tools.
We recommend using Ubuntu 20.04 LTS as the Linux operating system.
If you’re using a Windows PC then you can use Oracle’s VirtualBox to setup a virtual machine and access your tag that way. Once you have installed VirtualBox on a PC be sure to setup USB to it passes through from the host. Here’s a useful guide showing you how.
If using Windows 10 then you should also install the Windows 10 Horizon Driver to ensure that Windows can detect the tag when connected over USB.
If you get stuck installing VirtualBox then also take a look at our more detailed VirtualBox setup guide for help.
Once you have setup VirtualBox / Linux and are ready to install the tools enter the following commands into Terminal. Tools and firmware are cloned from our Github repository so you should inherit the latest release.
If you run into any problems then be sure to look at our troubleshooting page too.
The tools are installed as tracker_config and can be called from the command line by running sudo tracker_config
To confirm that the tools installed successfully you can run the following command. It should return the version of the tools you have installed, i.e Version: 2.0.0
3. Connecting your tag
Connect your tag using the provided micro USB cable.
You should see it light up and two LEDs will be active (power and activity).
We can now call the tracker_config tool and provide it with arguments to talk to your tag. Let’s send a status request first and see what we get back. Enter the following command:
For a full list of commands that you can use type the following;
4. Configuring your tag
Issue the following command to configure the Horizon board to use the ARTIC R2 firmware;
Next, to configure your tag and start using the Argos / Kineis satellite module we can download the tag’s configuration file and made some edits.
The tag uses a JSON configuration file so it’s nice and easy to make changes and apply them.
Let’s start by downloading the default configuration installed on your tag from the factory.
To do this run the following command;
Note – you call the file downloaded anything you like, but in this instance we have just called it default.json
You should now have the configuration file default.json on your computer.
Open that file up in a text viewer and you’ll be able to see what’s inside. You can also open it from terminal by typing;
We can now see the configuration of the tag. For information on what each configuration value does (and means) a complete list is available on Arribada’s Horizon github repository.
Your tag straight out of the box has been configured ready to go with the following configuration:
- Wake every 30 minutes
- Take a maximum of 3 GPS fixes
- Transmit the GPS location and battery voltage via Argos / Kineis
- Aquire the time from the GPS fix
- Log everything locally to the tag
You’ll notice that “iot“, “enable” is set to “false“. This is the only value you need to change to start using the Argos / Kineis functionality. It is disabled by default so we need to change this value and upload the new configuration file to the tag.
To do this manually change “false” to “true” and save the file (in nano you would press CTRL+ O and then press enter to save the file.
Once saved, let’s upload it to the tag by running the following command;
Your tag is now ready to go. You’ll need to provide power and attach an antenna to the satellite board, also not forgetting to register an account with CLS so you can see your data in the ArgosWeb dashboard.
Remember, your Argos ID is printed on the card inside your Developer’s Kit box.
Additional advice, including how to download and decode data received in the ArgosWeb dashboard to view GPS locations / battery status etc, is available in our follow on complete deployment guide.
We’re all in this together