Date   

locked Re: FT4 Output Audio

kk5aa_fred
 

Bill,
Apparently, you did not read the post. I have checked the output in all available HF modes.
Fred - KK5AA


locked Re: FT4 Output Audio

kk5aa_fred
 
Edited

Michael,
Neither.
Fred - KK5AA


locked Re: Uninstalling

Ron Haltermon WA4HWN
 

This may be a Windows update problem.  Their (Microsoft) updates cause more problems than fixes, in my concerted opinion, which is why I run linux on 6 of my computers and only Windows 7 on my Ham radio computer.  No problems.  I have licensed versions of Windows XP, XP Pro, 7 Home Premium, 7 Pro, 8.1 and 10 and ceased using all of them except Windows 7 Home Premium.  I run HDR, NaP3, WSJT-X, and N4PY software all on Win 7 machine and have downloaded, and used, each of WSJT release over the past two+ years with no issues.  (I have stuck with 32 bit in all instances on the Windows machine and 64 bit on all Linux machines. 

I dropped SKYPE and went to qTOX and uTOX since Microsoft acquire SKYPE and every update seemed to adversely affect SKYPE (not to mention all of their ads!).  Anyway, Paul, I feel for you.  Been there and done that.......Hi Hi!

Good luck and I hope it turns out to be, for your sake, something simple and not Windows update related.

73 de Ron WA4HWN 

On 7/25/19 11:07 AM, Paul Godwin via Groups.Io wrote:
I'm at my wits end.

Until last Saturday WSJT-X 2.0.1 worked fine.
Then any transmissions quit totally while trying F/H clng 1A0C, but rcv still OK.

Using FT1000MP MKV, Signalink, vox keying, no CAT.

PC updated itself to Win10 1903 (build 18362).
I noticed driver for USB Root Hub 3.0 is now dated 3/18/19. Pwr Management for it turned off.

I  reinstalled 2.0.1, rcv is fine, transmit dead,no tones. PC audio set up as directed, ditto Signalink.
I  saw that F2 Confg tabs were already populated, so the uninstall was apparently incomplete.

I found the WSJT-X.ini file and copied it to a new folder & renamed it too.
Ran Uninstall again then deleted wsjt directories including "log directory".

Installed 2.0.1 again, F2 Config tabs STILL populated ! How can this be ?
Even tried 2.1.0 32 and 64bit versions, same results.

I figured I'd try a clean install, start from scratch having to re- enter everything and so on but no go.

I've spent hours on this, totally frustrated.
I'm getting to where I'm thinking of dropping the whole thing until  smarter folks can sort it out and a stable installation becomes possible.

73, comments welcome, Paul N5PG

BTW not RFI, been using dummy load with minimum pwr.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3755): https://groups.io/g/WSJTX/message/3755
Mute This Topic: https://groups.io/mt/32599621/476579
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/3366251/1608637857/xyzzy  [rhaltermon@...]
-=-=-=-=-=-=-=-=-=-=-=-
--


locked Re: Installed 2.1.0 64 bit and now getting "Rig Control Error"

HB9BRJ
 

Have seen sporadic Rig Control Errors as well after upgrading to WJST-X 2.1.0. Did not capture the error msg but it was like "rig took too long to respond". Today, when trying to force the error to appear again, it didn't!

Here is my configuration:
- WSJT-X v2.1.0 Win64
- Windows 10 1903 x64 (10.0.18362.239)
- Omni-Rig 1.19 (38400 Bd, 500ms poll interval, 4000ms timeout)
- Elecraft K3 attached to a real COM0
- Log4OM 1.38 including its TCP communicator running
- 2 instances of Omni-Rig client (by Alex VE3NEA) running (just additional Omni-Rig "load")
- GridTracker running (forwards WSJT-X log data to the Log4OM communicator)

I can change QRG in any of the 4 softwares or on the K3's front panel, and all others are following. Not a single error during 1 hour! Maybe it depends on which software is being launched first?

