Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x28AX8EX020265 for ; Fri, 8 Mar 2019 11:33:15 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1h2CgN-0003D4-QP for rs_out_1@blacksheep.org; Fri, 08 Mar 2019 10:24:51 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1h2CgB-0003Cv-9E for rsgb_lf_group@blacksheep.org; Fri, 08 Mar 2019 10:24:39 +0000 Received: from rhcavuit04.kulnet.kuleuven.be ([2a02:2c40:0:c0::25:137]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h2Cg8-0002p4-BI for rsgb_lf_group@blacksheep.org; Fri, 08 Mar 2019 10:24:38 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: CE414120014.A4A98 X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-2.cc.kuleuven.be (icts-p-smtps-2e.kulnet.kuleuven.be [134.58.240.34]) by rhcavuit04.kulnet.kuleuven.be (Postfix) with ESMTP id CE414120014 for ; Fri, 8 Mar 2019 11:24:33 +0100 (CET) Received: from ICTS-S-EXMBX23.luna.kuleuven.be (icts-s-exmbx23.luna.kuleuven.be [10.112.11.58]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by icts-p-smtps-2.cc.kuleuven.be (Postfix) with ESMTPS id BF14420006; Fri, 8 Mar 2019 11:24:33 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX23.luna.kuleuven.be (10.112.11.58) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 8 Mar 2019 11:24:31 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a]) by ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a%25]) with mapi id 15.00.1395.000; Fri, 8 Mar 2019 11:24:31 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" , "rsgb-lf-group@groups.io" , "600MRG@mailman.qth.net" <600MRG@mailman.qth.net> Thread-Topic: [rsgb-lf-group] LF: Audio alert for JT-9 activity? Thread-Index: AQHU1QpyMDZvZOdvhEC02E5JTAd0naYAYW2AgAEhM2w= Date: Fri, 8 Mar 2019 10:24:31 +0000 Message-ID: <1552040669728.46881@kuleuven.be> References: <1924848029.20190307171930@gmail.com>, In-Reply-To: Accept-Language: nl-BE, en-GB, en-US Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.112.50.1] MIME-Version: 1.0 X-Spam-Score: -2.3 (--) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello Chris, Andy, all, Regarding SlowJT9: adding a simple alert via a serial port pin going high is easy. Via that pin you can drive whatever you want (a simple buzzer or a more sophisticated "alarm"). Content analysis details: (-2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [2a02:2c40:0:c0:0:0:25:137 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_FONT_LOW_CONTRAST BODY: HTML font color similar or identical to background 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 58067cca381a9a29d283a47426ceb5b1 Subject: Re: [rsgb-lf-group] LF: Audio alert for JT-9 activity? Content-Type: multipart/alternative; boundary="_000_155204066972846881kuleuvenbe_" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_30_40,HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false --_000_155204066972846881kuleuvenbe_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Chris, Andy, all, Regarding SlowJT9: adding a simple alert via a serial port pin going high i= s easy. Via that pin you can drive whatever you want (a simple buzzer or a = more sophisticated "alarm"). Other options such as UDP messages, an e-mail or message to a smartphone to= be sent are also possible but will be more labor intensive to implement. But the first question is: what events should trigger the alarm? There can be various criteria: - DX station (DX =3D based on distance or on other continent?) - New DXXX entity - New station (never worked before) - A specific callsign (useful on sked) - ... Evaluating the incoming messages might become more complicated that impleme= nting the alert itself ... So my questions to all of you: - To whom would alert option in SlowJT9 be useful? - Based on what criteria should it be possible to trigger an alert? - What way the alert should be send? 73, Rik ON7YD - OR7T ________________________________ Van: rsgb-lf-group@groups.io namens Andy G4JNT Verzonden: donderdag 7 maart 2019 18:49 Aan: rsgb_lf_group@blacksheep.org; rsgb-lf-group@groups.io Onderwerp: Re: [rsgb-lf-group] LF: Audio alert for JT-9 activity? The trouble with that is that the sound card output is used for audio drive= to the transmitter, so unless you play your Tx audio also through the spea= kers or use different sound cards, you'll run into complications. One way, without actually doing anything to the WSJT-X software would be t= o intercept the UDP messages broadcast by WSJT-X and, using a another prog = running on teh sam emachine, read these messages and parse them for a JT9 d= ecode. Then do whatever you need to do for an audio alert. Sound card is= sues are the same, but a piezo bleeper on a spare COM port would do the tri= ck. JT9-SLow software doesn't broadcast UDP messages, but that's more am= enable to the author implementing the facility - perhaps ? Andy www.g4jnt.com On Thu, 7 Mar 2019 at 17:23, Chris Wilson > wrote: Hi all, I just sent this message to the WSJT-X forum, would anyone support this request? If so please respond there. If Slow JT-9 could add this I would find it a very useful addition :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I work mainly on LF 136kHz and although even trans Atlantic QSO's occur from here in the UK activity is very limited and spasmodic. When I check for activity I have often missed the chance to respond. A selectable audio alert of activity would be a Godsend, would there be any interest in supporting such an addition? Thanks 2E0ILY ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~, -- Best regards, Chris mailto:dead.fets@gmail.com _._,_._,_ ________________________________ Groups.io Links: You receive all messages sent to this group. View/Reply Online (#8618) |= Reply To Group | Reply= To Sender | Mu= te This Topic | New Topic Your Subscription | Cont= act Group Owner | Unsubscribe [rik.strobbe@kule= uven.be] _._,_._,_ --_000_155204066972846881kuleuvenbe_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello Chris, Andy, all,


