Date   

Re: Commander's new Spectrum-Waterfall Display

Björn SM7IUN
 

Dave,

A fair comment and I do not disagree but always displaying the entire band (e.g. 21,000-21,450MHz) as a waterfall is fairly useless. 

The straightforward approach is of course ot use the currently active waterfall edges in the radio. This is how e.g. N1MM+ works.

The problem is that there are only three waterfall edge sets in the radio, making it impossible to have unique waterfall edge sets for CW, Phone and Digital modes if you want to also allocate one for zoom in on pile-ups. On top of that you have to sacrifice one of the 80m sets for use on 60m. 

Another option is to use a Rumlog-like method where the waterfall only shows a section of the band in
use (say, a 20kHz segment) and shifts this section in half steps (in this case 10kHz) as you turn the VFO knob.  

Björn SM7IUN


2017-10-07 21:02 GMT+02:00 'w6de' w6de@... [dxlab] <dxlab@...>:

 

You say: “My thinking was that a very useful feature would be if Commander set the waterfall edges based on current mode and band.

 

Performing this would depend on the bandmode file in SpotCollector.  This could get ugly as the mode edges vary depending on the activity on the air.  Contests widen mode areas substantially.  In addition new modes are popping up now and the questions about why doesn’t the correct mode populate WinWarbler and/or the Capture window for a spot? 

 

DXLab users have to be above the average computer user knowledge user to trouble shoot problems as it is now.  Adding yet another variable increases the skill user of the user community.  I can see some user community frustration now, as to why things don’t automatically fix themselves.

 

The ultimate decision is AA6YQ’s but making things more complex is an issue.

 

Dave, w6de

 

From: dxlab@... [mailto:dxlab@...]
Sent: 07 October, 2017 05:11
To: DXLab forum
Subject: Re: [dxlab] Commander's new Spectrum-Waterfall Display

 




Hi Art,

 

Although in theory you could use a slider to set the waterfall edges I am not sure it would be very useful.

 

My thinking was that a very useful feature would be if Commander set the waterfall edges based on current mode and band.

 

For instance, when you are 20m CW the Waterfall would display 14,000-14,070. Then if you change to RTTY, it would switch to, say, 14,070-14,100.

 

Also, having a built-in possibility for a "pile-up zoom-in" would be great, meaning showing just five or ten kHz of the band with the current receive frequency in the left half.

 

Since the waterfall zero level varies somewhat with bandwidth on the IC-7300, it would also be useful to have a custom REF level for each such subband.

 

73,


Björn SM7IUN

 

 

2017-10-07 6:45 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:

 

Hi Björn,

 

I think you're talking over my head. I think I understand your per band/per mode slider objective. My objectives are a little easier, all CW in narrow band segments but vary in different places on the band.  But can you do this with a slider?  Or are you hoping for this option in Dave's Spectrum software enhancement?

 

73, Art, W2NRA


On Oct 5, 2017, at 4:30 PM, Björn Ekelund bjorn@... [dxlab] <dxlab@...> wrote:

 

Thanks Art,

 

My primary objective was to have a per-band REF level. This is solved with a per-band slider control.

 

Having per-mode/per-band waterfall edges would also be a super nice feature, meaning that you would zoom in on only the relevant mode band segment. 

 

Also, having a pile-up zoom-in that's, say, 5kHz for CW and 10 for SSB wide would also be great.

 

To be really useful the size and span of the waterfall needs to be constant for reasonable amounts of time.

 

73,

 

Björn I1/SM7IUN

 

2017-10-05 19:42 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:

 

Bjorn,

 

I think it would be impossible to create sliders that would vary the Scope Band Edges.  There are 4 variables; Band, Edge #, Lower Frequency, Higher Frequency.   Sliders can only handle one variable.  Also the frequencies are not even sequential.  

 

They're:  10Hz, 1Hz, 1KHz, 100Hz, 100KHz, 10KHz, 10MHz, 1MHz, 1000MHz, 100MHz

 

73, Art, W2NRA


On Oct 05, 2017, at 01:07 PM, "Björn Ekelund bjorn@... [dxlab]" <dxlab@...> wrote:

 

 

Of course Dave had already thought of this...

 

Reading the documentation more carefully I just found that you can include sliders in Commander’s Device control.

 

Problem solved.

 

Björn SM7IUN 

 

 

 


5 okt. 2017 kl. 15:29 skrev Björn Ekelund <bjorn@...>:

Because of the limitations of DXLab Commander macros I have written a few Python scripts for waterfall edge management.

 

The one I use most often sets edge set #2 for the band in question to 1kHz below the current receive frequency and 6kHz above. 

Perfect zoom-in for working a CW pile-up. I also have a program that resets all the edges to a "reasonable" default, including e.g. the European 60m band. (Having this integrated in Commander would be great but I realize it may be a little too niche...)

 

I would be more than happy to share the code with anyone interested. The scripts are written in Python 3.6 with serial.py installed. 

I let them talk to my IC-7300 via "physical" C-IV interface but you can also use a software COM-port splitter.

 