73, Markus HB9BRJ


locked Re: Uninstalling

Jim Cooper
 

On 25 Jul 2019 at 9:07, Paul Godwin via Groups.Io wrote:

Until last Saturday WSJT-X 2.0.1 worked fine.
version 2.0.1 is OBSOLETE and I believe it
was coded to stop working when 2.1.0 was
released ...

UPDATE to version 2.1.0 and it should probably work.


locked Re: Installed 2.1.0 64 bit and now getting "Rig Control Error"

Bill Somerville
 

Hi Bernie,

more details please. WSJT-X rig control errors come with a details panel that states exactly what the error was.

For your convenience you can copy the *full* text of the error message to the Windows clipboard by hitting CTRL+C while the message box has keyboard focus.

Just in case you  are in doubt of what that means (many seem to lack this basic keyboard skill) - left mouse button click the title bar of the message then press the CTRL and C keys on your keyboard simultaneously. The captured message can then be pasted into an email message by hitting CTRL+V while entering text into the email message body.

73
Bill
G4WJS.

On 25/07/2019 17:29, Ham Radio wrote:
Getting Hamlib error on 64 bit version of WSJTX when program tries to connect to Icom 746PRO. Audio functions are OK.

The 32 bit version of WSJTX works just fine on the same Windows 64 bit PRO version at update level 1803.

73, Bernie

Sent from my iPad

On Jul 25, 2019, at 12:10 PM, Bill Somerville <g4wjs@...> wrote:

On 25/07/2019 16:53, Ham Radio wrote:
Had the same issue.  The 32 bit version works fine on a 64 bit Windows 10 OS.
OM,

more details please?

73
Bill
G4WJS.



locked Re: Uninstalling

Michael Black
 

Uninstall all your USB devices and let them reinstall.

1903 seems to have messed up a few things.

de Mike W9MDB



On Thursday, July 25, 2019, 11:17:31 AM CDT, Paul Godwin via Groups.Io <n5pg@...> wrote:


I'm at my wits end.

Until last Saturday WSJT-X 2.0.1 worked fine.
Then any transmissions quit totally while trying F/H clng 1A0C, but rcv still OK.

Using FT1000MP MKV, Signalink, vox keying, no CAT.

PC updated itself to Win10 1903 (build 18362).
I noticed driver for USB Root Hub 3.0 is now dated 3/18/19. Pwr Management for it turned off.

I  reinstalled 2.0.1, rcv is fine, transmit dead,no tones. PC audio set up as directed, ditto Signalink.
I  saw that F2 Confg tabs were already populated, so the uninstall was apparently incomplete.

I found the WSJT-X.ini file and copied it to a new folder & renamed it too.
Ran Uninstall again then deleted wsjt directories including "log directory".

Installed 2.0.1 again, F2 Config tabs STILL populated ! How can this be ?
Even tried 2.1.0 32 and 64bit versions, same results.

I figured I'd try a clean install, start from scratch having to re- enter everything and so on but no go.

I've spent hours on this, totally frustrated.
I'm getting to where I'm thinking of dropping the whole thing until  smarter folks can sort it out and a stable installation becomes possible.

73, comments welcome, Paul N5PG

