Status CONNECT
|
Rob Giuliano
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04. I connect to RF ports either through USB COMM port, AGW, or KISS over IP. Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down. It says "CONNECT" until I manually hit Transmit. I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing. The RF port tomeout is Zero (not much RF received the way this is setup. I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself. Maybe not because of the Timeout setting. Anyone else experience this with Windows or Linux and Wine? Robert Giuliano
|
|
|
|
Lynn Deffenbaugh
Does the top line rotate through all of your various ports statuses? It sounds like you may have Configure / Beacon / After Transmit checked. This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent. If your station is fixed, you probably don't want this option checked. That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should. Can you get a screen shot of the "CONNECT"? It's not likely, but
maybe it will reveal something different to me. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 10/21/2020 12:56 PM, Rob Giuliano
via groups.io wrote:
|
|
|
|
Rob Giuliano
Reply in BLUE Robert Giuliano
On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:
Does the top line rotate through all of your various ports
statuses? Yes, rotates through all the connections and all 3 say OK.
It sounds like you may have Configure / Beacon / After Transmit
checked. Nope, Just double checked and that is not set.
This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent. If your station is fixed, you probably don't want this option checked. That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should. Can you get a screen shot of the "CONNECT"? It's not likely, but
maybe it will reveal something different to me. I'll try and enable logging across restart. As is typical, it stops doing it when I try to duplicate. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 10/21/2020 12:56 PM, Rob Giuliano
via groups.io wrote:
I am running APRSIS32 under
WINE 5.0 in Kubuntu 20.04.
I connect to RF ports
either through USB COMM port, AGW, or KISS over IP.
Not always, but often on
first start (after reboot), the connections all say OK, but
the beacon timer underneath does not start counting down.
It says "CONNECT" until I manually hit Transmit. I have
waited longer than the timer to see if it just a timing
issue, but requires a manual TX to start the beaconing.
The RF port tomeout is
Zero (not much RF received the way this is setup.
I think this may be an
issue where the TX request is before the port is fully open,
but it seems this should correct by itself. Maybe not
because of the Timeout setting.
Anyone else experience this
with Windows or Linux and Wine?
Robert Giuliano
|
|
|
|
Lynn Deffenbaugh
I'll try and enable logging across restart. As is typical, it stops doing it when I try to duplicate. Corollary to https://en.wikipedia.org/wiki/Murphy%27s_law When you want something to go wrong, it won't. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 10/21/2020 1:47 PM, Rob Giuliano via
groups.io wrote:
|
|
|
|
Greg D
For what it's worth, I run APRSIS32 on a Linux system under Wine,
and I have not seen this behavior. The only "odd" thing is that the
first start-up after boot creates a small Wine window off to the
side, with nothing in it. No idea what it's for, and closing it has
no apparent effect.
toggle quoted messageShow quoted text
Greg KO6TH Lynn Deffenbaugh wrote:
|
|
|
|
Rob Giuliano
Got it, but once I did the print screen, it seemed to connect.  Now the timer is working  I disabled the logging though, so no logs. I may re-enable them and keep trying. Robert Giuliano
On Wednesday, October 21, 2020, 1:59:58 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:
I'll try and enable logging across restart. As is typical, it stops doing it when I try to duplicate. Corollary to https://en.wikipedia.org/wiki/Murphy%27s_law When you want something to go wrong, it won't. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 10/21/2020 1:47 PM, Rob Giuliano via
groups.io wrote:
Reply in BLUE
Robert Giuliano On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn
Deffenbaugh <kj4erj@...> wrote:
Does the top line rotate through all of your
various ports statuses?
Yes, rotates through all the
connections and all 3 say OK.
It sounds like you may have Configure / Beacon /
After Transmit checked.
Nope, Just double
checked and that is not set.
This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent. If your station is fixed, you probably don't want this option checked. That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should. Can you get a screen shot of the "CONNECT"? It's
not likely, but maybe it will reveal something
different to me.
I'll try and enable
logging across restart. As is typical, it
stops doing it when I try to duplicate.
Lynn
(D) - KJ4ERJ - Author of APRSISCE for Windows Mobile
and Win32
On
10/21/2020 12:56 PM, Rob Giuliano via groups.io
wrote:
I am running APRSIS32 under WINE
5.0 in Kubuntu 20.04.
I connect to RF ports either
through USB COMM port, AGW, or KISS over IP.
Not always, but often on first
start (after reboot), the connections all say
OK, but the beacon timer underneath does not
start counting down. It says "CONNECT" until I
manually hit Transmit. I have waited longer
than the timer to see if it just a timing issue,
but requires a manual TX to start the beaconing.
The RF port tomeout is Zero (not
much RF received the way this is setup.
I think this may be an issue where
the TX request is before the port is fully open,
but it seems this should correct by itself.
Maybe not because of the Timeout setting.
Anyone else experience this with
Windows or Linux and Wine?
Robert Giuliano
|
|
|