Re: [wsjt-devel] Connecting the Yaesu FTdx10
OK on that link, however with the CP2105 comports it is best to wsjtx select the standard comport instead of CAT for PTT, and use RTS as KI5GFU has RPTT set. RPORT gain is better at 7 to 10 rather than 25, as this allows better wsjtx 'TX pwr' linear control, where small adjustments result in audio levels results when setting alc meter minimum. Higher (default) RPORT Gain results in a compressed audio zone causing TX gain adj steps to have no effect over a certain range and compromised signal quality. 73 vk4tux On 24/6/22 08:12, Black Michael via wsjt-devel wrote: From my notes helping somebody else. FTDX-10 Data/Pkt mode bandwidth not working..had to use USB mode Data Out Level=0 () Some more info https://ki5gfu.com/2021/10/14/ftdx-10-setting-up-wsjt-x-configuration-for-digital-eg-ft8/ Mike W9MDB On Thursday, June 23, 2022 at 05:02:21 PM CDT, BRIAN JONES via wsjt-devel wrote: Got the Yaesu FTdx10 a couple of weeks ago and and trying to get on FT8 everything said I needed a laptop or PC with windows 10/11. So last Monday I went out & caught one with win11 home installed, while I was in the shop they got it setup for me with all the updates etc. sorted. jobs a good one so I thought! Having used WJST before with a Icom bit of junk the 7300, very similar settings to the FTdx10. As having set all parameters up to Yaesu and a lot of the geeks say the same including, downloading virtual ports, firmware both off Yaesu & BktTimesync; Then loaded WSJT-X . Now on settings got radio setting done clicks box turns green 1st part sorted the pressing next button radio goes into TX clicks ok, box closes and all I keep getting is a box with red circle and X in red ring with message (ERROR IN SOUND INPUT) but can you tell me where the sound input is coming from my Radio or my Laptop, then how to stop this error and get back on the air with FT8 & FT4? If anyone has a PDF with all settings for windows 11 so all I would need to do is swop over com port numbers. Up to now I have wasted close to 35 hours trying to get up & running and up to now no one knows what or where this problem is! Did send an email to Joe Taylor K1JT even though he sent me to Wiki to find a cure! I had Icoms NAIL the 7300 ( had four for just one band in the UK 70Mhz ) totally deaf as a post. But Icom UK recon they can hear signals off a DUMMY LOAD dummies. my email address is below if anyone has a clue as I don't Thanks. 2e0...@gmail.com Regards Best 73 Brian De M6OXO ___ 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Connecting the Yaesu FTdx10
From my notes helping somebody else. FTDX-10 Data/Pkt mode bandwidth not working..had to use USB mode Data Out Level=0 () Some more info https://ki5gfu.com/2021/10/14/ftdx-10-setting-up-wsjt-x-configuration-for-digital-eg-ft8/ Mike W9MDB On Thursday, June 23, 2022 at 05:02:21 PM CDT, BRIAN JONES via wsjt-devel wrote: Got the Yaesu FTdx10 a couple of weeks ago and and trying to > get on FT8 everything said I needed a laptop or PC with windows 10/11. > So last Monday I went out & caught one with win11 home installed, > while I was in the shop they got it setup for me with all the updates > etc. sorted. jobs a good one so I thought! > Having used WJST before with a Icom bit of junk the 7300, very similar > settings to the FTdx10. As having set all parameters up to Yaesu and a > lot of the geeks say the same including, downloading virtual ports, > firmware both off Yaesu & BktTimesync; Then loaded WSJT-X . Now on > settings got radio setting done clicks box turns green 1st part sorted > the pressing next button radio goes into TX clicks ok, box closes and > all I keep getting is a box with red circle and X in red ring with > message (ERROR IN SOUND INPUT) but can you tell me where the sound input > is coming from my Radio or my Laptop, then how to stop this error and > get back on the air with FT8 & FT4? If anyone has a PDF with all settings for windows 11 so all I would need to do is swop over com port numbers. Up to now I have wasted close to 35 hours trying to get up & running and up to now no one knows what or where this problem is! Did send an email to Joe Taylor K1JT even though he sent me to Wiki to find a cure! I had Icoms NAIL the 7300 ( had four for just one band in the UK 70Mhz ) totally deaf as a post. But Icom UK recon they can hear signals off a DUMMY LOAD dummies. my email address is below if anyone has a clue as I don't Thanks. 2e0...@gmail.com > Regards > Best 73 > Brian De M6OXO ___ 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] Connecting the Yaesu FTdx10
Got the Yaesu FTdx10 a couple of weeks ago and and trying to > get on FT8 everything said I needed a laptop or PC with windows 10/11. > So last Monday I went out & caught one with win11 home installed, > while I was in the shop they got it setup for me with all the updates > etc. sorted. jobs a good one so I thought! > Having used WJST before with a Icom bit of junk the 7300, very similar > settings to the FTdx10. As having set all parameters up to Yaesu and a > lot of the geeks say the same including, downloading virtual ports, > firmware both off Yaesu & BktTimesync; Then loaded WSJT-X . Now on > settings got radio setting done clicks box turns green 1st part sorted > the pressing next button radio goes into TX clicks ok, box closes and > all I keep getting is a box with red circle and X in red ring with > message (ERROR IN SOUND INPUT) but can you tell me where the sound input > is coming from my Radio or my Laptop, then how to stop this error and > get back on the air with FT8 & FT4? If anyone has a PDF with all settings for windows 11 so all I would need to do is swop over com port numbers. Up to now I have wasted close to 35 hours trying to get up & running and up to now no one knows what or where this problem is! Did send an email to Joe Taylor K1JT even though he sent me to Wiki to find a cure! I had Icoms NAIL the 7300 ( had four for just one band in the UK 70Mhz ) totally deaf as a post. But Icom UK recon they can hear signals off a DUMMY LOAD dummies. my email address is below if anyone has a clue as I don't Thanks. 2e0...@gmail.com > Regards > Best 73 > Brian De M6OXO ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Error
It's happened on both my PC's as well Mike, one is running W10 and the other W11. 73 Tony, ZL3HAM On 24/06/2022 4:10 am, mpcorey--- via wsjt-devel wrote: Good afternoon, I am using the 2.6.0-rc1 release, and generally like the new features and have encountered no problems. However, today while calling CQ on 6 meters FT8, the program abruptly shut down. There was no indication in the task bar that it was still running. I tried to restart it and received these two error messages (see attached). I went into the task manager and was able to locate a file called JT9 that was running, once I ended that process I was able to restart the program. I am running a Windows 11 machine. Thanks, Mike, KI1U ___ 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] Hamlib rigcontrol and PTT
Hamlib PTT issue seems to be a regression in Hamlib. I was running Hamlib built from github master. When I built hamlib from the 4.4 release instead of master, PTT works fine over hamlib network connection. It was my mistake to oversee that github master was not the latest released version. Thank you all for your help and time, sorry for my oversight. Best regards Hrafnkell TF3HR On Thu, Jun 23, 2022 at 3:10 PM Hrafnkell Eiriksson wrote: > When pressing Test CAT a connection is opened from WSJT-X to rigctld and > closed very quickly as WSJT-X displays the error message in my original > email > This is the part of the log after I press Test CAT. I'll send you the log > directly as I do not think the mailing list allows them. > > 2022-06-23T15:05:21.684637-: Connection opened from > 192.168.1.173:65129 > 2022-06-23T15:05:21.685519-: mutex_rigctld: client lock engaged > 2022-06-23T15:05:21.685778-: mutex_rigctld: client lock disengaged > 2022-06-23T15:05:21.685895-: mutex_rigctld: client lock engaged > 2022-06-23T15:05:21.686008-: mutex_rigctld: client lock disengaged > 2022-06-23T15:05:21.686120-: handle_socket: doing rigctl_parse > vfo_mode=0, secure=0 > 2022-06-23T15:05:21.686235-: rigctl_parse: called, interactive=1 > 2022-06-23T15:05:23.686621-: scanfc: ret=-1 > 2022-06-23T15:05:23.686809-: rigctl_parse: nothing to scan#1? > retcode=-1, last_cmd=^@ > 2022-06-23T15:05:23.686924-: handle_socket: rigctl_parse retcode=2 > 2022-06-23T15:05:23.687046-: Connection closed from > 192.168.1.173:65129 > > Error in WSJT-X > 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 > > Tnx > Hrafnkell TF3HR > > On Thu, Jun 23, 2022 at 2:20 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> All 5 >> -v >> >> >> >> >> On Thursday, June 23, 2022 at 09:18:14 AM CDT, Hrafnkell Eiriksson via >> wsjt-devel wrote: >> >> >> I'll get you that log later today. What verbose level do you need on >> rigctld (how many v)? >> >> Thanks >> Hrafnkell TF3HR >> >> On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >> And if CAT PTT still fails I need to see debug info -- add ">log.txt >> 2>&1" to the rigctld line. >> >> rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 >> --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON >> --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >log.txt 2>&1 >> >> Then send me the log file. >> >> Mike W9MDB >> >> >> >> >> >> >> On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via >> wsjt-devel wrote: >> >> >> It works fine when I'm running WSJT-X on the same computer as hamlib >> rigctld and I can set it to access the serial port directly for PTT. >> But in this case I'm running WSJT-X on Windows but running hamlib rigctld >> on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the >> raspberry pi. >> The communication between WSJT-X and hamlib happens over a network. So >> I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a >> rig_set_ptt command that then turns into a network message and the rigctld >> backend then performs a PTT. >> >> Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed >> call rig_set_ptt. >> >> Is it possible that WSJT-X is trying to open a local COM port on windows >> when setting up the communication to hamlib even though it is not set to >> use DTR or RTS PTT? >> Could it be that the code still tries to open a local COM port even >> though the rig control is set to a network server and PTT is selected as >> CAT? >> >> Thanks for your help >> Hrafnkell TF3HR >> >> On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >> WSJT-X has to be set up to use the same RTS keying and the the >> /dev/ttyUSB1 port. >> >> Just tested it here and it uses it correctly (though I tested on Windows). >> >> Mike W9MDB >> >> >> >> >> >> >> >> On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via >> wsjt-devel wrote: >> >> >> > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and >> might be why it's not working. >> I have rts_state and dts_state ON to power the CAT cable. The --set_conf >> option only seems to apply to the rig-file device, not the ptt device. I >> can remove the rts_state=ON, it has no effect on PTT >> >> PTT over hamlib is working, it's just WSJT-X that is not using it. I can >> use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. >> >> 73 de Hrafnkell TF3HR >> >> On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >> The 706MKIIG does not
Re: [wsjt-devel] Error
Same infos here with Win 11 + RC1 Keijo OG5O Lähetetty Windowsin Sähköpostiista Lähettäjä: mpcorey--- via wsjt-devel Lähetetty: torstai 23. kesäkuuta 2022 19.13 Vastaanottaja: wsjt-devel@lists.sourceforge.net Kopio: mpco...@gmail.com Aihe: [wsjt-devel] Error Good afternoon, I am using the 2.6.0-rc1 release, and generally like the new features and have encountered no problems. However, today while calling CQ on 6 meters FT8, the program abruptly shut down. There was no indication in the task bar that it was still running. I tried to restart it and received these two error messages (see attached). I went into the task manager and was able to locate a file called JT9 that was running, once I ended that process I was able to restart the program. I am running a Windows 11 machine. Thanks, Mike, KI1U ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Error
I had this begin to happen on a previously stable version 2.5.3 but a long delayed upgrade to 2.5.4 got rid of it, W10. Only a week or so ago. I haven't been able to test the RC yet, but thought I'd report this just in case it's from the same cause. Alan G0TLK, sent from my mobile device On 23 June 2022 17:12:55 mpcorey--- via wsjt-devel wrote: Good afternoon, I am using the 2.6.0-rc1 release, and generally like the new features and have encountered no problems. However, today while calling CQ on 6 meters FT8, the program abruptly shut down. There was no indication in the task bar that it was still running. I tried to restart it and received these two error messages (see attached). I went into the task manager and was able to locate a file called JT9 that was running, once I ended that process I was able to restart the program. I am running a Windows 11 machine. Thanks, Mike, KI1U ___ 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] Hamlib rigcontrol and PTT
> On the Pi, or any Linux based system, you have to be a member of the dialout group in order to have access to the serial port. So if all of the software is being denied access to the serial port, most likely, your not a member of group dialout. Thank you for the suggestion Jeff. This is not the problem though as I can have other software than wsjtx trigger a ptt over the network. Best Hrafnkell TF3HR On Thu, Jun 23, 2022 at 3:28 PM Jeff Stillinger via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On the Pi, or any Linux based system, you have to be a member of the > dialout group in order to have access to the serial port. So if all of the > software is being denied access to the serial port, most likely, your not a > member of group dialout. > > sudo -a -G dialout > > Reboot to be safe, but logging out and back in will also work. > > You should now have access to your /dev/ttyUSB* ports. > > > > On 6/23/22 08:13, Hrafnkell Eiriksson via wsjt-devel wrote: > > It works fine when I'm running WSJT-X on the same computer as hamlib > rigctld and I can set it to access the serial port directly for PTT. > But in this case I'm running WSJT-X on Windows but running hamlib rigctld > on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the > raspberry pi. > The communication between WSJT-X and hamlib happens over a network. So I'm > expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a > rig_set_ptt command that then turns into a network message and the rigctld > backend then performs a PTT. > > Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed > call rig_set_ptt. > > Is it possible that WSJT-X is trying to open a local COM port on windows > when setting up the communication to hamlib even though it is not set to > use DTR or RTS PTT? > Could it be that the code still tries to open a local COM port even though > the rig control is set to a network server and PTT is selected as CAT? > > Thanks for your help > Hrafnkell TF3HR > > On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> WSJT-X has to be set up to use the same RTS keying and the the >> /dev/ttyUSB1 port. >> >> Just tested it here and it uses it correctly (though I tested on Windows). >> >> Mike W9MDB >> >> >> >> >> >> >> >> On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via >> wsjt-devel wrote: >> >> >> > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and >> might be why it's not working. >> I have rts_state and dts_state ON to power the CAT cable. The --set_conf >> option only seems to apply to the rig-file device, not the ptt device. I >> can remove the rts_state=ON, it has no effect on PTT >> >> PTT over hamlib is working, it's just WSJT-X that is not using it. I can >> use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. >> >> 73 de Hrafnkell TF3HR >> >> On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >> The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. >> >> Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might >> be why it's not working. >> >> And dtr_state=ON would only be needed if your CAT cable needs power from >> the computer to work. >> >> Mike W9MDB >> >> >> >> >> On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via >> wsjt-devel wrote: >> >> >> Hi >> >> I'm running WSJT-X v2.5.4 on a Win10 computer. >> I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected >> it to my Icom706mk2g. >> I'm using two com ports from the RPi, one for CAT control and one for PTT. >> I've set WSJT-X to use hamlib for rig control and pointed it to the >> ip:port of my RPi. >> >> Test CAT works fine and WSJT-X can set and read the frequency if I have >> PTT method set to Vox. >> If I set PTT method to CAT then Test CAT fails with the error: >> Rig failure >> 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 >> >> I can use the hamlib CAT PTT from other software such as Log4OM without >> issues. >> I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the >> same, that is use hamlib calls to do PTT. >> >> My rigctld command line is >> rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 >> --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON >> --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >> >> Am I setting something wrong or misunderstanding something? >> >> Thanks >> Hrafnkell TF3HR >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Error
Good afternoon, I am using the 2.6.0-rc1 release, and generally like the new features and have encountered no problems. However, today while calling CQ on 6 meters FT8, the program abruptly shut down. There was no indication in the task bar that it was still running. I tried to restart it and received these two error messages (see attached). I went into the task manager and was able to locate a file called JT9 that was running, once I ended that process I was able to restart the program. I am running a Windows 11 machine. Thanks, Mike, KI1U ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hamlib rigcontrol and PTT
When pressing Test CAT a connection is opened from WSJT-X to rigctld and closed very quickly as WSJT-X displays the error message in my original email This is the part of the log after I press Test CAT. I'll send you the log directly as I do not think the mailing list allows them. 2022-06-23T15:05:21.684637-: Connection opened from 192.168.1.173:65129 2022-06-23T15:05:21.685519-: mutex_rigctld: client lock engaged 2022-06-23T15:05:21.685778-: mutex_rigctld: client lock disengaged 2022-06-23T15:05:21.685895-: mutex_rigctld: client lock engaged 2022-06-23T15:05:21.686008-: mutex_rigctld: client lock disengaged 2022-06-23T15:05:21.686120-: handle_socket: doing rigctl_parse vfo_mode=0, secure=0 2022-06-23T15:05:21.686235-: rigctl_parse: called, interactive=1 2022-06-23T15:05:23.686621-: scanfc: ret=-1 2022-06-23T15:05:23.686809-: rigctl_parse: nothing to scan#1? retcode=-1, last_cmd=^@ 2022-06-23T15:05:23.686924-: handle_socket: rigctl_parse retcode=2 2022-06-23T15:05:23.687046-: Connection closed from 192.168.1.173:65129 Error in WSJT-X 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 Tnx Hrafnkell TF3HR On Thu, Jun 23, 2022 at 2:20 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > All 5 > -v > > > > > On Thursday, June 23, 2022 at 09:18:14 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > I'll get you that log later today. What verbose level do you need on > rigctld (how many v)? > > Thanks > Hrafnkell TF3HR > > On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" > to the rigctld line. > > rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 > --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON > --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >log.txt 2>&1 > > Then send me the log file. > > Mike W9MDB > > > > > > > On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > It works fine when I'm running WSJT-X on the same computer as hamlib > rigctld and I can set it to access the serial port directly for PTT. > But in this case I'm running WSJT-X on Windows but running hamlib rigctld > on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the > raspberry pi. > The communication between WSJT-X and hamlib happens over a network. So I'm > expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a > rig_set_ptt command that then turns into a network message and the rigctld > backend then performs a PTT. > > Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed > call rig_set_ptt. > > Is it possible that WSJT-X is trying to open a local COM port on windows > when setting up the communication to hamlib even though it is not set to > use DTR or RTS PTT? > Could it be that the code still tries to open a local COM port even though > the rig control is set to a network server and PTT is selected as CAT? > > Thanks for your help > Hrafnkell TF3HR > > On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > WSJT-X has to be set up to use the same RTS keying and the the > /dev/ttyUSB1 port. > > Just tested it here and it uses it correctly (though I tested on Windows). > > Mike W9MDB > > > > > > > > On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and > might be why it's not working. > I have rts_state and dts_state ON to power the CAT cable. The --set_conf > option only seems to apply to the rig-file device, not the ptt device. I > can remove the rts_state=ON, it has no effect on PTT > > PTT over hamlib is working, it's just WSJT-X that is not using it. I can > use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. > > 73 de Hrafnkell TF3HR > > On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might > be why it's not working. > > And dtr_state=ON would only be needed if your CAT cable needs power from > the computer to work. > > Mike W9MDB > > > > > On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > Hi > > I'm running WSJT-X v2.5.4 on a Win10 computer. > I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected > it to my Icom706mk2g. > I'm using two com ports from the RPi, one for CAT control and one for PTT. > I've
Re: [wsjt-devel] Hamlib rigcontrol and PTT
On the Pi, or any Linux based system, you have to be a member of the dialout group in order to have access to the serial port. So if all of the software is being denied access to the serial port, most likely, your not a member of group dialout. sudo -a -G dialout Reboot to be safe, but logging out and back in will also work. You should now have access to your /dev/ttyUSB* ports. On 6/23/22 08:13, Hrafnkell Eiriksson via wsjt-devel wrote: It works fine when I'm running WSJT-X on the same computer as hamlib rigctld and I can set it to access the serial port directly for PTT. But in this case I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi. The communication between WSJT-X and hamlib happens over a network. So I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a rig_set_ptt command that then turns into a network message and the rigctld backend then performs a PTT. Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call rig_set_ptt. Is it possible that WSJT-X is trying to open a local COM port on windows when setting up the communication to hamlib even though it is not set to use DTR or RTS PTT? Could it be that the code still tries to open a local COM port even though the rig control is set to a network server and PTT is selected as CAT? Thanks for your help Hrafnkell TF3HR On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel wrote: WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1 port. Just tested it here and it uses it correctly (though I tested on Windows). Mike W9MDB On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. I have rts_state and dts_state ON to power the CAT cable. The --set_conf option only seems to apply to the rig-file device, not the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel wrote: The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. And dtr_state=ON would only be needed if your CAT cable needs power from the computer to work. Mike W9MDB On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: Hi I'm running WSJT-X v2.5.4 on a Win10 computer. I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g. I'm using two com ports from the RPi, one for CAT control and one for PTT. I've set WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi. Test CAT works fine and WSJT-X can set and read the frequency if I have PTT method set to Vox. If I set PTT method to CAT then Test CAT fails with the error: Rig failure 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 I can use the hamlib CAT PTT from other software such as Log4OM without issues. I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the same, that is use hamlib calls to do PTT. My rigctld command line is rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z Am I setting something wrong or misunderstanding something? Thanks Hrafnkell TF3HR ___ 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel
[wsjt-devel] WSJT-X 2.6.0 rc1 - wspr transmit ending early
2.6.0-rc1, built from source on Fedora Core 36, 64-bit. In the WSPR mode, the first transmit cycle (after several normal receive cycles) ends 95 seconds after the start of the window.. Example - Transmit window starts at 14:16:00, ends at 14:17:35. WSJT-X stays on the same band from that point until the end of the next window at 14:20:00. There is also a warning on startup: QSocketNotifier: Can only be used with threads started with QThread Does that imply that the thread in question was *not* started with QThread? -- P.J. "Josh" Rovero http://www.roveroresearch.org Ham Radio: KK1D ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hamlib rigcontrol and PTT
All 5-v On Thursday, June 23, 2022 at 09:18:14 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: I'll get you that log later today. What verbose level do you need on rigctld (how many v)? Thanks Hrafnkell TF3HR On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel wrote: And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" to the rigctld line. rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >log.txt 2>&1 Then send me the log file. Mike W9MDB On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: It works fine when I'm running WSJT-X on the same computer as hamlib rigctld and I can set it to access the serial port directly for PTT.But in this case I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi.The communication between WSJT-X and hamlib happens over a network. So I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a rig_set_ptt command that then turns into a network message and the rigctld backend then performs a PTT. Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call rig_set_ptt. Is it possible that WSJT-X is trying to open a local COM port on windows when setting up the communication to hamlib even though it is not set to use DTR or RTS PTT?Could it be that the code still tries to open a local COM port even though the rig control is set to a network server and PTT is selected as CAT? Thanks for your help Hrafnkell TF3HR On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel wrote: WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1 port. Just tested it here and it uses it correctly (though I tested on Windows). Mike W9MDB On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be >why it's not working.I have rts_state and dts_state ON to power the CAT >cable. The --set_conf option only seems to apply to the rig-file device, not >the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel wrote: The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. And dtr_state=ON would only be needed if your CAT cable needs power from the computer to work. Mike W9MDB On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: Hi I'm running WSJT-X v2.5.4 on a Win10 computer.I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g.I'm using two com ports from the RPi, one for CAT control and one for PTT.I've set WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi. Test CAT works fine and WSJT-X can set and read the frequency if I have PTT method set to Vox.If I set PTT method to CAT then Test CAT fails with the error:Rig failureHamlib error: IO errornetwork.c(441):network_close return(0)iofunc.c(361):port_close return(0)rig.c(1047):rig_open return(-6) IO errornetwork.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 I can use the hamlib CAT PTT from other software such as Log4OM without issues.I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the same, that is use hamlib calls to do PTT. My rigctld command line isrigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z Am I setting something wrong or misunderstanding something? Thanks Hrafnkell TF3HR___ 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 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 mailing list
Re: [wsjt-devel] Hamlib rigcontrol and PTT
I'll get you that log later today. What verbose level do you need on rigctld (how many v)? Thanks Hrafnkell TF3HR On Thu, Jun 23, 2022 at 1:44 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" > to the rigctld line. > > rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 > --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON > --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >log.txt 2>&1 > > Then send me the log file. > > Mike W9MDB > > > > > > > On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > It works fine when I'm running WSJT-X on the same computer as hamlib > rigctld and I can set it to access the serial port directly for PTT. > But in this case I'm running WSJT-X on Windows but running hamlib rigctld > on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the > raspberry pi. > The communication between WSJT-X and hamlib happens over a network. So I'm > expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a > rig_set_ptt command that then turns into a network message and the rigctld > backend then performs a PTT. > > Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed > call rig_set_ptt. > > Is it possible that WSJT-X is trying to open a local COM port on windows > when setting up the communication to hamlib even though it is not set to > use DTR or RTS PTT? > Could it be that the code still tries to open a local COM port even though > the rig control is set to a network server and PTT is selected as CAT? > > Thanks for your help > Hrafnkell TF3HR > > On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > WSJT-X has to be set up to use the same RTS keying and the the > /dev/ttyUSB1 port. > > Just tested it here and it uses it correctly (though I tested on Windows). > > Mike W9MDB > > > > > > > > On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and > might be why it's not working. > I have rts_state and dts_state ON to power the CAT cable. The --set_conf > option only seems to apply to the rig-file device, not the ptt device. I > can remove the rts_state=ON, it has no effect on PTT > > PTT over hamlib is working, it's just WSJT-X that is not using it. I can > use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. > > 73 de Hrafnkell TF3HR > > On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might > be why it's not working. > > And dtr_state=ON would only be needed if your CAT cable needs power from > the computer to work. > > Mike W9MDB > > > > > On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > Hi > > I'm running WSJT-X v2.5.4 on a Win10 computer. > I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected > it to my Icom706mk2g. > I'm using two com ports from the RPi, one for CAT control and one for PTT. > I've set WSJT-X to use hamlib for rig control and pointed it to the > ip:port of my RPi. > > Test CAT works fine and WSJT-X can set and read the frequency if I have > PTT method set to Vox. > If I set PTT method to CAT then Test CAT fails with the error: > Rig failure > 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 > > I can use the hamlib CAT PTT from other software such as Log4OM without > issues. > I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the > same, that is use hamlib calls to do PTT. > > My rigctld command line is > rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 > --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON > --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z > > Am I setting something wrong or misunderstanding something? > > Thanks > Hrafnkell TF3HR > ___ > 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 mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ > wsjt-devel mailing
Re: [wsjt-devel] RC1 quits
In \Users\[username]\AppData\Local\WSJT-X rename the WSJT-X.ini file. That will allow you to start a new setup. Mike W9MDB On Wednesday, June 22, 2022 at 07:06:52 PM CDT, Donhawbaker via wsjt-devel wrote: At first RC1 worked fine. But now it boots up, shows the splash beta screen, then the TS-2000 beeps, and when I hit Okay, the program quits. I have no access to the setup screen. I reloaded the program twice. Same result. 2.5.4 runs fine. ___ 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] Hamlib rigcontrol and PTT
And if CAT PTT still fails I need to see debug info -- add ">log.txt 2>&1" to the rigctld line. rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z >log.txt 2>&1 Then send me the log file. Mike W9MDB On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: It works fine when I'm running WSJT-X on the same computer as hamlib rigctld and I can set it to access the serial port directly for PTT.But in this case I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi.The communication between WSJT-X and hamlib happens over a network. So I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a rig_set_ptt command that then turns into a network message and the rigctld backend then performs a PTT. Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call rig_set_ptt. Is it possible that WSJT-X is trying to open a local COM port on windows when setting up the communication to hamlib even though it is not set to use DTR or RTS PTT?Could it be that the code still tries to open a local COM port even though the rig control is set to a network server and PTT is selected as CAT? Thanks for your help Hrafnkell TF3HR On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel wrote: WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1 port. Just tested it here and it uses it correctly (though I tested on Windows). Mike W9MDB On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be >why it's not working.I have rts_state and dts_state ON to power the CAT >cable. The --set_conf option only seems to apply to the rig-file device, not >the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel wrote: The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. And dtr_state=ON would only be needed if your CAT cable needs power from the computer to work. Mike W9MDB On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: Hi I'm running WSJT-X v2.5.4 on a Win10 computer.I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g.I'm using two com ports from the RPi, one for CAT control and one for PTT.I've set WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi. Test CAT works fine and WSJT-X can set and read the frequency if I have PTT method set to Vox.If I set PTT method to CAT then Test CAT fails with the error:Rig failureHamlib error: IO errornetwork.c(441):network_close return(0)iofunc.c(361):port_close return(0)rig.c(1047):rig_open return(-6) IO errornetwork.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 I can use the hamlib CAT PTT from other software such as Log4OM without issues.I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the same, that is use hamlib calls to do PTT. My rigctld command line isrigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z Am I setting something wrong or misunderstanding something? Thanks Hrafnkell TF3HR___ 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 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 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] Hamlib rigcontrol and PTT
Then PTT CAT should work. WSJTX should send the "T" command to rigctld and rigctld then uses the RTS keying. I just confirmed that works. 2022-06-23T08:37:29.191879-0600: rigctl(d): T 'currVFO' '3' '' ''2022-06-23T08:37:29.191879-0600: rigctl_parse: vfo_opt=02022-06-23T08:37:29.191879-0600: 2:rigctl_parse.c(2466):rigctl_set_ptt entered2022-06-23T08:37:29.191879-0600: rigctl_set_ptt: set_ptt ptt=32022-06-23T08:37:29.191879-0600: rigctl_set_ptt: ptt=32022-06-23T08:37:29.191879-0600: 3:rig.c(2845):rig_set_ptt entered2022-06-23T08:37:29.191879-0600: ser_set_rts: RTS=12022-06-23T08:37:29.191879-0600: rig_set_ptt: rigport=COM21, pttport=127.0.0.1:12345, ptt_share=02022-06-23T08:37:29.243640-0600: 3:rig_set_ptt: elapsed=52ms2022-06-23T08:37:29.243640-0600: 3:rig.c(3114):rig_set_ptt returning(0) Mike W9MDB On Thursday, June 23, 2022 at 08:19:19 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: It works fine when I'm running WSJT-X on the same computer as hamlib rigctld and I can set it to access the serial port directly for PTT.But in this case I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi.The communication between WSJT-X and hamlib happens over a network. So I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a rig_set_ptt command that then turns into a network message and the rigctld backend then performs a PTT. Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call rig_set_ptt. Is it possible that WSJT-X is trying to open a local COM port on windows when setting up the communication to hamlib even though it is not set to use DTR or RTS PTT?Could it be that the code still tries to open a local COM port even though the rig control is set to a network server and PTT is selected as CAT? Thanks for your help Hrafnkell TF3HR On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel wrote: WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1 port. Just tested it here and it uses it correctly (though I tested on Windows). Mike W9MDB On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be >why it's not working.I have rts_state and dts_state ON to power the CAT >cable. The --set_conf option only seems to apply to the rig-file device, not >the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel wrote: The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. And dtr_state=ON would only be needed if your CAT cable needs power from the computer to work. Mike W9MDB On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: Hi I'm running WSJT-X v2.5.4 on a Win10 computer.I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g.I'm using two com ports from the RPi, one for CAT control and one for PTT.I've set WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi. Test CAT works fine and WSJT-X can set and read the frequency if I have PTT method set to Vox.If I set PTT method to CAT then Test CAT fails with the error:Rig failureHamlib error: IO errornetwork.c(441):network_close return(0)iofunc.c(361):port_close return(0)rig.c(1047):rig_open return(-6) IO errornetwork.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 I can use the hamlib CAT PTT from other software such as Log4OM without issues.I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the same, that is use hamlib calls to do PTT. My rigctld command line isrigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z Am I setting something wrong or misunderstanding something? Thanks Hrafnkell TF3HR___ 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___
Re: [wsjt-devel] Hamlib rigcontrol and PTT
It works fine when I'm running WSJT-X on the same computer as hamlib rigctld and I can set it to access the serial port directly for PTT. But in this case I'm running WSJT-X on Windows but running hamlib rigctld on a Raspberry Pi. WSJT-X does not have access to the /dev/ttyUSB* on the raspberry pi. The communication between WSJT-X and hamlib happens over a network. So I'm expecting the hamlib code in WSJT-X to delegate the PTT to hamlib as a rig_set_ptt command that then turns into a network message and the rigctld backend then performs a PTT. Browsing the code shows that there HamlibTranceiver::do_ptt() does indeed call rig_set_ptt. Is it possible that WSJT-X is trying to open a local COM port on windows when setting up the communication to hamlib even though it is not set to use DTR or RTS PTT? Could it be that the code still tries to open a local COM port even though the rig control is set to a network server and PTT is selected as CAT? Thanks for your help Hrafnkell TF3HR On Thu, Jun 23, 2022 at 12:06 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > WSJT-X has to be set up to use the same RTS keying and the the > /dev/ttyUSB1 port. > > Just tested it here and it uses it correctly (though I tested on Windows). > > Mike W9MDB > > > > > > > > On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and > might be why it's not working. > I have rts_state and dts_state ON to power the CAT cable. The --set_conf > option only seems to apply to the rig-file device, not the ptt device. I > can remove the rts_state=ON, it has no effect on PTT > > PTT over hamlib is working, it's just WSJT-X that is not using it. I can > use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. > > 73 de Hrafnkell TF3HR > > On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might > be why it's not working. > > And dtr_state=ON would only be needed if your CAT cable needs power from > the computer to work. > > Mike W9MDB > > > > > On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > Hi > > I'm running WSJT-X v2.5.4 on a Win10 computer. > I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected > it to my Icom706mk2g. > I'm using two com ports from the RPi, one for CAT control and one for PTT. > I've set WSJT-X to use hamlib for rig control and pointed it to the > ip:port of my RPi. > > Test CAT works fine and WSJT-X can set and read the frequency if I have > PTT method set to Vox. > If I set PTT method to CAT then Test CAT fails with the error: > Rig failure > 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 > > I can use the hamlib CAT PTT from other software such as Log4OM without > issues. > I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the > same, that is use hamlib calls to do PTT. > > My rigctld command line is > rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 > --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON > --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z > > Am I setting something wrong or misunderstanding something? > > Thanks > Hrafnkell TF3HR > ___ > 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 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hamlib rigcontrol and PTT
WSJT-X has to be set up to use the same RTS keying and the the /dev/ttyUSB1 port. Just tested it here and it uses it correctly (though I tested on Windows). Mike W9MDB On Thursday, June 23, 2022 at 03:53:35 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be >why it's not working.I have rts_state and dts_state ON to power the CAT >cable. The --set_conf option only seems to apply to the rig-file device, not >the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel wrote: The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. And dtr_state=ON would only be needed if your CAT cable needs power from the computer to work. Mike W9MDB On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via wsjt-devel wrote: Hi I'm running WSJT-X v2.5.4 on a Win10 computer.I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected it to my Icom706mk2g.I'm using two com ports from the RPi, one for CAT control and one for PTT.I've set WSJT-X to use hamlib for rig control and pointed it to the ip:port of my RPi. Test CAT works fine and WSJT-X can set and read the frequency if I have PTT method set to Vox.If I set PTT method to CAT then Test CAT fails with the error:Rig failureHamlib error: IO errornetwork.c(441):network_close return(0)iofunc.c(361):port_close return(0)rig.c(1047):rig_open return(-6) IO errornetwork.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 I can use the hamlib CAT PTT from other software such as Log4OM without issues.I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the same, that is use hamlib calls to do PTT. My rigctld command line isrigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z Am I setting something wrong or misunderstanding something? Thanks Hrafnkell TF3HR___ 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 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] Hamlib rigcontrol and PTT
> Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might be why it's not working. I have rts_state and dts_state ON to power the CAT cable. The --set_conf option only seems to apply to the rig-file device, not the ptt device. I can remove the rts_state=ON, it has no effect on PTT PTT over hamlib is working, it's just WSJT-X that is not using it. I can use e.g. a voice keyer in Log4OM and it does PTT properly through hamlib. 73 de Hrafnkell TF3HR On Wed, Jun 22, 2022 at 11:07 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > The 706MKIIG does not do CAT PTT per se but the ptt-type=RTS should work. > > Why do you have rst_state=ON? That conflicts with ptt-type=RTS and might > be why it's not working. > > And dtr_state=ON would only be needed if your CAT cable needs power from > the computer to work. > > Mike W9MDB > > > > > On Wednesday, June 22, 2022 at 11:35:27 AM CDT, Hrafnkell Eiriksson via > wsjt-devel wrote: > > > Hi > > I'm running WSJT-X v2.5.4 on a Win10 computer. > I've set up hamlib rigctld (version 4.4) on a Raspberry Pi and connected > it to my Icom706mk2g. > I'm using two com ports from the RPi, one for CAT control and one for PTT. > I've set WSJT-X to use hamlib for rig control and pointed it to the > ip:port of my RPi. > > Test CAT works fine and WSJT-X can set and read the frequency if I have > PTT method set to Vox. > If I set PTT method to CAT then Test CAT fails with the error: > Rig failure > 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 > > I can use the hamlib CAT PTT from other software such as Log4OM without > issues. > I would expect CAT PTT with hamlib rigcontrol in WSJT-X to behave the > same, that is use hamlib calls to do PTT. > > My rigctld command line is > rigctld --model=3011 --rig-file=/dev/ttyUSB0 --serial-speed=4800 > --port=4532 --set-conf=stop_bits=1,dtr_state=ON,rts_state=ON > --ptt-file=/dev/ttyUSB1 --ptt-type=RTS -Z > > Am I setting something wrong or misunderstanding something? > > Thanks > Hrafnkell TF3HR > ___ > 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 mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