BTW not RFI, been using dummy load with minimum pwr.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3755): https://groups.io/g/WSJTX/message/3755
Mute This Topic: https://groups.io/mt/32599621/212453
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4121090/1473993136/xyzzy [mdblack98@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Re: Uninstalling

Ham Radio <bernard.murphy@...>
 

Have you another radio that has a CAT interface that you could try?

Update 1903 could be the issue as well. Do you have another PC you could try?


Sent from my iPad

On Jul 25, 2019, at 12:07 PM, Paul Godwin via Groups.Io <n5pg@...> wrote:

I'm at my wits end.

Until last Saturday WSJT-X 2.0.1 worked fine.
Then any transmissions quit totally while trying F/H clng 1A0C, but rcv still OK.

Using FT1000MP MKV, Signalink, vox keying, no CAT.

PC updated itself to Win10 1903 (build 18362).
I noticed driver for USB Root Hub 3.0 is now dated 3/18/19. Pwr Management for it turned off.

I reinstalled 2.0.1, rcv is fine, transmit dead,no tones. PC audio set up as directed, ditto Signalink.
I saw that F2 Confg tabs were already populated, so the uninstall was apparently incomplete.

I found the WSJT-X.ini file and copied it to a new folder & renamed it too.
Ran Uninstall again then deleted wsjt directories including "log directory".

Installed 2.0.1 again, F2 Config tabs STILL populated ! How can this be ?
Even tried 2.1.0 32 and 64bit versions, same results.

I figured I'd try a clean install, start from scratch having to re- enter everything and so on but no go.

I've spent hours on this, totally frustrated.
I'm getting to where I'm thinking of dropping the whole thing until smarter folks can sort it out and a stable installation becomes possible.

73, comments welcome, Paul N5PG

BTW not RFI, been using dummy load with minimum pwr.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3755): https://groups.io/g/WSJTX/message/3755
Mute This Topic: https://groups.io/mt/32599621/365823
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4121309/1217653951/xyzzy [bernard.murphy@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Re: Uninstalling

Bill Somerville
 

On 25/07/2019 17:07, Paul Godwin via Groups.Io wrote:
I'm at my wits end.

Until last Saturday WSJT-X 2.0.1 worked fine.
Then any transmissions quit totally while trying F/H clng 1A0C, but rcv still OK.

Using FT1000MP MKV, Signalink, vox keying, no CAT.

PC updated itself to Win10 1903 (build 18362).
I noticed driver for USB Root Hub 3.0 is now dated 3/18/19. Pwr Management for it turned off.

I  reinstalled 2.0.1, rcv is fine, transmit dead,no tones. PC audio set up as directed, ditto Signalink.
I  saw that F2 Confg tabs were already populated, so the uninstall was apparently incomplete.

I found the WSJT-X.ini file and copied it to a new folder & renamed it too.
Ran Uninstall again then deleted wsjt directories including "log directory".

Installed 2.0.1 again, F2 Config tabs STILL populated ! How can this be ?
Even tried 2.1.0 32 and 64bit versions, same results.

I figured I'd try a clean install, start from scratch having to re- enter everything and so on but no go.

I've spent hours on this, totally frustrated.
I'm getting to where I'm thinking of dropping the whole thing until  smarter folks can sort it out and a stable installation becomes possible.

73, comments welcome, Paul N5PG

BTW not RFI, been using dummy load with minimum pwr.
Paul,

you mention several items that are related to different setup issues. Can you simply list exactly what is not working for you and we can start from there. Changing multiple random configuration settings will not achieve anything but confusion.

73
Bill
G4WJS.


locked Re: Installed 2.1.0 64 bit and now getting "Rig Control Error"

Ham Radio <bernard.murphy@...>
 

Getting Hamlib error on 64 bit version of WSJTX when program tries to connect to Icom 746PRO. Audio functions are OK.

The 32 bit version of WSJTX works just fine on the same Windows 64 bit PRO version at update level 1803.

73, Bernie

Sent from my iPad

On Jul 25, 2019, at 12:10 PM, Bill Somerville <g4wjs@...> wrote:

On 25/07/2019 16:53, Ham Radio wrote:
Had the same issue. The 32 bit version works fine on a 64 bit Windows 10 OS.
OM,

more details please?

73
Bill
G4WJS.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3754): https://groups.io/g/WSJTX/message/3754
Mute This Topic: https://groups.io/mt/32551707/365823
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4121309/1217653951/xyzzy [bernard.murphy@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Uninstalling

Paul N5PG
 

I'm at my wits end.

Until last Saturday WSJT-X 2.0.1 worked fine.
Then any transmissions quit totally while trying F/H clng 1A0C, but rcv still OK.

Using FT1000MP MKV, Signalink, vox keying, no CAT.

PC updated itself to Win10 1903 (build 18362).
I noticed driver for USB Root Hub 3.0 is now dated 3/18/19. Pwr Management for it turned off.

I  reinstalled 2.0.1, rcv is fine, transmit dead,no tones. PC audio set up as directed, ditto Signalink.
I  saw that F2 Confg tabs were already populated, so the uninstall was apparently incomplete.

I found the WSJT-X.ini file and copied it to a new folder & renamed it too.
Ran Uninstall again then deleted wsjt directories including "log directory".

Installed 2.0.1 again, F2 Config tabs STILL populated ! How can this be ?
Even tried 2.1.0 32 and 64bit versions, same results.

I figured I'd try a clean install, start from scratch having to re- enter everything and so on but no go.

I've spent hours on this, totally frustrated.
I'm getting to where I'm thinking of dropping the whole thing until  smarter folks can sort it out and a stable installation becomes possible.

73, comments welcome, Paul N5PG

BTW not RFI, been using dummy load with minimum pwr.


locked Re: Installed 2.1.0 64 bit and now getting "Rig Control Error"

Bill Somerville
 

On 25/07/2019 16:53, Ham Radio wrote:
Had the same issue.  The 32 bit version works fine on a 64 bit Windows 10 OS.
OM,

more details please?

73
Bill
G4WJS.


locked Re: Installed 2.1.0 64 bit and now getting "Rig Control Error"

Ham Radio <bernard.murphy@...>
 

Had the same issue.  The 32 bit version works fine on a 64 bit Windows 10 OS.


locked Tentative FT4 operating frequencies?

Ham Radio <bernard.murphy@...>
 

Lots of action on 7.045 last evening July 24.  Made about 25 contacts including some nice DX.

Any tentative list of FT4 frequencies to use?

73, Bernie, VE3FWF


locked Re: need help

Bill Somerville
 

On 25/07/2019 16:51, jim crisco via Groups.Io wrote:
hi all...need help with entering a call sign...
vx2a11...
i think it is a non-standard call...
when i enter it in gen standard msg's tab 1 for sending cq....
will not send the grid square when calling cq...
on a mini-dxpedition...a island..iles la grosse ..grid FN97fo
i must be missing something....
thanks
jim
wa4yiz

Hi Jim,

you have not missed anything. The details are in the WSJT-X User Guide here: https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.1.0.html#COMP-CALL

You can send a message including your grid but not as part of the standard exchange supported by WSJT-X when auto-sequencing in the FT8, MSK144 and FT4 modes. You could send a message like this after a QSO:

G4WJS <VX2A11> FN97

Note your call is sent as a hash code, therefore this message cannot be used as the first message in a QSO.

73
Bill
G4WJS.


locked need help

jim crisco WA4YIZ
 

hi all...need help with entering a call sign...
vx2a11...
i think it is a non-standard call...
when i enter it in gen standard msg's tab 1 for sending cq....
will not send the grid square when calling cq...
on a mini-dxpedition...a island..iles la grosse ..grid FN97fo
i must be missing something....
thanks
jim
wa4yiz


locked Re: FT4 Output Audio

Bill Somerville
 

On 25/07/2019 16:34, kk5aa_fred via Groups.Io wrote:
Is there a particular reason that the output audio of FT4 has been suppressed?

My output on FT8 can go as high as 80 watts, if I crank it up. Same on JT65 or JT9. If I switch to JTDX, I get the same output capabilities. But, on FT4, the maximum I can generate is 40 watts unless I change the output on the interface. This tells me that the audio output from the software has been decreased for some reason and I would like to know why.

Fred - KK5AA
Fred,

like all the other modes in WSJT-X FT4 generates full scale audio output. I will guess that you have installed the 64-bit Windows build of WSJT-X and have not bothered checking the output in modes other than FT4, you will find that they are all the same. What you are probably seeing is a difference between how the 64-bit Windows version interacts with the Windows audio mixer control. Once you understand this and adjust accordingly there will be no difference. See this message for details:

https://groups.io/g/WSJTX/message/3721

73
Bill
G4WJS.


locked Re: FT4 Output Audio

Michael Black
 

Are you perhaps transmitting at the edges of your bandpass in FT4?

Do you have Fake It or Rig Split turned on in the WSJT-X radio settings?  That solves that problem and allows you to actually transmit outside your bandpass by shifting the base frequency.

de Mike W9MDB




On Thursday, July 25, 2019, 10:34:43 AM CDT, kk5aa_fred via Groups.Io <poppafred@...> wrote:


Is there a particular reason that the output audio of FT4 has been suppressed?

My output on FT8 can go as high as 80 watts, if I crank it up. Same on JT65 or JT9. If I switch to JTDX, I get the same output capabilities. But, on FT4, the maximum I can generate is 40 watts unless I change the output on the interface. This tells me that the audio output from the software has been decreased for some reason and I would like to know why.

Fred - KK5AA
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#3747): https://groups.io/g/WSJTX/message/3747
Mute This Topic: https://groups.io/mt/32599248/212453
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4121090/1473993136/xyzzy [mdblack98@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked FT4 Output Audio

kk5aa_fred
 

Is there a particular reason that the output audio of FT4 has been suppressed?

My output on FT8 can go as high as 80 watts, if I crank it up. Same on JT65 or JT9. If I switch to JTDX, I get the same output capabilities. But, on FT4, the maximum I can generate is 40 watts unless I change the output on the interface. This tells me that the audio output from the software has been decreased for some reason and I would like to know why.

Fred - KK5AA


locked Re: Another case of decoding stopping...

Joe
 

Latest update: As of this morning, business as usual.  I get a hung decode about once every 15 minutes if I am active, often less than that.  If I am just decoding and not transmitting, then it often, but not always, runs much longer, maybe even hours.  When it hangs, restarting DAX always restarts it.  When I run LatencyMon, it seems to happen more frequently, but LM almost always shows an excursion of the "Highest Measured Interrupt to DPC Latency", often in the 20,000 microsecond range.  Flex says DAX is sensitive to this problem if there is a latency over 1000 microseconds.  (But Flex also seems to think that DAX not being able to recover from this is ok with them, since it is MY computer that is the problem!  How late '70s's, from a computer science perspective.)  Keep in mind that this is mostly theory.  While Flex is "aware" they are not saying this is what is happening with WSJT-X.

Specifically: audiodax.sys, txdax.sys, and iqdax.sys all average around .125 microsec until the hangup, whereupon they are usually around 2000-4000 microsecs, respectively.  I just had one hangup a minute ago that showed no anomalies at all on LM.  Go figure.

Here is a typical LM listing before the DAX hang (only a 10 minute run):



And here it is after:



I have backed SSDR down to 2.4.9. No change.  I have backed Windows back down to release 1803. No change.  I have not backed out my driver upgrades for Nvidia, network driver, Intel chipset, and I still have Intel's Speed Shift turned off.  Not much effect.  I am in the process of bringing everything back up to the latest revs.  While this problem has existed for a long time (maybe ever since I fired up SSDR and WSJT-X) it certainly did not happen nearly as frequently.  What used to happen once every day or two now happens within 15-20 minutes, if I am transmitting.  At least my logging software and other apps will have the latest and greatest underneath it all.  Tim at Flex seems to think it is a problem with the Nvidia driver but that didn't change over this whole episode until I upgraded it.  It does show long latencies, but so does NDIS.  I am not sure NVidia is the cause. 

I am ready to reverse roles with my backup ICOM rig, but I hate to admit defeat!