开云体育

To be clear I'm using a Raspberry Pi 4 for this project with the latest x64 RPI OS. My radio= G90 with a digirig I just attempted this on my Raspberry Pi 5 with the latest x64 RPI OS and fresh

Off work trying to figure this out again... I really do appreciate everyone's help! I did miss the comma after "true" but that didn't seem to change anything. I tried your config but it wouldn't work

My plan was to hang a 32” Vizio TV in my shack and run HamClock and other programs. The Raspberry Pi output to a 42” worked just fine, but when I set it up with the Vizio 32” the image I guess

I appreciate the link and don't know how I missed that post in a search... my apologies.

Here is my working config. "http_addr": "0.0.0.0:8080", "motd": [ "Open source Winlink client - getpat.io" ], "connect_aliases": { "telnet":

/g/KM4ACK-Pi/topic/88592007#msg6997 -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store (

That makes the html fail to load.

Solved the failure to populate at startup with an added @reboot line in the crontab. Does anyone have a thought regarding the small boxes?

Looks like you just need to change rig ptt_ctrl to true. "rig": "my-rig", "ptt_ctrl": true, "beacon_interval": 0, "cwid_enabled": true [email protected]> wrote:

Can you share your config without the user info on top please? or compare to mine. I did try changing "my-rig" to "FLRig" with the same results. "http_addr": "127.0.0.1:8080", "motd": [ "Open source

Pat won't let me get past connecting to test any. I'm using the most reliable gateway that I use on my Windows machine fine. I'm actually hitting it with my rain gutter for an antenna on winlink on

If you can test it on an 80m gateway or any gateway that you know for sure you can reach would be much better. I'm not sure what transceiver you are using but your audio levels are important in the

Thank you for your reply, Lee! In my case is was the rig was @ /usr/bin/rigctl not /usr/local/bin/rigctl I'm connected to the rig now but still having other issues... More info in the post below.

Thanks, Kyle That was my issue getting connected, it was in /usr/bin not /usr/local/bin. Now that I am connected with the rig it does change the freq, however, it just says "dialing..." and doesn't do

Hi Bobby, I had the same issue. What I found in my case using Linux Mint was in Pat menu under Settings/Config - current configuration - the rig control command location was (? /usr/local/bin/rigctl

I recently pulled a long forgotten Build-A-Pi (3B+) out for some updates and noticed 73Linux is the new format. Decided to just do a new build. Install & updates went off without a hitch. As I was

One more thing.? I'm not running the 64 bit version of the OS.? I don't think it's ready for prime time.

Hi Bobby, This is how I set up my G90 to work with VARA 1. Installed the latest firmware for the g90.? This should be 1.8 for the display unit.? This allows you to switch to upper side band digital

Greetings, I have been attempting to get winlink and vara hf to run on my pi 4 with the lastest x64 RPI os. Rig control works fine (Flrig), I can tune in Vara, I can use WSJTX just fine. When I try to

I am running 32-bit "Bookworm" on a RPi4b. Wayland is partly to blame, I thought.? I found out how to switch between Wayland and X11. I thought by switching? back to X11 Conky would function.? I