You can subscribe to this list here.
2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(11) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Doug B. Sr. <dou...@gm...> - 2025-02-07 13:50:30
|
Thanks. The meter on Flrig itself. I assume it should be flashing some green with even noise? That brings up another thing, Flrig's sliders are there but grayed out. Any idea what that means? On Fri, Feb 7, 2025 at 8:45 AM Black Michael <mdb...@ya...> wrote: > Which signal meter are you referring to? The IC706 or FLRig's? > > Check the RF gain on FLRig. Should be the 2nd slider from the top. > > Mike W9MDB > > > > > On Friday, February 7, 2025 at 06:31:12 AM CST, Doug Breault, Sr. via > wsjt-devel <wsj...@li...> wrote: > > > Hello All, > > This might be a super dumb idea but just wanted to throw it out there: > > I was able to get my Linux Mint -> Digirig -> Icom 706 MkIIG working > perfectly with WSJTX, however, I can't for the life of me get it fully > working w/ Flrig. In Flrig, frequency control is working, Tx is going on > (and even off) w/ the PTT button, but now I'm noticing the signal meter has > nothing on it, like somehow it's not hearing signal. (using Flrig 2.0.0.4) > > This might not even be apples-to-apples or politically possible, but it > would be cool if WSJT-X could expose a settings file, and Flrig could read > it, fire up, and just work. > > Thanks, > 73 Doug KC1UUH > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
From: Black M. <mdb...@ya...> - 2025-02-07 13:46:58
|
I should also note that WSJT-X can use FLRig too so test that configuration. Mike W9MDB On Friday, February 7, 2025 at 07:45:38 AM CST, Black Michael <mdb...@ya...> wrote: Which signal meter are you referring to? The IC706 or FLRig's? Check the RF gain on FLRig. Should be the 2nd slider from the top. Mike W9MDB On Friday, February 7, 2025 at 06:31:12 AM CST, Doug Breault, Sr. via wsjt-devel <wsj...@li...> wrote: Hello All, This might be a super dumb idea but just wanted to throw it out there: I was able to get my Linux Mint -> Digirig -> Icom 706 MkIIG working perfectly with WSJTX, however, I can't for the life of me get it fully working w/ Flrig. In Flrig, frequency control is working, Tx is going on (and even off) w/ the PTT button, but now I'm noticing the signal meter has nothing on it, like somehow it's not hearing signal. (using Flrig 2.0.0.4) This might not even be apples-to-apples or politically possible, but it would be cool if WSJT-X could expose a settings file, and Flrig could read it, fire up, and just work. Thanks,73 Doug KC1UUH _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Black M. <mdb...@ya...> - 2025-02-07 13:45:55
|
Which signal meter are you referring to? The IC706 or FLRig's? Check the RF gain on FLRig. Should be the 2nd slider from the top. Mike W9MDB On Friday, February 7, 2025 at 06:31:12 AM CST, Doug Breault, Sr. via wsjt-devel <wsj...@li...> wrote: Hello All, This might be a super dumb idea but just wanted to throw it out there: I was able to get my Linux Mint -> Digirig -> Icom 706 MkIIG working perfectly with WSJTX, however, I can't for the life of me get it fully working w/ Flrig. In Flrig, frequency control is working, Tx is going on (and even off) w/ the PTT button, but now I'm noticing the signal meter has nothing on it, like somehow it's not hearing signal. (using Flrig 2.0.0.4) This might not even be apples-to-apples or politically possible, but it would be cool if WSJT-X could expose a settings file, and Flrig could read it, fire up, and just work. Thanks,73 Doug KC1UUH _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Doug B. Sr. <dou...@gm...> - 2025-02-07 12:28:20
|
Hello All, This might be a super dumb idea but just wanted to throw it out there: I was able to get my Linux Mint -> Digirig -> Icom 706 MkIIG working perfectly with WSJTX, however, I can't for the life of me get it fully working w/ Flrig. In Flrig, frequency control is working, Tx is going on (and even off) w/ the PTT button, but now I'm noticing the signal meter has nothing on it, like somehow it's not hearing signal. (using Flrig 2.0.0.4) This might not even be apples-to-apples or politically possible, but it would be cool if WSJT-X could expose a settings file, and Flrig could read it, fire up, and just work. Thanks, 73 Doug KC1UUH |
From: Charles S. <g3...@gm...> - 2025-02-06 05:56:55
|
Hi Lance Yes, that's the figure in the User Guide. 73 Charlie DL3WDG On Thu, 6 Feb 2025 at 06:27, Lance Collister via wsjt-devel < wsj...@li...> wrote: > I need to provide this information for a new 6m EME DXpedition license. > Does anyone > know what this value is? I think it is 1.67 bits/second, but I am not > sure... > > MNI TNX and VY 73, Lance > > -- > Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, > 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, > S79GJ, FO/W7GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ) > P.O. Box 73 > Frenchtown, MT 59834-0073 > USA > TEL: (406) 626-5728 > QTH: DN27ub > URL: http://www.bigskyspaces.com/w7gj > Skype: lanceW7GJ > 2m DXCC #11 - 6m DXCC #815 - FFMA #7 > > Interested in 6m EME? Ask me about subscribing to the Magic Band EME > email group, or just fill in the request box at the bottom of my web > page (above)! > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
From: Lance C. <w7...@ho...> - 2025-02-06 05:20:01
|
I need to provide this information for a new 6m EME DXpedition license. Does anyone know what this value is? I think it is 1.67 bits/second, but I am not sure... MNI TNX and VY 73, Lance -- Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, FO/W7GJ, TX7MB, TO7GJ, 3B9GJ, ZD9GJ) P.O. Box 73 Frenchtown, MT 59834-0073 USA TEL: (406) 626-5728 QTH: DN27ub URL: http://www.bigskyspaces.com/w7gj Skype: lanceW7GJ 2m DXCC #11 - 6m DXCC #815 - FFMA #7 Interested in 6m EME? Ask me about subscribing to the Magic Band EME email group, or just fill in the request box at the bottom of my web page (above)! |
From: Reino T. <rei...@ko...> - 2025-02-04 06:48:41
|
> Neil Smith, Tuesday, February 4, 2025 4:24 AM wrote: > You will need to run the two decoders in parallel using virtual audio cable to prove whether one program is better than the other. Hi, for reception you do not need a virtual cable at all. At least in Windows just select the same USB Codec for both or multiple instances of wsjt-x or other programs. How to run multiple instances of wsjt-x parallel see user guide 17. Frequently Asked Questions second item. Your may modify the wsjt-x shortcut to e.g. C:\WSJT\wsjtx2.7.0-rc8\bin\wsjtx.exe --rig-name=Test and wsjt-x will prepare a new log directory for you to keep the instances independent. You may try to use a narrower receiver bandwidth to attenuate strong interferences. A narrow filter will provide a better S/N indication, but does not provide a better decoding sensitivity unless e.g. AGC otherwise reduce RF gain too much due to other stations. 73, Reino OH3mA |
From: Neil S. <ne...@g4...> - 2025-02-04 02:45:39
|
Hi Pete, can you hear them well on other modes? What receive antennas are you using on 80? Do you have Beverages or K9AYs or similar aperiodic loops, or e-field probes or something? Do you have a noise blanker enabled? (best disabled) Are you getting desense from loud signals? Can you see their signal clearly in the waterfall? It's fun to try multiple decoder programs in parallel to compare performance, but if you are using the same power as them and have as good a receive system and your PC clock is absolutely accurate, using Meinberg or similar NTP sync, and your rig isn't running AGC or blanking or nose refuction, and the levels are set to about 30 dB on the wsjt-x receive indicator on band noise, and you have no desense and aren't seeing the indicator going up too high, then you should be OK. Do you generally hear as well as folks in your area on 80 metres? You will need to run the two decoders in parallel using virtual audio cable to prove whether one program is better than the other. I've rarely seen any differences, it's almost always time sync, agc, rx audio levels, or the lack of a high performance receive antenna system that wrecks LF digimode performance. Best of luck with your experiments! Neil G4DBN https://youtube.com/MachiningandMicrowaves > On 3 Feb 2025, at 23:03, w1rm--- via wsjt-devel <wsj...@li...> wrote: > > I have a rather odd situation. I am running version rc8. I have been using it to work 9V1YC on 80. A very tough path. What’s interesting is that he hears me as strong as -12 but I don’t hear him at all. I am going to try JTDX which has been reported by some to hear better. > > Are there any tricks or settings that can help? If you have some version in the works with improved sensitivity, I would love to test it. > > |
From: <w1...@co...> - 2025-02-03 22:59:26
|
I have a rather odd situation. I am running version rc8. I have been using it to work 9V1YC on 80. A very tough path. What's interesting is that he hears me as strong as -12 but I don't hear him at all. I am going to try JTDX which has been reported by some to hear better. Are there any tricks or settings that can help? If you have some version in the works with improved sensitivity, I would love to test it. Thanks Pete Chamalian, W1RM W1...@Co... |
From: Jim S. <ji...@gm...> - 2025-02-02 19:07:21
|
On Sat, 1 Feb 2025 18:29:20 +0000 (UTC) Black Michael via wsjt-devel <wsj...@li...> wrote: > The 7300 has a USB B 2.0 FemaleYou also have to supply power to it from the cable. I don't have one of these radios but this has me wondering now. Is this a bug or a feature? Why would Icom do this? Self powered USB devices are part of the USB spec. There does not necessarily need to be a power connection from the host. Maybe some enterprising soul could void his warranty and see if the rig can be modified for self powered USB. -- 73 -Jim NU0C |
From: Sam W. <w2...@ao...> - 2025-02-01 19:53:12
|
Hi All, Does anyone here know the required Hex address for the new 6200? Thanks for any help. 73, Sam W2JDB |
From: Black M. <mdb...@ya...> - 2025-02-01 18:29:37
|
The 7300 has a USB B 2.0 FemaleYou also have to supply power to it from the cable.So that's why a hub in the middle is necessary.And the optical has USB B 3.0 Male along with the hub having USB B 3.0 Female and the hub supplies power as the optical doesn't pass power lines. Mike W9MDB On Saturday, January 25, 2025 at 10:47:51 PM CST, Enrico OE1EQW <oe...@oe...> wrote: Maybe this item can help you: Amazon ASIN B0D3FYJ4MM 73 Enrico OE1EQW Am 25.01.2025 um 22:19 schrieb Black Michael via wsjt-devel: In my current setup there is an IC-7300 that has been unable to transmit even 1W without dropping the USB connection. I have numerous rigs hooked up and lots of USB connections. The 7300 is well known for being RFI sensitive dropping CAT and Audio service. So I bought an optical USB cable, plugged it into a non-powered Startech hub, then ran a triplite cable to the rig. Now able to run full power without any problems. I'll be doing more investigation with a cheaper hub and adding more USB devices to this new hub. But the optical cable has a USB-B on one end and USB-A on the other. So do need a USB hub that takes a USB-B cable. Not a cheap solution but effective. https://www.amazon.com/dp/B01N94D03E https://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8 Mike W9MDB _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Landesleiter ÖVSV LV NÖ |
From: Kevin R. <kr...@ya...> - 2025-01-31 16:21:31
|
Thank you to all who responded to my thread. The first response from Reino nailed it. I renamed the WSJT-X ini file and restarted WSJTX and a default ini file was created and it runs like a Swiss watch now. Thank you again for all of your help and responses. If I hadn't gotten on here for answers I would still be looking for Valium or Xanax KR |
From: Uwe, D. <dg...@gm...> - 2025-01-31 09:52:15
|
Good Morning Helga, I have removed that email address from the list. My sincere condolences! 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 31.01.2025 um 10:15 schrieb Albrecht via wsjt-devel: > > Good morning, > > please don´t send us any more messages, my partner ( husband) Prof. > Dr. Albrecht Mugler sadly past away en september last year. > > Thank you so much. > regards > Helga Barth > > Am 30.01.2025 um 19:09 schrieb Christopher Wawak via wsjt-devel: >> I see this error regularly with OmniRig, Log4OM and WSJTX. All are >> running as a regular user, and this only seems to happen after the >> system has been booted for a while. Sometimes restarting all the apps >> helps, sometimes resetting com ports helps, sometimes rebooting >> helps, sometimes none of these help. This has been going on for at >> least 3 years, and I've never really seen an improvement or found a >> solid way to troubleshoot. >> >> Not much to add, but I wanted to give some moral support. >> >> 73 KC2IEB Chris >> >> On Thu, Jan 30, 2025 at 10:16 AM Kevin R. via wsjt-devel >> <wsj...@li...> wrote: >> >> Resubmission after joining the mailing list >> >> ----- Forwarded Message ----- >> *From:* Kevin R. <kr...@ya...> >> *To:* wsj...@li... >> <wsj...@li...> >> *Sent:* Wednesday, January 29, 2025 at 09:59:33 PM CST >> *Subject:* Omnirig error message >> >> * Program version - WSJT-X v2.6.1 - OmniRig v1.20 >> * Operating system - Windows 10 Pro 64-bit operating system, >> x64-based processor >> * Concise description of the problem >> >> I'm having a MAJOR problem with OmniRig. All of the sudden I get >> this message when opening WSJT-X >> Inline image >> I get the same error message when opening JTDX but OmniRig works >> with Log3OM. >> I have uninstalled and reinstalled both WSJT-X and OmniRig but I >> continue to get the error message. >> >> These are questions from the author of OmniRig - he has not >> responded yet to my answered to his questions. >> OmniRig worked fine with WSJT-X before, and only recently the >> error started to appear? *Correct - I was testing a different >> radio (Yaesu FTDX10) to see if I wanted to buy it. Went back to >> my original settings (Kenwood TS590sg) and the problems started.* >> You did not change any settings in OmniRig, and Log4OM works with >> OmniRig fine even now. Is this correct? *OmniRig connects the >> radio (TS590sg) to Log4OM and the freqs change etc. When opening >> WSJTX either with or without Log4OM, the com error message appears.* >> Also, are you trying to run Wsjtx and Log4om at the same time? - >> *I want to run Log4OM, WSJT-X, JTAlert, and GridTracker at the >> same time - I had it working that way once before but only Log4OM >> is connecting with OmniRig now - I don't think GridTracker >> depends on OmniRig. Without WSJT-X working, JTAlert won't work >> either.* >> What happens of you do not start the logger and run only wsjtx? - >> *Com error message. The same for JTDX.* >> * >> * >> *I have not gotten into ini files to edit or anything like that >> but, I did remove all of the prior OmniRig and downloaded the >> latest v1.20 version plus the latest Rigini and it did not make a >> difference. Device manager shows the proper driver, and the Com >> port is 5 and the baud rate is set at 38400. The port and baud >> rate was part of the original Omnirig settings for the 590. If >> there is something corrupted I cannot figure out where it would >> be. It is puzzling that OmniRig works with Log4OM but not WSJT-X >> or JTDX. I just thought of this and don't know if it has any >> bearing since they don't show up without the radio connected to >> the computer, but I removed the USB drivers for the Yaesu. The >> Yaesu drivers defaulted to different com ports as well. I >> re-entered my USB drivers for the Kenwood just in case, deleted >> and reinstalled WSJT-X and still get the same error message, it >> doesn't work with JTDX either. Can't tell about JT Alert because >> for it to work it has to connect with one of those. I emailed the >> OmniRig guru but haven't heard back. I think that there is a >> hidden file somewhere in the WSJT-X stuff that's messed up >> because when I reinstalled. my data (callsign, QTH, etc.) was >> still there but I still get the error message. >> >> * >> * >> * >> How can I get this fixed? >> THANKS IN ADVANCE >> >> KR >> >> **Kevin RushEmoji ** >> *KR5TX* >> >> *Lubbock, TX >> Ol...@ya... >> *“The things a man has to have are hope and confidence in himself >> against odds, and sometimes he needs somebody, his pal or his >> mother or his wife or God, to give him that confidence. He's got >> to have some inner standards worth fighting for or there won't be >> any way to bring him into conflict. And he must be ready to >> choose death before dishonor without making too much song and >> dance about it. That's all there is to it.” -Clark Gable >> >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> >> -- >> -- Chris >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Albrecht <alb...@t-...> - 2025-01-31 09:16:17
|
Good morning, please don´t send us any more messages, my partner ( husband) Prof. Dr. Albrecht Mugler sadly past away en september last year. Thank you so much. regards Helga Barth Am 30.01.2025 um 19:09 schrieb Christopher Wawak via wsjt-devel: > I see this error regularly with OmniRig, Log4OM and WSJTX. All are > running as a regular user, and this only seems to happen after the > system has been booted for a while. Sometimes restarting all the apps > helps, sometimes resetting com ports helps, sometimes rebooting helps, > sometimes none of these help. This has been going on for at least 3 > years, and I've never really seen an improvement or found a solid way > to troubleshoot. > > Not much to add, but I wanted to give some moral support. > > 73 KC2IEB Chris > > On Thu, Jan 30, 2025 at 10:16 AM Kevin R. via wsjt-devel > <wsj...@li...> wrote: > > Resubmission after joining the mailing list > > ----- Forwarded Message ----- > *From:* Kevin R. <kr...@ya...> > *To:* wsj...@li... > <wsj...@li...> > *Sent:* Wednesday, January 29, 2025 at 09:59:33 PM CST > *Subject:* Omnirig error message > > * Program version - WSJT-X v2.6.1 - OmniRig v1.20 > * Operating system - Windows 10 Pro 64-bit operating system, > x64-based processor > * Concise description of the problem > > I'm having a MAJOR problem with OmniRig. All of the sudden I get > this message when opening WSJT-X > Inline image > I get the same error message when opening JTDX but OmniRig works > with Log3OM. > I have uninstalled and reinstalled both WSJT-X and OmniRig but I > continue to get the error message. > > These are questions from the author of OmniRig - he has not > responded yet to my answered to his questions. > OmniRig worked fine with WSJT-X before, and only recently the > error started to appear? *Correct - I was testing a different > radio (Yaesu FTDX10) to see if I wanted to buy it. Went back to my > original settings (Kenwood TS590sg) and the problems started.* > You did not change any settings in OmniRig, and Log4OM works with > OmniRig fine even now. Is this correct? *OmniRig connects the > radio (TS590sg) to Log4OM and the freqs change etc. When opening > WSJTX either with or without Log4OM, the com error message appears.* > Also, are you trying to run Wsjtx and Log4om at the same time? - > *I want to run Log4OM, WSJT-X, JTAlert, and GridTracker at the > same time - I had it working that way once before but only Log4OM > is connecting with OmniRig now - I don't think GridTracker depends > on OmniRig. Without WSJT-X working, JTAlert won't work either.* > What happens of you do not start the logger and run only wsjtx? - > *Com error message. The same for JTDX.* > * > * > *I have not gotten into ini files to edit or anything like that > but, I did remove all of the prior OmniRig and downloaded the > latest v1.20 version plus the latest Rigini and it did not make a > difference. Device manager shows the proper driver, and the Com > port is 5 and the baud rate is set at 38400. The port and baud > rate was part of the original Omnirig settings for the 590. If > there is something corrupted I cannot figure out where it would > be. It is puzzling that OmniRig works with Log4OM but not WSJT-X > or JTDX. I just thought of this and don't know if it has any > bearing since they don't show up without the radio connected to > the computer, but I removed the USB drivers for the Yaesu. The > Yaesu drivers defaulted to different com ports as well. I > re-entered my USB drivers for the Kenwood just in case, deleted > and reinstalled WSJT-X and still get the same error message, it > doesn't work with JTDX either. Can't tell about JT Alert because > for it to work it has to connect with one of those. I emailed the > OmniRig guru but haven't heard back. I think that there is a > hidden file somewhere in the WSJT-X stuff that's messed up because > when I reinstalled. my data (callsign, QTH, etc.) was still there > but I still get the error message. > > * > * > * > How can I get this fixed? > THANKS IN ADVANCE > > KR > > **Kevin RushEmoji ** > *KR5TX* > > *Lubbock, TX > Ol...@ya... > *“The things a man has to have are hope and confidence in himself > against odds, and sometimes he needs somebody, his pal or his > mother or his wife or God, to give him that confidence. He's got > to have some inner standards worth fighting for or there won't be > any way to bring him into conflict. And he must be ready to choose > death before dishonor without making too much song and dance about > it. That's all there is to it.” -Clark Gable > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > -- Chris > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Alan <al...@al...> - 2025-01-30 22:10:33
|
You may find this is all related to USB enumeration, which is done when the machine first starts. That will also presumably affect Com ports as I've seen those vary as well. My understanding is they are all allocated depending on what's connected and the connection history, when the machine starts up. I had something similar happen, albeit with different hardware and software, and the cure was to plug each USB device into every socket one at a time so recognition became near instant. Order of software start may also be important? Don't know if that kind of approach will help. Alan G0TLK, sent from my mobile device On 30 January 2025 21:08:41 "roland.hartmann--- via wsjt-devel" <wsj...@li...> wrote: > Hi Kevin, > > I have an in general equal configuration. > IC7300 (instead of TS590) > Windows 11 Pro 64-bit (but should be equal) > WSJT-Z (instead of WSJT-X) > Omni-Rig 1.16 > > So far I remember I had issues with Omni-Rig 1.20. I do not remember what > it was exactly – cause it is running yet I will not test with 1.20. > So would be one part to test with version 1.16. > > But what I remember if in the time where the PC starts (more exactly when > the background-task for Omni-Rig starts) the virtual COM-Port of the TRX > was not present I had the same issues like you describe. > Simple to switch on the TRX later on did not help – I had to restart the PC. > What I found out – to swich on the TRX, change with the program OmniRig.exe > shortly the COM-Port to another one, save, and go back to the right port. Save. > Than all was working. > > Maybe a third one. If I change the audio-devices on the PC (eg plugging or > unplugging USB-Headset) and start in my case WSJT-Z it says also that the > connection to the RIG do not work. Found out those is working – but the > configuration for the SoundCard of the TRX was not correctly. Those one > could also be an issue on your configuration. > > Hopefully one of those hints will work for you. > > 73 Roland DK4RH > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: <rol...@we...> - 2025-01-30 21:06:32
|
Hi Kevin, I have an in general equal configuration. * IC7300 (instead of TS590) * Windows 11 Pro 64-bit (but should be equal) * WSJT-Z (instead of WSJT-X) * Omni-Rig 1.16 So far I remember I had issues with Omni-Rig 1.20. I do not remember what it was exactly - cause it is running yet I will not test with 1.20. So would be one part to test with version 1.16. But what I remember if in the time where the PC starts (more exactly when the background-task for Omni-Rig starts) the virtual COM-Port of the TRX was not present I had the same issues like you describe. Simple to switch on the TRX later on did not help - I had to restart the PC. What I found out - to swich on the TRX, change with the program OmniRig.exe shortly the COM-Port to another one, save, and go back to the right port. Save. Than all was working. Maybe a third one. If I change the audio-devices on the PC (eg plugging or unplugging USB-Headset) and start in my case WSJT-Z it says also that the connection to the RIG do not work. Found out those is working - but the configuration for the SoundCard of the TRX was not correctly. Those one could also be an issue on your configuration. Hopefully one of those hints will work for you. 73 Roland DK4RH |
From: Christopher W. <ch...@wa...> - 2025-01-30 20:36:11
|
Appreciate the recommendation. I only use Windows Defender, and it does not generate any notifications. There are never entries in the Windows Defender logs. As far as I can tell from the OmniRig debug logs, OminRig thinks the serial port isn't responding. I have never had problem accessing with Log4OM2 or WSJTX via Omnirig alone (such as when using N1MM for contesting), or connecting directly with WSJTX without OmniRig. Chris On Thu, Jan 30, 2025 at 1:53 PM DG2YCB <DG...@gm...> wrote: > Hi Kevin, Chris and all, > > FYI: I have used OmniRig for many years and have never experienced such > problems. You should check whether your virus scanner is intervening. > > 73 de DG2YCB, > Uwe > _________________________________________ > German Amateur Radio Station DG2YCB > Dr. Uwe Risse > eMail: DG...@gm... > Info: www.qrz.com/db/DG2YCB > > > Am 30. Januar 2025 19:39:57 schrieb Christopher Wawak via wsjt-devel < > wsj...@li...>: > >> I see this error regularly with OmniRig, Log4OM and WSJTX. All are >> running as a regular user, and this only seems to happen after the system >> has been booted for a while. Sometimes restarting all the apps helps, >> sometimes resetting com ports helps, sometimes rebooting helps, sometimes >> none of these help. This has been going on for at least 3 years, and I've >> never really seen an improvement or found a solid way to troubleshoot. >> >> Not much to add, but I wanted to give some moral support. >> >> 73 KC2IEB Chris >> >> On Thu, Jan 30, 2025 at 10:16 AM Kevin R. via wsjt-devel < >> wsj...@li...> wrote: >> >>> Resubmission after joining the mailing list >>> >>> ----- Forwarded Message ----- >>> *From:* Kevin R. <kr...@ya...> >>> *To:* wsj...@li... <wsj...@li... >>> > >>> *Sent:* Wednesday, January 29, 2025 at 09:59:33 PM CST >>> *Subject:* Omnirig error message >>> >>> >>> - Program version - WSJT-X v2.6.1 - OmniRig v1.20 >>> - Operating system - Windows 10 Pro 64-bit operating system, >>> x64-based processor >>> - Concise description of the problem >>> >>> I'm having a MAJOR problem with OmniRig. All of the sudden I get this >>> message when opening WSJT-X >>> [image: Inline image] >>> I get the same error message when opening JTDX but OmniRig works with >>> Log3OM. >>> I have uninstalled and reinstalled both WSJT-X and OmniRig but I >>> continue to get the error message. >>> >>> These are questions from the author of OmniRig - he has not responded >>> yet to my answered to his questions. >>> OmniRig worked fine with WSJT-X before, and only recently the error >>> started to appear? *Correct - I was testing a different radio (Yaesu >>> FTDX10) to see if I wanted to buy it. Went back to my original settings >>> (Kenwood TS590sg) and the problems started.* >>> You did not change any settings in OmniRig, and Log4OM works with >>> OmniRig fine even now. Is this correct? *OmniRig connects the radio >>> (TS590sg) to Log4OM and the freqs change etc. When opening WSJTX either >>> with or without Log4OM, the com error message appears.* >>> Also, are you trying to run Wsjtx and Log4om at the same time? - *I >>> want to run Log4OM, WSJT-X, JTAlert, and GridTracker at the same time - I >>> had it working that way once before but only Log4OM is connecting with >>> OmniRig now - I don't think GridTracker depends on OmniRig. Without WSJT-X >>> working, JTAlert won't work either.* >>> What happens of you do not start the logger and run only wsjtx? - *Com >>> error message. The same for JTDX.* >>> >>> >>> *I have not gotten into ini files to edit or anything like that but, I >>> did remove all of the prior OmniRig and downloaded the latest v1.20 version >>> plus the latest Rigini and it did not make a difference. Device manager >>> shows the proper driver, and the Com port is 5 and the baud rate is set at >>> 38400. The port and baud rate was part of the original Omnirig settings for >>> the 590. If there is something corrupted I cannot figure out where it would >>> be. It is puzzling that OmniRig works with Log4OM but not WSJT-X or JTDX. I >>> just thought of this and don't know if it has any bearing since they don't >>> show up without the radio connected to the computer, but I removed the USB >>> drivers for the Yaesu. The Yaesu drivers defaulted to different com ports >>> as well. I re-entered my USB drivers for the Kenwood just in case, deleted >>> and reinstalled WSJT-X and still get the same error message, it doesn't >>> work with JTDX either. Can't tell about JT Alert because for it to work it >>> has to connect with one of those. I emailed the OmniRig guru but haven't >>> heard back. I think that there is a hidden file somewhere in the WSJT-X >>> stuff that's messed up because when I reinstalled. my data (callsign, QTH, >>> etc.) was still there but I still get the error message.* >>> >>> How can I get this fixed? >>> THANKS IN ADVANCE >>> >>> KR >>> >>> *Kevin Rush [image: Emoji] * >>> *KR5TX* >>> >>> *Lubbock, TX...@ya... <Ol...@ya...>*“The things a man has to >>> have are hope and confidence in himself against odds, and sometimes he >>> needs somebody, his pal or his mother or his wife or God, to give him that >>> confidence. He's got to have some inner standards worth fighting for or >>> there won't be any way to bring him into conflict. And he must be ready to >>> choose death before dishonor without making too much song and dance about >>> it. That's all there is to it.” -Clark Gable >>> >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >> >> >> -- >> -- Chris >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> > -- -- Chris |
From: DG2YCB <DG...@gm...> - 2025-01-30 18:53:35
|
Hi Kevin, Chris and all, FYI: I have used OmniRig for many years and have never experienced such problems. You should check whether your virus scanner is intervening. 73 de DG2YCB, Uwe _________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: DG...@gm... Info: www.qrz.com/db/DG2YCB Am 30. Januar 2025 19:39:57 schrieb Christopher Wawak via wsjt-devel <wsj...@li...>: > I see this error regularly with OmniRig, Log4OM and WSJTX. All are running > as a regular user, and this only seems to happen after the system has been > booted for a while. Sometimes restarting all the apps helps, sometimes > resetting com ports helps, sometimes rebooting helps, sometimes none of > these help. This has been going on for at least 3 years, and I've never > really seen an improvement or found a solid way to troubleshoot. > > Not much to add, but I wanted to give some moral support. > > > 73 KC2IEB Chris > > > On Thu, Jan 30, 2025 at 10:16 AM Kevin R. via wsjt-devel > <wsj...@li...> wrote: > > Resubmission after joining the mailing list > > > > ----- Forwarded Message ----- > From: Kevin R. <kr...@ya...> > To: wsj...@li... <wsj...@li...> > Sent: Wednesday, January 29, 2025 at 09:59:33 PM CST > Subject: Omnirig error message > > > Program version - WSJT-X v2.6.1 - OmniRig v1.20 > Operating system - Windows 10 Pro 64-bit operating system, x64-based processor > Concise description of the problem > I'm having a MAJOR problem with OmniRig. All of the sudden I get this > message when opening WSJT-X > > I get the same error message when opening JTDX but OmniRig works with Log3OM. > I have uninstalled and reinstalled both WSJT-X and OmniRig but I continue > to get the error message. > > > These are questions from the author of OmniRig - he has not responded yet > to my answered to his questions. > OmniRig worked fine with WSJT-X before, and only recently the error started > to appear? Correct - I was testing a different radio (Yaesu FTDX10) to see > if I wanted to buy it. Went back to my original settings (Kenwood TS590sg) > and the problems started. > You did not change any settings in OmniRig, and Log4OM works with OmniRig > fine even now. Is this correct? OmniRig connects the radio (TS590sg) to > Log4OM and the freqs change etc. When opening WSJTX either with or without > Log4OM, the com error message appears. > > Also, are you trying to run Wsjtx and Log4om at the same time? - I want to > run Log4OM, WSJT-X, JTAlert, and GridTracker at the same time - I had it > working that way once before but only Log4OM is connecting with OmniRig now > - I don't think GridTracker depends on OmniRig. Without WSJT-X working, > JTAlert won't work either. > > What happens of you do not start the logger and run only wsjtx? - Com error > message. The same for JTDX. > > > I have not gotten into ini files to edit or anything like that but, I did > remove all of the prior OmniRig and downloaded the latest v1.20 version > plus the latest Rigini and it did not make a difference. Device manager > shows the proper driver, and the Com port is 5 and the baud rate is set at > 38400. The port and baud rate was part of the original Omnirig settings for > the 590. If there is something corrupted I cannot figure out where it would > be. It is puzzling that OmniRig works with Log4OM but not WSJT-X or JTDX. I > just thought of this and don't know if it has any bearing since they don't > show up without the radio connected to the computer, but I removed the USB > drivers for the Yaesu. The Yaesu drivers defaulted to different com ports > as well. I re-entered my USB drivers for the Kenwood just in case, deleted > and reinstalled WSJT-X and still get the same error message, it doesn't > work with JTDX either. Can't tell about JT Alert because for it to work it > has to connect with one of those. I emailed the OmniRig guru but haven't > heard back. I think that there is a hidden file somewhere in the WSJT-X > stuff that's messed up because when I reinstalled. my data (callsign, QTH, > etc.) was still there but I still get the error message. > > > > > How can I get this fixed? > THANKS IN ADVANCE > > > KR > > > Kevin Rush > KR5TX > Lubbock, TX > Ol...@ya... > “The things a man has to have are hope and confidence in himself against > odds, and sometimes he needs somebody, his pal or his mother or his wife or > God, to give him that confidence. He's got to have some inner standards > worth fighting for or there won't be any way to bring him into conflict. > And he must be ready to choose death before dishonor without making too > much song and dance about it. That's all there is to it.” -Clark Gable > > > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > > -- Chris > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Christopher W. <ch...@wa...> - 2025-01-30 18:39:32
|
I see this error regularly with OmniRig, Log4OM and WSJTX. All are running as a regular user, and this only seems to happen after the system has been booted for a while. Sometimes restarting all the apps helps, sometimes resetting com ports helps, sometimes rebooting helps, sometimes none of these help. This has been going on for at least 3 years, and I've never really seen an improvement or found a solid way to troubleshoot. Not much to add, but I wanted to give some moral support. 73 KC2IEB Chris On Thu, Jan 30, 2025 at 10:16 AM Kevin R. via wsjt-devel < wsj...@li...> wrote: > Resubmission after joining the mailing list > > ----- Forwarded Message ----- > *From:* Kevin R. <kr...@ya...> > *To:* wsj...@li... <wsj...@li...> > *Sent:* Wednesday, January 29, 2025 at 09:59:33 PM CST > *Subject:* Omnirig error message > > > - Program version - WSJT-X v2.6.1 - OmniRig v1.20 > - Operating system - Windows 10 Pro 64-bit operating system, x64-based > processor > - Concise description of the problem > > I'm having a MAJOR problem with OmniRig. All of the sudden I get this > message when opening WSJT-X > [image: Inline image] > I get the same error message when opening JTDX but OmniRig works with > Log3OM. > I have uninstalled and reinstalled both WSJT-X and OmniRig but I continue > to get the error message. > > These are questions from the author of OmniRig - he has not responded yet > to my answered to his questions. > OmniRig worked fine with WSJT-X before, and only recently the error > started to appear? *Correct - I was testing a different radio (Yaesu > FTDX10) to see if I wanted to buy it. Went back to my original settings > (Kenwood TS590sg) and the problems started.* > You did not change any settings in OmniRig, and Log4OM works with OmniRig > fine even now. Is this correct? *OmniRig connects the radio (TS590sg) to > Log4OM and the freqs change etc. When opening WSJTX either with or without > Log4OM, the com error message appears.* > Also, are you trying to run Wsjtx and Log4om at the same time? - *I want > to run Log4OM, WSJT-X, JTAlert, and GridTracker at the same time - I had it > working that way once before but only Log4OM is connecting with OmniRig now > - I don't think GridTracker depends on OmniRig. Without WSJT-X working, > JTAlert won't work either.* > What happens of you do not start the logger and run only wsjtx? - *Com > error message. The same for JTDX.* > > > *I have not gotten into ini files to edit or anything like that but, I did > remove all of the prior OmniRig and downloaded the latest v1.20 version > plus the latest Rigini and it did not make a difference. Device manager > shows the proper driver, and the Com port is 5 and the baud rate is set at > 38400. The port and baud rate was part of the original Omnirig settings for > the 590. If there is something corrupted I cannot figure out where it would > be. It is puzzling that OmniRig works with Log4OM but not WSJT-X or JTDX. I > just thought of this and don't know if it has any bearing since they don't > show up without the radio connected to the computer, but I removed the USB > drivers for the Yaesu. The Yaesu drivers defaulted to different com ports > as well. I re-entered my USB drivers for the Kenwood just in case, deleted > and reinstalled WSJT-X and still get the same error message, it doesn't > work with JTDX either. Can't tell about JT Alert because for it to work it > has to connect with one of those. I emailed the OmniRig guru but haven't > heard back. I think that there is a hidden file somewhere in the WSJT-X > stuff that's messed up because when I reinstalled. my data (callsign, QTH, > etc.) was still there but I still get the error message.* > > How can I get this fixed? > THANKS IN ADVANCE > > KR > > *Kevin Rush [image: Emoji] * > *KR5TX* > > *Lubbock, TX...@ya... <Ol...@ya...>*“The things a man has to > have are hope and confidence in himself against odds, and sometimes he > needs somebody, his pal or his mother or his wife or God, to give him that > confidence. He's got to have some inner standards worth fighting for or > there won't be any way to bring him into conflict. And he must be ready to > choose death before dishonor without making too much song and dance about > it. That's all there is to it.” -Clark Gable > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- -- Chris |
From: Reino T. <rei...@ko...> - 2025-01-30 17:40:16
|
Hi Kevin, I know nothing about the OmniRig, but WSJT-X holds all user settings related information in the WSJT-X.ini file. That file is in the log directory. You may go there using File | Open log directory menu item. You may rename the file to something else and restart WSJT-X. You need to perform all settings as WSJT-X has built a default wsjt-x.ini file and don’t any more know about you. The re-installation of the wsjt-x does not clear the wsjt-x.ini file. 73, Reino OH3mA |
From: Kevin R. <kr...@ya...> - 2025-01-30 15:15:28
|
Resubmission after joining the mailing list ----- Forwarded Message ----- From: Kevin R. <kr...@ya...>To: wsj...@li... <wsj...@li...>Sent: Wednesday, January 29, 2025 at 09:59:33 PM CSTSubject: Omnirig error message - Program version - WSJT-X v2.6.1 - OmniRig v1.20 - Operating system - Windows 10 Pro 64-bit operating system, x64-based processor - Concise description of the problem I'm having a MAJOR problem with OmniRig. All of the sudden I get this message when opening WSJT-X I get the same error message when opening JTDX but OmniRig works with Log3OM.I have uninstalled and reinstalled both WSJT-X and OmniRig but I continue to get the error message. These are questions from the author of OmniRig - he has not responded yet to my answered to his questions. OmniRig worked fine with WSJT-X before, and only recently the error started to appear? Correct - I was testing a different radio (Yaesu FTDX10) to see if I wanted to buy it. Went back to my original settings (Kenwood TS590sg) and the problems started.You did not change any settings in OmniRig, and Log4OM works with OmniRig fine even now. Is this correct? OmniRig connects the radio (TS590sg) to Log4OM and the freqs change etc. When opening WSJTX either with or without Log4OM, the com error message appears. Also, are you trying to run Wsjtx and Log4om at the same time? - I want to run Log4OM, WSJT-X, JTAlert, and GridTracker at the same time - I had it working that way once before but only Log4OM is connecting with OmniRig now - I don't think GridTracker depends on OmniRig. Without WSJT-X working, JTAlert won't work either. What happens of you do not start the logger and run only wsjtx? - Com error message. The same for JTDX. I have not gotten into ini files to edit or anything like that but, I did remove all of the prior OmniRig and downloaded the latest v1.20 version plus the latest Rigini and it did not make a difference. Device manager shows the proper driver, and the Com port is 5 and the baud rate is set at 38400. The port and baud rate was part of the original Omnirig settings for the 590. If there is something corrupted I cannot figure out where it would be. It is puzzling that OmniRig works with Log4OM but not WSJT-X or JTDX. I just thought of this and don't know if it has any bearing since they don't show up without the radio connected to the computer, but I removed the USB drivers for the Yaesu. The Yaesu drivers defaulted to different com ports as well. I re-entered my USB drivers for the Kenwood just in case, deleted and reinstalled WSJT-X and still get the same error message, it doesn't work with JTDX either. Can't tell about JT Alert because for it to work it has to connect with one of those. I emailed the OmniRig guru but haven't heard back. I think that there is a hidden file somewhere in the WSJT-X stuff that's messed up because when I reinstalled. my data (callsign, QTH, etc.) was still there but I still get the error message. How can I get this fixed?THANKS IN ADVANCE KR Kevin Rush ADDRESS: KR5TX ADDRESS: Lubbock, TX Ol...@ya... “The things a man has to have are hope and confidence in himself against odds, and sometimes he needs somebody, his pal or his mother or his wife or God, to give him that confidence. He's got to have some inner standards worth fighting for or there won't be any way to bring him into conflict. And he must be ready to choose death before dishonor without making too much song and dance about it. That's all there is to it.” -Clark Gable |
From: Black M. <mdb...@ya...> - 2025-01-26 16:14:58
|
The 7300 doesn't work with a USB isolator as it requires power from the hub/computer.I've now tested a couple of powered hubs and they work too. So it's isolating the data lines appears to be the things that works best. Mike W9MDB On Sunday, January 26, 2025 at 10:03:57 AM CST, Jari A via wsjt-devel <wsj...@li...> wrote: There are USB-isolators. Galvanic isolator and provides 1500V potential isolation and USB-2 speed. Gives enough power for external audio cards.It uses ADUM 3160 chip. Solve my RF and ground loop problems with computer Available from ebay, aliexpress, amazon and other sellers. :Jari / OH2FQV On Sun, Jan 26, 2025 at 7:17 AM Enrico OE1EQW via wsjt-devel <wsj...@li...> wrote: Maybe this item can help you: Amazon ASIN B0D3FYJ4MM 73 Enrico OE1EQW Am 25.01.2025 um 22:19 schrieb Black Michael via wsjt-devel: In my current setup there is an IC-7300 that has been unable to transmit even 1W without dropping the USB connection. I have numerous rigs hooked up and lots of USB connections. The 7300 is well known for being RFI sensitive dropping CAT and Audio service. So I bought an optical USB cable, plugged it into a non-powered Startech hub, then ran a triplite cable to the rig. Now able to run full power without any problems. I'll be doing more investigation with a cheaper hub and adding more USB devices to this new hub. But the optical cable has a USB-B on one end and USB-A on the other. So do need a USB hub that takes a USB-B cable. Not a cheap solution but effective. https://www.amazon.com/dp/B01N94D03E https://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8 Mike W9MDB _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Landesleiter ÖVSV LV NÖ _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
From: Jari A <oh...@gm...> - 2025-01-26 15:57:53
|
There are USB-isolators. Galvanic isolator and provides 1500V potential isolation and USB-2 speed. Gives enough power for external audio cards. It uses ADUM 3160 chip. Solve my RF and ground loop problems with computer Available from ebay, aliexpress, amazon and other sellers. :Jari / OH2FQV On Sun, Jan 26, 2025 at 7:17 AM Enrico OE1EQW via wsjt-devel < wsj...@li...> wrote: > Maybe this item can help you: > > Amazon ASIN B0D3FYJ4MM > > 73 > > Enrico OE1EQW > Am 25.01.2025 um 22:19 schrieb Black Michael via wsjt-devel: > > In my current setup there is an IC-7300 that has been unable to transmit > even 1W without dropping the USB connection. I have numerous rigs hooked > up and lots of USB connections. The 7300 is well known for being RFI > sensitive dropping CAT and Audio service. > > So I bought an optical USB cable, plugged it into a non-powered Startech > hub, then ran a triplite cable to the rig. Now able to run full power > without any problems. > I'll be doing more investigation with a cheaper hub and adding more USB > devices to this new hub. But the optical cable has a USB-B on one end and > USB-A on the other. So do need a USB hub that takes a USB-B cable. > > Not a cheap solution but effective. > > https://www.amazon.com/dp/B01N94D03E > > https://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8 > > Mike W9MDB > > > > > _______________________________________________ > wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- > Landesleiter > ÖVSV LV NÖ > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
From: Enrico O. <oe...@oe...> - 2025-01-26 05:12:58
|
Maybe this item can help you: Amazon ASIN B0D3FYJ4MM 73 Enrico OE1EQW Am 25.01.2025 um 22:19 schrieb Black Michael via wsjt-devel: > In my current setup there is an IC-7300 that has been unable to > transmit even 1W without dropping the USB connection. I have numerous > rigs hooked up and lots of USB connections. The 7300 is well known > for being RFI sensitive dropping CAT and Audio service. > > So I bought an optical USB cable, plugged it into a non-powered > Startech hub, then ran a triplite cable to the rig. Now able to run > full power without any problems. > I'll be doing more investigation with a cheaper hub and adding more > USB devices to this new hub. But the optical cable has a USB-B on one > end and USB-A on the other. So do need a USB hub that takes a USB-B > cable. > > Not a cheap solution but effective. > > https://www.amazon.com/dp/B01N94D03E > https://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8 > <https://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8> > > Mike W9MDB > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Landesleiter ÖVSV LV NÖ |