John:

On Sat, Feb 20, 2021 at 03:49 AM, John G8BPQ wrote:

It used to be a problem with some browsers, but I thought I'd fixed it - it seems ok with the ones I use here. Which browser are you using?

Chrome.

The Terminal in the Web interface isn't really intended for regular use, just occasional troubleshooting. There are much better terminal programs, eg QtTermTCP.

I was researching that earlier today and have to figure out how to install it.? Another local ham is using it and has had good success.

Thanks.
73 Carmine, K3CWP

VARAFM is running under Wine and I am using VNC for remote windowing
access. I had to make one tweak to Wine to make the USB devices more
distinguishable (adding card # into the descriptive string). This is
only an issue because I have 2 instances of VARAFM running on the same
computer. I will be submitting this back to the Wine project in the
near future.
Otherwise it runs out of the box on a modern version of
Wine (32-bit). I have an automated install based on Debian Buster.

I was pleasantly surprised.

-Doug-

It used to be a problem with some browsers, but I thought I'd fixed it - it seems ok with the ones I use here. Which browser are you using?

The Terminal in the Web interface isn't really intended for regular use, just occasional troubleshooting. There are much better terminal programs, eg QtTermTCP.

OK, I fleshed it out further.? The problem is only with Port 1.? I can save changes on other ports.

Screenshot of how it looks before attempting to change:

Then edited the path (replaced KB9PVH-7 with KB9UNZ-7) and clicked Save.

What I didn't notice previously is it changed to show Port 0 !

Then when I go back to Ports and click Beacons for port 1 it looks the same as where I started.? This is when accessing locally via 127.0.0.1, but I don't think it matters whether I am local or remote.

I suspect I did something to the configuration somewhere a long time ago that caused this.

73,

Lee K5DAT

On Sat, Feb 20, 2021 at 11:42 AM John G8BPQ <john.wiseman@...> wrote:

The message is warning you that you need to be signed in - it isn't saying you aren't signed in. So long as you are on 127.0.0.1 or signed it it will save. If not, you get an error message "Not authorized - please sign in" when you try to save.

At least that is what happens here!

73,
John

On 20/02/2021 17:02, K5DAT wrote:

In PiLinBPQ in the web interface when I select "Ports" and then "Beacons" on any port, I get the message above saying I need to be signed in to save changes. I get this message even after signing in as the sysop.? I also get it when I am on the host computer web browsing to 127.0.0.1 where no signing is normally required. I am not able to save any changes made to the beacons.? The only way I can change them is to edit the UIUtil.cfg file.

This issue has been there for a long time - has not changed through several upgrades. I've been working around it by editing the file, but it would be nice to be able to do it the easy way.

Thanks,

Lee K5DAT

In PiLinBPQ in the web interface when I select "Ports" and then "Beacons" on any port, I get the message above saying I need to be signed in to save changes. I get this message even after signing in as the sysop.? I also get it when I am on the host computer web browsing to 127.0.0.1 where no signing is normally required. I am not able to save any changes made to the beacons.? The only way I can change them is to edit the UIUtil.cfg file.

This issue has been there for a long time - has not changed through several upgrades. I've been working around it by editing the file, but it would be nice to be able to do it the easy way.

Thanks,

Lee K5DAT

?

In my bpq32 windows version

Go to bpq32 console, click windows, click beacon configuration

Ray N3HYM

?

In my bpq32 windows version

Go to bpq32 console, click windows, click beacon configuration

Ray N3HYM

?

In my bpq32 windows version

Go to bpq32 console, click windows, click beacon configuration

Ray N3HYM

?

What type of HF port are you using? Not all support beaconing.

73,
John

Hello,
I am having an issue where my beacon only transmits on AXIP. Is there script in the cfg file I need to massage to make it work on my HF port (port 1) .
Thanks,
Brian WD9HXC

?

?

What type of HF port are you using? Not all support beaconing.

73,
John

Hello,
I am having an issue where my beacon only transmits on AXIP. Is there script in the cfg file I need to massage to make it work on my HF port (port 1) .
Thanks,
Brian WD9HXC

?

Hello,
I am having an issue where my beacon only transmits on AXIP. Is there script in the cfg file I need to massage to make it work on my HF port (port 1) .
Thanks,
Brian WD9HXC

Hi Ken,

The web version is not working for me for some reason, so I set the timings in the cfg file, but it does not seem to have any effect on it.?

The hf port works as I can connect and transmit...etc, just can't get the beacon to send on any port but axip.

Thanks,

--Brian

On Sat, Feb 20, 2021, 8:04 AM Ken <ken@...> wrote:

Hi Brian,

Your BTINTERVAL or IDINTERVAL? may not be set in the config file.
I recommend you set your Beacons up in Web Node under Ports.
That way you can change them on the fly without rebooting
BPQ.

I have both my BTINTERVAL and IDINTERVAL set to 0 in the config
file, then use the Port > Beacon setup.

73,
Ken W9GM

On 2/20/2021 7:47 AM, Brian Vodvarka wrote:

Hello,
I am having an issue where my beacon only transmits on AXIP. Is there script in the cfg file I need to massage to make it work on my HF port (port 1) .
Thanks,
Brian WD9HXC

Hello,
I am having an issue where my beacon only transmits on AXIP. Is there script in the cfg file I need to massage to make it work on my HF port (port 1) .
Thanks,
Brian WD9HXC