Date   

locked Re: weird random/intermittent/recurring rig control failure

andypdanp@...
 

Hi again Bill--

I tried setting rig control to CAT, and got the same behavior as I mentioned before; the rig keys, i hear a tone but nothing actually goes out over the air. I have a speaker connected to my Rig Blaster's "audio out" monitoring jack, so that's where I can hear the tone, and I see the TX red LED on the radio illuminate and hear the relays click on, but no actual modulation occurs over the air. This happens whether I set front or rear for the audio source. I am using a Kenwood TS-480 SAT and a Rigblaster Advantage, so there is a modular cable going from the RB to the radio's mic jack. There is also a specialty serial 9-pin cable I got from West Mountain Radio that connects between the serial port on the Rigblaster and the serial port on the radio. I got this after learning the hard way that a standard serial cable doesn't work. If I recall right, one of the wires has to be flipped, sort of like the old null modem cables/serial adapters of bygone days.

RTS is the only setup that works it seems. Choosing DTR does not key the radio at all. Current settings of my radio screen are attached.  These work....until they don't ;) 

Also, if I set flow control to Hardware, I immediately get an error that will not resolve until I change that setting back. It says "Hamlib error: IO error while testing getting current VFO. Also attached.

Thanks again for helping me!

73,

Andy K3NP


locked Re: weird random/intermittent/recurring rig control failure

andypdanp@...
 

Hi Bill--

Sure thing. It's attached. Thank you!

73,
Andy K3NP


locked Re: weird random/intermittent/recurring rig control failure

Bill Somerville
 

On 04/01/2020 21:11, andypdanp@... wrote:

Rig: Kenwood TS-480   Poll interval=2s

CAT control: Serial Port 5    (Note that my serial ports for rig control, PTT, and CW keying are virtually created/split by the Rigblaster’s software, which actually uses COM3)

9600 baud (which is also what is set on the radio)

8 data bits, 1 stop bit (per TS-480 manual)

Handshake=none

Force Control lines: DTR (blank) RTS=high

PTT method=RTS    Port=COM6

Mode=USB

Split=Fake it

Andy,

any chance of sharing with us the actual error message from WSJT-X? For you convenience you can copy the full error message text, including the important details panel, to the Windows clipboard by hitting Ctrl+C while the error message window has keyboard focus.

You could use "Settings->Radio->PTT Method" as CAT if you correctly set the Tx audio source setting according to how the audio is fed to your rig by your interface. Set it to Front if it goes to the mic socket, set it to rear if it goes to the ANI pin of the rear REMOTE socket. I believe the RigBlaster interfaces feed the audio to the mic socket.

You should set "Settings->Radio->Handshake" to "Hardware" and leave both Force Control Lines options blank.

73
Bill
G4WJS.


locked Re: Q DX or just CQ.RE: [FT8-Digital-Mode] Option on CQ only to indicate it is a directed CQ such as CQ DX

Gilbert Baron
 

 

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Gilbert Baron <w0mn00@...>
Sent: Saturday, January 4, 2020 16:11
To: jim.w2jc@...
Subject: RE: Q DX or just CQ.RE: [FT8-Digital-Mode] Option on CQ only to indicate it is a directed CQ such as CQ DX

 

2.1.1 and my screen clip shows no such thing.

 

Ver 2.1.2

 

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Jim Cooper <jim.w2jc@...>
Sent: Saturday, January 4, 2020 15:52
To: w0mn00@...
Subject: Re: Q DX or just CQ.RE: [FT8-Digital-Mode] Option on CQ only to indicate it is a directed CQ such as CQ DX

 

On 4 Jan 2020 at 13:16, w0mn00@... wrote:

 

> I have not the least interest I

> using JTALERT. I consider SC Far

> superior for the most part and do not

> wish to use different spotters for

> different modes of operation.

 

I guess everyone has their prejudices...

suit yourself, but then why ask others

to duplicate what you refuse to use?

>

> Actually the decode does NOT show

> the whole message. You get CALL and