Another feature I would love a waterfall-capable Commander to include would be per-band REF level setting. REF is the zero point for the waterfall and spectrum scope and because atmospheric/man-made background noise levels vary quite a bit between bands, it would be very helpful if this setting was per-band. Perhaps it is on the more expensive ICOMs? On the IC-7300 it is a single global setting meaning the Waterfall background is completely black on e.g 12m but pretty white on 80m. 

 

Or is this just my ignorance and you could do this already today with Commander? It would require the transmission of a per-band unique CI-V command at band changes.

 

Björn I1/SM7IUN

 

 

2017-10-05 14:38 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:

 

Hi Dave,

 

FYI the Spectrum Display in N1MM Logger+ only displays the band edge as displayed in the IC-7300.  N1MM Logger+ does not changes the band edges.  I’ve set up simple macro in Commander to do that.  Your version of the Spectrum Display within Commander would be a big improvement.  I look forward to assist you in testing your new Spectrum-Waterfall Display.

73, Art, W2NRA


On Oct 4, 2017, at 11:22 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

Last Wednesday, I asked Ray N9JA, Icom America's Senior Sales Manager, if Icom would loan me an IC-7300 for a couple of weeks so I
could extend Commander to provide a Spectrum-Waterfall display using the scope data the radio reports via its USB connection. A
brand new IC-7300 arrived yesterday; support from a radio manufacturer just doesn't get any better than that!

Commander's new Spectrum-Waterfall Display is now displaying both a spectrum and a waterfall. There's still more work to do before
I'll have a minimal first iteration for IC-7300 owners to check out-- adding a frequency display that controls and tracks the "span"
and "centered/fixed settings", displaying active DX stations highlighted for "award need" and eQSL/LoTW participation, and
controlling VFOs with mouse gestures -- but much of the technical risk in this project has been eradicated.

The IC-7850 and IC-7851 can also report scope data via their USB connections, and the new IC-7610 is expected to provide this
capability. The IC-7850 and IC-7851 report more scope data than does the IC-7300, albeit in the same format. I've implemented the
Spectrum-Waterfall Display in a manner that should accommodate this difference, so I'll soon be looking for a "first tester" who
owns one of these radios.

The downside? Completing the transition to an override database in DXView, SpotCollector, and DXKeeper will be delayed by a few more
weeks.

It's only been here for one day, but I now see why IC-7300 owners are so enthusiastic about their radios. It'd be a big step up from
the IC-7200 I take on holiday operations.

73,

Dave, AA6YQ

 

 

 

 

 

 






Re: Rotor control with N1MM Rotor on other compuer?

Gordon LaPoint
 

Dave,
     Thanks for the answer.   Is it possible to add the address choice as an upgrade in the future?
Gordon - N1MGO

On 10/7/2017 3:49 PM, 'Dave AA6YQ' aa6yq@... [dxlab] wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, October 07, 2017 11:08 AM
To: DXLab forum
Subject: [dxlab] Rotor control with N1MM Rotor on other compuer?

Is it possible to setup DXView to use N1MM rotor control on another computer on the same subnet?

>>>No, the host address is hardwired to 127.0.0.1

73,

Dave, AA6YQ



Re: Commander's new Spectrum-Waterfall Display

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Saturday, October 07, 2017 3:03 PM
To: dxlab@yahoogroups.com
Subject: RE: [dxlab] Commander's new Spectrum-Waterfall Display

DXLab users have to be above the average computer user knowledge user to trouble shoot problems as it is now. Adding yet another variable increases the skill user of the user community. I can see some user community frustration now, as to why things don’t automatically fix themselves.

What things should automatically fix themselves?
73,

Dave, AA6YQ


Re: Rotor control with N1MM Rotor on other compuer?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Saturday, October 07, 2017 11:08 AM
To: DXLab forum
Subject: [dxlab] Rotor control with N1MM Rotor on other compuer?

Is it possible to setup DXView to use N1MM rotor control on another computer on the same subnet?

No, the host address is hardwired to 127.0.0.1
73,

Dave, AA6YQ


Re: DXK - Detecting changed LoTW QSL

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Saturday, October 07, 2017 11:17 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXK - Detecting changed LoTW QSL

If I have a LoTW QSL in DXK and that QSL information is changed by a later LoTW conformation then I don't seem to receive any notification of the change(s).

LoTW does not provide a means of notifying you (or a logging application acting on your behalf) that one of your QSOs has been newly confirmed, or that the details of one of your already- confirmed QSOs have changed (e.g. a previously-missing grid square is now included in the confirmation). However, when you invoke DXKeeper's "Sync LoTW QSLs" operation, LoTW will report all new or updated confirmations since the last time you invoked "Sync LoTW QSLs". You can also right-click a QSO's Log Page Display entry and select "Update from LoTW" from the popup menu.
73,

Dave, AA6QY


Re: DXKeeper will not open

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Saturday, October 07, 2017 2:21 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] DXKeeper will not open

Hello...I've been running DXLabs for years. For some reason now I can't get the DXKeeper window to open. It's green on the launcher and I have a icon showing that it's active but it's nowhere to be seen on the screen.

