Date   

locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

Bill Somerville
 

On 03/11/2021 16:16, Andy TALBOT wrote:
Oh dear, red face, I must be getting too old for this sort of thing
Yes, you're quite right, command 03 is just a straightforward one; send and wait for response

Andy

Hi Andy,

also I think the warning is simply to remind users that a CAT "POWER OFF" command is not really powering off the rig since there is a matching "POWER ON" command. So I think it is just about preserving battery life.

73
Bill
G4WJS.


locked Re: Possible to Adjust Time to Match Sending Station? #Timesync

chas cartmel
 

Alan" I have not used as a default timekeeper so I do not know how it performs in the long term."In answer to your perceived question above, the default for windows is totally inadequate for WS modes.73 CharlieG4ESTwww.g4est.me.ukStay safe out there-----Original Message-----From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Alan G4ZFQSent: Wednesday, November 3, 2021 4:01 PMTo: main@...: Re: [WSJTX] Possible to Adjust Time to Match Sending Station? #Timesync> I think the only way is to stop sync and adjust your clock manually. > But if there exists a sync software with this capability I'm interested, too!Pietrohttps://www.qsl.net/dl4yhf/rsNTP/rsNTP.htmI have used this on Windows 10.I have not used as a default timekeeper so I do not know how it performs in the long term.73 Alan G4ZFQ


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

Andy Talbot
 

Oh dear, red face, I must be getting too old for this sort of thing
Yes, you're quite right, command 03 is just a straightforward one; send and wait for response


locked Re: #FoxAndHound: Please do not QSY back to "normal" frequency

Bill Somerville
 

On 03/11/2021 16:10, Philip Rose via groups.io wrote:
This afternoon I was on 12m, and on the IC-7300 spectrum scope I could see FT8 activity 5kHz down. Tuned down to see what it was and it was the HD8R DXPedition. Thought I would join the throng so went into Hound mode. I wondered why I was now seeing normal transmissions and realised that setting "hound" mode had reset the frequency to the normal for 12m.

I assume that the dial frequency was 18.095 - this put the fox on 530 Hz plus the 3 60 Hz higher. When they came back, I cleared the "Enable TX" in my excitement - I had the mouse hovering over it to re-enable it when it was cleared after too many transmissions.

-- 73 Phil GM3ZZA
Hi Phil,

I can't offer anything with respect to the coupling between changing settings and resetting the CAT connection, at this time, but in FT8 DXpedition Mode the ENTER key is a shortcut to enable transmit, which will at least mean you can avoid unintended mouse clicks on the "Enable Tx" button.

73
Bill
G4WJS.


locked #FoxAndHound: Please do not QSY back to "normal" frequency

 

This afternoon I was on 12m, and on the IC-7300 spectrum scope I could see FT8 activity 5kHz down. Tuned down to see what it was and it was the HD8R DXPedition. Thought I would join the throng so went into Hound mode. I wondered why I was now seeing normal transmissions and realised that setting "hound" mode had reset the frequency to the normal for 12m.

I assume that the dial frequency was 18.095 - this put the fox on 530 Hz plus the 3 60 Hz higher. When they came back, I cleared the "Enable TX" in my excitement - I had the mouse hovering over it to re-enable it when it was cleared after too many transmissions.

--
73 Phil GM3ZZA


locked Re: WSPR Spot validation #WSPR

Roland
 
Edited

On Wed, Nov 3, 2021 at 05:06 PM, <groups@...> wrote:
Many qrz.com entries for those using WSJTX are out of date or just
wrong, sometimes deliberately for privacy reasons.

Me? I don't change qrz.com when I'm not operating from home.

I am totally against using qrz.com for amending my decoded messages and
would block that website if necessary to prevent WSJTX from making any
changes.


Roland

You are making it very difficult to follow your argument as you're not
including the comments you're replying to.

73
Roger
moderator
Roger thanks for sharing. Do you have any other ideas to reduce false Spots being uploaded and stored in the Database? Look at the Screenshot in my opening post. I am still looking for ways to count these error Spots. Is it 1%, 10% of all the WSPR Spots or even more?

It looks substantial to me, try this DB query showing Spots last 24h where distance is > 10000 km and SNR < 0 dB


locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

PFA
 
Edited

Hi Mike, Andy

some notes / clarifications

