PoLo Features

• 1: Operations with more than one Operator
• 2: Tips and Tricks
• 3: Operations Panel
• 4: Satellite Operations
• 5: Spotting
• 6: Band and Modes
• 7: Callsign Notes
• 8: Emojis
• 9: Online and Offline
• 10: Developer Mode
• 11: Callsign Expansion
• 12: Data Lookups
• 13: Mapping Requirements and FAQ

1 - Operations with more than one Operator

PoLo provides for a single logging operation where more than one Operator is activating, so one person can do the logging for both operators. On completion of the activation, separate logs will be generated for each Operator. There is no need to duplicate a single log and edit the contents for the second operator.

Setup

After creating the operation and adding whatever activities are applicable, you can edit the Station & Operator settings to reflect the callsigns of the operators who are handing the microphone around. The callsigns are entered as a comma separated list in the Station Callsign field.

Continue to log the calls as you would for a normal single operator operation/activation. The heading for the operation will indicate the number of operators.

Self Spotting

When you spot with this setup, the default spot comment includes “2 ops” in the comment. Two spots will be created - one for each operator. This allows for non-PoLo environments to see both of you.

Polo Spots has the ability to consolidate spots from the same park on the same frequency. In cases like this, for other PoLo users, tapping on the spot for a multi-op activation will result in a log entry with both callsigns in the “Their Call” entry field. You can just confirm the callsigns and send them for 2 entries to be created in your log, one for each operator on the other end.

Finalising/Exporting the logs

When you finish the operation, it’s time to export the logs. This time, however, you will be offered the export of logs for each Operator in the comma separated list as separate logs.

Future Template

Once this operation is present on your device, the setup will be offered as a Template. So for future operations with the same buddy, you can just choose the template to get the Station & Operator settings.

2 - Tips and Tricks

Shortcut Commands from the Callsign Input Field

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.

Smart Data Entry

Call stacking can be done by using // or ... The last valid call in the list is accepted when you press “Send”, and the rest are preserved in the callsign entry field.

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.

Quick field selection

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.

Multiple QSOs at once

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.

Callsign Stacking

Everyone will have their favourite way to handle a pileup. For those who like the callsign fragment method i.e. one where you might scribble down callsign fragments and then back track to each fragment in the list one at a time, then Callsign Stacking may be of interest.

In the “Their Call” entry field, enter each fragment that is heard separated by double slashes

Then work backwards through the stack, correcting each call until confirmed. Once confirmed, send the corrected call to you log.

Sending a complete call will remove it from the stack and leave the stack ready for correcting the next partial/fragment.

Continue until all fragments are corrected and submittted.

Smart Slash

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.

Bearing and distance

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.

3 - Operations Panel

Operations Panel

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.

• If you entered a qrz.com account in PoLo settings then the name and location held for your contact will be displayed.
• If you subscribe to qrz.com then their bearing and distance will also be displayed (assuming your contact has location details set at qrz.com)
• You should also see a country flag, and occasionally an emoji, that contact is in the Ham2K Hams of Note list. The meaning for these is covered in the emojis area of the manual.
• If you’ve worked a station previously then the number of contacts and time period will be displayed.

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.

4 - Satellite Operations

Enabling a Satellite Operation

Scroll down on the App Features tab to find “Other Features”. Enable Satellite Operations.

Next, create a New Operation and in the Activities section, add Satellite Operations.

Next go to the QSO tab of the Operation and open the “More Controls” section. Tap the Sats control to bring the satellite list into view for the operation.

Selecting the Stats button will provide a drop-down list of the satellites currently available in PoLo, select the one you are working. It should bring the frequencies into view for that satellite.

Ensure that the satellite you are selecting is visibly selected in the control panel.

The export feature will export all fields associated with these satellite contacts.

The list of satellites available for selection within PoLo can be found here.

If you are aware of a satellite missing from this list please leave a message to the effect on the PoLo support forums

5 - Spotting

Self Spotting

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. Enter these commands in the “Their Call” field and just send it. There’s no need to open and edit your spot comments in this instance. It saves even more time.

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.

Spotting another Operator (coming in June 2025 for beta first)

You may often work another portable operator who may not have coverage to spot themselves. PoLo provides two ways to spot other operators. You can either spot them during or after you take their details, or just take their details, spot them and discard the settings.

