This is the multi-page printable view of this section. Click here to print.
This the manual for the Ham2K Portable Logger which is a mobile application currently available through the Google and Apple environments, as well as on Github as PoLo is an Open Source project.
The menu will take you to the various sections on installation, configuration, and tips and tricks. If you are unable to find the answer you need then the Community section will guide to places where you can get further help.
PoLo is currently available for Android and iOS devices. You can install it from the Google Play Store or Apple TestFlight.
PoLo is available on the Google Play Store. You can install it by clicking the badge below:
PoLo is not yet on the iOS AppStore, but it is available through Apple’s TestFlight. You can install it by clicking the badge below:
You will have to first install TestFlight, and then click the badge again, or use code TjRq5t5Y in the TestFlight app.
PoLo is not available for Windows devices at this time, but we’re working on it.
In the meantime, some users have reported success running PoLo on Windows using Android emulators like BlueStacks.
The iPad version of PoLo can be installed on Macs with Apple Silicon (M1 processors and newer) using the same AppStore link above.
A version for older Macs with Intel processors might be available in the future.
In PoLo, an Operation is a collection of contacts made during a specific event or activity. For example, you might create an Operation for a park activation, a contest, or a special event station.
To get started, add a new operation and select it, then select any specific activations or special activities associated with it.
Once you’re happy with the operation settings, you can start logging contacts in the “QSOs” tab. But first, remember to check the band and mode and adjust them as needed.
You can log a QSO by entering the callsign of the station you contacted, then pressing the [Send] key or button on the screen.
Keep logging contacts, and once you’re done go to the “Operation” tab and select “Export Log Files” to generate ADIF files that you can use to submit your activation.
PoLo is currently supports the following “On The Air” types of operations. More will be added over time and if you have a request please ask on the Discord Server.
A single operation can involve multiple activities and PoLo will provide all the fields required to log the contacts for each activity, as well as generate separate ADIF and Cabrillo files as needed.
Official Site • Data file downloaded to device. Supports search of nearby references, or by name or code; self-spotting; show spots.
PoLo can be used to activate multiple parks and will generate a separate ADIF file for each park reference.
PoLo accepts multiple park references in a single QSO (use a comma or space in the field), and will generate a separate QSO for each park reference in the resulting ADIF file.
Official Site • Data file downloaded on device. Supports search of nearby references, or by name or code.
Official Site • Data file downloaded on device. Supports search of nearby references, or by name or code; self-spotting.
Official Site • Data file downloaded on device. Supports search of nearby references, or by name or code; self-spotting.
Official Site • Data file downloaded on device.
Official Site • Data file downloaded on device.
Official Site • Data file downloaded on device.
Official Site • Data file downloaded on device. Supports search of nearby references, or by name or code.
Official Site • PoLo enables the logging of satellite contacts; the local satellite list is not expansive, if your choice of satellite is not available please raise it.
If the activity you are interested in is not listed above, you can still add it as a “Custom Activity” as long
as the organizers accept ADIF logs using the SIG_INFO fields. (see the ADIF docs)
When you are in the callsign input field, you can use the following shortcuts, always followed by the [Send] key or button on the screen:
Enter a band or mode to change the current band or mode. For example 20m or CW.
Enter a frequency to change the current frequency (and band). For example 14.070 or 14070.
Enter a power level to change the current power level. For example 5W or 100W.
Enter a new decimal frequency to change just part of the current frequency. For example, if you are on 14.245 and you type .247, the frequency will change to 14.247.
Enter a time or date to change the QSO time. For example 14:30 or 14:30:25 for time, or 05-09 for May 9th.
Enter a time difference to change the QSO time. For example, if you are logging a QSO at 14:30 and you type +15m, the time will change to 14:45. If you type -1h, the time will change to 13:30. You can use h for hours, m for minutes, and s for seconds, as well as d for days and w for weeks.
Enter QRV, QSY, or QRT to self-spot with the respective comment. Enter SPOTME or SPME to self-spot with current frequency and mode but no comments.
Change operators with OPER/ or OP/ followed by the new operator’s callsign.
Enter KONAMI to enable or disable Developer Mode.
In most activation reference fields (POTA, SOTA, etc) you only need to enter letters and number, and PoLo will automatically fill in any dashes and slashes. And in many cases you can skip the prefix too and PoLo will guess it from the callsign.
So for a POTA Park-to-Park contact with, say, LB4FH in NO-2518, you can just enter 2518 and PoLo will fill in the rest.
For SOTA reference VK1/AC-001, all you need is to enter VK1AC001.
Use the [space] key to quickly select the next field in the form. This is especially useful when you are logging a lot of contacts and want to keep your hands on the keyboard.
Also, if the report is just 59, you can leave the field empty.
Some keyboards also support using the [tab] key to move to the next field, but this can be less reliable. We’re working on
expanding this to more keyboards, but iOS and Android make it harder to deal with these keys than desktop operating systems.
You can use commas to enter more than one callsign at a time and PoLo will log them as separate QSOs. This is useful, for example, when you log a POTA Park-to-park contact with multiple operators on the other end.
This also works when editing existing QSOs if you want to duplicate the information for another operator.
Most phone and tablet keyboards make it hard to enter a slash (/) character, which is often needed when logging callsigns like WV3H/VE or VK1AO/P. A period (.) can be used instead and PoLo will convert it to a slash.
Entering your qrz.com credentials in Settings > Accounts > QRZ will enable PoLo to provide details of contacts you make. If you have a qrz.com subscription it will also provide bearing and distance information to your contact.
The PoLo Operations Panel is where you will interact with the package once you’ve set up you operation. Once your frequency and mode have been entered (which may have been picked up from your previous operation) the left pointing (or less than) arrow exapnds the operations panel to show all available interactions. Tapping the Controls (settings) wheel will reveal any that are available, but not set with the operation. This might be useful when a caller from an unexpected award system such as UKBOTA or SiOTA call you. Selecting them from the More Controls section will make them available for use within the Active Controls. Once the selection is complete back out of the Controls section by tapping the Controls wheel.
Tapping an Active Control will provide the appropriate fields for infomation to be entered, eg P2P will enable park details to be entered in addition to the contact details. The Notes control is for per contact information to be added, and the More Control displays all information stored for the QSO.
The Callsign Information Panel can show various pieces of information dependant on your installation and circumstances.
Once QSO details are entered, tapping the up arrow will save them into the operation log. Tapping that QSO or an other within the operation log will bring the details into the Callsign Information Panel where you can change them and save them by tapping the save icon, or delete the QSO with the trash can icon, which will need to be tapped twice before the QSO is lined through in the operation log. Even then it can be recovered by tapping it in the operation log, then then undo arrow, and then the save icon again.
When an operation begins PoLo will enable you to send an activation spot. Reveal the Spotting button using the left pointing arrow in the details area; pressing the button will give you a chance to add a comment to the spot. The spot button will display icons for each of the activities included in the operation that provide self-spotting services.
Re-spotting is done in the same way, with QSY or QRT entered into the Comments window depending on the operators actions.
You can also self-spot by using the SPOTME or just SPME commands in the callsign entry field. You can add a short comment after a /, such as SPME/QRV.
And for the most common uses, you can just use the even shorter commands QRV, QSY and QRT to self-spot with the respective comment.
PoLo currently supports receiving spots for POTA, SOTA and WWFF, clicking any spot within the list on the spots tab will put all of that contact’s details into a new slot on the QSO tab enabling quick and easy contact to be made.
All frequency bands and modes that PoLo supports are made available for use from Settings > Logging Settings > Bands & Modes. Initially the common bands and modes are available, this can be changed to all bands, and all modes by tapping ‘Show all bands’ or ‘Show more modes’ at the bottom of each section.
Once you have access to the band or mode you’re searching for enable it by using its switch. Backing out of that page to the Logging Settings page will show you the bands and modes available to be used in a new operation.
The list of the most popular modes and bands are enabled by default. There are numerous other bands and modes available and can be enabled by the user.
To enable more Bands or Modes, first select Logging Settings then click Bands and Modes. The currently available bands and modes are listed on the next screen which allows for more to be enabled by clicking the slider controls. Still more bands and modes are available behind the Show all bands or Show more modes item.
Once open, the Bands & Modes page will show even more bands or modes. Enable the bands or modes desired using the slider controls and return to Operation Settings
“Callsign Notes” is a feature that allows you to show short notes for specific callsigns in the logging screen. This can be useful to remember the name of a friend, or to know if a station is a member of a club or a special event station.
PoLo comes with a built-in file, called “Ham2K’s Hams of Note”, but you can add as many additional files as you want, and enable and disable them as needed.
The built-in Notes include emojis such as 🧑💻, 👷, 📺, 💻, 🌳 and others, so if you see one in the logs somewhere, this is where they come from.
Custom callsign notes are stored as simple text files, one call per line followed by information you wish to show in the logging screen.
If the information starts with an emoji, it will be shown in log and spotting entries.
Empty lines, and lines that start with # are ignored.
An example of the simplest format used for the file would be:
VK1AO Alan
VK4KC Marty
KI2D Sebastián
# etc
The file also supports simplified markdown tags similar to the ones used on GitHub. So you may supply hyperlinks and text formatting which is then used by PoLo to display the text.
Once this file is created, you may place the file in your favourite cloud storage folder and copy the public link for the file to be installed into PoLo.
The URL you provide must be a direct link to the file in plain text, and not a link to a web page that contains the file as it’s often the case for file sharing tools and cloud storage services.
However, PoLo knows how to handle some cloud storage services, and can automatically convert the link to a direct link. This is currently supported for Dropbox, OneDrive, Google Drive and Google Docs.
In the application Settings, tap Data Settings.
In the Data Settings, tap Callsign Notes
In the Callsign Notes page, click on + Add a new file then give the file a name and copy the url into the Location field. Activate the file with the slider control.
In the Custom window, provide a name for your files and paste the url for the file into the Location field
Click Done to return to the Callsign Notes, then enable the file you have added by using the slider control
From this point, you may return to the Offline Data page and click on the file name so you can Refresh the file. This action will pull the file onto the device. The date and time of the last update is shown in this dialog so future refresh actions can be managed as your wish. Click Done.
Every now and then you will see an emoji within the Callsign Info Panel, for example if you enter KI2D you'll get the following: 🤩 Sebastián - Ham2K PoLo Creator.
You can expect to see any of the following, and some others too:
🧑💻 - Ham2K PoLo contributor
👷 - Ham2K Test Crew
📺 - YouTuber
💻 - Software developer
In addition, it’s possible to add your own list of callsigns with details (and emojis) using the Settings > Data Settings > Custom Callsign Notes option. You can link to your offsite list which could include POTA friends, fellow club members etc.
During an operation PoLo only needs an Internet connection to enable spotting, and to pull contact data from qrz.com, all other data is stored on your device.
These offline data files, those within the Settings > Offline Data area along with those in Settings Callsign Notes synchronise periodically dependant on how often they might change. Callsign Notes update daily; the well established programmes such as SOTA update every 3 months or so, but POTA and WWFF are set to update monthly due to their possibilty of expanding as more sites are included within those programmes.
Each of these data sets can be refreshed manually by selecting them in the Data Settings area, and tapping Refresh on the pop-up.
WARNING: Using Developer Mode features can increase the chances of crashes and data loss. Use with caution.
To enable Developer Mode, start a new operation, or open an existing one, type KONAMI in the callsign input field, and press the [Send] key (or [RETURN] or [ENTER]) in your keyboard.
You should see a short message confirming that the mode is now enabled.
You can use this same procedure to toggle it off.
You will now find new features and options in the app, usually highlighted in an orange color.
In the Deverloper Settings you can now select between three different “update channels”:
Stable: The default channel, with the most stable and tested versions.
Unstable: The latest versions, with new features and bug fixes, but not as well tested.
Bleeding Edge: Work in progress, with the newest features and bug fixes, but also the most likely to have issues.
After changing channels, you should use the option to “Check for new versions” to download the latest version from the selected channel.
In Developer Mode you can now export and import raw data files used by PoLo, in the “QSON” data format used internally by the app.
You can export an operation in the Operation Settings tab. And you can import a QSON file as a new operation from the main Developer Settings screen.
PoLo offers several sources for data both offline and online.
QRZ XML data Lookups are available for both free accounts and paid subscription. The data offered by QRZ retrieved during the query to QRZ is, however, different in each case. According to QRZ policy, free accounts provide for 100 lookups per day after which no data will be returned. Additionally, the data provided for free accounts is a subset of the data returned for paid account queries. Your QRZ account details on the qrz.com website will show your Callsign Lookup Activity as total web lookups today, total XML lookups today and your daily maximum limit is also shown. The lowest QRZ subscription level of “XML Data” will provide unlimited XML data lookups.
Previous Operations may be left on your device and serve as data lookups in the event that no cell coverage is available and no ADIF data has been uploaded to the device. Callsign Notes, if enabled, will always be presented on the callsign entry form when a callsign match is found.
Operation Data also serves to provide statistics with regard to the number of contacts/QSOs made with another operator.
It is also possible to upload an ADIF file to your device to serve as lookup data. In this case, historical lookups are done across all operations plus the ADIF records you have loaded.
The XML data fields returned from a callsign query for free QRZ subscriptions are limited to FirstName, Surname, Address, Country field values only. The raw data return from such a query is show below and includes a Session Message that A subscription is required to access the complete record.
In particular, queries for free subscribers DO NOT include grid locators, which is what PoLo uses to show the QSOs on maps.
<Callsign>
<call>VK1AO</call>
<fname>Alan</fname>
<name>McDonald</name>
<addr2>Yellowtail Way NSW</addr2>
<country>Australia</country>
</Callsign>
<Session>
<Key>8080e595830xxx23939b3fefa049983e</Key>
<Count>3</Count>
<SubExp>non-subscriber</SubExp>
<Message>A subscription is required to access the complete record.</Message>
<GMTime>Sat Aug 10 03:11:55 2024</GMTime>
<Remark>cpu: 0.017s</Remark>
</Session>
</QRZDatabase>
For subscribers to QRZ, the XML data returned is comprehensive and includes the sort after callsign gridsquare and QRZ primary image link. The callsign gridsquare, if returned, will be used in the QSO Map. The veracity of the gridsquare is, of course, subject to whether the OP being queried has recorded accurate data.
<QRZDatabase version="1.36" xmlns="http://xmldata.qrz.com">
<Callsign>
<call>VK1AO</call>
<aliases>4W/VK1AO,VK2MET,AX1AO,VK1O</aliases>
<dxcc>150</dxcc>
<fname>Alan</fname>
<name>McDonald</name>
<addr1>Worimi Country - Yellowtail Way</addr1>
<addr2>CORLETTE NSW</addr2>
<zip>2315</zip>
<country>Australia</country>
<lat>-32.729451</lat>
<lon>152.117641</lon>
<grid>QF67bg</grid>
<ccode>18</ccode>
<land>Australia</land>
<efdate>0000-00-00</efdate>
<expdate>0000-00-00</expdate>
<qslmgr>eQSL, LoTW, HRDLOG.net, ClubLog and OQRS (see below)</qslmgr>
<email>vk2met@meta.com.au</email>
<u_views>12043</u_views>
<bio>55766</bio>
<biodate>2024-07-22 08:47:47</biodate>
<image>https://cdn-xml.qrz.com/o/vk1ao/rd_VK1AO_with_Badges_Alignment_M.png</image>
<imageinfo>337:770:498048</imageinfo>
<moddate>2024-07-31 11:57:02</moddate>
<eqsl>1</eqsl>
<mqsl>0</mqsl>
<cqzone>30</cqzone>
<ituzone>59</ituzone>
<iota>OC-001</iota>
<lotw>1</lotw>
<geoloc>user</geoloc>
<name_fmt>Alan McDonald</name_fmt>
</Callsign>
<Session>
<Key>64772b0a412573xxxd61071d6fac6d19</Key>
<Count>99619</Count>
<SubExp>Mon Apr 21 16:06:43 2025</SubExp>
<GMTime>Sat Aug 10 03:12:19 2024</GMTime>
<Remark>cpu: 0.020s</Remark>
</Session>
</QRZDatabase>
The QSO map is a very popular feature. There are some basic requirements to produce this map:
To provide the origin of the map, you must supply your location for each operation. If you select a park or summit etc, the location grid will be supplied by PoLo based on the park/summit/activity list. Please note that the grid will be based on the centroid of a park so a trail crossing several state borders may not accurately represent your exact location. In these cases, you should enter a gridsquare that represents your current location. You can use your device’s GPS or enter the grid manually in the Operation Location setting.
In cases where you have chosen to log general QSOs, you must remember to enter your location manually.
Why do I not see any lines on my QSO map? Most likely because you do not have your own location set for the operation.
The other operator may be at their home location, or in a park/summit etc. For operators at their home location, their gridsquare is sourced from either a live/online lookup (refer to Data Lookups in this doumentation), offline or historical data, or the Park2Park or Summit etc gridsquare.
The primary source of lookup data at this time is QRZ and/or if active, HamDB lookups (free, but US, Canada and Germany only). As stated elsewhere in this documentation, the details of live data from QRZ is subject to your subscription level. A paid subscription will return the other operator’s gridsquare. Using a free subscription will not return this data.
In the case of a missing gridsquare e.g. using a free subscription and a chaser at their home QTH, their location will be based on the ability of PoLo to interpret the callsign location. The locaiton may be the centre of the operator’s country only, or in some cases a state of the operator’s country.
Why do all the lines on my map go to one place, in the centre of the country? The most likely reason is becuase you are limited to a free QRZ subscription and operator gridsquares are not available. Country centroids may be used in this case.
The secondary source of lookup data for your QSOs is historical data. You may, if you wish import an ADIF file of previous QSOs (your amateur radio log file). If this data is available, it will be used where other sources of data are not available.
Of course, if your historical data is all subject to a free QRZ subscription, operators’ gridsquares will be missing. Gridsquares may be present as sourced from digital modes such as FT8. But in the main, your hisitorical data in this instance may only be able to provide name and address information as per Data Lookups.
If the above data is available, the map can be produced with your location centred. QSO lines are drawn for your contacts based on the level of data available and the map dots are coloured based on the band used for each contact. Clicking on a dot will reveal the QSO details.
The Ham2K Forums is the best place to report bugs, suggest new features and discuss the use of PoLo with other users.
We have a Discord Server where you can chat with other users and the development team.
The @Ham2KApps Instagram account is a great place to see what other users are doing with PoLo.
These basic sample guidelines assume that your Docsy site is deployed using Netlify and your files are stored in GitHub. You can use the guidelines “as is” or adapt them with your own instructions: for example, other deployment options, information about your doc project’s file structure, project-specific review guidelines, versioning guidelines, or any other information your users might find useful when updating your site. Kubeflow has a great example.
Don’t forget to link to your own doc repo rather than our example site! Also make sure users can find these guidelines from your doc repo README: either add them there and link to them from this page, add them here and link to them from the README, or include them in both locations.
We use Hugo to format and generate our website, the Docsy theme for styling and site structure, and Netlify to manage the deployment of the site. Hugo is an open-source static site generator that provides us with templates, content organisation in a standard directory structure, and a website generation engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps them up into a website.
All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.
Here’s a quick guide to updating the docs. It assumes you’re familiar with the GitHub workflow and you’re happy to use the automated preview of your doc updates:
If you’ve just spotted something you’d like to change while using the docs, Docsy has a shortcut for you:
If you want to run your own local Hugo server to preview your changes as you work:
Follow the instructions in Getting started to install Hugo and any other tools you need. You’ll need at least Hugo version 0.45 (we recommend using the most recent available version), and it must be the extended version, which supports SCSS.
Fork the PoLo Docs repo repo into your own project, then create a local copy using git clone. Don’t forget to use --recurse-submodules or you won’t pull down some of the code you need to generate a working site.
git clone --recurse-submodules --depth 1 https://github.com/ham2k/polo.ham2k.com
Run hugo server in the site root directory. By default your site will be available at http://localhost:1313/. Now that you’re serving your site locally, Hugo will watch for changes to the content and automatically refresh your site.
Continue with the usual GitHub workflow to edit files, commit them, push the changes up to your fork, and create a pull request.
If you’ve found a problem in the docs, but you’re not sure how to fix it yourself, please create an issue in the PoLo Docs repo. You can also create an issue about a specific page by clicking the Create Issue button in the top right hand corner of the page.
If you want to add an icon to a page, referencing one of the icons in the app, visit the Material Design Icon Community Library, find the icon you want,
click on the “Copy SVG” button, paste the SVG code into your page and add a height="1.5rem" attribute to the <svg> tag to set the size.