Re: [wsjt-devel] Some minor issues.
On Sun, Oct 17, 2021 at 9:08 AM Marco Calistri via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Il 17/10/21 03:47, jarmo via wsjt-devel ha scritto: > > Wed, 29 Sep 2021 16:15:00 + (UTC) > Black Michael via wsjt-devel > > kirjoitti: > > Hi Mike > > Compiled latest git version 4.4 and no cahnge with TS-590SG. > We can run wsjtx (2.5.0) when radio set as TS-590SG, 9600 rest > as default. Audio goes out. > But again, if I set there /usr/local/bin/rigctld -m 2037 -r /dev/radio > -s 9600, wsjt setting radio set as Hamlib Net Rigctl, audio does not > go out, just tiny sound goes, but no matter how much turn output + > it stays kind of "muted" > > I was having the same issue using hamlib's flrig interface, however, I updated both hamlib and wsjtx to the latest release and have new behavior: 1. When in WSJT-X settings "Test CAT" works fine as well as "Test PTT". 2. When trying a QSO or "Tune", I get rapid relay clicking and WSJT-X loses connection to hamlib randomly after < 1 to a couple of seconds. Clicking retry always works until the next TX attempt. Changing to the FT-991 hamlib interface everything works as expected, but of course I lose my Flrig interface. Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 17/10/21 03:47, jarmo via wsjt-devel ha scritto: Wed, 29 Sep 2021 16:15:00 + (UTC) Black Michael via wsjt-devel kirjoitti: Hi Mike Compiled latest git version 4.4 and no cahnge with TS-590SG. We can run wsjtx (2.5.0) when radio set as TS-590SG, 9600 rest as default. Audio goes out. But again, if I set there /usr/local/bin/rigctld -m 2037 -r /dev/radio -s 9600, wsjt setting radio set as Hamlib Net Rigctl, audio does not go out, just tiny sound goes, but no matter how much turn output + it stays kind of "muted" Jarmo, OH1MRR Also...please the the git clone so you can get any patches I put in.The tar file only gets updated overnight. On Wednesday, September 29, 2021, 11:03:57 AM CDT, jarmo via wsjt-devel wrote: Wed, 29 Sep 2021 12:05:31 -0300 Marco Calistri via wsjt-devel kirjoitti: Il 29/09/21 11:07, Black Michael ha scritto: Can you please try the latest hamlib and see if it's fixed now? Unfortunately not working. Compiled hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. If try to use NetHamlib rictl, audio does not go into radio. Cat control works ok. But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works ok... Jarmo This exactly what happens with me using YAESU FT-100. The only way to go is by selecting Data/Pkt and not USB in WSJT-X. Once again I wan to to repeat that some months ago - supposedly with different Hamlib coding - I could use USB. --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Wed, 29 Sep 2021 16:15:00 + (UTC) Black Michael via wsjt-devel kirjoitti: Hi Mike Compiled latest git version 4.4 and no cahnge with TS-590SG. We can run wsjtx (2.5.0) when radio set as TS-590SG, 9600 rest as default. Audio goes out. But again, if I set there /usr/local/bin/rigctld -m 2037 -r /dev/radio -s 9600, wsjt setting radio set as Hamlib Net Rigctl, audio does not go out, just tiny sound goes, but no matter how much turn output + it stays kind of "muted" Jarmo, OH1MRR > Also...please the the git clone so you can get any patches I put > in.The tar file only gets updated overnight. > > > > On Wednesday, September 29, 2021, 11:03:57 AM CDT, jarmo via > wsjt-devel wrote: > Wed, 29 Sep 2021 12:05:31 -0300 > Marco Calistri via wsjt-devel > kirjoitti: > > > Il 29/09/21 11:07, Black Michael ha scritto: > > > Can you please try the latest hamlib and see if it's fixed now? > > Unfortunately not working. Compiled > hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. > If try to use NetHamlib rictl, audio does not go into radio. > Cat control works ok. > But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works > ok... > > Jarmo > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 01/10/21 04:48, Claude Frantz via wsjt-devel ha scritto: On 10/1/21 12:38 AM, Marco Calistri via wsjt-devel wrote: Hi Bill, Marco & all, Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. I have no experience with the FT-100, but with the FT-2000. There the menu setting "072dATa PKTDISP" (Packet mode frequency display offset) is the important one here. I have used the same value of 1000 as set on "073dATa PKT SFT" (Packet mode carrier point frequency). The factory default is different. Best wishes, Claude (DJ0OT) Hi Claude, What I want to do is testing for at least one hour to use DIG mode in FT8 and see how many QSO's I can make, then switch to USB and compare the results. In my case with YAESU FT-100, the MENU 38 PKT DISPLAY is the one I need to adjust to 0 (zero) in order to have the TX frequency as close as possible to the FT8 standard frequency available in WSJT-X bands selector. Cheers, --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Wed, 29 Sep 2021 16:15:00 + (UTC) Black Michael via wsjt-devel kirjoitti: > Also...please the the git clone so you can get any patches I put > in.The tar file only gets updated overnight. I tried this one too, no change. Strange thing is, that when TX, ptt fires up, so something is going into radio, because PTT is set as VOX. And when I monitor same freq, where I set friends system calling CQ, I can see him there, but signal is VERY low. We have distance abt 1 mile. If normal, he's coming to me +33, now -03. And this if Radio selected Hamlib Net Rigctl. If I select Kenwood TS-590SG, he's back in +33. So somehow, tone does dump down if used RIGCTLD... Have to admit, I'm far out now :) I tried to go back 2.4.0, but some libraries was too new, for that version. Huge job downgrade... Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 10/1/21 12:38 AM, Marco Calistri via wsjt-devel wrote: Hi Bill, Marco & all, Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. I have no experience with the FT-100, but with the FT-2000. There the menu setting "072dATa PKTDISP" (Packet mode frequency display offset) is the important one here. I have used the same value of 1000 as set on "073dATa PKT SFT" (Packet mode carrier point frequency). The factory default is different. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 30/09/21 19:20, Bill Somerville ha scritto: On 30/09/2021 16:35, Marco Calistri wrote: Il 30/09/21 10:58, Bill Somerville via wsjt-devel ha scritto: On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the */chkvfo/* feature, settings adjusted as suggested but again _*no AFSK going to radio rear data connector if I select mode USB in WSJT-X*_, in order to transmit an FT8 signal _*I *__*need to select DIG mode*_. Then, the only possible solution *IMHO* should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. Hey Bill! I've not doubts about what you say, but unluckily, due some reasons I'm not aware of, if I select Mode Data/Pkt in WSJT-X, it looks like nobody station being able to listen and consequently to answer to my calls. Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. --- *73 de Marco, PY1ZRJ (former IK5BCU)* Hi Marco, which DIG mode (AFSK MODE) have you set in your rig's menu? Have you set the PKT DISPLAY menu item to zero to remove any VFO dial frequency offset in PCt-U mode? 73 Bill G4WJS. Bill, I confess that I have not checked this parameter so far, sad to admit it but this demonstrate my little effort to document myself better about this specific configurations. Now I entered into YAESU FT-100 Menu and the parameters related to DIG mode are as following: 34 - AFSK Mode = PCt-U 35 - RTTY SHIFT = 170 (I guess this not important in this case) 36 - RTTY DISPLAY = nor 37 - PACKET RATE = 1200 38 -*PKT DISPLAY = 2125 (!!!)* 39 - PACKET TONE = 2125 Is that just MENU 38 to be set Bill? Thanks and regards. --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 30/09/2021 16:35, Marco Calistri wrote: Il 30/09/21 10:58, Bill Somerville via wsjt-devel ha scritto: On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the */chkvfo/* feature, settings adjusted as suggested but again _*no AFSK going to radio rear data connector if I select mode USB in WSJT-X*_, in order to transmit an FT8 signal _*I *__*need to select DIG mode*_. Then, the only possible solution *IMHO* should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. Hey Bill! I've not doubts about what you say, but unluckily, due some reasons I'm not aware of, if I select Mode Data/Pkt in WSJT-X, it looks like nobody station being able to listen and consequently to answer to my calls. Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. --- *73 de Marco, PY1ZRJ (former IK5BCU)* Hi Marco, which DIG mode (AFSK MODE) have you set in your rig's menu? Have you set the PKT DISPLAY menu item to zero to remove any VFO dial frequency offset in PCt-U mode? 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 30/09/21 12:42, Black Michael ha scritto: According to hamspots.net and pskreporter you are being seen. Mike W9MDB On Thursday, September 30, 2021, 10:39:29 AM CDT, Marco Calistri via wsjt-devel wrote: Il 30/09/21 10:58, Bill Somerville via wsjt-devel ha scritto: On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the */chkvfo/* feature, settings adjusted as suggested but again _*no AFSK going to radio rear data connector if I select mode USB in WSJT-X*_, in order to transmit an FT8 signal _*I *__*need to select DIG mode*_. Then, the only possible solution *IMHO* should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. Hey Bill! I've not doubts about what you say, but unluckily, due some reasons I'm not aware of, if I select Mode Data/Pkt in WSJT-X, it looks like nobody station being able to listen and consequently to answer to my calls. Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. --- *73 de Marco, PY1ZRJ (former IK5BCU)*** Hey Mike! Yes I'm also monitoring my FT8 status trough pskreporter.de and there appears that some station is able to decode my FT8 transmission, but so far, if I use DIG instead of SSB, I didn't received any replies. Anyway, I will stop for a while to send messages here now because I think I'm abusing of the list just for my specific problem. Many thanks to everybody which have provided some sort of feedback on this regard! --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
According to hamspots.net and pskreporter you are being seen. Mike W9MDB On Thursday, September 30, 2021, 10:39:29 AM CDT, Marco Calistri via wsjt-devel wrote: Il 30/09/21 10:58, Bill Somerville via wsjt-devel ha scritto: On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the chkvfo feature, settings adjusted as suggested but again no AFSK going to radio rear data connector if I select mode USB in WSJT-X, in order to transmit an FT8 signal I need to select DIG mode. Then, the only possible solution IMHO should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. Hey Bill! I've not doubts about what you say, but unluckily, due some reasons I'm not aware of, if I select Mode Data/Pkt in WSJT-X, it looks like nobody station being able to listen and consequently to answer to my calls. Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 30/09/21 10:58, Bill Somerville via wsjt-devel ha scritto: On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the */chkvfo/* feature, settings adjusted as suggested but again _*no AFSK going to radio rear data connector if I select mode USB in WSJT-X*_, in order to transmit an FT8 signal _*I *__*need to select DIG mode*_. Then, the only possible solution *IMHO* should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. Hey Bill! I've not doubts about what you say, but unluckily, due some reasons I'm not aware of, if I select Mode Data/Pkt in WSJT-X, it looks like nobody station being able to listen and consequently to answer to my calls. Probably when I set Data/Pkt my radio transmit on a little shifted frequency out of the center of the standard transmission FT8 frequency and this unallow my signal to be heard. --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 30/09/2021 14:36, Marco Calistri via wsjt-devel wrote: CQRLOG now has been compiled with the */chkvfo/* feature, settings adjusted as suggested but again _*no AFSK going to radio rear data connector if I select mode USB in WSJT-X*_, in order to transmit an FT8 signal _*I *__*need to select DIG mode*_. Then, the only possible solution *IMHO* should be that Hamlib being modified accordingly in order to permits AFSK being usable for rear data connector in SSB too and not just in DIG mode. Marco, DIG mode is the correct rig mode setting for AFSK digimodes when using the FT-100. There is no facility to select the Tx audio source other than the rig mode settings with the FT-100. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Thu, 30 Sep 2021 09:25:41 -0300 Marco Calistri via wsjt-devel kirjoitti: > Il 30/09/21 06:20, Reino Talarmo ha scritto: > > > > 2) *_AFSK is being regularly produced by WSJT-X through the > > computer sound card_*, then I guess that there is a sort of > > "*/software muting/*" of this signal which is blocked in some way > > to feed the rear data connector of my YAESU FT-100 which in turn > > doesn't transmit any RF. May be if I would attach the AFSK output > > directly to the radio mic plug, then the RF transmission would be > > possible. > > > > Hi Marco, > > > > This a wild guess as I have no access to YAESU FT-100, but in some > > rigs you need to select Mode Data/Pkt not USB in order to get audio > > via the rear data connector. > > > > 73, Reino OH3mA > > > > Yeah Jarmo!!! > > You are right, in fact yesterday I was playing around the modes and I > verified that if I select digital and set accordingly my FT-100 menu > to use "PCT_USB", then my environment works: AFSK reach the rear data > port and my FT8 signal is being transmitted. > > However I guess DIG mode is not ideal for my setup because it looks > like nobody is answering to my CQ's (tested some minutes on 40 meters > band). > > I will try again today the DIG mode on the higher frequencies, where > is more easy to get a station reply. > > Best regards > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** Hi Now, again, question is about version change into 2.5.0. These Kenwoods, ts590, ts890 have been working like charm. And my TS890 works OK with 2.5.0. Audio (afsk) is put into radio USB-A --- USB-B cable, no interfaces between computer/radio. Again, if chosen Hamlib Net Rigctl, no TX audio out, PTT fires radio TX on. RX works perfect. If chosen KENWOOD TS590SG as RADIO both TX and RX works OK. This is the problem, I want to use HAMLIB NET RIGCTL, because want to connect CQRLOG also. AN AGAIN, THIS HAVE BEEN working before.. Only thing, what also made me thinking, if SELINUX does not let TX-audio out. Anyway, something dumps audio.. Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 30/09/21 06:20, Reino Talarmo ha scritto: 2) *_AFSK is being regularly produced by WSJT-X through the computer sound card_*, then I guess that there is a sort of "*/software muting/*" of this signal which is blocked in some way to feed the rear data connector of my YAESU FT-100 which in turn doesn't transmit any RF. May be if I would attach the AFSK output directly to the radio mic plug, then the RF transmission would be possible. Hi Marco, This a wild guess as I have no access to YAESU FT-100, but in some rigs you need to select Mode Data/Pkt not USB in order to get audio via the rear data connector. 73, Reino OH3mA Yeah Jarmo!!! You are right, in fact yesterday I was playing around the modes and I verified that if I select digital and set accordingly my FT-100 menu to use "PCT_USB", then my environment works: AFSK reach the rear data port and my FT8 signal is being transmitted. However I guess DIG mode is not ideal for my setup because it looks like nobody is answering to my CQ's (tested some minutes on 40 meters band). I will try again today the DIG mode on the higher frequencies, where is more easy to get a station reply. Best regards --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
2) AFSK is being regularly produced by WSJT-X through the computer sound card, then I guess that there is a sort of "software muting" of this signal which is blocked in some way to feed the rear data connector of my YAESU FT-100 which in turn doesn't transmit any RF. May be if I would attach the AFSK output directly to the radio mic plug, then the RF transmission would be possible. Hi Marco, This a wild guess as I have no access to YAESU FT-100, but in some rigs you need to select Mode Data/Pkt not USB in order to get audio via the rear data connector. 73, Reino OH3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Thu, 30 Sep 2021 08:06:34 +0200 Claude Frantz via wsjt-devel kirjoitti: > On 9/30/21 5:01 AM, jarmo via wsjt-devel wrote: > > Hi Jarmo & all, > These rigs may have different USB interfaces and different sound > chips, so that they appear as different items in pavucontrol. Yes, I know that and sure have selected right in pavucontrol.. Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 9/30/21 5:01 AM, jarmo via wsjt-devel wrote: Hi Jarmo & all, I think, it has nothing to do with souncard. Both radios are connected directly via USB so wsjtx uses audio codec as input and output. These rigs may have different USB interfaces and different sound chips, so that they appear as different items in pavucontrol. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 9/30/21 6:19 AM, Marco Calistri via wsjt-devel wrote: Hi Marco & all, 2) _*AFSK is being regularly produced by WSJT-X through the computer sound card*_, then I guess that there is a sort of "*/software muting/*" of this signal which is blocked in some way to feed the rear data connector of my YAESU FT-100 which in turn doesn't transmit any RF. May be if I would attach the AFSK output directly to the radio mic plug, then the RF transmission would be possible. Please verify the settings in "pavucontrol" which is part of pulseaudio. Verify that you have selected the right source, sink and that no one of them is muted. Verify that pavucontrol shows a signal on the selected items. In WSJT-X, verify that you have selected the appropriate "sound card". If you use an USB connected "sound card", you will see a least 2 cards, because there is probably an internal soundcard in the computer. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Wed, 29 Sep 2021 18:23:28 +0200 Claude Frantz via wsjt-devel kirjoitti: > > Please debug the audio matter. My suggestion, at first: > > aplay -l > aplay -L > arecord -l > arecord -L > pactl list I think, it has nothing to do with souncard. Both radios are connected directly via USB so wsjtx uses audio codec as input and output. All have been working with Hamlib Net Rigctl earlier versions of wsjtx. Now this 2.5.0 somehow rejects. As said, if I choose from wsjtx prferences Radio TS-590SG instead of Hamlib Net Rigctl, I can get TX working like charm. RX works with both. And ONLY with TS-590SG TX does not work, when RADIO is set as Hamlib Net Rigctl. With my TS-890S, RADIO set as Hamlib Net Rigctl RX/TX works as have done all the time. OS in both cases is Fedora 34 with XFCE4 desktop, hardware is a bit different, but, as have been working earlier, now vers 2.5.0 of wsjtx make TX impossible.. Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 29/09/21 12:58, jarmo ha scritto: Wed, 29 Sep 2021 12:05:31 -0300 Marco Calistri via wsjt-devel kirjoitti: Il 29/09/21 11:07, Black Michael ha scritto: Can you please try the latest hamlib and see if it's fixed now? Unfortunately not working. Compiled hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. If try to use NetHamlib rictl, audio does not go into radio. Cat control works ok. But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works ok... Jarmo Same story here Jarmo: *NET rigctld is not usable* because no AFSK reach the radio also by following the Saku suggestion, for me NET rigctld is not a valid option. For @Mike: I'm using back data connector of YAESU FT-100 and the audio is coming directly from the jacks of the laptop sound card, not USB. --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
CAT can be related to audio -- front/back connectors matter for example. Mike W9MDB On Wednesday, September 29, 2021, 11:27:09 AM CDT, Claude Frantz via wsjt-devel wrote: On 9/29/21 5:58 PM, jarmo via wsjt-devel wrote: Hi Marco, Jarmo and all, > Unfortunately not working. Compiled > hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. > If try to use NetHamlib rictl, audio does not go into radio. CAT is not related to Audio. > Cat control works ok. This is fine. hamlib does the job. > But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works > ok... Please debug the audio matter. My suggestion, at first: aplay -l aplay -L arecord -l arecord -L pactl list Please examine the output. As mentioned previously, if the "sound card" is connected via USB, verify that gpsd (or another program) doesn't grasp the "sound card". The output of dmesg can help. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
On 9/29/21 5:58 PM, jarmo via wsjt-devel wrote: Hi Marco, Jarmo and all, Unfortunately not working. Compiled hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. If try to use NetHamlib rictl, audio does not go into radio. CAT is not related to Audio. Cat control works ok. This is fine. hamlib does the job. But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works ok... Please debug the audio matter. My suggestion, at first: aplay -l aplay -L arecord -l arecord -L pactl list Please examine the output. As mentioned previously, if the "sound card" is connected via USB, verify that gpsd (or another program) doesn't grasp the "sound card". The output of dmesg can help. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Also...please the the git clone so you can get any patches I put in.The tar file only gets updated overnight. On Wednesday, September 29, 2021, 11:03:57 AM CDT, jarmo via wsjt-devel wrote: Wed, 29 Sep 2021 12:05:31 -0300 Marco Calistri via wsjt-devel kirjoitti: > Il 29/09/21 11:07, Black Michael ha scritto: > > Can you please try the latest hamlib and see if it's fixed now? Unfortunately not working. Compiled hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. If try to use NetHamlib rictl, audio does not go into radio. Cat control works ok. But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works ok... Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Marco Calistri kirjoitti 29.9.2021 klo 16.49: Hi dear Saku I was hopefully waiting a feedback from your side as being one member of the CQRLOG developers team as well as a WSJT-X user. However, sorry to say this, but your reply doesn't sounds pretty clear to me... Despite this I will try to follow your suggestion about starting rigctld by a separate session. I demonstrated though my answer to Mike that CQRLOG has not any influence on the anomalies I faced (minor issue 1: no AFSK using NET rigctl and minor issue 2: radio split issue). I could keep using my current settings on both CQRLOG and WSJT-X since I feel that Hamlib will not works anymore as it was before (using NET rigctl) but at least I would like to get rid of the need to manually push VFO A=B button on my FT-100 every time I switch the band from WSJT-X. Thanks and best regards! HI Marco! Cqrlog does not have influence to A=B needs, but it is related to this. To get rid of pushing A=B after band change with wsjtx rigctld that access rig needs starting parameter "--vfo" if you start rigctld outside of wsjtx and use "Hamlib Net rigctld" as rig in wsjtx configuration. That helped at least me with Icom IC7300. As reminder: You can not start wsjtx with your rig model and serial port as rig in configuration(F2/radio) if you also start cqrlog with your rig model and serial port in preferences/TRXControl. This will cause two programs trying to share same serial port to access to your rig at same time and that will not work. You have to start rigctld with rig parameters separately and then make your programs call that rigctld with "Hamlib net rigctld" as rig in programs. ( https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctld_for_all_programs.pdf ) But when "--vfo" is used to get wsjtx happy problem arise with cqrlog that does not like "--vfo" parameter at rigctld start at all. And the reason is, as said, rigctld one letter commands need additional parameter about vfo (VFOA, VFOB, currVFO etc...) for almost all commands. This makes it not being backward compatible any more with older rigctld commands. So making wsjtx happy with "--vfo" makes cqrlog unhappy because it uses legacy one letter commands for accessing rigctld that then do not work any more. If you try latest hamlib 29 10:46:53 2021 + SHA=a2b3a8 you could also try my fix for cqrlog at https://github.com/OH1KH/cqrlog/tree/hamlib_vfo It has a new checkbox at preferences/TRXcontrol called "Use \chkvfo". It is default checked and then tries to find out has user started rigctld with or without "--vfo" parameter. With that information it changes command format for accessing rigctld from cqrlog. When unchecked it acts like previous cqrlogs. I.E: disables this fix. It seems to work with IC7300 when "--vfo" parameter is used and both cqrlog and wsjtx become happy. -- Saku OH1KH ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Wed, 29 Sep 2021 12:05:31 -0300 Marco Calistri via wsjt-devel kirjoitti: > Il 29/09/21 11:07, Black Michael ha scritto: > > Can you please try the latest hamlib and see if it's fixed now? Unfortunately not working. Compiled hamlib-4.4~git-dd1376be-20210929.tar.gz and same behaviour. If try to use NetHamlib rictl, audio does not go into radio. Cat control works ok. But if chosen Kenwood ts-590SG in WSJTX radio preferences, audio works ok... Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 29/09/21 11:07, Black Michael ha scritto: Can you please try the latest hamlib and see if it's fixed now? Mike W9MDB Sure Mike! I'll repeat both the tests: 1 - Rigctld and AFSK issue 2 - FT-100 and SPLIT issue I'll let you know. Thanks. --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Can you please try the latest hamlib and see if it's fixed now? Mike W9MDB On Tuesday, September 28, 2021, 04:51:21 PM CDT, Marco Calistri wrote: Il 28/09/21 18:08, Black Michael ha scritto: > #1 Does the rig behave when NOT running cqrlog? > #2 Please run rigctld like this, duplicate the problem, and send me > the log.txt file > rigctld -m 1021 --vfo -v -Z >log.txt 2>&1 > > Mike W9MDB > > > Hi Mike, Yes, CQRLOG is not affecting at all in these behaviors. In attachment the two logs: 1 - *rigctld.usb.log.txt *produced when selecting "NET rigctl" into WSJT-X: result is that no AFSK is generated and FT-100 just switch the PTT on/off. 2 - *FT-100ctld.usb.log.txt* produced when selecting FT-100 as Rig into WSJT-X. In this case I tried to change band from 10 to 17 meters and going back to 10 meters and the result is that *_only_* the receiving VFO changes correctly though WSJT-X commands, while the transmitting VFO holds on 10 meters initial frequency. So yes, both issues are still present independently of CQRLOG and as I told, they are news issues since the newer software versions (hamlib/wsjt-x) has been released. Regards, -- *73 de Marco, PY1ZRJ (former IK5BCU)* ** ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Il 29/09/21 03:34, Saku via wsjt-devel ha scritto: Hi Marco! Sounds familiar, hi... As you use #2 Net Hamlib rigctld as cqrlog's rig you have to start rigctld elsewhere with rig parameters. I guess that happens via bash script. There you should use "--vfo" to get wsjtx work with split=rig. Unfortunately that causes problems with cqrlog. It does not work if parameter "--vfo" is used as using it changes the format of rigctld short (one letter) commands. They are no more backwards compatible because almost every command needs vfo stated as first parameter when start parameter "--vfo" is used. There is a workaround to start rigctld with rig parameters and "--vfo" via bash script. That makes wsjtx happy with rig #2 Hamlib Net rigctld configured there, but then you need to start another rigctld without "--vfo" for cqrlog and that 2nd rigctld accesses the 1st rigctld that then accesses your rig. For doing this: With bash script start rigctld with your normal rig parameters and "--vfo" wsjtx: rig #2 Net Hamlib rigctld selected, server localhost:4532 cqrlog/trxcontrol: "Run rigctld when program starts" checked rig #2 Hamlib Net rigctld selected localhost Port 14532 !!! Note the port number !!! Extra command line arguments I.E. do not write anything there Other settings do not affect with rig #2 no need to set them Instead of "localhost" I prefer using 127.0.0.1 because sometimes IPv6, if enabled, causes troubles when "localhost" is used directing connects to IPv6 that may not been supported by all programs. I'm working with fix for cqrlog, it is under testing and Mike has done good work at Hamlib side to get this issue solved. Specially Icom rigs that can not report vfo with "v" command have caused extra work. As soon as I have tested it properly I will make pull request to cqrlog's GitHub Another way to resolve this is leave the "--vfo" parameter away from bash started rigctld and then set wsjtx split=fake it. Then it is happy without "--vfo" and also cqrlog works as always before. For the audio issue I can not give help. All I know that pulse audio (pipewire) does not work properly. It has been so always, at least with Fedoras. Alsa is the only one that works. And when you change band and press Tune there as the first thing to do the first period transmit after that is always without audio. So do not use Tune button for tuning the new band first, just start transmit immediately and let the first transmit period activate autotuner (just wondering what the Tune button is for...) -- Saku OH1KH Marco Calistri via wsjt-devel kirjoitti 29.9.2021 klo 0.51: Il 28/09/21 18:08, Black Michael ha scritto: #1 Does the rig behave when NOT running cqrlog? #2 Please run rigctld like this, duplicate the problem, and send me the log.txt file rigctld -m 1021 --vfo -v -Z >log.txt 2>&1 Mike W9MDB Hi Mike, Yes, CQRLOG is not affecting at all in these behaviors. In attachment the two logs: 1 - *rigctld.usb.log.txt *produced when selecting "NET rigctl" into WSJT-X: result is that no AFSK is generated and FT-100 just switch the PTT on/off. 2 - *FT-100ctld.usb.log.txt* produced when selecting FT-100 as Rig into WSJT-X. In this case I tried to change band from 10 to 17 meters and going back to 10 meters and the result is that *_only_* the receiving VFO changes correctly though WSJT-X commands, while the transmitting VFO holds on 10 meters initial frequency. So yes, both issues are still present independently of CQRLOG and as I told, they are news issues since the newer software versions (hamlib/wsjt-x) has been released. Regards, -- *73 de Marco, PY1ZRJ (former IK5BCU)* ** Hi dear Saku I was hopefully waiting a feedback from your side as being one member of the CQRLOG developers team as well as a WSJT-X user. However, sorry to say this, but your reply doesn't sounds pretty clear to me... Despite this I will try to follow your suggestion about starting rigctld by a separate session. I demonstrated though my answer to Mike that CQRLOG has not any influence on the anomalies I faced (minor issue 1: no AFSK using NET rigctl and minor issue 2: radio split issue). I could keep using my current settings on both CQRLOG and WSJT-X since I feel that Hamlib will not works anymore as it was before (using NET rigctl) but at least I would like to get rid of the need to manually push VFO A=B button on my FT-100 every time I switch the band from WSJT-X. Thanks and best regards! --- *73 de Marco, PY1ZRJ (former IK5BCU)* **___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Tue, 28 Sep 2021 21:08:48 + (UTC) Black Michael via wsjt-devel kirjoitti: > #1 Does the rig behave when NOT running cqrlog?#2 Please run rigctld > like this, duplicate the problem, and send me the log.txt filerigctld > -m 1021 --vfo -v -Z >log.txt 2>&1 > > Mike So, problem is, that can't get audio to radio with rigctld from wsjtx. Upgraded to 2.5.0, strance things seen. With my TS-890s HamlibNet rigctld works so far, with my Friends TS-590SG does not. Have to choose in wsjtx settings Kenwood ts590sg, then it works. With CQRLOG, I have to choose also Rdio Kenwood TS-590SG and from settings choose "Take freq from WSJTX. This works... Shortly, start CQRLOG, choose Remote for WSJTX, it starts wsjtx and both programs now getting right freq and audio goes out from radio. Wsjtx version 2.5.0 Richards experimental Fedora 34 rpm. Hamlib version 4,4 daily snapshot, does not matter, if I change to 4.2 or 4.3 version, all work ok. So, with TS-890s works HamliNet rigctld, with TS-590SG does not. Jarmo, oh1mrr ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
Hi Marco! Sounds familiar, hi... As you use #2 Net Hamlib rigctld as cqrlog's rig you have to start rigctld elsewhere with rig parameters. I guess that happens via bash script. There you should use "--vfo" to get wsjtx work with split=rig. Unfortunately that causes problems with cqrlog. It does not work if parameter "--vfo" is used as using it changes the format of rigctld short (one letter) commands. They are no more backwards compatible because almost every command needs vfo stated as first parameter when start parameter "--vfo" is used. There is a workaround to start rigctld with rig parameters and "--vfo" via bash script. That makes wsjtx happy with rig #2 Hamlib Net rigctld configured there, but then you need to start another rigctld without "--vfo" for cqrlog and that 2nd rigctld accesses the 1st rigctld that then accesses your rig. For doing this: With bash script start rigctld with your normal rig parameters and "--vfo" wsjtx: rig #2 Net Hamlib rigctld selected, server localhost:4532 cqrlog/trxcontrol: "Run rigctld when program starts" checked rig #2 Hamlib Net rigctld selected localhost Port 14532 !!! Note the port number !!! Extra command line arguments I.E. do not write anything there Other settings do not affect with rig #2 no need to set them Instead of "localhost" I prefer using 127.0.0.1 because sometimes IPv6, if enabled, causes troubles when "localhost" is used directing connects to IPv6 that may not been supported by all programs. I'm working with fix for cqrlog, it is under testing and Mike has done good work at Hamlib side to get this issue solved. Specially Icom rigs that can not report vfo with "v" command have caused extra work. As soon as I have tested it properly I will make pull request to cqrlog's GitHub Another way to resolve this is leave the "--vfo" parameter away from bash started rigctld and then set wsjtx split=fake it. Then it is happy without "--vfo" and also cqrlog works as always before. For the audio issue I can not give help. All I know that pulse audio (pipewire) does not work properly. It has been so always, at least with Fedoras. Alsa is the only one that works. And when you change band and press Tune there as the first thing to do the first period transmit after that is always without audio. So do not use Tune button for tuning the new band first, just start transmit immediately and let the first transmit period activate autotuner (just wondering what the Tune button is for...) -- Saku OH1KH Marco Calistri via wsjt-devel kirjoitti 29.9.2021 klo 0.51: Il 28/09/21 18:08, Black Michael ha scritto: #1 Does the rig behave when NOT running cqrlog? #2 Please run rigctld like this, duplicate the problem, and send me the log.txt file rigctld -m 1021 --vfo -v -Z >log.txt 2>&1 Mike W9MDB Hi Mike, Yes, CQRLOG is not affecting at all in these behaviors. In attachment the two logs: 1 - *rigctld.usb.log.txt *produced when selecting "NET rigctl" into WSJT-X: result is that no AFSK is generated and FT-100 just switch the PTT on/off. 2 - *FT-100ctld.usb.log.txt* produced when selecting FT-100 as Rig into WSJT-X. In this case I tried to change band from 10 to 17 meters and going back to 10 meters and the result is that *_only_* the receiving VFO changes correctly though WSJT-X commands, while the transmitting VFO holds on 10 meters initial frequency. So yes, both issues are still present independently of CQRLOG and as I told, they are news issues since the newer software versions (hamlib/wsjt-x) has been released. Regards, -- *73 de Marco, PY1ZRJ (former IK5BCU)* ** ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Some minor issues.
#1 Does the rig behave when NOT running cqrlog?#2 Please run rigctld like this, duplicate the problem, and send me the log.txt filerigctld -m 1021 --vfo -v -Z >log.txt 2>&1 Mike W9MDB On Tuesday, September 28, 2021, 03:17:37 PM CDT, Marco Calistri via wsjt-devel wrote: Hello, I'm trying to summarize some "minor issues" which are not blocking problems at all, but they are a bit annoying, especially because I haven't been able to sort out them so far and I'm still facing it on my current setup which includes: a) WSJT-X 2.5.0 GA b) Linux Tumbleweed updated daily c) CQRLOG latest GIT which starts the WSJT-X application d) YAESU FT-100 e) CAT USB cable + Audio USB cable plugged to the rear panel radio pigtail and data connector. MINOR ISSUE 1: With the majority of the older WSJT-X versions, I used to set the hamlib NET rigctl into the WSJT-X and this has worked flawlessly for a lot of time and at least until something has been changed into Hamlib, WSJT-X or both. From that moment on, if I set in this way the WSJT-X, by selecting NET rigctl, then no audio signal is produced and my radio just switch the PTT, without modulating the SSB carrier. In order I can operate I need to switch from NET rigctl to YAESU FT-100 in the settings>option>radio>rig. MINOR ISSUE 2: This is a lower severity issue but it happens that I need to press my YAESU FT-100 A=B vfo button every time I switch to other band with WSJT-X otherwise radio receive on the right selected frequency but keeps transmitting on the previous one. Additional details: Into WSJT-X I select mode: USB, Split: RIG. Into CQRLOG settings I'm using the following parameters to manage WSJT-X: Path to rigctld: /usr/local/bin/rigctld (note: this is coming from my Hamlib compiled from latest GIT repository). RIG model: 2 Hamlib NET rigctl Extra command line arguments: -m 1021 --vfo That's all. If someone, using an environment similar to mine, is able to use NET rigctl and or able to switch the radio bands by WSJT-X, without pressing the A=B VFO, please reply to this message. Many thanks! --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Some minor issues.
Hello, I'm trying to summarize some "minor issues" which are not blocking problems at all, but they are a bit annoying, especially because I haven't been able to sort out them so far and I'm still facing it on my current setup which includes: a) WSJT-X 2.5.0 GA b) Linux Tumbleweed updated daily c) CQRLOG latest GIT which starts the WSJT-X application d) YAESU FT-100 e) CAT USB cable + Audio USB cable plugged to the rear panel radio pigtail and data connector. MINOR ISSUE 1: With the majority of the older WSJT-X versions, I used to set the hamlib NET rigctl into the WSJT-X and this has worked flawlessly for a lot of time and at least until something has been changed into Hamlib, WSJT-X or both. From that moment on, if I set in this way the WSJT-X, by selecting NET rigctl, then no audio signal is produced and my radio just switch the PTT, without modulating the SSB carrier. In order I can operate I need to switch from NET rigctl to YAESU FT-100 in the settings>option>radio>rig. MINOR ISSUE 2: This is a lower severity issue but it happens that I need to press my YAESU FT-100 A=B vfo button every time I switch to other band with WSJT-X otherwise radio receive on the right selected frequency but keeps transmitting on the previous one. Additional details: Into WSJT-X I select mode: USB, Split: RIG. Into CQRLOG settings I'm using the following parameters to manage WSJT-X: Path to rigctld: /usr/local/bin/rigctld (note: this is coming from my Hamlib compiled from latest GIT repository). RIG model: 2 Hamlib NET rigctl Extra command line arguments: -m 1021 --vfo That's all. If someone, using an environment similar to mine, is able to use NET rigctl and or able to switch the radio bands by WSJT-X, without pressing the A=B VFO, please reply to this message. Many thanks! --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
