On 16/02/2021 21:40, Pat Tracy WI0K
wrote:
How do I fix this. Hi Pat, you cannot mix the Debian package we provide with ones provided
by package maintainers. If you want to install the WSJT-X v.2.2.2
package called wsjtx-data from the repo then remove the separately
installed wsjtx package first: sudo dpkg -P wsjtx sudo apt install wsjtx-data or conversely: sudo apt remove wsjtx-data sudo dpkg -i ~/Downloads/wsjtx-2.3.0_amd64.deb 73
|
|
On 16/02/2021 21:12, Ken WB8UFC wrote:
This doesn't seem right to me...Hi Ken, try double-clicking the repeated RRR message. 73 Bill G4WJS.
|
|
Hasan Schiers N0AN
Joe, I would suggest you not go to 50.275 for MSK144. That freq is in use a lot for Q65-30A in the States. I didn't see a callsign for you, ... Typically MSK144 alternate frequencies here are 255, 250, 265, even 257 works. 73, N0AN Hasan
I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?
|
|
Pat Tracy WI0K
How do I fix this.
wptracy@ubuntu:/usr/share/pixmaps$ sudo apt-get install wsjtx-data Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: glib-networking:i386 gstreamer1.0-x:i386 libaa1:i386 libavc1394-0:i386 libcaca0:i386 libdv4:i386 libgstreamer-plugins-good1.0-0:i386 libgudev-1.0-0:i386 libiec61883-0:i386 libproxy1v5:i386 libraw1394-11:i386 libsamplerate0:i386 libshout3:i386 libslang2:i386 libsoup2.4-1:i386 libtag1v5:i386 libtag1v5-vanilla:i386 libxv1:i386 Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: wsjtx-data 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/3,625 kB of archives. After this operation, 3,832 kB of additional disk space will be used. (Reading database ... 220225 files and directories currently installed.) Preparing to unpack .../wsjtx-data_2.2.2+repack-2_all.deb ... Unpacking wsjtx-data (2.2.2+repack-2) ... dpkg: error processing archive /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx 2.3.0 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: js8call: Depends: wsjtx-data but it is not installed Depends: libc6 (>= 2.29) but 2.32-0ubuntu3 is installed Depends: libfftw3-single3 (>= 3.3.5) but 3.3.8-2ubuntu6 is installed Depends: libgcc-s1 (>= 3.0) but 10.2.0-13ubuntu1 is installed Depends: libgfortran5 (>= 10) but 10.2.0-13ubuntu1 is installed Depends: libgomp1 (>= 4.2.1) but 10.2.0-13ubuntu1 is installed Depends: libhamlib2 (>= 3.1) but 3.3-10build1 is installed Depends: libqt5core5a (>= 5.14.1) but 5.14.2+dfsg-6 is installed Depends: libqt5gui5-gles (>= 5.14.1) but it is not installed Depends: libqt5multimedia5 (>= 5.6.0~beta) but 5.14.2-3 is installed Depends: libqt5network5 (>= 5.0.2) but 5.14.2+dfsg-6 is installed Depends: libqt5serialport5 (>= 5.6.0) but 5.14.2-2 is installed Depends: libqt5widgets5 (>= 5.14.1) but 5.14.2+dfsg-6 is installed Depends: libsqlite3-0 (>= 3.5.9) but 3.33.0-1ubuntu0.1 is installed Depends: libstdc++6 (>= 5.2) but 10.2.0-13ubuntu1 is installed wptracy@ubuntu:/usr/share/pixmaps$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: glib-networking:i386 gstreamer1.0-x:i386 libaa1:i386 libavc1394-0:i386 libcaca0:i386 libdv4:i386 libgstreamer-plugins-good1.0-0:i386 libgudev-1.0-0:i386 libiec61883-0:i386 libproxy1v5:i386 libraw1394-11:i386 libsamplerate0:i386 libshout3:i386 libslang2:i386 libsoup2.4-1:i386 libtag1v5:i386 libtag1v5-vanilla:i386 libxv1:i386 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: wsjtx-data The following NEW packages will be installed: wsjtx-data 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/3,625 kB of archives. After this operation, 3,832 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 220225 files and directories currently installed.) Preparing to unpack .../wsjtx-data_2.2.2+repack-2_all.deb ... Unpacking wsjtx-data (2.2.2+repack-2) ... dpkg: error processing archive /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx 2.3.0 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) wptracy@ubuntu:/usr/share/pixmaps$
|
|
locked
Re: #Cat_RigControl
#Cat_RigControl
Lutz-DL9DAN
Hi Bill,
So now with this sequence I do not need the test cat as it works perfect.
73 Lutz
Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von Bill Somerville
Lutz,
perhaps you could have saved yourself some time by checking the WSJT-X User Guide FAQ section, item 6:
73
On 16/02/2021 20:35, Lutz-DL9DAN wrote:
|
|
Ken WB8UFC
This doesn't seem right to me...
Mode: FT8
Relevant setting: Auto Seq (checked)
I answer a CQ by d-clicking on a line in the Rx Frequency list box.
The other side sends my signal report.
WSJT-X sends "R-" plus his signal report.
The other side sends RRR.
WSJT-X sends 73 (and advances the Next message to my CQ message).
The other side sends RRR again.
I d-click on his RRR line in the Rx Frequency list box, but after enabling the "Enable Tx" button, WSJT-X sends CQ instead of 73 because it doesn't re-position the "Next" message.
Is this expected behavior (and if so, why)?
At any other point in the QSO, d-clicking on the other side's line in the Rx Frequency list box selects the correct next message.
My best current workaround is to quickly click the radio button for the 73 message and then click on "Halt Tx" and then click on "Enable Tx" Is there a faster/better way? As a prophylactic measure I've taken to sometimes re-positioning the "Next" radio button manually back to the 73 message in anticipation of another RRR from the other side, but this seems kinda hokey. WB8UFC
|
|
On 16/02/2021 21:06, Nico Ebbendorf wrote:
Hi,Hi Nico, non-linear behaviour of the WSJT-X Pwr slider is usually a sign that you have too much audio level into your rig. It also is a sign that you may be transmitting a poor quality signal. Find the data mode input gain in your rig's menu and reduce it until the unwanted behaviour stops. See this post for a recipe for setting Tx audio levels correctly: https://wsjtx.groups.io/g/main/message/13890 73 Bill G4WJS.
|
|
Nico Ebbendorf
Hi,
Trying to control the TX output with the PWR slider. My transceiver is a FTDX101D. Coding and decoding FT8 is working and also the transceiver freq. control Observation: Set TX power at 40 Watt using the transceiver power control knop. Then sliding the PWR control down will reduce output power but this increases automatically within a second or so to the maximum power that is set by the transceiver (in this case 40 Watt). So the power output is always the maximum that is set by the transceiver regardles the PWR slider position. Is there anything to set in the software to correct this or do I need to go into the transceiver menu? 73, Nico PA3ADU
|
|
Bob K4RCG
Jim, I've been using Q65/30A on 50.275. 50.235 is said to be for 120/A. And finally, I believe DX/EU is on .305. Lots of fun. 73 Bob K4RCG
On Tue, Feb 16, 2021 at 6:30 PM ve4cy <jwt@...> wrote: I notice on PSK Reporter, there are quite a few stations running Q65 on Six Meters.
|
|
On 16/02/2021 20:53, joe gay via groups.io wrote:
I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?Hi Joe, WSJT-X has a feature that allows easy operation with MSK144 to call on a calling frequency but carry out QSOs on a different working frequency. This is only available if you have working CAT control and enable one of the "Settings->Radio->Split Operating" options. Check the checkbox to the right of the "Tx CQ 260" spin box, then tune your VFO to a free working frequency. WSJT-X will automatically amend the CQ message to inform repliers of your working frequency, make CQ calls on the .260 (or whatever kHz offset you set the spin box to) calling frequency, and proceed with any QSOs on your working frequency. When your QSO is completed the next CQ call you make will be back on the calling frequency. To make a QSO double-click a decode of any station that replies to your CQ. None of the above will happen if you do not check the checkbox mentioned above. 73 Bill G4WJS.
|
|
joe gay
I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?
Joe
|
|
Hasan Schiers N0AN
In the current 2.4.0 RC1 we discovered that the number of observable decodes is greater with Enable Averaging OFF. The next release will take care of this. In the mean time, if you are just monitoring the band for possible decodes, turn Enable Averaging OFF. When in QSO, turn it back on, as it permits better sensitivity under certain conditions. 73, N0AN Hasan
On Tue, Feb 16, 2021 at 2:35 PM W4AS <w4as@...> wrote: Why disable Averaging?
|
|
locked
Re: #Cat_RigControl
#Cat_RigControl
Lutz,
perhaps you could have saved yourself
some time by checking the WSJT-X User Guide FAQ section, item 6:
73
Bill G4WJS.
On 16/02/2021 20:35, Lutz-DL9DAN wrote:
|
|
locked
Re: #Cat_RigControl
#Cat_RigControl
Kenneth Williams
Hello Jacques
Maybe you should update your WSJT-X to 2.4 rc1. While you may not like this response, I have had a recent experience where this was indeed the proper solution. I am mentioning this because I have a TS-570S, and while it is not a 590 as you have, these radios may share some of the problem causing behavior. OK, here is some boring detail: I started using FT8 with version 2.2. WSJT-X would frequently report loss of communication with the radio although I did not need to reboot my computer, I did suffer this kind of problem. It was suggested that I update to V2.3. This did not completely resolve the problem. v2.4 solved the problem. The problem: In my case, my radio would occasionally respond to an 'IF' (information query) command with an answer that was one or two bytes shorts. Hamlib, the library that is used to interface with the various radios, would reject the responses that were one byte too short (in v2.3) but responses that were two bytes too short would cause hamlib to report loss of communication. I know this because when validating the problem, mostly for my own curiosity, I instrumented the serial interface to my rig and I could see the short responses come out of the radio. With WSJT-X v2.2, I saw a loss of communication message frequently (once every few hours). With v2.3, the messages were less frequent (once or twice a day). Since running v2.4 for almost a week, I have not seen that problem at all (except when I tripped the circuit breaker to my radio, but I do not think that this event counts) Good luck Ken KC6PUQ
|
|
locked
Re: #Cat_RigControl
#Cat_RigControl
Lutz-DL9DAN
Hi Gene,
Its funny, but:
2) Start the microham router with the virtual ports
4) Start SDRCONSOLE and all digi modes are present and work, the rig works with CAT for both programs
It seems to me that WSJT-X is calling the OMNIRIG up on its own and cannot see that it is always running.
I have tested and confirmed this behavior now several times!
Its like fishing - you need patience sitting behind the rod!
Thanks Lutz/DL9DAN
Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von RVnRadio
I will add to the response "It sounds like more than one program is trying to access the same port", except my suffix will be "for sure" instead of maybe. At least that is my assessment. here is what I do, which I think is just a bigger version of what your trying to accomplish.
|
|
locked
Re: Sudden blindness to sound card and ports windows 10
#AudioIssues
#Cat_RigControl
#IssueReport
On 16/02/2021 19:36, Chris wrote:
I think it would be better to focus on the bigger issue which is the sound card problem.Hi Chris, the (Not found) annotation means exactly what it says. The underlying Qt framework functionality we use to enumerate audio devices did not list the one you last used in WSJT-X. If the drop down list is also empty then no audio devices are available to WSJT-X. MS Windows has several audio sub-systems, the one we have access to is called MME (Multi-Media Extensions). If MME is unable to enumerate your audio devices then the problem lies within MS Windows and your best source of support is probably with Microsoft support. A basic question like "I am using an application that uses MME audio and it can't see any audio devices, what should I do?" seems pertinent. If you are happy to download and run a pre-built executable from me, the following application will enumerate the audio devices seen by MME using just MS system library code without any of the framework layers we use in WSJT-X, it would be interesting to see the output: https://www.dropbox.com/s/kidxhnb8w20j7w4/audio_devices_enumeration.exe?dl=1 The source code is here if you want to know what it does or prefer to build it yourself: https://www.dropbox.com/s/6mj0f68q7xd07h4/audio_devices_enumeration.zip?dl=1 73 Bill G4WJS.
|
|
W4AS
Why disable Averaging?
toggle quoted messageShow quoted text
73 de Sebastian, W4AS
On Feb 16, 2021, at 1:49 PM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
|
|
K0GU
On 2/16/2021 12:20 PM, Chris Hannagan
wrote:
Yep, I have those same problems with terrestrial operations. 73, Jay K0GU
|
|
locked
Re: Sudden blindness to sound card and ports windows 10
#AudioIssues
#Cat_RigControl
#IssueReport
Chris
I think it would be better to focus on the bigger issue which is the sound card problem.
Note this capture. The correct card shows initially as "not found". If I click on the pick list (which I did on the bottom output list) No cards show up. I'm pretty sure this is due to some corruption in the WSJT-X installation, but un installing and re installing does not fix it. I'm hoping someone with good knowledge of the "under the hood" areas might shed some light on this. To restate, all other programs see and work it the card just fine, and WSJT-X worked fine until a bit over a week ago. This was a sudden and unexpected change. Chris, AB6QK
|
|
Chris Hannagan
I have run some tests with a friend in ZL and I see a few shortcomings and I don't know whether there is input from the EME community to the developers. I see that Call 1st is broken and it will not start the auto sequence when a legitimate mycall hiscall sequence is received. The sequencing never moves to tx6 even after the QSO is logged and continues to send 73 until manually changed. The single tone shorthand messages are referenced against the carrier frequency only not the transmitting stations DF. Envisage some EME DXpeditions where you have stations every plus/minus 200 Hz for 1000Hz bandwidth each way and someone misses a transmission and the DX moves on to the next station. I'm sure the old SH messages referenced to the sync frequency are probably much more effective way to avoid the confusion. I don't think I'm game to try shorthand for EME in a situation where there might be more than one caller and going to the FT8 style TX3 TX4 TX5 messages (probably) defeats the extra sensitivity... I presume (maybe wrongly) the single tone for a CQ message when SH is checked is a feature for microwave users to find each other's signal?
|
|