locked
Re: Win10 Dark Theme not affecting WSJT-X v2.1.1.
Mike Azzarello
Could you tell me how to do this on a Mac? Thanks...Mike..kb3lan
|
|
Randy Diddel
Hi Ted,
I own 3 Elecraft radios, also a PX3, and a KXPA100. I have copies of each factory configuration file backed up in multiple places. You reminded me that I still need to reach out to Elecraft support for the factory settings on this K3s. This may be why I did not bother to do a full reset. A good reminder to others that may not know this about Elecraft gear. 73 K5RHD /randy
|
|
neil_zampella
FWIW... I would uninstall, you won't lose any of your settings or
logs as they're kept in a separate directory, then install the 64
bit version. There is a small issue with audio settings that
Bill has posted about previously, I'm fairly sure you can do a
search to find that post.
On 1/12/2020 2:44 AM,
spabish@... wrote:
Running the 32 bit version of WSJT-X on a Windows 10 computer.
|
|
On 12/01/2020 07:44, spabish@... wrote:
Running the 32 bit version of WSJT-X on a Windows 10 computer.Hi OM, you can do either. What is important is that the way Tx audio is handled in the 64-bit version is slightly different and you will have to do some initial setup. See this post for details: https://groups.io/g/WSJTX/message/5077 73 Bill G4WJS.
|
|
Scott N2GNT
Running the 32 bit version of WSJT-X on a Windows 10 computer.
Should I uninstall WSJT-X if I want to upgrade/install the 64 bit version? Or should I just install the 64 bit version of WSJT-X on top of the current install? Thanks N2GNT
|
|
locked
Re: IO error when testing PTT control with 'no rig'
Dave, Thanks for your comments.
With the FT-736, my initial concern is to use the Echo mode for testing the EME system. I expect that the oscillator drift will not be critical for the echoes. But I will look at either modifying or replacing the FT-736R if I want to do EME data modes later. Regarding the DATA IO cables, I was advised just a couple of days ago that the Data-IN/OUT socket on the rear panel of the FT-736R is for FM modes only and that you can't use that socket in the SSB mode. I am not sure if that is correct. Certainly the FT-736R manual says the data socket connects your computer directly to the FM discriminator, but I find it hard to believe that Yaesu would have connected that socket up in such a way that no audio goes in or comes out in SSB mode. I am thinking of setting up a FT-736R on the bench and testing this, but I would be interested in your thoughts on that advice. Cheers George vk3eip
|
|
Ted VE3TRQ
I suggest you don’t ever do a full reset on a K3 without having a copy of the (hopefully vanilla) settings file. There are many things that are set up at the Elecraft factory to configure the radio. If you reset all to defaults, you lose the factory calibration, and have a whole lot of calibration to do with equipment and procedures you may not have.
-- VE3TRQ Ted
|
|
locked
Re: Win10 Dark Theme not affecting WSJT-X v2.1.1.
Gary Gorniak
Thanks for posting this info, Bill! MUCH easier on my eyes.
toggle quoted messageShow quoted text
73 de Gary - W9BS
-----Original Message-----
From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Bill Somerville Sent: Saturday, January 11, 2020 9:21 AM To: WSJTX@groups.io Subject: Re: [WSJTX] Win10 Dark Theme not affecting WSJT-X v2.1.1. On 11/01/2020 03:51, edpostiii@... wrote: I'd like to make WSJT-X v2.1.1.operate with the Dark Theme or Dark Mode.Hi Ed, yes, start WSJT-X with the following command line: wsjtx -stylesheet :/qdarkstyle/style.qss 73 Bill G4WJS.
|
|
locked
Re: IO error when testing PTT control with 'no rig'
Dave_G0WBX
I also have a FT736r.
Nice radio, even now, but... You will need to do something to prevent the 20.48MHz reference oscillator drifting with temperature (even the TCXO drifts!) It's "OK"(ish) for voice modes, but is just not good enough for many digital modes on 23cms. Note too, that the "DATA" I/O cable, has a tendency to couple RF into the radio in a bad way (a classic "Pin 1" problem) causing "wide" signals and overall splatter. Difficult to tell, as these rig's don't have a TX monitor facility as standard, unless you use another RX to monitor your TX signal with mk1 ear'ole. Re the PTT. Hamlib (V3.3 onwards) correctly controls the FT736r for PTT, mode & frequency etc from WSJTx (Thanks to Bill G4WJS) so go for CAT control. It works. (And it correctly releases the radio when you exit WSJTx.) 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using free and open source software:
|
|
Dave_G0WBX
Hi Gil.
So, there is no problem now? 73. Dave G0WBX. (Sounds like 40m is open to India from the UK, @ 23:49 UTC.) -- Created on and sent from a Unix like PC running and using free and open source software:
|
|
Dave Garber
in settings somewhere, set cat to data or none, not rig. rig may be causing radio to go to lsb, and should not be. ( based on bandplan) Dave Garber VE3WEJ / VE3IE
On Sat, Jan 11, 2020 at 7:48 AM Gilbert Baron <w0mn00@...> wrote: I do not think that is the answer. WSJTX sets my TS590 to LSB on 80 Mtr and decode works fine. I was a bit surprised at that too since it sets it to USB on all of the other bands , including 40 Mtrs.
|
|
locked
Re: IO error when testing PTT control with 'no rig'
Hi Bill, the adduser command fixed the WSJT-X problem and Test PTT now works. Clearly I didn't have the rights to access the serial port.
However, the computer still doesn't key the FT-101E, so at least now I am down to a hardware problem. Thanks for your advice George vk3eip
|
|
locked
Re: Waterfall Speed
On 11.1.2020 23.22, W7VH wrote:
Hi everybody,
Jon, N Avg on Wide Graph. 1 is as fast as it will go, bigger numbers = slower. 'Kari, oh2gqc
|
|
locked
Re: Waterfall Speed
Reino Talarmo
Jon, I the Waterfall display with controls active you see lower left N Avg n, with the arrows you can set average values and those do define speed of the waterfall display. It is a stepwise setting not continuous. 73, Reino oh3mA
|
|
locked
Waterfall Speed
W7VH
Hi everybody,
Does anyone know how to increase the speed of the waterfall display? I haven't been able to find such a setting. Thanks, Jon W7VH
|
|
Randy Diddel
Rich VE3KI nailed it!
The digital setting was something other than Data A (cannot remember which). I now regret not doing a full reset on my K3s when I first got it from the person I bought it from. 73 everyone! K5RHD /randy
|
|
Randy Diddel
Hi Rich,
Good point. I will check these settings in Data Mode on the K3s. Data mode should be USB already but your suggestion #1 and #2 may be the issue. I bought the radio used and the previous owner could have set something up goofy. Suggestion #3: Already reset the frequency in the preferences in WSJT-x and I do see FT8 sigs in the waterfall. B Smith, this is RX not TX. Why would the power slider matter? I will report back later today. Thanks everyone, 73 K5RHD /randy
|
|
Randy,
To me this sounds like some band-specific setting within the radio. My old ICOM 746 "remembers" which antenna (1 or 2) I last selected for each band, and WSJT-X doesn't control that. Could it be that that the radio "remembers" that you last used LSB on 80 meters instead of USB? Maybe there are other settings like that in the radio causing similar trouble - I'm not familiar with Elecraft. 73 de Tim, WA5MD
|
|
locked
Re: Old versions on the PC
On 11/01/2020 01:18, K5TCJ wrote:
Hi Tim, if we removed old uninstall entries you could not easily install multiple versions of WSJT-X. The redundant uninstaller entries in "Programs & Features" or "Apps & Features" are benign. If you really want to clean them up then you must uninstall every one, ignoring warning messages and including the currently installed version(s), then re-install latest version. You log files and settings will be preserved. If you do not want redundant uninstall entries then uninstall WSJT-X before installing a new version. 73
|
|
locked
Re: IO error when testing PTT control with 'no rig'
On 11/01/2020 02:43, vk3eip wrote:
I am new to WSJT-X and just getting it running on an Ubuntu laptop into an FT-101E. It seems to work and I have had a few QSOs on 20 meters.Hi George, i/o error means the port you specified does not exist, or something else has access, or you do not have rights to access it. Have you added your user to the dialout group? sudo adduser $USER dialout Then logout and back in, by logout I mean log out the whole desktop or just reboot. 73 Bill G4WJS.
|
|