On the Launcher's Configuration window, click the Reset button along the bottom.

I have deleted and reinstalled, no difference.

This is an extraordinarily bad step to take. It risks creating a situation where your only recourse is to wipe your hard drive and re-install Windows.
Uninstalling an re-installing a Windows application is only indicated when Windows complains that a component or library is missing or uninstalled.
73,

Dave, AA6YQ


Re: Commander's new Spectrum-Waterfall Display

w6de
 

You say: “My thinking was that a very useful feature would be if Commander set the waterfall edges based on current mode and band.”

Performing this would depend on the bandmode file in SpotCollector. This could get ugly as the mode edges vary depending on the activity on the air. Contests widen mode areas substantially. In addition new modes are popping up now and the questions about why doesn’t the correct mode populate WinWarbler and/or the Capture window for a spot?

DXLab users have to be above the average computer user knowledge user to trouble shoot problems as it is now. Adding yet another variable increases the skill user of the user community. I can see some user community frustration now, as to why things don’t automatically fix themselves.

The ultimate decision is AA6YQ’s but making things more complex is an issue.

Dave, w6de

From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: 07 October, 2017 05:11
To: DXLab forum
Subject: Re: [dxlab] Commander's new Spectrum-Waterfall Display





Hi Art,

Although in theory you could use a slider to set the waterfall edges I am not sure it would be very useful.

My thinking was that a very useful feature would be if Commander set the waterfall edges based on current mode and band.

For instance, when you are 20m CW the Waterfall would display 14,000-14,070. Then if you change to RTTY, it would switch to, say, 14,070-14,100.

Also, having a built-in possibility for a "pile-up zoom-in" would be great, meaning showing just five or ten kHz of the band with the current receive frequency in the left half.

Since the waterfall zero level varies somewhat with bandwidth on the IC-7300, it would also be useful to have a custom REF level for each such subband.

73,

Björn SM7IUN


2017-10-07 6:45 GMT+02:00 ART SEARLE w2nra@me.com [dxlab] <dxlab@yahoogroups.com>:

Hi Björn,

I think you're talking over my head. I think I understand your per band/per mode slider objective. My objectives are a little easier, all CW in narrow band segments but vary in different places on the band. But can you do this with a slider? Or are you hoping for this option in Dave's Spectrum software enhancement?

73, Art, W2NRA

On Oct 5, 2017, at 4:30 PM, Björn Ekelund bjorn@ekelund.nu [dxlab] <dxlab@yahoogroups.com> wrote:

Thanks Art,

My primary objective was to have a per-band REF level. This is solved with a per-band slider control.

Having per-mode/per-band waterfall edges would also be a super nice feature, meaning that you would zoom in on only the relevant mode band segment.

Also, having a pile-up zoom-in that's, say, 5kHz for CW and 10 for SSB wide would also be great.

To be really useful the size and span of the waterfall needs to be constant for reasonable amounts of time.

73,

Björn I1/SM7IUN

2017-10-05 19:42 GMT+02:00 ART SEARLE w2nra@me.com [dxlab] <dxlab@yahoogroups.com>:

Bjorn,

I think it would be impossible to create sliders that would vary the Scope Band Edges. There are 4 variables; Band, Edge #, Lower Frequency, Higher Frequency. Sliders can only handle one variable. Also the frequencies are not even sequential.

They're: 10Hz, 1Hz, 1KHz, 100Hz, 100KHz, 10KHz, 10MHz, 1MHz, 1000MHz, 100MHz

73, Art, W2NRA

On Oct 05, 2017, at 01:07 PM, "Björn Ekelund bjorn@ekelund.nu [dxlab]" <dxlab@yahoogroups.com> wrote:


Of course Dave had already thought of this...

Reading the documentation more carefully I just found that you can include sliders in Commander’s Device control.

Problem solved.

Björn SM7IUN




5 okt. 2017 kl. 15:29 skrev Björn Ekelund <bjorn@ekelund.nu>:
Because of the limitations of DXLab Commander macros I have written a few Python scripts for waterfall edge management.

The one I use most often sets edge set #2 for the band in question to 1kHz below the current receive frequency and 6kHz above.
Perfect zoom-in for working a CW pile-up. I also have a program that resets all the edges to a "reasonable" default, including e.g. the European 60m band. (Having this integrated in Commander would be great but I realize it may be a little too niche...)

I would be more than happy to share the code with anyone interested. The scripts are written in Python 3.6 with serial.py installed.
I let them talk to my IC-7300 via "physical" C-IV interface but you can also use a software COM-port splitter.

Another feature I would love a waterfall-capable Commander to include would be per-band REF level setting. REF is the zero point for the waterfall and spectrum scope and because atmospheric/man-made background noise levels vary quite a bit between bands, it would be very helpful if this setting was per-band. Perhaps it is on the more expensive ICOMs? On the IC-7300 it is a single global setting meaning the Waterfall background is completely black on e.g 12m but pretty white on 80m.

Or is this just my ignorance and you could do this already today with Commander? It would require the transmission of a per-band unique CI-V command at band changes.

Björn I1/SM7IUN


