Date   

Locked Re: FT991a and WSJT-x 2.1.2 No Output Power

WØIY
 

I'm trying to get a RPI working with my FT991. I'm just using the single USB connection from the FT to Pi.
Rx is working ok, but Tx is not, with the radio in USB mode. If I change to Data/PKT then it DOES Tx, but the Rx bw is limited to Narrow. I will try a few more settings in the FT.

btw - in the RPi (running Raspbian), I selected USB0 for the comm to the radio and Audio is hw:CARD-CODEC DEV-0


Locked transmit sequence lockup

Matthew Chambers NR0Q
 

I've been having this occur with significant frequency with my QSO partners, and saw in another group that others where having this issue with WSJT-X. I'm running JTDX and have not seen my end have this behavior unless AutoSeq is turned off.
bigbug.png
It ended up taking me over 10min to complete this QSO, I would go back to calling CQ but JTDX would go right back to W7PC when he called me again even if other stations called me. I was locked in this back and forth and had no way to break out of it until the QSO was completed. I've had this same situation happen dozens of times over the last few days and gets super frustrating when I'm calling CQ DX, and a stateside station comes back to me, locking me in a 20-30min long QSO attempt with them and the DX I was wanting to work would fade in and out. Any word on if this is a known bug to the developers and if there's an estimated time to fix?

Matthew Chambers, CBT, NR0Q
Owner/Engineer
M Chambers Communications Engineering LLC
PO BOX 855, Moberly, MO 65270
Mobile (660)415-5620


Locked Re: WSJTX_2-2-0-RC1 dont start ---

Walter OE6IWG (JN77pk)
 

Haris wrote:
 
> "When the decimal point in regional settings is set to "." (period) we have the not launching problem.
> When the decimal point in regional settings is set to "," (comma) the program launches as it should.

the same here:
i checked this, changed from "." to "," AND NOW......... WSJTx starts and works :-))

it takes 65.524 kb in the Taskmanager

> "The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation."

i think the same was here,

on my other PC was the "," WSJTx = startet
here on the 1st PC was the "." - WSJTx = not startet

so, that was the problem :-)

@Haris
i*m abt 2 weeks in the middle of september near PortoHelios, take a boat and came over, there are waiting 1 or 2 beer for you   hihi

@Bill,
mny tnx 2 u and the group for the UFB work with WSJTx

@John - N7GHZ
 tnx 2 u for the tipp with the international settings(!)

-- 
73 de Walter - OE6IWG


Locked Off topic looking for help with R9 antenna

Gerald Klotz
 

Forgive me for being off topic but I am having trouble with a Cushcraft R9 antenna assembly and lint find any type of group like this for help.

If you have familiarity with tuning the 30,40 and 80 meter band of this antenna, please email me directly instead of bothering everyone with an off topic.

If this request violates anything please remove it.

Gerry
Kb9pki


Locked Re: 2.2.0-rc1

Hasan Schiers N0AN
 

...and one other note:

Far fewer -24 decodes than I typically get. I don't know if the scale has changed or what, but the difference is striking. I have always gotten several per sequence on 20m no matter what time of day. I just operated for half an hour and saw a total of two -24 decodes.

73, N0AN

Hasan


On Wed, May 13, 2020 at 1:24 PM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:

Gary,
I am seeing the same thing on 20m crowded band. I am seeing MANY more -19 to -23 decodes than I ever have before in a typical sequence. 

At 1800z, 20m, I am seeing almost no positive SNR's, and even those are just +2 to +4...35 decodes per sequence or more.

My general impressions:

1. Many more total decodes per sequence
2. Many more -17 or weaker decodes per sequence.
3. Much faster decoding and presentation of same.
4. Double peak of CPU use at the two points:

At the 11 second blue light mark: 75%
At the 2nd blue light: 40%
Idling (prior to 11 sec): 7%

Intel Core I5-3470  3.2 GHz , 8 GB Ram Win10 Pro, DxLabSuites, JTAlert, Multiple Tabs of Browser window open

Very impressive, indeed!
73, N0AN
Hasan


On Mon, May 11, 2020 at 5:05 PM Gary Gorniak <w9bs@...> wrote:

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS

 




Locked Re: TS440s (Was Re: WSJT-X 2.2.0-rc1)

JP Tucson, AZ
 

Hi Bill,

For the record... 

I was wrong! 

I called Kenwood U.S.A. this morning for some clarifications.

My rig; which s/n starts with 711xxxx - was manufactured in 1986. Production of the TS-440 ended in 1990.

Where we all got bad info from, there was only 1 TS-440 in production; and they were ALL TS-440S's - - - apparently some lazy folks who just left off the "S" in software & websites, magazines, etc.

