Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25;
Message-ID: <531CF785.8020204@gmx.net>
Date: Mon, 10 Mar 2014 00:21:41 +0100
From: Tobias DG3LV <DG3LV@gmx.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <006b01cf3969$43a83480$caf89d80$@de> <5318C740.50901@mvnet.de> <5318D051.2080907@freenet.de> <5318DA98.7090606@broadpark.no> <5318E10B.3080701@freenet.de> <5318F763.6010607@broadpark.no> <53190028.9070900@freenet.de> <1981194039.20140309191717@mterrier.net> <531CCCC4.9060001@freenet.de> <531CE824.9080709@gmx.net> <531CED4B.3040604@freenet.de>
In-Reply-To: <531CED4B.3040604@freenet.de>
Subject: Re: LF: WSQ2 new version uploaded
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

Hi Wolf!

>> One may assume that, when closing the port all outputs switch back to
>> the default state
Yes, it does. The statuslines DTR RTS are reset (= cleared) when the 
port is closed. Just tested on onboard COM1: and my Prolific USB-adapter 
using several programs. (Windows does some toggling of statuslines at 
startup to find a serial mouse, but resets them to standard thereafter).

73 de dg3lv Tobias

Am 09.03.2014 23:38, schrieb wolf_dl4yhf:
> Hi Tobias,
>
> Ok, thanks for testing. Compared to some other modifications, the serial
> port issue should be easy to fix.
>
>
> You wrote:
>>
>> suggestion :
>> K1JT's programs do open the serial port just at the start of each
>> transmit sequence and close the serial port immediately after the end
>> of this transmission. By this feature more than one program can run at
>> a time using the same serial port for PTT, as long as only one program
>> wants to transmit at any time. i.e. you can run WSPR-x and WSJT-x
>> simultaneously without the need to deactivate the (same) serial port
>> of the program that is on receive only. It would be nice if WSQ would
>> behave similar.
>>
> Ok, makes sense.. and lines up with Michel's reply which just arrived
> here ... but will the port's RTS and DTR output remain safely in the
> 'receive' state when WSQ closes the serial port after each transmit-over ?
> One may assume that, when closing the port all outputs switch back to
> the default state - or leave them as-is, until another call of the
> 'EscapeCommFunction'.
>
> Further experimentation will show...
>
> 73 and good night,
>    Wolf .
>
>
>
>
>
>