2017-10-05 14:38 GMT+02:00 ART SEARLE w2nra@me.com [dxlab] <dxlab@yahoogroups.com>:

Hi Dave,

FYI the Spectrum Display in N1MM Logger+ only displays the band edge as displayed in the IC-7300. N1MM Logger+ does not changes the band edges. I’ve set up simple macro in Commander to do that. Your version of the Spectrum Display within Commander would be a big improvement. I look forward to assist you in testing your new Spectrum-Waterfall Display.
73, Art, W2NRA

On Oct 4, 2017, at 11:22 PM, 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com> wrote:

Last Wednesday, I asked Ray N9JA, Icom America's Senior Sales Manager, if Icom would loan me an IC-7300 for a couple of weeks so I
could extend Commander to provide a Spectrum-Waterfall display using the scope data the radio reports via its USB connection. A
brand new IC-7300 arrived yesterday; support from a radio manufacturer just doesn't get any better than that!

Commander's new Spectrum-Waterfall Display is now displaying both a spectrum and a waterfall. There's still more work to do before
I'll have a minimal first iteration for IC-7300 owners to check out-- adding a frequency display that controls and tracks the "span"
and "centered/fixed settings", displaying active DX stations highlighted for "award need" and eQSL/LoTW participation, and
controlling VFOs with mouse gestures -- but much of the technical risk in this project has been eradicated.

The IC-7850 and IC-7851 can also report scope data via their USB connections, and the new IC-7610 is expected to provide this
capability. The IC-7850 and IC-7851 report more scope data than does the IC-7300, albeit in the same format. I've implemented the
Spectrum-Waterfall Display in a manner that should accommodate this difference, so I'll soon be looking for a "first tester" who
owns one of these radios.

The downside? Completing the transition to an override database in DXView, SpotCollector, and DXKeeper will be delayed by a few more
weeks.

It's only been here for one day, but I now see why IC-7300 owners are so enthusiastic about their radios. It'd be a big step up from
the IC-7200 I take on holiday operations.

73,

Dave, AA6YQ


Re: DXKeeper will not open

John Battin
 

You do not happen to have dual momitors?

From: bryanbeam@yahoo.com [dxlab]<mailto:dxlab@yahoogroups.com>
Sent: Saturday, October 7, 2017 1:21 PM
To: dxlab@yahoogroups.com<mailto:dxlab@yahoogroups.com>
Subject: [dxlab] DXKeeper will not open



Hello...I've been running DXLabs for years. For some reason now I can't get the DXKeeper window to open. It's green on the launcher and I have a icon showing that it's active but it's nowhere to be seen on the screen.



I have deleted and reinstalled, no difference.



Any help will be appreciated!



73,



Bryan, W4HLD




[Non-text portions of this message have been removed]


DXKeeper will not open

bryanbeam
 

Hello...I've been running DXLabs for years. For some reason now I can't get the DXKeeper window to open. It's green on the launcher and I have a icon showing that it's active but it's nowhere to be seen on the screen.


I have deleted and reinstalled, no difference. 


Any help will be appreciated!


73,


Bryan, W4HLD


Re: LOTW changed FT8 mode to DATA for batch uploaded QSOs

Dave AA6YQ
 

There have been no other reports of a "temporary problem of the lotw servers" converting the mode of FT8 QSOs to DATA, Andrea. The LoTW Server doesn't have the capability to do that; it's TQSL that performs the mapping from FT8 to DATA under your direction; it does this before submitting your QSOs to the LotW Server.

I'll consider this issue closed. If it happens again, please let me know.

73,

Dave, AA6YQ

-----Original Message-----
From: Andrea Maestri - IU4DEG [mailto:iu4deg@gmail.com]
Sent: Saturday, October 07, 2017 3:04 AM
To: Dave AA6YQ
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

You thought right. The other day I selected all the QSOs from the 1st to the 2rd of Oct )about 50 more or less), then I added them all to the Lotw QSL queue and then uploaded. When I checkd the lotw web site they were online but with the generic data mode instead of ft8. Perhaps it's been a temporary problem of the lotw servers.

Thanks again!

Andrea


2017-10-07 5:48 GMT+02:00 Dave AA6YQ <aa6yq@ambersoft.com>:


I thought you reported that the mode was changed to DATA when you uploaded via the QSL Queue.

What's the scenario that doesn't work correctly?

Dave

-----Original Message-----
From: Andrea Maestri - IU4DEG [mailto:iu4deg@gmail.com]

Sent: Friday, October 06, 2017 6:37 PM
To: Dave AA6YQ
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Hallo Dave!

Here it is the file. The upload worked fine and on the lotw server the three QSOs are in the right FT8 mode.
73!

Andrea


2017-10-06 21:34 GMT+02:00 Dave AA6YQ <aa6yq@ambersoft.com>:


Thanks. Please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. log 3 QSOs in FT8 mode

3. On the Main window's QSL tab

3a. set the "QSL Via" panel to LoTW

3b. click the "Add Requested" button and confirm that the QSL Queue is populated with the 3 FT8 QSOs you worked

3c. click the "Upload to LoTW" button

