Date   

Re: FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Nuno Lopes - CT2IRY
 

 ++++ CT2IRY comments below.


73 Nuno
  CT2IRY



On Saturday, October 8, 2016 6:19 PM, "' Dave AA6YQ' aa6yq@... [dxlab]"



 
>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, October 08, 2016 2:51 AM
To: dxlab@...
Subject: Re: [dxlab] FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Many thanks to Salvatore, Nino and all the other volunteers! I think the same job should be done also for DxLab suite: many friends don't use it due to difficulties with English

>>>Having to translate the documentation changes in each new version of each DXLab application would greatly slow the rate of development. But all of the documentation files are accessible online, so "independent" translation efforts are certainly feasible. I'd be happy to enable any such groups to make their translated documentation accessible via the DXLab web site.

and because it's not possible (as far as I know) to easily manage awards like castles, abbeys, flora and fauna and so on.

>>>DXKeeper provides 8 user-defined fields that can be used to capture castle identifiers, abbey identifiers, flora and fauna identifiers, etc; filtered and sorted log report provides a basic view of award progress. If there's a significant group of users pursuing one or several of these awards, adding a dedicated item to each QSO and providing a progress report is literally only an hour or two of development effort - small enough that it can interrupt larger ongoing development efforts.
++++ Would it be feasible one drop down button to select the award: WAC, SOTA, WWFF, etc, and the second drop down with should present the List related to the first selector and also related to the Prefix of the Call, e.g.
Let's say the Call is CT2IRY/P, the first drop down the OP would select WAC,  one the second drop down (List) would present the WAC list related to the Call (DXCC).
WAC List < http://wcagroup.org/?page_id=207 >, SOTA List < summits >, WWFF  List < WWFF >
This are some of the most use awards, I think. :-)




73,

Dave, AA6YQ




Re: New poll for dxlab

Rex Turvin <turvin2009@...>
 

2


On Oct 8, 2016, at 10:58 AM, dxlab@... wrote:

 

Enter your vote today! A new poll has been created for the dxlab group:
Do you currently use "Green Heron Everywhere" or plan to acquire it within the next 3 month?
Created by: aa6yq
  1. yes
  2. no


Thanks!


New poll for dxlab

dxlab@...
 

Enter your vote today! A new poll has been created for the dxlab group:
Do you currently use "Green Heron Everywhere" or plan to acquire it within the next 3 month?
Created by: aa6yq
  1. yes
  2. no


Thanks!


using DXLab with the "Green Heron Everywhere"

Dave AA6YQ
 

As Dwight NS9I describes in

<http://www.dxlabsuite.com/dxlabwiki/GreenHeronEverywhere>

the extension of Commander 12.3.6 to optionally send N1MM-style "radio info" messages makes it possible to use DXLab with the
"Green Heron Everywhere" product, a sophisticated antenna rotator control system described here:

<http://www.greenheronengineering.com/GHE_Overview.php>

At present this must be accomplished by having DXView interoperate with the "N1MM Rotor" application, which in turn sends directives
to "Green Heron Everywhere". The need to run "N1MM Rotor" could be eliminated if DXView were extended to optionally send "rotator
control" messages in the same format used by "N1MM Rotor". I'd like to understand how many users would employ such an extension.

So if you're a current or prospective user of "Green Heron Everywhere", please visit the poll at

<https://groups.yahoo.com/neo/groups/dxlab/polls/poll/3225665>

Thanks!

73,

Dave, AA6YQ


An existing poll has been modified, check it out. All votes have been reset.

dxlab@...
 

Do you currently use "Green Heron Everywhere" or plan to acquire it within the next 3 months?
Created by: aa6yq


Thanks!


An existing poll has been modified, check it out. All votes have been reset.

dxlab@...
 

Do you currently use "Green Heron Everywhere" or plan to acquire it within the next 3 month?
Created by: aa6yq


Thanks!


An existing poll has been modified, check it out. All votes have been reset.

dxlab@...
 

Do you currently use "Green Heron Everywhere" or plan to acquire it within the next 3 month?
Created by: aa6yq


Thanks!


