Date   

locked Re: Upgrading from v2.12 to 2.3 Hamlib error #Cat_RigControl

reg williams
 

 This is the error message when in transmit mode on the main screen of wsjt-x

Hamlib error: Communication timed out

kenwood.c(577):kenwood_transaction return(-5)

kenwood.c(1604):kenwood_set_freq return(-5)

rig.c(1769):rig_set_freq return(-5) while setting frequency

 

Timestamp: 2021-05-31T15:33:32.069Z

Attached is the error message when testing cat control test button in settings > radio


locked Re: #BugReport - Display issue using HRD Log #IssueReport

neil_zampella
 

Wrong groups.io list OM, try hamapps.groups.io for JTAlert support.

Neil, KN3ILZ

On 5/31/2021 9:40 AM, N S via groups.io wrote:

Strange Bug to report.

Display issue with JTAlert menu bar window when using Ham Radio Deluxe LOG

 

SYSTEM:

Processor: i7-4770k 3.5Ghz

RAM: 16.0 GB

OS: 64-bit Windows 10 Pro Version 20H2 OS build 19042.985

With Windows Feature Experience Pac 120.2212.2020.0

Display Adapter: NVIDIA GeForce GTX 1080 with driver 27.21.14.6192

Display Samsung 4k x 2k, 3840 x 2160 native 60Hz

 

Win4IcomSuite v 1.3.1.4 – also acts as ICOM Compatible HRD Server

    address 127.0.0.1 port 7809, HRD 6

 HRD Logbook v6.7.0.277

 WSJT-X v2.4.0

JTAlert v2.50.1

PROBLEM:

If I go into JTAlert and select Logging to HRD v5/v6, Version 6.3 or later, 6.7.0.269 or later adif 3.1 compliant Log – I EXPERIENCE THIS PROBLEM:

The JTAlert menu bar flashes and when it finally connects to display HRD Log in the top of the menu bar, the window changes size (smaller) and the drop down menu titles appear to be below the box.  The drop down menus are still accessible but are extremely difficult to access because only the very tops of the letters Alerts, Settings, View, Sound ON and Help are displayed at the very bottom of the window.   The menu titles are no longer readable because they appear nearly off the screen.

If I uncheck “Select Logging to HRD”, close JTAlert and restart it, the menu bar appears to be normal again.

I have uninstalled and reinstalled nearly everything but still getting the same results.   I’ve also taken Win4IcomSuite out and have use HRD and HRD Logbook directly. Still get the same results.

Norm – W7CK





locked Upgrading from v2.12 to 2.3 Hamlib error #Cat_RigControl

reg williams
 

I have recently upgraded from v2.12 to v2.3 on a Windows 10 operating system. While v 2.12 worked perfectly there is a Hamlib error with communication with my radio a TS870. 
When testing "cat control" in radio settings the button turns green. Then pressing ptt sends the radio into transmit. If I then go back to cat control the hamlib error message appears
At the main screen of WSJT-X, When I change the frequency the radio will respond to the new frequency but the display frequency on the main screen does not. If I then change frequency again the radio responds and the main screen display changes to the previous chosen frequency.  In other words it is always one step behind..
Transmitting. The radio will transmit once only then the "rig control" error screen appears.
I thought the upgrade would be quite straightforward. All the radio settings are exactly the same as they were in the previous version of WSJT-X.
I am at a loss trying to resolve the problem. Any help would be appreciated. 

Reg


locked #BugReport - Display issue using HRD Log #IssueReport

N S <kl7rs@...>
 

Strange Bug to report.

Display issue with JTAlert menu bar window when using Ham Radio Deluxe LOG

 

SYSTEM:

Processor: i7-4770k 3.5Ghz

RAM: 16.0 GB

OS: 64-bit Windows 10 Pro Version 20H2 OS build 19042.985

With Windows Feature Experience Pac 120.2212.2020.0

Display Adapter: NVIDIA GeForce GTX 1080 with driver 27.21.14.6192

Display Samsung 4k x 2k, 3840 x 2160 native 60Hz

 

Win4IcomSuite v 1.3.1.4 – also acts as ICOM Compatible HRD Server

    address 127.0.0.1 port 7809, HRD 6

 HRD Logbook v6.7.0.277

 WSJT-X v2.4.0

JTAlert v2.50.1

PROBLEM:

