Re: [Xastir] Firenet data
Can you explain a little more about what firenet data is and why you might want to see it in an APRS client? On Thu, Jun 14, 2018 at 3:17 PM, Tom Henderson wrote: > Holy smokes! I set up an second Internet interface so I could receive > firenet data, and boy did I! > > Some of the data is easy to figure out, such as lightning strikes. > > Other things, not so much. Weird squiggly tracks, yellow and red squares, > thunderclouds. > > Is there a decent resource out there somewhere that explains what they are? > > > -- > Tom Henderson > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] My Xastir window sure is pretty!
I'm leaving 7 land tonight - my D72a with the rubber duck couldn't be heard by a digipeater from my basement apartment in Redmond, WA. On Fri, Nov 11, 2011 at 1:09 PM, Curt, WE7U curt.w...@gmail.com wrote: It's connected to Firenet. The whole western side of Washington is lighting up. Should be a fun day! -- Curt, WE7U. http://www.eskimo.com/~archer 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] CVS back open, problem compiling latest 2.0.0 today
Thanks Tom, Using GraphicsMagick did the trick. 73 de Joseph M. Durnal NE3R On Thu, Sep 15, 2011 at 5:19 PM, Tom Russo ru...@bogodyn.org wrote: On Thu, Sep 15, 2011 at 04:41:55PM -0400, we recorded a bogon-computron collision of the joseph.dur...@gmail.com flavor, containing: I'm having the same issue: #error QuantumDepth != 16 or 8 I've found the lines in /usr/include/ImageMagick/magick/magick-config.h /* Number of bits in a pixel Quantum (8/16/32/64) */ #ifndef MAGICKCORE_QUANTUM_DEPTH #define MAGICKCORE_QUANTUM_DEPTH 16 #endif I'm not sure what to do with it, I tried removing the # (comments?) but got the same error when I tried to compile again. Maybe I'm missing a step. Editing the config file for magick is the Wrong Thing To Do. The config header describes the options that were used when Magick was built, and changing it will cause applications that use Magick to get the wrong values. You should put it back the way it was when it was installed, or any other software that uses ImageMagick will have build/run problems. Besides, the # lines are not comments, but compiler directives. What that block means is if nobody has defined MAGICKCORE_QUANTUM_DEPTH yet, then define it as 16. The fact must be that someone has already defined it by the time that line is processed, and it's neither 16 nor 8. You can find the actual value being used by typing: Magick-config --version Mine shows : 6.7.1 Q16 which means I have version 6.7.1 with 16 bit quantums. My guess is yours will show either 32 or 64 bit quantums, and maybe even HDRI. If you want to stick with Image Magick, what is required is that you *rebuild* Magick with a quantum depth of 16 or 8. If you're installing Magick from a system repository, you're out of luck with ImageMagick, which tends to be cutting edge and not at all stable --- your system-provided ImageMagick may be even be installed with HDRI support (a very experimental high definition raster format that uses double precision pixel values rather than integer). If you're willing to build ImageMagick from source, use --disable-hdri --with-quantum-depth=16 or --disable-hdri --with-quantum-depth=8 when you configure it. If you're not interested in installing ImageMagick from source code, then try installing GraphicsMagick. Xastir will use that rather than ImageMagick if it finds it, and GraphicsMagick puts more of a premium on stability than the other --- its default pixel depth is 8, and it doesn't even support HDRI rasters. They also don't randomly change their API on us requiring a scramble to fix our code *AND* remain compatible with older versions of IM. Most Xastir developers prefer GM for this reason. There was even once talk about removing IM support and requiring GM instead. That idea had to go because... Some old versions of Ubunutu wouldn't let you install both ImageMagick and GraphicsMagick from repository packages at the same time (they unnecessarily overwrote pieces of each other), but that probably isn't true in any recent vintage system. In those old systems, we couldn't require GM because if the user had any other software installed that required IM we'd have required them out of the user base. On Fri, Feb 11, 2011 at 8:37 AM, David Flood davi...@mindspring.com wrote: Hello Mike, Here's an explanation of that error that Tom Russo posted last December: Check your *Magick install. ?It must have a QuantumDepth of something other than 8 or 16, and Xastir won't work properly if so. ?Apparently some installs of ImageMagick can have 32 or 64-bit quanta. ?GraphicsMagick defaults to 8-bit now, perhaps ImageMagick went to 32 or 64 as default. It'll be in either magick-config.h (for ImageMagick) or magick_config.h for GraphicsMagick). -Original Message- From: xastir-boun...@lists.xastir.org [mailto:xastir-boun...@lists.xastir.org] On Behalf Of wolth...@msu.edu Sent: Friday, February 11, 2011 03:41 Found CVS open again this morning and so I?grabbed the latest source.? I attempted to build it on my Ubuntu 10.10 box and get this problem. map_OSM.c:165: error: #error QuantumDepth != 16 or 8 make[3]: *** [map_OSM.o] Error 1 make[3]: *** Waiting for unfinished jobs mv -f .deps/map_pop.Tpo .deps/map_pop.Po mv -f .deps/main.Tpo .deps/main.Po make[3]: Leaving directory `/home/morphius/xastir/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/morphius/xastir/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/morphius/xastir' make: *** [all] Error 2 ___ 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 -- Tom Russo KM5VY SAR502 DM64ux
Re: [Xastir] CVS back open, problem compiling latest 2.0.0 today
I'm having the same issue: #error QuantumDepth != 16 or 8 I've found the lines in /usr/include/ImageMagick/magick/magick-config.h /* Number of bits in a pixel Quantum (8/16/32/64) */ #ifndef MAGICKCORE_QUANTUM_DEPTH #define MAGICKCORE_QUANTUM_DEPTH 16 #endif I'm not sure what to do with it, I tried removing the # (comments?) but got the same error when I tried to compile again. Maybe I'm missing a step. Thanks, Joe On Fri, Feb 11, 2011 at 8:37 AM, David Flood davi...@mindspring.com wrote: Hello Mike, Here's an explanation of that error that Tom Russo posted last December: Check your *Magick install. It must have a QuantumDepth of something other than 8 or 16, and Xastir won't work properly if so. Apparently some installs of ImageMagick can have 32 or 64-bit quanta. GraphicsMagick defaults to 8-bit now, perhaps ImageMagick went to 32 or 64 as default. It'll be in either magick-config.h (for ImageMagick) or magick_config.h for GraphicsMagick). -Original Message- From: xastir-boun...@lists.xastir.org [mailto:xastir-boun...@lists.xastir.org] On Behalf Of wolth...@msu.edu Sent: Friday, February 11, 2011 03:41 Found CVS open again this morning and so I grabbed the latest source. I attempted to build it on my Ubuntu 10.10 box and get this problem. map_OSM.c:165: error: #error QuantumDepth != 16 or 8 make[3]: *** [map_OSM.o] Error 1 make[3]: *** Waiting for unfinished jobs mv -f .deps/map_pop.Tpo .deps/map_pop.Po mv -f .deps/main.Tpo .deps/main.Po make[3]: Leaving directory `/home/morphius/xastir/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/morphius/xastir/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/morphius/xastir' make: *** [all] Error 2 ___ 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] Please consider ...
I found a little fix - WIDE1-1,MD2-2 works fine. I should have thought of that before. That will still bounce me off of the two home stations that can hear me direct. That is why I use WIDE2-1 instead. I'll give the latest CVS a shot when I get a chance. On Fri, Feb 12, 2010 at 12:14 AM, Curt, WE7U curt.w...@gmail.com wrote: 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 ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Please consider (plus AP codes)
That is a state code. MD2-2 works (well, should work) just like WIDE2-2, but only digipeaters in Maryland would digipeat it. And VAn-N for Virginia, WVn-N for West Virginia, and so on. See: http://www.aprs.org/fix14439.html Fix #4 73 de Joseph M. Durnal NE3R On Fri, Feb 12, 2010 at 9:32 AM, Kurt Savegnago ksav...@sbcglobal.net wrote: Ah, Am familiar with the usual statements but what is MD2-2 supposed to mean/do? As an aside. I've been looking to decode the APX codes for a heck of a long time. A fellow had a page up but it went down. I finally found a source here that has them listed so I can look up the equipment being used if not spelled out in the statement. http://aprs.org/aprs11/tocalls.txt I was doing a search on the MD2-2 statement but couldn't find an explanation. Looked again for AP codes and one of the hits was the site above. Sorry about hijacking the subject but I've looked for months since my prior source went down to find the equipment codes. I only did it in case someone else tries a search. Might make it easier to find. Kurt KC9LDH --- On Fri, 2/12/10, Joseph M. Durnal joseph.dur...@gmail.com wrote: From: Joseph M. Durnal joseph.dur...@gmail.com Subject: Re: [Xastir] Please consider ... To: Xastir - APRS client software discussion xastir@lists.xastir.org Date: Friday, February 12, 2010, 5:19 AM I found a little fix - WIDE1-1,MD2-2 works fine. I should have thought of that before. That will still bounce me off of the two home stations that can hear me direct. That is why I use WIDE2-1 instead. I'll give the latest CVS a shot when I get a chance. ___ 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] 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] Linux Journal Article, linked to Xastir homepage
You are going to the right place, the link is right there on the Main_Page. Great article. I was writing a long comment but I closed the browser by accident (tabbed browsing has its drawbacks). 73 de Joseph M. Durnal NE3R On Sun, Jan 31, 2010 at 10:45 AM, David Aitcheson david.aitche...@gmail.com wrote: Curt, Clicking on http://www.xastir.org gets one sent to http://www.xastir.org/wiki/index.php/Main_Page with no hope of ever getting to anything but the wiki. Dave - KB3EFS On Sun, Jan 31, 2010 at 5:22 AM, Curt, WE7U curt.w...@gmail.com wrote: The January Linux Journal Xastir article is now available on LJ's site, so I linked it into our Xastir homepage. Enjoy! http://www.xastir.org -- Curt, WE7U. http://www.eskimo.com/~archerhttp://www.eskimo.com/%7Earcher 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 ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] APRS for Bike Tours
I've tried to get APRS involved in some events, but I find the hard part is getting folks to volunteer :). Used xastir at the finish line of a 40 mile hike, had a few other APRS stations along the way. I hiked the last 20 miles myself, carrying a D7 w/ GPS. http://cryptojoe.blogspot.com/2009/05/twenty-mile-hike.html 73 de Joseph Durnal NE3R On Fri, Jun 19, 2009 at 7:33 PM, Jason Godfreygodfr...@gmail.com wrote: Hello. I was just browsing the list archives, and saw this question from Mike Benonis from about two weeks ago: By the way, as a more general question to those who have used APRS for bike tours/races, does anyone have any tips for a smooth event? I'm not sure if it is too late for him, but since we just had the Minnesota MS150 last weekend I thought I would comment. In past years we've had APRS beacons on all of our sag wagons and few other key vehicles and a full APRS station at net control. This year we decided to expand and add a full APRS station at each rest stop as well as on the Incident Response Team vehicles (the IRTs may of had a full station past years, I forget.) Another key decision was was to add a dedicated APRS op to net control. The expanded use APRS helped quite a bit, especially in the view of our longtime net control supervisor. He felt it reduced his workload noticeably. Using APRS messaging for lower priority messages kept traffic off of our UHF voice backbone. The use of objects to track rider pickups, incidents, and other issues helped with situational awareness, and in the case of IRT's - finding where we sent them. A couple of points of things that can help for a smooth event: 1. Training and testing before the event. Make sure the equipment works and the operators who are going to be using it know how to. 2. Check digipeater coverage. We had to add in some for the event. (And unfortunately one wasn't working, which impacted coverage on Sunday.) 3. For net control at least - Listen to both RF and IGATE if you can. Sometimes messages/objects come in one interface and not the other. 4. Having a dedicated APRS op at net control is very helpful. The person(s) running the voice net is too busy to use APRS effectively by himself. 5. Use APRS for more then just tracking vehicles. Objects and messaging are useful. I think that covers the highlights. - Jason, N0RPM -- I have learned to use the word 'impossible' with the greatest caution. -- Wernher von Braun ___ 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
