Date   

modifications on the logbook entries

ghassan chammas
 

Dear Dave

I was going through the various reports that DXK generates and I found one that tabulates the qso’s worked against those uploaded to LOTW and EQSL and if confirmed or not and the percentages. I found out that I have a difference of 37 between QSO’s logged and those uploaded to LOTW and or EQSL, so I thought I have errors in my logbook entries.

In  fact, I have exported a tab delimited dump of my callbook kept in dxkeeper, and through filtering in excel of each and every field, I came across various errors and anomalies that I corrected in dxkeeper. I found some 50 errors in similar qso’s, and they were all corrected. Tx freq, dates, dxcc entities, station owner, etc were all corrected.

I wish to ask you the following:

 

  1. How can I reflect those corrections in LoTW and EQSL? If I upload through DXK, I will be clicking on “ADD Requested” which I assume will only choose those qso’s not already uploaded. If I upload all the file again, I will create 4000 duplicates. What is the best way to upload my new corrected logbook to LOTW and EQSL?
  2. Is there a way to “delete” the entire logbook in LOTW and EQSL and upload it again, with the new corrected version? Is it a direct upload through their sites or is it through DXK?
  3. Most importantly, if I find a way to upload the new corrected log by deleting the old version on the websites of LOTW and EQSL, would I loose the qsl confirmed qso’s and sent or received? (no verified yet, since I did not submit any logs for awards or verification)? This issue is very important for me.

 

Please note that I am unable to correct on eqsl and lotw the individual qso’s I modified because I lost track of my modifications. I only have an error free log in my DXK.

 

73, and thanks as usual, OD5YA

Kind regards

 

Dr. Ghassan Chammas
Beirut - Lebanon

 


Re: To separately log or not to separately log ... that is the question

Joe Subich, W4TV
 

Would it be best to put each of these in a separate log, or could I put them in the VK2IG log, noting off course that the station callsign would be different - I assume the owner would be VK2IG for
all?
I suppose you could make the Owner VK2IK for all ... I did not.

For each of my old callsigns the Owner/Operator/Station callsigns were
the same (my then licensed callsign). Each had a different "MyQTHid"
(in some cases more than one) with differing state/grid/CQ zone/ITU
zone/county/etc.

73,

... Joe, W4TV


On 11/20/2017 6:53 AM, vk2ig@... [dxlab] wrote:
Good morning / evening all,
I have started using FLE (and some other tools) to convert my paper logs dating approximately 35 years into electronic format. These logs cover two VK4 callsigns (the equivalent to my original Standard and then Advanced licence), two VK1 callsigns, a VK2 callsign and a VK7 callsign. My primary interest is obtaining DXCC credits which I haven't obtained under my current call (e.g. KH3). There is also the odd deleted entity, e.g. Y2, Okinawa, etc.
In summary:
- all callsigns are in the same DXCC entity (VK).
- all callsigns are in the same CQ zone (30).
- VK7 is a different IOTA to the other VK call areas, but I didn't make many HF QSOs from VK7.
- VK4 is a different ITU zone (55) than the other call areas (59).
Would it be best to put each of these in a separate log, or could I put them in the VK2IG log, noting off course that the station callsign would be different - I assume the owner would be VK2IG for all?
73,
Mike VK2IG


To separately log or not to separately log ... that is the question

Mike Dower
 

Good morning / evening all,

I have started using FLE (and some other tools) to convert my paper logs dating approximately 35 years into electronic format.  These logs cover two VK4 callsigns (the equivalent to my original Standard and then Advanced licence), two VK1 callsigns, a VK2 callsign and a VK7 callsign.  My primary interest is obtaining DXCC credits which I haven't obtained under my current call (e.g. KH3).  There is also the odd deleted entity, e.g. Y2, Okinawa, etc.

In summary:

- all callsigns are in the same DXCC entity (VK).
- all callsigns are in the same CQ zone (30).
- VK7 is a different IOTA to the other VK call areas, but I didn't make many HF QSOs from VK7.
- VK4 is a different ITU zone (55) than the other call areas (59).


Would it be best to put each of these in a separate log, or could I put them in the VK2IG log, noting off course that the station callsign would be different - I assume the owner would be VK2IG for all?


73,


Mike VK2IG



Re: Commander and WSJT-x Question

Scott
 

Bill,

