Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 X-Spam-DCC: EATSERVER: mailn 1166; Body=2 Fuz1=2 Fuz2=2 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mailn.lipkowski.org (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id uB2LYxde020654 for ; Fri, 2 Dec 2016 22:35:00 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1cCvR0-0004l4-Mv for rs_out_1@blacksheep.org; Fri, 02 Dec 2016 21:31:58 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1cCvR0-0004kv-9l for rsgb_lf_group@blacksheep.org; Fri, 02 Dec 2016 21:31:58 +0000 Received: from smtp-out01.xworks.net ([31.25.48.13]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1cCvQw-000679-Tt for rsgb_lf_group@blacksheep.org; Fri, 02 Dec 2016 21:31:57 +0000 Received: from mailbackend2 (cluster06.xworks.net [10.100.1.80]) by smtp-out01.xworks.net (Postfix) with ESMTP id 769556120A; Fri, 2 Dec 2016 22:31:53 +0100 (CET) X-DKIM-Result: Domain=kabelmail.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kabelmail.de; s=mail; t=1480714313; bh=wmSzZfrXKfGPNehD07Ohw4k7UvyOCPA0tgXsfuCGvws=; h=Subject:To:References:From:Date:MIME-Version:In-Reply-To: Content-Type; b=ueeRfKk4kvlEp+fatGKOECymEAVqEnhzzdYCv7j53jzR7yeeAasbXLYV4ekdAl9za 0TpfaR0RvbPm+J64D8CC+VhQ4gA4lrqjtx1ovIzJ3eNE3sg+4YxYaGF6st2PnHn+pW QfhZqCdsgunatRmRjNEuXMAFemOp0vyON1YgGyG8= Received: from [192.168.178.33] (ipbcc15037.dynamic.kabel-deutschland.de [188.193.80.55]) (authenticated bits=0) by smtpa.mediabeam.com with ESMTP id uB2LVo0Q027700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2016 22:31:51 +0100 X-mediaBEAM-Originating-IP: [188.193.80.55] X-mediaBEAM-AUTHID: [DK1IS@kabelmail.de] To: rsgb_lf_group@yahoogroups.co.uk, rsgb_lf_group@blacksheep.org References: <1B6E0A56-9CD8-4821-8C11-52C3C3980207@gmail.com> <93ae7fe3-cbfd-7cff-bfc7-2eac0fe3dc3f@usa.net> <7512eb1c-08fa-df06-0352-2cd9e2c7246e@usa.net> <8F8EA0CDE74C412290C5D52D56A788A8@Clemens0811> From: DK1IS Message-ID: <9b8ce39c-8043-69a1-f5cd-b5070a6451b1@kabelmail.de> Date: Fri, 2 Dec 2016 22:33:16 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: X-mediaBEAM-AuthCheck: route13 X-mediaBEAM-AuthScore: 1.6/5.0, scanned in 1.164sec X-Scan-Signature: c8ff00257edaad8e124ab9389da9609a Subject: LF: Argo Extensions? Content-Type: multipart/alternative; boundary="------------D5D2A072345119C129A33657" 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 X-Scanned-By: MIMEDefang 2.75 Status: O X-Status: X-Keywords: X-UID: 9651 This is a multi-part message in MIME format. --------------D5D2A072345119C129A33657 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtpa.mediabeam.com id uB2LVo0Q027700 Dear Alberto, lots of QRSS operators are successfully using your fine Argo software -=20 so do I. It has been essential for making the LF and MF band accessible=20 to amateur radio. So, first of all, thank you so much for this great=20 piece of work! At Nov 6, 2016 you wrote to Clemens, DL4RAJ: "I have in my future plans, after I will have finished a couple of projects that are absorbing all of my time at present, to do an=20 overhaul of Argo, maybe changing some of its architecture, which dates back to 20=20 years ago..." So I think it could be a good moment to ask for possible future=20 extensions of Argo=B4s features. Could it be practicable to add something= =20 like a "notch-function" to the horizontal waterfall display, at its best=20 with an adjustable bandwidth? It should work in front of the ALC=20 function to avoid reduced sensitivity due to strong unwanted signals and=20 should be effective in the non-ALC-modes too. For example: the MF QRSS=20 beacon IQ2MI on 476,180 kHz usually booms in here every evening making=20 it difficult to look at weaker signals within spittig distance to this=20 frequency. In such situations a visual notch would be great! Having an=20 extremly sharp AF notch my Perseus RX does this job rather well (indeed=20 not on its own screen but on the VAC linked Argo screen!) but with many=20 other receivers it isn=B4t possible due to their notches being much to=20 wide for use at real narrow bandwidths. Another nice gimmick would be to have an alarm function if a signal=20 appears in a given range of frequencies on the running waterfall -=20 perhaps something like an inversion of the notch function. Most of the=20 usual squelch circuits of the upstream receivers would not do this job=20 at weak signals without blanking the whole screen. Sorry - it=B4s not difficult to create ideas but I can=B4t measure effort= =20 nor feasibility for their realization. But perhaps something is possible = .... Thanks for your ever-lasting inspiration, gl es vy 73 de Tom, DK1IS www.qrz.com/db/dk1is --------------D5D2A072345119C129A33657 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtpa.mediabeam.com id uB2LVo0Q027700
Dear Alberto,

lots of QRSS operators are successfully using your fine Argo software - so do I. It has been essential for making the LF and MF band accessible to amateur radio. So, first of all, thank you so much for this great piece of work! At Nov 6, 2016 you wrote to Clemens, DL4RAJ:

"I have in my future plan= s, after I will have finished a couple
of projects that are absorbing all of my time at present, to do an overhaul of
Argo, maybe changing some of its architecture, which dates back to 20 years ago..."

So I think it could be a good moment to ask for possible future extensions of Argo=B4s features. Could it be practicable to add something like a "notch-function" to the horizontal waterfall display, at its best with an adjustable bandwidth? It should work in front of the ALC function to avoid reduced sensitivity due to strong unwanted signals and should be effective in the non-ALC-modes too. For example: the MF QRSS beacon IQ2MI on 476,180 kHz usually booms in here every evening making it difficult to look at weaker signals within spittig distance to this frequency. In such situations a visual notch would be great! Having an extremly sharp AF notch my Perseus RX does this job rather well (indeed not on its own screen but on the VAC linked Argo screen!) but with many other receivers it isn=B4t possible due to their notches being much to wide for use at real narrow bandwidths.

Another nice gimmick would be to have an alarm function if a signal appears in a given range of frequencies on the running waterfall - perhaps something like an inversion of the notch function. Most of the usual squelch circuits of the upstream receivers would not do this job at weak signals without blanking the whole screen.

Sorry - it=B4s not difficult to create ideas but I can=B4t measure effort nor feasibility for their realization. But perhaps something is possible ...

Thanks for your ever-lasting inspiration,

gl es vy 73 de

Tom, DK1IS
www.qrz.com/db/dk1is

--------------D5D2A072345119C129A33657--