Roy, You found the thing I saw immediately, so all is good. You probably just need to make sure the device is in full view of the sky, at least to get the initial fix and the almanac

Lynn, I appear to have found the answer. Looking at the data file I attached I noticed one of the sentences mentioned only a single satellite was in view, Of course this is not enough for a fix. I

Thanks, Lynn GPS data attached. regards, Roy

Please open and enable the NMEA trace log and capture some of the sentences from it. I can compare them to the code and figure out which one is saying there is no fix. And it may be

Using Win 10/64 on a Panasonic Toughbook with built-in gps. Windows sees the gps on Com3, 4800b and other programs have no problems using the gps. The NMEA port is set to Com3, 4800b and the GPS is

Hi Lynn. Only to let you know I have tried APRSISMO on my Samsung phone with Mobilinkd + HT. It works great. Many thanks, 73, de J, M0IPU YO3FCA

“There is also a problem of not using WIDE1-1. In Northern California, a majority of the digipeaters do not respond to anything more than WIDE1-1, So if your mobile has a path of WIDE2-1, you will

Your first sentence is correct. Beginning a path with WIDE1-1, is only for mobiles and not for fixed stations. Fixed stations can more efficiently just use WIDE2-2 and it makes every packet 7 bytes

"If however high powered stations use WIDE1-1, there’s a potential for many home stations to hear the request and act upon it, causing lots of potential noise on the channel. The solution then is to

That’s a loaded question as you can see from Arnold’s reply. How do you define proper? Is proper what the original intent was, or is it what people have decided the intent should have been, or

There is also a problem of not using WIDE1-1. In Northern California, a majority of the digipeaters do not respond to anything more than WIDE1-1, So if your mobile has a path of WIDE2-1, you will

Now I am curious what is the proper WIDE X-X setting for fixed stations? From your comments I assume WIDE1-1, WIDE2-1 for a fixed station is not proper? Most stations in my area

@James Thank you for this info. I have learned something from your post. I did not know this? 73 KD7TWW Vince

And to clarify another point, no fixed station should be using WIDE1-1 as a hop request. WIDE1-1 is intended to be used as a request from low powered stations for an extra helping hand from home

To expand upon the above, try putting the callsign of the digi you want to digipeat you, and then NOGATE in the path after.i.e. LARES,NOGATEThen no-one who hears you should gate you to the internet.

Rather than using WIDE1-1 as a path, try putting in just the callsign of the digi you are trying to reach. For example, just put in LARES for the path. HOWEVER, if the nearest digi is also an IGate,

Is there a way, on my end, to temporarily stop a specific digipeater from digipeating my RF beacon (and also stop iGating me if possible)? I'm testing out a yagi and an amp/preamp setup to see if I

Yes, -b/call* will block all -SSIDs for the specified callsign. But again, only in the Additional Filter for the APRS-IS.  If you receive a packet via RF, it will be processed and displayed. Lynn

There is one callsign sending a non APRS position that makes an altitude ring, not unlike a balloon or aircraft. Dang nuisance, and the position is off by a whole state! Currently, all I can do is

Made me laugh, reminded me of a feature on APRSdos program version that Bob WB4APR had included. Basically, the program allowed the user to set a range ring and it would generate an alarm if the area