Date   
Re: LPT port bi-directional? #n1mm

Larry K8UT
 

Rene

No. It is not possible to operate today's LPT ports bi-directionally. Older motherboard-based ports were bi-directional, but not today's PCIe cards and USB-to-LPT adapters. N1MM's LPT/BCD antenna selection is a one-way message sent to external devices.

>So when selecting the band the correct BCD code has been sent to the interface

Where do you select the band? In N1MM? On your radio? somewhere else? If you're selecting somewhere else, that info does not flow upstream to the logger or the radio.

You might want to consider using TCP/UDP packets if you want bi-directional input and response when changing bands. Take a look at the design for Band Decoding and Remote Antenna control in my freeware FreqEZ program.:

www.hamprojects.info/freqez

-larry (K8UT)


------ Original Message ------
From: pe9rx@...
Sent: 2019-04-14 08:14:03
Subject: [N1MMLoggerPlus] LPT port bi-directional? #n1mm

I am working here with the N1mm logger + and have successfully setup the Antenna data and mapped it to the LPT port.

So when selecting the band the correct BCD code has been sent to the interface and the correct antenna has been selected.
But is it also possible for the interface to sent a command back to the logger, so that when i manually select a band, the Logger pick's this up and set's the correct band in the program?

FYI,  I am using the logger for Microwave bands and instead of selecting just the antenna, I am selecting the correct transverter etc.
made my own interface for the band/antenna selector.

73, René

Re: FLEX RADIO V 3.0 Interface to N1MM

Bruce Whitney W8RA
 

Thanks for your response Jeff.  It looks to me from DAX/CAT that the 3.0 is a lot different from previous V's...
I will try to get some help from Flex as well... 
73

Re: LPT port bi-directional? #n1mm

pe9rx@...
 

I select the band on N1MM now, but also have a interface on my desk which does the same.
For now I can pnly let N1MM doe the band select during contest, en when I am using the setup without the contest I use the interface box.

The Ethernet solution is also a great solution. i will look into this. Thanx.

Log problem Gagarin Cup

Les Elliott
 

Logger is not transferring the Rcvd info into the Cabrillo log 100%
Log1 is as logged.
 
Log1:
QSO:  7011 CW 2019-04-14 0737 M5M           599 27     YL1ZF         599 29       
QSO:  7021 CW 2019-04-14 0740 M5M           599 27     YT6W          599 28       
QSO:  7020 CW 2019-04-14 0740 M5M           599 27     LA8OM         599 18       
QSO:  7029 CW 2019-04-14 0742 M5M           599 27     LY3B          599 29       
QSO:  7009 CW 2019-04-14 0743 M5M           599 27     S52NY         599 28       
QSO: 14011 CW 2019-04-14 0745 M5M           599 27     UA5C          599 29       
QSO: 14013 CW 2019-04-14 0746 M5M           599 27     UA3KW         599 29       
QSO: 14015 CW 2019-04-14 0747 M5M           599 27     R3FX          599 29       
QSO: 14016 CW 2019-04-14 0749 M5M           599 27     R2ZA          599 29       
QSO: 14018 CW 2019-04-14 0750 M5M           599 27     YU1YV         599 28       
QSO: 14020 CW 2019-04-14 0753 M5M           599 27     UA1ORK        599 19       
QSO: 14021 CW 2019-04-14 0754 M5M           599 27     9H1XT         599 28       
QSO: 14022 CW 2019-04-14 0755 M5M           599 27     RM1T          599 29       
QSO: 14022 CW 2019-04-14 0756 M5M           599 27     RK9LWA        599 30       
QSO: 14026 CW 2019-04-14 0757 M5M           599 27     RA9AP         599 30       
QSO: 14033 CW 2019-04-14 0759 M5M           599 27     UA3RZ         599 29       
QSO: 14033 CW 2019-04-14 0800 M5M           599 27     RW3QJ         599 29       
QSO: 14036 CW 2019-04-14 0801 M5M           599 27     UN2E          599 30       
QSO: 14045 CW 2019-04-14 0805 M5M           599 27     RK3DK         599 29       
QSO: 14045 CW 2019-04-14 0805 M5M           599 27     RK4S          599 29       
QSO: 14055 CW 2019-04-14 0806 M5M           599 27     EW6F          599 29       
QSO: 14012 CW 2019-04-14 0809 M5M           599 27     EU5C          599 29       
QSO: 14014 CW 2019-04-14 0812 M5M           599 27     RN3F          599 29       
QSO: 14028 CW 2019-04-14 0818 M5M           599 27     RT9A          599 30       
QSO: 14031 CW 2019-04-14 0818 M5M           599 27     RT4F          599 29       
QSO: 14034 CW 2019-04-14 0821 M5M           599 27     RC9J          599 21       
QSO: 14038 CW 2019-04-14 0825 M5M           599 27     RL9I          599 21       
QSO: 14044 CW 2019-04-14 0826 M5M           599 27     RT5G          599 29       
QSO: 14011 CW 2019-04-14 0828 M5M           599 27     UN9LW         599 30       
QSO: 14011 CW 2019-04-14 0829 M5M           599 27     YT6W          599 28
 