I just got around to looking at this and I updated using the formatting for my radio, and this does work perfectly now, so I can let WinWarbler on in the background and can click on a spot and work or listen to the DX. When I am switching WSJT-x now, it stays on USB. Perfect! The only thing, for example, on 1,840 on Commander, the VFO A is red, which apparently indicates out of band. I can easily correct that by changing the color from red to aqua like the other one.

I appreciate your help a lot Bill.

73 Scott
KN3A


SpotCollector 7.8.1 is available

Dave AA6YQ
 

This release corrects a regression in SpotCollector 7.8.0 that when deciding whether to convey a new or updated Spot Database Entry
to Commander erroneously considers SpotCollector's current filtering even though Commander is configured to ignore SpotCollector's
filtering (tnx to Björn SM7IUN)

Notes:

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

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

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


SpotCollector 7.8.1 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: Reconizing the call?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 19, 2017 4:46 AM
To: dxlab@...
Subject: [dxlab] Reconizing the call?

I have been working with Winwarbler for a few weeks now and I have to say that it works very well, but I can not find an option.

And that is the option when I'm calling CQ on Repeat

that when there comes a staion back after the 2 CQ that the transmission is abort

Here's an excerpt from the documentation of <repeat: r, t> in http://www.dxlabsuite.com/winwarbler/Help/Macros.htm>
" the following actions will prematurely terminate any remaining macro repetitions:

a. clicking Cancel in the Repeating Macro window

b. striking the escape key

c. striking any function key

d. clicking any macro button

e. clicking any start, stop, or abort button

f. changing WinWarbler's Mode panel selection"


and where can I find Macros for PSK or do I have to create them myself?

WinWarbler's Scripts folder contains the files "psk sample.txt" and "rtty sample.txt", which contain sample macros. See
<http://www.dxlabsuite.com/dxlabwiki/Macros>