My Rig is mcHF-QRP (http://www.m0nka.co.uk/) an open HW device, running UHSDR sw  (https://github.com/df8oe/UHSDR).
Its CAT interface is emulating FT817.
Everything were fine till Hamlib 4.3.0, and CAT for 817 was fine reading VFO, as well FT847. Starting from Hamlib 4.3.1, on my case, cat for ft817 is failing read back VFO.   


@Mike
Your reply doesn't  match with my observations (not yet open the src code ...) with Hamlib till 4.3.0:
  • FT817 and FT847 seems support in some way the VFO read back and wsjtx updates the freq box according my rig manual setting
  • FT847UNI is not reading back the VFO since CAT is unidirectional. Freq BOX on wsjtx become RED and value is set to "0". This affect ADIF file that report wrong band and freq. (very annoying)  
any way this evening I'm going to repeat tests using a real FT817.

Will followup


--
73 paolo IU2OMT


locked Re: WSPR Spot validation #WSPR

Roger
 

On 03/11/2021 14:20, Roland wrote:
Many are already registered members on qrz.com (free or paid sub). In order to use the XML API ( https://www.qrz.com/page/current_spec.html ) you need to have an XML subscription (USD29.95/year). I use the service for several other HAM-related programs, so WSJT-X would just be another use case for their service. The API provides a convenient way to search for calls locators etc.
You are not forcing anyone to subscribe to qrz.com if you make it an option in WSJT-X.
73
Roland

Many qrz.com entries for those using WSJTX are out of date or just wrong, sometimes deliberately for privacy reasons.

Me? I don't change qrz.com when I'm not operating from home.

I am totally against using qrz.com for amending my decoded messages and would block that website if necessary to prevent WSJTX from making any changes.


Roland

You are making it very difficult to follow your argument as you're not including the comments you're replying to.

73
Roger
moderator


locked Re: Possible to Adjust Time to Match Sending Station? #Timesync

Alan G4ZFQ
 

I think the only way is to stop sync and adjust your clock manually. But if there exists a sync software with this capability I'm interested, too!
Pietro

https://www.qsl.net/dl4yhf/rsNTP/rsNTP.htm
I have used this on Windows 10.
I have not used as a default timekeeper so I do not know how it performs in the long term.

73 Alan G4ZFQ


locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

Michael Black
 

You may be misreading the manual.
It's the Power On/Off that talks about the battery pack.

Mike W9MDB


Inline image





On Wednesday, November 3, 2021, 09:59:20 AM CDT, Andy TALBOT <andy.g4jnt@...> wrote:


Reading this thread piqued my intrigue, so went and had a look at the manual for my FT817ND.  The CAT command for getting frequency is there, but has the feeling of having been added as an afterthought.  It looks bodged

Issue CAT command 03 with 4 dummy bytes
It should return 5 bytes of data with frequency and mode.  
BUT BUT BUT ...

In footnotes, firstly it states "Do not use this command when using alkaline batteries or the supplied FNB-85 Ni-MH battery pack"
Then it goes on to state "Send a 5-byte dummy data (such as 00 00 00 00 00) first when sending this command

Why the battery pack should affect this particular CAT command  I shudder to think





locked Re: Possible to Adjust Time to Match Sending Station? #Timesync

Michael Black
 

Look for TimeFudge on my QRZ page.
I have a Windows executable and source code for Linux/Unix.

Mike W9MDB




On Wednesday, November 3, 2021, 10:32:07 AM CDT, Pietro Molina <pietro@...> wrote:


I think the only way is to stop sync and adjust your clock manually. But if there exists a sync software with this capability I'm interested, too! 

Pietro I2OIM

Il giorno mer 3 nov 2021 alle ore 16:24 K1dj via groups.io <k1dj=aol.com@groups.io> ha scritto:
Is it possible to adjust my time to match an off-time DX station?  [Right now, 7P8RU's clock is running about 1.2 sec fast.]
73 - Rich, K1DJ






locked Re: Possible to Adjust Time to Match Sending Station? #Timesync

Pietro Molina
 

I think the only way is to stop sync and adjust your clock manually. But if there exists a sync software with this capability I'm interested, too! 

Pietro I2OIM

Il giorno mer 3 nov 2021 alle ore 16:24 K1dj via groups.io <k1dj=aol.com@groups.io> ha scritto:
Is it possible to adjust my time to match an off-time DX station?  [Right now, 7P8RU's clock is running about 1.2 sec fast.]
73 - Rich, K1DJ



locked Possible to Adjust Time to Match Sending Station? #Timesync

K1dj
 

Is it possible to adjust my time to match an off-time DX station?  [Right now, 7P8RU's clock is running about 1.2 sec fast.]
73 - Rich, K1DJ


locked Re: Exact frequency span occupied #TechnicalHelpQuestion #FT8

Kermit Lehman
 

This is okay if it's an option, which is what Ellis suggested. Otherwise, one should be allowed to transmit anywhere your governmental rules allow. The existing bands have no official status.  And DXpeditions can be all over the place.


It's very nice to have all the FT activity grouped together in 3 kHz segments where you can see all the activity at once, but that's not an official requirement.  20m and 40m at their peak times are extremely crowded and folks should be encouraged to spread out beyond the normal segment.  Moving up is better in my opinion as those higher frequencies are already claimed by WSJT-X for essentially obsolete modes.


The only exception here in the USA would be the 60m band, which is channelized and passband limited to a SSB signal width of 2.8 kHz . FT8 is done at the dial frequency of 5357.0 kHz.  FT8 can operate anywhere within that 2.8 kHz.


73,

Ken, AB1J






-----Original Message-----
From: Ellis Birt (G7SAI) via groups.io <ellis.birt@...>
To: dave@...
Cc: main@wsjtx.groups.io
Sent: Wed, Nov 3, 2021 2:53 pm
Subject: Re: [WSJTX] Exact frequency span occupied #help #FT8

It might be worth asking the WSJT-X developers to add the option of setting frequency limits for each band.  That way there would be no risk of transmitting out of band

On Wed, 3 Nov 2021 at 14:49, David Gould <dave@...> wrote:
Thanks Bill

73
Dave G3UEG






locked Re: WSPR Spot validation #WSPR

Roland
 
Edited

On Wed, Nov 3, 2021 at 03:53 PM, Reino Talarmo wrote:
If GM1BAN sends 4 character locator, how the receiving entity can provide 6 character locator to the spot collector?
http://www.wsprnet.org/drupal/node/7109


locked Re: WSJT-X 2.5.0 and MCHF: issue reading-back the VFO setting #Cat_RigControl #linux #Yaesu #IssueReport

Andy Talbot
 

Reading this thread piqued my intrigue, so went and had a look at the manual for my FT817ND.  The CAT command for getting frequency is there, but has the feeling of having been added as an afterthought.  It looks bodged

Issue CAT command 03 with 4 dummy bytes
It should return 5 bytes of data with frequency and mode.  
BUT BUT BUT ...

In footnotes, firstly it states "Do not use this command when using alkaline batteries or the supplied FNB-85 Ni-MH battery pack"
Then it goes on to state "Send a 5-byte dummy data (such as 00 00 00 00 00) first when sending this command

Why the battery pack should affect this particular CAT command  I shudder to think


locked Re: Exact frequency span occupied #TechnicalHelpQuestion #FT8

Ellis Birt (G7SAI)
 

It might be worth asking the WSJT-X developers to add the option of setting frequency limits for each band.  That way there would be no risk of transmitting out of band


On Wed, 3 Nov 2021 at 14:49, David Gould <dave@...> wrote:
Thanks Bill

73
Dave G3UEG



locked Re: WSPR Spot validation #WSPR

Reino Talarmo
 

On 03/11/2021 12:56, Roland wrote:
Biil, GM1BAN is only sending 4 character locator as all of our Beacons
Many of the large volume WSPR spotting sources are not using WSJT-X so I guess they are forming spots from their own decoders, or more likely from running the underlying wsprd decoder application. Do you know if these bad spots are more prevalent from particular types of spot sources?
Hi Roland,
If GM1BAN sends 4 character locator, how the receiving entity can provide 6 character locator to the spot collector?

By the way could the spot collector check the validity of the call - locator pair or are there too many spots arriving for current computers? Also any data analyzing program should filter out clear outliers as in your example. Of course single spots of a station are that simple and an external database could be a proper solution (if it is up-to-date).

73, Reino OH3mA


locked Re: Exact frequency span occupied #TechnicalHelpQuestion #FT8

David Gould
 

Thanks Bill

73
Dave G3UEG


locked Re: Hamlib update for Xiegu G1M #Cat_RigControl

Antony Watts <antonywatts@...>
 

Absolutely no luck I'm afraid. Installed flrig for Mac (v "bs"). Chose G90 as rig, 19200, /dev/tty.usbserial110 seems to be the port.

Every time Ihit "init" the program crashes..

Will keep fiddling about, but this program seems somewhat sensitive and flaky?

10481 - 10500 of 40086