4. on the Configuration window's General tab, uncheck the "Log debugging info" box

5. attach the errorlog.txt file from your DXKeeper folder to an email message, and send it my way

73,

Dave, AA6YQ

-----Original Message-----

From: Andrea Maestri - IU4DEG [mailto:iu4deg@gmail.com]
Sent: Friday, October 06, 2017 4:34 AM
To: Dave AA6YQ
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Hallo Dave!

Attached is the shot of my last qso with YO3CDN. It's been regulary loaded as FT8. In the same shot you find double QSOs (DATA - FT8) starting from the one with W1EQ because at first I put all the QSOs from the first of october to the LOTW DXKeeper Qsl queue and then uploaded to the server and resulted in DATA mode insted of FT8. The same QSOs with the corrcect FT8 mode were obtained using the exporting to adif for lotw, signing and uploadin them with TQSL. As regards "uploading one by one" I used both the LOTW DXKeeper Qsl queue and right click on the QSO "upload to Lotw" function. Both of them returned a correct FT8 mode in the uploaded QSO. I only encountered this problem queueing batch of QSOs. Sorry if I haven't been able to be clear enough.

Thanks again.
73!

Andrea IU4DEG


2017-10-06 9:48 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:





Earlier, you posted

"If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode."

What actions you are taking when you say "If I upload QSOs one by one".

When you next log an FT8 QSO, please do the following:

1. upload the QSO to LoTW using DXKeeper's QSL Queue

2. log in to your LoTW web account

3. direct LoTW to display your most recently submitted QSOs

4. make a screen shot showing your most recently submitted QSOs in LoTW

5. attach the screen shot to an email message the specifies the callsign of the FT8 station you logged

6. send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]


Sent: Friday, October 06, 2017 2:56 AM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Done and no sign of mapping is present i TQSL.

Andrea

2017-10-06 3:58 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:




If you have TQSL running, please terminate it.

On the LoTW tab of DXKeeper's "QSL Configuration" window, click the TQSL panel's Run button to start TQSL. Has the "FT8 to DATA" mapping been deleted from this instance of TQSL?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:27 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Yes Dave! I followed the instructions and I deleted the FT8 to DATA mapping as I updated TQSL. If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode. Also if I export an adif file for LOTW, sign and upload it with TQSL, all is fine and the right mode is preserved.

Thanks for your help!

Andrea

2017-10-06 3:11 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:




>>>AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:03 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

No, my TQSL is updated with the latest Configuration Data file version 11.1 since it was released.

>>>Did you delete the "FT8 to DATA" mapping you added to TQSL before the 11.1 configuration file was available?




<https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > > > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > > > > >

73,

Dave, AA6YQ







<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > > > Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > > >








<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > > Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > >












<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > >






<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >






<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Rotor control with N1MM Rotor on other compuer?

Gordon LaPoint
 

Is it possible to setup DXView to use N1MM rotor control on another computer on the same subnet?

I currently have DXView using the rotor thru N1MM rotor control on the same computer, but I use a second station setup on a second computer.


PS.   Thanks for the auto upload to LOTW when using JTAlert!!!


Thank you,

Gordon - N1MM


Re: Commander's new Spectrum-Waterfall Display

Björn SM7IUN
 

Hi Art,

Although in theory you could use a slider to set the waterfall edges I am not sure it would be very useful.

My thinking was that a very useful feature would be if Commander set the waterfall edges based on current mode and band.

For instance, when you are 20m CW the Waterfall would display 14,000-14,070. Then if you change to RTTY, it would switch to, say, 14,070-14,100.

Also, having a built-in possibility for a "pile-up zoom-in" would be great, meaning showing just five or ten kHz of the band with the current receive frequency in the left half.

Since the waterfall zero level varies somewhat with bandwidth on the IC-7300, it would also be useful to have a custom REF level for each such subband.

73,

Björn SM7IUN


2017-10-07 6:45 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:

 

Hi Björn,

I think you're talking over my head. I think I understand your per band/per mode slider objective. My objectives are a little easier, all CW in narrow band segments but vary in different places on the band.  But can you do this with a slider?  Or are you hoping for this option in Dave's Spectrum software enhancement?

73, Art, W2NRA

On Oct 5, 2017, at 4:30 PM, Björn Ekelund bjorn@... [dxlab] <dxlab@...> wrote:

 

Thanks Art,

My primary objective was to have a per-band REF level. This is solved with a per-band slider control.

Having per-mode/per-band waterfall edges would also be a super nice feature, meaning that you would zoom in on only the relevant mode band segment. 

Also, having a pile-up zoom-in that's, say, 5kHz for CW and 10 for SSB wide would also be great.

To be really useful the size and span of the waterfall needs to be constant for reasonable amounts of time.

73,

Björn I1/SM7IUN

2017-10-05 19:42 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:
 

Bjorn,

I think it would be impossible to create sliders that would vary the Scope Band Edges.  There are 4 variables; Band, Edge #, Lower Frequency, Higher Frequency.   Sliders can only handle one variable.  Also the frequencies are not even sequential.  

