开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

New M1 Mac and not paying attention


 

I'm guilty of not paying attention to the issue of running YAAC on a M1 Mac. Can it be done? If so, what do I download and how do I install it?


 

It should be doable. Any build of YAAC since #169 (#175 is current) has a version of the JSSE library that includes both Intel and ARM CPU versions of the Mac OS X native code. So, as long as you have a suitable Java runtime installed on your Mac M1, you should be able to download the YAAC.zip file, unzip it in a suitable folder, and click on the YAAC.jar file within the installation folder and have YAAC up and running with serial port support for your TNCs.

Let us know if you have any difficulties.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Friday, July 8, 2022 12:55 PM
To: [email protected]
Subject: [yaac-users] New M1 Mac and not paying attention

I'm guilty of not paying attention to the issue of running YAAC on a M1 Mac. Can it be done? If so, what do I download and how do I install it?


 

开云体育

I apparently have a “suitable Java runtime” installed because downloading and installing the latest version worked perfectly. I have YAAC 1.0-beta175 on both my older intel Mac and now on my M1 Mac, the menu system looks different. But I'm going to push that off as my imagination.

Thank you for the encouragement to just give it a try.

Keith, WA0?TJT
Take a look at:
Then consider joining:?/g/NCM

On Jul 8, 2022, at 5:07 PM, Andrew P. <andrewemt@...> wrote:

It should be doable. Any build of YAAC since #169 (#175 is current) has a version of the JSSE library that includes both Intel and ARM CPU versions of the Mac OS X native code. So, as long as you have a suitable Java runtime installed on your Mac M1, you should be able to download the YAAC.zip file, unzip it in a suitable folder, and click on the YAAC.jar file within the installation folder and have YAAC up and running with serial port support for your TNCs.

Let us know if you have any difficulties.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Keith Kaiser <wa0tjt@...>
Sent: Friday, July 8, 2022 12:55 PM
To: [email protected]
Subject: [yaac-users] New M1 Mac and not paying attention

I'm guilty of not paying attention to the issue of running YAAC on a M1 Mac. Can it be done? If so, what do I download and how do I install it?








 

Andrew,

thank you for showing how to install YAAC on an M1MAC. ?I have it running and showing data from my FTM-400. I also have a USB GPS plugged into my Mac but there its putting me in the wrong location. ?I check the GPS data and its correct but there seems to be an offset. ?I am running?Version 1.0 (1.8.0_341) on the Mac and I hope I can find a way to debug why there is an offset on my position. ?

Thank you,
Tim KM4ESU


 

Andrew,

I did check the GPS from the FTM-400 that shows the correct location and the GPS data YAAC is showing they basically match. I do not know why it shows my shack in a different location. ?

Also in the Yaesu data can you get GPS location and I will remove the other GPS. ?

thank you,
Tim KM4ESU


 

Well,

1. What is the fixed station location configured in your beacon? Per chance, is it where your station is displayed?
2. Is your beacon configured to actually _use_ the GPS information to override the fixed location in the beacon configuration? If not, the GPS data will be ignored when generating your station's location. It doesn't matter that you can't _send_ a YAAC beacon through a Yaesu APRS-capable radio; it still controls how your location is determined by YAAC.

Re: eliminating the 2nd GPS: Sorry. Unlike the Kenwood radios, the Yaesu radio does not feed its connected GPS data through interleaved with received APRS traffic. So YAAC has no way of knowing what GPS information is fed directly into the Yaesu radio. If you are using an RS232/DB9 connected GPS, might I suggest an RS232 splitter, so one GPS can feed both the radio and the computer? Something like this, perhaps?



Alternatively, I can look into adding a port for _exporting_ GPS from YAAC in NMEA-0183 serial format, so you wouldn't need a clunky hookup like that (but would need to have a second USB-to-RS232 adapter on your computer to feed the GPS data out to the radio). Not sure if that is a useful enough configuration option (especially with the cost of either a second RS232-USB adapter or getting a dual one in the first place), but let me know.

Hope this helps.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Tim Huffaker
Sent: Friday, October 7, 2022 12:03 PM

Andrew,

I did check the GPS from the FTM-400 that shows the correct location and the GPS data YAAC is showing they basically match. I do not know why it shows my shack in a different location.

Also in the Yaesu data can you get GPS location and I will remove the other GPS.

thank you,
Tim KM4ESU


 

On Fri, Oct 7, 2022 at 10:03 AM Tim Huffaker <thuffaker@...> wrote:
?
I did check the GPS from the FTM-400 that shows the correct location and the GPS data YAAC
is showing they basically match. I do not know why it shows my shack in a different location. ?

What's the callsign of your shack? Where is your shack actually located? What do you consider an offset?

Your station KM4ESU-10 is wandering around the neighborhood due to a wandering GPS fix.