Cabrillo log:
QSO:  7011 CW 2019-04-14 0737 M5M           599 27     YL1ZF         599 29       
QSO:  7021 CW 2019-04-14 0740 M5M           599 27     YT6W          599 29       
QSO:  7020 CW 2019-04-14 0740 M5M           599 27     LA8OM         599 18       
QSO:  7029 CW 2019-04-14 0742 M5M           599 27     LY3B          599 29       
QSO:  7009 CW 2019-04-14 0743 M5M           599 27     S52NY         599 28       
QSO: 14011 CW 2019-04-14 0745 M5M           599 27     UA5C          599 29       
QSO: 14013 CW 2019-04-14 0746 M5M           599 27     UA3KW         599 29       
QSO: 14015 CW 2019-04-14 0747 M5M           599 27     R3FX          599 29       
QSO: 14016 CW 2019-04-14 0749 M5M           599 27     R2ZA          599 29       
QSO: 14018 CW 2019-04-14 0750 M5M           599 27     YU1YV         599 28       
QSO: 14020 CW 2019-04-14 0753 M5M           599 27     UA1ORK        599 29       
QSO: 14021 CW 2019-04-14 0754 M5M           599 27     9H1XT         599 28       
QSO: 14022 CW 2019-04-14 0755 M5M           599 27     RM1T          599 29       
QSO: 14022 CW 2019-04-14 0756 M5M           599 27     RK9LWA        599 29       
QSO: 14026 CW 2019-04-14 0757 M5M           599 27     RA9AP         599 29       
QSO: 14033 CW 2019-04-14 0759 M5M           599 27     UA3RZ         599 29       
QSO: 14033 CW 2019-04-14 0800 M5M           599 27     RW3QJ         599 29       
QSO: 14036 CW 2019-04-14 0801 M5M           599 27     UN2E          599 30       
QSO: 14045 CW 2019-04-14 0805 M5M           599 27     RK3DK         599 29       
QSO: 14045 CW 2019-04-14 0805 M5M           599 27     RK4S          599 29       
QSO: 14055 CW 2019-04-14 0806 M5M           599 27     EW6F          599 29       
QSO: 14012 CW 2019-04-14 0809 M5M           599 27     EU5C          599 37       
QSO: 14014 CW 2019-04-14 0812 M5M           599 27     RN3F          599 29       
QSO: 14028 CW 2019-04-14 0818 M5M           599 27     RT9A          599 29       
QSO: 14031 CW 2019-04-14 0818 M5M           599 27     RT4F          599 29       
QSO: 14034 CW 2019-04-14 0821 M5M           599 27     RC9J          599 29       
QSO: 14038 CW 2019-04-14 0825 M5M           599 27     RL9I          599 29       
QSO: 14044 CW 2019-04-14 0826 M5M           599 27     RT5G          599 29       
QSO: 14011 CW 2019-04-14 0828 M5M           599 27     UN9LW         599 30       
QSO: 14011 CW 2019-04-14 0829 M5M           599 27     YT6W          599 28       
Les, G4OGB

Re: Log problem Gagarin Cup

Gerald Boutin (VE1DT)
 

Big oops. I see that here as well. GCUP contest

The program appears to be logging the exchange in SECT and generating the Cabrillo from something that ended up into ZN.

It was broken in v1.0.7170. Going back to v1.0.7161 fixes the issue. 



--
Gerald, VE1DT

Re: Log problem Gagarin Cup

Axel Schernikau, DL6KVA
 

The number put into zone seems to be guessed from first letters put into the callsign entry box. It doesn't change afterwards if you correct the call or just add some more numbers/letters to the prefix.