During or after logging them

Take the details such as park number(s), frequency, mode etc and before you tap Send to save, open the controls panel where you will notice that the “Self-Spotting” button has become “Spot”. Simply tap this button now to send a spot for the other operator. When the spot is confirmed, save the QSO in the normal way with the “Send” button.

Working and spotting multiple operators is easy as entering the callsigns as a comma-separated list in the “Their Call” entry field. Spotting will then spot both callsigns and subsequent logging will save each as a separate contact. See also Multi-Op Operations for more details

Without logging them

If you have already worked the other station or do not wish to log them them for other reasons, you can just fill in the QSO details as you would normally, then “Spot” them, then just wipe the QSO details.

You may be portable but not specifically activating a site and this “Spot other” action gives you the ability to help out when you have cell coverage and the other OP does not.

6 - Band and Modes

Select the Bands and Modes you operate on

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.

Enabling other modes and bands

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

7 - Callsign Notes

“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 Files

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.

File Format

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.

File storage and access

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.

Step 1:

In the application Settings, tap Data Settings.

Step 2:

In the Data Settings, tap Callsign Notes

Step 3:

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.

Step 4:

In the Custom window, provide a name for your files and paste the url for the file into the Location field

Step 5:

Click Done to return to the Callsign Notes, then enable the file you have added by using the slider control

Step 6:

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.

8 - Emojis

What do the emojis mean?

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.

9 - Online and Offline

Online and Offline

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.

10 - Developer Mode

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.

Developer Mode Features

Unstable Versions

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.

Raw Data Export and Import

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.

11 - Callsign Expansion

The Callsign Notes file can be used to store and retrieve multiple callsign lists from a shortcut stored in the file.

Callsign Shortcuts/Abbreviations

A typical Callsign Notes file entry will look like this:

VK1AO Alan
VK4KC Marty
KI2D Sebastián
# etc

For each callsign entered, the accompanying name will be displayed as a note, but the callsign will be in the “Their Call” ready for sending (saving).

When an entry is made with 2 leading dots (or slashes) and the note file entry is formatted with a comma separated list instead of a single name entry, the list of callsigns are expanded and entered into the “Their Call” entry field ready for confirmation and saving.

1AO VK1AO,VK2MET
4KC VK4KC,VK4MAD,VK4DOG
1RF VK1RF,VK2MK, VK4CEE
# etc

So by entering ..1RF or //1RF the prompt becomes:

The first tap of the send button will drop the expanded list into “Their Call” where you may edit, add or remove a callsign to confirm. The second tap of the send button will submit the list of callsigns into you operation as separate QSOs.

12 - Data Lookups

Lookup Data Sources

PoLo offers several sources for data both offline and online.

• QRZ Lookup is the primary source of online data and falls into two categories depending on whether you have
• a paid subscripion to QRZ or
• use only the free account provisions. In addition to this source, there is the
• Callsign Notes feature which is data downloaded and avilable offline,
• and also history from both the Operations present on the device and any historical ADIF data you have chosen to import.
• HamDB lookups (free, but US, Canada and Germany only)

QRZ Lookups

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.

QRZ Authentication

Please remember that logging into QRZ via the API requires that you use your callsign, NOT your email address. You can use either email address or callsign when logging on to your QRZ account, but only your callsign for the api which is required for lookups.

Addtionally, the QRZ API is known to have problems with passwords with some special characters that might work fine when logging thru the web. If you’re having problems using your credentials in PoLo, please consider changing your password to use only letters, numbers and common symbols.

Use the account Check Credentials link to ensure you have the password correct

If a login is successful, this link test will change to a tick

Operation Data

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.

ADIF History

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.

Differences in Data returned by QRZ for free accounts

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> 

13 - Mapping Requirements and FAQ

Mapping - What you need and FAQ

The QSO map is a very popular feature. There are some basic requirements to produce this map:

• Your location,
• The location of the other operator,
• Live/online data lookup (primary) or,
• Offline/Historical data (secondary).

Your location

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 location of the other operator

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.

Live/online lookup

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 location 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 because you are limited to a free QRZ subscription and operator gridsquares are not available. Country centroids may be used in this case.

Offline/Historical Data

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.

The Map

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.