> GRID and COUNTRY but you do not see

> the directional information such as

> CQ DX UNTIL you double click to set

> up the standard TX messages and it

> is then too late as it immediately

> transmits a call to the station that

> called CQ no matter if it is CQ  DX

> or any other CQ.

 

graphic

 

I don't know what version of WSJT-X you

are using, but mine clearly shows all directional

and special calls in the decode ... today happens

to be the Rtty roundUp so a lot of them have

that, but DX or EU or MT or any other indicator

for directional calls shows right there ... how

can you miss it if you are double-clicking on it?

 

graphic

 

doesn't your display show those?

 

graphic

 

> To respect the caller I then have to

> stop transmit which has now wasted

> both my time and his.

 

not his, unless you let your call go longer

than about 6 seconds.

 

> I consider that missing needed

> function. If I am missing how to

> make it show that information I did

> not find it in the online

> documentation.

 

it's hard to understand why it would not

show, since it is part of the sent message.

 

  


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


locked weird random/intermittent/recurring rig control failure

andypdanp@...
 

Hello all—

 

 

I’ve been using WSJT-X with JTAlert and my Kenwood TS-480 and WMR Rigblaster Advantage for several years now without issues. But several months ago my desktop PC’s Windows 10 crashed and I had to reinstall Windows 10, and all my programs as well. When I initially reinstalled WSJT-X and JT Alert, I was able to find files with my previous settings in the AppData folder in my saved Windows.old directory (auto-saved files from the previous, crashed installation) on my hard drive, so I didn’t have to manually set all the settings again.

 

However, ever since then, randomly I’ll randomly get a popup that there is a rig control error, with buttons displayed to retry, configure, etc. I click “retry” and it restores to working condition right away. But the problem will recur, typically within 5-10 minutes. It happens more often when I’m just monitoring the radio than when I’m transmitting. It also frequently happens when I first start WSJT-X.

 

Yesterday, I completely uninstalled both WSJT-X and JTAlert, and verified no traces of anything left in folders like AppData, Program Files (x86), etc. Then I rebooted my PC and reinstalled both programs from scratch, and manually re-entered all my settings. Unfortunately, the problem still occurs, though perhaps not as often.

 

Someone on a Facebook group suggested it might be an RF problem; so I re-routed my serial cable that connects the Rigblaster to the radio so that it was no longer wrapped/bundled with other cables. I also discovered that the serial plug to the radio had not been screwed down, so I did that. And I was hopeful that maybe this  was all just due to a loose connection. Unfortunately, it still occurred a couple times tonight, although noticeably less—perhaps twice in 45 minutes, during which I operated and worked a bunch of stations without a problem.  I did various power output levels from 30 to 200 watts; they seemed to work fine for the most part; there was no correlation between using high power and the problem suddenly occurring. Again, this usually happens when I’m not transmitting at all.

 

I also tried changing the settings on the “Radio” tab:

Handshake: I switched between default, none, XON/XOFF,  hardware, etc;

Forcing RTS line low, or high. None of that seems to make a difference.

 

Someone on FB asked me why I have the rig control set for RTS and not CAT; when I select CAT, the rig keys up and I hear a tone, but no audio goes out over the air, and the radio’s wattmeter reads zero watts out. And if I choose DTR, nothing happens at all when I try to tx. I also changed the polling interval from 1 to 2 seconds. I don’t typically use VOX, but I just tried it and it works, albeit with a slight delay to start tx, so I might set it for VOX a bit and see if that changes anything.

 

I do note that when I first start WSJT-X, the problem almost always occurs. I do have JT Alert set to autorun/auto start WSJT-X, so I actually start JTAlert first and it in turn starts WSJT-X and also opens my log, website for PSK Reporter etc.

 

Current radio control settings are:

 

Rig: Kenwood TS-480   Poll interval=2s

CAT control: Serial Port 5    (Note that my serial ports for rig control, PTT, and CW keying are virtually created/split by the Rigblaster’s software, which actually uses COM3)

9600 baud (which is also what is set on the radio)

