开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. Yaac-Users
  2. Messages
Expanded Topics Messages Polls
Date
Tiny Trac 4 and NMEA passthrough

 

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
Re: Free email service suggestion?

 
Edited

Here's what I see when I try to send a test message:

Exception in thread "Email test sender" java.lang.NoClassDefFoundError: javax/activation/DataHandler

at org.ka2ddo.yaac.telemetryalarm.TelemetryAlarmMonitor.composeEmail(TelemetryAlarmMonitor.java:413)

at org.ka2ddo.yaac.telemetryalarm.TelemetryAlarmMonitor.composeEmail(TelemetryAlarmMonitor.java:375)

at org.ka2ddo.yaac.telemetryalarm.gui.ConfigureEmail$7$1.run(ConfigureEmail.java:180)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.ClassNotFoundException: javax.activation.DataHandler

at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)

... 4 more

testing connection to smtp.gmail.com:587

changing email server port from 587 to 587

?

testing connection to smtp.gmail.com:587

?
?
Re: Free email service suggestion?

 

开云体育

YAAC's email setup should support STARTTLS, which allows an initial connect unsecured and an immediate upgrade to TLS. Is that working when you connect to gmail? If gmail does insist on immediate TLS, make sure you are connecting to the correct port (usually 587).

If you want to see what YAAC is doing, add the extra Java runtime option

-Dmail.debug=true?

to the command line before the -jar parameter. That will tell the Java mail library to print out what it is doing as it attempts to connect to the mail server.

Hope this helps.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: Bill WA4OPQ <wa4opq@...>
Date: 6/28/20 03:02 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Free email service suggestion?

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?
Free email service suggestion?

 

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?
Re: next beta build#154 of YAAC, created 2020-Jun-25

 

Yes that helps, just what I was looking for and would expect it to work!

Thanks for the insight, it wasn't obvious to use that feature.

Brian N2KGC

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Andrew
P.
Sent: Thursday, June 25, 2020 10:00 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#154 of YAAC, created 2020-Jun-25

Yes, YAAC does, although it doesn't work perfectly because not all
digipeaters "trace" by inserting their callsign-SSID into the digipeat path.
Also, it only shows the most recent path from any given sender, so if the
signal takes multiple paths, only the last duplicate path heard will be
shown.

You enable this on the map with the menu choice View->Layers...->Show
Digipeat Hop Paths. Note that nothing will be drawn for stations received
from the APRS-IS Internet backbone; only stations received from an RF port
into YAAC will be drawn this way.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Brian Webster
via groups.io <radiowebst@...>
Sent: Thursday, June 25, 2020 9:41 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#154 of YAAC, created 2020-Jun-25

Andrew,
Does YACC have a mode where when receiving over the air only it
draws lines between the stations that the packet is hopping through? I have
used that with Radio Mobile in APRS mode and APRSIS32 and really like being
able to visually see on the map how paths are moving and working (and being
able to see bad path statements happening).

Brian N2KGC
Re: next beta build#154 of YAAC, created 2020-Jun-25

 

Yes, YAAC does, although it doesn't work perfectly because not all digipeaters "trace" by inserting their callsign-SSID into the digipeat path. Also, it only shows the most recent path from any given sender, so if the signal takes multiple paths, only the last duplicate path heard will be shown.

You enable this on the map with the menu choice View->Layers...->Show Digipeat Hop Paths. Note that nothing will be drawn for stations received from the APRS-IS Internet backbone; only stations received from an RF port into YAAC will be drawn this way.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Brian Webster via groups.io <radiowebst@...>
Sent: Thursday, June 25, 2020 9:41 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#154 of YAAC, created 2020-Jun-25

Andrew,
Does YACC have a mode where when receiving over the air only it
draws lines between the stations that the packet is hopping through? I have
used that with Radio Mobile in APRS mode and APRSIS32 and really like being
able to visually see on the map how paths are moving and working (and being
able to see bad path statements happening).

Brian N2KGC
Re: next beta build#154 of YAAC, created 2020-Jun-25

 