If I go into JTAlert and select Logging to HRD v5/v6, Version 6.3 or later, 6.7.0.269 or later adif 3.1 compliant Log – I EXPERIENCE THIS PROBLEM:

The JTAlert menu bar flashes and when it finally connects to display HRD Log in the top of the menu bar, the window changes size (smaller) and the drop down menu titles appear to be below the box.  The drop down menus are still accessible but are extremely difficult to access because only the very tops of the letters Alerts, Settings, View, Sound ON and Help are displayed at the very bottom of the window.   The menu titles are no longer readable because they appear nearly off the screen.

If I uncheck “Select Logging to HRD”, close JTAlert and restart it, the menu bar appears to be normal again.

I have uninstalled and reinstalled nearly everything but still getting the same results.   I’ve also taken Win4IcomSuite out and have use HRD and HRD Logbook directly. Still get the same results.

Norm – W7CK


locked Re: Installing WSJT 2.4.0-1 #linux #install

Brian Morrison
 

On Mon, 2021-05-31 at 05:00 -0700, JD Delancy wrote:

I upgraded my Linux box to Fedora 34 (from 33) and then tried to upgrade the WSJTx to the General Availiablity release WSJT-X 2.4.0

It would not load, and the following error appeared:
  - nothing provides libboost_chrono.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_date_time.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_filesystem.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_system.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_thread.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_atomic.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log_setup.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_regex.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64

I tried the --skip broken files suggested by the system; no good

What now?

The new version is currently in the testing repo. I don't know why hamlib 4.2 is currently not available on F34, I built that myself. It may not matter but there were problems with earlier hamlib versions and the latest is helpful.

This should work from the command prompt, it will pull in needed dependency updates for wsjtx:

sudo dnf --enablerepo=updates-testing upgrade wsjtx

It's sensible to have been applying the released F34 updates too, as the boost package version is currently 1.75.0, you can do that using:

sudo dnf --enablerepo=updates-testing upgrade

Richard built the wsjtx package GA version about a week ago, it's also easy to build using the mock buildsystem if you want to learn how to do it a bit of Googling will reveal all.

-- 

Brian  G8SEZ


locked Re: Installing WSJT 2.4.0-1 #linux #install

Bill Somerville
 

On 31/05/2021 13:00, JD Delancy wrote:
I upgraded my Linux box to Fedora 34 (from 33) and then tried to upgrade the WSJTx to the General Availiablity release WSJT-X 2.4.0

It would not load, and the following error appeared:
  - nothing provides libboost_chrono.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_date_time.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_filesystem.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_system.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_thread.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_atomic.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log_setup.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_regex.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64

I tried the --skip broken files suggested by the system; no good

What now?
Hi JD,

our production system is still on Fedora 33, it will probably be upgraded for the upcoming WSJT-X v2.5.x releases. You should either build from sources, or wait for our RPM style package maintainer to publish v2.4.0 GA packages.

73
Bill
G4WJS.


locked Installing WSJT 2.4.0-1 #linux #install

JD Delancy
 

I upgraded my Linux box to Fedora 34 (from 33) and then tried to upgrade the WSJTx to the General Availiablity release WSJT-X 2.4.0

It would not load, and the following error appeared:
  - nothing provides libboost_chrono.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_date_time.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_filesystem.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_system.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_thread.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_atomic.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_log_setup.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64
  - nothing provides libboost_regex.so.1.73.0()(64bit) needed by wsjtx-2.4.0-1.x86_64

I tried the --skip broken files suggested by the system; no good

What now?



locked Re: #BugReport No receive after transmit - rig control disables RX on Yaesu FTDX-3000 VFO A running split #IssueReport

Mark Steele
 
Edited

Gary,

Thank you for your response, however I was referring to the fact that 2.4.0 GA has a rig control bug - a severe one.

I was referencing a bug fix for the GA and not a replacement for rc4

Best regards,

Mark


locked Re: Import Hamlib #Cat_RigControl

Bill Somerville
 

On 30/05/2021 23:36, Bob wrote:
Bill, I'm not sure what you mean about that driver.  I am identifying the radio as TS-2000 both in Power SDR and WSJTx settings.  I did try FlexRadio/PowerSDR ANAN/Thetis choice in JTx but that won't even CAT, RED TestCAT and HamLib error there.  Is there some other driver I'm not familiar with?  The other two stations and this one on 222 all work fine in 2.3.1 with the TS-2000 chosen and if there is another driver, it must be the same but I don't know about it. Thanks for the quick response.  Bob
Hi Bob,

