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 |