Re: [Xastir-dev] interface igate config?
On Thu, Feb 11, 2010 at 9:14 AM, Curt, WE7U curt.w...@gmail.com wrote: Dreaming a little bit: The nicest (for me) setup would be a separate igating dialog where I could turn on/off global gating, turn on/off individual directions for each interface, and perhaps do some cross-wiring between interfaces for those special instances where you're supporting a public service event or emergency and need to gate RF-RF. That last has been asked for and we've never had the capability. Combine the above with named interfaces (any string for a name) and you'd have something easy to read maintain. We can make this a requirement. Got anything more specific (e.g. sketch of a dialog), or do you want me to try and describe this to them? This goes for anything and anyone else, too. If anyone has a wish list for data display/filtering, dialogs, etc let me know. We're implementing a small subset of xastir, but anything we do implement is wide open. I'm a bit unsure if I should be posting this sort of offer to the main list, though. -Jason kg4wsv ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
Re: [Xastir] Please consider ...
On Thu, Feb 11, 2010 at 7:58 AM, Joseph M. Durnal joseph.dur...@gmail.com wrote: Xastir annoyed me into using a more obnoxious path than I wanted to. As best I recall, this is partly from an idea from wb4apr to do exactly that - annoy the user into using a path recommended by him. -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider ...
On Thu, 11 Feb 2010, Joseph M. Durnal wrote: Xastir annoyed me into using a more obnoxious path than I wanted to. I'm probably running an older version, but it seemed to freak out when I used WIDE2-1,MD2-2 and suggested WIDE1-1,WIDE2-2. While both paths would get my packets where I needed them to go, the first path would light up 9 or 10 digipeaters and the second, I lost count after about 20. There are two things wrong here: One is that the Xastir code should be working properly off either of those *2-1,*2-2 paths without annoying you about your path selection. I can take a look at that bit of code when I have a bit of free time. The second: Being able to count 20 digipeaters on transmit means that the digi's do _not_ have DWAIT set to 0, so are waiting on each other before transmitting... This is not supposed to happen. They are supposed to transmit immediately and all at once. You ideally should get three digipeat slots out of that path, with lots of digipeaters transmitting in at least the last two slots (probably only one or two digi's repeating you during that first slot). Perhaps there are lots of home fill-in digi's that are set up improperly, or you have multiple types of digipeater firmware/software that don't play well in the system together, therefore the fratricide that Bob is always talking about as beneficial ain't happening. After looking up that word, siblicide seems more descriptive of the desired situation, but fraticide is used in the military and Bob's a Navy guy. Here's Bob talking about it: http://www.tapr.org/pipermail/aprssig/2009-October/031823.html Here's another (near the top): http://on1gl.dyndns.org:7373/cmd?cmd=READ+OZAPRS+376 -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] work-around for right-click problem under Cygwin
Rob, Is this a true PS/2 keyboard or a USB one? This sounds like some sort of negative interaction in keyboard control lines like used to happen with some printer ports and PS2 keyboards. -Original Message- From: xastir-boun...@lists.xastir.org [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Rob Locher W7GH Sent: Tuesday, February 09, 2010 17:22 I discovered a work-around. The purpose of this email is to document the work-around in case someone else has the same problem in the future. The work-around is to launch XASTIR with Num Lock on. Then when I right-click on an icon in XASTIR I get the familiar warning to turn off Caps Lock, Num Lock, and Scroll Lock. Then when I turn off Num Lock everything works fine. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider ...
When I first started using APRS, I was a bit of a path abuser, that was before someone took the time to explain how it worked. A wide1-1 packet from my station can relay off of 4 digipeaters, that is why I don't use it from my fixed station. WIDE2-1 works well for me, 2 digis often hear me, one in Virginia and one in Maryland. The local Maryland digi that I hit is in an area that could lose power during this winter event. But several other Maryland digis can hear the Virginia digi that can hear me, but want to make sure the packets get back to MD, hence the MD2-2. Sure, the WIDE2-2 works fine, but my packets are probably being heard on wide digis in Ohio, Tennessee, NY, ... you get the picture. The 20 or so is based on digis that can hear each other. A couple of years ago I did some testing on the impact of my packets (late at night so I wouldn't bother anybody). 3 WIDE hops from my station at 5 watts gets out pretty far. Sorry to complain, it was probably an e-mail I shouldn't have sent - just one of those things that was driving me nuts while I was in the middle of trying to do something (now I have to go over to APRSSIG with my head hung low and say I'm sorry for something else). 73 de Joseph M. Durnal NE3R On Thu, Feb 11, 2010 at 9:56 AM, Curt, WE7U curt.w...@gmail.com wrote: On Thu, 11 Feb 2010, Joseph M. Durnal wrote: Xastir annoyed me into using a more obnoxious path than I wanted to. I'm probably running an older version, but it seemed to freak out when I used WIDE2-1,MD2-2 and suggested WIDE1-1,WIDE2-2. While both paths would get my packets where I needed them to go, the first path would light up 9 or 10 digipeaters and the second, I lost count after about 20. There are two things wrong here: One is that the Xastir code should be working properly off either of those *2-1,*2-2 paths without annoying you about your path selection. I can take a look at that bit of code when I have a bit of free time. The second: Being able to count 20 digipeaters on transmit means that the digi's do _not_ have DWAIT set to 0, so are waiting on each other before transmitting... This is not supposed to happen. They are supposed to transmit immediately and all at once. You ideally should get three digipeat slots out of that path, with lots of digipeaters transmitting in at least the last two slots (probably only one or two digi's repeating you during that first slot). Perhaps there are lots of home fill-in digi's that are set up improperly, or you have multiple types of digipeater firmware/software that don't play well in the system together, therefore the fratricide that Bob is always talking about as beneficial ain't happening. After looking up that word, siblicide seems more descriptive of the desired situation, but fraticide is used in the military and Bob's a Navy guy. Here's Bob talking about it: http://www.tapr.org/pipermail/aprssig/2009-October/031823.html Here's another (near the top): http://on1gl.dyndns.org:7373/cmd?cmd=READ+OZAPRS+376 -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at! http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] work-around for right-click problem under Cygwin
On Feb 11, 2010, at 12:07 PM, David Flood wrote: Rob, Is this a true PS/2 keyboard or a USB one? This sounds like some sort of negative interaction in keyboard control lines like used to happen with some printer ports and PS2 keyboards. -Original Message- From: xastir-boun...@lists.xastir.org [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Rob Locher W7GH Sent: Tuesday, February 09, 2010 17:22 I discovered a work-around. The purpose of this email is to document the work-around in case someone else has the same problem in the future. The work-around is to launch XASTIR with Num Lock on. Then when I right-click on an icon in XASTIR I get the familiar warning to turn off Caps Lock, Num Lock, and Scroll Lock. Then when I turn off Num Lock everything works fine. I can speak to this condition. I recently put Cygwin on my new HP 17 laptop. I also did a CVS install of xastir (1.9.9). As an aside, I copied my Texas Tigerline 2008 shapefiles (17.8gb) into the maps folder. And, I did copy my customized dbfawk files (even though the current CVS versions are quite usable) into the config folder. Finally, I ran a custom sed script *after* the first-time map index by xastir to get the layers of the index.sys file corrected. I saw the freeze-up with a right-click in the map region as others have mentioned. I remembered someone saying to turn on Num-Lock, get the warning message about turning it off. I turned on Num-Lock, got the warning, turned off Num-Lock as instructed. The right-click started working. The only thing different is that I have to hold down the right-button to stay in that mode. It's not a right-click-on, left-click-off as under linux. I did not have to turn on Num-Lock before starting xastir. I can do it after xastir is running. So, it appears to not necessarily have anything to do with the type of keyboard used (PS2 vs USB), but I could be wrong - been there, done that! To be honest, I am not sure what kind of keyboard controller is used in that laptop. It could be USB-centric or it could be PS2-centric. Finally, here are some thoughts that I have put off writing about until now. I really like this setup. That is such good news about the upgraded Cygwin. And, indeed it works slick for xastir. I lashed up an OT+ with KISS firmware installed, mated with a VX-1R (at 0.5 watts) The deviation is at 2.55kc high tone with the low tone about 2.1kc (as it should be - no twist as I've experienced with my FT-1500s). That's the best I could get out of the OT+ without doing any circuit mods. Close enough, as it hits the digi just fine which is about 8 miles due east of me. This is all setting on my kitchen table as a temp setup for testing. I had installed VirtualBox, but was less than satisfied with it. It was when I saw the blurb about the upgraded Cygwin, that I gave it a shot and am so glad I did. The main impetus of my effort was to get other local hams going with xastir, rather than some other PC-centric APRS client, but lessen the issues of working with *nix. Consider me a satisfied customer. 73 - Dale. KG5LT ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider ...
On Thu, 11 Feb 2010, Joseph M. Durnal wrote: Sorry to complain, it was probably an e-mail I shouldn't have sent - No, the other developers and I like to hear when a feature is not working as designed or as expected. Often it's a disconnect between the developers and the users, sometimes a training issue. This time it sounds like the code needs a bit of a re-work in that area to fix it for your particular instance and others like it. just one of those things that was driving me nuts while I was in the middle of trying to do something (now I have to go over to APRSSIG with my head hung low and say I'm sorry for something else). Been there, done that. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider ...
On Thu, 11 Feb 2010, Joseph M. Durnal wrote: Xastir annoyed me into using a more obnoxious path than I wanted to. I'm probably running an older version, but it seemed to freak out when I used WIDE2-1,MD2-2 and suggested WIDE1-1,WIDE2-2. I just tried the above and sure enough, the WIDE2-1,MD2-2 path triggers the annoyance popup (should we add a talking paperclip graphic to that dialog?). WIDE1-1,WIDE2-2 does not. Obviously the code that tries to figure out maximum path length is triggering on the first of each number-set instead of the second. That code was most likely written before the 2-1 path element became prevalent. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] work-around for right-click problem under Cygwin
On Feb 11, 2010, at 12:07 PM, David Flood wrote: Is this a true PS/2 keyboard or a USB one? This sounds like some sort of negative interaction in keyboard control lines like used to happen with some printer ports and PS2 keyboards. Hi David! I'm using a USB keyboard. On Thu, 11 Feb 2010 11:32:12 -0800, Dale Seaburg kg...@verizon.net wrote: I saw the freeze-up with a right-click in the map region as others have mentioned. I remembered someone saying to turn on Num-Lock, get the warning message about turning it off. I turned on Num-Lock, got the warning, turned off Num-Lock as instructed. The right-click started working. The only thing different is that I have to hold down the right-button to stay in that mode. It's not a right-click-on, left-click-off as under linux. I did not have to turn on Num-Lock before starting xastir. I can do it after xastir is running. Hi Dale! I don't have that particular feature; I get right-click-on, left-click-off. Finally, here are some thoughts that I have put off writing about until now. I really like this setup. That is such good news about the upgraded Cygwin. And, indeed it works slick for xastir. [snip] I had installed VirtualBox, but was less than satisfied with it. It was when I saw the blurb about the upgraded Cygwin, that I gave it a shot and am so glad I did. The main impetus of my effort was to get other local hams going with xastir, rather than some other PC-centric APRS client, but lessen the issues of working with *nix. Consider me a satisfied customer. I concur! I spent four years as a professional software developer, and in my opinion the future belongs to software that will run on any platform. XASTIR fills the bill nicely as far as I'm concerned. I thought about trying other Windows APRS software, but the app with the most market share hasn't been maintained since the author's key fell silent in 2004, and the app seems to require purchasing expensive mapping software that I've never heard of to make it work. (Thanks but no thanks, UI-View32.) XASTIR's installation procedure for Windows is clunky, but I understand why. If I had more time available I would volunteer to streamline the installation procedure for Windows users. Considering that XASTIR's authors are all busy people improving and maintaining the software in their free time for nothing, it really is excellent software. Bravo! And Bravo to all the people who offer friendly advice on the reflector! 73, - Rob W7GH ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider ...
On Thu, 11 Feb 2010, Curt, WE7U wrote: I'll try to figure out a proper fix to the code itself (check_unproto_path in util.c) and get it checked into CVS. I checked a fix into CVS. Give it a shot and see if it fixes your problem. I think it will. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