Re: FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Saturday, October 08, 2016 2:51 AM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Many thanks to Salvatore, Nino and all the other volunteers! I think the same job should be done also for DxLab suite: many friends don't use it due to difficulties with English

Having to translate the documentation changes in each new version of each DXLab application would greatly slow the rate of development. But all of the documentation files are accessible online, so "independent" translation efforts are certainly feasible. I'd be happy to enable any such groups to make their translated documentation accessible via the DXLab web site.
and because it's not possible (as far as I know) to easily manage awards like castles, abbeys, flora and fauna and so on.

DXKeeper provides 8 user-defined fields that can be used to capture castle identifiers, abbey identifiers, flora and fauna identifiers, etc; filtered and sorted log report provides a basic view of award progress. If there's a significant group of users pursuing one or several of these awards, adding a dedicated item to each QSO and providing a progress report is literally only an hour or two of development effort - small enough that it can interrupt larger ongoing development efforts.
73,

Dave, AA6YQ


Re: Yaesu RX ANT selection via CAT command

N1BUG
 

On 10/08/2016 08:13 AM, William Liporace wc2l@wc2l.com [dxlab] wrote:


My radio is not hooked up at the moment. I think the antenna
selection is per band. So you would have to do it per band, then it
should stay.
That is true for bands native to the radio... 160 - 6 meters. For higher bands using transverters, the radio has no way of knowing what band is actually being worked or what the settings should be.

Commander remembers the last frequency for each band but has no way of remembering other parameters such as antenna selection.

It's a minor thing, but I wanted to see if anyone had found a way to handle it.

73,
Paul N1BUG


Re: Yaesu RX ANT selection via CAT command

William Liporace WC2L
 

My radio is not hooked up at the moment. I think the antenna selection is per band. So you would have to do it per band, then it should stay.

Will WC2L

On 10/8/2016 6:14 AM, N1BUG paul@... [dxlab] wrote:
I have hesitated to ask because this isn't a DXLab question per se. 
But I want to make sure I am not overlooking something which could 
make life simpler in the "heat of battle".

Since the wonderful extension of DXLab to support transverters on 
more bands (especially 1.25M) I have been working on automating 
VHF/UHF band switching. I have set up custom user control buttons in 
Commander for VHF/UHF band switching. Each button sets important 
FT-2000 parameters such as antenna, IPO, roofing filter, NB, etc. 
This saves a lot of button pushing to get optimum parameters for 
each band. (On HF the FT-2000 remembers all these settings per band 
on its own; I am trying to mimic that for VHF/UHF)

The one thing I cannot control is RX ANT, which in my station must 
always be ON for VHF/UHF. The CAT command for RX ANT is a toggle. If 
that CAT command is sent while RX ANT is off, it turns it on (good). 
But if RX ANT is already on, the command turns it off. Commander has 
no way of knowing the current state, so whether I include that CAT 
command or not, results are not always the same.

Just to be sure I haven't overlooked something: Does anyone know of 
any trick using a third party bridge, extender, or application that 
could ensure RX ANT is always ON after I press one of my user 
defined band change buttons?

Thanks,
Paul N1BUG


------------------------------------
Posted by: N1BUG 
------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/dxlab/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/dxlab/join
    (Yahoo! ID required)

<*> To change settings via email:
    dxlab-digest@... 
    dxlab-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    dxlab-unsubscribe@...

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/



-- 
William Liporace WC2L
http://www.wc2l.com or http://dxc.wc2l.com
AR-Cluster Node  telnet dxc.wc2l.com or 144.93 MHz
wc2l@...


Yaesu RX ANT selection via CAT command

N1BUG
 

I have hesitated to ask because this isn't a DXLab question per se. But I want to make sure I am not overlooking something which could make life simpler in the "heat of battle".

Since the wonderful extension of DXLab to support transverters on more bands (especially 1.25M) I have been working on automating VHF/UHF band switching. I have set up custom user control buttons in Commander for VHF/UHF band switching. Each button sets important FT-2000 parameters such as antenna, IPO, roofing filter, NB, etc. This saves a lot of button pushing to get optimum parameters for each band. (On HF the FT-2000 remembers all these settings per band on its own; I am trying to mimic that for VHF/UHF)

