Date   

locked Re: USB MODE #FT8

Lev <leventelist@...>
 

That is data-USB. This is the right mode for FT8. Use the connector on the back to supply audio.

Lev

On Wed, Apr 21, 2021, 09:11 Michael Optie <heymoe1@...> wrote:
My FT-891 goes into D-U mode when running WSJT-X.  I cannot force FT-891 into USB.  What in WJST-X is forcing the FT-891 into the D-U mode?

HELP!!



locked USB MODE #FT8

Michael Optie
 

My FT-891 goes into D-U mode when running WSJT-X.  I cannot force FT-891 into USB.  What in WJST-X is forcing the FT-891 into the D-U mode?

HELP!!


locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Greg
 

Hello Tony!

The frequency list is static, sort of. Using the Settings, you can go in and define other frequencies but I suggest you leave them as is. Most people are transmitting and receiving within the limitations of the base frequency. You can 'fine tune' where you receive and transmit by clicking and shift-clicking (hold shift key while you click with mouse button) respectively in the waterfall portion of the software.

Having a displayed frequency mismatch between the software and the radio could be the reason you are seeing the red mode indicator. If CAT isn't able to tune you to the frequency, adjust your radio to the frequency listed in the software and see if that makes the mode indicator turn color. Check the WSJT-X user manual for the proper frequencies for each band and mode to make sure you are on the right one for your intended use.

I've got a Xiegu G90 and the XGGComms Digimode-4 cable. It took some trial and error to get it setup and working properly, part of the problem is I don't have a permanent shack setup and I am getting RFI wigglies into my 'shack'. Ferrite, and lots of it, have helped squash some of those problems. I also refer back to the WSJT-X user manual and the FT8 Hinson tips for DXers PDF. I will throw a link to the PDF below:

https://g4ifb.com/FT8_Hinson_tips_for_HF_DXers.pdf

73
Greg KJ7AWJ

On Tue, Apr 20, 2021 at 7:55 PM Tony Castelli <kj4joa@...> wrote:
Thanks Pat. The frequency list is static, I can't change anything in it. I was thinking that I should be able to. Am I wrong to think that?

A. J. Castelli 
KJ4JOA
General Class Operator
AEMT







On Tue, Apr 20, 2021 at 5:33 PM PATRICK COKER <n6rmj@...> wrote:
Check your feq list in wsjt
> On Apr 20, 2021, at 3:15 PM, Tony Castelli <kj4joa@...> wrote:
>
> Well, I finally got the waterfall to show up. I am waiting for my new Digimode-4 to show up any day now, hoping THAT will be a logical upgrade from the U5 Link; until then, I need some help.
> I can't receive on anything other than JT 65. If I try to go to another mode, the mode indicator is red (Red not good? Yellow if I select the JT 9 & JT 65 combination)
> I set my receiver for one frequency, i.e. 14.075, but WSJT shows me at 14.072.711.
> I am also not seeing anything in the Band Activity. I can hear it and I can see it on the waterfall, but nothing decodes.
>
> Your expertise regarding any and/or all of the issues is needed and your input will be greatly appreciated.
>
>








locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

Tony Castelli <kj4joa@...>
 

Thanks Pat. The frequency list is static, I can't change anything in it. I was thinking that I should be able to. Am I wrong to think that?

A. J. Castelli 
KJ4JOA
General Class Operator
AEMT







On Tue, Apr 20, 2021 at 5:33 PM PATRICK COKER <n6rmj@...> wrote:
Check your feq list in wsjt
> On Apr 20, 2021, at 3:15 PM, Tony Castelli <kj4joa@...> wrote:
>
> Well, I finally got the waterfall to show up. I am waiting for my new Digimode-4 to show up any day now, hoping THAT will be a logical upgrade from the U5 Link; until then, I need some help.
> I can't receive on anything other than JT 65. If I try to go to another mode, the mode indicator is red (Red not good? Yellow if I select the JT 9 & JT 65 combination)
> I set my receiver for one frequency, i.e. 14.075, but WSJT shows me at 14.072.711.
> I am also not seeing anything in the Band Activity. I can hear it and I can see it on the waterfall, but nothing decodes.
>
> Your expertise regarding any and/or all of the issues is needed and your input will be greatly appreciated.
>
>





locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

PATRICK COKER
 

Check your feq list in wsjt

On Apr 20, 2021, at 3:15 PM, Tony Castelli <kj4joa@...> wrote:

Well, I finally got the waterfall to show up. I am waiting for my new Digimode-4 to show up any day now, hoping THAT will be a logical upgrade from the U5 Link; until then, I need some help.
I can't receive on anything other than JT 65. If I try to go to another mode, the mode indicator is red (Red not good? Yellow if I select the JT 9 & JT 65 combination)
I set my receiver for one frequency, i.e. 14.075, but WSJT shows me at 14.072.711.
I am also not seeing anything in the Band Activity. I can hear it and I can see it on the waterfall, but nothing decodes.

Your expertise regarding any and/or all of the issues is needed and your input will be greatly appreciated.


locked Re: Can't move forward! #Cat_RigControl #NewUser #WSJTX_config

M0PWX
 

A picture paints a thousand word

 

A screen shot of the issue would likely help, as we can see exactly what you are seeing, and probably a screen shot of you “radio” tab in the setting dialogue

 

What are you using for rig control? Flrig?, HRD or something else

 

73

 

