Date   

locked Re: FT8 intermittent decoding

jmontsecal@...
 

Hi,
     I have been in the similar situations several times and for different reasons: Low audio level, excessive audio level, receiver not in "Data mode" in my IC-7300,  plugged or unplugged the earphones in W10 and the audio changes the configuration or with some audio improvement active,  receiver in narrower bandwidth mode, W10 audio configuration no set to the correct sampling rate and bits, ....  and yesterday every thing was perfect and nice signals but not decoding .... It was in LSB mode ..


locked Re: Power Transmitted vs Power Out #FT8 #FT4

George J Molnar, KF2T
 

When you don't use rig control, and operate away from the center of your transmitter's passband (audio response), you will transmit at lower and lower power the further you get. At 100 Hz or 2900 Hz, for example, some radios will barely put out anything, despite whatever your sound card is pumping out.

Moral of the story - Use "fake it" and rig control whenever you can. Or stay in the middle of the waterfall as best possible.


locked Re: #icom #706

Bob Lewis
 

One other check to make. With the digi-one connected, measure the voltage on the PTT line when it is trying to key the radio. I have seen cases where the PTT circuit in the in the interface does not pull the PTT line low enough to activate the radio’s PTT. It should be well under 1 volt. Make sure there is no significant series resistance in the PTT line (RFI chokes, etc).

 

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chris Rayner
Sent: Friday, August 28, 2020 6:32 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #icom #706 #ACC

 

Many thanks to all of you for taking the time to respond - the ham community never ceases to amaze me how generous people are with their time.

@Dave (VE3WEJ) - no menu setting for the 706 (MkI), only for the MkII. And as flagged, the pin 3 SEND function is both input & output.

@Martin/Bruce: I've tried the following
(1) ACC connected to 706, shorting pin 3 (SEND) to pin 2 (GND) - 706 transmits (so looks like the 706 is doing what it should)
(2) Moving to the other end of the ACC cable (where it joins my DigiOne+ board), again, if I short SEND to GND, the 706 transmits - so the cable is also OK

The issue seems to be in the DigiOne+ board. Now, here's the issue - I didn't design it, so I don't know how it's setup. I've contacted Allan (designer) and am awaiting his feedback.

So, I'm still drawing a blank at the moment.

Chris
G7BED 


locked Re: Time Sync Software

Alan G4ZFQ
 

> Get it to synch more frequently than 7 day default, I use 7200, every
2 hours.
http://noosphere.princeton.edu/time.regedit.html
Dave,

I checked my W10 Home this morning, I found the default was 32768 (~9 hours).
I can't imagine the retail seller changing that on a new installation.
Not many computers would need more than that although I did make it 14400.

73 Alan G4ZFQ


locked Re: #icom #706

Chris Rayner
 

Many thanks to all of you for taking the time to respond - the ham community never ceases to amaze me how generous people are with their time.

@Dave (VE3WEJ) - no menu setting for the 706 (MkI), only for the MkII. And as flagged, the pin 3 SEND function is both input & output.

@Martin/Bruce: I've tried the following
(1) ACC connected to 706, shorting pin 3 (SEND) to pin 2 (GND) - 706 transmits (so looks like the 706 is doing what it should)
(2) Moving to the other end of the ACC cable (where it joins my DigiOne+ board), again, if I short SEND to GND, the 706 transmits - so the cable is also OK

The issue seems to be in the DigiOne+ board. Now, here's the issue - I didn't design it, so I don't know how it's setup. I've contacted Allan (designer) and am awaiting his feedback.

So, I'm still drawing a blank at the moment.

Chris
G7BED 


locked Re: Time Sync Software

Dave H
 

Hi,

 

You just need to "Tweak" Windows Time

> Get it to synch more frequently than 7 day default, I use 7200, every 2 hours.
   http://noosphere.princeton.edu/time.regedit.html

> Use a ntp server from a ntp pool in your Geography, just type a new one in the Window Server Box
   https://www.pool.ntp.org/zone/us

GL - 73 - Dave ~ G8LIY


locked Re: Rig Control error

Svein Henriksen
 

Bill,

 

Understand all that but as you indicated, that does not help any.

As long as Radio has been configured to None, HAMLIB should simply open the COMPORT and toggle the RTS on and off.

So it is definitely a bug/anomaly/misconceived functionality there that should be fixed.

Or even better, WSJT-X should not go via HAMLIB when no radio is configured but rater control the RTS directly. That is a simple matter to achieve.

So how do I contact the HAMLIB guys?

 

73 de LA3PU Svein

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: torsdag 27. august 2020 17:06
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig Control error

 

Hi Svein,

 

Hamlib does close a serial port used just for PTT when PTT is reset, the intent is to allow other applications to also key the radio so long as they do the same. The port is held open while PTT is set as an attempt to do so exclusively. The whole arrangement is supposed to emulate a "wired-OR" physical connection without each application requiring a separate serial port.

 