73,
[
Dave, AA6YQ


Re: ClubLog Upload Help

Richard Parker <NguruweMwitu@...>
 

Hi Dave,

As per usual,  you are serving our ham community with greatness.  As per your instruction,  DxKeeper is able to upload to Club Log again.


Many thanks for all your efforts and please continue as you have done in the past.


73 de Rick W4UEF


In a message dated 11/19/2017 15:05:31 Eastern Standard Time, aa6yq@... writes:

On your system, DXKeeper will attempt to delete the existing file whose pathname is

C:\Ham\DxLab\DxKeeper\ClubLogUpload.ADI

and then create a new file with that pathname containing QSOs to be uploaded to ClubLog. Windows is preventing either the deletion or creation operation.

As a first step, use Windows Explorer to navigate to

C:\Ham\DxLab\DxKeeper

Is there a file present named ClubLogUpload.ADI ? If so, delete it. If you succeed, then try directing DXKeeper to upload to Club Log again.

73,

Dave, AA6YQ


-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 19, 2017 12:52 PM
To: dxlab@...
Subject: [dxlab] ClubLog Upload Help



Hello,

I have never gotten an error when uploading to Club Log. However, now DxKeeper sends the following:



Upload File to Club Log: Program error; see errorlog.txt file.


This is in the errorLog:


19-Nov-2017 17:18:56 > DXLogMain.ClubLogUploadCmd_Click
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: N5LXI
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: complete
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, QSOsNeedingUploadingOnly = True, UploadLimit = 5000
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, Callsign = W4UEF
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: TotalsQSOs = 247, Total Files = 1
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: generating file 1
19-Nov-2017 17:18:56 > Program Error in ClubLogModule.UploadFile, err.number = 75, err.description = Path/File access error
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile error hander, response code = 0, response info =


My old PC crashed. DxLab Suite was installed the new PC using DxLauncher. It is running under Windows 10. I have full control on my PC. DxKeeper resides at C:\Ham\DxLab\DxKeeper\DXKeeper.exe


My memory is short. But think that my log has been uploaded to Club Log on the new PC.



Thanking you in advance for any help.


73 de Rick W4UEF




<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: ClubLog Upload Help

Dave AA6YQ
 

On your system, DXKeeper will attempt to delete the existing file whose pathname is

C:&#92;Ham&#92;DxLab&#92;DxKeeper&#92;ClubLogUpload.ADI

and then create a new file with that pathname containing QSOs to be uploaded to ClubLog. Windows is preventing either the deletion or creation operation.

As a first step, use Windows Explorer to navigate to

C:&#92;Ham&#92;DxLab&#92;DxKeeper

Is there a file present named ClubLogUpload.ADI ? If so, delete it. If you succeed, then try directing DXKeeper to upload to Club Log again.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 19, 2017 12:52 PM
To: dxlab@...
Subject: [dxlab] ClubLog Upload Help



Hello,

I have never gotten an error when uploading to Club Log. However, now DxKeeper sends the following:



Upload File to Club Log: Program error; see errorlog.txt file.


This is in the errorLog:

<snip>
19-Nov-2017 17:18:56 > DXLogMain.ClubLogUploadCmd_Click
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: N5LXI
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: complete
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, QSOsNeedingUploadingOnly = True, UploadLimit = 5000
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, Callsign = W4UEF
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: TotalsQSOs = 247, Total Files = 1
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: generating file 1
19-Nov-2017 17:18:56 > Program Error in ClubLogModule.UploadFile, err.number = 75, err.description = Path/File access error
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile error hander, response code = 0, response info = <snip>


My old PC crashed. DxLab Suite was installed the new PC using DxLauncher. It is running under Windows 10. I have full control on my PC. DxKeeper resides at C:&#92;Ham&#92;DxLab&#92;DxKeeper&#92;DXKeeper.exe


My memory is short. But think that my log has been uploaded to Club Log on the new PC.



Thanking you in advance for any help.


73 de Rick W4UEF




<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: SORTING FOR WAZ - CARDS N EQSL?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, November 19, 2017 9:34 AM
To: dxlab@...
Subject: RE: [dxlab] SORTING FOR WAZ - CARDS N EQSL?

The reason I have not taken your first suggestion was that submission would be in the 'thousands' of Q's and I was not anxious to trigger all the possible responses that would likely occur. Hence the desire to limit that upload to those Qs that filled a WAZ need.

If you have thousands of QSOs to upload to eQSL.cc, use this procedure:
<http://www.dxlabsuite.com/dxlabwiki/ExporteQSLADIF>

Since eQSL confirmations count towards awards sponsored by CQ, your QSO partners will thank you.
I had overlooked the WAZ submission capability - does that apply to 5 band WAZ?

Yes: check the "5-band WAZ" box in the "WAZ Bands & Modes" panel on the Configuration window's Awards tab.

The other desired result is to generate an eQSL sort that I can then print QSL cards from those confirmations. I believe CQ requires 'hard copy' QSLs for submission.

CQ accepts eQSLs without your having to print them. See
<http://www.cq-amateur-radio.com/cq_awards/cq_on_line_confirmation/cq_on_line_confirmations.html>

73,

Dave, AA6YQ


ClubLog Upload Help

Richard Parker <NguruweMwitu@...>
 

Hello,

I have never gotten an error when uploading to Club Log.  However,  now DxKeeper sends the following:


Upload File to Club Log: Program error; see errorlog.txt file.


This is in the errorLog:


19-Nov-2017 17:18:56 > DXLogMain.ClubLogUploadCmd_Click
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: N5LXI
19-Nov-2017 17:18:56 > DXLogMain.ValidFields: complete
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, QSOsNeedingUploadingOnly = True, UploadLimit = 5000
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile, Callsign = W4UEF
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: TotalsQSOs = 247, Total Files = 1
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile: generating file 1
19-Nov-2017 17:18:56 > Program Error in ClubLogModule.UploadFile, err.number = 75, err.description = Path/File access error
19-Nov-2017 17:18:56 > ClubLogModule.UploadFile error hander, response code = 0, response info =


My old PC crashed. DxLab Suite was installed the new PC using DxLauncher.  It  is running under Windows 10.   I have full control on my PC.  DxKeeper resides at C:\Ham\DxLab\DxKeeper\DXKeeper.exe


My memory is short.  But think that my log has been uploaded to Club Log on the new PC.


Thanking you in advance for any help.


73 de Rick W4UEF


Re: SORTING FOR WAZ - CARDS N EQSL?

w4qn@...
 

Thanks Dave, 
The reason I have not taken your first suggestion was that submission would be in the 'thousands' of Q's and I was not anxious to trigger all the possible responses that would likely occur.  Hence the desire to limit that upload to those Qs that filled a WAZ need.  

I had overlooked the WAZ submission capability - does that apply to 5 band WAZ?

The other desired result is to generate an eQSL sort that I can then print QSL cards from those confirmations.  I believe CQ requires 'hard copy' QSLs for submission. 

I shall check out the suggestions, it may lead to satisfying my objectives.

Norm W4QN


Reconizing the call?

r1aarden@...
 

Good day


I have been working with Winwarbler for a few weeks now and I have to say that it works very well, but I can not find an option.

And that is the option when I'm calling CQ  on Repeat

that when there comes a staion back after the 2 CQ that the transmission is abort 

this works with MixW in this way and that is very useful.

and where can I find Macros for PSK or do I have to create them myself?

Maybe someone has some example macros for PSK / RTTY?

Thank you in advance


73'

Rien, PA7RA

 


SpotCollector 7.8.0 is available

Dave AA6YQ
 

This release

- sends needed active DX stations to Commander whether or not they are on the transceiver's current band so that the Bandspread
window can properly alert the user to needed DX stations not visible in the Bandspread (tnx to Björn SM7IUN)

- when updating SNR predictions, doesn't generate an errorlog.txt file entry when a deleted Spot Database Entry is encountered

- correctly handles lower-case band and mode names in the sub-band definition file (tnx to Mike AA1AR)

- if the CTRL key is depressed while clicking the "Outgoing spots" panel's Local button, creates a local spot database entry for the
Outgoing spot panel's call on a frequency you are prompted to specify

- correctly conveys active DX stations to Commander's bandspread window when the Spot Database Display is filtered with an SQL
expression and the "Spot Filter" panel is set to "SC Filter" on the Bandspread tab of Commander's Configuration window (tnx to Art
W2NRA)