They're:  10Hz, 1Hz, 1KHz, 100Hz, 100KHz, 10KHz, 10MHz, 1MHz, 1000MHz, 100MHz

73, Art, W2NRA

On Oct 05, 2017, at 01:07 PM, "Björn Ekelund bjorn@... [dxlab]" <dxlab@...> wrote:

 


Of course Dave had already thought of this...

Reading the documentation more carefully I just found that you can include sliders in Commander’s Device control.

Problem solved.

Björn SM7IUN 




5 okt. 2017 kl. 15:29 skrev Björn Ekelund <bjorn@...>:

Because of the limitations of DXLab Commander macros I have written a few Python scripts for waterfall edge management.

The one I use most often sets edge set #2 for the band in question to 1kHz below the current receive frequency and 6kHz above. 
Perfect zoom-in for working a CW pile-up. I also have a program that resets all the edges to a "reasonable" default, including e.g. the European 60m band. (Having this integrated in Commander would be great but I realize it may be a little too niche...)

I would be more than happy to share the code with anyone interested. The scripts are written in Python 3.6 with serial.py installed. 
I let them talk to my IC-7300 via "physical" C-IV interface but you can also use a software COM-port splitter.

Another feature I would love a waterfall-capable Commander to include would be per-band REF level setting. REF is the zero point for the waterfall and spectrum scope and because atmospheric/man-made background noise levels vary quite a bit between bands, it would be very helpful if this setting was per-band. Perhaps it is on the more expensive ICOMs? On the IC-7300 it is a single global setting meaning the Waterfall background is completely black on e.g 12m but pretty white on 80m. 

Or is this just my ignorance and you could do this already today with Commander? It would require the transmission of a per-band unique CI-V command at band changes.

Björn I1/SM7IUN


2017-10-05 14:38 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:
 

Hi Dave,


FYI the Spectrum Display in N1MM Logger+ only displays the band edge as displayed in the IC-7300.  N1MM Logger+ does not changes the band edges.  I’ve set up simple macro in Commander to do that.  Your version of the Spectrum Display within Commander would be a big improvement.  I look forward to assist you in testing your new Spectrum-Waterfall Display.

73, Art, W2NRA

On Oct 4, 2017, at 11:22 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

Last Wednesday, I asked Ray N9JA, Icom America's Senior Sales Manager, if Icom would loan me an IC-7300 for a couple of weeks so I
could extend Commander to provide a Spectrum-Waterfall display using the scope data the radio reports via its USB connection. A
brand new IC-7300 arrived yesterday; support from a radio manufacturer just doesn't get any better than that!

Commander's new Spectrum-Waterfall Display is now displaying both a spectrum and a waterfall. There's still more work to do before
I'll have a minimal first iteration for IC-7300 owners to check out-- adding a frequency display that controls and tracks the "span"
and "centered/fixed settings", displaying active DX stations highlighted for "award need" and eQSL/LoTW participation, and
controlling VFOs with mouse gestures -- but much of the technical risk in this project has been eradicated.

The IC-7850 and IC-7851 can also report scope data via their USB connections, and the new IC-7610 is expected to provide this
capability. The IC-7850 and IC-7851 report more scope data than does the IC-7300, albeit in the same format. I've implemented the
Spectrum-Waterfall Display in a manner that should accommodate this difference, so I'll soon be looking for a "first tester" who
owns one of these radios.

The downside? Completing the transition to an override database in DXView, SpotCollector, and DXKeeper will be delayed by a few more
weeks.

It's only been here for one day, but I now see why IC-7300 owners are so enthusiastic about their radios. It'd be a big step up from
the IC-7200 I take on holiday operations.

73,

Dave, AA6YQ








Re: Commander's new Spectrum-Waterfall Display

ART SEARLE <w2nra@...>
 

Hi Björn,

I think you're talking over my head. I think I understand your per band/per mode slider objective. My objectives are a little easier, all CW in narrow band segments but vary in different places on the band.  But can you do this with a slider?  Or are you hoping for this option in Dave's Spectrum software enhancement?

73, Art, W2NRA

On Oct 5, 2017, at 4:30 PM, Björn Ekelund bjorn@... [dxlab] <dxlab@...> wrote:

 

Thanks Art,

My primary objective was to have a per-band REF level. This is solved with a per-band slider control.

Having per-mode/per-band waterfall edges would also be a super nice feature, meaning that you would zoom in on only the relevant mode band segment. 

Also, having a pile-up zoom-in that's, say, 5kHz for CW and 10 for SSB wide would also be great.

To be really useful the size and span of the waterfall needs to be constant for reasonable amounts of time.

73,

Björn I1/SM7IUN

2017-10-05 19:42 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:
 

Bjorn,

I think it would be impossible to create sliders that would vary the Scope Band Edges.  There are 4 variables; Band, Edge #, Lower Frequency, Higher Frequency.   Sliders can only handle one variable.  Also the frequencies are not even sequential.  

They're:  10Hz, 1Hz, 1KHz, 100Hz, 100KHz, 10KHz, 10MHz, 1MHz, 1000MHz, 100MHz

73, Art, W2NRA

