I¡¯ve been following this topic with interest as I have been using APRS since it started in ¡®92 and downloaded it from BBS¡¯s! It sounds to me that Bob Bruninga¡¯s original APRS would suit your purpose fine. It is low resolution and easy to use for messaging etc as that was one of his original concepts
You can still get APRS876 from Bob¡¯s site and then run it under QEMU on the RPi.
Also wanted to say that Andrew is doing a great job meeting the various constituencies within amateur radio with YAAC and many kudos to him for doing this and also for free!
Bob AB2NE
toggle quoted message
Show quoted text
On Sat, Dec 28, 2019 at 16:19 Michael WA7SKG < wa7skg@...> wrote: Okay, I am new to this. I am happy you have $600 for a new radio for
APRS, I do not. To begin with, I have to use existing or low cost
equipment. For my desired purpose, I am using equipment dedicated to the
purpose, in place and in use all the time. The goal is to provide
position and status reporting in real time, as well as to send and
receive short messages. I would also be interested in seeing other
stations in my vicinity. When I originally brought this up on various
forums, the overwhelming reply was to use YAAC for the purpose, even
after explaining my equipment configuration.
My biggest complaint with ham radio operators today, is they don't
understand why their particular solution is the only one and if it works
for them, then everybody should accept that is the way to go. If your
solution works for you, that is great. However, if your particular
solution does not fit my need, there is no need to chastise me for
wanting something different than you do.
At this time, a larger, higher resolution screen is not an option for
me. Granted, I may have to consider that option in the future, but it
would require a significant restructuring of my installation. To arrive
at a location and need to change my status a bunch of times per day, I
don't have time to connect a laptop in the vehicle, fire it up, launch
programs, run through menus and make a status update.
If there is a non-graphical client for APRS that will provide the
information I need and able to quickly update status and message
information, and run on my existing hardware, that would be fine. As of
now, I have yet to find such software.
rhclinton wrote on 12/28/19 9:26 AM:
> Hmm,? maybe I'm missing the point too - of WA7SKG's complaint.? I have
> been using APRS or nearly
> 20 years, fixed station and mobile.? Most of the time mobile I have been
> satisfied with the
> non-graphic display of a Kenwood D700/710.? When I needed a full graphic
> display of APRS-FI,
> UI-View or YAAC it wasn't a big deal to use my iPad or connect a
> laptop.? No doubt? a format
> suitable for a 7" display connected to an RPi would be useful but APRS
> has been useful without
> it for a long time.? If Andrew can come up with a suitable layout for
> use with YAAC that would
> be great but it is more important to get it right than? to? just get it
> released.
>
> Bob? G0BUX/W0BUX
>
>
> On 2019-12-28 17:07, Andrew P. wrote:
>> Let me clarify.
>>
>> YAAC's screens were designed for a conventional laptop PC, with
>> minimally 1024x768 pixels to work with. They weren't designed for
>> low-resolution screens, because it's too hard to draw a usable map
>> with limited pixels. So the screen layout assumed that there would be
>> enough width to display all the messaging controls at the bottom of
>> the map window.
>>
>> The menu choice Message->Station provides the same functionality in a
>> popup dialog window, but has the fields in different lines, so it may
>> not require as much screen width.
>>
>> I have been contemplating an alternate screen for low-res mobile
>> operations (such as the 7" touchscreen for Raspberry Pi), but haven't
>> come up with a layout I like yet that will fit in such a tiny space
>> and still be operable with fat fingers on a touchscreen.
>>
>> Andrew, KA2DDO
>> author of YAAC
>> ________________________________________
>> From: [email protected] <[email protected]> on behalf of
>> Christopher Rose <kb8uih88@...>
>> Sent: Saturday, December 28, 2019 11:13 AM
>> To: '[email protected]'
>> Subject: Re: [yaac-users] Message box
>>
>> Michael, Andrew said menu choices will get you where you want to go
>> on your smaller screen. Then you say too bad? Did I misunderstand this
>> exchange?
>>
>> Chris
>>
>>
>> -----------------------------------------
>>
>> From: "Michael WA7SKG"
>> To: "Andrew P.", "[email protected]"
>> Cc:
>> Sent: Saturday December 28 2019 6:05:11AM
>> Subject: Re: [yaac-users] Message box
>>
>> That is too bad. Perhaps I am misinformed or have misunderstood, but I
>> thought the whole purpose of APRS was to cater to the mobile user to
>> provide a quick and easy method of reporting position, status, and brief
>> messages. Mobile operation, by its nature, necessitates smaller screens
>> and demands minimal operator actions to accomplish a task. The system
>> should be driven to meet that situation, rather than make it more
>> difficult for the primary purpose.
>>
>> Maybe I am missing the point of APRS. Perhaps further investigation is
>> in order.
>>
>> Michael WA7SKG
>>
>>
>> Andrew P. wrote on 12/27/19 6:24 PM:
>>> It's because your window is too small. The rightmost controls in the
>>> footer are being drawn off-screen because they don't fit in the allowed
>>> window space.
>>>
>>> There are menu choices to get you the same functionality in a smaller
>>> window.
>>>
>>>
>>>
>>> Sent from my Verizon 4G LTE smartphone
>>>
>>>
>>> -------- Original message --------
>>> From: Michael WA7SKG <wa7skg@...>
>>> Date: 12/27/19 20:16 (GMT-05:00)
>>> To: [email protected]
>>> Subject: [yaac-users] Message box
>>>
>>> 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
>>>
>>
|