The one thing I cannot control is RX ANT, which in my station must always be ON for VHF/UHF. The CAT command for RX ANT is a toggle. If that CAT command is sent while RX ANT is off, it turns it on (good). But if RX ANT is already on, the command turns it off. Commander has no way of knowing the current state, so whether I include that CAT command or not, results are not always the same.

Just to be sure I haven't overlooked something: Does anyone know of any trick using a third party bridge, extender, or application that could ensure RX ANT is always ON after I press one of my user defined band change buttons?

Thanks,
Paul N1BUG


Re: FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Andrea Maestri
 

Many thanks to Salvatore, Nino and all the other volunteers! I think the same job should be done also for DxLab suite: many friends don't use it
due to difficulties with English and because it's not possible (as far as I know) to easily manage awards like castles, abbeys, flora and fauna and so on. If there's a team of translators or some help is needed it would a pleasure for me to give an hand (for the translation, of course- I have no idea on how to make DxLab more suitable for managing the above awards). 
73!
Andrea, IU4DEG
Inviato da iPhone

Il giorno 08 ott 2016, alle ore 02:52, ' Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> ha scritto:

 

Note the contributions of Salvatore IV4FYV and Nuno CT2IRY, both frequent participants here. Thanks guys!

Will no one rescue French from the grasp of "Google Translate"? Merde!

73,

Dave, AA6YQ

-----Original Message-----
From: ARRL-LOTW@... [mailto:ARRL-LOTW@...]
Sent: Friday, October 07, 2016 8:40 PM
To: ARRL-LOTW@...; 'ARRL LoTW-devel'; 'tqsl-beta'; 'facilitate the testing of TQSL'
Subject: RE: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

The Chinese, English, German, Italian, Japanese, Portuguese, Russian, and Spanish localizations of TQSL 2.3 are each work of volunteer translators:

Chinese: Caros, BH4TXN
German: Andreas DF4WC
Italian: Salvatore IV4FYV
Japanese: Akihiro JL3OXR
Portuguese: Nuno CT2IRY
Russian: Vic US5WE

The easier it is for ops around the world to use LoTW, the higher will be the LoTW confirmation rate. Thus all of us who use LoTW owe these volunteer translators our gratitude, not just those users who will employ a particular localization.

Et qui va représenter la France?

Volunteers are also needed to provide translations for the following languages:

Afrikaans
Albanian
Arabic
Azerbaijani
Belorussian
Bengali
Berber
Bosnian
Bulgarian
Comorian
Croatian
Czech
Danish
Estonian
Fijian
Filipino
Finnish
Georgian
Greek
Hausa
Hebrew
Hindi
Hungarian
Icelandic
Indonesian
Kazakh
Kiribati
Kyrgyz
Latvian
Lithuanian
Malay
Mongolian
Nepali
Norwegian
Pashto
Persian
Punjabi
Romanian
Samoan
Serbian
Sinhala
Slovak
Slovenian
Swahili
Swedish
Tahitian
Tajik
Thai
Tongan
Turkish
Turkmen
Ukrainian
Urdu
Uzbek
Vietnamese

73,

Dave, AA6YQ


Re: Commander 12.3.6 is available

Peter Krüger
 

"- provides the ability to send N1MM-style UDP packets describing the transceiver's frequencies and modes to up to 4 address/port
pairs (Tnx to Larry K8UT, Terry W1TR, and Dwight NS9I)"

That works fine with my n1mm_wag_dxk program - thanks for implementing this feature.
Peter


Commander 12.3.6 is available

Dave AA6YQ
 

This release

- correctly sends decoded CW and RTTY characters to WinWarbler (tnx to Joe K4JKB)

- when controlling a Flex 6000, prevents an overflow in FlexSigClient.FlexTCPPClientWinsock_DataArrival (tnx to Jim NM1W)

- when controlling a Flex 6000, accepts negative values in Filter Group low-cut frequencies (tnx to Kevin K4VD)