- updates the ConfigurationDatabase.htm and SpotDatabase.htm documentation files


Notes:

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

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

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


SpotCollector 7.8.0 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


Re: SORTING FOR WAZ - CARDS N EQSL?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, November 18, 2017 9:03 PM
To: dxlab@...
Subject: [dxlab] SORTING FOR WAZ - CARDS N EQSL?

I have had both CW, Phone and Mixed WAZ awards for many years. I note that when in DXKEEPER using WAZ 'Check Progress' I am just an handful short of 5 Band WAZ. CQ Magazine WAZ award program recognizes 5-BAND WAZ award applications with less then the full 200 in hand. CQ also accepts eQSL cards, as well as regular QSL cards for QSO proof, but at this time NOT LoTW confirmations. All facts I think everybody is aware of.

My Quest is to identify and sort my DXKeeper log for ZONE confirmations via eQSL. Then print 'paper' QSL confirmations for submission to CQ.

I infrequently upload to eQSL, and therefore may have an eQSL members, worked for a needed zone, but not submitted to eQSL. I would like to filter my Log, for Needed Zones, Worked with a eQSL user that has not been uploaded to eQSL.

The two objectives above may be somewhat redundant - not sure what a SQL expression would look like.

Summary -

I want to find NEEDED ZONE QSO's with eQSL members that have not been uploaded to eQSL.

I also need to identify NEEDED ZONE QSO's that have been submitted and Confirmed via eQSL.

Hopefully I have understood CQ's WAZ submission requirements correctly, and the filter requests above are possible.

I would appreciate the guidance of those more versed in SQL language then I.

For your first objective, why not simply submit all QSOs to eQSL that have not yet been submitted to eQSL?
See
<http://www.dxlabsuite.com/dxlabwiki/UploadeQSLMarked>

To make a WAZ submission with eQSL AG confirmations, see
<http://www.dxlabsuite.com/dxlabwiki/GenerateWAZSubmission>

73,

Dave, AA6YQ






Norm W4QN





<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>


spam from amazon

Thomas Buesing
 

Sorry if you received a spam email from amazon.

Ttom Bueisng


SORTING FOR WAZ - CARDS N EQSL?

w4qn@...
 

I have had both CW, Phone and Mixed WAZ awards for many years.  I note that when in DXKEEPER  using WAZ 'Check Progress' I am just an handful short of 5 Band WAZ.  CQ Magazine WAZ award program recognizes 5-BAND WAZ award applications with less then the full 200 in hand.  CQ also accepts eQSL cards, as well as regular QSL cards for QSO proof, but at this time NOT LoTW confirmations.  All facts I think everybody is aware of. 


My Quest is to identify and sort my DXKeeper log for ZONE confirmations via eQSL. Then print 'paper' QSL confirmations for submission to CQ.  


I infrequently upload to eQSL, and therefore may have an eQSL members, worked for a needed zone, but not submitted to eQSL.  I would like to filter my Log, for Needed Zones, Worked with a eQSL user that has not been uploaded to eQSL.


