[wsjt-devel] (no subject)
Hello Please remove me from the mailing list Thank you 73 HB3YMW Rolf Banholzer ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
Hello Please remove me from the mailing list Thank you 73 HB3YMW Rolf Banholzer ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Tried that. Can't recover the PW to log in. -Original Message- From: Neil Zampella [mailto:ne...@techie.com] Sent: Friday, February 5, 2021 11:38 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] (no subject) That's not going to work, you have to go to the URL shown at the bottom of each message. Neil, KN3ILZ On 2/5/2021 11:30 AM, John Zantek wrote: > unsub > > > > ___ 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] (no subject)
That's not going to work, you have to go to the URL shown at the bottom of each message. Neil, KN3ILZ On 2/5/2021 11:30 AM, John Zantek wrote: unsub ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
unsub ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Bill, Robert had already provided you this info in response on your posts on the FT8 group, with his link to the thread ; "robert.e.pierce@... Mar 28 #3591 <https://groups.io/g/FT8-Digital-Mode/message/3591> Which version of the Silicon Labs driver are you using? I had to roll back to an earlier version CP210x Macintosh OSX VCP Driver 5.3.5 - February 25, 2020 - Fails CP210x Macintosh OSX VCP Driver 5.2.3 - December 6, 2019 - Works" and I think he deserves the credit for steering you to a solution. On 25/5/20 12:58 am, Bill wrote: PROBLEM SOLVED There appears to be an incompatibility issue between the currently posted Silicon Labs Driver for Mac version 5.3.5 and the Yaesu FTDX101MP at least on my Mac system running OS version High Sierra. I had to uninstall the 5.3.5 driver and install the previous version 5.2.4 (Dated Dec 13, 2019). Once the legacy driver was installed everything started working with my previously posted WSJT-X and FTDX101MP settings. A Google search on this issue resulted in finding others who have fixed the radio connection issue by downgrading the SILAB driver. I hope this solution helps others in getting their new radios going. Thanks to everyone helping solve this issue! 73, Bill - AK6A On Sat, May 23, 2020 at 11:11 PM Adrian <mailto:vk4...@gmail.com>> wrote: After the latest MP FW update, wsjtx 2.1.2, and using Data-U designed for this purpose re WSJTX, the setup is simple, especially using both the enhanced compors for CAT and standard comport for Ptt via RTS. It works great. On 24/5/20 3:28 pm, Ken Chandler via wsjt-devel wrote: I had issues to but on window 10 platform. I used the FT5000 rig, everything burst into life when I switched over from FTdx101D Ken.. G0ORH Sent from my iPad On 24 May 2020, at 01:02, John Zantek mailto:j...@zantek.net>> wrote: Bill, Many new 101MP owners in the PNW have been experiencing some setup issues, resulting in lots of phone calls. Have you been able to talk to the rig with any other S/W via USB and with what virtual settings? Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in that regard. No hubs, right? 73 John W7CD *From:*Bill [mailto:brightl...@gmail.com] *Sent:* Saturday, May 23, 2020 3:59 PM *To:* WSJT software development *Subject:* Re: [wsjt-devel] (no subject) Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville mailto:g4...@classdesign.com>> wrote: On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be t
Re: [wsjt-devel] (no subject)
Without seeing debug logs can't tell you...but it sure sounds like a driver problem. Hamlib doesn't know or care what driver you're using. If changing drivers makes/breaks things then it's most likely the driver. Mike W9MDB On Sunday, May 24, 2020, 10:02:31 AM CDT, Bill wrote: Hi Mike, I was able to fix the issue by installing an earlier version of the Mac OS SILAB driver. Is the issue really within HAMLIB and the earlier driver just gets around the issue? 73, Bill - AK6A On Sun, May 24, 2020 at 7:59 AM Black Michael via wsjt-devel wrote: I've identified some problems with the 101D that I'll be fixing. Mike W9MDB On Sunday, May 24, 2020, 12:55:37 AM CDT, Ken Chandler via wsjt-devel wrote: I had issues to but on window 10 platform.I used the FT5000 rig, everything burst into life when I switched over from FTdx101D Ken.. G0ORH Sent from my iPad On 24 May 2020, at 01:02, John Zantek wrote: Bill, Many new 101MP owners in the PNW have been experiencing some setup issues, resulting in lots of phone calls. Have you been able to talk to the rig with any other S/W via USB and with what virtual settings? Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in that regard. No hubs, right? 73 John W7CD From: Bill [mailto:brightl...@gmail.com] Sent: Saturday, May 23, 2020 3:59 PM To: WSJT software development Subject: Re: [wsjt-devel] (no subject) Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville wrote: On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A Hi Bill, try with "Settings->Radio->Handshake->None". 73 Bill G4WJS. ___ 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] (no subject)
Hi Mike, I was able to fix the issue by installing an earlier version of the Mac OS SILAB driver. Is the issue really within HAMLIB and the earlier driver just gets around the issue? 73, Bill - AK6A On Sun, May 24, 2020 at 7:59 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I've identified some problems with the 101D that I'll be fixing. > > Mike W9MDB > > > > > On Sunday, May 24, 2020, 12:55:37 AM CDT, Ken Chandler via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > I had issues to but on window 10 platform. > I used the FT5000 rig, everything burst into life when I switched over > from FTdx101D > > Ken.. G0ORH > > Sent from my iPad > > > On 24 May 2020, at 01:02, John Zantek wrote: > > Bill, > > Many new 101MP owners in the PNW have been experiencing some setup issues, > resulting in lots of phone calls. > > Have you been able to talk to the rig with any other S/W via USB and with > what virtual settings? > > Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety > in that regard. > > No hubs, right? > > 73 John W7CD > > > > *From:* Bill [mailto:brightl...@gmail.com ] > *Sent:* Saturday, May 23, 2020 3:59 PM > *To:* WSJT software development > *Subject:* Re: [wsjt-devel] (no subject) > > > > Hi, > > > > Thanks for the quick response. I just tried HandShake = NONE and I > have the same result - Rig Failure - HamLib Error. > > > >Any other suggestions? > > > > Thanks! > > > > Bill - AK6A > > > > On Sat, May 23, 2020 at 3:32 PM Bill Somerville > wrote: > > On 23/05/2020 23:16, Bill wrote: > > I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m > able to get the receive Audio Codec to work properly and I can see decodes > but I get a “Rig Failure - Hamlib Error - Invalid configuration while > opening connection to rig” whenever I do a Test CAT. I am unable to get > WSJT-X to establish control communications with the radio. I’ve seen online > suggestions that say use the HamLib FT-991 selection. I am using the > regular WSJT-X version 2.1.2. I am also just using a USB cable from the > radio to the Mac which is running High Sierra. I am using the following > settings: > > > > WSJT-X > > > > RADIO TAB > > > > Rig: Yaesu FT-991 > > > > Serial Port: /dev/cu.SLAB_USBtoUART1 > > Note: Installed latest Silicon Labs Drivers - Also Available selections: > > /dev/tty.SLAB_USBtoUART1 > > /dev/cu.SLAB_USBtoUART > > /dev/tty.SLAB_USBtoUART > > > > Baud Rate: 38400 > > Polling Interval: 1S > > Data Bits: Eight > > Stop Bits: Two > > Handshake: Hardware > > Force Control Lines: Both Empty > > > > PTT Method: CAT > > Mode: None > > Split: Rig > > > > AUDIO Tab > > > > Input - USB AUDIO CODEC > Output - USB AUDIO CODEC > > FTDX101MP Menu > > > > FUNC --> Operation Settings > General > 232C RATE - 38400 > CAT RATE - 38400 > > FUNC --> RADIO SETTINGS > MODE SSB > SSB MOD SOURCE - REAR > REAR SELECT - USB > RPORT GAIN - 10 > DATA MODE SOURCE - REAR (This is the default) > REAR SELECT - USB > DATA OUT LEVEL - 10 > RPORT GAIN - 10 > > RADIO MAIN PANEL & DISPLAY > > > > > > R.FIL - 3kHz > WIDTH - 4000Hz > > > APPLE COMPUTER > > > > USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz > USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz > > > > > > > > Any ideas what might be the issue in getting this going? Has anyone else > been able to get a FTDX-101MP working with WSJT-X? Do I need to install a > newer version of HamLib for this new radio? > > > > Thanks! > > > > Bill - AK6A > > Hi Bill, > > try with "Settings->Radio->Handshake->None". > > 73 > Bill > G4WJS. > > ___ > 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] (no subject)
PROBLEM SOLVED There appears to be an incompatibility issue between the currently posted Silicon Labs Driver for Mac version 5.3.5 and the Yaesu FTDX101MP at least on my Mac system running OS version High Sierra. I had to uninstall the 5.3.5 driver and install the previous version 5.2.4 (Dated Dec 13, 2019). Once the legacy driver was installed everything started working with my previously posted WSJT-X and FTDX101MP settings. A Google search on this issue resulted in finding others who have fixed the radio connection issue by downgrading the SILAB driver. I hope this solution helps others in getting their new radios going. Thanks to everyone helping solve this issue! 73, Bill - AK6A On Sat, May 23, 2020 at 11:11 PM Adrian wrote: > After the latest MP FW update, wsjtx 2.1.2, and using Data-U designed for > this purpose re WSJTX, the setup is simple, especially using both the > enhanced compors for CAT and standard > > comport for Ptt via RTS. It works great. > > > On 24/5/20 3:28 pm, Ken Chandler via wsjt-devel wrote: > > I had issues to but on window 10 platform. > I used the FT5000 rig, everything burst into life when I switched over > from FTdx101D > > Ken.. G0ORH > > Sent from my iPad > > > On 24 May 2020, at 01:02, John Zantek wrote: > > Bill, > > Many new 101MP owners in the PNW have been experiencing some setup issues, > resulting in lots of phone calls. > > Have you been able to talk to the rig with any other S/W via USB and with > what virtual settings? > > Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety > in that regard. > > No hubs, right? > > 73 John W7CD > > > > *From:* Bill [mailto:brightl...@gmail.com ] > *Sent:* Saturday, May 23, 2020 3:59 PM > *To:* WSJT software development > *Subject:* Re: [wsjt-devel] (no subject) > > > > Hi, > > > > Thanks for the quick response. I just tried HandShake = NONE and I > have the same result - Rig Failure - HamLib Error. > > > >Any other suggestions? > > > > Thanks! > > > > Bill - AK6A > > > > On Sat, May 23, 2020 at 3:32 PM Bill Somerville > wrote: > > On 23/05/2020 23:16, Bill wrote: > > I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m > able to get the receive Audio Codec to work properly and I can see decodes > but I get a “Rig Failure - Hamlib Error - Invalid configuration while > opening connection to rig” whenever I do a Test CAT. I am unable to get > WSJT-X to establish control communications with the radio. I’ve seen online > suggestions that say use the HamLib FT-991 selection. I am using the > regular WSJT-X version 2.1.2. I am also just using a USB cable from the > radio to the Mac which is running High Sierra. I am using the following > settings: > > > > WSJT-X > > > > RADIO TAB > > > > Rig: Yaesu FT-991 > > > > Serial Port: /dev/cu.SLAB_USBtoUART1 > > Note: Installed latest Silicon Labs Drivers - Also Available selections: > > /dev/tty.SLAB_USBtoUART1 > > /dev/cu.SLAB_USBtoUART > > /dev/tty.SLAB_USBtoUART > > > > Baud Rate: 38400 > > Polling Interval: 1S > > Data Bits: Eight > > Stop Bits: Two > > Handshake: Hardware > > Force Control Lines: Both Empty > > > > PTT Method: CAT > > Mode: None > > Split: Rig > > > > AUDIO Tab > > > > Input - USB AUDIO CODEC > Output - USB AUDIO CODEC > > FTDX101MP Menu > > > > FUNC --> Operation Settings > General > 232C RATE - 38400 > CAT RATE - 38400 > > FUNC --> RADIO SETTINGS > MODE SSB > SSB MOD SOURCE - REAR > REAR SELECT - USB > RPORT GAIN - 10 > DATA MODE SOURCE - REAR (This is the default) > REAR SELECT - USB > DATA OUT LEVEL - 10 > RPORT GAIN - 10 > > RADIO MAIN PANEL & DISPLAY > > > > > > R.FIL - 3kHz > WIDTH - 4000Hz > > > APPLE COMPUTER > > > > USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz > USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz > > > > > > > > Any ideas what might be the issue in getting this going? Has anyone else > been able to get a FTDX-101MP working with WSJT-X? Do I need to install a > newer version of HamLib for this new radio? > > > > Thanks! > > > > Bill - AK6A > > Hi Bill, > > try with "Settings->Radio->Handshake->None". > > 73 > Bill > G4WJS. > > ___ > 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 > listwsjt-devel@lists.sourceforge.nethttps://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] (no subject)
I've identified some problems with the 101D that I'll be fixing. Mike W9MDB On Sunday, May 24, 2020, 12:55:37 AM CDT, Ken Chandler via wsjt-devel wrote: I had issues to but on window 10 platform.I used the FT5000 rig, everything burst into life when I switched over from FTdx101D Ken.. G0ORH Sent from my iPad On 24 May 2020, at 01:02, John Zantek wrote: Bill, Many new 101MP owners in the PNW have been experiencing some setup issues, resulting in lots of phone calls. Have you been able to talk to the rig with any other S/W via USB and with what virtual settings? Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in that regard. No hubs, right? 73 John W7CD From: Bill [mailto:brightl...@gmail.com] Sent: Saturday, May 23, 2020 3:59 PM To: WSJT software development Subject: Re: [wsjt-devel] (no subject) Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville wrote: On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A Hi Bill, try with "Settings->Radio->Handshake->None". 73 Bill G4WJS. ___ 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] (no subject)
After the latest MP FW update, wsjtx 2.1.2, and using Data-U designed for this purpose re WSJTX, the setup is simple, especially using both the enhanced compors for CAT and standard comport for Ptt via RTS. It works great. On 24/5/20 3:28 pm, Ken Chandler via wsjt-devel wrote: I had issues to but on window 10 platform. I used the FT5000 rig, everything burst into life when I switched over from FTdx101D Ken.. G0ORH Sent from my iPad On 24 May 2020, at 01:02, John Zantek <mailto:j...@zantek.net>> wrote: Bill, Many new 101MP owners in the PNW have been experiencing some setup issues, resulting in lots of phone calls. Have you been able to talk to the rig with any other S/W via USB and with what virtual settings? Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in that regard. No hubs, right? 73 John W7CD *From:*Bill [mailto:brightl...@gmail.com] *Sent:* Saturday, May 23, 2020 3:59 PM *To:* WSJT software development *Subject:* Re: [wsjt-devel] (no subject) Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville mailto:g4...@classdesign.com>> wrote: On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A Hi Bill, try with "Settings->Radio->Handshake->None". 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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] (no subject)
I had issues to but on window 10 platform. I used the FT5000 rig, everything burst into life when I switched over from FTdx101D Ken.. G0ORH Sent from my iPad > On 24 May 2020, at 01:02, John Zantek wrote: > > Bill, > Many new 101MP owners in the PNW have been experiencing some setup issues, > resulting in lots of phone calls. > Have you been able to talk to the rig with any other S/W via USB and with > what virtual settings? > Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in > that regard. > No hubs, right? > 73 John W7CD > > From: Bill [mailto:brightl...@gmail.com] > Sent: Saturday, May 23, 2020 3:59 PM > To: WSJT software development > Subject: Re: [wsjt-devel] (no subject) > > Hi, > > Thanks for the quick response. I just tried HandShake = NONE and I have > the same result - Rig Failure - HamLib Error. > >Any other suggestions? > > Thanks! > > Bill - AK6A > > On Sat, May 23, 2020 at 3:32 PM Bill Somerville wrote: > On 23/05/2020 23:16, Bill wrote: > I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m > able to get the receive Audio Codec to work properly and I can see decodes > but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening > connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to > establish control communications with the radio. I’ve seen online suggestions > that say use the HamLib FT-991 selection. I am using the regular WSJT-X > version 2.1.2. I am also just using a USB cable from the radio to the Mac > which is running High Sierra. I am using the following settings: > > > > WSJT-X > > > > RADIO TAB > > > > Rig: Yaesu FT-991 > > > > Serial Port: /dev/cu.SLAB_USBtoUART1 > > Note: Installed latest Silicon Labs Drivers - Also Available selections: > > /dev/tty.SLAB_USBtoUART1 > > /dev/cu.SLAB_USBtoUART > > /dev/tty.SLAB_USBtoUART > > > > Baud Rate: 38400 > > Polling Interval: 1S > > Data Bits: Eight > > Stop Bits: Two > > Handshake: Hardware > > Force Control Lines: Both Empty > > > > PTT Method: CAT > > Mode: None > > Split: Rig > > > > AUDIO Tab > > > > Input - USB AUDIO CODEC > Output - USB AUDIO CODEC > > FTDX101MP Menu > > > > FUNC --> Operation Settings > General > 232C RATE - 38400 > CAT RATE - 38400 > > FUNC --> RADIO SETTINGS > MODE SSB > SSB MOD SOURCE - REAR > REAR SELECT - USB > RPORT GAIN - 10 > DATA MODE SOURCE - REAR (This is the default) > REAR SELECT - USB > DATA OUT LEVEL - 10 > RPORT GAIN - 10 > > RADIO MAIN PANEL & DISPLAY > > > > > > R.FIL - 3kHz > WIDTH - 4000Hz > > > APPLE COMPUTER > > > > USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz > USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz > > > > > > > > Any ideas what might be the issue in getting this going? Has anyone else been > able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer > version of HamLib for this new radio? > > > > Thanks! > > > > Bill - AK6A > > Hi Bill, > > try with "Settings->Radio->Handshake->None". > > 73 > Bill > G4WJS. > > ___ > 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] (no subject)
Hi John, I'm using a Mac so whatever problems there might be are doubled. I've tried accessing the radio through the MacLoggerDX program but that didn't work either. I'm using USB2 direct - no hubs. There is some talk about the new Silicon Labs drivers not working properly and an older version seems to work but I can find a download for it (Version 5,2,3). It seems like some people can get it to work but how they do it is a bit vague. My FT991a took off and worked the first try. I can see the audio codecs and use them find for RX, its the radio control part that is just not cooperating. 73, Bill - AK6A On Sat, May 23, 2020 at 6:29 PM John Zantek wrote: > Bill, > > Many new 101MP owners in the PNW have been experiencing some setup issues, > resulting in lots of phone calls. > > Have you been able to talk to the rig with any other S/W via USB and with > what virtual settings? > > Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety > in that regard. > > No hubs, right? > > 73 John W7CD > > > > *From:* Bill [mailto:brightl...@gmail.com] > *Sent:* Saturday, May 23, 2020 3:59 PM > *To:* WSJT software development > *Subject:* Re: [wsjt-devel] (no subject) > > > > Hi, > > > > Thanks for the quick response. I just tried HandShake = NONE and I > have the same result - Rig Failure - HamLib Error. > > > >Any other suggestions? > > > > Thanks! > > > > Bill - AK6A > > > > On Sat, May 23, 2020 at 3:32 PM Bill Somerville > wrote: > > On 23/05/2020 23:16, Bill wrote: > > I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m > able to get the receive Audio Codec to work properly and I can see decodes > but I get a “Rig Failure - Hamlib Error - Invalid configuration while > opening connection to rig” whenever I do a Test CAT. I am unable to get > WSJT-X to establish control communications with the radio. I’ve seen online > suggestions that say use the HamLib FT-991 selection. I am using the > regular WSJT-X version 2.1.2. I am also just using a USB cable from the > radio to the Mac which is running High Sierra. I am using the following > settings: > > > > WSJT-X > > > > RADIO TAB > > > > Rig: Yaesu FT-991 > > > > Serial Port: /dev/cu.SLAB_USBtoUART1 > > Note: Installed latest Silicon Labs Drivers - Also Available selections: > > /dev/tty.SLAB_USBtoUART1 > > /dev/cu.SLAB_USBtoUART > > /dev/tty.SLAB_USBtoUART > > > > Baud Rate: 38400 > > Polling Interval: 1S > > Data Bits: Eight > > Stop Bits: Two > > Handshake: Hardware > > Force Control Lines: Both Empty > > > > PTT Method: CAT > > Mode: None > > Split: Rig > > > > AUDIO Tab > > > > Input - USB AUDIO CODEC > Output - USB AUDIO CODEC > > FTDX101MP Menu > > > > FUNC --> Operation Settings > General > 232C RATE - 38400 > CAT RATE - 38400 > > FUNC --> RADIO SETTINGS > MODE SSB > SSB MOD SOURCE - REAR > REAR SELECT - USB > RPORT GAIN - 10 > DATA MODE SOURCE - REAR (This is the default) > REAR SELECT - USB > DATA OUT LEVEL - 10 > RPORT GAIN - 10 > > RADIO MAIN PANEL & DISPLAY > > > > > > R.FIL - 3kHz > WIDTH - 4000Hz > > > APPLE COMPUTER > > > > USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz > USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz > > > > > > > > Any ideas what might be the issue in getting this going? Has anyone else > been able to get a FTDX-101MP working with WSJT-X? Do I need to install a > newer version of HamLib for this new radio? > > > > Thanks! > > > > Bill - AK6A > > Hi Bill, > > try with "Settings->Radio->Handshake->None". > > 73 > Bill > G4WJS. > > ___ > 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] (no subject)
Bill, Many new 101MP owners in the PNW have been experiencing some setup issues, resulting in lots of phone calls. Have you been able to talk to the rig with any other S/W via USB and with what virtual settings? Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in that regard. No hubs, right? 73 John W7CD From: Bill [mailto:brightl...@gmail.com] Sent: Saturday, May 23, 2020 3:59 PM To: WSJT software development Subject: Re: [wsjt-devel] (no subject) Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville mailto:g4...@classdesign.com> > wrote: On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A Hi Bill, try with "Settings->Radio->Handshake->None". 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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] (no subject)
Using /dev/cu.SLAB_USBtoUART the handshake is set to NONE When I tried the Handshake = Hardware I received the same error. Thanks for helping me with this. I know you are very busy with the RC. Since the FTDX101MP is a new radio there doesn't seem to be much info out there. - Bill On Sat, May 23, 2020 at 4:43 PM Bill Somerville wrote: > On 24/05/2020 00:18, Bill wrote: > > When using /dev/cu.SLAB_USBtoUART The error details shows: HamLib Error: > Communication timed out while getting current frequency. > > Hi Bill, > > was that with "Settings->Radio->Handshake->Hardware" or > "Settings->Radio->Handshake->None"? > > 73 > Bill > G4WJS. > ___ > 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] (no subject)
On 24/05/2020 00:18, Bill wrote: When using /dev/cu.SLAB_USBtoUART The error details shows: HamLib Error: Communication timed out while getting current frequency. Hi Bill, was that with "Settings->Radio->Handshake->Hardware" or "Settings->Radio->Handshake->None"? 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Hi Bill, When using /dev/cu.SLAB_USBtoUART1 The error details shows: HamLib Error: Invalid configuration while opening connection to rig. When using /dev/cu.SLAB_USBtoUART The error details shows: HamLib Error: Communication timed out while getting current frequency. Both selections end up with a RED Test Cat. Thanks! On Sat, May 23, 2020 at 4:08 PM Bill Somerville wrote: > On 23/05/2020 23:59, Bill wrote: > > Hi, > > > > Thanks for the quick response. I just tried HandShake = NONE and I > > have the same result - Rig Failure - HamLib Error. > > > >Any other suggestions? > > > > Thanks! > > > > Bill - AK6A > > Hi Bill, > > please include the message shown by pressing the "Show Details ..." > button when you get a Hamlib error. > > Have you tried using the other serial port /dev/cu.SLAB_USBtoUART ? If > not then try it with and without Hardware handshaking. > > 73 > Bill > G4WJS. > > > > ___ > 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] (no subject)
On 23/05/2020 23:59, Bill wrote: Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A Hi Bill, please include the message shown by pressing the "Show Details ..." button when you get a Hamlib error. Have you tried using the other serial port /dev/cu.SLAB_USBtoUART ? If not then try it with and without Hardware handshaking. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Hi, Thanks for the quick response. I just tried HandShake = NONE and I have the same result - Rig Failure - HamLib Error. Any other suggestions? Thanks! Bill - AK6A On Sat, May 23, 2020 at 3:32 PM Bill Somerville wrote: > On 23/05/2020 23:16, Bill wrote: > > I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m > able to get the receive Audio Codec to work properly and I can see decodes > but I get a “Rig Failure - Hamlib Error - Invalid configuration while > opening connection to rig” whenever I do a Test CAT. I am unable to get > WSJT-X to establish control communications with the radio. I’ve seen online > suggestions that say use the HamLib FT-991 selection. I am using the > regular WSJT-X version 2.1.2. I am also just using a USB cable from the > radio to the Mac which is running High Sierra. I am using the following > settings: > > > WSJT-X > > > RADIO TAB > > > Rig: Yaesu FT-991 > > > Serial Port: /dev/cu.SLAB_USBtoUART1 > > Note: Installed latest Silicon Labs Drivers - Also Available selections: > > /dev/tty.SLAB_USBtoUART1 > > /dev/cu.SLAB_USBtoUART > > /dev/tty.SLAB_USBtoUART > > > Baud Rate: 38400 > > Polling Interval: 1S > > Data Bits: Eight > > Stop Bits: Two > > Handshake: Hardware > > Force Control Lines: Both Empty > > > PTT Method: CAT > > Mode: None > > Split: Rig > > > AUDIO Tab > > > Input - USB AUDIO CODEC > Output - USB AUDIO CODEC > > FTDX101MP Menu > > > FUNC --> Operation Settings > General > 232C RATE - 38400 > CAT RATE - 38400 > > FUNC --> RADIO SETTINGS > MODE SSB > SSB MOD SOURCE - REAR > REAR SELECT - USB > RPORT GAIN - 10 > DATA MODE SOURCE - REAR (This is the default) > REAR SELECT - USB > DATA OUT LEVEL - 10 > RPORT GAIN - 10 > > RADIO MAIN PANEL & DISPLAY > > > > R.FIL - 3kHz > WIDTH - 4000Hz > > > APPLE COMPUTER > > > USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz > USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz > > > > > Any ideas what might be the issue in getting this going? Has anyone else > been able to get a FTDX-101MP working with WSJT-X? Do I need to install a > newer version of HamLib for this new radio? > > > Thanks! > > > Bill - AK6A > > Hi Bill, > > try with "Settings->Radio->Handshake->None". > > 73 > Bill > G4WJS. > ___ > 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] (no subject)
On 23/05/2020 23:16, Bill wrote: I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A Hi Bill, try with "Settings->Radio->Handshake->None". 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m able to get the receive Audio Codec to work properly and I can see decodes but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to establish control communications with the radio. I’ve seen online suggestions that say use the HamLib FT-991 selection. I am using the regular WSJT-X version 2.1.2. I am also just using a USB cable from the radio to the Mac which is running High Sierra. I am using the following settings: WSJT-X RADIO TAB Rig: Yaesu FT-991 Serial Port: /dev/cu.SLAB_USBtoUART1 Note: Installed latest Silicon Labs Drivers - Also Available selections: /dev/tty.SLAB_USBtoUART1 /dev/cu.SLAB_USBtoUART /dev/tty.SLAB_USBtoUART Baud Rate: 38400 Polling Interval: 1S Data Bits: Eight Stop Bits: Two Handshake: Hardware Force Control Lines: Both Empty PTT Method: CAT Mode: None Split: Rig AUDIO Tab Input - USB AUDIO CODEC Output - USB AUDIO CODEC FTDX101MP Menu FUNC --> Operation Settings General 232C RATE - 38400 CAT RATE - 38400 FUNC --> RADIO SETTINGS MODE SSB SSB MOD SOURCE - REAR REAR SELECT - USB RPORT GAIN - 10 DATA MODE SOURCE - REAR (This is the default) REAR SELECT - USB DATA OUT LEVEL - 10 RPORT GAIN - 10 RADIO MAIN PANEL & DISPLAY R.FIL - 3kHz WIDTH - 4000Hz APPLE COMPUTER USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz Any ideas what might be the issue in getting this going? Has anyone else been able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer version of HamLib for this new radio? Thanks! Bill - AK6A ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
Sent from Yahoo Mail on Android___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
hi all, I did mention this briefly a few days ago. - The build platform is suse leap 15 - issue is active with wsjtx-2.01/linux (someone else built it for suse) - issue is active with wsjtx-2.1.0rc5/linux (built myself) - no issue with both versions in windows 10 pro I believe it might be a SUSE issue but I am a bit in the dark where to start it. there is NO change at all in the configuration. all same cables etc. It happens with the IC7300, as well as the IC9700. RX goes fine with ft8, wspr etc, to the moment where a TX cycle is started. TX goes fine but after switching back, the RX codec is not see and the default built-in mic is used. (Even then, if theh volume's up a bit I do have a working FT8 and WSPR but ) It does not happen when I use the same setup with windows 10. It looks like the RX path to the codec is lost after every TX. If I keep the setup in RX, it stays working. If I go into the audio config I still see the audio codec selected. Most of the time, switching between internal devices by hand and back to the USB codec path, it works agan ... until a TX cycle is started. Note -- it is NOT related to RF to cabling etc. The exact setup without moving cables work just fine under windows. It also happens on a dummy load and with power set to 0% (which is approx 100 mW on 23 or so) So if someone could hint me where to look at for a start? I do see logs like: warn:2019-04-27T20:42:05.790306+02:00 taplop pulseaudio[3306]: [alsa-sink-USB Audio] alsa-util.c: Got POLLNVAL from ALSA warn:2019-04-27T20:42:05.790776+02:00 taplop pulseaudio[3306]: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device warn:2019-04-27T20:42:05.810980+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:05.812022+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:05.812287+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:09.883886+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:24.085620+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:24.085909+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:42:24.086199+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:43:04.281827+02:00 taplop plasmashell[3268]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T20:50:49.397231+02:00 taplop systemd-udevd[767]: Process '/usr/sbin/alsactl restore 1' failed with exit code 99. warn:2019-04-27T20:50:49.397239+02:00 taplop systemd-udevd[770]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99. warn:2019-04-27T23:11:26.805523+02:00 taplop plasmashell[3471]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T23:11:26.806186+02:00 taplop plasmashell[3471]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T23:11:26.806494+02:00 taplop plasmashell[3471]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-27T23:11:36.433418+02:00 taplop plasmashell[3471]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-28T15:12:29.384527+02:00 taplop systemd-udevd[664]: Process '/usr/sbin/alsactl restore 0' failed with exit code 99. warn:2019-04-28T15:12:29.384537+02:00 taplop systemd-udevd[703]: Process '/usr/sbin/alsactl restore 1' failed with exit code 99. warn:2019-04-30T20:12:02.933894+02:00 taplop plasmashell[3359]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-04-30T20:12:02.934406+02:00 taplop plasmashell[3359]: message repeated 2 times: [ org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo"] warn:2019-04-30T20:12:02.934664+02:00 taplop plasmashell[3359]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" warn:2019-05-03T06:26:11.976851+02:00
[wsjt-devel] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
BTW, Sorry to everyone for posting this message with no subject line. I'm not sure how to fix it. I'm sure everyone is getting spam alerts on this post like I am. On Sat, Mar 2, 2019 at 8:34 AM Bill wrote: > Hi Larry, > > That is possible. It's hard to know what he is actually seeing on his > side. I do know that he is usually very strong here in Oregon and my > reports back are usually in the +05 range so I should have enough signal > there to power through some QRM. It would be nice though if people would > look for a clear frequency before calling. The bands are getting a lot more > crowded and QRM is really becoming an issue. > > Bill - AK6A > > On Sat, Mar 2, 2019 at 8:04 AM Larry Banks > wrote: > >> They came back to me with a signal report three times, but then someone >> else in FN42 jumped on top of my frequency with more power and the Q never >> could complete. This may be what is happening to you. Lots of hams >> calling, and not necessarily looking for an open frequency. >> >> 73 -- Larry -- W1DYJ >> >> >> *From:* Bill >> *Sent:* Saturday, March 02, 2019 9:07 >> *To:* WSJT software development >> *Subject:* [wsjt-devel] (no subject) >> >> Is anyone else have issues working T31EU on FT8? He responses back to me >> when I call with very good signal reports but the QSO never finishes (All I >> get is my signal report and not an acknowledgment). This happens on >> multiple tries. I've tried both normal FT8 mode and also Fox Hound but no >> luck Sometimes it appears that he is sending Fox Hound responses (multiple >> calls on one line) and at other times it seems like standard FT8 contacts. >> He is transmitting on at least two frequencies so it seems like it should >> be Fox Hound. Any ideas what he is doing? >> >> I have been able to make valid QSOs with him using normal FT8 mode on a >> few bands but more often than not it gets stuck with my signal report and >> that's all. Is he using a WSJT-X variant of some sort or maybe equipment >> issues? >> >> Thanks! >> >> Bill - AK6A >> >> -- >> >> -- >> ___ >> 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] (no subject)
Hi Larry, That is possible. It's hard to know what he is actually seeing on his side. I do know that he is usually very strong here in Oregon and my reports back are usually in the +05 range so I should have enough signal there to power through some QRM. It would be nice though if people would look for a clear frequency before calling. The bands are getting a lot more crowded and QRM is really becoming an issue. Bill - AK6A On Sat, Mar 2, 2019 at 8:04 AM Larry Banks wrote: > They came back to me with a signal report three times, but then someone > else in FN42 jumped on top of my frequency with more power and the Q never > could complete. This may be what is happening to you. Lots of hams > calling, and not necessarily looking for an open frequency. > > 73 -- Larry -- W1DYJ > > > *From:* Bill > *Sent:* Saturday, March 02, 2019 9:07 > *To:* WSJT software development > *Subject:* [wsjt-devel] (no subject) > > Is anyone else have issues working T31EU on FT8? He responses back to me > when I call with very good signal reports but the QSO never finishes (All I > get is my signal report and not an acknowledgment). This happens on > multiple tries. I've tried both normal FT8 mode and also Fox Hound but no > luck Sometimes it appears that he is sending Fox Hound responses (multiple > calls on one line) and at other times it seems like standard FT8 contacts. > He is transmitting on at least two frequencies so it seems like it should > be Fox Hound. Any ideas what he is doing? > > I have been able to make valid QSOs with him using normal FT8 mode on a > few bands but more often than not it gets stuck with my signal report and > that's all. Is he using a WSJT-X variant of some sort or maybe equipment > issues? > > Thanks! > > Bill - AK6A > > -- > > -- > ___ > 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] (no subject)
They came back to me with a signal report three times, but then someone else in FN42 jumped on top of my frequency with more power and the Q never could complete. This may be what is happening to you. Lots of hams calling, and not necessarily looking for an open frequency. 73 -- Larry -- W1DYJ From: Bill Sent: Saturday, March 02, 2019 9:07 To: WSJT software development Subject: [wsjt-devel] (no subject) Is anyone else have issues working T31EU on FT8? He responses back to me when I call with very good signal reports but the QSO never finishes (All I get is my signal report and not an acknowledgment). This happens on multiple tries. I've tried both normal FT8 mode and also Fox Hound but no luck Sometimes it appears that he is sending Fox Hound responses (multiple calls on one line) and at other times it seems like standard FT8 contacts. He is transmitting on at least two frequencies so it seems like it should be Fox Hound. Any ideas what he is doing? I have been able to make valid QSOs with him using normal FT8 mode on a few bands but more often than not it gets stuck with my signal report and that's all. Is he using a WSJT-X variant of some sort or maybe equipment issues? Thanks! Bill - AK6A ___ 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] (no subject)
Is anyone else have issues working T31EU on FT8? He responses back to me when I call with very good signal reports but the QSO never finishes (All I get is my signal report and not an acknowledgment). This happens on multiple tries. I've tried both normal FT8 mode and also Fox Hound but no luck. Sometimes it appears that he is sending Fox Hound responses (multiple calls on one line) and at other times it seems like standard FT8 contacts. He is transmitting on at least two frequencies so it seems like it should be Fox Hound. Any ideas what he is doing? I have been able to make valid QSOs with him using normal FT8 mode on a few bands but more often than not it gets stuck with my signal report and that's all. Is he using a WSJT-X variant of some sort or maybe equipment issues? Thanks! Bill - AK6A ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
VK2/G3NJV. Paul, In addition to being active using WSJT-X v2.0.0 784f75 , I also run a Redpitaya to decode FT8 stations and feed the FT8 RBN as well as PSK reporter. My spot of you may also have been from the RP receiver/decoder. 73, Rich - K1HTV = = = From: Paul Randall To: "wsjt-devel@lists.sourceforge.net" Cc: Bcc: Date: Thu, 24 Jan 2019 01:50:04 +0000 Subject: [wsjt-devel] WSJT Reporting to PSK Reporter Hi, I got this address from the WSJT website. I am new to this group and not sure of the protocols. I tried emailing yesterday but am unsure if this was received. I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of my transmissions almost disappeared from PSK Reporter. I now get just a handful of reports all from stations NOT using WSJT. Most of these come from stations using “Red Pitaya FT8 TRX 1.0”. I spoke to Philip Gladstone about this and he told me that WSJT does not send reception reports to PSK Reporter unless it receives callsign and locator in a single message. It is impossible for me to transmit a message like this. Because I have a type B callsign, all that will fit in a single message is “CQ VK2/G3NJV” This seems a particularly harsh outcome for type B callsign holders upgrading to v2.0.0. who, like me, are often operating portable stations with makeshift antennas where reception reports are extremely valuable. The reports from stations using a Red Pitaya are perfectly acceptable and I’m not sure of the reasoning behind the current WSJT “callsign + QRA” rule. Would it be possible to modify this to allow reception reports for type B callsigns received without a QRA? Many thanks for your attention. Paul Randall G3NJV PS After completing this email I checked the PSK Reporter website again. Sure enough there were just 5 reception reports, four from monitors using Red Pitaya but also a single report from K1HTV using WSJT-X v2.0.0 784f75. This is the only WSJT reception report seen since 10 December so now I’m not sure what is going on! ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
On 17/12/2018 12:12, Unni Tharakkal wrote: 120815 -19 0.4 1739 ~ _<...>_ TA5/ON6ZG RRR What is the meaning of the highlighted text and acallsign iside the <> Unni VU2TE Hi Unni, you will find the answer here in the WSJT-X User Guide: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0.html#COMP-CALL 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
120815 -19 0.4 1739 ~ *<...>* TA5/ON6ZG RRR What is the meaning of the highlighted text and acallsign iside the <> Unni VU2TE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Unfortunately no, it's an export software encryption issue On Thu, Nov 29, 2018, 8:48 PM Gary McDuffie > > > On Nov 29, 2018, at 14:45, Bill Somerville > wrote: > > > > that install location is fine. Later on in the installer you will be > prompted if you want to install the libraries into the Windows System > directory as well which is defaulted to yes and to the correct location for > your system. > > I am assuming that this problem will go away on its own when the GA is > released? > > Gary - AG0N > > ___ > 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] (no subject)
Steve, you didn't give what Windows version you're using. I loaded it on Win8.1 with the defaults, and had no issues. Evidently the installer adds a system path variable or the like, as I didn't change the default install location and it works fine. Neil, KN3ILZ On 11/29/2018 4:36 PM, Steve Sacco wrote: Quick Start for 2.0 says: image.png Item #1: the direct download link does not function. After downloading the exe, I attempted to install, and notice that it is not defaulting to "the Windows system directory": image.png Where should it be installed? Windows\System32? Thanks/73, Steve NN4X --- This email has been checked for viruses by AVG. https://www.avg.com ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
On 29/11/2018 21:36, Steve Sacco wrote: After downloading the exe, I attempted to install, and notice that it is not defaulting to "the Windows system directory": Hi Steve, that install location is fine. Later on in the installer you will be prompted if you want to install the libraries into the Windows System directory as well which is defaulted to yes and to the correct location for your system. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
John and all who are discussing the contest dupe issue. Here is my solution which I think is great. I run my logging program on the screen all the time. When a contact is logged in WSJT-X, it automatically gets sent to my log and shows up on the screen. (Then it is easy for me to make any adjustments or notes about the contact that I would like to make. For example, I like to keep the propagation mode in my log.) So anyway my log is always up to date. Now, whenever a new call appears in the To Radio filed in WSJT-X, it is also sent to my logging program. The log then searches that call and pops up a box showing every contact I have ever made with that station, date, time, grid, country. So I can immediately see if it is a dupe for the current contest, if I need him on another band, if he is in a new grid, etc. So I double click on the call, it shows up in the To field, and my logger shows all the info. Very easy. My logging program is one I wrote years ago and not available for others, but I am sure something similar could be done with other programs. You might have to convince the program author to include the features, but implementation is really easy. 73, Russ K2TXB From: John Harper Sent: Thursday, November 29, 2018 1:15 PM To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] (no subject) Yes, I did. After a dozen or so contacts (many from the same call area) it became hard to remember who I'd worked and therefore difficult to see an in-progress QSO about to end and know whether I should call the station or not rather than waiting for him to call CQ again. Color coding in a future version would add much to the feasibility of using FT8 in a major contest like CQ-WPX, Field Day and others. Without it, such contests will contain logs with many dupes. Everything worked well and as expected as I took turns between calling CQ and S V20. -rc5, Windows 10 laptop Apache Anan-10e, amp, 40 watts, dipole up 110ft 73, John AE5X https://ae5x.blogspot.com >I wonder if anyone has reverted to the old fashioned dupe sheet >techniques using a pen and paper? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
Quick Start for 2.0 says: [image: image.png] Item #1: the direct download link does not function. After downloading the exe, I attempted to install, and notice that it is not defaulting to "the Windows system directory": [image: image.png] Where should it be installed? Windows\System32? Thanks/73, Steve NN4X ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
Yes, I did. After a dozen or so contacts (many from the same call area) it became hard to remember who I'd worked and therefore difficult to see an in-progress QSO about to end and know whether I should call the station or not rather than waiting for him to call CQ again. Color coding in a future version would add much to the feasibility of using FT8 in a major contest like CQ-WPX, Field Day and others. Without it, such contests will contain logs with many dupes. Everything worked well and as expected as I took turns between calling CQ and S V20. -rc5, Windows 10 laptop Apache Anan-10e, amp, 40 watts, dipole up 110ft 73, John AE5X https://ae5x.blogspot.com >I wonder if anyone has reverted to the old fashioned dupe sheet >techniques using a pen and paper? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Can someone please block this user? This is the 5th blank note from this person. > On Sep 25, 2018, at 6:25 AM, Анатолий wrote: > > ___ > 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] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Please stop sending empty messages to the dev list. > On Sep 23, 2018, at 11:15 AM, Анатолий wrote: > > ___ > 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] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
unscribe Windows メール から送信-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
-- 123 54-- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
Hi Franco, I'm not sure I understand what the question is. build-wsjtx rinstall simply builds the development branch for testing. For additional build options, in JTSDK-QT, use: help-wsjtx 73's Greg, KI7MT On 7/5/2016 15:17, bag...@libero.it wrote: > Goodmorning everyone > > > To all the members of the Group and special recognition from me > to all developers of the WSJT-X system > > > Question using JTSDK-QT perscaricare there is an option a > special version > > > > In place of the classic "build-wsjtx rinstall" > > > Tried in various documents found nothing > > > I apologize for your time and for the silly question > > > 73 Franco > -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] (no subject)
Goodmorning everyone To all the members of the Group and special recognition from me to all developers of the WSJT-X system Question using JTSDK-QT perscaricare there is an option a special version In place of the classic "build-wsjtx rinstall" Tried in various documents found nothing I apologize for your time and for the silly question 73 Franco-- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] (no subject)
On 12/04/2014 07:33, Claude Frantz wrote:
Hi Claude,
On 04/11/2014 07:40 PM, Greg Beam wrote:
Hamlib 3 is not part of my current Linux distribution. I have compiled
and installed it separately.
There some changes that are newer even than the Hamlib 3 main
repository, currently they are in my fork of Hamlib. They have been
submitted upstream to the Hamlib team but at the moment Nate N0NB (the
Hamlib integrator) is moving QTH so has higher priorities.
You can get the sources from my fork by:
git clone git://git.code.sf.net/u/bsomervi/hamlib u-bsomervi-hamlib
cd u-bsomervi-hamlib
git checkout integration
The integration branch has my very latest tested changes awaiting
acceptance upstream.
To build Hamlib on Windows you will need the full MinGW install, the one
bundled with Qt is only really suitable for building Qt projects and
doesn't contain the GNU tools needed for an autotools project like Hamlib.
You can build it as per Hamlib 3 with:
mkdir ~/build/hamlib
cd ~/build/hamlib
~/src/u-somervi-hamlib/autogen.sh --prefix ~/local/hamlib --disable-shared
make make install
What is the recommended method to tell Cmake to use this Hamlib 3
include and dynamic modules ?
If you have pkc-config installed then CMake will correctly identify the
Hamlib version and link it statically. On Windows you can get a cut down
binary pkg-config (the full package is difficult to install on Windows)
from https://sourceforge.net/projects/pkgconfiglite/files/ which works
just fine.
Tell CMake about the Hamlib location by adding it to CMAKE_PREFIX_PATH,
for example if you have the Qt5 package installed at .../Qt/5.2.1/ then
on Windows with the Qt5 MinGW tools set up (mingw48_32):
You will probably find it easier to set up a CMake toolchain file for
compiler and other tool chain location, I use:
#
# the name of the target operating system
set (CMAKE_SYSTEM_NAME Windows)
set (QTDIR C:/Tools/Qt/5.2.1)
set (FFTWDIR C:/Tools/fftw-3.3.3-dll32-2)
set (HAMLIBDIR C:/test-install/hamlib/mingw32)
# where to find required packages
set (CMAKE_PREFIX_PATH ${QTDIR}/mingw48_32 ${FFTWDIR} ${HAMLIBDIR}
${HAMLIBDIR}/bin)
# here is the target environment located
set (CMAKE_FIND_ROOT_PATH ${QTDIR}/mingw48_32)
# adjust the default behaviour of the FIND_XXX() commands:
# search headers and libraries in the target environment, search
# programs in the host environment
set (CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set (CMAKE_FIND_ROOT_PATH_MODE_LIBRARY BOTH)
set (CMAKE_FIND_ROOT_PATH_MODE_INCLUDE BOTH)
#--
Then:
mkdir %HOMEPATH%\build\wsjtx\Release
cd build\wsjtx\Release
cmake -D CMAKE_TOOLCHAIN_FILE=%HOMEPATH%/MinGW-Qt-ToolChain.cmake ^
-D CMAKE_INSTALL_PREFIX=%HOMEPATH%/local/wsjtx ^
-D CMAKE_BUILD_TYPE=Release ^
%HOMEPATH%/src/wsjtx
Then build with:
cmake --build %HOMEPATH%/build/wsjtx/Release --target install -- -kj
That should leave a fully working WSJT-X in %HOMEPATH%\local\wsjtx\bin .
On Linux things are a bit simpler and a toolchain file isn't required;
so with commands something like:
cd ~/src
git clone git://git.code.sf.net/u/bsomervi/hamlib u-bsomervi-hamlib
cd u-bsomervi-hamlib
git checkout integration
mkdir ~/build/hamlib
cd ~/build/hamlib
~/src/u-bsomervi-hamlib/autogen --prefix ~/local/hamlib --disable-shared
make make install
mkdir -p ~/build/wsjtx/Release
cd ~/build/wsjtx/Release
cmake -D CMAKE_PREFIX_PATH=~/Qt/5.2.1/gcc_64\;~/local/hamlib \
-D CMAKE_INSTALL_PREFIX=~/local/wsjtx \
-D CMAKE_BUILD_TYPE=Release \
~/src/wsjtx
cmake --build ~/build/wsjtx/Release --target install -- -kj
~/local/wsjtx/Release/bin/wsjtx
Thanks a lot !
Best 88 de Claude
Any questions, don't hesitate to ask.
73
Bill
G4WJS.
The Makefile.linux build method has not worked since 3942 or 2842 cant
remember which. You need to build it with CMake and you Hamlib3 also.
I just built r4011 on Ubuntu 14.04 Beta2. I have it monitoring on 10m
this afternoon. All seems ok,
73's
Greg, KI7MT
On 04/09/2014 11:31 PM, Waldek SPdwaONG wrote:
Hi,
I have download latest version WSJT-X r4005 from svn adn I have try
compile on my UBUNTU 13.04 but I have problem follow:
when I have try compile:
cd lib/
make -f Makefile.linux
.
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously
Re: [wsjt-devel] (no subject)
Hi Bill,
Ok got it.
I'm using a native install of 14.04 so the VM issue not a problem. I'm
also using /proc/cpuinfo to get the core count so should be ok.
73's
Greg, KI7MT
On 04/12/2014 12:44 PM, Bill Somerville wrote:
On 12/04/2014 19:36, Greg Beam wrote:
HI Bill,
Hi Greg,
Thanks. I'm putting everything in /opt for testing and the installer
makes that easy.
I forgot to ask about one other thing. I can't find the documentation on
one of the flags your using:
-- cmake --build ~/build/wsjtx/Release --target install -- -kj
the ( -- -kj ) Is that the same as say, make -j5 on quad core box?
everything after -- is passed to the underlying make tool.
-k means keep going after errors, I run builds using the emacs compile
command and prefer all the errors in the compilation buffer at once.
-j is use multiple parallel command invocations where possible, the
number of parallel processes is determined by make if you don't pass a
number. I'm not sure it is related to the available core count, it seems
to be unlimited but that's no so bad since compiles are usually i/o
bound rather than CPU bound so they tend to wait anyway.
There is one gotcha I've found with '-j' on virtual machines, it seems
to be able to spawn more parallel processes than the vm can handle, so
in that case I use '-jn' where n is a couple more that the number of
cores assigned to that VM.
73's
Greg, KI7MT
73
Bill
G4WJS.
On 04/12/2014 12:24 PM, Bill Somerville wrote:
On 12/04/2014 19:19, Greg Beam wrote:
Hi Bill,
Hi Greg,
Quick Question. Did you install QT5 from the Linux open source installer ?
I use the open source installer for a vanilla install on all platforms.
If 5.2.x is in a distribution repository then that is probably the best
option as it will be picked up without having to specify
CMAKE_INSTALL_PREFIX. Having said that I haven't tested that because I
don't have a machine with 5.2.x available in the relevant repo.
I used the repo packages, but I think the installer method may be a
better way to go in the long run.
73's
Greg, KI7MT
73
Bill
G4WJS.
On 04/12/2014 03:29 AM, Bill Somerville wrote:
On 12/04/2014 07:33, Claude Frantz wrote:
Hi Claude,
On 04/11/2014 07:40 PM, Greg Beam wrote:
Hamlib 3 is not part of my current Linux distribution. I have compiled
and installed it separately.
There some changes that are newer even than the Hamlib 3 main
repository, currently they are in my fork of Hamlib. They have been
submitted upstream to the Hamlib team but at the moment Nate N0NB (the
Hamlib integrator) is moving QTH so has higher priorities.
You can get the sources from my fork by:
git clone git://git.code.sf.net/u/bsomervi/hamlib u-bsomervi-hamlib
cd u-bsomervi-hamlib
git checkout integration
The integration branch has my very latest tested changes awaiting
acceptance upstream.
To build Hamlib on Windows you will need the full MinGW install, the one
bundled with Qt is only really suitable for building Qt projects and
doesn't contain the GNU tools needed for an autotools project like Hamlib.
You can build it as per Hamlib 3 with:
mkdir ~/build/hamlib
cd ~/build/hamlib
~/src/u-somervi-hamlib/autogen.sh --prefix ~/local/hamlib --disable-shared
make make install
What is the recommended method to tell Cmake to use this Hamlib 3
include and dynamic modules ?
If you have pkc-config installed then CMake will correctly identify the
Hamlib version and link it statically. On Windows you can get a cut down
binary pkg-config (the full package is difficult to install on Windows)
from https://sourceforge.net/projects/pkgconfiglite/files/ which works
just fine.
Tell CMake about the Hamlib location by adding it to CMAKE_PREFIX_PATH,
for example if you have the Qt5 package installed at .../Qt/5.2.1/ then
on Windows with the Qt5 MinGW tools set up (mingw48_32):
You will probably find it easier to set up a CMake toolchain file for
compiler and other tool chain location, I use:
#
# the name of the target operating system
set (CMAKE_SYSTEM_NAME Windows)
set (QTDIR C:/Tools/Qt/5.2.1)
set (FFTWDIR C:/Tools/fftw-3.3.3-dll32-2)
set (HAMLIBDIR C:/test-install/hamlib/mingw32)
# where to find required packages
set (CMAKE_PREFIX_PATH ${QTDIR}/mingw48_32 ${FFTWDIR} ${HAMLIBDIR}
${HAMLIBDIR}/bin)
# here is the target environment located
set (CMAKE_FIND_ROOT_PATH ${QTDIR}/mingw48_32)
# adjust the default behaviour of the FIND_XXX() commands:
# search headers and libraries in the target environment, search
# programs in the host environment
set (CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set (CMAKE_FIND_ROOT_PATH_MODE_LIBRARY BOTH)
set (CMAKE_FIND_ROOT_PATH_MODE_INCLUDE BOTH)
#--
Then:
mkdir %HOMEPATH%\build\wsjtx\Release
cd build\wsjtx\Release
cmake -D