yes I mean the PowerSDR/Thetis rig selction in WSJT-X "Settings->Radio->Rig". What is the error message, including details, when you use that?

73
Bill
G4WJS.


locked Re: 6 meter Q65 from CN71 #Q65

Jamie GOLLY
 

Hi Dwight, 50.275 30A is pretty standard. I would like the try to work you from CN81 in Yreka. A bit of a challenge since I have 6’000’ + mountains between you and I and am very close to them.

Jamie
K6NGN

On May 30, 2021, at 8:22 PM, Dwight Jones <dwightjones@...> wrote:

I'm new to this mode (I guess everyone is.) Can someone tell me the best frequency and submode for 6 meters in the western US?

I'm open to schedules with anyone who needs CN71 on this mode. My days are pretty free. Just send me a message with the time you would like to try. I'll let you know if that time works. Mid-day is probably the most productive time. (We would reschedule if Es happens to come to this grid at the time of our sked.)

Dwigfht
KO6FE
CN71


locked Re: Restore QSOs to the log file after a crash #FT8 #raspberryPi

Anuraag Bhargava
 

Thanks Bill,

I replaced the ADIF file in wsjtx with the ADI file from qrz.com and that seems to show the existing QSOs as green.

Much appreciated.


locked 6 meter Q65 from CN71 #Q65

Dwight Jones
 

I'm new to this mode (I guess everyone is.) Can someone tell me the best frequency and submode for 6 meters in the western US?

I'm open to schedules with anyone who needs CN71 on this mode. My days are pretty free. Just send me a message with the time you would like to try. I'll let you know if that time works. Mid-day is probably the most productive time. (We would reschedule if Es happens to come to this grid at the time of our sked.)

Dwigfht
KO6FE
CN71


locked Re: Import Hamlib #Cat_RigControl

Bob
 

Bill, I'm not sure what you mean about that driver.  I am identifying the radio as TS-2000 both in Power SDR and WSJTx settings.  I did try FlexRadio/PowerSDR ANAN/Thetis choice in JTx but that won't even CAT, RED TestCAT and HamLib error there.  Is there some other driver I'm not familiar with?  The other two stations and this one on 222 all work fine in 2.3.1 with the TS-2000 chosen and if there is another driver, it must be the same but I don't know about it. Thanks for the quick response.  Bob


locked Re: No TX #FT8

Tom V. Segalstad
 

ARRL’s comparative overview (below), of different types of measurements, confirms the relation between S-meter and transmitting power, as given by Gary, AG0N.

As an example, if we look at S-meter reading 4 (second last vertical axis), this compares in this overview with transmitting power of 1 Watt (last vertical axis).

A doubling of transmitting power from 1 to 2 Watt, is a 3 dB power increase, and will increase the S-meter from 4 to 4.5, because there are 6 dB increase between each S-meter unit.

So another doubling of transmitting power from 2 to 4 Watt, another 3 dB increase, should move the S-meter from 4.5 to 5.

And this continues: Another 6 dB increase, from 4 to 16 Watt, equivalent to 1 S-meter unit, should increase the S-meter in this example from 5 to 6, as given in ARRL’s overview.

 

73 from Tom, LA4LN

 

 

 

Fra: Gary - AG0N
Sendt: søndag 30. mai 2021 kl. 22.11
Til: main@WSJTX.groups.io
Emne: Re: [WSJTX] No TX #FT8

 



> On May 30, 2021, at 07:28, Gilbert Baron <w0mn00@...> wrote:
>
> Really, if you double your power you add 1 S-Unit.

If a meter is properly calibrated (few are), six db is one S unit.  Three db is double the power.

Gary - AG0N


 


--
Tom (LA4LN)


locked Re: Restore QSOs to the log file after a crash #FT8 #raspberryPi

Bill Somerville
 

On 30/05/2021 21:59, Anuraag Bhargava wrote:
Hello all,

I run wsjtx on a raspberry pi and recently had a bad SD card leading to lost data. I ended up rebuilding everything but lost my log files of QSOs.

I log everything automatically into QRZ.com and can get an extract from there. The format however seems a bit different. Is there a way I can import this into the wsjtx log file?

Has anyone tried this before?

All help appreciated. 

Thanks in advance.

Anuraag

Hi Anuraag,

WSJT-X requires an ADIF file containing at least the following fields for each recorded QSO:

CALL

also recommended:

BAND
MODE
SUBMODE for modes like MFSK
GRIDSQUARE only the first 4 characters are used.

Other ADIF QSO fields are ignored.

73
Bill
G4WJS.


locked Re: #general Moving macros. #general

Bill Somerville
 

On 30/05/2021 22:02, Dave Tucker Nu4N wrote:
Is there a way to rearrange my macros without having to type them over agn the way I want them ?

--
Thanks 73's de NU4N/Dave
Hi Dave,

see the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.4.0.html#TXMACROS

73
Bill
G4WJS.


locked Re: Import Hamlib #Cat_RigControl

Bill Somerville
 

On 30/05/2021 22:19, Bob wrote:
After upgrading to WJSTx2.4.0, I am getting a HAMLIB error on PTT now.  Worked OK with 2.3.1 and 2.4.0-rc4.  No settings changed.  W10/64 up to date, Ryzen 7 PC, Flex 1500 running Power SDR 2.7.2. I have 3 identical stations on 2m, 222 and 432 for terrestrial and EME.  2m and 432 still at 2.3.1 and with the upcoming VHF contest, I don't want to mess with them unless I can fix it on this 222 station, other than going back to 2.3.1.  I run VAC and VSP mgr.
In 2.4.0, I get green TestCAT but Red TestPTT and HAMLIB error shown below and TestCAT turns Red.  Click TestCAT again and it will return to green but PTT again will produce the error.  I saw one note on this thread where someone suggested changing radio setting in WSJTx to USB.  I must have Flex in DIGU to use VAC.  I did try with USB.  No error but also no PTT.  Any help appreciated.  I would be OK for the upcoming contest using 2.3.1 but eventually want to get 2.4.0 going to have access to Q65 for EME as I have seen a number of stations using it already.  I also saw some chatter about hamlib now as a DLL file and I see that in the 2.4.0 install directory but don't know if it actually works from there.  I don't know where it should go if it would be of help.  Thanks and 73, Bob
Hi Bob,

are you using the PowerSDR CAT driver in WSJT-X?

73
Bill
G4WJS.


locked Re: Documentation for format of .ini file #general

Bill Somerville
 

On 30/05/2021 22:00, Kenneth Williams wrote:
My interest centers around starting wsjt-x with the --rig-name option.
I am primarily interested in those settings which affect the rig configuration during startup and any nuances or subtleties in the usage of these setting.
I saw something about this mentioned in an earlier posting but the usage was unclear to me.

With respect to my ability to understand technical details, I am pretty technically literate and I am able to bit-streams, byte-streams, packet formats, etc., including the command set for my rig (TS-570) so feel free to comment with the minimum necessary level of detail .

Ken
KC6PUQ
Hi Ken,

starting WSJT-X with a unique --rig-name= argument will cause it to create an use a unique settings file and log files directory, each instance is completely isolated. There are no nuances or subtleties.

73
Bill
G4WJS.


locked Re: Import Hamlib #Cat_RigControl

Bob
 

After upgrading to WJSTx2.4.0, I am getting a HAMLIB error on PTT now.  Worked OK with 2.3.1 and 2.4.0-rc4.  No settings changed.  W10/64 up to date, Ryzen 7 PC, Flex 1500 running Power SDR 2.7.2. I have 3 identical stations on 2m, 222 and 432 for terrestrial and EME.  2m and 432 still at 2.3.1 and with the upcoming VHF contest, I don't want to mess with them unless I can fix it on this 222 station, other than going back to 2.3.1.  I run VAC and VSP mgr. 
In 2.4.0, I get green TestCAT but Red TestPTT and HAMLIB error shown below and TestCAT turns Red.  Click TestCAT again and it will return to green but PTT again will produce the error.  I saw one note on this thread where someone suggested changing radio setting in WSJTx to USB.  I must have Flex in DIGU to use VAC.  I did try with USB.  No error but also no PTT.  Any help appreciated.  I would be OK for the upcoming contest using 2.3.1 but eventually want to get 2.4.0 going to have access to Q65 for EME as I have seen a number of stations using it already.  I also saw some chatter about hamlib now as a DLL file and I see that in the 2.4.0 install directory but don't know if it actually works from there.  I don't know where it should go if it would be of help.  Thanks and 73, Bob


locked #general Moving macros. #general

 

Is there a way to rearrange my macros without having to type them over agn the way I want them ?

--
Thanks 73's de NU4N/Dave

10201 - 10220 of 35397