The two objectives above may be somewhat redundant - not sure what a SQL expression would look like.


Summary -

I want to find NEEDED ZONE QSO's with eQSL members that have not been uploaded to eQSL.


I also need to identify NEEDED ZONE QSO's that have been submitted and Confirmed via eQSL.


Hopefully I have understood CQ's WAZ submission requirements correctly, and the filter requests above are possible.


I would appreciate the guidance of those more versed in SQL language then I.


Norm W4QN


Re: QSL Labels

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, November 18, 2017 2:30 PM
To: dxlab@...
Subject: [dxlab] QSL Labels

I want to send multiple QSOs/label on 3 column labels, but when I add several QSOs, sometimes over 1 year apart, to the same call I
get multiple labels. However, if the dates are real close I get a single label with 2 QSOs. Where do I set the number of QSOs/label
and or the time limits?

QSO Dates have no impact on whether QSOs are printed on the same card or label. From the documentation:
"When QSLing via QSL cards, Reply cards, or QSL labels, DXKeeper will by default confirm multiple QSOs with the same station on the
same card or label if

- the station callsign items of each such QSO are identical

- the Via item of each such QSO are identical

- if multiple QTH's are in use, the QTH components, e.g. street, city, state, country, and postal code, of each such QSO are
identical

- there is space on the cards or labels"

<http://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing with Paper>

73,

Dave, AA6YQ


QSL Labels

Ed Kuebert, K5EK
 

I want to send multiple QSOs/label on 3 column labels, but when I add several QSOs, sometimes over 1 year apart, to the same call I get multiple labels. However, if the dates are real close I get a single label with 2 QSOs. Where do I set the number of QSOs/label and or the time limits?

 

Thanks for your help.

 

Ed, K5EK

 


Re: Commander and WSJT-x Question

g4wjs
 

Hi Scott,

that means that WinWarbler is asking Commander to switch to LSB. I use WSJT-X while WInWarbler is running and have had that issue in the past, I don't recall which setting resolved it, I suspect you need to create a custom BandModes.txt in the SpotCollector directory with segments for digital AFSK modes like those used by WSJT-X marked as USB. For example here is an extract from mine (for rigs with USB-DATA mode it would be different):

1800,1838,CW,160M
1838,1842,USB,160M
1842,2000,LSB,160M
3500,3576,CW,80M
3576,3580,USB,80M
3580,3600,RTTY,80M
3600,3800,LSB,80M
7000,7040,CW,40M
7040,7050,RTTY,40M
7050,7076,LSB,40M
7076,7080,USB,40M
7080,7200,LSB,40M
10100,10130,CW,30M
10130,10138,RTTY,30M
10138,10142,USB,30M
10142,10150,RTTY,30M
14000,14070,CW,20M
14070,14076,RTTY,20M
14076,14080,USB,20M
14080,14099,RTTY,20M
14099,14101,CW,20M
14101,14350,USB,20M
18068,18095,CW,17M
18095,18102,RTTY,17M
18102,18106,USB,17M
18106,18109,RTTY,17M
18109,18111,CW,17M
18111,18168,USB,17M
21000,21070,CW,15M
21070,21076,RTTY,15M
21076,21080,USB,15M
21080,21149,RTTY,15M
21149,21151,CW,15M
21151,21450,USB,15M
24890,24915,CW,12M
24915,24917,RTTY,12M
24917,24921,USB,12M
24921,24929,RTTY,12M
24929,24931,CW,12M
24931,24990,USB,12M
28000,28070,CW,10M
28070,28076,RTTY,10M
28076,28080,USB,10M
28080,28190,RTTY,10M
28190,28300,CW,10M
28300,29510,USB,10M
29510,29700,FM,10M
50000,50110,CW,6M
50110,50300,USB,6M
50500,54000,FM,6M
70000,71000,CW,4M
144000,144180,CW,2M
144180,144400,USB,2M
144400,144500,CW,2M
144500,144794,USB,2M
144794,145800,FM,2M
145800,146000,USB,2M
430000,432000,FM,70CM
432000,432100,CW,70CM
432100,432400,USB,70CM
432400,432500,CW,70CM
432500,432994,USB,70CM
432994,433600,FM,70CM
433600,434000,USB,70CM
434000,440000,FM,70CM
902000,928000,FM,33CM
1240000,1300000,FM,23CM
2400000,2600000,FM,12CM

73
Bill
G4WJS.