It's not really fun to check 600+ QSOs ... I did that step by step while CQing ;)

73

Axel, DL6KVA

Am 14.04.2019 um 17:00 schrieb Gerald Boutin (VE1DT):

Big oops. I see that here as well. GCUP contest

The program appears to be logging the exchange in SECT and generating the Cabrillo from something that ended up into ZN.

It was broken in v1.0.7170. Going back to v1.0.7161 fixes the issue. 



--
Gerald, VE1DT

Re: Log problem Gagarin Cup

Victor Androsov
 

Hi,

As I see the latest version is 1.7610.0 (I don't see any 1.7170 on the N1MM+ site))

Anyway I see a lot of serious bugs in 1.7610.

1. Total mess up with multipliers:

- N1MM doesn't recognize new zone multiplier. For example I worked AA3B with zone 8 on 15m. The next QSO with KO7SS from zone 6 should give me a new one mult. But it has been ignored. ))

- On 15m bandmap I have plenty of calls from new zones: PY (z12) LU (z14). But they are not marked by red on the bandmap.

- Some multipliers are marked as non worked even they were worked already. I worked VE3 from z4 on 20m but I still see on the bandmap VE3 stations in red.

- Wrong entered callsign could trigger the entry windows to show up a new mult even after correction. For example:  I've incorrectly entered EL5MW instead of DL5MW. After correction to DL5MW it still marks a new mult even I've worked a number DLs before. After log the QSO I see the red sign on the M1 field and I also see the mult summary has been updated by plus one.

So finally I've found few "fake" mults in my log. All my attempts to re-score the whole contest doesn't have any effect. All the numbers are still the same without any changes.

2. One more sad logger behavior started after upgrading to the new version 1.7610.0. In the ECM mode logger can log QSO with empty exchange number. That wasn't like that before! I tried to find out an appropriate option in the N1MM+ settings to stop that. But I didn't find anything related.

So this year GC-CUP contest has been completely ruined. I have no idea what's my score and multiplier. Not a big deal since it's a part time. But could be nice to have something reliable before next major contest as CQ WPX CW etc..  Is any chance to roll back to a good known version?

73!

Victor
VA2WA


On Sun, 14 Apr 2019 at 13:03, Axel Schernikau, DL6KVA <dl6kva@...> wrote:
The number put into zone seems to be guessed from first letters put into the callsign entry box. It doesn't change afterwards if you correct the call or just add some more numbers/letters to the prefix.

It's not really fun to check 600+ QSOs ... I did that step by step while CQing ;)

73

Axel, DL6KVA

Am 14.04.2019 um 17:00 schrieb Gerald Boutin (VE1DT):
Big oops. I see that here as well. GCUP contest

The program appears to be logging the exchange in SECT and generating the Cabrillo from something that ended up into ZN.

It was broken in v1.0.7170. Going back to v1.0.7161 fixes the issue. 



--
Gerald, VE1DT

Alfaspid rotor

sp5ewx
 

HELLO
Maybe somebody encountered the same problem during control alfaspid
rotor...It doesnt exists permanently but from time to time ....There
is report of error in error log ...I have to restart comp to resume
the contro;ll ...System is WIn7 pro 64
Regards
Mike sp5ewx



Thread # 1 @ 2019-04-14 20:12:01.618 PM
N1MMRotor.Net - Version 1.0.7610.0
Built: 4/9/2019 1:14:42 PM
Microsoft Windows NT 6.1.7601 Service Pack 1, 64 bit:True
Error occurred at: 4/14/2019 10:12:01 PM
---------------------------------------------------------------------------------------
System.InvalidOperationException: Port is closed
at System.IO.Ports.SerialPort.Write(String text)
at N1MMRotor.Net.Rotor.GoAZIAlfaSpid(Double& Direction) in
C:\N1MM+Source\N1MM Logger on .NET\N1MM
Rotor.Net\Classes\Rotor_cls.vb:line 451
at N1MMRotor.Net.Rotor.GoAzi(Double& Direction, Double& offsetdir,
Boolean& Bidirect) in C:\N1MM+Source\N1MM Logger on .NET\N1MM
Rotor.Net\Classes\Rotor_cls.vb:line 313
---------------------------------------------------------------------------------------


Call Stack before the runtime error: at
System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM
Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 89
at N1MMRotor.Net.SharedCode.HandleError(Exception e, String
PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM
Rotor.Net\Modules\SharedCode.vb:line 157
at N1MMRotor.Net.Rotor.GoAzi(Double& Direction, Double& offsetdir,
Boolean& Bidirect) in C:\N1MM+Source\N1MM Logger on .NET\N1MM
Rotor.Net\Classes\Rotor_cls.vb:line 325
at N1MMRotor.Net.RotorForm.GoBtn_Click(Object eventSender,
EventArgs eventArgs) in C:\N1MM+Source\N1MM Logger on .NET\N1MM
Rotor.Net\Forms\Rotor_frm.vb:line 427
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr
dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[]
commandLine)
at N1MMRotor.Net.My.MyApplication.Main(String[] Args) in :line 82

Re: FLEX RADIO V 3.0 Interface to N1MM

Kari Gustafsson SM0HRP
 

I have the same set-up as you Bruce and N1MM works fine. Even in SO2R mode. 73 Kari SM0HRP

OK-OM DX Contest Cabrillo from N1MM refused

Ben
 

Hello,


I try to upload my cabrillo log from N1MM for this contest , but it is always refused by the system " incorrect number of fields in QSO record "

Is there a solution , can somebody help me ?

Looking forward  for your comments and help.


Thanks in advance

Bernard
ON5GQ

Re: Log problem Gagarin Cup

Gerald Boutin (VE1DT)
 

On Sun, Apr 14, 2019 at 02:34 PM, Victor Androsov wrote:
As I see the latest version is 1.7610.0 (I don't see any 1.7170 on the N1MM+ site))
 
The v1.0.7161 file is available where all of the downloads are. Files/Latest Updates.  v1.7170 is the version where the problem first showed up.

http://n1mm.hamdocs.com/tiki-list_file_gallery.php?galleryId=15

It was near the bottom of page 1 when I found it earlier today. As best as I can tell, it appears to generate a correct Cabrillo file. I don't know about the other issues you mentioned

--
Gerald, VE1DT

SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

Alan Holdsworth <alanholdsworth@...>
 

For anyone that is interested.

 

I have had confirmation from 2 sources that the SPID RAU controller using the USB port/cable works using N1MM+ AlfaSpid software.

 

Thank you to all who helped with this enquiry.

 

TTFN AlanH g8oo

 

Re: SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

sp5ewx
 

Hi Alan
It works indeed but ...did you encounter the problem I mentioned in my
e-mail on the group before ???
Regards
sp5ewx

On Mon, Apr 15, 2019 at 4:41 AM Alan Holdsworth
<alanholdsworth@...> wrote:

For anyone that is interested.



I have had confirmation from 2 sources that the SPID RAU controller using the USB port/cable works using N1MM+ AlfaSpid software.



Thank you to all who helped with this enquiry.



TTFN AlanH g8oo



Re: SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

Alan Holdsworth <alanholdsworth@...>
 

Hi sp5ewx

I have not purchased the SPID rotator but needed to know that it worked with N1MM before going any further.

A helpful radio ham from Scotland who already owns a SPID RAU and also required the settings for N1MM tried out the AlfaSpid software last night with N1MM and responded that it worked OK and no I cannot recall your previous comments on the SPID RAU rotator pse repeat or send your comments through the reflector or direct to alan@...

De AlanH g8oo

G800.com

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of sp5ewx
Sent: 15 April 2019 07:51
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

Hi Alan
It works indeed but ...did you encounter the problem I mentioned in my
e-mail on the group before ???
Regards
sp5ewx

On Mon, Apr 15, 2019 at 4:41 AM Alan Holdsworth
<alanholdsworth@...> wrote:

For anyone that is interested.



I have had confirmation from 2 sources that the SPID RAU controller using the USB port/cable works using N1MM+ AlfaSpid software.



Thank you to all who helped with this enquiry.



TTFN AlanH g8oo



Re: SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

Maciej Muszalski
 

It does work with N1MM+. Have it, use it. 


On Mon, Apr 15, 2019 at 10:17 AM Alan Holdsworth <alanholdsworth@...> wrote:
Hi sp5ewx

I have not purchased the SPID rotator but needed to know that it worked with N1MM before going any further.

A helpful radio ham from Scotland who already owns a SPID RAU and also required the settings for N1MM tried out the AlfaSpid software last night with N1MM and responded that it worked OK and no I cannot recall your previous comments on the SPID RAU rotator pse repeat or send your comments through the reflector or direct to alan@...

De AlanH g8oo

G800.com


-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of sp5ewx
Sent: 15 April 2019 07:51
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] SPID RAU. Has anyone got any experience of this rotator and is it compatible with N1MM+?

Hi Alan
It works indeed but ...did you encounter the problem I mentioned in my
e-mail on the group before ???
Regards
sp5ewx

On Mon, Apr 15, 2019 at 4:41 AM Alan Holdsworth
<alanholdsworth@...> wrote:
>
> For anyone that is interested.
>
>
>
> I have had confirmation from 2 sources that the SPID RAU controller using the USB port/cable works using N1MM+ AlfaSpid software.
>
>
>
> Thank you to all who helped with this enquiry.
>
>
>
> TTFN AlanH g8oo
>
>
>
>






Re: FLEX RADIO V 3.0 Interface to N1MM

Bruce Whitney W8RA
 

I Just left a voice message at Flex,for help, seems their on-line help desk is broken?
Maybe they are getting lots of calls re. V3.0?

N1MM logger for WWV special event

markholbrook
 

Hi all,

 

I’m part of a club putting together a special event station to celebrate the 100 year anniversary of radio station WWV.

 

Our plan is to operate 4-6 stations from 28, September through 1, October 2019 at the WWV site in Fort Collins, CO.

 

Please see:   wwv100.com

 

We are in need of operators that would like to come to Fort Collins and be a part of this special event.

 

I’ve been placed in charge of setting up station logging.   I am strongly leaning toward using N1MM as the logger for all stations.

 

What I don’t know and I’m wondering if the group here can answer some questions:

 

  1. Since this is not a contest in the true sense of the word do I need to work with N1MM developers for a special “non-contest” module that will allow the logging to work?   I see this as similar to a DXpedition where we simply need to keep track of CALL, FREQ, BAND, MODE, DATE, TIME.  We don’t really care about duplicates and there really is no score other than how many contacts we make.   Suggestions would be appreciated.
  2. When we have networked our 5-6 stations and all are running N1MM does each station get a complete copy of the database?  I know the instances do talk for duplicate checking, but I’m wondering about ensuring we have a good backup of the log data.
  3. During the event we will have a highspeed network link and we plan to upload to ClubLog.  What is the best way do to this?  I have not tried to set something like this up in N1MM and I’m not sure if it even can.  So how do DXpeditions log data to ClubLog?
  4. After the event is over we will need to take the full database and perform a number of tasks including submission to a QSL Bureau and probably LOTW   Same question:   What is the best way to accomplish this?

 

I realize some of these questions might be answered in some prior DXpedition notes so I’m looking for those right now.  If anyone knows of any DXpeditions that did similar things please point me to their websites or locations where I might be able to ask or access their operations data.

 

Thanks in advance.

 

I hope to see some of you in Fort Collins for this event!   We are expecting a lot of activity.

 

Mark – WS7M

Re: FLEX RADIO V 3.0 Interface to N1MM

Andy (KU7T)
 

Bruce,
N1MM+ works fine with Flex v3. Zero issues. Also, nothing has changed in the CAT interface which is being used to interface the two.

What exact issues are you having?

73,
Andy
KU7T

CTY-2906 Country Files - 16 April 2019

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 16 April 2019:

http://www.country-files.com/cty-2906-16-april-2019/

For installation instructions, start at:

http://www.country-files.com/

Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:

http://www.country-files.com/big-cty-16-april-2019/

Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.

As a reminder, there is an RSS feed of the latest country file announcements:

http://www.country-files.com/feed/

Here are the release notes:

16 April 2019 (CTY-2906)
VER20190416, Version entity is Bonaire, PJ4

Added/changed Entities/Prefixes/Callsigns:

* 3Y0E is Bouvet, 3Y/b
* 9M4CKT and 9M4CRB are both East Malaysia, 9M6
* EA2EZ/P is Spain, EA
* AM70URE/6 is Balearic Islands, EA6
* AM70URE/8 is Canary Islands, EA8
* AM70URE/9 is Ceuta & Melilla, EA9
* GB19CIM is Isle of Man, GD
* GB19CGI, GB19CNI and GB4UAS are all Northern Ireland, GI
* GB19CJ is Jersey, GJ
* GB0BOC, GB19CGM, GB19CS, GB2M and GB5FHC are all Scotland, GM
* GB19CG is Guernsey, GU
* GB19CGW, GB19CW, GB19SG, GB2BYF, GB4GM and GB8MD are all Wales, GW
* N9BD is United States, K in CQ zone 3, ITU zone 6
* KD9BSO, KP2XX, N3CI, W1JCW, W9RM and WF3H are all United States, K in CQ zone 4, ITU zone 7
* K4TZ, KM4RO, KY4KD, N4BCB and N4HID are all United States, K in CQ zone 4, ITU zone 8
* AJ7G, KH6CT, N0SMX, NP2L and W7IGC are all United States, K in CQ zone 5, ITU zone 8
* KB5OXR is Guam, KH2
* AJ6JF, K7NRJ, KB1UHL, W8WH and WY6F are all Hawaii, KH6
* K1KAO, K7Y, KB3VQE, KC0LLL, KD5WYP, N1HEN and NM0H are all Alaska, KL
* KC1KZI and N1ZJC are both Puerto Rico, KP4
* LU1XZ/H, LU4ERS/D, LU5HA/H, LU5QR/Q, LU9GOY/L and LW3EK/D are all Argentina, LU
* R0WX/P, R1961AG, R1961GP, R1994YU, R1996VK, R2019DC, R75SEV, R9OM/6,
RA9SGI/1, RO75KR, RT9K/6 and UE19DC are all European Russia, UA
* UD6AOP/0 is Asiatic Russia, UA9
* R26RRC is Asiatic Russia, UA9 in CQ zone 19, ITU zone 34
* VE2NN is Canada, VE in CQ zone 2, ITU zone 4
* VK6AV/2 is Australia, VK

Removed Entities/Prefixes/Callsigns:

* 3Y0I in Bouvet, 3Y/b
* B9/BH1NGG in China, BY
* IA0/IZ1KHY, RI1ANV and RI1ANX in Antarctica, CE9
* TO8T in Martinique, FM
* GB50WAB in Northern Ireland, GI
* GB0GGR and GB5AG in Scotland, GM
* GB4SDD in Wales, GW
* IT9RGY/4 in Italy, I
* AJ5E, AK9D, K7BG, K7GM, K9CQ, KE5PRL, KK9A, KP3M, N1KEZ, N4AB, W4CQE,
W4HOD, W4UAT, W8AKS, W8HAP and WL7YQ in United States, K
* N0J and NU2A in Mariana Islands, KH0
* AE5AB and K6APP in Hawaii, KH6
* K7UNX and KF7PUQ in Alaska, KL
* K5YJR in Puerto Rico, KP4
* LU1WL/W, LU2CRV/D, LU2DT/D, LU2VV/V, LU2XWL/XP, LU3DRP/D, LU3DRP/E,
LU3DXG/D, LU4DQ/D, LU5DGG/D, LU5DMP/D, LU5JCL/J, LU6DDC/D, LU6DM/D, LU6WG/W,
LU7DD/W, LU7DZV/D, LU7WFM/W, LU8ACH/D, LU8DCH/D, LU8EHV/D, LU8XW/X, LU8XW/XP,
LU9JMG/J, LW3DER/D and LW7EDH/D in Argentina, LU
* R120MG, R30AFC, R30AFG, R30AFO, R30AFQ, R30AFR, R30AMV, R30DIK, R30DRA,
R30GNP, R30ZIN, RA9UUY/6, RM0L/1, UE23DKA, UE23DSA, UE23DZO and UE96ME
in European Russia, UA
* RK4PA/9 and RZ5D/9 in Asiatic Russia, UA9
* VK6MB/1 in Australia, VK

73 - Jim AD1C

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us

Re: FT8 DX Contest

Ken G0ORH
 

I could not find anything relating to this contest setup, wot Frequencies for contesting! Etc.
 FT8 with N1MM google drew a blanc here for some reason.
Got it now, via Lee, VE7CC...'tks.

WHEN is the next FT8 contest scheduled guys! 
I'll setup and give some points out on the Flex6500.


Ken.. G0ORH



On 4 Apr 2019, at 21:13, Steve Sawyer <kt0dx@q.com> wrote:

If you are referring to the FT8 Contest that starts on 13 April from the information on the web site you would use the RTTY RU file from what I can tell.  WSJT-X only has a set up for RTTY Round Up and Field Day for contesting.


On 4/4/2019 17:45, Al - N1API wrote:
Is there any file for the FT8 DX Contest for N1MM?

Thanks

Al

Virus-free. www.avg.com