开云体育

Hi Andrew I live in the vicinity of East Lake Ontario Canada and the lake is missing from the YAAC map , instead of the lake there is a white space. The coordinates of the lake are 43.9189° N, 77.2003° W. Also, going right through the words Prince Edward Count on the YAAC map is a blue band which should not be there. I have checked the same location on Openstreetmap.org and the map features for the same location are correct on the openstreetmap site, indicating that the source of the data is correct. Could it be that these errors were introduced during the transition to the yaac map? I would appreciate your thoughts on what could be done here. If you give me step by step directions, I could also make the map tiles from the original as I have a fast internet connection. Thanks. Joe VA3JLF

next beta build#151 of YAAC ("Yet Another APRS Client"), created 2020-May-20 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. fix barometric pressure units in OpenTRAC weather reports. 2. fix Julian date extraction for Peet Bros Ultimeter weather station reports. 3. fix Yaesu port driver's parsing of Yaesu APRS radio data. 4. fix NullPointerException from cancelling non-started timeout timer. 5. improve error reporting if a plugin can't be activated. 6. don't do map pan-and-flash for blacklisted station that is reporting an emergency (presumably, they were blacklisted for abusive/illegal transmissions already). 7. add new mini-webserver page for weather data from the local station. 8. (courtesy of James Parker) sort the bookmarks menu into alphabetical order. 9. properly handle keyboard mnemonics and accelerators for menu entries defined by plugins (courtesy of James Parker). 10. ensure Help menu is all the way to the right on menu bars. 11. fix raw packet table view to not break when bodiless frames are received (such as connected-mode packet supervisory [S] frames handling flow-control). 12. allow map mouse-clicks to select the local station. 13. prevent IndexOutOfBoundsExceptions when viewing the Last Digipeater table in the filter UI. 14. add debugging hook to allow playing back Yaesu port log file. 15. fix OpenStreetMap rendering errors for Ways whose width values use punctuation marks to indicate units of width. 16. stop doing unnecessary land fills on island shorelines. 17. try to reduce plotting OpenStreetMap labels on top of other labels. 18. harden mini-webserver against browsers who send Unicode byte order marks as the start of their HTTP request. 19. fix more import issues with OpenStreetMap data, optimize open ocean tile data for more efficient reading and rendering. 20. begin effort of localizing mini-webserver pages so they will appear in the locale of the station operator. 21. allow mini-webserver page handlers to throw FileNotFoundException so they can conditionally be reported as HTTP 404 Not Found instead of having to show content that doesn't exist in the local station. 22. fix menu keyboard mnemonics for callsign DB plugin. 23. update tocalls list from the master lists as of build date.

Is there any way to have the small screen plugin display on a different screen than the default monitor? I have a 7" USB monitor connected to my computer and I would like to use the small screen display on that monitor instead of the default one. Ron N8WCR

New install of YACC on a pi with the new May 2020 buster load. Open program, configure settings and run for a while. Close program and about 2 seconds later it opens again. The second time I close it ,it stays closed. Anyone seen this before?

I'm planning on going mobile with YAAC and MOBILINK Bluetooth. In my home, I have no issues. I'll be connecting to my Samsung Tablet which has data to pull the map part of YAAC. I'll be using my Bluetooth TNC. In theory, the map should load. I like to use PI 4 using KM4ACK build. This is my Test PI for Jason builds. For power, I'll be using a 12 v with a USB 5 v plug with 2 12 cigar plugs in the. I'm hoping I don't have any hiccups. Yesterday my Aprsdroid shut down because of overheating. I hope PI 4 doesn't have any issues. I'm hoping my USB GPS dongle will work instead of my static GPS. 73 Don Poaps New Westminster, BC VA7DGP DATA VA7QU VOICE Winlink: va7qu@... Subject://wl2k

Greetings. After looking at yet another email about adding digipeaters, the thought came up of "What do we really need to add to APRS?" Except in certain areas, we generally have good coverage with digipeaters, so we don't usually need more of them. What we need is content. To quote the old Bruce Springsteen song, "there's 57 channels and nothing's on." So what are you adding to APRS? More fixed beacons don't really add value and mobile trackers (unless some other station wants to track that specific mobile) aren't much more useful. But services, they add value. The QRU service is a simple capability of announcing on demand what services are in the area. So, if someone's driving through and looking for a good 2-meter voice repeater for a rag-chew, they should be able to send to QRU a request for RP2M (two-meter analog repeaters) and get an answer of Objects identifying local repeaters (preferably in correct syntax so a Kenwood radio can one-button tune to the repeater). YAAC supports defining Objects and associating them with QRU categories, so your station could answer a QRU query. To avoid channel clutter, you don't need to be transmitting those Objects all the time, just when someone asks for them. And there are dozens of QRU categories. One category is the INFO category, which allows you to ask local QRU servers what categories of information they provide. Of course, every one in the neighborhood shouldn't report the same information. Say, each one provide the RP2M or RP70 for their own club's repeater, so all clubs with open repeaters are supported from multiple QRU servers, instead of one Single Point Of Failure announcing all repeaters. This is a little different from Bob Bruninga's Local Info Initiative that expects one high-level digipeater to do it all periodically instead of on-demand, but with the amount of local info that could be available, cluttering the channel with Objects the locals know about is a waste of bandwidth, but announcing it for transient mobiles on-demand is much more effective use of the channel. Similarly, there are services on the APRS-IS that are useful to RF stations, but they can't be accessed unless there is a transmit-capable I-gate within range of the RF station. Without a Tx I-gate, the service's answer won't make it back to the RF station. So running a Tx I-gate (instead of the less useful receive-only I-gate) expands the usability of RF stations (which is really what Amateur Radio [as opposed to the Amateur Internet] is all about). Andrew, KA2DDO author of YAAC