So since they started production in 1982, that would put mine at around the midline of production.

Hopefully this info helps.

I really hate it when people give us all bad info, leading to confusion.


So really, the wsjt-x rig selection should read 440S...

Now, that leaves the question still as to why it works in N1MM, appears to respond according to the rigctl tests last night, but won't do a thing during wsjt-x ops...

It's a head scratcher...

Thanks,



73 - John - N7GHZ


On Tue, May 12, 2020, 8:23 PM Bill Somerville <g4wjs@...> wrote:
On 13/05/2020 04:18, JP Tucson, AZ wrote:
Ok, there is it...  grrrgh!

Here is what I got: be ready to get dizzy...

d:\HAM RADIO stuff\WSJT-X\WSJT-X 2.2.0-rc (beta)\wsjtx\bin>rigctl-wsjtx -m 2002 -r COM7 -s 4800 -Cserial_handshake=Hardware -vvvvv -Z f

Hi John,

thanks for that. Now try it again with this command:

rigctl-wsjtx -m 2002 -r COM7 -s 4800 -vvvvv -Z f

The difference being that hardware handshaking may not be needed with your CAT interface. Some loop RTS/CTS at the rig end to free up both DTR and RTS for switching PTT etc.

73
Bill
G4WJS.



Locked Re: WSJTX_2-2-0-RC1 dont start ---

Haris SV1GRB
 

IC-7300 using a single USB cable with CAT command for PTT
image.png

Haris
SV1GRB



Στις Τετ, 13 Μαΐ 2020 στις 9:41 μ.μ., ο/η Bill Somerville <g4wjs@...> έγραψε:

On 13/05/2020 18:27, Haris SV1GRB wrote:
When the decimal point in regional settings is set to "." (period) we have the not launching problem.
When the decimal point in regional settings is set to "," (comma) the program launches as it should.

The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation.
It would be very convenient to be able to work with both settings.

Haris
SV1GRB

Hi Haris,

what is your rig CAT control arrangement please?

73
Bill
G4WJS.



Locked Re: WSJTX_2-2-0-RC1 dont start ---

Bill Somerville
 

On 13/05/2020 18:27, Haris SV1GRB wrote:
When the decimal point in regional settings is set to "." (period) we have the not launching problem.
When the decimal point in regional settings is set to "," (comma) the program launches as it should.

The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation.
It would be very convenient to be able to work with both settings.

Haris
SV1GRB

Hi Haris,

what is your rig CAT control arrangement please?

73
Bill
G4WJS.


Locked Re: FT8 channels (was TS440s (Was Re: WSJT-X 2.2.0-rc1))

Reino Talarmo
 

Hi John,

Your implied proposal using e.g. 50 Hz channels for FT8 to prevent ’non-exact’ overlapping signals may or may not improve band ‘throughput’. But there is a major difficulty in its implementation using typical Ham radios. To my knowledge frequency accuracy of most rigs is a few ppm. That means an absolute accuracy at 10 MHz is a few tens of hertz. If everybody will use their rig’s 50 Hz ticks, the end result would be almost even distribution of transmit frequencies. I don’t want to have a huge fight about frequency correctness of station and no channeling should be recommended. Sure at 137 kHz situation is different, but also much less users.
Of course it is nice to set your frequency in a free ‘slot’ between other signals you happen to see. A DX station may have a totally different view of transmit signal locations.

 

73, Reino OH3mA

 

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of JP Tucson, AZ
Sent: 13. toukokuuta 2020 17:19
To: WSJTX@groups.io
Subject: Re: [WSJTX] TS440s (Was Re: WSJT-X 2.2.0-rc1)

 

Hi Bill, 

 

Just saw you answer another OM;

 

Mostly unrelated to that, behavior...

 

Is there a 'proper' location to set down your signal other than not on top of other tx's? 

 

Meaning; is it more appropriate to say between the tick marks, or split them?

 

Or put this way... I have a large display so I set my waterfall @ 2bin which results in a display from abt 100Hz to 2600Hz - with tick marks convieniently at 50Hz spacing; therefore, I place my tx bracket - 'in the lane' between the tick marks, or 'on the 50s', if you prefer.  However; I see more than a few users that 'split the tick marks'. (On the 25s...) or as I put it, all over the road & crashing over other stations. (I suspect they drive their vehicles in the same fashion!)

 

I have to say that wsjt-x has an amazing ability to usually pull out & decode from the background QRM! But not always... I have lost so many important dxcc type qso's due to what can only be described as discourteousness!

 

Anyway, how shall we drive? Within the lanes, or all over the place? What say you (even if you drive on the wrong side of the road over there... haha...).

 

