Re: [Xastir] Position rate question
I will look at the routine also. Many eyes make a load light (duck). Plus, outside they are talking about temps with THREE digits here in Brew City today. Plus, winds in the 15-30 MPH range - can you spell "convection oven"? The threshold setup is akin to windowing. I may be going over previously discussed material here, so forgive me. Fixed position operation is simple, beacon every x minutes. Moving, it should be either time or distance traveled. When you have a GPS unit sending data every second or two, this confounds the issue. Turning is the issue with these beacon rates. You can turn at an intersection and be done with the turn in two seconds. Before I dig myself a hole (It's not Black Friday), let me see what the code is really doing. Maybe we can all participate in getting this to work. 73 from 807 (breakfast bell), Richard, N6NKO Tom Russo wrote: On Sun, Jul 08, 2007 at 12:01:47AM -0600, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: Curt, since you are so intimate with the code, can you point me at the relevant section of Xastir code that deals with SmartBeaconing and CornerPegging? I'll have a look at it to see if how the logic is processed. It's in db.c, the routine "compute_smart_beacon". ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Position rate question
On Sun, Jul 08, 2007 at 12:01:47AM -0600, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Curt, since you are so intimate with the code, can you point me at the > relevant section of Xastir code that deals with SmartBeaconing and > CornerPegging? I'll have a look at it to see if how the logic is > processed. It's in db.c, the routine "compute_smart_beacon". -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Position rate question
James Ewen wrote: When do you plan on getting your 18 wheeler up to 240 MPH? If you want one position report every 5 miles at highway speed, why not set your high speed to 60 MPH, and high rate to 300. When you exceed the high speed, your beacon rate will not go less than 300 seconds. I guess you will always beacon every 5 miles, where my settings beacon closer than every 5 miles when exceeding the high speed rate. Oh -- I've been using 240 as the high speed for some years now. Originally with the idea that I might get my HamHUD up in a Cessna at some point. It's never happened, but it might. Someday. 7 3 Earl -- Earl Needham KD5XB Clovis, New Mexico DM84jk ZUT ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Position rate question
> I running mobile in an 18-wheeler as KD5XB-11. SmartBeaconing is enabled, > and set for high speed of 240 MPH with a beacon rate at that speed of once > every 75 seconds. (I calculate that out to one position report every 5 > miles.) When below the low speed threshold of 2 MPH, I should be getting a > positinb report every 30 minutes. When do you plan on getting your 18 wheeler up to 240 MPH? If you want one position report every 5 miles at highway speed, why not set your high speed to 60 MPH, and high rate to 300. When you exceed the high speed, your beacon rate will not go less than 300 seconds. I guess you will always beacon every 5 miles, where my settings beacon closer than every 5 miles when exceeding the high speed rate. Bring your low speed threshold up to about 5 MPH. This is most likely the source of the numerous zero speed triggered reports. > When I right-click on my own station and get station info, the list of > recent packets received fills up really quickly with 0 MPH reports. For > instance, I've been sitting here in Shreveport for about 45 minutes, and the > entire list is made up of 0 MPH reports. I really expected to see only 1 or > 2. > > So -- is this something I have mis-configured? A bug? Or am I > interpreting this list incorrectly? Probably a combination of the low speed threshold being set too low, and possibly a logic problem in the programming. I, too, have had trouble with the smartbeaconing parameters. A long time ago I saw exactly the same behavior you see, and disabled smartbeaconing at that time. Near as I can tell, somehow the random fluctuations of GPS fixes seem to allow Xastir to beacon very, very often when stationary if you don't set your smartbeaconing just so. But I never spent any time figuring out why. CornerPegging watches for changes in direction that exceed the threshold. Random position changes due to GPS wandering look like you are making changes in your direction of travel. In the HamHUD, the first thing we look for is if the current speed is lower than the low speed threshold. If it is, we set the beacon rate to the low rate. We never look at any other parameters after that. Changes in direction only get processed if we are exceeding the low speed threshold. Curt, since you are so intimate with the code, can you point me at the relevant section of Xastir code that deals with SmartBeaconing and CornerPegging? I'll have a look at it to see if how the logic is processed. In the mean time, there are a couple pages describing SmartBeaconing and CornerPegging on the APRS Wiki... http://info.aprs.net/wikka.php?wakka=SmartBeaconing James VE6SRV ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Position rate question
On Sat, Jul 07, 2007 at 10:08:46PM -0600, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > > I've noticed that when I stop I'm getting more positions sent out than > I > expected. > > Running Xastir 1.9.0 under Kubuntu 7. > > I running mobile in an 18-wheeler as KD5XB-11. SmartBeaconing is > enabled, > and set for high speed of 240 MPH with a beacon rate at that speed of once > every 75 seconds. (I calculate that out to one position report every 5 > miles.) When below the low speed threshold of 2 MPH, I should be getting a > positinb report every 30 minutes. > > When I right-click on my own station and get station info, the list of > recent packets received fills up really quickly with 0 MPH reports. For > instance, I've been sitting here in Shreveport for about 45 minutes, and the > entire list is made up of 0 MPH reports. I really expected to see only 1 or > 2. > > So -- is this something I have mis-configured? A bug? Or am I > interpreting this list incorrectly? I, too, have had trouble with the smartbeaconing parameters. A long time ago I saw exactly the same behavior you see, and disabled smartbeaconing at that time. I've recently re-enabled it on the rare occasions that I actually run a laptop in my truck instead of just the D700. What do you have your turn threshold, turn slope, and wait time set to? The default wait time of 5 seconds is absurd, and should not be left there. Also, Xastir's algorithm for some reason multiplies the turn slope by 10 where the original HamHud implementation does not. So you need to use a smaller turn slope in Xastir than you did in your HamHud. Near as I can tell, somehow the random fluctuations of GPS fixes seem to allow Xastir to beacon very, very often when stationary if you don't set your smartbeaconing just so. But I never spent any time figuring out why. Supposedly the fact that you're at 0mph *should* disable any corner pegging and only beacon at the slow rate, but as near as I can tell the little hops that the position fix confuse the issue and make it look like you're *not* stationary just enough for the code to think you've turned. But it doesn't make any sense. I have found, though, that setting the wait time to 30 seconds (the most frequently I *ever* want to beacon, no matter how many turns I make) has decreased the problems I have had with Xastir's smartbeaconing. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
