When I used to write software and there were specific error messages to create I would have had a format similar to these. I figure the error code will allow them to specifically locate in their code what was happening.

--73, Glenn, AF8C

On 11/6/2022 5:27 PM, alan2--- via wsjt-devel wrote:
I wasn't aware of this file so just took a look, finding it starting in November 2021 and 11MB in size.

Rig in use is a TS590S, and the bulk of those log lines were in the form of:

[RIGCTRL]<varying date time string>[warning] kenwood_get_split_vfo_if(1552): unknown rxVFO=None

For some reason WSJT-X (currently v 2.5.4) is set for None rather than Rig or Fake-it as I recall I too was experimenting with what happens with different settings but I've not had a chance to use it for many months now so I've forgotten!

I therefore suspect those messages might be reflecting the setting I'm using, but posting here in case it's useful.  They started while I was running v2.5.3 by the looks of it.

Alan G0TLK

On 06/11/2022 15:02, Glenn Williams via wsjt-devel wrote:
I am sending this to the developers list because it seems to be too detailed and too specific to only one type of rig to warrant sending to the general [WSJTX] reflector.   --de AF8C, Glenn

HARDWARE/SOFTWARE CONFIGURATION

Version 2.5.4
Windows 10
Cabled via USB only to a Kenwood TS590SG.

Do you need more information on the above configuration?

HISTORY

Operation has been flawless for months.  I basically usually never look at the file wsjtx_syslog.log. In that file there is nothing before November 1, 2022. Something changed on November 1 that caused the syslog file to start growing nearly without bounds. That was only 6 days ago.

In the syslog file appear messages that apparently only started on November 1, when possibly I might have tested what happens if I selected RIG instead of FAKE-IT,  But then I went back to FAKE-IT because that's where I found it when I noticed what syslog was doing.

Then after a few days I accidentally caught that wsjtx_syslog.log was getting very large. There is an error message every second, as shown below, but only when I am in FAKE-IT mode.

DETAILS OF PROBLEM

After some testing, I learned that the major problem of a warning every second goes away while in RIG mode but comes back if I go to FAKE-IT mode. The only was to stop it is to go back to RIG.  This did not happen before November 1 because I always ran FAKE-IT mode. It's as if a flag was set that wasn't set before November 1, indicating that my TS590SG transceiver can do RIG so let's no longer accept FAKE-IT as valid. (That's a guess.)

Below between the two lines is a transcript of a short test with RIG and FAKE-IT, today.I have INSERTED a few comments or questions with a leading "greater than" symbol and upper case text.