Look at the lat/long, course and speed in these decoded packets.

2022-10-06 09:57:07 MDT:?>STSV3T,,WIDE2-1,qAo,:`r=?l"P-/`"6!}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.550666666667 °
???course: 252 °
???speed: 0 km/h
???altitude: 192 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:03:35 MDT:?>STSV3V,,WIDE1*,qAo,:`r=?l@~-/`"5s}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.550666666667 °
???course: 298 °
???speed: 5.556 km/h
???altitude: 183 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:05:02 MDT:?>STSV3V,,WIDE2-1,qAo,:`r=!lA<0x1d>-/`"5q}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.550833333333 °
???course: 301 °
???speed: 5.556 km/h
???altitude: 181 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:10:54 MDT:?>STSV3U,,qAo,:`r=#l!(-/`"5C}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.551166666667 °
???course: 112 °
???speed: 0 km/h
???altitude: 135 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:33:15 MDT:?>STSV3V,,qAo,:`r=<0x1d>l4^-/`"5w}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.550166666667 °
???course: 66 °
???speed: 3.704 km/h
???altitude: 187 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:34:18 MDT:?>STSV3W,,WIDE2-1,qAo,:`r<~l@--/`"5u}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3W
???latitude: 34.606166666667 °
???longitude: -86.549666666667 °
???course: 217 °
???speed: 5.556 km/h
???altitude: 185 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:35:20 MDT:?>STSV3Y,,qAo,:`r<{l>F-/`"5r}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3Y
???latitude: 34.6065 °
???longitude: -86.549166666667 °
???course: 42 °
???speed: 5.556 km/h
???altitude: 182 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:37:16 MDT:?>STSV3V,,WIDE2-1,qAo,:`r=?l4T-/`"5p}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.550666666667 °
???course: 56 °
???speed: 3.704 km/h
???altitude: 180 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:39:00 MDT:?>STSV3T,,qAo,:`r=<0x1c>l?z-/`"5s}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.55 °
???course: 194 °
???speed: 5.556 km/h
???altitude: 183 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:43:05 MDT:?>STSV3V,,WIDE2-1,qAo,:`r=<0x1e>l4P-/`"5y}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.550333333333 °
???course: 52 °
???speed: 3.704 km/h
???altitude: 189 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 10:52:18 MDT:?>STSV3T,,WIDE2-1,qAo,:`r=<0x1f>mTD-/`"5t}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.5505 °
???course: 240 °
???speed: 27.78 km/h
???altitude: 184 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 11:02:39 MDT:?>STSV3T,,WIDE1*,qAo,:`r<<0x7f>l!m-/`"6<}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.549833333333 °
???course: 181 °
???speed: 0 km/h
???altitude: 219 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 11:27:00 MDT:?>STSV3T,,WIDE2-1,qAo,:`r=?l5^-/`"61}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.550666666667 °
???course: 166 °
???speed: 3.704 km/h
???altitude: 208 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 11:44:08 MDT:?>STSV3U,,qAo,:`r=<0x1f>l?a-/`"6)}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.5505 °
???course: 69 °
???speed: 0 km/h
???altitude: 200 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 13:51:20 MDT:?>STSV3U,,qAo,:`r=?l"|-/`"5R}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550666666667 °
???course: 296 °
???speed: 0 km/h
???altitude: 150 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 13:59:21 MDT:?>STSV3U,,WIDE1*,WIDE2-1,qAo,:`r=<0x1f>l5X-/`"5\}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.5505 °
???course: 160 °
???speed: 3.704 km/h
???altitude: 160 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 14:08:56 MDT:?>STSV3U,,WIDE1*,qAo,:`r=<0x1e>l?`-/`"5[}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550333333333 °
???course: 68 °
???speed: 0 km/h
???altitude: 159 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-06 14:40:43 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=?l!o-/`"5v}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550666666667 °
???course: 183 °
???speed: 0 km/h
???altitude: 186 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 08:30:50 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=<0x1e>l#P-/`"6D}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550333333333 °
???course: 352 °
???speed: 0 km/h
???altitude: 227 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 08:55:23 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=<0x1e>l"l-/`"5J}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550333333333 °
???course: 280 °
???speed: 0 km/h
???altitude: 142 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 08:59:08 MDT:?>STSV3T,,WIDE2-1,qAo,:`r=?l,--/`"5k}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3T
???latitude: 34.605666666667 °
???longitude: -86.550666666667 °
???course: 217 °
???speed: 1.852 km/h
???altitude: 175 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 08:59:39 MDT:?>STSV3P,,qAo,:`r="l@"-/`"5i}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3P
???latitude: 34.605 °
???longitude: -86.551 °
???course: 206 °
???speed: 5.556 km/h
???altitude: 173 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:04:41 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=!l42-/`"5e}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.550833333333 °
???course: 22 °
???speed: 3.704 km/h
???altitude: 169 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:06:22 MDT:?>STSV3W,,qAo,:`r=<0x1d>l6$-/`"5g}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3W
???latitude: 34.606166666667 °
???longitude: -86.550166666667 °
???course: 208 °
???speed: 3.704 km/h
???altitude: 171 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:12:29 MDT:?>STSV3V,,,WIDE2*,qAo,:`r="l,Z-/`"5i}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3V
???latitude: 34.606 °
???longitude: -86.551 °
???course: 262 °
???speed: 1.852 km/h
???altitude: 173 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:12:58 MDT:?>STSV3R,,WIDE2-1,qAo,:`r=$lJ1-/`"5j}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3R
???latitude: 34.605333333333 °
???longitude: -86.551333333333 °
???course: 221 °
???speed: 7.408 km/h
???altitude: 174 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:27:07 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=<0x1f>l@z-/`"5u}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.5505 °
???course: 294 °
???speed: 5.556 km/h
???altitude: 185 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:33:58 MDT:?>STSV3U,,qAo,:`r=<0x1f>l?,-/`"5k}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.5505 °
???course: 16 °
???speed: 0 km/h
???altitude: 175 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 09:54:51 MDT:?>STSV3W,,WIDE2-1,qAo,:`r=<0x1e>l6l-/`"6&}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3W
???latitude: 34.606166666667 °
???longitude: -86.550333333333 °
???course: 280 °
???speed: 3.704 km/h
???altitude: 197 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 10:07:49 MDT:?>STSV3S,,qAo,:`r=<0x1f>l5<0x7f>-/`"5m}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3S
???latitude: 34.6055 °
???longitude: -86.5505 °
???course: 199 °
???speed: 3.704 km/h
???altitude: 177 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%

2022-10-07 10:26:01 MDT:?>STSV3U,,WIDE2-1,qAo,:`r=<0x1f>l!0-/`"6/}winlink_%
???type: location
???format: mice
???srccallsign: KM4ESU-10
???dstcallsign: STSV3U
???latitude: 34.605833333333 °
???longitude: -86.5505 °
???course: 120 °
???speed: 0 km/h
???altitude: 206 m
???symboltable: /
???symbolcode: -
???mbits: 111
???posresolution: 18.52 m
???posambiguity: 0
???comment: `winlink_%
?
If your house isn't moving that often, you might want to just set a static location in it rather than use a GPS.