Really just looking for advice in order for all of us to use the same method to reduce QRM & frustrations...

 

 

73 - John - N7GHZ

 

On Wed, May 13, 2020, 6:07 AM Bill 

Somerville <g4wjs@...> wrote:

On 13/05/2020 13:33, Joe Subich, W4TV wrote:
> Unfortunately, there seems to be something odd with your TS-440
> - perhaps a very old version of the firmware that does not respond
> to the AI; inquiry.  Bill would need to answer whether that is a
> critical failure.

Hi Joe,

the non-response to an AI; query is fine, only much later rigs support
that, Hamlib tries that query so it can restore the AI state on exit.
The AI0; command does work which is expected. The diagnostic worked as
expected, i.e. just fine, when run without hardware flow control. So far
I don't see a problem but we need to look at the response to other CAT
commands for further diagnosis.

73
Bill
G4WJS.


Locked Re: 2.2.0-rc1

Hasan Schiers N0AN
 

Gary,
I am seeing the same thing on 20m crowded band. I am seeing MANY more -19 to -23 decodes than I ever have before in a typical sequence. 

At 1800z, 20m, I am seeing almost no positive SNR's, and even those are just +2 to +4...35 decodes per sequence or more.

My general impressions:

1. Many more total decodes per sequence
2. Many more -17 or weaker decodes per sequence.
3. Much faster decoding and presentation of same.
4. Double peak of CPU use at the two points:

At the 11 second blue light mark: 75%
At the 2nd blue light: 40%
Idling (prior to 11 sec): 7%

Intel Core I5-3470  3.2 GHz , 8 GB Ram Win10 Pro, DxLabSuites, JTAlert, Multiple Tabs of Browser window open

Very impressive, indeed!
73, N0AN
Hasan


On Mon, May 11, 2020 at 5:05 PM Gary Gorniak <w9bs@...> wrote:

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS

 



Locked Re: WSJTX_2-2-0-RC1 dont start ---

Haris SV1GRB
 

I agree with you Bill.
I tried uninstall and then install again this particular application (anytone 878 CPS) and this time it did not changed the decimal point setting. Maybe a previous version did this dirty job.

The good part of all this is that you developers have something in your hands now :-)


Haris
SV1GRB



Στις Τετ, 13 Μαΐ 2020 στις 8:31 μ.μ., ο/η Bill Somerville <g4wjs@...> έγραψε:

Haris,

no user application installer should be changing the regional setting for you PC account, that is very bad behaviour!

73
Bill
G4WJS.

On 13/05/2020 18:27, Haris SV1GRB wrote:
When the decimal point in regional settings is set to "." (period) we have the not launching problem.
When the decimal point in regional settings is set to "," (comma) the program launches as it should.

The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation.
It would be very convenient to be able to work with both settings.

Haris
SV1GRB



Στις Τετ, 13 Μαΐ 2020 στις 5:49 μ.μ., ο/η Andy McMullin <Andy.McMullin@...> έγραψε:
John,

While that might sound like a good reason — I am running the “international” version of Windows 10: set for the UK, with a UK keyboard, UK date format etc. and version 2.2.0-rc1 (64 bit) is working just fine here. Both windows open as per normal. 

One thing I did do for installation was to uninstall the previous version though: I did not install “over the top”; that had caused me troubles in the past.

I hope this helps identify the issue better.

Regards
Andy, G8TQH




Walt (KK4DF)
 
Edited

It will only exhibit this behavior if the RR73 to the other station shows up in MY RX Frequency window.  If I were to move my Rx frequency from the station I'm working while they complete their QSO, my transmissions continue with my Tx 3 transmissions.  But if I am "listening" in on their conversation when it ends, it resets my sequence to Tx 1.  Not what I would want or expect, and it's difficult to catch, as I have zero seconds to prevent this when it occurs.  I accept your explanation to not want to create a QSO machine, but I would still consider this a "bug" since the RR73 was not to my callsign.


Locked Re: WSJTX_2-2-0-RC1 dont start ---

Bill Somerville
 

Haris,

no user application installer should be changing the regional setting for you PC account, that is very bad behaviour!

73
Bill
G4WJS.

On 13/05/2020 18:27, Haris SV1GRB wrote:

When the decimal point in regional settings is set to "." (period) we have the not launching problem.
When the decimal point in regional settings is set to "," (comma) the program launches as it should.

The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation.
It would be very convenient to be able to work with both settings.

Haris
SV1GRB



Στις Τετ, 13 Μαΐ 2020 στις 5:49 μ.μ., ο/η Andy McMullin <Andy.McMullin@...> έγραψε:
John,

While that might sound like a good reason — I am running the “international” version of Windows 10: set for the UK, with a UK keyboard, UK date format etc. and version 2.2.0-rc1 (64 bit) is working just fine here. Both windows open as per normal. 

