Date
1 - 9 of 9
Locked Repeatedly Sending "Wanted Call" on 28.074 #txaudio #QSO_practices #AudioIssues
|
Someone has been repeatedly sending "Wanted Call" on voice (SSB) on 28.074 for the past couple of days. This message is generated by JTAlert and it is supposed to be sent to the computer's speakers, not to the transmitter. The operator has not configured their computer properly. Besides being extremely annoying, it is against the rules to transmit voice on this frequency.
My question for you folks is this; how can we track down this person and get in touch with them to let them know that they have misconfigured their system and must stop doing this? I cannot figure out how to interpret the waterfall to identify the responsible party. Thank you. -- 73, Edgar - K9RE |
|
|
|
Dave Garber <ve3wej@...>
i thought later versions of jtalert was disallowing same speaker ports. I
toggle quoted message
Show quoted text
would ask on hamapps/jtalert group... also would depend on how old a version they are using Dave Garber VE3WEJ / VE3IE On Sat, Nov 26, 2022 at 6:11 PM Edgar Reihl <ereihl@...> wrote:
Someone has been repeatedly sending "Wanted Call" on voice (SSB) on 28.074 |
|
|
|
Michael Black
That's going to be hard to track down. Triangulation being one possibility.
toggle quoted message
Show quoted text
JTAlert is supposed to block using the same sound card as WSJTX -- but I'm not sure when that was implemented so this operator might have an older version of JTAlert and probably also an older version of WSJT-X. If only the WAV file had a callsign in it.... Mike W9MDB On Saturday, November 26, 2022 at 05:11:06 PM CST, Edgar Reihl <ereihl@...> wrote:
Someone has been repeatedly sending "Wanted Call" on voice (SSB) on 28.074 for the past couple of days. This message is generated by JTAlert and it is supposed to be sent to the computer's speakers, not to the transmitter. The operator has not configured their computer properly. Besides being extremely annoying, it is against the rules to transmit voice on this frequency. My question for you folks is this; how can we track down this person and get in touch with them to let them know that they have misconfigured their system and must stop doing this? I cannot figure out how to interpret the waterfall to identify the responsible party. Thank you. -- 73, Edgar - K9RE |
|
|
|
Mike Chace-Ortiz
The TDoA direction finding service <https://www.rtl-sdr.com/kiwisdr-tdoa-direction-finding-now-freely-available-for-public-use/> on the kiwiSDR network should be able to show you where the signal originates.
toggle quoted message
Show quoted text
PM me and I’ll be happy to send you my guide to using this amazing service. 73 —mco AB1TZ On Nov 26, 2022, at 3:14 PM, Edgar Reihl <ereihl@...> wrote: |
|
|
|
JTAlert Support (VK3AMA)
On 27/11/2022 10:14 am, Dave Garber wrote:
i thought later versions of jtalert was disallowing same speaker ports. IJTAlert has always disabled audio output if WSJTX is using the same output device, but that was a one-off check at startup. and didn't take into account changes mid session. With the JTAlert 2.51.0 release (2022-Feb-15) the audio blocking was changed to a continuous check so that if any time during a JTAlert/WSJTX session a Windows re-enumeration of audio devices changed the WSJTX output device to be the same as JTAlert all sound output from JTAlert would be muted. From the JTAlert release notes... - Audio output disable: All sounds play will be disabled if the WSJTX/JTDX My guess is that the offending station is using an old JTAlert release. de Laurie VK3AMA (JTAlert author) |
|
|
|
Unfortunately it arrive to 30Mhz only. For as I know.
toggle quoted message
Show quoted text
73 Pietro I2OIM Il dom 27 nov 2022, 02:31 Mike Chace-Ortiz <mchaceortiz@...> ha scritto: The TDoA direction finding service < |
|
|
|
K7RA Tad Cook
So much great info in this thread. For several years I've heard the
"wanted call" voices on FT8 and did not know what the source was or even what the words were. Nice to know what it is. Also, the remote DF via KiwiSDR sounds very interesting. On Sat, Nov 26, 2022 at 5:31 PM Mike Chace-Ortiz <mchaceortiz@...> wrote: The TDoA direction finding service <-- *Listen for K7RA/B CW beacon on 28.2833 MHz.* *Tad Cook - K7RA* *Seattle, WA* *k7ra@... <k7ra@...>* |
|
|
|
Sorry, I lost the first part of the messages.
The same occurs on QO-100 satellite... (and obviously can't work on the downlink...) Pietro Il giorno dom 27 nov 2022 alle ore 08:20 Pietro Molina via groups.io <pietro@...> ha scritto: Unfortunately it arrive to 30Mhz only. For as I know. |
|
|
|
William Smith
Love to see how that works out in the real world, there's a lot of handwaving in the description (works best on low frequencies, ground wave, near the transmitter) and even then it's a degree or so of {lat,lon}gitude, which is 60-ish miles, so might work in sparsely populated areas with lots of KiwiSDR boxes (yes, a contradiction), hopefully the OP gets to ask Mike for his guide and can narrow it down, please report back!
toggle quoted message
Show quoted text
73, Willie N1JBJ On Nov 26, 2022, at 7:38 PM, Mike Chace-Ortiz <mchaceortiz@...> wrote: |
|
|