I'm trying to set up a Sgate in my regional area 160km south of the big smoke. I'm using a RPi, a RTL-SDR, and direwolf. It works as an Igate. What's the difference between an I gate and a S gate? Besides the RX frequency. In testing my S gate I found I get an error at a remote direwolf receiver telling me I'm using a lowercase character in my maidenhead grid like QF55hd It doesn't like the lower case hd. I tracked this down to my status beacon but there is nowhere to set the grid square on this status beacon page. There is only space for my text which is how I know it's by status beacon which sends the lower case character. I remember there was a once only place where you can set the status grid during the initial installation so how can I replace my grid square QF55hd with QF55HD? Without deleting and re installing YAAC. Thanks, Bob vk2byf

next beta build#152 of YAAC ("Yet Another APRS Client"), created 2020-Jun-12 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. fix generation of Maidenhead locators to use more string all-uppercase as specified in the APRS Protocol Specification. 2. fix round-off errors for decoding day-hour-minute timestamps near end of month. 3. fix some Javadoc errors in source code. 4. fix reschedulable timers (as used for timeslot code in port drivers) to actually be reschedulable after they expire. 5. properly handle classpath setup for plugins that reject initialization. 6. fix timer-based logger classes to allow changing the flush rate independent of the log rollover time, and to allow post-processing of a closed periodic log file. 7. fix configuration importer to force replaced callsigns to be restricted to legal AX.25 callsign-SSID syntax. 8. allow popup menu "View URL" and "Send Email" to work on map views (as well as tabular views). 9. add keyboard mnemonics to Bookmarks menu (per James Palmer AG5VQ). 10. allow popup menu on callsign column of Tracked Station table view. 11. fix NullPointerException problem in Radio View display when rapid updates are occurring. 12. fix formatting of Credits tab of Help->About dialog. 13. make progress dialog more compact so it won't get in the way during extremely long background tasks (by James Palmer, AG5VQ). 14. correct errors in implementing MADIS quality checks (particularly the Level 1 self temporal consistency delta checks), add partial Level 3 spatial consistency checks. 15. add slot length control for timeslotted APRS ports, so that YAAC knows when to stop adding packets for transmission when the end of the timeslot approaches, even if there is more traffic to send. 16. more attempts to improve performance of OpenStreetMap renderer. 17. fix way statistics counters in OpenStreetMap PBF importer. 18. add device interface check to Bluetooth plugin using new plugin error reporting, so user will be informed if host computer does not have a Bluetooth interface or does not have a native library for that operating system. 19. add James Palmer's performance optimizations for downloading and parsing national public record databases for amateur radio callsigns. 20. enhance MADIS Post plugin to allow user-selectable file format in either CSV or JSON format, with the option to automatically push a finished file via HTTP POST or FTP to another host, and add help on how to use the feature. Default format is that used by previous version of plugin. 21. have the Small Screen plugin remember the desktop position and size of its window. 22. augment email client code in Telemetry Alarm plugin to allow non-default port numbers for the remote SMTP server. 23. allow displaying the defined units of telemetry data (as specified by the remote station) in telemetry alarms. 24. add built-in help for Telemetry Alarm plugin. 25. restructure Telemetry Alarm plugin configuration so email configuration is done in the expert-mode configuration dialog as for every other part of YAAC, and add ability to send self-addressed test emails to verify the email configuration. 26. fix plugin help index XML files to avoid index merge failures. 27. fix Weather Alert plugin to detect wind gusts from stations that only report current wind speed and not recent gust peaks. 28. add ability to speak station/object course (direction of travel) in Sounds plugin. 29. add weather station clock error condition to Weather Alert plugin. 30. more fixups of UoMD findbugs issues.

Greetings, all. Yes, it appears that automatic beaconing was broken by my attempt to not overflow antique hardware TNCs. I am working on a fix now. Please hold off on upgrading until I get build 153 available. Andrew, KA2DDO author of YAAC

