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
|
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
|
The problem here is that you are running YAAC in -nogui mode. The mini-webserver in YAAC depends on the graphics libraries to render the map image, so it won't work in headless mode.
For your setup, I recommend using vncserver to remotely access YAAC running in graphical mode.
Andrew, KA2DDO
author of YAAC
Sent from my Verizon 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------
From: Greg WB6ZSU <gregn1@...>
Date: 12/26/19 16:07 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Mini-Webserver
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
|
Andrew,
I actually am running in the GUI mode. I'm using the full desktop version of Buster which has the GUI. ?I was thinking about it a little more, and wondered if it has something to do with the Java version. ?Buster comes preloaded with Java build 11.0.5+10-post-Raspbian-ldeb10ul. Any reason to believe there's an issue with this?
|
That's odd. Do you have the mini-webserver enabled? Go to File->Configure->Expert Mode and see what port number is specified for the mini-webserver. There might be a port conflict, depending on what other applications are running on your Pi.
Try restarting YAAC from a command prompt and look at the startup messages to see if any exception happened (such as a SocketException indicating the webserver listening port couldn't be opened).
Sent from my Verizon 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------
From: Greg WB6ZSU <gregn1@...>
Date: 12/27/19 11:28 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] Mini-Webserver
Andrew,
I actually am running in the GUI mode. I'm using the full desktop version of Buster which has the GUI. ?I was thinking about it a little more, and wondered if it has something to do with the Java version. ?Buster comes preloaded with Java build 11.0.5+10-post-Raspbian-ldeb10ul.
Any reason to believe there's an issue with this?
|
I’ll do the restart when I get home this afternoon, but I have looked at the log in the past and didn’t see any clues.
I originally tried with the default port of 8008, but after that didn’t work, I tried another port. ?Still no luck. ?I’ve also tried 127.0.0.1 on the local machine, and that also doesn’t work.
|
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
|
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
|
Andrew...
I did a restart and didn't see anything in the startup messages or the syslog related to an exception. I really don't see any errors. It's just as if the web server isn't being enabled.
|
This will be used in a mobile environment. The various status reports of "off duty", "en route", "in service", "returning", "committed", "special", and others will be changed frequently throughout the day. Right now, that requires at least six mouse clicks, even more difficult to do on a small touchscreen. A stylus would help, but it is still a lot of clicks and double taps and easy to make errors, taking even more time. Far from convenient. And, making the change does not seem to trigger a beacon transmission to announce the change in status.
Having some buttons at the top of the screen, say after the start and stop message processing buttons could be an option. Lacking the buttons, perhaps a pulldown to select the status options and a SEND button to force a beacon with the updated status. Or possibly a way to utilize an outboard hardware button bar with maybe six programmable buttons that could utilize the GPIO pins of the Raspberry Pi. And have those buttons be configured to initiate a beacon transmission with the updated status when pushed.
Any of these would be preferable to needing six or more mouse clicks or screen taps just to change status.
BTW, related to this, is there any way for the screen icon to readily display the status of the mobile station?
Back in the old days of basic packet radio that used keyboard-to-keyboard comms, re-purposed MDTs were used with programmable macro keys that sent a beacon with similar status information, which was displayed as a timestamped list on the recipients screen. Not as fancy as the graphic APRS representations we have now, but plenty effective at the time.
Thanks,
Michael WA7SKG
Andrew P. wrote on 12/27/19 7:56 PM:
toggle quoted message
Show quoted text
I didn't expect that the MicE status would be changed that often, and it mostly applies to mobile stations, since a fixed station can't really be "en route" or "returning".
I didn't think it was that hard to edit that one beacon setting from the expert-mode configuration dialog.
Sent from my Verizon 4G LTE smartphone
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 12/27/19 15:55 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Station Status
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
|
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:
toggle quoted message
Show quoted text
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
|
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
>
|
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
|
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
toggle quoted message
Show quoted text
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
|
Re: Bug: Clearing monitor frequency
-‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, December 22, 2019 4:23 PM, Andrew P. <andrewemt@...> wrote: What frequency did you specify? If you want to turn it off, you have to specify a frequency of 000.000. Ahh, yes, this worked well. I had specified a VHF frequency but setting it to 0 cleared it. I'm having a similar problem the Supplemental Tx I-Gate filter. I had it set for b/AKQTOR/MHXTOR during Hurricane Dorian but I'd like to clear this out. Replacing this text with anything or removing it completely doesn't seem to work. 73, Eric WG3K
|
I believe you misunderstood the intent. Perhaps you only read the first sentence and did not read and comprehend the full message thread for context. The meaning was, it is too bad the only way to update the status was to go through multiple menus requiring at least six clicks on a tiny touchscreen for a simple status change. If this was something that only changed say once a month or so, that is one thing. For something that could conceivably change a dozen times per day, it is too bad it is so complex a function.
I hope that clears it up for you.
73,
Michael WA7SKG
Christopher Rose wrote on 12/28/19 8:13 AM:
toggle quoted message
Show quoted text
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
>
|
Re: Bug: Clearing monitor frequency
You need to press the Enter key after changing the supplemental Tx I-gate filter. That will cause the new expression (which can be a zero-length string) to be applied.
Sent from my Verizon 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------
From: "Eric H. Christensen via Groups.Io" <eric@...>
Date: 12/28/19 12:54 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] Bug: Clearing monitor frequency
-‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, December 22, 2019 4:23 PM, Andrew P. <andrewemt@...> wrote:
> What frequency did you specify? If you want to turn it off, you have to specify a frequency of 000.000.
Ahh, yes, this worked well.? I had specified a VHF frequency but setting it to 0 cleared it.
I'm having a similar problem the Supplemental Tx I-Gate filter.? I had it set for b/AKQTOR/MHXTOR during Hurricane Dorian but I'd like to clear this out.? Replacing this text with anything or removing it completely doesn't seem to work.
73,
Eric WG3K
|
I'll second the vote for a smaller footprint display, if it's possible.
In my case, I have the Pi hooked into my car's in-dash unit (back-up
camera port), which has a VGA display resolution. Mostly it seems to
affect the configuration pages, where stuff ends up below or off to the
side of the screen, but there aren't any scroll bars to access it. I
think simply triggering the scroll bars for those screens would make it
usable.
Lacking the scroll bars, what I do now is to access the Pi with VNC, and
that display is configured for 1024/768 resolution.
Greg KO6TH
rhclinton wrote:
toggle quoted message
Show quoted text
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
|
Re: Bug: Clearing monitor frequency
-‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 28, 2019 3:11 PM, Andrew P. <andrewemt@...> wrote: You need to press the Enter key after changing the supplemental Tx I-gate filter. That will cause the new expression (which can be a zero-length string) to be applied. Yep, that worked! *sigh* Thanks!
|
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:
toggle quoted message
Show quoted text
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
|
Michael WA7SKG