Regarding SlowJT9: adding a simple alert via a serial port pin goin= g high is easy. Via that pin you can drive whatever you want (a s= imple buzzer or a more sophisticated "alarm").

Other options such as UDP messages, an e-mail or message to a smart= phone to be sent are also possible but will be more labor in= tensive to implement.


But the first question is: what events should trigger the alarm? 

There can be various criteria:

- DX station (DX =3D based on distance or on other continent?)

- New DXXX entity

- New station (never worked before)

- A specific callsign (useful on sked)

- ...

Evaluating the incoming messages might become more complicated that impl= ementing the alert itself ...


So my questions to all of you:

- To whom would alert option in SlowJT9 be useful?

- Based on what criteria should it be possible to trigger an alert?

- What way the alert should be send?


73, Rik  ON7YD - OR7T



Van: rsgb-lf-group@groups.i= o <rsgb-lf-group@groups.io> namens Andy G4JNT <andy.g4jnt@gmail.co= m>
Verzonden: donderdag 7 maart 2019 18:49
Aan: rsgb_lf_group@blacksheep.org; rsgb-lf-group@groups.io
Onderwerp: Re: [rsgb-lf-group] LF: Audio alert for JT-9 activity?
 
The trouble with that is that the sound card output is used for audio drive= to the transmitter, so unless you play your Tx audio also through the spea= kers or use different sound cards, you'll run into complications.

One way, without actually doing anything to the WSJT-X software  would= be to intercept the UDP messages broadcast by WSJT-X and, using a another = prog running on teh sam emachine, read these messages and parse them for a = JT9 decode.   Then do whatever you need to do for an audio alert.  Sound card issues are the same, but a piez= o bleeper on a spare COM port would do the trick.    JT9-SLow sof= tware doesn't broadcast UDP messages, but that's more amenable to the autho= r implementing the facility - perhaps ?



On Thu, 7 Mar 2019 at 17:23, Chris Wi= lson <dead.fets@gmail.com>= wrote:


Hi all,

I  just  sent  this  message to the WSJT-X forum, would= anyone support
this  request? If so please respond there. If Slow JT-9 could add this=
I would find it a very useful addition :)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I work mainly on LF 136kHz and although even trans Atlantic QSO's
occur from here in the UK activity is very limited and spasmodic. When
I check for activity I have often missed the chance to respond. A
selectable audio alert of activity would be a Godsend, would there be
any interest in supporting such an addition? Thanks 2E0ILY


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~,



--
Best regards,
 Chris                  &= nbsp;       mailto:dead.fets@gmail.com


_._,_._,_
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#8618) | Reply To Group | Reply To Sender | Mute This Topic | Ne= w Topic

Your Subscrip= tion | Contact Group Owner | Unsubscribe [rik.strobbe@kuleuven.be]

_._,_._,_
--_000_155204066972846881kuleuvenbe_--