- when controlling a Flex 6000, prevents an errorlog.txt file entry when the specified hi-cut or low-cut filter parameter exceeds
the radio's range (tnx to Kevin K4VD)

- when controlling an Icom radio that is not Split, conveys the correct RX and TX frequencies to other DXLab applications (tnx to
Björn SM7IUN)

- when controlling an Icom radio that reports VFO selection and the user selects VFO B or the Sub VFO using the radio's front panel,
correctly updates the VFO B or the Sub VFO frequency display on Commander's Main window

- accepts a CmdSendTX TCP directive that reports whether the primary transceiver is transmitting (tnx to Andy K3WYC and Bill G4WJS)

- if the TCP Network Service's BasePort registry entry is not initialized, sets it to the default value (tnx to Laurie VK3AMA)

- provides the ability to send N1MM-style UDP packets describing the transceiver's frequencies and modes to up to 4 address/port
pairs (Tnx to Larry K8UT, Terry W1TR, and Dwight NS9I)

- adds the NetworkService.htm documentation file

- updates the ChangingBandwidth.htm, CommandSequences.htm, Configuration, Controlling MultipleRadios.htm, index.htm,
Prerequisites.htm, and TXMeter.htm documentation files


Notes:

1. The ability to send N1MM-style UDP packets is controlled from a new "UDP Network Service" panel on Commander's "Network Service"
window, which appears when you click the NetServ button on the right side of the Configuration window's General tab

2. "Interoperating with Green Heron Everywhere" by Dwight NS9I provides step-by-step instructions for using Commander 12.3.6 and
N1MM Rotor to control this Green Heron product:

<http://www.dxlabsuite.com/dxlabwiki/GreenHeronEverywhere>

3. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"

4. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

5. After upgrading, to revert to the previous version of Commander, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


Commander 12.3.6 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ


FW: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

Dave AA6YQ
 

Note the contributions of Salvatore IV4FYV and Nuno CT2IRY, both frequent participants here. Thanks guys!

Will no one rescue French from the grasp of "Google Translate"? Merde!

73,

Dave, AA6YQ

-----Original Message-----
From: ARRL-LOTW@yahoogroups.com [mailto:ARRL-LOTW@yahoogroups.com]
Sent: Friday, October 07, 2016 8:40 PM
To: ARRL-LOTW@yahoogroups.com; 'ARRL LoTW-devel'; 'tqsl-beta'; 'facilitate the testing of TQSL'
Subject: RE: [ARRL-LOTW] TQSL 2.3-rc2 kit available for testing

The Chinese, English, German, Italian, Japanese, Portuguese, Russian, and Spanish localizations of TQSL 2.3 are each work of volunteer translators:

Chinese: Caros, BH4TXN
German: Andreas DF4WC
Italian: Salvatore IV4FYV
Japanese: Akihiro JL3OXR
Portuguese: Nuno CT2IRY
Russian: Vic US5WE

The easier it is for ops around the world to use LoTW, the higher will be the LoTW confirmation rate. Thus all of us who use LoTW owe these volunteer translators our gratitude, not just those users who will employ a particular localization.

Et qui va représenter la France?

Volunteers are also needed to provide translations for the following languages:

Afrikaans
Albanian
Arabic
Azerbaijani
Belorussian
Bengali
Berber
Bosnian
Bulgarian
Comorian
Croatian
Czech
Danish
Estonian
Fijian
Filipino
Finnish
Georgian
Greek
Hausa
Hebrew
Hindi
Hungarian
Icelandic
Indonesian
Kazakh
Kiribati
Kyrgyz
Latvian
Lithuanian
Malay
Mongolian
Nepali
Norwegian
Pashto
Persian
Punjabi
Romanian
Samoan
Serbian
Sinhala
Slovak
Slovenian
Swahili
Swedish
Tahitian
Tajik
Thai
Tongan
Turkish
Turkmen
Ukrainian
Urdu
Uzbek
Vietnamese

73,

Dave, AA6YQ


FW: TQSL 2.3-rc2 kit available for testing

Dave AA6YQ
 

FYI

73,

Dave, AA6YQ