On Oct 05, 2017, at 01:07 PM, "Björn Ekelund bjorn@... [dxlab]" <dxlab@...> wrote:

 


Of course Dave had already thought of this...

Reading the documentation more carefully I just found that you can include sliders in Commander’s Device control.

Problem solved.

Björn SM7IUN 




5 okt. 2017 kl. 15:29 skrev Björn Ekelund <bjorn@...>:

Because of the limitations of DXLab Commander macros I have written a few Python scripts for waterfall edge management.

The one I use most often sets edge set #2 for the band in question to 1kHz below the current receive frequency and 6kHz above. 
Perfect zoom-in for working a CW pile-up. I also have a program that resets all the edges to a "reasonable" default, including e.g. the European 60m band. (Having this integrated in Commander would be great but I realize it may be a little too niche...)

I would be more than happy to share the code with anyone interested. The scripts are written in Python 3.6 with serial.py installed. 
I let them talk to my IC-7300 via "physical" C-IV interface but you can also use a software COM-port splitter.

Another feature I would love a waterfall-capable Commander to include would be per-band REF level setting. REF is the zero point for the waterfall and spectrum scope and because atmospheric/man-made background noise levels vary quite a bit between bands, it would be very helpful if this setting was per-band. Perhaps it is on the more expensive ICOMs? On the IC-7300 it is a single global setting meaning the Waterfall background is completely black on e.g 12m but pretty white on 80m. 

Or is this just my ignorance and you could do this already today with Commander? It would require the transmission of a per-band unique CI-V command at band changes.

Björn I1/SM7IUN


2017-10-05 14:38 GMT+02:00 ART SEARLE w2nra@... [dxlab] <dxlab@...>:
 

Hi Dave,


FYI the Spectrum Display in N1MM Logger+ only displays the band edge as displayed in the IC-7300.  N1MM Logger+ does not changes the band edges.  I’ve set up simple macro in Commander to do that.  Your version of the Spectrum Display within Commander would be a big improvement.  I look forward to assist you in testing your new Spectrum-Waterfall Display.

73, Art, W2NRA

On Oct 4, 2017, at 11:22 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

Last Wednesday, I asked Ray N9JA, Icom America's Senior Sales Manager, if Icom would loan me an IC-7300 for a couple of weeks so I
could extend Commander to provide a Spectrum-Waterfall display using the scope data the radio reports via its USB connection. A
brand new IC-7300 arrived yesterday; support from a radio manufacturer just doesn't get any better than that!

Commander's new Spectrum-Waterfall Display is now displaying both a spectrum and a waterfall. There's still more work to do before
I'll have a minimal first iteration for IC-7300 owners to check out-- adding a frequency display that controls and tracks the "span"
and "centered/fixed settings", displaying active DX stations highlighted for "award need" and eQSL/LoTW participation, and
controlling VFOs with mouse gestures -- but much of the technical risk in this project has been eradicated.

The IC-7850 and IC-7851 can also report scope data via their USB connections, and the new IC-7610 is expected to provide this
capability. The IC-7850 and IC-7851 report more scope data than does the IC-7300, albeit in the same format. I've implemented the
Spectrum-Waterfall Display in a manner that should accommodate this difference, so I'll soon be looking for a "first tester" who
owns one of these radios.

The downside? Completing the transition to an override database in DXView, SpotCollector, and DXKeeper will be delayed by a few more
weeks.

It's only been here for one day, but I now see why IC-7300 owners are so enthusiastic about their radios. It'd be a big step up from
the IC-7200 I take on holiday operations.

73,

Dave, AA6YQ







Re: Spot Collector not populating

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Friday, October 06, 2017 12:53 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Spot Collector not populating

Spot Collector has been acting up lately and finally quit. I removed the app and downloaded spot collector from the Launcher but now it will not populate the spot display. The Tel-Net Clusters are working, all my settings are the same but the Filter in the Spot display Shows, All. I have tried to clear the filter but to no avail.

In the past a quick Filter clear would restore the spots but not now.

Any suggestions would be much appreciated.

Is there an errorlog.txt file in your SpotCollector folder? If so, please attach it to an email message, and send it to me via
aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Spot Collector not populating

james aprile
 

Spot Collector has been acting up lately and finally quit. I removed the app and downloaded spot collector from the Launcher but now it will not populate the spot display. The Tel-Net Clusters are working, all my settings are the same but the Filter in the Spot display Shows, All. I have tried to clear the filter but to no avail.

In the past a quick Filter clear would restore the spots but not now.

Any suggestions would be much appreciated.

Thank you de Jim K5KND



Re: PSK JT & FT Not Working

Bob Schaps WB2NVR <wb2nvr@...>
 

Thanks Dave and Joe.

After checking all of the configuration settings and cables and not finding anything wrong, I was ready to give up. Using the MK2 Soundcard Test feature, I noticed that the ACC2 output was working correctly, but the TS-990 was intermittent. I decided to do a full reset of the TS-990, and that resolved the problem.

I just want to thank Dave (one more time!) for the great software, and Joe for the excellent manual for the microKeyer II.

73 ES GUD DX,