8 data bits, 1 stop bit (per TS-480 manual)

Handshake=none

Force Control lines: DTR (blank) RTS=high

PTT method=RTS    Port=COM6

Mode=USB

Split=Fake it

 

Latest troubleshooting steps:

-I looked at my ports in Device manager: for the virtual ports created by the Rigblaster software, under the General tab it says “working properly” but under the events  tab it says “Device FABULATECH\VSPC\DEVICE4294967294 requires further installation.”. This is apparently the virtual port driver.

-I unistalled Rigblaster, downloaded latest drivers form WMR, reinstalled RB. Above issue with the ports still persists.

-changed auto start so JTAlert no longer auto starts WSJT-X; I open WSJT-X manually first, then I open JT Alert. *NOTE: now the rig control error happens after opening JTAlert, not WSJT-X.

_I also reinstalled JT Alert from scratch again; under the TCP settings (for text messages etc.) I left the defaults. Previously I had changed them to match what was displayed prior to my computer crash. It was only 1 port of 3 that was 1 number different, and it doesn’t  seem to affect my rig control problem.

 

-I tried leaving just WSJT-X running for a while with no JT Alert; unfortunately, after about 10-15 minutes, the problem happened again.

 

Thanks in advance for any ideas you can provide on how to resolve this problem!  (Maybe a bad USB cable to the Rig Blaster and/or bad CAT control cable between Rigblaster and rig? Or maybe I need to start WSJT-X manually and then start JTAlert afterwards?)

 

73,

 

Andy K3NP

 

 


locked Re: logging QSO

AB8WD-Willie
 

what is the best format or default format to use?


locked Re: logging QSO

Jim Cooper
 

On 4 Jan 2020 at 11:05, willicott@... wrote:

After making contact the log qso
comes up with 04/01/2020 and when I
change the date it still logs that
date. Please help!!
I use that format on my OS and my logs
from WSJT-X are read correctly in QRZ.com
and LotW ... I suggest you not worry about it.


locked Re: logging QSO

willicott@...
 

I tried that but it didn't work '
Thank You


locked Directional CQ

Gilbert Baron
 

I just monitored for 15 minutes. The CQ data is NOT shown UNTIL I click in the band activity window. It then shows the message in the right had window and starts to transmit my call. If it was a CQ DX it is too late and my only choice is to stop the transmitting. If I am missing some way to fix this I am totally without understanding how. I can find nothing about it in documentation.

 

Example of band activity window with or without CQ only on a station that is sending a CQ

 

200345  -6   0.1  1607  ~  WB9RFI  EN31  U.S.A

 

So how am I to know if he is calling CQ DX UNTIL I double click and it appears in the right hand window, Generates standard messages and instantly starts to call him?

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


locked Re: logging QSO

Joe Roper
 

I believe it is the time/date format in your OS. If you're running W10, click on Start in lower left corner, Settings (little gear icon), Time and Language, Date time & regional formatting in upper right corner. If the format down doesn't match the mm/dd/yyyy that I mentioned earlier, click on Change data formats and adjust it there. Hope this helps.

Joe
N7IHB

On Jan 4, 2020, at 13:06, "willicott@..." <willicott@...> wrote:

How do I change that -=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#5134): https://groups.io/g/WSJTX/message/5134
Mute This Topic: https://groups.io/mt/69423738/1925301
-=-=-
WSJT-X Weak Signal Communication . ©2001-2020 by Joe Taylor, K1JT. References : <a href="https://physics.princeton.edu/pulsar/K1JT/refs.html" target="_blank">https://physics.princeton.edu/pulsar/K1JT/refs.html</a>
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/7416643/489129533/xyzzy [n7ihb@...]
-=-=-=-=-=-=-=-=-=-=-=-


locked Reminder to choose "assisted" option when submitting logs for ARRL RTTY RU #ContestMode

Doug Gerard
 

Just a reminder that all log submissions that use WSJT-X for today's
RTTY RU need to categorized as using spotting assistance.  WSJT-X
decodes multiple signals at once and the ARRL says this is classified as
using spotting assistance.