-----Original Message-----
From: k1mu.nospam@gmail.com [mailto:k1mu.nospam@gmail.com] On Behalf Of Rick Murphy
Sent: Friday, October 07, 2016 7:28 PM
To: ARRL LoTW-devel; tqsl-beta; facilitate the testing of TQSL; yahoogroups
Subject: TQSL 2.3-rc2 kit available for testing

After a lot of work by several volunteers to help with a localized version of TQSL, I'm happy to announce a new TQSL release candidate, TQSL v2.3-rc2.

This release incorporates the translations mentioned above, plus several other improvements:

1. A defect that could cause TQSL to fail to import a callsign certificate with "OpenSSL error - bad end line" has been corrected.

2. Creating callsign certificate requests for renewal or for new requests now verify that the "QSO start date" and "QSO end date" match the start and end date for operations from that DXCC entity.

3. When creating a new callsign certificate request, TQSL no longer asks if it should be "signed" or not. Instead, TQSL asks what the callsign certificate is meant for (personal call, dxpedition, club call, etc.) and chooses the proper approach depending on the type of callsign.

As always, testing is very much appreciated. This is a "Release Candidate" which means that I think it's about ready for prime time - testing is the only way I can avoid defects that impact fellow hams. Please give this a try; if there's a problem, you can always uninstall and install the 2.2 release with no loss of data.


Kits:
http://www.rickmurphy.net/lotw/tqsl-2.3.msi for Windows http://www.rickmurphy.net/lotw/tqsl-2.3.dmg for Mac OSX http://www.rickmurphy.net/lotw/tqsl-2.3.tar.gz for Linux

Please give this a spin and let us know how it goes.
73,
-Rick
--

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA


Re: WinWabler xmit rtty, no receive

k4lm
 

Fixed so far.  For some reason my codec microphone input level would turn off.  No matter where I set the level, after a minute the level would shut off.  I rebooted the computer and reset the level and it is holding.  Very strange.

73,
Vant K4LM


Re: Adding DXKeeper Audio Recording

Bob Schaps WB2NVR <wb2nvr@...>
 

Hi Dave -

Finally had a chance to follow your instructions. Everything is now restored.

The only issue I had was that when I double clicked on the audio recording box, it didn't open the location where the recordings were stored.

Other than that, it was easy. Great addition to the suite!

TNX es 73,

Bob WB2NVR


WinWabler xmit rtty, no receive

k4lm
 

All of a sudden I do not get any receive rtty, I don't get any indication of receiving audio.  I am using a TS 590 with USB control and audio is USB codec.  I use FSK and that works fine on transmit.  Receive was working OK and now nothing.  I use Norton and had to delete and reload, but I do not see any blocking.  Any ideas.

Thanks,
Vant K4LM



Re: Rotor issue

Julio Peralta
 

Yes it's working in a much better manner now. I feel like I have better control and better visual indication of what the rotor is doing.

Thanks, Julio W4HY

On 10/7/2016 12:10 PM, 'DGB' ns9i2016@... [dxlab] wrote:
 

Yes Julio that is correct - great program!

73 Dwight NS9I


On 10/7/2016 10:46 AM, Julio jperalta4@... [dxlab] wrote:
 

Thanks for the reply Dwight. I checked confirm Imported Data as you suggested and the rotor isn't moving when clicking on a QSO in DXKeeper anymore, but the black line that indicates where the rotor will go if the GO button is pushed moves to the heading of the QSO in DXKeeper. Is that the way it should work?

Julio

On 10/7/2016 11:33 AM, 'DGB' ns9i2016@... [dxlab] wrote:
 

Julio ... in PST / Setup make sure that Confirm Imported Data is checked.

73 Dwight NS9I


On 10/7/2016 9:58 AM, Julio jperalta4@... [dxlab] wrote:
 

I just started using PST Rotor with DXLabs. I like it because it gives
me more information and control with my rotor.

The problem I'm having is that when I click in any entry in DXKeeper the
rotor moves to a heading for that QSO. I've looked around but don't see
any setting that would cause that in DXKeeper. Is there a way to stop
that from happening?

Julio, W4HY





43141 - 43160 of 204790