Andrew,
Does YACC have a mode where when receiving over the air only it
draws lines between the stations that the packet is hopping through? I have
used that with Radio Mobile in APRS mode and APRSIS32 and really like being
able to visually see on the map how paths are moving and working (and being
able to see bad path statements happening).

Brian N2KGC

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Andrew
P.
Sent: Thursday, June 25, 2020 5:47 PM
To: [email protected]
Subject: [yaac-users] next beta build#154 of YAAC, created 2020-Jun-25

next beta build#154 of YAAC ("Yet Another APRS Client"), created 2020-Jun-25

downloadable from
or

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.
next beta build#154 of YAAC, created 2020-Jun-25

 

next beta build#154 of YAAC ("Yet Another APRS Client"), created 2020-Jun-25

downloadable from
or

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.
Re: Connecting a serial TNC

 

*sigh*

Yes, it all sounds familiar now.? (Why didn't I read the YAAC help files first?)? Thanks for pointing this out to me.? Hopefully I won't have to remember to do this again.? :D

Thanks!



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, June 21, 2020 5:25 PM, Andrew P. <andrewemt@...> wrote:

The problem on Fedora (as mentioned in the YAAC help files) is that Fedora no longer assumes unprivileged users will be creating lock files in the /var/lock directory (which is now a symlink to /run/lock). Since ordinary users supposedly don't need to use the lock directory, the directory's owner _and_ group is root. You need to become superuser and change the group of the /run/lock directory to the lock group, so the antique locking code in the RXTX library will work. Also, by default, the lock directory is read-only to group, so you'll have to change the permissions to g+w (group lock has write access). Then, the 20+-year-old locking code in RXTX will work.

Hope this helps.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Eric H. Christensen via groups.io" <eric@...>
Date: 6/21/20 14:01 (GMT-05:00)
Subject: [yaac-users] Connecting a serial TNC

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
Re: Connecting a serial TNC

 

开云体育

The problem on Fedora (as mentioned in the YAAC help files) is that Fedora no longer assumes unprivileged users will be creating lock files in the /var/lock directory (which is now a symlink to /run/lock). Since ordinary users supposedly don't need to use the lock directory, the directory's owner _and_ group is root. You need to become superuser and change the group of the /run/lock directory to the lock group, so the antique locking code in the RXTX library will work. Also, by default, the lock directory is read-only to group, so you'll have to change the permissions to g+w (group lock has write access). Then, the 20+-year-old locking code in RXTX will work.

Hope this helps.

Andrew, KA2DDO
author of YAAC


-------- Original message --------
From: "Eric H. Christensen via groups.io" <eric@...>
Date: 6/21/20 14:01 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Connecting a serial TNC

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
Connecting a serial TNC

 

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
Re: Strange Position Reports

 

If you're referring to my comment about hearing BAMBAM in Idaho, that is incorrect. Because BAMBAM uses a 3 path hop it has a HUGE potentional reach. The digi path is more like 4 hops because of an issue with older KPC units which do not properly mark the WIDE1 digipeat. So many of the next stations digipeat the WIDE1 again, and then properly mark it. It's pretty annoying.?
Re: Strange Position Reports

 

开云体育

Hi,

I was up at steens mountain near Burns and a person was using Aprs on the repeater (non-aprs). ?I think they said the person was traveling around Idaho.

Just fyi


On Jun 19, 2020, at 10:31 PM, Michael - NA7Q <mike.ph4@...> wrote:

?

I understand this thread is old. In fact I stumbled upon in because of the "BAMBAM" station that is operating under very poor ways..

I'm the owner of NICOLI (Nicolai Mountain) and various others APRS stations. But I see NICOLI was discussed by Jeff, so I'll address it.

So NICOLI operates in the most friendly of ways as a WIDE1 digi. It doesn't spew garbage beacons like BAMBAM or many of the other stations around. It beacons a position 1 time per 10 minutes, as is the legal requirement, AND does NOT use a path. I think that is very important. Because I have multiple igates within range, and is heard by many other igates, there is no reason to add a path.?

It also has 1, yes just 1 telemetry beacon that is sent 1 time, yes 1 time PER hour with a 1 hop path. This equals 7 beacons per hour, and only 1 hop in that duration. Pretty good compared to most that just clutter and congest the network beyond belief.

Another fun fact, NICOLI only uses 5 watts on a low gain antenna on top of the 30 foot tower.?

Why does it reach so far? Location location location.
Nicolai Mountain has an incredible path through the Gorge and into the east side almost across the entire station of Washington and Oregon at times.
Frequently my Trout Lake station is able to be heard on Nicolai under normal conditions. Everything about this digi is done with one thing in mind. Provide coverage to an area that isn't covered, reduce congestion, block as many digi beacons as possible that shouldn't be using a path. Unfortunately the unit has the maximum block slots filled up. So some junk gets through. Like BAMBAM....

I've been wanting to get a hold of KI7RUS because of BAMBAM. It's using a seriously bad path, and is able to be heard across the entire state of Washington and Oregon. I heard it coming across a digi in Idaho last week! It's outrageous. It's not even located at the location it beacons. It beacons too frequently for the weather and the telemetry. Which in his case is every 5 minutes. APRS.fi and APRSDirect only update at 10 minute intervals for weather and telemtry. So beaconing more often does nothing.

I hope to get a hold of that guy at some point, and I hope that he is understanding. All too often these guys are not.?

73
NA7Q
Re: Working Satellites w/FT3D

Gervais Fillion
 

开云体育

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

Re: Strange Position Reports

 

I understand this thread is old. In fact I stumbled upon in because of the "BAMBAM" station that is operating under very poor ways..

I'm the owner of NICOLI (Nicolai Mountain) and various others APRS stations. But I see NICOLI was discussed by Jeff, so I'll address it.

So NICOLI operates in the most friendly of ways as a WIDE1 digi. It doesn't spew garbage beacons like BAMBAM or many of the other stations around. It beacons a position 1 time per 10 minutes, as is the legal requirement, AND does NOT use a path. I think that is very important. Because I have multiple igates within range, and is heard by many other igates, there is no reason to add a path.?

It also has 1, yes just 1 telemetry beacon that is sent 1 time, yes 1 time PER hour with a 1 hop path. This equals 7 beacons per hour, and only 1 hop in that duration. Pretty good compared to most that just clutter and congest the network beyond belief.

Another fun fact, NICOLI only uses 5 watts on a low gain antenna on top of the 30 foot tower.?

Why does it reach so far? Location location location.
Nicolai Mountain has an incredible path through the Gorge and into the east side almost across the entire station of Washington and Oregon at times.
Frequently my Trout Lake station is able to be heard on Nicolai under normal conditions. Everything about this digi is done with one thing in mind. Provide coverage to an area that isn't covered, reduce congestion, block as many digi beacons as possible that shouldn't be using a path. Unfortunately the unit has the maximum block slots filled up. So some junk gets through. Like BAMBAM....

I've been wanting to get a hold of KI7RUS because of BAMBAM. It's using a seriously bad path, and is able to be heard across the entire state of Washington and Oregon. I heard it coming across a digi in Idaho last week! It's outrageous. It's not even located at the location it beacons. It beacons too frequently for the weather and the telemetry. Which in his case is every 5 minutes. APRS.fi and APRSDirect only update at 10 minute intervals for weather and telemtry. So beaconing more often does nothing.

I hope to get a hold of that guy at some point, and I hope that he is understanding. All too often these guys are not.?

73
NA7Q
YAAC Telemetry

 

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
URGENT: new beta build#153 of YAAC, created 2020-Jun-16

 

next beta build#153 of YAAC ("Yet Another APRS Client"), created 2020-Jun-16

downloadable from
or

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.
Re: Timed beacon not working beta152

 

I seem to be having the same problem. Here is a small portion of my error log.
How do I reload 151??
Sun Jun 14 12:50:42 MDT 2020:/dev/ttyS0: excessively long time 541msec to receive 62-byte frame
Sun Jun 14 12:51:16 MDT 2020:/dev/ttyS0: excessively long time 641msec to receive 75-byte frame
Sun Jun 14 12:51:17 MDT 2020:/dev/ttyS0: excessively long time 701msec to receive 82-byte frame
Sun Jun 14 12:51:23 MDT 2020:/dev/ttyS0: excessively long time 500msec to receive 58-byte frame
Sun Jun 14 12:52:22 MDT 2020:/dev/ttyS0: excessively long time 642msec to receive 75-byte frame
Sun Jun 14 12:52:58 MDT 2020:/dev/ttyS0: excessively long time 641msec to receive 75-byte frame
purgeStaleTraffic: deleted 41 old msgs and 2 old stations
Sun Jun 14 12:54:01 MDT 2020:/dev/ttyS0: excessively long time 842msec to receive 100-byte frame
Sun Jun 14 12:54:25 MDT 2020:/dev/ttyS0: excessively long time 642msec to receive 75-byte frame
Sun Jun 14 12:55:00 MDT 2020:/dev/ttyS0: excessively long time 339msec to receive 40-byte frame
Sun Jun 14 12:55:25 MDT 2020:/dev/ttyS0: excessively long time 541msec to receive 62-byte frame
Sun Jun 14 12:55:29 MDT 2020:/dev/ttyS0: excessively long time 722msec to receive 84-byte frame
Sun Jun 14 12:55:34 MDT 2020:/dev/ttyS0: excessively long time 480msec to receive 55-byte frame
Sun Jun 14 12:55:52 MDT 2020:/dev/ttyS0: excessively long time 601msec to receive 71-byte frame
Sun Jun 14 12:56:48 MDT 2020:/dev/ttyS0: excessively long time 480msec to receive 55-byte frame
Sun Jun 14 12:57:38 MDT 2020:/dev/ttyS0: excessively long time 802msec to receive 94-byte frame
Sun Jun 14 12:58:16 MDT 2020:/dev/ttyS0: excessively long time 641msec to receive 75-byte frame
purgeStaleTraffic: deleted 18 old msgs and 1 old stations
Sun Jun 14 12:59:02 MDT 2020:/dev/ttyS0: excessively long time 842msec to receive 100-byte frame
Sun Jun 14 12:59:05 MDT 2020:/dev/ttyS0: excessively long time 903msec to receive 107-byte frame
Sun Jun 14 12:59:08 MDT 2020:/dev/ttyS0: excessively long time 601msec to receive 70-byte frame
Sun Jun 14 13:00:01 MDT 2020:/dev/ttyS0: excessively long time 461msec to receive 54-byte frame
Sun Jun 14 13:00:18 MDT 2020:/dev/ttyS0: excessively long time 782msec to receive 93-byte frame
Sun Jun 14 13:00:29 MDT 2020:/dev/ttyS0: excessively long time 721msec to receive 86-byte frame
Sun Jun 14 13:02:00 MDT 2020:/dev/ttyS0: excessively long time 540msec to receive 64-byte frame
Sun Jun 14 13:02:21 MDT 2020:/dev/ttyS0: excessively long time 521msec to receive 61-byte frame
Sun Jun 14 13:02:37 MDT 2020:/dev/ttyS0: excessively long time 843msec to receive 100-byte frame
Sun Jun 14 13:03:16 MDT 2020:/dev/ttyS0: excessively long time 782msec to receive 91-byte frame
purgeStaleTraffic: deleted 76 old msgs and 2 old stations
Sun Jun 14 13:03:47 MDT 2020:/dev/ttyS0: excessively long time 782msec to receive 91-byte frame
Sun Jun 14 13:03:48 MDT 2020:/dev/ttyS0: excessively long time 742msec to receive 88-byte frame
Sun Jun 14 13:03:49 MDT 2020:/dev/ttyS0: excessively long time 742msec to receive 88-byte frame
Sun Jun 14 13:04:36 MDT 2020:/dev/ttyS0: excessively long time 360msec to receive 41-byte frame
Sun Jun 14 13:05:00 MDT 2020:/dev/ttyS0: excessively long time 400msec to receive 47-byte frame
Sun Jun 14 13:05:26 MDT 2020:/dev/ttyS0: excessively long time 843msec to receive 100-byte frame
Sun Jun 14 13:05:34 MDT 2020:/dev/ttyS0: excessively long time 581msec to receive 67-byte frame
Sun Jun 14 13:05:44 MDT 2020:/dev/ttyS0: excessively long time 763msec to receive 89-byte frame
Sun Jun 14 13:06:47 MDT 2020:/dev/ttyS0: excessively long time 581msec to receive 68-byte frame
Sun Jun 14 13:08:20 MDT 2020:/dev/ttyS0: excessively long time 420msec to receive 48-byte frame
purgeStaleTraffic: deleted 44 old msgs and 1 old stations
Sun Jun 14 13:09:47 MDT 2020:/dev/ttyS0: excessively long time 581msec to receive 69-byte frame
Sun Jun 14 13:10:01 MDT 2020:/dev/ttyS0: excessively long time 400msec to receive 47-byte frame
Sun Jun 14 13:10:02 MDT 2020:/dev/ttyS0: excessively long time 460msec to receive 54-byte frame
Sun Jun 14 13:10:30 MDT 2020:/dev/ttyS0: excessively long time 782msec to receive 93-byte frame
Sun Jun 14 13:10:34 MDT 2020:/dev/ttyS0: excessively long time 843msec to receive 100-byte frame
Sun Jun 14 13:10:40 MDT 2020:/dev/ttyS0: excessively long time 1024msec to receive 122-byte frame
Sun Jun 14 13:10:43 MDT 2020:/dev/ttyS0: excessively long time 722msec to receive 86-byte frame
Sun Jun 14 13:10:44 MDT 2020:/dev/ttyS0: excessively long time 541msec to receive 62-byte frame
Sun Jun 14 13:11:00 MDT 2020:/dev/ttyS0: excessively long time 460msec to receive 54-byte frame
Sun Jun 14 13:11:15 MDT 2020:/dev/ttyS0: excessively long time 520msec to receive 61-byte frame
Sun Jun 14 13:11:31 MDT 2020:/dev/ttyS0: excessively long time 561msec to receive 65-byte frame
Sun Jun 14 13:11:59 MDT 2020:/dev/ttyS0: excessively long time 460msec to receive 54-byte frame
Sun Jun 14 13:12:21 MDT 2020:/dev/ttyS0: excessively long time 581msec to receive 68-byte frame
Sun Jun 14 13:14:02 MDT 2020:/dev/ttyS0: excessively long time 602msec to receive 71-byte frame
Sun Jun 14 13:14:17 MDT 2020: invalid message format K5RHD-10>APMI06 => "K5RHD-10>APMI06,WIDE1-1,qAR,N0AUX-1:@141914#3950.70N/10505.14W&PHG8230 Digi/iGate in Arvada, CO DM79", treat as DefaultMessage:
java.lang.IllegalArgumentException: invalid format time '141914#'?

On Sun, Jun 14, 2020 at 7:50 PM Ian Morrison <imorrison@...> wrote:

Hi Andrew,

I see the same thing and had to go back to 151.

?

73, Ian

VE3EP

?

Sent from for Windows 10

?

From: Joseph LaFerla
Sent: Sunday, June 14, 2020 7:32 PM
To: [email protected]
Subject: [yaac-users] Timed beacon not working beta152

?

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

?



--
Thank You and God Bless?
Richard
?

Richard Beggs? ? ? ? ? ? N0EB? ? ? 145.295
1220 H Street?
?Salida, Co. 81201?
??Email:?Richard.N0EB@...
?Cell 719-239-1788 LL 719-539-5435?
**
?A socialist is basically a communist who doesn’t?
have the power to take everything from their?
citizens at gunpoint ... Yet!
broken beaconing

 

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
Re: Timed beacon not working beta152

 

开云体育

Hi Andrew,

I see the same thing and had to go back to 151.

?

73, Ian

VE3EP

?

Sent from for Windows 10

?

From: Joseph LaFerla
Sent: Sunday, June 14, 2020 7:32 PM
To: [email protected]
Subject: [yaac-users] Timed beacon not working beta152

?

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

?

0E3CC93CC47544CFB043DD73F6C50A38.png

2481 - 2500 of 2873