I could see using a GPS in Ft. Myers or Orlando, but you are probably far enough away that the winds weren't that strong.

James
VE6SRV


 

Hi Andrew,

I have a USB GPS plugged into the Mac and YAAC sees the GPS and shows basically the same coordinates as the FTM-400 shows. When I beacon from the FTM-400 it puts out the correct location. ?I see the GPS running and look at its data its correct but my location is still off. This is what is confusing me. ?If the radio show a similar location as the USB GPS so why is the station so far off?

I do what to debug this so any suggestion would help. Note the GPS is a serial GPS from the USB port.?

Tim KM4ESU


 

Hi James,

I am using two different GPS. ?1 is the GPS location of my station and yes its KM4ESU-10. ?my second GPS 2 is a USB GPS input to my Mac and it is on a different USB to Serial line. ?Yes the GPS is having locking issue due to the monitor next to it and the GPS for the Mac has a clear view of the sky.?

Tim?
KM4ESU


 

Andrew,

Interesting development. I went back to the configure by wizard and the GPS. ?I turned off the GPS and used the exact coordinates showing in GPS and now it showing the correct location. I wonder why I get such a different with the same data. ?

If you can point to something to resolve this please let me know. ?

Tim?
KM4ESU


 

You already provided the answer to your own question.

> Yes the GPS is having locking issue due to the monitor next to it

If the GPS position is changing, then the location reported will be changing.

That is unless you are complaining about something completely different. You keep saying that you are seeing something different than what you expect, but you have as of yet to provide any description or example of what it is that you are seeing that is different.

James
VE6SRV


On Fri, Oct 7, 2022 at 3:12 PM Tim Huffaker <thuffaker@...> wrote:
Andrew,

Interesting development. I went back to the configure by wizard and the GPS.? I turned off the GPS and used the exact coordinates showing in GPS and now it showing the correct location. I wonder why I get such a different with the same data. ?

If you can point to something to resolve this please let me know. ?

Tim?
KM4ESU


 

Hi James,

I am sorry but I think I confused you on what is going on. ?The radio is a Yaesu FTM-400 that has a built in GPS. ?So it know its position and does not know YAAC is running. ?It also does not share its position with YAAC only APRS objects etc it receives.?