(My email setup on this computer wants to wrap lines.)
------------------------------------------------------------------------------
>STARTED WSJT-X for FT8
[SYSLOG][2022-11-05 19:23:07.085455][00:00:00.000629][info] Log Start
[SYSLOG][2022-11-05 19:23:07.085455][00:00:00.000685][info] WSJT-X v2.5.4 d28164  by K1JT, G4WJS, K9AN, and IV3NWV - Program startup [SYSLOG][2022-11-05 19:23:07.101079][00:00:00.004517][info] locale: language: English script: Latin country: United States ui-languages: en-US [SYSLOG][2022-11-05 19:23:07.101079][00:00:00.004726][info] Loaded Qt translations for current locale from resources [SYSLOG][2022-11-05 19:23:07.101079][00:00:00.004773][info] Loaded WSJT-X base translation file from :/Translations based on language en [SYSLOG][2022-11-05 19:23:07.101079][00:00:00.004808][info] Loaded WSJT-X translations for current locale from resources [SYSLOG][2022-11-05 19:23:07.116702][00:00:00.026421][info] shmem size: 48275456 [RIGCTRL][2022-11-05 19:23:07.147949][00:00:00.049428][info] Hamlib version: Hamlib 4.5~git Sat Jan 01 23:05:51 2022 +0000 SHA=18548e
> WHAT DOES THIS SINGLE NEXT LINE MEAN?  WAS IN FAKE=IT MODE
[RIGCTRL][2022-11-05 19:23:08.335330][00:00:01.251647][warning] rig_init: backend for TS-590SG does not contain hamlib_check_rig_caps
> THIS HAPPENS WHILE IN FAKE=IT MODE, EVERY SECOND.   WHY?
[RIGCTRL][2022-11-05 19:23:08.672954][00:00:01.575576][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:08.904705][00:00:01.807581][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:09.991857][00:00:02.894678][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:10.986785][00:00:03.888094][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:11.995429][00:00:04.896624][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:12.990514][00:00:05.891802][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:13.989950][00:00:06.891254][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:14.991988][00:00:07.893143][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:16.018014][00:00:08.925182][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:16.993229][00:00:09.894732][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:17.992101][00:00:10.893433][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:18.993175][00:00:11.894598][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:19.995426][00:00:12.896514][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:20.990059][00:00:13.891410][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:21.985164][00:00:14.886039][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:22.986873][00:00:15.888210][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:23.985876][00:00:16.887256][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:24.993242][00:00:17.894310][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:25.992766][00:00:18.894096][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:26.988595][00:00:19.890267][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None [RIGCTRL][2022-11-05 19:23:27.991908][00:00:20.893155][warning] kenwood_get_split_vfo_if(1583): unknown rxVFO=None
> FOR THIS LINE I WAS SWITCHING OVER TO RIG MODE
[RIGCTRL][2022-11-05 19:23:28.350439][00:00:21.251822][warning] rig_set_split_mode(4002): Unhandled TXVFO=VFOB, tx_mode=PKTUSB [SYSLOG][2022-11-05 19:23:29.383605][00:00:22.284784][warning] Detected dropped audio source samples: 864 (0.018 S)
> FOR THIS LINE I GUESS IT WAS PART OF SWITCHING OVER TO RIG MODE
[RIGCTRL][2022-11-05 19:24:14.979895][00:01:07.880158][warning] rig_set_split_mode(4002): Unhandled TXVFO=VFOB, tx_mode=PKTUSB > NOTE THAT ONCE IN RIG MODE THE "kenwood_get_split_vfo_if(1583)" HAS NOW STOPPED HAPPENING. WHY? > HOWEVER THE "dropped audio source samples" MESSAGES APPEAR AT THE END OF MANY RECEIVE CYCLES.  WHY? [SYSLOG][2022-11-05 19:25:44.374381][00:02:37.272193][warning] Detected dropped audio source samples: -576 (-0.012 S) [SYSLOG][2022-11-05 19:25:59.393319][00:02:52.291720][warning] Detected dropped audio source samples: 1008 (0.021 S) [SYSLOG][2022-11-05 19:26:14.377554][00:03:07.275763][warning] Detected dropped audio source samples: -720 (-0.015 S) [SYSLOG][2022-11-05 19:26:44.400835][00:03:37.298909][warning] Detected dropped audio source samples: 1104 (0.023 S) [SYSLOG][2022-11-05 19:27:14.406583][00:04:07.304155][warning] Detected dropped audio source samples: 1248 (0.026 S) [SYSLOG][2022-11-05 19:27:44.393508][00:04:37.291014][warning] Detected dropped audio source samples: 1008 (0.021 S) [SYSLOG][2022-11-05 19:28:14.420086][00:05:07.317571][warning] Detected dropped audio source samples: 1488 (0.031 S) [SYSLOG][2022-11-05 19:28:44.412721][00:05:37.309422][warning] Detected dropped audio source samples: 1104 (0.023 S) [SYSLOG][2022-11-05 19:29:14.401724][00:06:07.298804][warning] Detected dropped audio source samples: 1440 (0.03 S) [SYSLOG][2022-11-05 19:29:44.388490][00:06:37.285320][warning] Detected dropped audio source samples: 1104 (0.023 S) [SYSLOG][2022-11-05 19:30:14.410824][00:07:07.307798][warning] Detected dropped audio source samples: 1344 (0.028 S) [SYSLOG][2022-11-05 19:30:44.410770][00:07:37.307750][warning] Detected dropped audio source samples: 1008 (0.021 S) [SYSLOG][2022-11-05 19:31:14.411572][00:08:07.307960][warning] Detected dropped audio source samples: 1248 (0.026 S) [SYSLOG][2022-11-05 19:31:44.401560][00:08:37.297999][warning] Detected dropped audio source samples: 912 (0.019 S) [SYSLOG][2022-11-05 19:32:44.389935][00:09:37.286603][warning] Detected dropped audio source samples: 1152 (0.024 S) [SYSLOG][2022-11-05 19:33:44.383696][00:10:37.280219][warning] Detected dropped audio source samples: 720 (0.015 S) [SYSLOG][2022-11-05 19:34:14.379468][00:11:07.275859][warning] Detected dropped audio source samples: 720 (0.015 S)
-----------------------------------------------------------------------------------------------------

--73, Glenn, AF8C



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
This email has been checked for viruses by Avast antivirus software.
www.avast.com


_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to