I went to use the CW split on my RigPi this weekend and it didn't work. I ran into this issue before, if it is in split CW it won't send. I don't know yet what the issue is. It is hard from RigPi interface if maybe VFOB was in USB mode or something else. I know Mike fixed something before for me with this exact problem and it worked. I did contact Howard and he told me to ask over here.
I don't know if RigPi is suppose to set the mode or hamlib is (I haven't been in front of the radio to see myself). Using Flrig I set it manually but it didn't seem to carry over to when I went back to the rigpi hamlib screen. Or the patch was overridden with a later release of hamlib which it appears I am on HamLib 5 now.
Any help would be appreciated.
73, Kevin, W4RKU
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I went to use the CW split on my RigPi this weekend and it didn't work. I ran into this issue before, if it is in split CW it won't send. I don't know yet what the issue is. It is hard from RigPi interface if maybe VFOB was in USB mode or something else. I know Mike fixed something before for me with this exact problem and it worked. I did contact Howard and he told me to ask over here.
I don't know if RigPi is suppose to set the mode or hamlib is (I haven't been in front of the radio to see myself). Using Flrig I set it manually but it didn't seem to carry over to when I went back to the rigpi hamlib screen. Or the patch was overridden with a later release of hamlib which it appears I am on HamLib 5 now.
Any help would be appreciated.
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Without a -m switch you're talking to the dummy rig.And you can also stack up the commands.
rigctl -m 2 v m f
Not sure if this works
rigctl -m 2 --vfo v m VFOA m VFOB f VFOA f VFOB
Mike W9MDB
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Without a -m switch you're talking to the dummy rig.And you can also stack up the commands.
rigctl -m 2 v m f
Not sure if this works
rigctl -m 2 --vfo v m VFOA m VFOB f VFOA f VFOB
Mike W9MDB
On Wednesday, July 6, 2022 at 04:39:18 PM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
rigctl_parse: input_line: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
rigctl_parse: vfo_opt=0
3:rigctl_parse.c(2251):rigctl_set_vfo entered
rig_parse_vfo called
rig_parse_vfo: 'VFOAM' not found so vfo='None'
Invalid parameter
Precede multiple character command names with '\'
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 14:33
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Could you please test the latest?At least the problems taking it out of
split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence
please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
Sitting here at the rig itself I have been using rigctl interactively. I am
having problems still. If I am use the "X" command. See below and if I am
doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x
or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
You can via the radio. I looked at the CAT commands extensively. In the
addendum you can issue the OI command the refers to split but it also says
it is referring to the memory channel.
Here is the real kicker, if you were to look at the computer commands in the
manual under "IF" command (which looks like a read only command) under
answer byte P12 it says "Split operation status. See SP command". However
there is no SP command documented! There also seems to be a lot of cross
over between the TS-480 and the TS2K.
Frankly I always considered you the expert on this stuff. I see you do a
lot for Flrig and digi. This stuff is in my wheelhouse but without
documentation I don't know. I can send command via Flrig and see what
happens.
I would be willing to help figure this out some how. If you want to take
this off group that is fine too.
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there.
Linux/Unix/Mac users need to compile the latest tar file from http://n0nb.users.sourceforge.net/\
Note: If compiling on Unix-like systems please uninstall any Hamlib package you have before installing the new build
3 If you don't save directly you need to open a file browser and move the file that way.
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Thanks again.
Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 08:12
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
It's not their own versions -- they just rename it so it doesn't conflict
with the standard names of rigctl and rigctld.
You can just copy the rigctl and rigctld over the wsjtx versions.
Mike W9MDB
On Wednesday, July 27, 2022 at 10:52:54 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Ok here is where I stand. As you know this all started with me to get it to work on the RigPi. So I have been testing using direct as well as via hamlib with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I realized that I installed WSJT-X using the deb. So I built WSJT-X from the source. The result is better. If I disconnect the RigPi application and go to direct to the TS-2000 using WSJT-X it works! However if I set it to Hamlib (see attached) I get the following errors:
JTDX does work with the Hamlib as the rig. One thing I noticed that caught my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld were (the copying didn't work as you said. Here is the listing:
The size difference will be the diff between static and dynamic build.
Compiling Hamlib by default will give you dynamic which means you need to ensure you remove any system hamlib packages.
If you do
ldd rigctl
It will show you the libraries it references and you should see /usr/local/lib/libhamlib*
If you see /usr/lib/libhamlib* then you have a hamlib package installed that must be removed.
Ok here is where I stand. As you know this all started with me to get it to work on the RigPi. So I have been testing using direct as well as via hamlib with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I realized that I installed WSJT-X using the deb. So I built WSJT-X from the source. The result is better. If I disconnect the RigPi application and go to direct to the TS-2000 using WSJT-X it works! However if I set it to Hamlib (see attached) I get the following errors:
JTDX does work with the Hamlib as the rig. One thing I noticed that caught my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld were (the copying didn't work as you said. Here is the listing:
The size difference will be the diff between static and dynamic build.
Compiling Hamlib by default will give you dynamic which means you need to
ensure you remove any system hamlib packages.
If you do
ldd rigctl
It will show you the libraries it references and you should see
/usr/local/lib/libhamlib*
If you see /usr/lib/libhamlib* then you have a hamlib package installed that
must be removed.
Mike W9DMB
On Wednesday, July 27, 2022 at 06:17:41 PM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Ok here is where I stand. As you know this all started with me to get it to
work on the RigPi. So I have been testing using direct as well as via hamlib
with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I
realized that I installed WSJT-X using the deb. So I built WSJT-X from the
source. The result is better. If I disconnect the RigPi application and go
to direct to the TS-2000 using WSJT-X it works! However if I set it to
Hamlib (see attached) I get the following errors:
JTDX does work with the Hamlib as the rig. One thing I noticed that caught
my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld
were (the copying didn't work as you said. Here is the listing:
I went to use the CW split on my RigPi this weekend and it didn't work. I ran into this issue before, if it is in split CW it won't send. I don't know yet what the issue is. It is hard from RigPi interface if maybe VFOB was in USB mode or something else. I know Mike fixed something before for me with this exact problem and it worked. I did contact Howard and he told me to ask over here.
I don't know if RigPi is suppose to set the mode or hamlib is (I haven't been in front of the radio to see myself). Using Flrig I set it manually but it didn't seem to carry over to when I went back to the rigpi hamlib screen. Or the patch was overridden with a later release of hamlib which it appears I am on HamLib 5 now.
Any help would be appreciated.
73, Kevin, W4RKU
Rig Pi is supposed to set the mode -- Hamlib just does what it is told to do.
Mike W9MDB
I went to use the CW split on my RigPi this weekend and it didn't work. I ran into this issue before, if it is in split CW it won't send. I don't know yet what the issue is. It is hard from RigPi interface if maybe VFOB was in USB mode or something else. I know Mike fixed something before for me with this exact problem and it worked. I did contact Howard and he told me to ask over here.
I don't know if RigPi is suppose to set the mode or hamlib is (I haven't been in front of the radio to see myself). Using Flrig I set it manually but it didn't seem to carry over to when I went back to the rigpi hamlib screen. Or the patch was overridden with a later release of hamlib which it appears I am on HamLib 5 now.
Any help would be appreciated.
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Thank you for your answer.
73, Kevin, W4RKU
Without a -m switch you're talking to the dummy rig.And you can also stack up the commands.
rigctl -m 2 v m f
Not sure if this works
rigctl -m 2 --vfo v m VFOA m VFOB f VFOA f VFOB
Mike W9MDB
Mike,
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Thank you for your answer.
73, Kevin, W4RKU
Attachments:
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Awesome – thank you for the tutorial. Will save this and good to know if I have to set thing manually via the console.
Thanks much!
73, Kevin W4RKU
From: discussion@hamlib.p.re.sourceforge.net discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 6, 2022 18:02
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Without a -m switch you're talking to the dummy rig.And you can also stack up the commands.
rigctl -m 2 v m f
Not sure if this works
rigctl -m 2 --vfo v m VFOA m VFOB f VFOA f VFOB
Mike W9MDB
On Wednesday, July 6, 2022 at 04:39:18 PM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
I pretty much agree with you after going to the remote station today and there are some issues in the logic in rigpi. I think you patch was before V3 of rigpi came out. So I upgraded I may not tried using remote split since.
I do have a question, and that might be my misunderstanding of how things work.
Obviously the RigPi runs rigctld.
With Rigpi displaying the radio frequency (picture of rig frequency display attached). I ran the following commands using rigctl. Why am I getting these returns?
pi@rigpi3:~ $ rigctl v
VFOA
pi@rigpi3:~ $ rigctl m
FM
15000
pi@rigpi3:~ $ rigctl f
145000000
Obviously they don't match what RigPi and what the radio is showing?
Thank you for your answer.
73, Kevin, W4RKU
Attachments:
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000 https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit=25#b5f1/04a4
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
Please run this
rigctl -m 2014 -r com1 -s 9600 --vfo -vvvvv -Z M VFOA USB -1 M VFOB USB -1 S VFOA 1 VFOB X CW 500 m VFOA m VFOB >log.txt 2>&1
And send me the log.txt file.
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
I did install the latest and seems to be working. However when I used your command request this is the result:
Rig command: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
set_vfo: error = kenwood.c(682):kenwood_safe_transaction returning2(0)
kenwood2rmode called
kenwood.c(2700):kenwood_get_mode returning2(0)
rig.c(4467) trace
kenwood_set_vfo called vfo=currVFO, is_emulation=0, curr_mode=
kenwood.c(1153) trace
kenwood.c(1155):kenwood_set_vfo returning2(0)
3:rigctl_parse.c(2931):rigctl_get_split_mode returning(0)
rigctl_parse: called, interactive=1
rigctl_parse: input_line: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
rigctl_parse: vfo_opt=0
3:rigctl_parse.c(2251):rigctl_set_vfo entered
rig_parse_vfo called
rig_parse_vfo: 'VFOAM' not found so vfo='None'
Invalid parameter
Precede multiple character command names with '\'
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 14:33
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000 https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit=25#dbb3/f323
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
I'm sorry...that email was not formatted correctly.
Commands are as follows on separate lines.
V VFOA
M USB -1
V VFOB
M CW -1
V VFOA
m
V VFOB
m
Mike W9MDB
On Tuesday, July 26, 2022 at 02:43:43 PM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
I did install the latest and seems to be working. However when I used your command request this is the result:
Rig command: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
set_vfo: error = kenwood.c(682):kenwood_safe_transaction returning2(0)
kenwood2rmode called
4:rig.c(2464):rig_passband_normal entered
4:rig_passband_normal: return filter#1, width=600
4:rig.c(2485):rig_passband_normal returning(600)
kenwood.c(2700):kenwood_get_mode returning2(0)
rig.c(4467) trace
4:kenwood.c(1103):kenwood_set_vfo entered
kenwood_set_vfo called vfo=currVFO, is_emulation=0, curr_mode=
kenwood.c(1153) trace
kenwood.c(1155):kenwood_set_vfo returning2(0)
4:rig.c(4486):rig_get_split_mode returning(0)
3:rigctl_parse.c(2931):rigctl_get_split_mode returning(0)
rigctl_parse: called, interactive=1
rigctl_parse: input_line: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
rigctl_parse: vfo_opt=0
3:rigctl_parse.c(2251):rigctl_set_vfo entered
rig_parse_vfo called
rig_parse_vfo: 'VFOAM' not found so vfo='None'
Invalid parameter
Precede multiple character command names with '\'
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 14:33
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Could you please test the latest?At least the problems taking it out of split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy <krutzy@users.sourceforge.net krutzy@users.sourceforge.net > wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am having problems still. If I am use the "X" command. See below and if I am doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000 https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit=25#dbb3/f323
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
Below is the session I just did. Oddly the only thing that didn't work is
the "m" when it was set to VFOA. Other than that all looked fine.
Kevin
rigctl -m 2014 -r /dev/ttyUSB1 -s 38400
Rig command: V VFOA
Rig command: M USB -1
Rig command: V VFOB
Rig command: M CW -1
Rig command: V VFOA
Rig command: m
Rig command: V VFOB
Rig command: m
Mode: CW
Passband: 600
Rig command:
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 16:34
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
I'm sorry...that email was not formatted correctly.
Commands are as follows on separate lines.
V VFOA
M USB -1
V VFOB
M CW -1
V VFOA
m
V VFOB
m
Mike W9MDB
On Tuesday, July 26, 2022 at 02:43:43 PM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
I did install the latest and seems to be working. However when I used your
command request this is the result:
Rig command: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
set_vfo: error = kenwood.c(682):kenwood_safe_transaction returning2(0)
kenwood2rmode called
4:rig.c(2464):rig_passband_normal entered
4:rig_passband_normal: return filter#1, width=600
4:rig.c(2485):rig_passband_normal returning(600)
kenwood.c(2700):kenwood_get_mode returning2(0)
rig.c(4467) trace
4:kenwood.c(1103):kenwood_set_vfo entered
kenwood_set_vfo called vfo=currVFO, is_emulation=0, curr_mode=
kenwood.c(1153) trace
kenwood.c(1155):kenwood_set_vfo returning2(0)
4:rig.c(4486):rig_get_split_mode returning(0)
3:rigctl_parse.c(2931):rigctl_get_split_mode returning(0)
rigctl_parse: called, interactive=1
rigctl_parse: input_line: V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
rigctl_parse: vfo_opt=0
3:rigctl_parse.c(2251):rigctl_set_vfo entered
rig_parse_vfo called
rig_parse_vfo: 'VFOAM' not found so vfo='None'
Invalid parameter
Precede multiple character command names with '\'
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 14:33
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Could you please test the latest?At least the problems taking it out of
split should be fixed now.
Can you actually set a different mode on VFOB? Can you do this sequence
please and show me the results.
V VFOAM USB -1V VFOBM CW -1V VFOAmV VFOBm
Mike W9MDB
On Tuesday, July 12, 2022 at 12:13:18 AM CDT, Kevin Utzy
<krutzy@users.sourceforge.net krutzy@users.sourceforge.net
krutzy@users.sourceforge.net%20krutzy@users.sourceforge.net%20 >
wrote:
Mike,
Sitting here at the rig itself I have been using rigctl interactively. I am
having problems still. If I am use the "X" command. See below and if I am
doing something wrong:
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 0
Rig command: X CW 600
Rig command: s
Split: 1
TX VFO: VFOB
Rig command: x
TX Mode: USB
TX Passband: 2200
Rig command: X CW 600
Rig command: X
TX Mode: CW
TX Passband: 600
The X command does nothing. Even interactive. Sometimes when issuing the x
or the X took the radio out of split.
The version is: 4.5~git from indeterminate source revision.
Is this an issue or something else I need to do?
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit=2
5#dbb3/f323
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit= 25#dbb3/f323/1b6f/9e0d
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Mike,
I tried it again and got different results
Rig command: V VFOA
Rig command: M USB -1
Rig command: V VFOB
Rig command: M CW -1
Rig command: V VFOA
Rig command: m
Mode: CW
Passband: 600
Rig command: V VFOB
Rig command: m
Mode: CW
Passband: 600
Though I would share this too.
Kevin
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
On Tuesday, July 26, 2022 at 05:07:07 PM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
I tried it again and got different results
Rig command: V VFOA
Rig command: M USB -1
Rig command: V VFOB
Rig command: M CW -1
Rig command: V VFOA
Rig command: m
Mode: CW
Passband: 600
Rig command: V VFOB
Rig command: m
Mode: CW
Passband: 600
Though I would share this too.
Kevin
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
You can via the radio. I looked at the CAT commands extensively. In the
addendum you can issue the OI command the refers to split but it also says
it is referring to the memory channel.
Here is the real kicker, if you were to look at the computer commands in the
manual under "IF" command (which looks like a read only command) under
answer byte P12 it says "Split operation status. See SP command". However
there is no SP command documented! There also seems to be a lot of cross
over between the TS-480 and the TS2K.
Frankly I always considered you the expert on this stuff. I see you do a
lot for Flrig and digi. This stuff is in my wheelhouse but without
documentation I don't know. I can send command via Flrig and see what
happens.
I would be willing to help figure this out some how. If you want to take
this off group that is fine too.
73,
Kevin
W4RKU
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
Linux/Unix/Mac users need to compile the latest tar file from http://n0nb.users.sourceforge.net/\
Note: If compiling on Unix-like systems please uninstall any Hamlib package you have before installing the new build
3 If you don't save directly you need to open a file browser and move the file that way.
If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Thanks again.
Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 08:12
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
Linux/Unix/Mac users need to compile the latest tar file from
http://n0nb.users.sourceforge.net/\ http://n0nb.users.sourceforge.net/
Note: If compiling on Unix-like systems please uninstall any Hamlib package
you have before installing the new build
3 If you don't save directly you need to open a file browser and move the
file that way.
If you're not familiar with that here's a video on the file browser -
https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit= 25#dbb3/f323/1b6f/9e0d/7ce1/fba8/ddbc/5cb4
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
It's not their own versions -- they just rename it so it doesn't conflict with the standard names of rigctl and rigctld.
You can just copy the rigctl and rigctld over the wsjtx versions.
Mike W9MDB
On Wednesday, July 27, 2022 at 10:52:54 AM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Thanks again.
Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 08:12
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
Linux/Unix/Mac users need to compile the latest tar file from
http://n0nb.users.sourceforge.net/\ http://n0nb.users.sourceforge.net/
Note: If compiling on Unix-like systems please uninstall any Hamlib package
you have before installing the new build
3 If you don't save directly you need to open a file browser and move the
file that way.
If you're not familiar with that here's a video on the file browser -
https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit= 25#dbb3/f323/1b6f/9e0d/7ce1/fba8/ddbc/5cb4
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Ah - ok thanks Mike - very good. That was always a head scratcher.
I'll let you know later today.
73, Kevin
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 12:20
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
It's not their own versions -- they just rename it so it doesn't conflict
with the standard names of rigctl and rigctld.
You can just copy the rigctl and rigctld over the wsjtx versions.
Mike W9MDB
On Wednesday, July 27, 2022 at 10:52:54 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
One clarification since this is on the RPI, after I rebuild the latest
hamlib, wouldn't I also need to rebuild WSJTX and JTDX to recreate the
rigctl and rigctld versions. I have wondered for a while why they used
their own versions.
Thanks again.
Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 08:12
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
Please try the latest hamlib in both WSJTX and JTDX -- Rig Split should be
working.
New hamlib for installation directions
1 Shut down WSJTX/JTDX
2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you
multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and
replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
Linux/Unix/Mac users need to compile the latest tar file from
http://n0nb.users.sourceforge.net/\ http://n0nb.users.sourceforge.net/
http://n0nb.users.sourceforge.net/
Note: If compiling on Unix-like systems please uninstall any Hamlib package
you have before installing the new build
3 If you don't save directly you need to open a file browser and move the
file that way.
If you're not familiar with that here's a video on the file browser -
https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
On Wednesday, July 27, 2022 at 12:54:41 AM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Related issue. WSJT-X and JTDX have their own versions of rigctl and
rigctld. With WSJT-X 2.5.4 I have to use under "Split" I have to use "fake
it". That didn't happen before. But the older JTDX 2.2.0-rc155 I can use
"Rig".
So the same thing must be happening - because WSJT-X use to work just fine
with "Rig".
Just something I thought about.
73, Kevin, W4RKU
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Tuesday, July 26, 2022 18:56
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
So it would appear there is no ability to set VFOB mode different from VFOA.
That's what I thought.
Mike W9MDB
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit=
25#dbb3/f323/1b6f/9e0d/7ce1/fba8/ddbc/5cb4
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit= 25#dbb3/f323/1b6f/9e0d/7ce1/fba8/ddbc/5cb4/763c/f94b
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
Mike,
Log file attached.
TU 73 Kevin W4RKU
Mike,
Not being impatient, I just wanted to ensure the output I sent was ok and wanted. I know you are very busy.
73, Kevin, W4RKU
Yes...I have the problem report.
Mike
Mike,
Not being impatient, I just wanted to ensure the output I sent was ok and wanted. I know you are very busy.
73, Kevin, W4RKU
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
Ok here is where I stand. As you know this all started with me to get it to work on the RigPi. So I have been testing using direct as well as via hamlib with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I realized that I installed WSJT-X using the deb. So I built WSJT-X from the source. The result is better. If I disconnect the RigPi application and go to direct to the TS-2000 using WSJT-X it works! However if I set it to Hamlib (see attached) I get the following errors:
Hamlib error: IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
rig.c(1047):rig_open return(-6) IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
iofunc.c(361):port_close return(0) while opening connection to rig
Timestamp: 2022-07-27T21:59:17.002Z
JTDX does work with the Hamlib as the rig. One thing I noticed that caught my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld were (the copying didn't work as you said. Here is the listing:
pi@rigpi3:/usr/local/bin $ ls -l rigctl*
-rwxr-xr-x 1 root root 524228 Jul 27 12:11 rigctl
-rwxr-xr-x 1 root root 549008 Jul 27 12:11 rigctlcom
-rwxr-xr-x 1 root root 8149296 Jul 27 14:48 rigctlcom-wsjtx
-rwxr-xr-x 1 root root 544508 Jul 27 12:11 rigctld
-rwxr-xr-x 1 root root 15380432 Dec 29 2020 rigctld-jtdx
-rwxr-xr-x 1 root root 8365688 Jul 27 14:48 rigctld-wsjtx
-rwxr-xr-x 1 root root 15359572 Dec 29 2020 rigctl-jtdx
-rwxr-xr-x 1 root root 8341040 Jul 27 14:48 rigctl-wsjtx
So that is where it stands now.
73, Kevin, W4RKU
The size difference will be the diff between static and dynamic build.
Compiling Hamlib by default will give you dynamic which means you need to ensure you remove any system hamlib packages.
If you do
ldd rigctl
It will show you the libraries it references and you should see /usr/local/lib/libhamlib*
If you see /usr/lib/libhamlib* then you have a hamlib package installed that must be removed.
Mike W9DMB
On Wednesday, July 27, 2022 at 06:17:41 PM CDT, Kevin Utzy krutzy@users.sourceforge.net wrote:
Mike,
Ok here is where I stand. As you know this all started with me to get it to work on the RigPi. So I have been testing using direct as well as via hamlib with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I realized that I installed WSJT-X using the deb. So I built WSJT-X from the source. The result is better. If I disconnect the RigPi application and go to direct to the TS-2000 using WSJT-X it works! However if I set it to Hamlib (see attached) I get the following errors:
Hamlib error: IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
rig.c(1047):rig_open return(-6) IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
iofunc.c(361):port_close return(0) while opening connection to rig
Timestamp: 2022-07-27T21:59:17.002Z
JTDX does work with the Hamlib as the rig. One thing I noticed that caught my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld were (the copying didn't work as you said. Here is the listing:
pi@rigpi3:/usr/local/bin $ ls -l rigctl*
-rwxr-xr-x 1 root root 524228 Jul 27 12:11 rigctl
-rwxr-xr-x 1 root root 549008 Jul 27 12:11 rigctlcom
-rwxr-xr-x 1 root root 8149296 Jul 27 14:48 rigctlcom-wsjtx
-rwxr-xr-x 1 root root 544508 Jul 27 12:11 rigctld
-rwxr-xr-x 1 root root 15380432 Dec 29 2020 rigctld-jtdx
-rwxr-xr-x 1 root root 8365688 Jul 27 14:48 rigctld-wsjtx
-rwxr-xr-x 1 root root 15359572 Dec 29 2020 rigctl-jtdx
-rwxr-xr-x 1 root root 8341040 Jul 27 14:48 rigctl-wsjtx
So that is where it stands now.
73, Kevin, W4RKU
Attachments:
* wsjt-x error.jpg (46.1 kB; image/jpeg)
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Mike,
I know I uninstalled the hamlib that I had installed before your download by
issuing "sudo make uninstall"
The I made the new snapshot.
This is the output of the ldd command:
pi@rigpi3:~ $ ldd /usr/local/bin/rigctl
/usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6faf000)
(0xb6f3d000)
(0xb6602000)
(0xb63dd000)
I take it I did not do the uninstall correctly. If not the way I did it,
how should I clean everything up?
With the tar.gz I downloaded I did the
./configure
cmake
make
sudo make install
I don't mind redoing everything, but just let me know how to get it really
cleaned and I will rebuild them.
Thank you much,
Kevin
From: discussion@hamlib.p.re.sourceforge.net
discussion@hamlib.p.re.sourceforge.net On Behalf Of Michael Black
Sent: Wednesday, July 27, 2022 23:18
To: [hamlib:discussion] 25919@discussion.hamlib.p.re.sourceforge.net
Subject: [hamlib:discussion] Re: RigPi Split Mode TS-2000
The size difference will be the diff between static and dynamic build.
Compiling Hamlib by default will give you dynamic which means you need to
ensure you remove any system hamlib packages.
If you do
ldd rigctl
It will show you the libraries it references and you should see
/usr/local/lib/libhamlib*
If you see /usr/lib/libhamlib* then you have a hamlib package installed that
must be removed.
Mike W9DMB
On Wednesday, July 27, 2022 at 06:17:41 PM CDT, Kevin Utzy
krutzy@users.sourceforge.net krutzy@users.sourceforge.net wrote:
Mike,
Ok here is where I stand. As you know this all started with me to get it to
work on the RigPi. So I have been testing using direct as well as via hamlib
with the RigPi starting rigctld and setting hamlib as the Rig in WSJT-X.
I built and installed the snapshot you asked me too. Same problem. Then I
realized that I installed WSJT-X using the deb. So I built WSJT-X from the
source. The result is better. If I disconnect the RigPi application and go
to direct to the TS-2000 using WSJT-X it works! However if I set it to
Hamlib (see attached) I get the following errors:
Hamlib error: IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
rig.c(1047):rig_open return(-6) IO error
network.c(441):network_close return(0)
iofunc.c(361):port_close return(0)
iofunc.c(361):port_close return(0) while opening connection to rig
Timestamp: 2022-07-27T21:59:17.002Z
JTDX does work with the Hamlib as the rig. One thing I noticed that caught
my eye was the size of the WSJT-X and JTDX versions of rigctl and rigctld
were (the copying didn't work as you said. Here is the listing:
pi@rigpi3:/usr/local/bin $ ls -l rigctl*
-rwxr-xr-x 1 root root 524228 Jul 27 12:11 rigctl
-rwxr-xr-x 1 root root 549008 Jul 27 12:11 rigctlcom
-rwxr-xr-x 1 root root 8149296 Jul 27 14:48 rigctlcom-wsjtx
-rwxr-xr-x 1 root root 544508 Jul 27 12:11 rigctld
-rwxr-xr-x 1 root root 15380432 Dec 29 2020 rigctld-jtdx
-rwxr-xr-x 1 root root 8365688 Jul 27 14:48 rigctld-wsjtx
-rwxr-xr-x 1 root root 15359572 Dec 29 2020 rigctl-jtdx
-rwxr-xr-x 1 root root 8341040 Jul 27 14:48 rigctl-wsjtx
So that is where it stands now.
73, Kevin, W4RKU
Attachments:
RigPi Split Mode TS-2000
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
RigPi Split Mode TS-2000
https://sourceforge.net/p/hamlib/discussion/25919/thread/9a17ff0e50/?limit= 25#7933/ce2e
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/