开云体育

Hi Jason, Making that change made no difference. However... Changing my callsign to all uppercase seems to have fixed some of the problems! It appears that when I entered my callsign in lowercase, the

We are all learning as we go. When we stop learning, we might as well give it up. ? it just gets frustrating sometimes. Can’t thank Jason enough for his time and effort as well. Truly a wealth of

Thanks Anthony. I had selected the right gps but when I set up rig control, selecting rigcat I selected enable flirt xcvr control with fldigi as client. I stopped selecting rigcat and it works great

Jason, This is what I got: pi@raspberrypi:~ $ rigctl -vvv -m 1 f Opened rig model 1, 'Dummy' 145000000 BUT... I did get the same error when I ran the Direwolf -p command this time. It first asked me

I had the same issue with flrig not keeping the settings and it turned out to be the wrong USB driver selected. Don’t know if that is your situation. I was using USB0 because that was what was

I am having the same problem. I followed the steps Jason sent out a few days ago written by another ham. It seems to try and connect but times out and says it can not connect. Also, flrig doesn’t

Yes, it remains green. rigctl: /usr/bin/rigctl /usr/local/bin/rigctl /usr/share/man/man1/rigctl.1.gz

Hi Everytime I restart my BAP, Conky starts up with it, bur some og the text in the display I am not able to read because the are blurry or Pixel'd (See attached photo) Whem I do a start Conky again,

Change the APRS path to CQ,ARISS and try it again. -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store (

You may have run into a bug concerning the newest version of hamlib (4.3). Run the following command and post the results please: *rigctl -vvv -m 1 f* -- 73, de KM4ACK YouTube (

Hi Jason, That gets rid of the error opening hamlib... But it still produces errors when trying to transmit. It gives an *Invalid Command* error: *n3jf-6>wide2-2:>n3jf Stationary* *Invalid command.

Sorry for the delayed response. Had to go back and look at the code. Rig control wasn't built into the app but should be easy enough to manually start. With FLRIG open, run the following command:

Executing conky from a terminal screen results in an otherwise behind the scenes warning that continues every conky screen update/repaint. The warning is: “awk: warning: escape sequence `\'' treated

Hi Jason, Yes, FLrig is running and working before starting Pi-APRS. My Pi-APRS *config* file is the following: MYCALL=n3jf SSID=6 CITY=Aliso-Viejo???? [Note: Separating the city into two words,

Let me add that I’m using the Sobrent sound card to connect pi and 818ND Richard

I've read over the issues about the FT818 can't use the FT-817 settings but as I try to work through finding something that does work (857??) I get the following after I start the Packet Modem in

I know this now.? I didn't know this on the mountain.? Thanks for the suggestion and work-around. 73 Dave

Conky Custom Settings - /g/KM4ACK-Pi/message/4678 Icom 7100 Setup - /g/KM4ACK-Pi/topic/85692067 Icom 7300 Setup - /g/KM4ACK-Pi/message/3838 Lab599

I ran into something odd helping a Patron setup his Pi with Pat last night. Does rigctl remain green in conky after starting the ARDOP modem? Please run this command and post the results: *whereis

Please post your Pi-APRS settings. Do you have FLRIG open before starting the program? -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter (