It could have something to do with the way you fixed your other issue. Since I don't know specifically what you did while manually editing things, I have no way of know the current state of the Pi. It might be best to start with a fresh build and not manually edit the files but use hotspot tools to manage the hotspot. --
73, de KM4ACK
|
|
|
Let's make sure we are talking about the same GPS If so, you should see a green blinking light on the GPS unit once it has a lock. Software on the Pi (installed or not) will not have any impact on the GPS unit getting a lock. If you don't have the green blinking light, the Pi will never get a grid because the GPS doesn't have a fix on the satellites. --
73, de KM4ACK
|
|
|
Re: FLRIG loses connectivity with 891
I ¡®choked¡¯ every cable to the Pi and that solved my problem. ?Thanks Brian.
|
|
|
Ok did the patch for hamlib. It installed
I restart rpi And start flrig Then i started pat menu and start ardop modem. Ardop off red turned to ardop on green Rigctl off red went to rigctl on green
But then i went to mailbox. Select a sysop and freq changed but end up with qso failure and line through freq
I did also rigctl -vvv -m 1 f Screen message as follows Opened rig mode 1 ¡®Dummy¡¯ Rigctl_parse: rig not open¡trying to reopen Rigctl_parse: RIG EIO? main: i/o error main: rig_close retcode=-1 main: rig_open retcode = 0
I then realized i started flrig with old hamlib? I loaded any radio in and then re added icom 7100. Enter init and i tried pat menu again Start ardop modem Rigctl on green Select sysop Freq select And ready for qso And all 100% working now
Thanks Jason for walking us through step by step. Much appreciated
Only qsstv that still have a problem with ptt but that is a qsstv issue after they upgraded. They must still sort their version out Greetings from the Namib
Pieter Jacobs De v51pj Pieter Jacobs
toggle quoted message
Show quoted text
On 13 Sep 2021, at 15:12, Pieter V51PJ via groups.io <v51pj@...> wrote:
? Ok did the test and screen say
Opened rig model 1, ¡®Dummy¡¯ 14500000
But rigctl in conkey is still red and off
What is interesting is that wsjtx, flrig, jtdx,js8call and cqrlog all work. But i think they have hamlib as part of them package and not looking at external hamlib maybe?
When i start pat menu and it ends with pat mailbox running then in black screen in mailbox the following
Unable to get frequency from rig my-rig : dial tcp 127.0.0.1:4532: ?connect : connection refused
Should rig my-rig not have a name pointing to what radio i use. Like icom 7100?
Greetings from the Namib
Pieter Jacobs De v51pj 73 On 13 Sep 2021, at 14:06, km4ack <jason.oleham@...> wrote:
?On Mon, Sep 13, 2021 at 12:31 AM, Pieter V51PJ wrote:
Rigctl ¡ªversion
Then it reply with
? ? ? ?rigctl(d), Hamlib 3.3
This is a pretty old version of hamlib. 4.3 is the latest version. You might try updating to a more current version. You can use the BAP update tool to update. Both of you should run the following command: rigctl -vvv -m 1 fand see if you get any errors. ? --
73, de KM4ACK
|
|
|
Here is what I get:
pi@AK4NG-pi4B:~ $ rigctl -vvv -m 1 f
Opened rig model 1, 'Dummy'
rigctl_parse: rig not open...trying to reopen
rigctl_parse: RIG_EIO?
main: i/o error
main: rig_close retcode=-1
main: rig_open retcode=0
|
Thanks, that works
George - AK4NG
|
Ok did the test and screen say
Opened rig model 1, ¡®Dummy¡¯ 14500000
But rigctl in conkey is still red and off
What is interesting is that wsjtx, flrig, jtdx,js8call and cqrlog all work. But i think they have hamlib as part of them package and not looking at external hamlib maybe?
When i start pat menu and it ends with pat mailbox running then in black screen in mailbox the following
Unable to get frequency from rig my-rig : dial tcp 127.0.0.1:4532: ?connect : connection refused
Should rig my-rig not have a name pointing to what radio i use. Like icom 7100?
Greetings from the Namib
Pieter Jacobs De v51pj 73
toggle quoted message
Show quoted text
On 13 Sep 2021, at 14:06, km4ack <jason.oleham@...> wrote:
?On Mon, Sep 13, 2021 at 12:31 AM, Pieter V51PJ wrote:
Rigctl ¡ªversion
Then it reply with
? ? ? ?rigctl(d), Hamlib 3.3
This is a pretty old version of hamlib. 4.3 is the latest version. You might try updating to a more current version. You can use the BAP update tool to update. Both of you should run the following command: rigctl -vvv -m 1 fand see if you get any errors. ? --
73, de KM4ACK
|
|
|
I am running 3.08 and I havent had a green light at all?
|
On Mon, Sep 13, 2021 at 12:31 AM, Pieter V51PJ wrote:
Rigctl ¡ªversion
Then it reply with
? ? ? ?rigctl(d), Hamlib 3.3
This is a pretty old version of hamlib. 4.3 is the latest version. You might try updating to a more current version. You can use the BAP update tool to update. Both of you should run the following command: rigctl -vvv -m 1 fand see if you get any errors. ? --
73, de KM4ACK
|
|
|
I just remembered the other thread where you had trouble with the WiFi. If you used hotspot tools to disable the hotspot, this would explain the hostapd.service not being available. --
73, de KM4ACK
|
|
|
Do you have a green blinking light on the GPS itself? If not, then the GPS doesn't have a fix. Which version of BAP are you running? ? --
73, de KM4ACK
|
|
|
The answer is in this video Note: the menus have changed since the video was done but the principal is the same. There are also other posts on this forum that include other ways to work through this. --
73, de KM4ACK
|
|
|
Try using Hotspot Tools instead of manually using the terminal. --
73, de KM4ACK
|
|
|
I'm running a pi4 8gb?
The error I keep getting is a "gpg no public key".
I have followed the?https://youtu.be/YIIC-iT6H-s video and haven't been able to get my GPS to work at all its the ublox7. I follow the steps and when I run cgps I get blank except on "NO FIX" and it never connects even out side for over an hour with a goof sky view. What am I doing wrong? Any help would be greatly appreciated?
|
Did a brand new install using BAP on www Rigctl ¡ªversion Then it reply with ? ? ? ?rigctl(d), Hamlib 3.3 Am i using the right BAP version? Greetings from the Namib
Pieter Jacobs De V51pj 73
toggle quoted message
Show quoted text
On 13 Sep 2021, at 04:53, ham123789 <ribet@...> wrote:
?rigctl --version
rigctl Hamlib 4.3 Wed Sep 01 02:14:39 2021 +0000 SHA=5a6134
|
Running a new Rasberry Pi 4B 8gb with the OS:
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
Problem: As long as there is a monitor plugged into the HDMI0 port,
I can use VNC to remotely access the Pi. If I unplug the monitor, reboot and
attempt to connect with VNC, following the login, I get a small window with
the message "Cannot currently show the desktop".
If I use SSH to login and run HTOP, it appears than none of the X window
services are running when I boot without a monitor plugged into the Pi.
Any suggestions? How do I force the windowing system to always start?
George - AK4NG
|
rigctl --version
rigctl Hamlib 4.3 Wed Sep 01 02:14:39 2021 +0000 SHA=5a6134
|
|
|
On Sun, Sep 12, 2021 at 11:01 AM, ham123789 wrote:
When I first built the Pi4B with BAP 3.08, the frequency would populate into the Pat window box but a red line would appear through the box with an error message indicating a failure to communicate with the radio.
After I did an upgrade of BAP to v3.1 (with all the upgrades), Pat populates the box and goes through a full attempt to connect to the RMS - as though it is actually controlling the radio and getting CAT responses from the radio. Of course, the connection fails because the radio is never tuned to the frequency nor is PTT activated.
Is there some other date you need to assist me?
Thanks, George - AK4NG
Which version of hamlib are you running? If unsure, run this command: rigctl --version? --
73, de KM4ACK
|
|
|
km4ack
Loyd