开云体育

Greetings, all. Just letting everyone know the new YAAC mailing list and the YAAC software author aren't dead yet (although I am declaring the old mailing list dead now). I'm still cleaning up the code after debugging and fixing a _very_ annoying GUI rendering issue introduced by a recent patch to the Java runtime, plus usual bugfixes, and some updates to support large-scale events as discussed on the aprssig@... mailing list a couple of weeks ago. But I hope to have build 143 of YAAC out before Christmas. Whether the large-scale event support plugin will be ready by then is a different question. Also, for all those who have asked for the ability to copy YAAC configurations from one system to another, I have reluctantly (i.e., dragged kicking and screaming :-) started implementing an experimental means to re-import a YAAC configuration saved by the File->Configuration->Export to XML File option. The difficulties were in ensuring that callsign-SSID assignments weren't duplicated on multiple active stations by negligence, and accounting for operating system changes (i.e., no /dev/tty devices on Microsoft Windows or COMn ports on Linux) during the transfer, while still making it generic to support arbitrary additional configuration data from plugins (and enhancing all relevant plugins to support it). It's a big issue. So, you'll have an upgrade with some big new features soon. It's been a long road since I first officially released YAAC back in 2012. Thanks, all, for making it worth the effort. Andrew Pavlin, KA2DDO author of YAAC

Got it loaded in a Linux Mint computer. Using an MFJ-1274 TNC with RAM upgrade and latest (1.1.9) TNC-2 firmware. I went through the configuration wizard and set everything up, proper serial port, speed, etc. With the Serial_TNC port page, I hit the TEST PORT button and see the data coming from the TNC. The text is somewhat garbled and each line overwrites the previous line, making it hard to read. I see callsigns, site aliases, and seemingly random characters. But I get no data showing on the map. I check View > Raw Packets and nothing shows on the window. Xastir shows all kinds of data, so I know the TNC and radio configurations should be right. Any ideas where to check? tnx es 73, Michael WA7SKG

I have a mixture of operators all on an island aredn mesh network; some mobile mesh capable. Is it possible to have YAAC transmit and receive positions over the mesh as well as RF? Say a mobile mesh raspberry pi running YAAC and a gps receiver able to be tracked by other YAAC users on the mesh and gated to the RF? Thanks for any advice on this. Bill KW4MP

I was getting annoyed at the old OSM tiles that were available directly through YAAC so I started downloading entire U.S. states via Geofabrik. First problem I noticed is that when I imported my Yukon pbf, YAAC seemed to not show any mapping data that I already had downloaded in the way of tiles. When I then imported the Alaska pbf the Yukon went away. This behavior was not expected as I would have assumed these pieces to have fit together instead of one being thrown out for the other. Is this a bug or am I missing something here? 73, Eric WG3K

next beta build#143 of YAAC ("Yet Another APRS Client"), created 2019-Dec-23 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. add support hooks for upcoming large-scale event distributed database plugin (not yet available) and demonstration plugin (now available). 2. clean up more issues discovered by University of Maryland findbugs utility, including in some plugins. 3. fix incorrect unit scaling in PositionlessWeatherReport. 4. separate digipeaters and I-gates in Station Category filter. 5. add first digipeater filter (still keeping last digipeater filter). 6. fix identification of a NewN-n digipeat alias. 7. add warning message when running YAAC in non-GUI mode, so users don't think it's stuck when it's actually running without a user interface. Especially important for Unix/Linux users that try to run YAAC without a graphical X-Windows desktop. 8. ensure weather data is consumed, even for delayed weather packets with timestamps that is pre-empted by later packets without weather data from the same station. 9. add configurable ability to ensure tactical names (aliases) for stations are preserved over YAAC restarts. 10. report the specific Java runtime version in use at YAAC startup time; in case there are any weird problems causing it to fail to startup, at least some info can be collected to help debug it. 11. add experimental means to copy a YAAC configuration from one installation to another, trying to apply reasonable precautions to avoid duplicate stations interfering with each other. Add javadocs to explain hooks needed in existing code to support the config importer. 12. on configuration export, ensure that user meant to overwrite an existing file before proceeding to do so. 13. fix NullPointerException in GPS processing through GPSD when the GPS doesn't have enough of a fix to report VDOP and PDOP. 14. fix weird font rendering issues where spaces didn't take up any space (caused by recent Java Runtime patch to all releases 8 through 11). 15. fix displaying of locally-created objects with area symbol codes when digipeater echo-backs aren't occurring (such as for Internet-only installations of YAAC). 16. fix layout problems for configuration panels if the user reduces the size of the configuration dialog window "too much". Now controls won't be lost from undersized windows, because scroll panes will allow the missing controls to be reached by scrolling the panels. 17. add smarts to the configuation wizard to prevent creating 2 I-gate ports in YAAC (can still be done in expert mode, but not a good idea unless you need to listen to FireNet whyile being connected to the regular APRS-IS backbone). 18. make use of KISS work-around for Kenwood MCP (Memory Control Program) protocols (so an AX.25 packet can't accidentally lose some of its bytes to an MCP command to the radio) optional, because some other TNCs can't handle the work-around as being an illegal KISS escape. 19. add extra debugging logic if OSM tile files aren't read correctly. 20. ensure port driver errors causing events (such as Internet connection lost and restored) are reported properly when YAAC is running in non-GUI mode. 21. add Javadoc warnings to buffered input stream classes regarding using them with intermittent real-time input streams (such as socket connections), as some packets might be delayed until enough traffic to fill an entire buffer arrives. 22. handle a few more OpenStreetMap non-standard amenity type names and map them to the standard ones, and recognize some more obscure standard keys (diplomatic="", emergency=""). 23. performance-tune the OpenStreetMap PBF importer some more. 24. stop keeping the YAAC builds compatible with Java 6, and move them up to Java 7 (not 8, due to people running antique computers). 25. include the new demonstration plugin. This is designed for stand-alone demonstrations of YAAC at hamfests, etc., and allows running an automatically-advanced PowerPoint slide show on one side of a split window and cycling through chose

I finally managed to pry the archives of the old mailing list out of Yahoo's hands. Is there any interest in preserving these historical emails? I'm not sure how to get them into groups.io, and it would still be a fair amount of work to put them on my website. I will keep them regardless, should opinions change in the future. Andrew, KA2DDO author of YAAC list moderator

Mark Lunday, WD4ELG Greensboro, NC FM06be wd4elg@... http://wd4elg.blogspot.com SKCC #16439 FISTS #17972 QRP ARCI #16497

Apologies if this is a repeat, I tried to post via web earlier and I do not see my post in the groups history yet. I tried to send myself an email to wd4elg@... (had to try several times before I was heard, but I was heard), but the email never made it through. I did see the packet get acknowledged, but then the YACC took over with a mind of its own and started transmitting again and again. Why not stop when the first digi-peater acknowledged it at 0531? APRS.FI message history shows that it went into the system. (I tried this with UISS software earlier tonight for three different email addresses and nothing went through then either). 12/26/2019 5:27 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0001 12/26/2019 5:28 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0001 12/26/2019 5:29 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0002 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0003 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0004 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0005 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0006 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0007 12/26/2019 5:30 WINNSB>APDW15,W4SNA-3,WIDE2:}WD4ELG>APJYC1,TCPIP,WINNSB*::EMAIL :wd4elg@... Email test v2{m0006 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0001 12/26/2019 5:30 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0002 12/26/2019 5:30 WINNSB>APDW15,ANDMTN:}WD4ELG>APJYC1,TCPIP,WINNSB*::EMAIL :wd4elg@... Email test{m0001 12/26/2019 5:31 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0003 12/26/2019 5:31 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0004 12/26/2019 5:31 WINNSB>APDW15,W4SNA-3,WIDE2:}WD4ELG>APJYC1,TCPIP,WINNSB*::EMAIL :wd4elg@... Email test v2{m0003 12/26/2019 5:31 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0005 12/26/2019 5:31 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0006 12/26/2019 5:31 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0007 12/26/2019 5:32 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test{m0002 12/26/2019 5:33 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0003 12/26/2019 5:33 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0004 12/26/2019 5:33 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0005 12/26/2019 5:33 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0006 12/26/2019 5:33 WD4ELG>APJYC1::EMAIL :wd4elg@... Email test v2{m0007 Why is some text appearing as pink in the packets/sniffer window? How does ISàRF gating work? RFàIS gating? Why does the software transmit data randomly through my rig, when I do NOT have beacon turned on? Is that the RFàIS gating? ISàRF gating? How do I know who is on the other end of my transmissions? I made sure this gating feature is turned off but the software is still sending out packets at random times and not showing what is being sent from me in the packet window. (no info in the manual) How do I send a single position report without repeated beacon? (did not find that in the manual) What should I select for my DigiPeat alias should I use? I entered WIDE2-2 because I see that often…should I ignore this if I am not using RFàIS? Under SETUPàBEHAVIOR, what am I enabling when I pick “Message to send to acknowledge text message (check o send without human intervention”? Looking at the Raw Packet Sniffer, how can I determine which signals are digipeated and which are not? I see filters, under station category, what should I choose? Just want to see the stations that I am hearing directly, so I can get an idea of propagation like on the map here without the digipeated signals: http://aprs.mennolink.org/ Mark Lunday, WD4ELG Greensboro, NC FM06be wd4elg@... http://wd4elg.blogspot.com SKCC #16439 FISTS #17972 QRP ARCI #16497

I previously set a monitoring frequency on my beacon but now I want to remove it. Every time I delete it and tab to the next field the frequency returns. Why does this happen? 73, Eric WG3K

Another question. On my base configuration, at the bottom of the screen, there are three boxes, TO, VIA, and Message, followed by a SEND button. I can put in a callsign, a path, and some text, hit send and it goes to that station. However, on my just configured mobile, only the TO and VIA boxes are visible. The TEXT box and the SEND button are missing. Is this a configuration issue? Or because I am using a much smaller screen (22" on base, 7" on mobile)? Thanks, Michael WA7SKG

In going through the configuration part of the manual, I see in the BEACON tab, there is a choice for Station Status if you are using the MicE Beacon Type. I haven't found everything yet in this manual. Is there a quicker way to set the status than going through the whole configuration routine? It would be nice to have something like macro buttons or something on the screen to change this on the fly. I'm sure I am missing something, as this seems like a fairly dynamic thing that should be readily changeable. tnx es 73, Michael WA7SKG

HOWDY GUYS; On sending a msg to a fellow ham, does this program show a reply from the other station? Also what does OPEN NET mean on the message board. TNX POB/K8LEN

Hopefully this message doesn't show up twice. My first one didn't seem to get through. I'm trying to get the mini-webserver functionality to work, but have been unsuccessful. I first tried accessing from the default port of 8008, and then assigned a different port and tried that one. I had no luck in either case. Is there something that I'm overlooking to make this work? I did some small amount of research, but didn't find anything. I'm running YAAC 1.0-beta 143 on a Raspberry Pi 2B with a Raspbian Buster build. Greg WB6ZSU

Note that you can't share the TNC between YAAC and javAPRSSrvr; only one program can own the serial port connected to the TNC. Assuming you're going to have YAAC control the TNC, create a port of type Serial_TNC and specify the serial port device name connected to the TNC, your callsign-SSID, and the correct baud rate. You don't connect the TNC and YAAC to the Linux AX.25 kernel; all the AX.25 logic is in YAAC so you don't use kissattach or /etc/axports. If you want YAAC to forward the received packets to javAPRSSrvr, also create a port of type APRS-IS and connect it to your local javAPRSSrvr's client port. Hope this helps. Andrew, KA2DDO author of YAAC Sent from my Verizon 4G LTE smartphone

next beta build#144 of YAAC ("Yet Another APRS Client"), created 2020-Jan-05 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. properly generate standard APRS packets in locales where a comma is used instead of a period as the numeric decimal point. also fix where executing KML files or CSV files of lat/lon data. 2. fix null pointer exception when using GPSD with a non-moving station or station that doesn't currently have a valid GPS fix. 3. shorten outgoing text message panel's text field for the message body to cut down on field loss when someone shrinks the desktop window too small (typically under 965 pixels in width of the map window, depending on font choice). 4. fix ClassCastException accidentally introduced by a refactoring to resolve a findbugs issue. 5. fix hang in mini-webserver caused by using buffered input in an invalid context. 6. fix null pointer exception and HTTP server error in mini-webserver when viewing the stations page on a system that is still rapidly growing its station list. 7. fix incorrect map direction rotation in repeater finder plugin, and handle fitting on small screens by using fullscreen mode and no window title bar.

New YAAC user here, so pardon me if this is a repeat or common question. In the blacklist function, I added a station to this list. After adding the station, I am unable to delete the station from the list. I've tried clicking on the callsign in the blacklist as well as using arrows and tabs, but the "Delete Callsign" option always remains grayed out or unavailable. I have shutdown, rebooted the pi and restarted YAAC with no changes. I've also cleared all filters. Any thoughts on how to remove a callsign from the blacklist? I'm running the 23-Dec-2019 version on a pi4 w/ buster. Great software, Andrew! Thanks in advance, W5AGM

I have recently switched over to using YAAC for my two-way IGate. I am trying to run it headless, and therefore I would like to be able to remotely access it from another computer on the same subnet. I have thus far been unable to make the mini-webserver work. I've tried using the default port of 8008 and also a different port, but with no luck. Is something else required to make this feature work? I've done some minimal amount of research, but haven't found anything. I am running YAAC 1.0-beta 143 on a RPI 2B with Raspbian Buster. Thanks, Greg WB6ZSU

next beta build#145 of YAAC ("Yet Another APRS Client"), created 2020-Jan-07 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. expose some private components of the core YAAC graphical UI so they could be re-used for the new Small Screen plugin. 2. make some of the popup menus alternatively have larger font sizes so the menu choices can be selected more accurately with fat fingers on a touchscreen. 3. fix a few pom.xml issues within the build structure. 4. Implement the first build of the Small Screen plugin. The Small Screen plugin is designed to make YAAC more usable on systems with low-resolution screens and/or touchscreens, such as the Raspberry Pi with the 7-inch touchscreen connected to the DSI port. It uses a different layout of the most useful of the YAAC screens (the map, raw packets table, station/object list, text message table, and the GPS status dialog) in a full-screen mode to take full advantage of what screen real-estate is available instead of having it consumed by window manager overhead. However, all of the other YAAC windows are still available for use. Note that the sounds plugin may also be useful in mobile environments using the Small Screen plugin. With the Raspberry Pi, sound effects could be played through the Pi's default output-only hardware sound interface with a small speaker, while other sound cards (such as the Tigertronics SignaLink or NW Digital Radio DRAWS HAT) handle packet audio input/output.