Locked
Re: Vertical spikes every 1000 hz prevent decoding
Joe KN5Y
Is this some sort of distortion?
|
|
Locked
Re: Vertical spikes every 1000 hz prevent decoding
Joe WB9SBD
There is something else wrong.
toggle quoted message
Show quoted text
Those spikes are not all that strong PLUS you have room for 100 signals in-between each of them. Reason for no decoding is, I don't see any signals to decode! Joe WB9SBD On 10/9/2020 4:22 PM, Joe KN5Y via
groups.io wrote:
Seen in v2.2.2. |
|
Locked
Vertical spikes every 1000 hz prevent decoding
Joe KN5Y
Seen in v2.2.2.
Windows 10/Yaesu FT-991A loaded USB drivers and can Rx/Tx No decoding because of strength of vertical spikes every 1000 hz. Don't hear spikes.j |
|
Locked
Re: Windows 10 app Vol Device Prefences slider grayed out
JP Tucson, AZ
Hi Ted, Wish I had of heard about your usb hub earlier! ...and your fix may only be temporary! Usb hubs have a nasty habit of interfering with wsjtx & soundcards; as they can have power shut downs with power save modes! (Even if you turn off your power save) And like the audio settings, windows can reassign stuff causing loss of contact with the hub. I know SignaLink, for example, specifically states not to use usb hubs because of these issues. If your problem starts up again, that usb hub is your first likely suspect! Just remove it & connect your usb cable directly to see if it works properly. 73 - John - N7GHZ On Fri, Oct 9, 2020, 9:17 AM teka920 <ted.g7obf@...> wrote: Thanks everbody - now got WSJT working |
|
Locked
Re: Windows 10 app Vol Device Prefences slider grayed out
teka920
Thanks everbody - now got WSJT working
The answer to my orginal question about the grayed out slider in Windows 10 settings appears to be that it is of no significance and that others have the same. To get my setup working I have
73 de Ted |
|
Locked
Re: error message on loading WSJT-X
On 09/10/2020 13:02, Bill Somerville
wrote:
On 09/10/2020 11:20, m_scot_alex wrote: Hi Mike, sorry, that's not quite right. The 64-bit Windows WSJT-X v2.3.0 RC1 uses Qt 5.15.1 for MinGW-w64. We will be reverting to v5.15.0 for the next release due to this https://bugreports.qt.io/browse/QTBUG-83084?focusedCommentId=529050&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-529050 which has led to this still in progress issue https://bugreports.qt.io/browse/QTBUG-87057 . 73 |
|
Locked
Re: error message on loading WSJT-X
On 09/10/2020 11:20, m_scot_alex wrote:
Bill -Hi Mike, WSJT-X v2.3.0 RC1 uses Qt v5.15.0 for MinGW-w64. The 32-bit build uses Qt v5.12.9 for MinGW. 73 Bill G4WJS. |
|
Locked
Re: error message on loading WSJT-X
m_scot_alex
Bill -
What Qt versions are you using? I could probably dig through the repo but if you know off the top of your head that would be great. I'm not aware of a Win7 SP1 dependency but will check with my staff later today. https://doc.qt.io/qt-5/supported-platforms.html 73, Mike - N8MSA |
|
Locked
Re: Movin' on up
Reino Talarmo
Hi Marcus, You may have at some stage defined those additional frequencies yourself or got those from an older wjts-x version as in the latest version v2.3.0-rc1 those are not / no more defined for FT8. After Reset only 7.074 and 14.074 are there. 73 Reino OH3mA
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of HB9BRJ
The default frequency list contains 2 FT8 frequencies on 40m and 20m: 7.071 and 7.074 on 40m, 14.071 and 14.074 on 20m. Several times I called CQ on an "alternate" channel but no response. In an ideal world, one would expect that users who cannot get through the QRM on the main channel would QSY to the alternate channel. |
|
Locked
Nevada QSO Party use of FT8/4
The Nevada QSO party will be using FT8 and FT4. They will be operating about 4 kHz up from the regular frequencies and will be using the Field Day overlay. The out of state exchange will be '1A SECTION' and the instate will be a 'coded number/letter NV' The coded number will represent the county or countyline operations in Nevada. You will have to use the Field Day overlay in order to complete a contact with a Nevada station. For those using N1MM+ logger to work the contest, you will have to exit N1MM and then start WSJT-X and use the logger in WSJT-X to record your contacts and you will end up having to send in 2 logs for your entry. Complete rules, FAQs, and a special section on the FT8/4 operation is available on the website, http://nvqso.com/
Come join us and have some FUN! Jim W6US |
|
Locked
Re: Movin' on up
Jeff Stillinger
They actually did document it in 2017. I am sorting through the documents now to find the exact one. I have stuff going all the say back prior to version 1.4, so it's a long search manually. It's there, because we used the document extensively in 2017. Give me time, I will fine it in the archives.
toggle quoted message
Show quoted text
On 10/8/20 1:03 PM, Reino Talarmo wrote:
Hi Jeff and all, |
|
Locked
Re: Movin' on up
HB9BRJ
The default frequency list contains 2 FT8 frequencies on 40m and 20m: 7.071 and 7.074 on 40m, 14.071 and 14.074 on 20m. Several times I called CQ on an "alternate" channel but no response. In an ideal world, one would expect that users who cannot get through the QRM on the main channel would QSY to the alternate channel.
Running low power and having only a vertical antenna, I realized many months ago that my QSO rate is significantly higher in FT4 than in FT8, despite the few dB difference in sensitivity. 73, Markus HB9BRJ |
|
Locked
Re: Request- Change FST4W default T/R setting
Alan G4ZFQ
Are there agreed-upon frequencies for FST4 modes on 80m?Jon, a group including a USA station are using 3.568800, see the Chat. 73 Alan G4ZFQ |
|
Locked
Re: error message on loading WSJT-X
JTAlert Support (VK3AMA)
On 9/10/2020 1:32 am, Bill Somerville
wrote:
The Qt versions we use both support Windows 7 or newer, 32- and 64-bit versions of WSJT-X should work the same Bill, Is that Win 7 or Win 7 + SP1? Perhaps the OP is running non SP1 and QT needs SP1 as a minimum. This is only speculation on my part, I don't know if QT has that limitation. de Laurie VK3AMA |
|
Locked
Re: Movin' on up
Reino Talarmo
Hi Jeff and all,
toggle quoted message
Show quoted text
The specification does not call any separation at all. The trick is a careful decoded signals reconstruction, QSB estimation and subtraction of decoded signals. Then a new decoding of the remaining signals is possible and quite often successful. Using slit i.e .not calling on the frequency of a CQing station is usually a better as on that frequency there may be too many stations overlapping. 73, Reino OH3mA -----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Jeff Stillinger Sent: 8. lokakuuta 2020 20:32 To: main@WSJTX.groups.io Subject: Re: [WSJTX] Movin' on up Overlapping signals are prefect fine. Specification calls for 1 Hz separation, but in reality, 6 Hz works. So... for example: I am on 1000 Hz having a contact for breakfast. You can be on 1006 Hz or 994 Hz having your breakfast. The decoder will keep our breakfast orders correct. Point being you do not need a "clear spot" on the water fall. Only the correct separation between signals. I know, it's a major mind melt to see over lapping signals and to see them working just fine. It takes some getting use to. On 10/8/20 11:11 AM, Kermit Lehman via groups.io wrote: FT8 is extremely popular and the covid-19 pandemic has doubled down on |
|
Locked
Re: Movin' on up
Jeff Stillinger
Overlapping signals are prefect fine. Specification calls for 1 Hz separation, but in reality, 6 Hz works.
toggle quoted message
Show quoted text
So... for example: I am on 1000 Hz having a contact for breakfast. You can be on 1006 Hz or 994 Hz having your breakfast. The decoder will keep our breakfast orders correct. Point being you do not need a "clear spot" on the water fall. Only the correct separation between signals. I know, it's a major mind melt to see over lapping signals and to see them working just fine. It takes some getting use to. On 10/8/20 11:11 AM, Kermit Lehman via groups.io wrote:
FT8 is extremely popular and the covid-19 pandemic has doubled down on FT8 activity. During their peak activity times 20m and 40m are so congested that QSOs become difficult. How about trying moving the dial frequency up a small amount, 500 or 1000 Hz? This would open up some new territory without sacrificing too much of the view of the standard band. |
|
Locked
Re: Linx 1010 Windows tablet 32 bit
#IssueReport
On 08/10/2020 10:19, Dr Neil A Mallett via groups.io wrote:
Trying 2.3.0 as it has control for my FT-817 that works without any problem.Hi Neil, the splash screen check box is blocked by the warning message about the release candidate expiry date. You should be able clear the hidden message box with ENTER or ESC then check the option to switch off the splash screen. Have you set up the audio devices in "Settings->Audio"? WSJT-X v2.3.0 no longer defaults to the default audio devices if none are set up. 73 Bill G4WJS. |
|
Locked
Linx 1010 Windows tablet 32 bit
#IssueReport
Dr Neil A Mallett
Trying 2.3.0 as it has control for my FT-817 that works without any problem.
Noticed that the waterfall doesn't fall..stays blank The pop up screen at the start cannot be stopped popping up at load time I'm not seeing any rx levels on the LH pane when using WSPR mode so not sure if anything is I guess these may be only happening to me as its not the most powerful of tablets but would be good for trips out of the home QTH 73's Neil G1ABR |
|
Locked
Movin' on up
Kermit Lehman
FT8 is extremely popular and the covid-19 pandemic has doubled down on FT8 activity. During their peak activity times 20m and 40m are so congested that QSOs become difficult. How about trying moving the dial frequency up a small amount, 500 or 1000 Hz? This would open up some new territory without sacrificing too much of the view of the standard band.
73,
Ken, AB1J
|
|
Locked
Re: error message on loading WSJT-X
On 08/10/2020 15:25, ny2ny wrote:
Hi Bill - says file not found ...still strange that error message only appears when I download the 64 bit version of WSJT, no message on 32 bit version ?Hi Jay, looks like it may be a Qt Framework error. The 64-bit version of WSJT-X uses a newer version of the Qt framework we use for cross platform facilities and portability. The Qt versions we use both support Windows 7 or newer, 32- and 64-bit versions of WSJT-X should work the same. All I can suggest is trying again with the 64-bit version for the next WSJT-X v2.3.0 release when it becomes available. 73 Bill G4WJS. |
|