Bob WB2NVR


Re: LOTW changed FT8 mode to DATA for batch uploaded QSOs

Dave AA6YQ
 

Earlier, you posted

"If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode."

What actions you are taking when you say "If I upload QSOs one by one".

When you next log an FT8 QSO, please do the following:

1. upload the QSO to LoTW using DXKeeper's QSL Queue

2. log in to your LoTW web account

3. direct LoTW to display your most recently submitted QSOs

4. make a screen shot showing your most recently submitted QSOs in LoTW

5. attach the screen shot to an email message the specifies the callsign of the FT8 station you logged

6. send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Friday, October 06, 2017 2:56 AM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs



Done and no sign of mapping is present i TQSL.

Andrea


2017-10-06 3:58 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:





If you have TQSL running, please terminate it.

On the LoTW tab of DXKeeper's "QSL Configuration" window, click the TQSL panel's Run button to start TQSL. Has the "FT8 to DATA" mapping been deleted from this instance of TQSL?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:27 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Yes Dave! I followed the instructions and I deleted the FT8 to DATA mapping as I updated TQSL. If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode. Also if I export an adif file for LOTW, sign and upload it with TQSL, all is fine and the right mode is preserved.

Thanks for your help!

Andrea

2017-10-06 3:11 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:




>>>AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:03 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

No, my TQSL is updated with the latest Configuration Data file version 11.1 since it was released.

>>>Did you delete the "FT8 to DATA" mapping you added to TQSL before the 11.1 configuration file was available?

<https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> <https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> > >

73,

Dave, AA6YQ







<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >










<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Re: LOTW changed FT8 mode to DATA for batch uploaded QSOs

Andrea Maestri
 

Done and no sign of mapping is present i TQSL.
Andrea

2017-10-06 3:58 GMT+02:00 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...>:

 

If you have TQSL running, please terminate it.

On the LoTW tab of DXKeeper's "QSL Configuration" window, click the TQSL panel's Run button to start TQSL. Has the "FT8 to DATA" mapping been deleted from this instance of TQSL?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, October 05, 2017 9:27 PM
To: dxlab@...
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

Yes Dave! I followed the instructions and I deleted the FT8 to DATA mapping as I updated TQSL. If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode. Also if I export an adif file for LOTW, sign and upload it with TQSL, all is fine and the right mode is preserved.

Thanks for your help!

Andrea

2017-10-06 3:11 GMT+02:00 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...>:




>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, October 05, 2017 9:03 PM
To: dxlab@...
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

No, my TQSL is updated with the latest Configuration Data file version 11.1 since it was released.

>>>Did you delete the "FT8 to DATA" mapping you added to TQSL before the 11.1 configuration file was available?

<https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> >

73,

Dave, AA6YQ







<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>




Re: LOTW changed FT8 mode to DATA for batch uploaded QSOs

Dave AA6YQ
 

If you have TQSL running, please terminate it.

On the LoTW tab of DXKeeper's "QSL Configuration" window, click the TQSL panel's Run button to start TQSL. Has the "FT8 to DATA" mapping been deleted from this instance of TQSL?

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:27 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs



Yes Dave! I followed the instructions and I deleted the FT8 to DATA mapping as I updated TQSL. If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode. Also if I export an adif file for LOTW, sign and upload it with TQSL, all is fine and the right mode is preserved.

Thanks for your help!

Andrea


2017-10-06 3:11 GMT+02:00 'Dave AA6YQ' aa6yq@ambersoft.com [dxlab] <dxlab@yahoogroups.com>:





>>>AA6YQ comments below

-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, October 05, 2017 9:03 PM
To: dxlab@yahoogroups.com
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

No, my TQSL is updated with the latest Configuration Data file version 11.1 since it was released.

>>>Did you delete the "FT8 to DATA" mapping you added to TQSL before the 11.1 configuration file was available?

<https://lotw.arrl.org/lotw-help/pref-adi/ <https://lotw.arrl.org/lotw-help/pref-adi/> >

73,

Dave, AA6YQ









<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Re: LOTW changed FT8 mode to DATA for batch uploaded QSOs

Andrea Maestri
 

Yes Dave! I followed the instructions and I deleted the FT8 to DATA mapping as I updated TQSL. If I upload QSOs one by one all it's working fine and the FT8 mode is preserved, instead If I add them to the QSL queue (lotw) when uploaded to the server they are listed with the DATA mode. Also if I export an adif file for LOTW, sign and upload it with TQSL, all is fine and the right mode is preserved.
Thanks for your help!
Andrea

2017-10-06 3:11 GMT+02:00 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...>:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, October 05, 2017 9:03 PM
To: dxlab@...
Subject: Re: [dxlab] LOTW changed FT8 mode to DATA for batch uploaded QSOs

No, my TQSL is updated with the latest Configuration Data file version 11.1 since it was released.

>>>Did you delete the "FT8 to DATA" mapping you added to TQSL before the 11.1 configuration file was available?

<https://lotw.arrl.org/lotw-help/pref-adi/>

73,

Dave, AA6YQ


33001 - 33020 of 204629