|
locked
Re: WSJT-X Loses TX Audio Connection to transceiver
#AudioIssues
HI,
It appears that many of you are mentioning the Audio Power Management feature in USB ports, but as I mentioned in the original post, I do have them all set to OFF (unchecked). So the USB ports are not going to sleep to save power. MICHAEL BLACK: What is USB SELECTIVE SUSPEND and where do I find this setting?? I'm not plugging or unplugging devices, everything here is well grounded to a single point ground, even the Desktop PC (thus not powered by a wallwart or external PS). RF is not causing this as there is no RF here when this quits working, I've been idle, only monitoring the band. -- Glen, WB4KTF Austin, TX
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Sam Birnbaum
Hi Bruce,
toggle quoted messageShow quoted text
You can try My AllText.exe program that is freely available on ProgramsByW2JDB@Groups.io. It does not load the file into memory and given the from/to date and the callsigns to search, should find the resulting lines in less than 1 second even in a file as large as 1.5 GB. In a file of 110MB, the results are found in less the 0.1 seconds. The program can be up and running while WSJT-X is also running. 73, Sam W2JDB
-----Original Message-----
From: Bruce Goldstein <wa3afs@...> To: main@WSJTX.groups.io Sent: Fri, Feb 25, 2022 9:52 am Subject: Re: [WSJTX] Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4 Thanks for those that reponded... Unfortunately, I have never looked at my ALL.TXT file and it is 1.3 GB in size and both WORD and notepad say it is too large. Is there some other editor that I could possibly try. I have now renamed the too large ALL.TXT and restarted WSJT-x so I now have a small file if this happens again. Maybe I should rename the ALL.TXT monthly.... You could be correct that the SV1 could have called me that morning, but I was calling the YB5 at the time and ignored him... Bruce, WA3AFS
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Reino Talarmo
Unfortunately, I have never looked at my ALL.TXT file and it is 1.3 GB in size and both WORD and notepad say it is too large. Is there some other editor that I could possibly try. I have now renamed the too large ALL.TXT and restarted WSJT-x so I now have a small file if this happens again.Bruce, You could try Notepad++, it is a free text editor I like. 73, Reino OH3mA
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Tom Melvin
Look for NotePad++ great editor with very few limits.
toggle quoted messageShow quoted text
Tom GM8MJV Tom@...
On 25 Feb 2022, at 14:52, Bruce Goldstein <wa3afs@...> wrote:
|
|
|
|
Erik Icket
For those interested, here is a small project that implements the encoding and signalling of WSPR / JT4 and JT8 in Java.
The “myWSJTEncoder” project can be found at https://github.com/eicket/myWSJTEncoder and is a pure Java implementation for generating WSJT signals on the selected audio port. The implementation for all modes is faithful to the protocol specifications, except for FT4/FT8 messages which are limited to the “Free Text” message type. The code is also not fully optimized for performance, but tries to be as readable and understandable as possible. The goal of the project is merely educational (implement the 3 modes from scratch) and experimental, with an implementation in a single programming language (Java) and this without the need for external libraries. The code is not fully optimized for performance, but tries to be as readable and understandable as possible. Any comments, questions, ideas, bug reports .. are more than welcome ! 73's Erik ON4PB
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Bruce - K5WBM
Notepad+ should be able to read it.
toggle quoted messageShow quoted text
I rename my all.txt file yearly. Bruce - K5WBM
On Feb 25, 2022, at 9:04 AM, Bruce Goldstein <wa3afs@...> wrote:
|
|
|
|
locked
Re: WSJT-X Loses TX Audio Connection to transceiver
#AudioIssues
Including HDMI ports.
toggle quoted messageShow quoted text
Larry / W1DYJ
On 2/25/2022 10:37, Michael Black via groups.io wrote:
The walk-away problem is usuallyi USB selective suspend.Turn them ALL off on ALL USB devices and hubs.
|
|
|
|
locked
Re: Off topic
#Cat_RigControl
Reino Talarmo
Pietro,
toggle quoted messageShow quoted text
Have a look at https://svn.python.org/projects/ctypes/tags/comtypes-0.3.2/docs/com_interfaces.html It may be what you are missing. 73, Reino OH3mA
I realized. It's an old (still common) technology. So I'll move to some other language, Python seem to be without support for COM.
|
|
|
|
locked
Re: WSJT-X Loses TX Audio Connection to transceiver
#AudioIssues
Bruce - K5WBM
I can confirm that an hdmi monitor going to sleep can cause the audio issue you describe. I had to disable the monitor audio source on my system and have not had issues since.
toggle quoted messageShow quoted text
Bruce - K5WBM
On Feb 25, 2022, at 9:22 AM, Chris VE3NRT <dx@...> wrote:
|
|
|
|
locked
Re: Off topic
#Cat_RigControl
I realized. It's an old (still common) technology. So I'll move to some
other language, Python seem to be without support for COM. Pietro Il giorno ven 25 feb 2022 alle ore 14:49 Michael Black via groups.io <mdblack98@...> ha scritto: OmniRig is WIndows only.OmniRig's API is a Windows-only thing too...it's a
|
|
|
|
locked
Re: WSJT-X Loses TX Audio Connection to transceiver
#AudioIssues
Michael Black
The walk-away problem is usuallyi USB selective suspend.Turn them ALL off on ALL USB devices and hubs.
toggle quoted messageShow quoted text
Mike W9MDB
On Friday, February 25, 2022, 09:22:42 AM CST, Chris VE3NRT <dx@...> wrote:
I have the same problem when I haven't transmitted for a while, using the audio device built into the motherboard. WSJT-X still receives signals and keys the transmitter, but it sends no audio to the rig. Restarting WSJT-X fixes it. There are at least two reasons not to suspect RFI. First is that restarting a program fixes it, and second is that there is no RF present. There is also no unplugging/replugging required. Just go away for a couple of hours, come back, and audio output no longer works. It could be related to the audio port in the monitor going to sleep when it goes into power save mode. That seems far-fetched, but easy enough to check. Next time it happens I'll poke around in device manager, etc., and report back if I see anything unusual. 73, Chris
|
|
|
|
Ray
K4 has newly designed different ALC circuit from the K3. Watch power out meter to monitor power.
Ray
|
|
|
|
locked
Re: WSJT-X Loses TX Audio Connection to transceiver
#AudioIssues
Chris VE3NRT
I have the same problem when I haven't transmitted for a while, using the audio device built into the motherboard. WSJT-X still receives signals and keys the transmitter, but it sends no audio to the rig. Restarting WSJT-X fixes it.
There are at least two reasons not to suspect RFI. First is that restarting a program fixes it, and second is that there is no RF present. There is also no unplugging/replugging required. Just go away for a couple of hours, come back, and audio output no longer works. It could be related to the audio port in the monitor going to sleep when it goes into power save mode. That seems far-fetched, but easy enough to check. Next time it happens I'll poke around in device manager, etc., and report back if I see anything unusual. 73, Chris
|
|
|
|
Ray
FT8 unlike other digital modes is constant envelope/carrier. ALC does not vary. Adjust K4 for solid 5 bars.
Ray
|
|
|
|
Carl Nord
I have been playing with WSPR for a while over the last several months using my Zachtek 80-10 meter transmitter into a 30 ft high OCF dipole.
I have been slowly adding in attenuation and watching the monitor spots reduce, but some remained. Sunday night I inserted a total of 36 dBm od attenuation (.050118723363 mW) For 3 days no monitors heard me. Thursday morning a station 406 miles west captured one of my 40-meter transmissions. -- Carl WA1KPD
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Bruce Goldstein
Thanks for those that reponded...
Unfortunately, I have never looked at my ALL.TXT file and it is 1.3 GB in size and both WORD and notepad say it is too large. Is there some other editor that I could possibly try. I have now renamed the too large ALL.TXT and restarted WSJT-x so I now have a small file if this happens again. Maybe I should rename the ALL.TXT monthly.... You could be correct that the SV1 could have called me that morning, but I was calling the YB5 at the time and ignored him... Bruce, WA3AFS
|
|
|
|
locked
Re: Incorrect time on FT8 Log QSO Screen WSJT-x v2.5.4
#IssueReport
Michael Black
Here's some comments in the code on how start time is calculated the "minutes" is actually transmit time periods now since this logic was put in before FT8.
toggle quoted messageShow quoted text
// m_ntx = -1 resets to default time // Our QSO start time can be fairly well determined from Tx 2 and Tx 3 -- the grid reports // If we CQ'd and sending sigrpt then 2 minutes ago n=2 // If we're on msg 3 then 3 minutes ago n=3 -- might have sat on msg1 for a while // If we've already set our time on just return. // This should mean that Tx2 or Tx3 has been repeated so don't update the start time // We reset it in several places Would be nice if we could see your ALL.TXT file from 12:00 to 01:00 Mike W9MDB
On Friday, February 25, 2022, 06:06:47 AM CST, Roger <groups@...> wrote:
On 25/02/2022 02:04, Bruce Goldstein wrote: WSJT-X v2.5.4I think WSJTX follows the standard practice of recording the QSO start from your original CQ call. If you want a non-standard start time you will have to adjust the start time in the pop up at the end of your QSO. 73 Roger GW4HZA
|
|
|
|
Michael Black
The problem with using less was that the rigs would do power hunting.So is the K4 doing power hunting with less than 5 solid bars? Or just doesn't' get full power?
toggle quoted messageShow quoted text
Mike W9MDB
On Friday, February 25, 2022, 08:46:20 AM CST, Ray <anyone1545@...> wrote:
Not on the K4. It’s different Ray Serial # 172.
|
|
|
|
Ray
Not on the K4. It’s different
Ray Serial # 172.
|
|
|
|
Michael Black
Technically 4 bars with the 5 flickering.
toggle quoted messageShow quoted text
Mike W9MDB
On Friday, February 25, 2022, 08:40:25 AM CST, Ray <anyone1545@...> wrote:
5 bars on the K4D Ray W8LYJ
|
|
|