A surprise invitation to a trip over to Braidwood with a bonus of “you can walk up that hill if you like” resulted in a short activation on Monday 24th October.
The climb up the eastern slope is always interesting, it presents a 3 dimensional challenge of not only climbing the bit in front of you, but also getting you to a place that will be easier to keep on climbing with a minimum of blockage by trees, rocks etc. The rocks are big ones.
Eventually I arrived at the summit and found a clear area near one of the compounds containing an apparently disused dish staring pointlessly at a position in the sky.
I had enough time for a handful of contacts on 40m ssb and then packed up and headed down to where my patient wife was happily reading a book.
The SOTAGOAT app is a well presented and popular app for iOS and works well on my iPhone 5s and the iPad.
Its features include displays for alerts and spots, just like the sotawatch.org website, configuration options allowing you to choose between UTC and local time for displays and posts, an option to produce a goat bleat when each new spot is received from sotawatch, a filter option to specify which modes you want to be informed about and the time periods in which you want the notifications and bleats to occur. It uses an internal list of summits which can be updated from a sotawatch site and can display a list of summits near to your current location, which it gets from the GPS info in the phone or tablet.
However, the current (2016) version of the app has an error in the time calculations for new alerts. Sotawatch uses UTC dates and times. I have sotagoat set to display and post in UTC. But the times posted and seen on sotawatch were always incorrect and I observed that they were incorrect by the UTC offset. The app was adding my UTC offset to the UTC times I wanted and then posting the adjusted time to sotawatch. I have found the error can be worked around by adjusting the alert time as follows.
When posting an alert I subtract my UTC offset from the alert time.
For example to post an alert for 2300 UTC I subtract 11 hours (in DST periods) or 10 hours (in standard time) and post the alert for the adjusted time, namely 1200 UTC.
This is easy for UTC times after 1100 but for earlier times, the date must be adjusted back too. It’s simple arithmetic you can do in your head. For say 0400, subtract 11 hours: I do that by one of these two methods:
First subtracting 4 hours to get back to 0000, then subtracting the remaining 7 hours (because 4+7=11) from 2400 to get 1700.
Add 24 hours to 0400 (2800) and subtract 11 hours from that (1700).
In each case, because the time is in the previous day, subtract one day from the date too.
What if I was in a time zone that is behind UTC instead of ahead?
I don’t know whether the software error treats both time offsets similarly. It is possible that it is correct for negative offsets.
The error has been notified to the author of the software but as it can take a while for new versions to be released via the iTunes Store, I will use this workaround until it is fixed. The utility of the application is too good in all other ways to stop using it.
My station setup for this event was later than planned. My original summit was to be VK2/ST-042 and to get access a phone call to the owner of the access road is usually all that’s required. However after two phone calls getting a voicemail response and no callback, I decided to go to Bobbara Hill, just west of Binalong, although that required a longer walk time as well as an extra 20 minutes of travel time.
Once I left the car, opened and closed the gate and starting to walk along the track leading to the hilltop, I was surprised by the wind strength even on the valley floor. As I climbed further I found the wind was even stronger on the hilltop.
I started setting up in the eastern side of the hill which happily allowed me to avoid the wind, but when I lifted the antenna pole up into the wind it was being blown around so vigorously in the turbulence that I decided it had no chance of surviving in that position and I moved everything further around to the east side of the mountain. More delay.
Finally I got on the band and called cq on cw, then worked 12 contacts, many being S2S. I tuned around for ssb activators but apart from Don M0HCU didn’t hear many. I did call some but lost out to Europeans. Looked for Ed DD8LP lower in the band where he was spotted but nothing there. Twice the pole collapsed mid-contact. Very difficult especially on a slope and in that wind.
I forgot to spot myself but while the contacts are coming you don’t need more qrm. I have a 250 hz filter in the 703 but that wasn’t narrow enough to sort through the signals at one stage. Have to say my sending was affected by the unseasonably cold temperatures, not sure exactly what the temp was, but less than 10C, possibly down to 6C or so by the time I finished. Others were making mistakes too.
Found the tablet was ok for logging but on cw it is tricky to log an incoming call as it happens. Pencil and paper are easier for that…
I worked 12 contacts, DL3TU, VK4BJS, HB9FVF, OK2PDT, DL3HXX, DL4CW, HB9DQM, OE5AUL, CT7AGR, HB9AFI, JP3DGT and M1EYP just after sunset. Thanks to all.
The surprise was to finally work Tom M1EYP as my last contact and then I looked up and realised the light was fading fast so I packed up. Walking back down the hill, I was in near darkness as I approached the car half an hour later.
The next morning I received an email from CT7AGR, Portugal, a very nice message thanking me for the contact. I was just relieved to make the 12 contacts I did including 8 as Summit to Summit (s2s).
Update: received another email re the S2S contacts. S2S are the most desirable of all the sota contacts.
I was having some trouble getting reliable linking to provide the android tablet (a Lenovo Tab3/7) with internet access while on hilltops or in parks.
A bit of research found a lot of wave-away-the-problems type of solutions, which didn’t solve it at all.
Finally I discovered a comment about the type of hotspot that the iphone actually provides. It is not an infrastructure type but an adhoc hotspot. And more to the point, it does not advertise it continuously. It only advertises the hotspot for a limited time after being enabled, or after you visit the Personal Hotspot option in the Settings menu.
After some experimentation I now find that the tablet happily links to the iphone every time, provided I go to the Settings > Personal Hotspot item in the iphone and then wait about 10 seconds. Nothing else needs to be done, provided the wifi password has been set in the tablet.
The other solution I have used from some hilltops is to take a personal hotspot device with me. As my phone provider uses a provider that does not have as good coverage as Telstra, this provides my tablet with excellent network coverage from places without any service on the other network.
Here’s a pic of the hotspot lashed to a tree on the Boboyan Range summit, 40 km south of Canberra.