One thing I did do for installation was to uninstall the previous version though: I did not install “over the top”; that had caused me troubles in the past.

I hope this helps identify the issue better.

Regards
Andy, G8TQH



Locked Re: WSJTX_2-2-0-RC1 dont start ---

Haris SV1GRB
 

When the decimal point in regional settings is set to "." (period) we have the not launching problem.
When the decimal point in regional settings is set to "," (comma) the program launches as it should.

The default decimal point for the Greek regional settings is the "," (comma) but another transceiver programming software forces this setting to "." (period) during the installation.
It would be very convenient to be able to work with both settings.

Haris
SV1GRB



Στις Τετ, 13 Μαΐ 2020 στις 5:49 μ.μ., ο/η Andy McMullin <Andy.McMullin@...> έγραψε:

John,

While that might sound like a good reason — I am running the “international” version of Windows 10: set for the UK, with a UK keyboard, UK date format etc. and version 2.2.0-rc1 (64 bit) is working just fine here. Both windows open as per normal. 

One thing I did do for installation was to uninstall the previous version though: I did not install “over the top”; that had caused me troubles in the past.

I hope this helps identify the issue better.

Regards
Andy, G8TQH



Locked Re: WSJTX_2-2-0-RC1 dont start ---

Glynn
 

Hi Bill,

Tried again but the problem remains. Nothing at all in the Windows Event Log Application, wsjt.exe no events for it.
Have tried turning off the Firewall but that has no effect, also tried running it as Administrator.
After the programme loads it asks if you want to Run it, click on Run, the little Bluish circle that spins comes up but disappears after a few seconds, the same when I click on the Desktop Icon for WSJT, little blue circle then zilch.
Frustrating.

73 Glynn GW4MVA


Locked Re: Transmit Delay after Double Click (WSJT-X 2.2.0-rc1)

Dave (NK7Z)
 

Hi Jeff,

I see the first pass decode is being presented at around say :12 seconds into the clock cycle, not :14 seconds after the cycle starts. This is sooner than it was in the previous version, by a few seconds. This make it look like a few seconds delay has been added, when in reality the transmit cycle is being held until the next :00 point.

Could this be what you are seeing?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/13/20 6:27 AM, Jeff, W8TB via groups.io wrote:
Just an observation, when double-clicking on a callsign with 2.2.0-rc1, there is a noticeable delay before the rig goes in to transmit.I switched back to the 2.1.2 version to test and compare and it is back to normal, which is nearly immediate.
Rig: IC-7300, connected USB to i5 PC
Jeff


Locked Re: Transmit Delay after Double Click (WSJT-X 2.2.0-rc1)

Jeff, W8TB
 

Thank you! That makes perfect sense.  It just didn't dawn on me that the decodes would be so quick that I could be ahead of the curve for transmitting.  Excellent!


Locked Re: callsign confusion in WSJT-X

Bill Somerville
 

On 13/05/2020 17:59, Tapio OH3HN wrote:
Bill,

With v.2.1.2

--
73 de Tapio at station OH3HN
Hi Tapio,

thanks for clarifying that.

73
Bill
G4WJS.


Locked Re: callsign confusion in WSJT-X

Tapio OH3HN
 

Bill,

With v.2.1.2

--
73 de Tapio at station OH3HN


Bill Somerville
 

On 13/05/2020 17:31, groups@... wrote:
On 13/05/2020 14:20, Bill Somerville wrote:
On 13/05/2020 12:56, wewilsonjr@... wrote:
I've noticed what I perceive as odd behavior of the Auto Seq function.  When the other station has responded with their report and I'm sending mine (Tx 3), they will sometimes temporarily go work another station as band conditions change.  As soon as they send their RR73 message to the OTHER station, my Auto Seq goes immediately back to Tx 1, essentially starting my QSO at the beginning.  If I catch this quickly, I will click Tx 3 to resume sending their report and complete the QSO.

Is this the planned behavior, or is there something I can do about this with some different option choices?

Hi OM,

you are correct that this behaviour is unhelpful, it is one of the several edge cases where we expect the operator to be alert and select the correct response. I hope you understand that we do not want to create an automated QSO machine, so we do not consider such issues to be a high priority.

73
Bill
G4WJS.


I've encountered a 2 or 3 stations in the RSGB FT4 contests who seem to be deliberately running two QSOs on alternate transmit cycles.  I presume there is some application which allows the to do this?

Hi OM,

more likely slick mouse work with auto sequencing disabled and manual logging. In general double-clicking a decoded message will select the right reply to transmit, regardless of QSO partner.

73
Bill
G4WJS.