QTH.app 0.7.1

[Weston Bustraan]

New build available: QTH-0.7.1.dmg

Changelog:

* Fixed Mic-E longitude encoding bug for stations in +/- 9..<10 degree range
* Clicking on errors in notification center will now open the log file automatically

- Wes W8WJB

[Ken Hagler]

On Jan 9, 2022, at 2:05 PM, Weston Bustraan <wbus...@gmail.com> wrote:
>
> * Fixed Mic-E longitude encoding bug for stations in +/- 9..<10 degree range

I’d been seeing strange behavior with my location, but I wasn’t sure it wasn’t on aprs.fi’s end. Whatever the problem is, it’s still going on—currently I’m in Morocco according to aprs.fi.
--
Ken Hagler

| http://www.orange-road.com/ |
| And tho' we are not now that strength which in old days |
| Moved earth and heaven, that which we are, we are --Tennyson |

[Weston Bustraan]

Did that just start happening with QTH 0.7.1? Which SSID? Are you sending Mic-E packets?

The position in Morocco says that it was sent by a Kenwood TM-D710

If anyone is curious about my "oops" in th +/- 9..<10 degree range, the APRS specification says this:

The longitude offset is set to +100 degrees when the longitude is in the range 0–9 degrees.

I mistakenly implemented this as:  if abs(longitude) <= 9

However, someone contacted me from Lisbon, Portugal, which happens to have a longitude of -9.xx and I realized the range above 9.0 and below 10.0 need the longitude offset as well.

So, I changed it to: if abs(longitude) < 10 to catch these 2 ranges of longitudes

- Wes W8WJB

[Ken Hagler]

On Jan 9, 2022, at 5:53 PM, Weston Bustraan <wbus...@gmail.com> wrote:
>
> Did that just start happening with QTH 0.7.1? Which SSID? Are you sending Mic-E packets?

I noticed it last night, when I was still on 0.7.0. The SSID I’m using for QTH is KI6HQT-1. As far as I know I am.

> The position in Morocco says that it was sent by a Kenwood TM-D710

That’s part of why I think the problem may be on APRS. I was also looking at the lat/long in the raw packet view, and it seemed right. The only reason I just didn’t write it off as certainly an aprs.fi bug is that KI6HQT-1 (my D710 in APRS mode, not QTH) and KI6HQT-7 (my D74) are both showing up in the right place.

Also, the place I show up as in aprs.fi is changing—last night it thought I was in north Austin, and earlier today it had me a few miles west. I’m also seeing info from other digipeaters mixed in with mine. For example, if you look at KI6HQT-10 on aprs.fi right now, you’ll see this:

Ver. 01Oct2009 - TCARES ARCHES System Online: www.tcares.org
Mic-E: Off duty
power 25W, antenna HAAT 40 ft, gain 4 dBi omni,

That’s the information for one of a series of digipeaters on hospital roofs around the Austin area. It should be showing “QTH.app experimental digipeater” as the comment, and different PHG info (more power, lower antenna).

[Ken Hagler]

On Jan 9, 2022, at 6:04 PM, Ken Hagler <kha...@gmail.com> wrote:
>
> I noticed it last night, when I was still on 0.7.0. The SSID I’m using for QTH is KI6HQT-1. As far as I know I am.

Oops, I meant I’m using KI6HQT-10 with QTH. -1 is for the D710 without QTH.

[Weston Bustraan]

I think I know what's going on. I didn't connect it until you said you were operating QTH as a digipeater. It probably started with 0.7.0, with the support for tactical callsigns. I think it is probably overriding the source callsign for packets that it iGates. It is only supposed to do this for packets that originate from QTH and not for repeated packets, but perhaps that flag is not being set properly. Investigating..

Assuming this is the case, I will have a fix shortly.

- Wes W8WJB

[Weston Bustraan]

Yep, that's it. The 'repeated' flag is getting set properly by the digipeater/igate code and there is code that checks for it when setting the source callsign, but with the advent of the tactical callsign support, each connection now makes a copy of the outgoing packets. It was not copying the 'repeated' flag.

Update incoming. Just waiting for Apple's notarization service.

- Wes W8WJB