HI Andrew I installed the new beta 152 and notice that the timed beacon does not seem to be working. I have YAAC set to beacon every 30 minutes. I can beacon by pressing the space bar or the BCN button but the auto beacon does not work. I downgraded to beta 151 and the timed beacon works fine with no setting changes. Is there some setting in 152 for the beacon that I have missed? Thanks for a great program and excellent support as usual. Thanks and 73 Joe VA3JLF

next beta build#153 of YAAC ("Yet Another APRS Client"), created 2020-Jun-16 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. [CRITICAL] fix timer breakage across many functions of YAAC that was introduced in build 152. This also affected rolling log file writing. 2. update tool used to post built-in help files to author's website so it will also post help for plugins. 3. update forced beaconing to also flush log files to disk immediately after the forced beaconing. 4. add James Palmer's mnemonics support to the Bookmarks menu. 5. fix logging of transmitted AX.25 packets to not occur until packets actually leave YAAC (i.e., after timeslotting delays, etc.). Note this doesn't account for TNC delays waiting for a clear channel, but it is still more time-accurate than the prior transmit logging. 6. clean-up of plugin help files to better merge with core YAAC help. 7. fix error display code in callsign DB plugin for downloading Canadian and Australian databases. 8. in MADIS post plugin, add the option of reporting the YAAC receive time of the weather packets, as opposed to any timestamp the sending weather station might include in the packets. Note that some weather stations have seriously incorrect clock settings.

Andrew, You may recall that several months ago we exchanged messages concerning problems I was having with telemetry alerts. When you announced YAAC release 152 I was encouraged to read points 22, 23, 24, and 25, and I was glad to see that there has been significant progress. However at least one problem still remains. (I am now running YAAC release 153 with telemetry plugin 0.3 installed.) When I go to the new email configuration page and set up an email server, and then initiate a test message, the message is sent and ultimately received in the email server inbox. This is a significant advance on previous versions when no connection to the server was achieved. However, when I go to the View Telemetry Alarms page and attempt a test message, nothing is received at the specified destination inbox. Robert Clinton W0BUX/G0BUX

keith may i ask what frequencies for those satellites? i wonder if i can hear them. thanks gervais ve2ckn De : [email protected] <[email protected]> de la part de Keith Kaiser <wa0tjt@...> Envoyé : 20 juin 2020 10:29 ? : [email protected] <[email protected]> Objet : [yaac-users] Working Satellites w/FT3D Has anyone out there programmed their FT3d with the splits for AO-91, AO-92, ISS? If so would you be willing to share that file? I'm curious also about how they should be set up. For example I think I should put the downlink frequency on the B side and the uplink on the A, is this correct? Additionally how many steps on the uplink side should I set to handle the doppler shifts? I was able to listen to AO-92 last night but I'm not convinced I had the radio set up correctly for a two way conversation. Any help would be appreciated. -- Keith

I swear I had this working before but for some reason it's not working now. I'm trying to connect my D72 to YAAC using /dev/ttyUSB0. When I enter /dev/ttyUSB0 into the device name and select "Test Port" I get the "Unable to bring up Test-Port for Serial_TNC" message. I have rxtx installed and I'm a member of dialout, lock, and tty, which should be enough permissions to gain access to the port. I'm able to access the device using minicom. What am I missing? I'm using Fedora 32. 73, Eric WG3K

next beta build#154 of YAAC ("Yet Another APRS Client"), created 2020-Jun-25 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and updates include: 1. more cleanups of the Maven pom.xml files; now possible to compile all supported components of YAAC with Maven, although Javadocs still don't work from Maven, and plugins requiring ZIP file collections of their JAR file and 3rd-party library JAR files aren't built correctly. 2. phase out using duplicate CharSet objects for standard character sets (US_ASCII, ISO_8859_1 and UTF_8), replace with the StandardCharsets class introduced with Java 7. 3. support messages having both altitude (/A=nnnnn) and range (RNGnnnn) optional data extensions in their comments. 4. support reading CSV format APRS packet files where the port column is provided but an empty string. 5. improve documentation of first window selection, merging plugins with first window choices into the help index. 6. add new AIS decoder plugin that works with DireWolf 1.6 and later. 7. fix status reporting and repeater detection in the repeater finder plugin, including identifying DMR repeaters and filtering out short-range hotspots that are out of range. Also add support for auto-tuning generic radios to repeaters using the Hamlib rigctl command. 8. fix emailing in the telemetry alarm plugin, including correcting Test buttons that didn't work.

I just installed the latest update of YAAC and I'm anxious to try out the telemetry and weather plugins. My problem is this: I have several email accounts that I could use but they are all Gmail. Gmail requires TLS or SSL. which YAAC doesn't indicate it uses. Can you suggest a free email SMTP service that doesn't require TLS or SSL? Or am I missing something?

Good Afternoon, I am wondering if I am missing something in the port configuration. Is it possible to use/capture the NMEA data that is passed through the TT4 from the GPS? Thank you, Dan