¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
next beta build#159 of YAAC, created 2020-Nov-16
next beta build#159 of YAAC ("Yet Another APRS Client"), created 2020-Nov-16 downloadable from https://www.ka2ddo.org/ka2ddo/YAAC.html or https://sourceforge.net/projects/yetanotheraprsc changes and
By Andrew P. · #651 ·
Re: Last Received 3014 Days ago
Well, the next build of YAAC is going to make the user responsible for selecting the same date format as they configured in the radio. So I don't have to force radio owners to use a format unfriendly
By Andrew P. · #650 ·
Re: Last Received 3014 Days ago
I'm not sure that mm/dd/yyyy is any more sane - particularly for those of us in the ROW :-) Better to stick with yyyy/mm/dd - a least worst option. Doug VK2DCR
By Doug VK2DCR / N1KIQ · #649 ·
Re: Last Received 3014 Days ago
It's your choice. I agree that MM/DD/YY is a more "sane" date code, but that's because I'm in the US. That would be my preference, but there is an argument to be made for supporting the default format
By John Roberts <intellisig@...> · #648 ·
Re: Last Received 3014 Days ago
OK, does that mean I should back out my change of timestamp format? I need to release a build today because of the Leonids meteor shower tonight (I also need to climb on my roof to set up another
By Andrew P. · #647 ·
Re: Last Received 3014 Days ago
Hi Andrew, I may have changed the setting in the FTM400 config menu. I planned to test that tonight. I think it's hard for you to build code that will anticipate whatever format the user may have
By John Roberts <intellisig@...> · #646 ·
Re: Last Received 3014 Days ago
I don't get to pick the format; Yaesu does, because their firmware is what is writing the date/time stamp to the serial port that YAAC is reading. I couldn't find anything in the Yaesu FTM400DR APRS
By Andrew P. · #645 ·
Re: Last Received 3014 Days ago
or how about the even saner year/month/day format
By rhclinton · #644 ·
Re: Last Received 3014 Days ago
That does seem too weird. I'm fixing the date format in the next build to be the saner month/day/year format your sample sent me.
By Andrew P. · #643 ·
Re: YAAC with ICOM
Well I'm moving towards working. the radio now transmits but i get a protocol error.? I'm getting closer.
By Peter Stokes <stokespeter@...> · #642 ·
Re: Last Received 3014 Days ago
Per chance, did you change the date format on your Yaesu? YAAC is coded for year/day/month date order (which seems a little strange, but I don¡¯t think it was a mistake from the samples another Yaesu
By Andrew P. · #641 ·
Re: Last Received 3014 Days ago
Thank you for replying. The messages seem to have the correct date (see below). Any suggestions on anything else I can check? [image: image.png]
By John Roberts <intellisig@...> · #640 ·
Re: Last Received 3014 Days ago
Considering that the delay you reported is 8 1/4 YEARS off, I would check the date (not the time) in the radio. The Yaesu radio provides the complete date/timestamp for each received packet. Hope this
By Andrew P. · #639 ·
Re: YAAC with ICOM
Since you're using DireWolf as your TNC, it has to control the PTT on your radio, not YAAC. Consult the DireWolf documentation as to the proper syntax for the PTT directive for your radio. Assuming
By Andrew P. · #638 ·
Last Received 3014 Days ago
Hi, I have YAAC running via RS232 with a Yaesu FTM400XDR. It's parsing APRS just fine, but the "last rcvd" date for all the stations is 3014days ago. My radio isn't able to get a GPS fix inside my
By John Roberts <intellisig@...> · #637 ·
Setup with Icom 705 on raspberry pi
I have the receive side operating but do not have control of the radio for beaconing. 1 port for 705¡¯s built-in gps on gpsd 1 port on AGWPE for direwolf modem cont get control port for radio, have
By Peter Stokes <stokespeter@...> · #636 ·
YAAC with ICOM
I have the gps and AGWPE ports operational using direwolf but I¡¯m have it no luck getting control of the radio for beaconing. The data shows in direwolf but no transmit signaling. I¡¯ve setup
By Peter Stokes <stokespeter@...> · #635 ·
Re: Water issues, again.
See below... That's about as good as you can get, given the present approved tag values. The "natural" tag does have a supported v
By Andrew P. · #634 ·
Re: Water issues, again.
©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\ Yep, that was me. OSM doesn't have a tag for "Sound" so it was questionable as to which tag to use for the Albemarle and Pamlico Sounds.
By Eric H. Christensen · #633 ·
Re: Water issues, again.
OK, I found out what was wrong with Pamlico Sound and related areas in North Carolina. Whoever entered those areas into OpenStreetMap listed them as natural=water, but didn't provide a water tag to
By Andrew P. · #632 ·