|
Today I came across an issue I haven't had with past releases. I use the "Tune" function, when changing bands, to tune the LDG antenna tuner with my TS-590s. Today when I hit the tune, the radio keyed up, the antenna tuner tuned as it always has. When i clicked on the "Tune" tab to unkey, the radio unkeyed and then keyed up right away. click the tune tab again and the radio stayed keyed up again. When the radio did unkey, the next time I try to send CQ, no output. Reboot the program cleared the problem. Thought I would pass this along to the team. I didn't know where else to post this. Sorry. Marv N0FJP 73 
|
|
|
I have attached the wsjtx_syslog.log for review and help. The middle of February I had an IT type look at my PC and try to find out why my hard drive was full. He found what he called "audio files" and I paid no attention to what or where they were. I had 130 gigs of files on a terabyte hard drive and the rest was full of these "audio files". Now I see these that I have sent. I'm no techie or even close but I believe it's a problem. I also believe it impacts my logging problem which is the amateur contact log from N3FJP by causing my call (WR4FT) to be spotted in the DX spotting section of the software. One issue at a time: what to do with the "syslog.log"?
|
|
|
C:\Users\username\AppData\Local\WSJT-X\wsjtx_log.adi This file will open with text editor. John, WØZI
toggle quoted message
Show quoted text
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Neil Foster Sent: Sunday, March 21, 2021 1:47 PM To: main@WSJTX.groups.io Subject: [WSJTX] Question #FT8 OK, not being a PC wizard I have a question. Yesterday 20 March I worked A25RU on 20m FT8. Before I could log the contact I had a PC glitch. As I understand it is possible to look in WSJT and find the contact in a past log. How can this be done?
Many thanks
73 and stay well
Neil N4FN
|
|
|
toggle quoted message
Show quoted text
From: PE0FK FrankSent: 20 March 2021 19:40 To: WSJTX@groups.ioSubject: [WSJTX] #AudioIssues Dear Group, I have an issue with selecting the required audio device. I have an Kenwood TS990 and an Icom IC-9100 connected by USB to my computer. (Running the latest update of Windows 10) In the sound settings I am able to select all the devices and if necessary set them as default. The audio works. However, in the settings of WSJTX 2.3.0 I can only see and select the device which set as windows default. The other devices don’t show up in the list. Does anyone know how to solve this issue? Thanks in advance. Kind regards and 73, PE0FK (Frank)
|
|
|
Neil Foster
OK, not being a PC wizard I have a question. Yesterday 20 March I worked A25RU on 20m FT8. Before I could log the contact I had a PC glitch. As I understand it is possible to look in WSJT and find the contact in a past log. How can this be done?
Many thanks
73 and stay well
Neil N4FN
|
|
|
Hello all,
I have been running Raspbian 10 on a Raspberry Pi 4 for months without issue. This morning, I discovered that the TX audio in WSJT-X has stopped working. Previously, I had it configured via ALSA to use my Yaesu FT-991A’s audio input and output directly without dealing with PulseAudio (at least not on the surface). RX audio still works perfectly fine, and audio in Fldigi works like it always has using PulseAudio directly, which adds to the confusion here. Additionally, sometimes when exiting, “wsjtx” executable hangs on a futex() call (described below).
In order to troubleshoot this sudden issue when I had changed literally nothing about my setup, I have taken the following steps: - Changed the audio card to “pulse” for input and output
- Run “wsjtx” from the command line in hopes that it would dump something to stdout that would show me what was happening
- Shut down WSJT-X, backed up and deleted the ~/.config/WSJT-X.ini and ~/.share/local/WSJT-X files/directories, then started and reconfigured WSJT-X
- Shut down WSJT-X and removed the above files/directories again, then ran an “sudo apt purge wsjtx && sudo apt autoremove”, then reinstalled 2.4.0-rc3 from the armhf deb file
- Run it via strace to see what it was doing (even though that generates a LOT of output), but this was more to see why it was hanging, which is how I discovered that it was hanging on futex(0x1a66be10, FUTEX_WAIT_PRIVATE, 0, NULL)
- Repeated the process in step 4, except installing the latest stable version of WSJT-X (2.3.0) instead
Even after all of that, TX audio still does not work. One thing I have noticed in all of this is that despite how the output sound device is configured, it does not send anything on the output. It will key the PTT just fine (and my rig is set up correctly to use DATA-USB as the output, taking its sound from what comes in via the USB connection - as I said, it works fine on Fldigi), but it does not even show up under Playback Streams or on pavucontrol’s Playback tab at all. RX audio does use a recording stream, which does show up under Recording Streams and also on pavucontrol’s Recording tab (and continues to after I close the WSJT-X window until I manually kill the “wsjtx” process due to that futex() issue I described above).
Additionally, it also appears that JS8Call is affected by this issue. I know that they’re different pieces of software used for different purposes, but there is a bunch of shared code between them (or at least there used to be), so my guess is that it has something to do with the Qt Multimedia libraries or something of that nature that both use.
I searched online for similar issues, but I didn’t see much of anything that amounted to a resolution. Is there a fix for this short of me having to reinstall Raspbian?
Mike K8WU
|
|
|
Jim Shorney
My typical response in a situation like that is to tell them "it's broken". That's the only correct answer when not enough information is given. :D 73 -Jim NU0C On Sun, 21 Mar 2021 14:08:17 -0400 "Jim Nuytens via groups.io" <jim.kj3n@...> wrote: Neil,
There are days were I don’t know how you folks keep your sanity in this group.
On Mar 21, 2021, at 1:10 AM, neil_zampella <neilz@...> wrote:
Really?? That's like saying my computer stopped without giving any other information.
Giving what version of WSJT-X you're using, what operating system, what rig you're running, how its connected to the computer, and so on would be of more use.
Neil, KN3ILZ
On 3/20/2021 7:07 PM, melvin.ruble via groups.io wrote:
FT8 stopped opening, please help
|
|
|
neil_zampella <neilz@...>
LOL ...
On 3/21/2021 1:08 PM, Jim Nuytens via
groups.io wrote:
toggle quoted message
Show quoted text
Neil,
There are days were I don’t know how you folks keep your
sanity in this group.
On Mar 21, 2021, at 1:10 AM,
neil_zampella <neilz@...> wrote:
Really?? That's like saying my computer stopped without
giving any other information.
Giving what version of WSJT-X you're using, what operating
system, what rig you're running, how its connected to the
computer, and so on would be of more use.
Neil, KN3ILZ
On 3/20/2021 7:07 PM,
melvin.ruble via groups.io wrote:
FT8 stopped opening, please help
|
|
|
One QSO made on 28.135 MHz today... K4RCG and N4ST about 1600z. Request a few CQs/minutes monitoring this freq/mode if your time permits. Tnx in advance.
73
Bob K4RCG
|
|
|
Neil,
There are days were I don’t know how you folks keep your sanity in this group.
toggle quoted message
Show quoted text
On Mar 21, 2021, at 1:10 AM, neil_zampella <neilz@...> wrote:
Really?? That's like saying my computer stopped without giving
any other information.
Giving what version of WSJT-X you're using, what operating system,
what rig you're running, how its connected to the computer, and so
on would be of more use.
Neil, KN3ILZ
On 3/20/2021 7:07 PM, melvin.ruble via
groups.io wrote:
FT8 stopped opening, please help
|
|
|
Tnx Mike!! Interest in 10m Q65 growing. Just made my first QSO! Will try to coordinate a better time/propagation window for DX. Several EU stations were QRV today; I heard three via remote SDR in Scotland.
73 Bob K4RC
toggle quoted message
Show quoted text
On Sun, Mar 21, 2021 at 3:38 PM Mike Phipps < qrz@...> wrote: I am going to monitor 28.135 MHz so I can spot anyone that I hear to PSK Reporter. I unfortunately will not be able to participate; Qt decided to make both WSJT-X and JS8Call randomly fail when trying to open a playback stream for TX, whether it’s set to use PulseAudio or a specific card does not matter. I am trying to work through that.
Mike K8WU On Mar 21, 2021, at 11:31 AM, M0PWX < M0PWX@...> wrote:
This Is me decoding my own signal via the 991a,no HF antenna in it, but enough to receive it O this should register in psk reporter Peter M0PWX Sent from Mail for Windows 10 On Sun, Mar 21, 2021 at 2:54 PM M0PWX < M0PWX@...> wrote: Qsy’ed to 28.135 Q65 30a Peter M0PWX Sent from Mail for Windows 10 I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing. Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz?? On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV < lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275 MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally, too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
21 March 1558z QSO N4ST/K4RCG 28.135 MHz Q65/30A :-)
TU Jim!
73 de Bob K4RCG
toggle quoted message
Show quoted text
On Sun, Mar 21, 2021 at 3:32 PM M0PWX < M0PWX@...> wrote:
This Is me decoding my own signal via the 991a,no HF antenna in it, but enough to receive it
O this should register in psk reporter
Peter
M0PWX
Sent from
Mail for Windows 10
On Sun, Mar 21, 2021 at 2:54 PM M0PWX <M0PWX@...> wrote:
Qsy’ed to 28.135 Q65 30a
Peter
M0PWX
Sent from
Mail for Windows 10
I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing.
Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz??
On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV <lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275
MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band
starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally,
too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
Yes, that is the way it works.
Larry W0OGH
On 3/20/2021 8:31 PM, Larry Weaver
wrote:
toggle quoted message
Show quoted text
I was trying to work A25RU on 80 meters FT8 this evening in F/H
mode. I had my transmit freq set to about 2550 HZ. When A25RU
called me my transmit freq would jump to his freq to respond. Is
this normal? I thought the TX freq would stay locked. I was in
"Hound " mode when this happened, twice. Other times I had used
F/H mode in the past few days I never noticed this happen. Any
comments or pointers would be appreciated.
Thanks,
Larry
|
|
|
I am going to monitor 28.135 MHz so I can spot anyone that I hear to PSK Reporter. I unfortunately will not be able to participate; Qt decided to make both WSJT-X and JS8Call randomly fail when trying to open a playback stream for TX, whether it’s set to use PulseAudio or a specific card does not matter. I am trying to work through that.
Mike K8WU
toggle quoted message
Show quoted text
On Mar 21, 2021, at 11:31 AM, M0PWX < M0PWX@...> wrote:
This Is me decoding my own signal via the 991a,no HF antenna in it, but enough to receive it O this should register in psk reporter Peter M0PWX Sent from Mail for Windows 10 On Sun, Mar 21, 2021 at 2:54 PM M0PWX < M0PWX@...> wrote: Qsy’ed to 28.135 Q65 30a Peter M0PWX Sent from Mail for Windows 10 I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing. Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz?? On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV < lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275 MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally, too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
Dear Group,
For people who have the same issue, I disabled the: 'Unimodem Half-Duplex Audio Device' in the Device Manager (it belongs to an old analog modem still installed in my PC)
This solved the problem.
Kind regards and 73,
PE0FK (Frank)
|
|
|
This Is me decoding my own signal via the 991a,no HF antenna in it, but enough to receive it
O this should register in psk reporter
Peter
M0PWX
Sent from
Mail for Windows 10
toggle quoted message
Show quoted text
On Sun, Mar 21, 2021 at 2:54 PM M0PWX < M0PWX@...> wrote:
Qsy’ed to 28.135 Q65 30a
Peter
M0PWX
Sent from
Mail for Windows 10
I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing.
Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz??
On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV <lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275
MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band
starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally,
too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
toggle quoted message
Show quoted text
On Sun, Mar 21, 2021 at 2:54 PM M0PWX < M0PWX@...> wrote:
Qsy’ed to 28.135 Q65 30a
Peter
M0PWX
Sent from
Mail for Windows 10
I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing.
Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz??
On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV <lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275
MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band
starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally,
too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
Several W/DX stations (W, VE7, GM, TA, M, DK) are QRV today testing Q65/30A on 10m. QRG is 28.135 MHz. I've heard 3 EU stations via remote SDR in Scotland but only a few "pings" on the waterfall here. If propagation improves, this mode should be a lot of fun on 10m as well as VHF/UHF.
73 de Bob
K4RCG
|
|
|
Qsy’ed to 28.135 Q65 30a
Peter
M0PWX
Sent from
Mail for Windows 10
I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing.
toggle quoted message
Show quoted text
On Sun, Mar 21, 2021 at 2:13 PM Bob via
groups.io <bobstohlman= gmail.com@groups.io> wrote:
Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz??
On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV <lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275
MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band
starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally,
too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
I passed the QSY request to stations in VE, GM, DK, G. We will QSY 28.135 MHz for Q65/30A for testing.
73 de Bob K4RCG
toggle quoted message
Show quoted text
Good catch Joe.... 28.275 is a beacon freq. Maybe 28.135 MHz??
73 Bob K4RCG
On Sun, Mar 21, 2021 at 2:01 PM Joe Subich, W4TV < lists@...> wrote:
> Perhaps 28.175 MHz would be a better choice. I have never heard any
> signals in much of the 28.1xx MHz range, and the closest thing I can
> think of there would be the QRGs for WSPR (28.1246 MHz) and FT4
> (28.180 MHz).
Beacon List here: <https://www.qsl.net/wj5o/bcn.htm>
The FT4 segment is questionable. I would recommend staying *below*
28.160 and look for something below 28.145 ... perhaps between 28.130
and 28.140.
73,
... Joe, W4TV
On 2021-03-21 9:30 AM, Mike Phipps wrote:
> I was just thinking about Q65 on HF yesterday after actually doing a JT65 QSO on 20m (answering someone that I heard calling and I was able to get WSJT-X up and running in time to copy his CQ). However, I think you might want to change your QRG for it. 28.275 MHz is toward the top of the beacon subband in ITU Region 2. There may be a beacon operating there that isn’t listed anywhere, and you may have never heard it, but it’s there and I don’t think they’d appreciate the QRM. Additionally, I think the phone band starts right around there (or even lower) in R1 and/or R3, for what it’s worth.
>
> Perhaps 28.175 MHz would be a better choice. I have never heard any signals in much of the 28.1xx MHz range, and the closest thing I can think of there would be the QRGs for WSPR (28.1246 MHz) and FT4 (28.180 MHz). I think that will work internationally, too, but maybe someone from the other ITU Regions can comment on that. Additionally, if anyone runs any CW or digital nets near there, we might want to adjust accordingly.
>
> Once the question of operating frequency is resolved, I’d love to participate in a Q65 “trial” on 10m, personally.
>
>
> Mike K8WU
>
>> On Mar 21, 2021, at 8:34 AM, Gary - AG0N <wb0kkm@...> wrote:
>>
>> My amp is at hospital, but when I get back to town next week, I’d entertain that idea and be glad to give it a go barefoot.
>>
>> Gary - AG0N - DN81fv
>>
>>> On Mar 21, 2021, at 06:05, Bob <bobstohlman@...> wrote:
>>>
>>> Several of my DX friends have been discussing giving 10m Q65 a go. I "think" we will try 28.275MHz to ensure compliance with applicable regs and to avoid QRM to beacons. Anyone else considering 10m Q65?
>>
>>
|
|
|