I'm not sure any of that helps here, except it might explain why the error happens when it does, i.e. it may be happening on a PTT set after a period with the PTT reset during which something happens that makes reopening the serial port impossible.

 

Serial ports in an idle state can become active if they receive data or if certain control lines are set (e.g. RI). I now you state that nothing is connected to the serial port, nevertheless this may be a clue. I see you are running on Windows, I'm not even sure if Windows Desktop systems respond to login attempts on serial ports, if it were Linux I would suggest making sure the serial port login handler was disabled for that serial port.

 

73
Bill
G4WJS.

 

On 27/08/2020 15:48, Svein Henriksen wrote:

Bill,

 

Only the RTS pin and pin 5(GND) are connected. Nothing else is connected to the computer at all besides audio in and out. I made the cable myself and yes it is screened. It goes to a control box where it drives an OPTOCOUPLER. So it is galvanically isolated from the radio. Since I did not have the problem on the previous computer at all, it is likely some timing difference between the two with respect to the comport responding then. Such differences must surely be taken into account in software.

So could be that HAMLIB is too quick to report if it does not detect the comport immediately.

 

73 de LA3PU Svein

 

 

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: torsdag 27. august 2020 13:06
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig Control error

 

Hi Svein,

 

WSJT-X, using Hamlib, opens the COM port being used for PTT control via RTS or DTR even though the port is not used for RS-232 CAT control. It the o/s reports the port as not available. or other related errors, then Hamlib and consequently WSJT-X reports that error. Is anything else connected to that serial port? Have you check the physical connections used for PTT control?

 

73
Bill
G4WJS.

 

On 27/08/2020 11:10, Svein Henriksen wrote:

Bill,

 

It definitely looks like it helps to set the polling frequency higher. I have set it to 30 seconds. The problem then comes much more seldom.

When it does it is often immediately after I double click on a station to answer a CQ call and seconds before the RTS line and hence the transmitter is even activated. So it definitely has nothing to do with RFI.

Now any computer has a few mV of noise on the comport lines. In my case only the RTS line is even connected.

So if it is noise that occasionally  triggers it this means that HAMLIB and / or WSJ-X (due to the way it has been integrated) is polling the com line for a radio that is not configured and not connected.

So this is definitely a bug. When Radio: None has been configured there should be no polling

Can you mention this to the HAMLIB people perhaps, or should I? How do I eventually contact them?

I will now try and install a couple of 100 nF capacitors from pins 2 and 3 to pin 5. I see on the oscilloscope that this attenuates the noise present. Its only a few mV and this is way below the threshold on an RS232 line so it could be pulses occurring now and then due to some WIN thingy and 100 nF may not be enough so I am dubious that this will help. But I think it should not be this way anyway.

 

73 de LA3PU Svein.

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: tirsdag 25. august 2020 19:52
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig Control error

 

On 25/08/2020 18:46, Svein Henriksen wrote:

Bill,

 

This morning everything started up without problems and has worked for some QSOs without failing.

But just now, a few minutes after finishing a QSO on FT8, the POPUP window appears.

Rig Error: Do you want to configure the radio interface?

On pressing Details: it says: HAMLIB error: IO error while opening connection to the rig.

Pressing retry and it goes back to working normally.

There is only one COM port (COM1) ant it is used for PTT with RTS.

No rig connected and in setup rig is set to none.

Nothing connected to any of the USB ports.

The WSJT-X is V2.2.2.

On the old computer I was running 2.2.0. Setup the same. Only one COM port and nothing else connected.

I never had this, or any other, problem while using this.

Maybe I need to roll back to 2.2.0.

I seam to remember having read similar reports with regard to HAMLIB on the reflector after the release of 2.2.2.

Is the old versions available on Princeton and any special precautions if rolling back?

 

Any other suggestions?

 

73 de LA3PU Svein

Hi Svein,

that sounds like RFI problems, does it only happen during QSOs on one band? Does reducing your transmitter power improve the situation?

As you say nothing is connected to your PC USB ports I assume this is a real serial port, you could try some ferrite clip on chokes at the PC end of the serial cable, or maybe just re-routing the serial cable to the rig. What interface are you using for the RTS to PTT switching, and where does it draw power from?

73
Bill
G4WJS.

 


locked FT8 intermittent decoding

Wayne ( VE3JV )
 
Edited