Doug
NP2GG


locked Re: logging QSO

willicott@...
 

How do I change that


locked Re: logging QSO

Joe Roper
 

Your date format looks like it may be set to dd/mm/yyyy instead of mm/dd/yyyy.


Joe

N7IHB


locked logging QSO

willicott@...
 

After making contact the log qso comes up with 04/01/2020 and when I change the date it still logs that date. Please help!!


locked Suddenly, in the middle of QSO, power dropped to near zero

Jim Sjoberg
 

Running v2.1.2 and multiple instances
Have been making QSO's for months no problem.
In the middle of a QSO my power dropped to almost nothing on my slice A.
Clicked on slice B, second instance, and all ok at about 50 Watts.
I am using Flex 6700, Windows 10, and Maestro.
Restarted program many times, rebooted computer many times, checked/compared settings, switched to backup rig Flex 6400, and also re-ran all under smart sdr and still have power loss on slice A.
I even re-installed v2.1.2. no change.
Both rigs work fine CW and SSB.
DAX window looks good.
I am at a loss.
Any help out there?


locked Guidelines for RU this weekend #ContestMode #WSJTX_config

Andrew OBrien
 

Just FY, I the following link

http://www.arrl.org/files/file/ContestResults/2019/January%202019%20QST%20-%20Taylor%20-%20FT8.pdf

is posted by ARRL and contains recommendations from Joe Taylor , K1JT,  about use of JT modes for this event.

Andy K3UK 


locked #GroupNews Group transition

Andrew OBrien
 

Just a brief note to confirm that the Yahoo group WSJTGROUP will be closing in a few days time and their membership will receive an invitation to join this group .  The moderators of that group will join the moderator team at this group. 

For those of you that have already moved over from WSJTGROUP , if you get a invitation from me, please ignore it.  The invitation is based on a mass mailing list. 

The goal is to make the transition as seamless as possible. Joe Taylor and team will make the necessary alteration to the links on the WSJTX web site.   This group's settings may differ a little from the Yahoo group. 

Andy K3UK 
Owner 


locked Re: Question for K1JT

Andrew OBrien
 

Neil , you might want to try sending this directly to Joe via his email address listed at QRZ.com 

Andy K3UK 


locked Re: Windows 10 and WSJTX-X Update installation

Martin G0HDB
 

On Tue, Dec 31, 2019 at 12:09 PM, Gilbert Baron wrote:

About this method, all I can say is you may be careful enough but even for you it is a disaster waiting to happen, I assume you have good backups.

It would only be a disaster if you didn't check, preferably at least twice, what you're about to do before doing it, but that's no different to many other things in life - measure twice and cut once!  And yes, I do have good (multiple) backups.

--
Martin G0HDB


locked Re: No power on transmit

Sid Frissell
 

Joe:  To solve most of my WSJT-x problems, i do a restart not a new download.  Just restarting a program can solve many of your problems.  Try that first.
Sid NZ7M

On Jan 2, 2020, at 12:06 PM, Bill Somerville <g4wjs@...> wrote:

On 02/01/2020 19:04, n5fjy wrote:

Hi Dave,

 

I did reset them before I reinstalled the app. What I did find out in experimenting is that it will transmit when set to split and fake it.

 

After multiple tests it does not transmit is split is set to none. Which was my initial config.

 

Not sure what is going on but I will continue to investigate.

 

Thanks for the replay and Happy New Year.

 

Joe

N5FJY

Joe,

those symptoms are consistent with you having set your Tx audio offset outside of the pass band of your rig's SSB filter. "Settings->Radio Split Operating" is there to remove that limitation and to keep your Tx signal clean.

73
Bill
G4WJS.

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#5123): https://groups.io/g/WSJTX/message/5123
Mute This Topic: https://groups.io/mt/69384746/878628
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4413322/1551603132/xyzzy  [sidfrissell@...]
-=-=-=-=-=-=-=-=-=-=-=-