Peter

M0PWX

 

From: Tony Castelli

 

Well, I finally got the waterfall to show up. I am waiting for my new Digimode-4 to show up any day now, hoping THAT will be a logical upgrade from the U5 Link; until then, I need some help.
I can't receive on anything other than JT 65. If I try to go to another mode, the mode indicator is red (Red not good? Yellow if I select the JT 9 & JT 65 combination)
I set my receiver for one frequency, i.e. 14.075, but WSJT shows me at 14.072.711. 
I am also not seeing anything in the Band Activity. I can hear it and I can see it on the waterfall, but nothing decodes.

Your expertise regarding any and/or all of the issues is needed and your input will be greatly appreciated.

 


Tony Castelli <kj4joa@...>
 

Well, I finally got the waterfall to show up. I am waiting for my new Digimode-4 to show up any day now, hoping THAT will be a logical upgrade from the U5 Link; until then, I need some help.
I can't receive on anything other than JT 65. If I try to go to another mode, the mode indicator is red (Red not good? Yellow if I select the JT 9 & JT 65 combination)
I set my receiver for one frequency, i.e. 14.075, but WSJT shows me at 14.072.711. 
I am also not seeing anything in the Band Activity. I can hear it and I can see it on the waterfall, but nothing decodes.

Your expertise regarding any and/or all of the issues is needed and your input will be greatly appreciated.


Charlie Hoffman
 

I've had that happen several times and I found that a "RESET" of the IC-7300 cleared up the problem.

If you do a full factory reset, make sure you save all your settings on on an SD card before you start
or you will have to enter them all back in manually.

I eventually found that my problem was caused by a bad factory barrel crimp on the power cord where
the flag fuse was spliced to the power cord.  I re-crimped the connection and have not had another issue.
Up until I corrected that problem, I had thought I had an RFI issue and had snap on ferrites on everything.


Bill Somerville
 

On 20/04/2021 01:53, Mike Cummings wrote:
I'm stumped and can't find anything about this issue after a lot of googling.

I'm on Windows 10 on an ASUS laptop and my rig is an IC-7300.

Suddenly, when I attempt to transmit (FT8) with my IC-7300, I get transmission, but at the end of the cycle, it just keeps transmitting. The only way to stop it is with the TRANSMIT button on the front panel. But after that, PTT control seems to be locked. Then the Test PTT button in Settings is grayed out. If I try exiting WSJT-X and relaunch, I get a message that another instance is running and it asks me if I want to remove the stale lock file. No answer works, and I can't kill it in Task Manager. All I can do is reboot, but then after launching WSJT-X, I just have the same problem.

I've been running FT8 every day for a week without problem. The only thing that's different is that I installed Gridtracker. The problem occurs whether Gridtracker is running or not.

My station isn't permanent. I live in a small rental house with no room for a shack, so I set up outside. I don't have a proper ground, because I can't here. I'm not allowed to drive a ground rod. I'm using an end-fed with my internal tuner. I know it's a compromise antenna. It's what I have for now. It's hard to get my ideal antenna due to rental restrictions and the fact that I'm disabled. I'm just using a USB cable without an intervening interface.

What gets me is that I've made 150 or so QSOs the past few days without problems and I haven't changed anything. I've reinstalled the USB driver, rearranged my USB cable, which had ferrite beads on both ends, and I don't know what else to do. Any ideas would be welcome.

Thanks.

Mike NX7E
Hi Mike,

your symptoms are likely caused by a loss of CAT control due to issues with the virtual serial port. Given it happens while transmitting then RFI is extremely likely to be the root cause. Verify by using reduced power, a dummy load, a different band, or another aerial.

73
Bill
G4WJS.


locked Re: #bugreport ALL.TXT #IssueReport

Tom Melvin
 

Dave sorry disagree

If you ‘filter’ all.txt to get all MSK entries - to see what was sent etc - no date there.
Your argument assumes there will be details ON THE SAME day before/after the MSK entries to allow you to find the date - what is to say the details before (or after) are for the same day.

The log file should show the date/time for each entry.

Tom
GM8MJV

On 20 Apr 2021, at 00:17, Dave Garber <ve3wej@...> wrote:

this has been this way for quite a while, I would have to look at release notes. but sounds normal. if the date does not change why append with it and slow the process..

Dave Garber
VE3WEJ / VE3IE


On Mon, Apr 19, 2021 at 5:47 PM Bill Lederer <w8lvn.9@...> wrote:
This issue still exists for Rc4, but apparently only for MSK144.


Looks fine for FT8, but not MSK144