This month, off & on, I have been trying to get WSJT-X working on a new Win 10 PC. I previously used a Dell Win Vista PC, but WSJT-X on Vista is no longer supported :(
Ever since I installed WSJT-X on the new PC, I get inconsistent decoding (no decodes in a lot of time slots that have signals, ‘sometimes’ 1-3 decodes, and today [for the first time!] a slot with 5-10 decodes). When I plug the same USB cable in the old PC, I get 10 times the number of decodes.
I have checked all the settings (Win 10 and WSJT-X) that I can think of.
Icom IC-7600 using direct USB cable to PC.
Win 10 V1909 with Icom driver V1.30 and Mic USB audio codec level -22.6 dB, 1 channel 16 bit 48000 Hz (DVD quality) audio.
Time sync by Dimension 4.
Incoming audio ‘seems’ ok (listened to .wav file from WSJT-X, and a .m4a file recorded by Voice Recorder), but I’m no audio expert.
Sometimes I think there should be more sigs than show on the Wide Graph (as compared to on the old PC).
I tried uninstall & re-install of the Icom driver. Port # changed, but otherwise no difference.
Quite often it seems I have to reset the audio settings to USB audio codec in WSJT-X (happens on both PCs). But that’s if I have changed PCs or turned the radio off, etc.
A screenshot of WSJT-X on the new PC is attached (I hope).

Does anyone have a suggestion? What did I forget to do? :) Maybe it’s a hardware or Win 10 audio problem on the new PC?
If anyone is running a similar setup, what versions of software are you using (Icom driver, Win 10, WSJT-X). Can I still get a copy of the previous WSJT-X V2.1.2 64 bit (.exe) for Win10 somewhere to try?

Thanks in advance for any help.

73 de Wayne VE3JV


locked Ubuntu 20.04 + Yaesu FT991a / WSJT-X Processing Stops After Transmit

Keith/KI5US
 

Does anyone else have the problem (and, hopefully, a solution) to WSJT-X halting processing after first transmit after running WSJT-X?  Prior to upgrading from Ubuntu 19.10 to 20.04 and to the current version of WSJT-X, everything worked fine.  Under 20.04, FLDIGI, QSSTV, and FLRIG continue to work perfectly.  The problem seems unique to WSJT-X.  And, yes, lots of ferrite cores, low power, etc, in use.  I'm using puavcontrol for the audio connection.  

When I start WSJT-X, the waterfall correctly displays signals and they are decoded in the Band Activity box. The initial transmission after starting WSJT-X seems to work. Then the FFT and waterfall displays seem to freeze and no further decoding occurs in the Band Activity box.

The WSJTX application also doesn't stop when closing the program - I have to kill it every time using top or system monitor.

Any help would be much appreciated.
Thanks
73
Keith Lindsay/KI5US


locked Re: #icom #706

Bruce
 

Hello Chris,

You are correct, this is not software issue but a hard ware issue. Because you did not give much information, I will start with the basics.

Trouble shoot both the cable and radio by checking this pin in reverse. By that I mean... Key the mic and (using VOM) check if the pin voltage toggles from high to low. Make voltage check both at end of cable and direct at pin 3 of DIN ACC socket. You want to check for HI in RX and low in TX. Email me direct with results and I will go from there for you. My direct is W8HW@....

73, Bruce, W8HW

==============================


On 8/27/2020 5:30 PM, Chris Rayner wrote:

Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED

    


locked Re: Power Transmitted vs Power Out #FT8 #FT4

Martin G0HDB
 

On Thu, Aug 27, 2020 at 09:20 PM, Ken White wrote:

Thanks Martin. I've made the adjustments as you suggested. The 718 is set to 100 watts, the software slider set to max, and I've adjusted my signal to 30 watts via the Signalink's TX pot. 
I reviewed my Mac's SL-USB's audio codec playback setting. The level is set to 0dB - which is the maximum level. 
Time to "play radio".

Sounds good, Ken.

Just out of interest, when you turn up the 'Tx' pot on the SL-USB so that you get as close as you can to 100W out of the 718, what's the ALC reading on the 718?  Ideally it should be zero or as close to zero as possible.  If it is, then your signal should be acceptably clean.

FWIW, I'm currently using an IC-7610 with a G4ZLP datamodes interface; this is functionally almost identical to the SL-USB but has much better LF noise performance (on both Tx and Rx).  When I turn up the Tx drive level pot on the G4ZLP device I find that I start to see an ALC reading on the 7610's meter when the RF power output is about 85W.  However, I never need to run the 7610 at this output level because I use the 7610 to drive a KPA500 amp that gives me our legal limit of 400W out with approx 25W in from the 7610, so there's never any ALC action on the 7610.

Have fun playing radio; I hope we can have a QSO sometime!

73
--
Martin G0HDB


locked Re: #icom #706

Dave Garber <ve3wej@...>
 

dual purpose, ok...


Dave Garber
VE3WEJ / VE3IE


On Thu, Aug 27, 2020 at 6:35 PM Bob Lewis <aa4pb@...> wrote:

Pin 3 is an input/output. If you key the PTT with the mike, pin 3 is pulled to ground. If you ground pin 3 then the PTT is keyed.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Dave Garber
Sent: Thursday, August 27, 2020 6:11 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #icom #706 #ACC

 

wirings I see says pin 3 is for keying an amp.....    recheck the manual again

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Thu, Aug 27, 2020 at 6:09 PM Dave ve3wej <ve3wej@...> wrote:

i cant remember, but was there not a menu item that tells the radio to use the acc for input, instead of mike jack, or something like that??

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Thu, Aug 27, 2020 at 5:31 PM Chris Rayner <Chris.rayner06@...> wrote:

Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED



locked Re: #icom #706

Martin G0HDB
 

Hi Chris, when you refer to grounding pin 3 are you connecting pin 3 to pin 2 which is the GND connection on the 13-pin socket?  Have you tried just connecting a switch between pins 2 and 3 and toggling it to check that the rig goes into transmit?

If it doesn't then perhaps there's an internal fault that's preventing the grounding of pin 3 from keying the rig.

Also, what do you have connected to pin 3 - are you using something like an open-collector transistor or perhaps a reed relay, connected between pins 3 and 2, as the means of grounding pin 3?

--
Martin G0HDB


locked Re: Receiving Indicator

Gary - AG0N
 

On Aug 27, 2020, at 13:05, Neil <n4fn.neil@...> wrote:

Looking at the Receiving Indicator on the Left, between the band drop down and Receiving Green button what seems to be the optimum dB to see?
When properly set (there are specific instructions) the radio should be tuned to an open frequency on the band you are wanting to operate. No signal, only white noise. Monitoring that white noise, your meter (mentioned above) should indicate a level of 30. Any incoming signal will raise it above that point.

Gary - AG0N


locked Re: #icom #706

Bob Lewis
 

Pin 3 is an input/output. If you key the PTT with the mike, pin 3 is pulled to ground. If you ground pin 3 then the PTT is keyed.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Dave Garber
Sent: Thursday, August 27, 2020 6:11 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #icom #706 #ACC

 

wirings I see says pin 3 is for keying an amp.....    recheck the manual again

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Thu, Aug 27, 2020 at 6:09 PM Dave ve3wej <ve3wej@...> wrote:

i cant remember, but was there not a menu item that tells the radio to use the acc for input, instead of mike jack, or something like that??

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Thu, Aug 27, 2020 at 5:31 PM Chris Rayner <Chris.rayner06@...> wrote:

Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED


locked Re: #icom #706

Dave Garber <ve3wej@...>
 

wirings I see says pin 3 is for keying an amp.....    recheck the manual again

Dave Garber
VE3WEJ / VE3IE


On Thu, Aug 27, 2020 at 6:09 PM Dave ve3wej <ve3wej@...> wrote:
i cant remember, but was there not a menu item that tells the radio to use the acc for input, instead of mike jack, or something like that??

Dave Garber
VE3WEJ / VE3IE


On Thu, Aug 27, 2020 at 5:31 PM Chris Rayner <Chris.rayner06@...> wrote:
Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED


locked Re: #icom #706

Dave Garber <ve3wej@...>
 

i cant remember, but was there not a menu item that tells the radio to use the acc for input, instead of mike jack, or something like that??

Dave Garber
VE3WEJ / VE3IE


On Thu, Aug 27, 2020 at 5:31 PM Chris Rayner <Chris.rayner06@...> wrote:
Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED


locked Re: Power Transmitted vs Power Out #FT8 #FT4

Ken White
 

I'll have to try and relate the information in the article to my Macbook.


locked Re: Power Transmitted vs Power Out #FT8 #FT4

Roger
 

On 27/08/2020 19:24, Ken White wrote:
Enjoying FT4/8 and learning a lot from the Group. My setup appears to be working for me but I'm curious about something.
My setup includes an Icom IC-718, Signalink USB, Diamond SX-200 SWR/PWR Meter, Macbook Computer, and an OCF Dipole Antenna. I do not use Rig Control. The antenna is tuned to an SWR of 1.2:1.
Although my setup appears to be effective I've noticed that in order to transmit a 30 watt digital signal, I have to set the 718's output at 50 watts. Is this something that I should expect or am I losing 20 watts somewhere along the way?
Have a read of this post:-

https://wsjtx.groups.io/g/main/topic/setting_windows_wsjt_x_tx/75435187?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75435187


locked #icom #706

Chris Rayner
 

Has anybody else had issues with the Icom 706 ACC 'SEND' function?

I have an early 706 (i.e. NOT the MkII/MkIIg) which has a 13 pin DIN ACC socket. Pin 3 is SEND, which when grounded should key transmit.

When I ground Pin3/SEND - the 706 doesn't transmit. 

There are no menu items to configure VSEND or HSEND like on the early 706. 

Would welcome any thoughts on this one.

Thanks
Chris
G7BED