YAAC wants to know were your station is located so I have a USB GPS plugging into my M1 Mac and in the /dev list I can see the gps USB to serial listed. When I run the wizard I added the GPS and then the FTM-400 USB to serial data for the radio. ?All were working but the GPS showed me about 40mi from ware I am located. ?I am in Huntsville and it showed my station close to Ft Payne. ?This was the offset. ?To get the station location to the correct location I turn off the GPS and inputted the GPS coordinates that the GPS showed from the GPS status drop down. Now my station is in the correct location. ?

The problem is why with the exact same location for the station I get two drastically different results. ?One used the GPS and the second uses the same GPS the data. ?

Tim
KM4ESU?


 

Now that's really strange. Can you privately send me the AX25xmit, AX25rcvd and GPS logs (and the YAAC.out file) from your system for a day when you are using the GPS as an automatic position source? Also export your configuration to XML and send me the XML file, too. I have never seen this before, so if some bug got introduced into the software, I want it fixed ASAP. Note you may have to turn on logging received APRS traffic and the GPS data, as those may not be enabled by default.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Tim Huffaker <thuffaker@...>
Sent: Saturday, October 8, 2022 9:32 AM
To: [email protected]
Subject: Re: [yaac-users] New M1 Mac and not paying attention

Hi James,

I am sorry but I think I confused you on what is going on. The radio is a Yaesu FTM-400 that has a built in GPS. So it know its position and does not know YAAC is running. It also does not share its position with YAAC only APRS objects etc it receives.

YAAC wants to know were your station is located so I have a USB GPS plugging into my M1 Mac and in the /dev list I can see the gps USB to serial listed. When I run the wizard I added the GPS and then the FTM-400 USB to serial data for the radio. All were working but the GPS showed me about 40mi from ware I am located. I am in Huntsville and it showed my station close to Ft Payne. This was the offset. To get the station location to the correct location I turn off the GPS and inputted the GPS coordinates that the GPS showed from the GPS status drop down. Now my station is in the correct location.

The problem is why with the exact same location for the station I get two drastically different results. One used the GPS and the second uses the same GPS the data.

Tim
KM4ESU


 


I am sorry but I think I confused you on what is going on.

No confusion on this end. You just explained your issue a second time, however this time you added a significant detail.?


All were working but the GPS showed me about 40mi from ware I am located.? I am in Huntsville and it showed my station close to Ft Payne.? This was the offset.

That’s the information that has been missing thus far. It would be even better if you gave us the actual location information so we know what you are dealing with.?

Manual data entry errors can show up like this when people make mistakes in changing the format. It isn’t usually an issue when the software does the conversion as programmers are pretty smart. :)?


The problem is why with the exact same location for the station I get two drastically different results.? One used the GPS and the second uses the same GPS the data. ?

Just as Andrew has asked, we would need to see what the GPS is telling the computer.?

It would be interesting to find out that if a specific set of coordinates just happens to find a bug in the conversion calculation.?

From what you are telling us, it doesn’t sound like user error… I am intrigued.?

A wandering GPS will usually wander around the neighborhood. For a consistent 40 mile error, something else is probably happening.?

There’s something that needs to be fixed. But I still am wondering how far your house moves on a regular basis. Why not just input a fixed location into your equipment?

James
VE6SRV
--
James
VE6SRV


 

From: James Ewen

A wandering GPS will usually wander around the neighborhood. For a
consistent 40 mile error, something else is probably happening.
There’s something that needs to be fixed. But I still am wondering how
far your house moves on a regular basis.
Reminds me of the early days of consumer GPS in the 1990's, when they still scrambled
the fine resolution of the position. I remember being parked in a friend's driveway,
and seeing my reported position moving in a circle about a mile in radius. Equipment
was a Delorme TripMate (which, alas, doesn't work any more because it couldn't
handle the GPS 1024-week rollover).

Why not just input a fixed location into your equipment?
Maybe he's living the RV lifestyle in a motorhome? :-)

Andrew, KA2DDO
author of YAAC


 

On Sat, Oct 8, 2022 at 08:57 Andrew P. <andrewemt@...> wrote:
>Why not just input a fixed location into your equipment?

Maybe he's living the RV lifestyle in a motorhome? :-)

Still more missing information from the description and responses.?

He could be setting the station up for mobile deployment for emergency response, and the GPS is the best way to keep track of an itinerant location.?

The Yaesu radio choice however is the weakest link. Yaesu’s decision to make a radio that only does half the job is very strange. That’s just me though.?
--
James
VE6SRV


 

开云体育

HI Andrew,
as another data point,

On 9 Oct 2022, at 12:46 am, Andrew P. <andrewemt@...> wrote:

.
.
I have never seen this before, so if some bug got introduced into the software, I want it fixed ASAP.?

I’m also running an M1 Macbook Pro with an older bluetooth GPS configured in pretty much the same way as Tim and I’m having no similar issues. ?The GPS derived location for me is spot on where I actually am.

I’m using beta178.


Carl.
(vk1kcm)
Canberra, Australia.