210419_070415 1.840 Tx FT8 0 0.0 1612 CQ W8LVN EN62
210419_070445 1.840 Tx FT8 0 0.0 1612 CQ W8LVN EN62
210419_070515 1.840 Tx FT8 0 0.0 1612 CQ W8LVN EN62
50.260 Rx MSK144 -6 7.0 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -5 11.3 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -6 9.8 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -5 13.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -2 1.1 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -1 2.5 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -2 0.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144 -7 13.3 1440 VE9GJ K2DRH RRR
50.260 Rx MSK144 -1 26.4 1475 N0AN K1RZ +02
50.260 Rx MSK144 0 23.0 1472 N0AN N1KWF FN32
50.260 Rx MSK144 -1 22.6 1460 N0AN N1KWF FN32
50.260 Rx MSK144 1 28.9 1464 N0AN N1KWF FN32
50.260 Rx MSK144 -8 28.6 1443 Z4VUR/R RH0BDY/R R DH26
50.260 Rx MSK144 8 22.6 1462 VE4CY W9DR EM78
50.260 Rx MSK144 11 22.9 1462 VE4CY W9DR EM78
50.260 Rx MSK144 12 27.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144 15 27.3 1460 VE4CY W9DR EM78
50.260 Rx MSK144 13 15.5 1460 VE4CY W9DR EM78
50.260 Rx MSK144 14 26.1 1462 VE4CY W9DR EM78
50.260 Rx MSK144 3 16.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144 4 16.0 1463 VE4CY W9DR EM78
50.260 Rx MSK144 6 16.6 1461 VE4CY W9DR EM78
50.260 Rx MSK144 7 16.7 1461 VE4CY W9DR EM78
50.260 Rx MSK144 13 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144 14 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144 -3 15.5 1463 VE4CY W9DR EM78
50.260 Rx MSK144 5 20.8 1462 VE4CY W9DR RRR
50.260 Rx MSK144 6 29.2 1462 VE4CY W9DR RRR
50.260 Rx MSK144 7 29.3 1460 VE4CY W9DR RRR
210419_140330 18.100 Rx FT8 -6 0.2 780 N5HHS N3GX R+05
210419_140330 18.100 Rx FT8 -11 0.2 1591 KB2M KI4KDR EM45
210419_140330 18.100 Rx FT8 -12 0.1 1261 CQ N3NVA FN20
210419_140400 10.136 Rx FT8 14 0.1 1328 CQ VA3MJR FN03
210419_140400 10.136 Rx FT8 1 0.1 607 KG0TR VE3RXO R-13

Thanks,
w8lvn


On Mon, Apr 19, 2021 at 10:59 AM Bill Lederer via groups.io<w8lvn.9@...> wrote:
Well, my issue was in the RC3 release. I'm now running with RC4, and will see if it iis still there.

w8lvn

On Mon, Apr 19, 2021 at 6:41 AM Sam Birnbaum via groups.io<w2jdb@...> wrote:
Hi Bill,

I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function.
I found that when I used WSJT-X 2.3 rc1 (or rc2). The Date and time was only included in the TX record that
was written to the All.txt file.

I believe the problem was fixed when 2.3 rc3 was released.

73,

Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: WSJTX@groups.io
Sent: Sun, Apr 18, 2021 9:54 pm
Subject: [WSJTX] #bugreport ALL.TXT

Team:

I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make.

What is a little more odd, this did happen when switching from 160 meter FT8 to 6 meter MSK144.

Is this a known issue?

I have just downloaded and installed the rc4 version in case the issue is resolved.

