|
FLRIG works fine with FLDIGI and WSJT-x
ARDOP and PAT does not change the radio frequency nor activate the PTT when
I select "Action/Connect" on the PAT menu and then select an RMS from the list.
The same happens if I use "Find WINLINK Gateways"
This is a new build on a new RP 4B
BAP v3.1.0 - all patches added
FLRIG v1.4.2
Pat Menu v2.3
ARDOPC v1.0.4.1j
Pat v0.11.0
PTT set to TRUE in Manage PAT/Set ARDOP PTT
#Config file for Pat Menu
#20200429 KM4ACK
MYCALLSIGN=AK4NG
MAP=usa
RIGCONTROL=yes
ARDOP="/home/pi/ardop/./piardopc 8515 plughw:2,0 plughw:2,0"
ARDOPGUI="/home/pi/ardop/./piARDOP_GUI"
DIREWOLF="direwolf -p"
KISS="sudo /usr/sbin/kissattach /tmp/kisstnc"
AXP=wl2k
RIG="/usr/local/bin/rigctl -m 4"
MODEHF=USB
MODE2M=FM
PORT=8080
LOG=/home/pi/Documents/mylog.txt
AMRRON=no
|
I have same problem here.? Only difference in setting is mine use 5000 instead of 8080
What i also noted is that rigcontrol in conkey does not go green -? In older version it used to go green but did not go red after closing down of pat winlink. Then i had to reboot pi otherwise other apps dont work as stand alone without flrig
Wsjt-x was not working but after installing the patch i cganged settings to another radio and then changed it back to correct radio and now it is working with new patch. Thanks for that solution Jason.? Greetings from the Namib
Pieter Jacobs De v51pj 73
toggle quoted message
Show quoted text
On 12 Sep 2021, at 00:38, ham123789 <ribet@...> wrote:
? [Edited Message Follows]
FLRIG works fine with FLDIGI and WSJT-x ARDOP and PAT does not change the radio frequency nor activate the PTT when I select "Action/Connect" on the PAT menu and then select an RMS from the list. The same happens if I use "Find WINLINK Gateways" This is a new build on a new RP 4B BAP v3.1.0 - all patches added FLRIG v1.4.2 Pat Menu v2.3 ARDOPC v1.0.4.1j Pat v0.11.0 PTT set to TRUE in Manage PAT/Set ARDOP PTT #Config file for Pat Menu #20200429 KM4ACK MYCALLSIGN=AK4NG MAP=usa RIGCONTROL=yes ARDOP="/home/pi/ardop/./piardopc 8515 plughw:2,0 plughw:2,0" ARDOPGUI="/home/pi/ardop/./piARDOP_GUI" DIREWOLF="direwolf -p" KISS="sudo /usr/sbin/kissattach /tmp/kisstnc" AXP=wl2k RIG="/usr/local/bin/rigctl -m 4" MODEHF=USB MODE2M=FM PORT=8080 LOG=/home/pi/Documents/mylog.txt AMRRON=no
|
FLRIG works fine with FLDIGI and WSJT-x
ARDOP and PAT does not change the radio frequency nor activate the PTT when
I select "Action/Connect" on the PAT menu and then select an RMS from the list.
In the pat connect screen does the frequency populate into the box when you choose an alias? If so, does the box turn green or red? --
73, de KM4ACK
|
|
|
Hi Jason it does put the freq in the block and with a line through it but then in the black screen it also say it cant connect which i assume is via ip to the flrig package
Also rigcontrol on conkey stay red
Busy with brand new build again then i will test again after latest patches installed and come vack to you
.?
Greetings from the Namib
Pieter Jacobs V51pj 73
toggle quoted message
Show quoted text
On 12 Sep 2021, at 13:39, km4ack <jason.oleham@...> wrote:
? FLRIG works fine with FLDIGI and WSJT-x
ARDOP and PAT does not change the radio frequency nor activate the PTT when
I select "Action/Connect" on the PAT menu and then select an RMS from the list.
In the pat connect screen does the frequency populate into the box when you choose an alias? If so, does the box turn green or red? --
73, de KM4ACK
|
|
|
On Sun, Sep 12, 2021 at 07:52 AM, Pieter V51PJ wrote:
Also rigcontrol on conkey stay red
Rig control staying red in Conky indicates that it isn't running. If it isn't running, Pat will not be able to control the rig. If you run into the same thing on the new system, let me know. I wouldn't apply the patch for hamlib4.2 until I tested the new system. You may not need that patch. ? --
73, de KM4ACK
|
|
|
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
|
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
|
|
|
rigctl --version
rigctl Hamlib 4.3 Wed Sep 01 02:14:39 2021 +0000 SHA=5a6134
|
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
|
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
|
|
|
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
|
|
|
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
|
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
|
|
|
On Mon, Sep 13, 2021 at 10:12 AM, ham123789 wrote:
rigctl -vvv -m 1 f
I solved the issue by re-installing Hamlib and now Fldigi, WSJT-x, JS8CALL and Pat applications all work using Flrig. I am assuming that something had gotten set wrong in the Hamlib config files and that a re-install corrected it Thanks, George AK4NG
|
Tested pat winlink this morning again and get a time out io error on black screen of pat mail screen I think a setting ??
All was working fine yesterday. I did a reboot too, but it stay same Freq written in blick and then red line through it. Qso error
Rigctl green Flrig green Ardop Green
Any suggestion where to look please? Greetings from the Namib
Pieter Jacobs De v51pj 73
toggle quoted message
Show quoted text
On 13 Sep 2021, at 21:49, ham123789 <ribet@...> wrote:
?On Mon, Sep 13, 2021 at 10:12 AM, ham123789 wrote:
rigctl -vvv -m 1 f
I solved the issue by re-installing Hamlib and now Fldigi, WSJT-x, JS8CALL and Pat applications all work using Flrig. I am assuming that something had gotten set wrong in the Hamlib config files and that a re-install corrected it Thanks, George AK4NG
|
km4ack