(I use the ALL.TXT file to recreate QSOs that don't get properly logged due to an xquartz crash. Usually I run WSJTX on Intel NUCs running Ubuntu after doing "ssh -Y <linux-host>" and xterm. Works most of the time, but xquartz on mac has proven to be unexpectedly crash-worthy.)

--w8lvn--

--
--w8lvn--








--
--w8lvn--





--
--w8lvn--





Greg
 

Hello Mike!

I don't have a permanent shack setup either so I run with a bunch of ferrites as well.
Do you have another USB cable you can swap out? Have you tried running at 1 watt to see if the problem persists? Have you tried using a different USB port on your computer? Can you create a common ground from your radio to your laptop with a USB grounding cord and alligator clip attached to your radio ground lug? Try changing things one at a time to see if it resolves the problem. If no single thing works then add another change into the mix but only one at a time as well. Let us know how the troubleshooting goes. 

Also, don't be ashamed of your setup. The best antenna is the one you can put up! The only antennas I can put up in my small backyard are compromise antennas. I still have a handful of FT8 QSLs from Salt Lake City, UT to Japan. Some at 20 watts!

73
Greg KJ7AWJ 


On Mon, Apr 19, 2021, 19:47 Mike Cummings <sciencemc@...> wrote:
I'm stumped and can't find anything about this issue after a lot of googling.

I'm on Windows 10 on an ASUS laptop and my rig is an IC-7300.

Suddenly, when I attempt to transmit (FT8) with my IC-7300, I get transmission, but at the end of the cycle, it just keeps transmitting. The only way to stop it is with the TRANSMIT button on the front panel. But after that, PTT control seems to be locked. Then the Test PTT button in Settings is grayed out. If I try exiting WSJT-X and relaunch, I get a message that another instance is running and it asks me if I want to remove the stale lock file. No answer works, and I can't kill it in Task Manager. All I can do is reboot, but then after launching WSJT-X, I just have the same problem.

I've been running FT8 every day for a week without problem. The only thing that's different is that I installed Gridtracker. The problem occurs whether Gridtracker is running or not.

My station isn't permanent. I live in a small rental house with no room for a shack, so I set up outside. I don't have a proper ground, because I can't here. I'm not allowed to drive a ground rod. I'm using an end-fed with my internal tuner. I know it's a compromise antenna. It's what I have for now. It's hard to get my ideal antenna due to rental restrictions and the fact that I'm disabled. I'm just using a USB cable without an intervening interface.

What gets me is that I've made 150 or so QSOs the past few days without problems and I haven't changed anything. I've reinstalled the USB driver, rearranged my USB cable, which had ferrite beads on both ends, and I don't know what else to do. Any ideas would be welcome.

Thanks.

Mike NX7E



locked Re: Using radios for wajtx and remote #Cat_RigControl

Gerald Klotz
 

I do have power out now both locally on the server and remotely. I am not sure but I believe the problem was with the com ports. I ended up installing a few things then reinstalling it and then renamed the cöm ports for the radio. Windows update is not your friend as far as com ports are involved.

Gerry Klotz

On Apr 19, 2021, at 7:46 PM, Joel <styx@...> wrote:


Gerry

Do you now have power out on transmit - it appeared that was the original problem that you were concerned about?

Joel
AC8WS

On Apr 19, 2021, at 8:19 PM, Gerald Klotz <KB9PKI@...> wrote:

Yes the settings are separate. I have the radios working locally with wsjtx and through rsbs1 locally. The radios now work remotely but I am trying to get FLdigi and flrig set up. 
I have flrig and Fldigi working locally on the 7300 but not on the 9700. I haven’t gotten Fldigi or flrig working remotely yet.

Gerry Klotz
Kb9pki

On Apr 19, 2021, at 6:25 PM, Dave Garber <ve3wej@...> wrote:


are you settings things separate under the configurations tab??

Dave Garber
VE3WEJ / VE3IE


On Tue, Apr 13, 2021 at 4:02 PM Gerald Klotz <KB9PKI@...> wrote:

Good afternoon. I got my income 7300 and 9700 set up and working again but forgot to check output power, which turns out to be zip. 

I went ahead and worked on the icom res-ba1 software and got that working remotely with both radios. I went to do some ft8 and no power out. I know it’s something in the settings somewhere, but I keep missing it. Everything works fine and I. An control both rigs but can’t transmit any power on either radio. Both have their own codec installed and assigned.

When I switch to 144.174 the software switches radios and then to the hf radio for hf freq’s.

Anyone have an idea?














Mike Cummings
 

I'm stumped and can't find anything about this issue after a lot of googling.

I'm on Windows 10 on an ASUS laptop and my rig is an IC-7300.

Suddenly, when I attempt to transmit (FT8) with my IC-7300, I get transmission, but at the end of the cycle, it just keeps transmitting. The only way to stop it is with the TRANSMIT button on the front panel. But after that, PTT control seems to be locked. Then the Test PTT button in Settings is grayed out. If I try exiting WSJT-X and relaunch, I get a message that another instance is running and it asks me if I want to remove the stale lock file. No answer works, and I can't kill it in Task Manager. All I can do is reboot, but then after launching WSJT-X, I just have the same problem.

I've been running FT8 every day for a week without problem. The only thing that's different is that I installed Gridtracker. The problem occurs whether Gridtracker is running or not.

My station isn't permanent. I live in a small rental house with no room for a shack, so I set up outside. I don't have a proper ground, because I can't here. I'm not allowed to drive a ground rod. I'm using an end-fed with my internal tuner. I know it's a compromise antenna. It's what I have for now. It's hard to get my ideal antenna due to rental restrictions and the fact that I'm disabled. I'm just using a USB cable without an intervening interface.

What gets me is that I've made 150 or so QSOs the past few days without problems and I haven't changed anything. I've reinstalled the USB driver, rearranged my USB cable, which had ferrite beads on both ends, and I don't know what else to do. Any ideas would be welcome.

Thanks.

Mike NX7E


locked Re: Using radios for wajtx and remote #Cat_RigControl

Joel
 

Gerry

Do you now have power out on transmit - it appeared that was the original problem that you were concerned about?

Joel
AC8WS

On Apr 19, 2021, at 8:19 PM, Gerald Klotz <KB9PKI@...> wrote:

Yes the settings are separate. I have the radios working locally with wsjtx and through rsbs1 locally. The radios now work remotely but I am trying to get FLdigi and flrig set up. 
I have flrig and Fldigi working locally on the 7300 but not on the 9700. I haven’t gotten Fldigi or flrig working remotely yet.

Gerry Klotz
Kb9pki

On Apr 19, 2021, at 6:25 PM, Dave Garber <ve3wej@...> wrote:


are you settings things separate under the configurations tab??

Dave Garber
VE3WEJ / VE3IE


On Tue, Apr 13, 2021 at 4:02 PM Gerald Klotz <KB9PKI@...> wrote:

Good afternoon. I got my income 7300 and 9700 set up and working again but forgot to check output power, which turns out to be zip. 

I went ahead and worked on the icom res-ba1 software and got that working remotely with both radios. I went to do some ft8 and no power out. I know it’s something in the settings somewhere, but I keep missing it. Everything works fine and I. An control both rigs but can’t transmit any power on either radio. Both have their own codec installed and assigned.

When I switch to 144.174 the software switches radios and then to the hf radio for hf freq’s.

Anyone have an idea?











locked Re: #bugreport ALL.TXT #IssueReport

Sam Birnbaum
 

Hi Bill,

Yes, it is a bug. I would suggest you test the RC release of ver 2.4 and see if it is in there as well.

I had to make special provisions in my Alltext.exe program to accommodate that bug.  

73,
 
Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: main@wsjtx.groups.io
Sent: Mon, Apr 19, 2021 8:11 pm
Subject: Re: [WSJTX] #bugreport ALL.TXT

So if adding the date to the beginning of a log file takes more than a handful of microseconds, I would be surprised. The bulk of time would be actually taking the underlying unix time (in seconds) and converting it to a string. This is already done for the display of the signal on the left panel.

Secondly, the date is not changing on either the 1.840 lines, nor on the 18.100 or the 10.136 FT8 lines, but the time is put on those lines.  Clearly the time changes, however.

Further, for the MSK144 lines, they occupy the clock time between 210419_140330 and 240419_070515, which is on the order of 7 hours. At what time does the line Z4VUR/R RH0BDY/R R DH26 occur? There is no way to tell from ALL.TXT.

Finally, why would it behave differently on FT8 as opposed to MSK144?

With respect to the release notes, for RC3 it says:

 - Repair regression with missing time-stamps in the ALL.TXT journal.

It would appear from my RC3 use and now RC4, that there are situations still exhibiting the behavior.

I am thinking this is a bug.

On Mon, Apr 19, 2021 at 6:18 PM Dave Garber <ve3wej@...> wrote:
this has been this way for quite a while, I would have to look at release notes.  but sounds normal.  if the date does not change why append with it and slow the process..

Dave Garber
VE3WEJ / VE3IE


On Mon, Apr 19, 2021 at 5:47 PM Bill Lederer <w8lvn.9@...> wrote:
This issue still exists for Rc4, but apparently only for MSK144.


Looks fine for FT8, but not MSK144

210419_070415     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070445     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070515     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
50.260 Rx MSK144  -6  7.0 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 11.3 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -6  9.8 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 13.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  1.1 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -1  2.5 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  0.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -7 13.3 1440 VE9GJ K2DRH RRR
50.260 Rx MSK144  -1 26.4 1475 N0AN K1RZ +02
50.260 Rx MSK144   0 23.0 1472 N0AN N1KWF FN32
50.260 Rx MSK144  -1 22.6 1460 N0AN N1KWF FN32
50.260 Rx MSK144   1 28.9 1464 N0AN N1KWF FN32
50.260 Rx MSK144  -8 28.6 1443 Z4VUR/R RH0BDY/R R DH26
50.260 Rx MSK144   8 22.6 1462 VE4CY W9DR EM78
50.260 Rx MSK144  11 22.9 1462 VE4CY W9DR EM78
50.260 Rx MSK144  12 27.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144  15 27.3 1460 VE4CY W9DR EM78
50.260 Rx MSK144  13 15.5 1460 VE4CY W9DR EM78
50.260 Rx MSK144  14 26.1 1462 VE4CY W9DR EM78
50.260 Rx MSK144   3 16.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144   4 16.0 1463 VE4CY W9DR EM78
50.260 Rx MSK144   6 16.6 1461 VE4CY W9DR EM78
50.260 Rx MSK144   7 16.7 1461 VE4CY W9DR EM78
50.260 Rx MSK144  13 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  14 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  -3 15.5 1463 VE4CY W9DR EM78
50.260 Rx MSK144   5 20.8 1462 VE4CY W9DR RRR
50.260 Rx MSK144   6 29.2 1462 VE4CY W9DR RRR
50.260 Rx MSK144   7 29.3 1460 VE4CY W9DR RRR
210419_140330    18.100 Rx FT8     -6  0.2  780 N5HHS N3GX R+05
210419_140330    18.100 Rx FT8    -11  0.2 1591 KB2M KI4KDR EM45
210419_140330    18.100 Rx FT8    -12  0.1 1261 CQ N3NVA FN20
210419_140400    10.136 Rx FT8     14  0.1 1328 CQ VA3MJR FN03
210419_140400    10.136 Rx FT8      1  0.1  607 KG0TR VE3RXO R-13


Thanks,
w8lvn


On Mon, Apr 19, 2021 at 10:59 AM Bill Lederer via groups.io <w8lvn.9=gmail.com@groups.io> wrote:
Well, my issue was in the RC3 release.  I'm now running with RC4, and will see if it iis still there.

w8lvn

On Mon, Apr 19, 2021 at 6:41 AM Sam Birnbaum via groups.io <w2jdb=aol.com@groups.io> wrote:
Hi Bill,

I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function.
I found that when I used WSJT-X  2.3 rc1 (or rc2).  The Date and time was only included in the TX record that
was written to the All.txt file.

I believe the problem was fixed when 2.3 rc3 was released.

73,  

Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: WSJTX@groups.io
Sent: Sun, Apr 18, 2021 9:54 pm
Subject: [WSJTX] #bugreport ALL.TXT

Team:

I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make.

What is a little more odd, this did happen when switching from 160 meter FT8 to 6 meter MSK144.

Is this a known issue?

I have just downloaded and installed the rc4 version in case the issue is resolved.

(I use the ALL.TXT file to recreate QSOs that don't get properly logged due to an xquartz crash. Usually I run WSJTX on Intel NUCs running Ubuntu after doing "ssh -Y <linux-host>" and xterm. Works most of the time, but xquartz on mac has proven to be unexpectedly crash-worthy.)

--w8lvn--

--
--w8lvn--








--
--w8lvn--





--
--w8lvn--








--
--w8lvn--




locked Re: Using radios for wajtx and remote #Cat_RigControl

Gerald Klotz
 

Yes the settings are separate. I have the radios working locally with wsjtx and through rsbs1 locally. The radios now work remotely but I am trying to get FLdigi and flrig set up. 
I have flrig and Fldigi working locally on the 7300 but not on the 9700. I haven’t gotten Fldigi or flrig working remotely yet.

Gerry Klotz
Kb9pki

On Apr 19, 2021, at 6:25 PM, Dave Garber <ve3wej@...> wrote:


are you settings things separate under the configurations tab??

Dave Garber
VE3WEJ / VE3IE


On Tue, Apr 13, 2021 at 4:02 PM Gerald Klotz <KB9PKI@...> wrote:

Good afternoon. I got my income 7300 and 9700 set up and working again but forgot to check output power, which turns out to be zip. 

I went ahead and worked on the icom res-ba1 software and got that working remotely with both radios. I went to do some ft8 and no power out. I know it’s something in the settings somewhere, but I keep missing it. Everything works fine and I. An control both rigs but can’t transmit any power on either radio. Both have their own codec installed and assigned.

When I switch to 144.174 the software switches radios and then to the hf radio for hf freq’s.

Anyone have an idea?








locked Re: #bugreport ALL.TXT #IssueReport

Bill Lederer
 

So if adding the date to the beginning of a log file takes more than a handful of microseconds, I would be surprised. The bulk of time would be actually taking the underlying unix time (in seconds) and converting it to a string. This is already done for the display of the signal on the left panel.

Secondly, the date is not changing on either the 1.840 lines, nor on the 18.100 or the 10.136 FT8 lines, but the time is put on those lines.  Clearly the time changes, however.

Further, for the MSK144 lines, they occupy the clock time between 210419_140330 and 240419_070515, which is on the order of 7 hours. At what time does the line Z4VUR/R RH0BDY/R R DH26 occur? There is no way to tell from ALL.TXT.

Finally, why would it behave differently on FT8 as opposed to MSK144?

With respect to the release notes, for RC3 it says:

 - Repair regression with missing time-stamps in the ALL.TXT journal.

It would appear from my RC3 use and now RC4, that there are situations still exhibiting the behavior.

I am thinking this is a bug.

On Mon, Apr 19, 2021 at 6:18 PM Dave Garber <ve3wej@...> wrote:
this has been this way for quite a while, I would have to look at release notes.  but sounds normal.  if the date does not change why append with it and slow the process..

Dave Garber
VE3WEJ / VE3IE


On Mon, Apr 19, 2021 at 5:47 PM Bill Lederer <w8lvn.9@...> wrote:
This issue still exists for Rc4, but apparently only for MSK144.


Looks fine for FT8, but not MSK144

210419_070415     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070445     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070515     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
50.260 Rx MSK144  -6  7.0 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 11.3 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -6  9.8 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 13.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  1.1 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -1  2.5 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  0.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -7 13.3 1440 VE9GJ K2DRH RRR
50.260 Rx MSK144  -1 26.4 1475 N0AN K1RZ +02
50.260 Rx MSK144   0 23.0 1472 N0AN N1KWF FN32
50.260 Rx MSK144  -1 22.6 1460 N0AN N1KWF FN32
50.260 Rx MSK144   1 28.9 1464 N0AN N1KWF FN32
50.260 Rx MSK144  -8 28.6 1443 Z4VUR/R RH0BDY/R R DH26
50.260 Rx MSK144   8 22.6 1462 VE4CY W9DR EM78
50.260 Rx MSK144  11 22.9 1462 VE4CY W9DR EM78
50.260 Rx MSK144  12 27.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144  15 27.3 1460 VE4CY W9DR EM78
50.260 Rx MSK144  13 15.5 1460 VE4CY W9DR EM78
50.260 Rx MSK144  14 26.1 1462 VE4CY W9DR EM78
50.260 Rx MSK144   3 16.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144   4 16.0 1463 VE4CY W9DR EM78
50.260 Rx MSK144   6 16.6 1461 VE4CY W9DR EM78
50.260 Rx MSK144   7 16.7 1461 VE4CY W9DR EM78
50.260 Rx MSK144  13 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  14 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  -3 15.5 1463 VE4CY W9DR EM78
50.260 Rx MSK144   5 20.8 1462 VE4CY W9DR RRR
50.260 Rx MSK144   6 29.2 1462 VE4CY W9DR RRR
50.260 Rx MSK144   7 29.3 1460 VE4CY W9DR RRR
210419_140330    18.100 Rx FT8     -6  0.2  780 N5HHS N3GX R+05
210419_140330    18.100 Rx FT8    -11  0.2 1591 KB2M KI4KDR EM45
210419_140330    18.100 Rx FT8    -12  0.1 1261 CQ N3NVA FN20
210419_140400    10.136 Rx FT8     14  0.1 1328 CQ VA3MJR FN03
210419_140400    10.136 Rx FT8      1  0.1  607 KG0TR VE3RXO R-13


Thanks,
w8lvn


On Mon, Apr 19, 2021 at 10:59 AM Bill Lederer via groups.io <w8lvn.9=gmail.com@groups.io> wrote:
Well, my issue was in the RC3 release.  I'm now running with RC4, and will see if it iis still there.

w8lvn

On Mon, Apr 19, 2021 at 6:41 AM Sam Birnbaum via groups.io <w2jdb=aol.com@groups.io> wrote:
Hi Bill,

I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function.
I found that when I used WSJT-X  2.3 rc1 (or rc2).  The Date and time was only included in the TX record that
was written to the All.txt file.

I believe the problem was fixed when 2.3 rc3 was released.

73,  

Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: WSJTX@groups.io
Sent: Sun, Apr 18, 2021 9:54 pm
Subject: [WSJTX] #bugreport ALL.TXT

Team:

I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make.

What is a little more odd, this did happen when switching from 160 meter FT8 to 6 meter MSK144.

Is this a known issue?

I have just downloaded and installed the rc4 version in case the issue is resolved.

(I use the ALL.TXT file to recreate QSOs that don't get properly logged due to an xquartz crash. Usually I run WSJTX on Intel NUCs running Ubuntu after doing "ssh -Y <linux-host>" and xterm. Works most of the time, but xquartz on mac has proven to be unexpectedly crash-worthy.)

--w8lvn--

--
--w8lvn--








--
--w8lvn--





--
--w8lvn--








--
--w8lvn--


locked Re: Using radios for wajtx and remote #Cat_RigControl

Dave Garber
 

are you settings things separate under the configurations tab??

Dave Garber
VE3WEJ / VE3IE


On Tue, Apr 13, 2021 at 4:02 PM Gerald Klotz <KB9PKI@...> wrote:

Good afternoon. I got my income 7300 and 9700 set up and working again but forgot to check output power, which turns out to be zip. 

I went ahead and worked on the icom res-ba1 software and got that working remotely with both radios. I went to do some ft8 and no power out. I know it’s something in the settings somewhere, but I keep missing it. Everything works fine and I. An control both rigs but can’t transmit any power on either radio. Both have their own codec installed and assigned.

When I switch to 144.174 the software switches radios and then to the hf radio for hf freq’s.

Anyone have an idea?





locked Re: #bugreport ALL.TXT #IssueReport

Sam Birnbaum
 

I has not been this way for a long time. It was a bug that was corrected but seems to be still in the version that bill is using.
I was running the Windows version and it was corrected in a later RC release. 
If appending the date and time slows the process on your PC, then you have a problem with your hardware.

73, 

Sam W2JDB



-----Original Message-----
From: Dave Garber <ve3wej@...>
To: WSJT-x group <main@wsjtx.groups.io>
Sent: Mon, Apr 19, 2021 7:17 pm
Subject: Re: [WSJTX] #bugreport ALL.TXT

this has been this way for quite a while, I would have to look at release notes.  but sounds normal.  if the date does not change why append with it and slow the process..

Dave Garber
VE3WEJ / VE3IE


On Mon, Apr 19, 2021 at 5:47 PM Bill Lederer <w8lvn.9@...> wrote:
This issue still exists for Rc4, but apparently only for MSK144.


Looks fine for FT8, but not MSK144

210419_070415     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070445     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070515     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
50.260 Rx MSK144  -6  7.0 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 11.3 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -6  9.8 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 13.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  1.1 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -1  2.5 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  0.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -7 13.3 1440 VE9GJ K2DRH RRR
50.260 Rx MSK144  -1 26.4 1475 N0AN K1RZ +02
50.260 Rx MSK144   0 23.0 1472 N0AN N1KWF FN32
50.260 Rx MSK144  -1 22.6 1460 N0AN N1KWF FN32
50.260 Rx MSK144   1 28.9 1464 N0AN N1KWF FN32
50.260 Rx MSK144  -8 28.6 1443 Z4VUR/R RH0BDY/R R DH26
50.260 Rx MSK144   8 22.6 1462 VE4CY W9DR EM78
50.260 Rx MSK144  11 22.9 1462 VE4CY W9DR EM78
50.260 Rx MSK144  12 27.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144  15 27.3 1460 VE4CY W9DR EM78
50.260 Rx MSK144  13 15.5 1460 VE4CY W9DR EM78
50.260 Rx MSK144  14 26.1 1462 VE4CY W9DR EM78
50.260 Rx MSK144   3 16.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144   4 16.0 1463 VE4CY W9DR EM78
50.260 Rx MSK144   6 16.6 1461 VE4CY W9DR EM78
50.260 Rx MSK144   7 16.7 1461 VE4CY W9DR EM78
50.260 Rx MSK144  13 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  14 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  -3 15.5 1463 VE4CY W9DR EM78
50.260 Rx MSK144   5 20.8 1462 VE4CY W9DR RRR
50.260 Rx MSK144   6 29.2 1462 VE4CY W9DR RRR
50.260 Rx MSK144   7 29.3 1460 VE4CY W9DR RRR
210419_140330    18.100 Rx FT8     -6  0.2  780 N5HHS N3GX R+05
210419_140330    18.100 Rx FT8    -11  0.2 1591 KB2M KI4KDR EM45
210419_140330    18.100 Rx FT8    -12  0.1 1261 CQ N3NVA FN20
210419_140400    10.136 Rx FT8     14  0.1 1328 CQ VA3MJR FN03
210419_140400    10.136 Rx FT8      1  0.1  607 KG0TR VE3RXO R-13

Thanks,
w8lvn


On Mon, Apr 19, 2021 at 10:59 AM Bill Lederer via groups.io <w8lvn.9=gmail.com@groups.io> wrote:
Well, my issue was in the RC3 release.  I'm now running with RC4, and will see if it iis still there.

w8lvn

On Mon, Apr 19, 2021 at 6:41 AM Sam Birnbaum via groups.io <w2jdb=aol.com@groups.io> wrote:
Hi Bill,

I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function.
I found that when I used WSJT-X  2.3 rc1 (or rc2).  The Date and time was only included in the TX record that
was written to the All.txt file.

I believe the problem was fixed when 2.3 rc3 was released.

73,  

Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: WSJTX@groups.io
Sent: Sun, Apr 18, 2021 9:54 pm
Subject: [WSJTX] #bugreport ALL.TXT

Team:

I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make.

What is a little more odd, this did happen when switching from 160 meter FT8 to 6 meter MSK144.

Is this a known issue?

I have just downloaded and installed the rc4 version in case the issue is resolved.

(I use the ALL.TXT file to recreate QSOs that don't get properly logged due to an xquartz crash. Usually I run WSJTX on Intel NUCs running Ubuntu after doing "ssh -Y <linux-host>" and xterm. Works most of the time, but xquartz on mac has proven to be unexpectedly crash-worthy.)

--w8lvn--

--
--w8lvn--








--
--w8lvn--





--
--w8lvn--







locked Re: #bugreport ALL.TXT #IssueReport

Dave Garber
 

this has been this way for quite a while, I would have to look at release notes.  but sounds normal.  if the date does not change why append with it and slow the process..

Dave Garber
VE3WEJ / VE3IE


On Mon, Apr 19, 2021 at 5:47 PM Bill Lederer <w8lvn.9@...> wrote:
This issue still exists for Rc4, but apparently only for MSK144.


Looks fine for FT8, but not MSK144

210419_070415     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070445     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
210419_070515     1.840 Tx FT8      0  0.0 1612 CQ W8LVN EN62
50.260 Rx MSK144  -6  7.0 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 11.3 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -6  9.8 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -5 13.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  1.1 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -1  2.5 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -2  0.7 1440 VE9GJ K2DRH EN41
50.260 Rx MSK144  -7 13.3 1440 VE9GJ K2DRH RRR
50.260 Rx MSK144  -1 26.4 1475 N0AN K1RZ +02
50.260 Rx MSK144   0 23.0 1472 N0AN N1KWF FN32
50.260 Rx MSK144  -1 22.6 1460 N0AN N1KWF FN32
50.260 Rx MSK144   1 28.9 1464 N0AN N1KWF FN32
50.260 Rx MSK144  -8 28.6 1443 Z4VUR/R RH0BDY/R R DH26
50.260 Rx MSK144   8 22.6 1462 VE4CY W9DR EM78
50.260 Rx MSK144  11 22.9 1462 VE4CY W9DR EM78
50.260 Rx MSK144  12 27.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144  15 27.3 1460 VE4CY W9DR EM78
50.260 Rx MSK144  13 15.5 1460 VE4CY W9DR EM78
50.260 Rx MSK144  14 26.1 1462 VE4CY W9DR EM78
50.260 Rx MSK144   3 16.0 1462 VE4CY W9DR EM78
50.260 Rx MSK144   4 16.0 1463 VE4CY W9DR EM78
50.260 Rx MSK144   6 16.6 1461 VE4CY W9DR EM78
50.260 Rx MSK144   7 16.7 1461 VE4CY W9DR EM78
50.260 Rx MSK144  13 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  14 18.4 1463 VE4CY W9DR EM78
50.260 Rx MSK144  -3 15.5 1463 VE4CY W9DR EM78
50.260 Rx MSK144   5 20.8 1462 VE4CY W9DR RRR
50.260 Rx MSK144   6 29.2 1462 VE4CY W9DR RRR
50.260 Rx MSK144   7 29.3 1460 VE4CY W9DR RRR
210419_140330    18.100 Rx FT8     -6  0.2  780 N5HHS N3GX R+05
210419_140330    18.100 Rx FT8    -11  0.2 1591 KB2M KI4KDR EM45
210419_140330    18.100 Rx FT8    -12  0.1 1261 CQ N3NVA FN20
210419_140400    10.136 Rx FT8     14  0.1 1328 CQ VA3MJR FN03
210419_140400    10.136 Rx FT8      1  0.1  607 KG0TR VE3RXO R-13


Thanks,
w8lvn


On Mon, Apr 19, 2021 at 10:59 AM Bill Lederer via groups.io <w8lvn.9=gmail.com@groups.io> wrote:
Well, my issue was in the RC3 release.  I'm now running with RC4, and will see if it iis still there.

w8lvn

On Mon, Apr 19, 2021 at 6:41 AM Sam Birnbaum via groups.io <w2jdb=aol.com@groups.io> wrote:
Hi Bill,

I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function.
I found that when I used WSJT-X  2.3 rc1 (or rc2).  The Date and time was only included in the TX record that
was written to the All.txt file.

I believe the problem was fixed when 2.3 rc3 was released.

73,  

Sam W2JDB



-----Original Message-----
From: Bill Lederer <w8lvn.9@...>
To: WSJTX@groups.io
Sent: Sun, Apr 18, 2021 9:54 pm
Subject: [WSJTX] #bugreport ALL.TXT

Team:

I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make.

What is a little more odd, this did happen when switching from 160 meter FT8 to 6 meter MSK144.

Is this a known issue?

I have just downloaded and installed the rc4 version in case the issue is resolved.

(I use the ALL.TXT file to recreate QSOs that don't get properly logged due to an xquartz crash. Usually I run WSJTX on Intel NUCs running Ubuntu after doing "ssh -Y <linux-host>" and xterm. Works most of the time, but xquartz on mac has proven to be unexpectedly crash-worthy.)

--w8lvn--

--
--w8lvn--








--
--w8lvn--





--
--w8lvn--



12521 - 12540 of 36729