Date   
Re: Operating time

ve3ki
 

View > Off Times

That displays all of the relevant times: individual segments that qualify as off times longer than 30 minutes, total off time up to now (= cumulative contest off time), and total operating time.

If you have the Info window open, there is also a setting for the off time counter that displays cumulative contest off time. Operating time is the total time elapsed during the contest minus the cumulative contest off time.

During a contest View > Off Times is simpler if what you really want to know is the operating time, not the off time, because you do not have to do as much mental arithmetic. Using View > Off Times also allows you to configure the Info window's off time counter to do what it does best, namely to tell you whether the current time off has been long enough to qualify as an official off time or not.

73,
Rich VE3KI



On Mon, Dec 9, 2019 at 09:29 AM, john ni0k wrote:
How do I see the operating time from a contest?

-de John NI0K

Re: Operating time

Dwight Orten
 

Under view click on off times.
73
Dwight, KM4FO

On Mon, Dec 9, 2019 at 8:29 AM john ni0k <jasimmons@...> wrote:
How do I see the operating time from a contest?

-de John NI0K



Re: Operating time

Kenneth Grimm
 



On Mon, Dec 9, 2019 at 9:29 AM john ni0k <jasimmons@...> wrote:
How do I see the operating time from a contest?

On the log window, View, Off Times.  You will find the "on time" at the bottom of that window.

73,
Ken - K4XL

 

-de John NI0K





--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com

Operating time

john ni0k
 

How do I see the operating time from a contest?

-de John NI0K

Re: TS890 USB CW and PTT Operaton

Jim W7RY
 

See my comments below.

Thanks
73
Jim W7RY
On 12/8/2019 8:57 PM, ve3ki wrote:
There seem to be a lot of things mixed up here. Here is my attempt to unsnarl them:

First, if you have two radios, both using the Silicon Labs CP210x driver and with each radio supporting two COM ports, then there should be four Silicon Labs serial ports showing up in the Windows Device Manager, two for each radio. Each radio would have its own separate radio control port, that would have to be configured for that radio, and each radio would also have its own separate CW/PTT port created by the Silicon Labs driver.
There are indeed 4.


With other radios using a Silicon Labs driver, as I understand it the "standard" port is the one that is used for CW and PTT, and the "enhanced" port is the one that is used for radio control. I suspect that the problem you are having with PTT might be caused by having the ports reversed. On the other hand, perhaps Kenwood has chosen to reverse the terminology used by Icom and Yaesu -- but why would they do that?
Not sure. I'll look into this. The 890 is brand new to me. I have been using the IC7610. More research is needed on my end.

Regardless, the settings in the radio and in the Configurer need to match. On the port that is used for radio control with the Kenwood  radio, in the radio's menu DTR would be set to Off and RTS would be set to Handshake. TxD and RxD are used for radio control commands on this port. In the N1MM+ Configurer, for the same port the Radio would be set to Kenwood and the CW/Other check box would *not* be checked.
I see. But, I used only one com port for my IC7610, (and IC7300 for that matter, I used 7610 for radio 1 and 7300 for radio 2. But I only use SO2R in RTTY contests where I dont use CW. I use 2ea MORTTYs for FSK, one for each radio) and used DTR and RTS for PTT on the radio control port. Worked perfectly. But I understand, the Icom is not a Kenwood and may work differently.

DTR would be set to Always Off and RTS would be set to Handshake. If you have only one radio, or for the first radio in an SO2R setup, the Radio Nr would be 1. Radio Nr = 2 is used for the second radio in an SO2R setup.
Understand. I use SO2R often.. See above.

On a port (the other one, not the radio control port) that is used for direct keying from the computer to the radio (*not* through an SO2R controller), in the radio's menu DTR would be set to CW and RTS would be set to PTT. TxD and RxD are not used on this port. In the N1MM+ Configurer, for the same port the Radio would be set to *None* and the CW/Other check box would be checked. DTR would be set to CW and RTS would be set to PTT. The Radio Nr would be the same as for the radio control port. The Two Radio Protocol would be set to None on any port that is connected directly to a radio. If this is how you are doing CW and PTT keying, there would be four ports in the Configurer - one for radio control for each radio (with the Radio set corresponding to the radio type and with CW/Other unchecked), and a second one for CW/PTT for each radio (with the Radio set to None and the CW/Other check box checked).

If you have two radios, and if you are controlling CW and PTT through an SO2R controller, you would not use the CW/PTT ports in each radio. Instead, CW and PTT would be controlled by physical connections between the SO2R controller and the radios. While there would be five ports showing up in the Windows Device Manager (two for each radio plus a separate one for the SO2R controller), only three of them would appear in the N1MM+ Configurer, namely the radio control port for each radio plus the separate control port for the SO2R controller. The SO2R controller's port would have whatever settings are needed for it (Radio Nr = Both, Two Radio Protocol set according to the needs of the controller), but this has nothing to do with the ports created by the Silicon Labs driver for the two radios.
I have NO SO2R controller. See above.

My failure was using a single radio, the new Kenwood TS-890.
The IC7300 was not turned on, but it is active because of the way the USB works. If the USB cable is plugged into the 7300, and the power is supplied to the radio, (but the radio not turned on) it shows up in the device manager.

Thanks Rich, Ill do some more reading in the TS-890 manual and on line to see what is what on the ports.

73,
Rich VE3KI




Re: Telnet #n1mm

InMiami Ale
 

Hi Peter, I gave a tip to momentarily solve the problem, IN EUROPA AND OTHER COUNTRIES OF AMERICA AND SOUTH AMERICA THE NODI NC7J AND W9PA NOT FUNCTION MORE FROM SEVERAL DAYS AND THE solution That I DATO I SERVIVA ONLY TO FAR CONTINUE THE CONTEST DISSS THAT ERA ACTIVE IN THIS LAST WEEKEND. I also know that this is not a definitive solution, but since this weekend I had to finish the contest that I was doing to solve the problem momentarily I had to do a lot of checks on it and since only in the United States the nodes mentioned they worked and in the rest of the world there are problems don't you think something could have happened? The trivial thing that only with some logs the nodes function but only for a short time. Now we need to do a more severe analysis to understand until the extent to which the reasons for the malfunction in Europe of the nodes described above. I have already had a clear idea of the reasons and after 48 hours of analysis I already know where to intervene.

73 Ale

Re: Telnet #n1mm

Ed W2LCQ
 

Pete N4ZR,

From your message I gather you watch over the RBN. Please allow me to thank you for such a fantastic reliable service. In the middle of the night when no one is responding to my CQs and I’m beginning to doubt if anyone is hearing my 100 watt signals off the end of my 30 ft wire antenna the RBN assures me that I’m being heard by many stations around the world and at decent SNRs too. Keep up the fine work. Much appreciated. 

Best, Ed


Vy 73, Ed Jones W2LCQ

                   Frankford Radio Club
CWops 701 - SKCC 5474C - FISTS 12294

“My ear barely caught signals coming in regular succession which could not have been produced on earth.” —- Nicola Tesla




            






On Dec 8, 2019, at 11:04 PM, Pete Smith <n4zr@...> wrote:



Alex, please DON'T advise people to connect to the telnet.reverse beacon.net:server.  That server is designed for feeding "retail" DX clusters such as NC7J, W9PA, VE7CC and W3LPL, as well as literally hundreds of nodes across the world.  The reversebeacon feed is stripped down for speed, and has absolutely no filters, such as spot origin by zone, country  or state

I have no idea what you encountered, but I think it is fantasy to think that Microsoft somehow changed things at the DNS level.  In fact, all of the nodes you mentioned are operating as expected right now.  I believe that what you were seeing from W9PA is an inter-node protocol, and it should not surprise anyone that the Available window is not displaying spots from it - the format is all "wrong" for the user level.  I don't know how you got into that - perhaps an incorrect port number?

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 12/8/2019 4:51 PM, InMiami Ale wrote:
Good evening to all, in recent days there have been changes on telnet links with some nodes the most used during the contests especially with the nodes nc7j, and w9ap. after several investigations I came to the conclusion that Microsoft changed something at the DNS level in fact the nodes mentioned above seem to work only in the United States but in Europe and other countries of South America did not telnet connect but it was not possible to see the online stations. I consulted with several emails with some friends of the n1mm team and with friend Dave w9ap and therefore to solve the problem will be required an update to the cluster dx of n1mm. For the moment I solved it in this way, connecting telnet to a reverse beacom node which is what it takes to us when we make contests and also serves for daily dx. So who still has problems as I understand for example in countries of South America and Central America to connect telnet of n1mm to the following node: telnet.reversebeacon.net:7000

open the telnet list editor and add the new node, Cluster Name, Telnet, URL: telnet.reversebeacon.net:7000

73 Ale
<Cattura3.JPG>

The photo above attached to the w9pa node as you see the fields on the right window are not populated.
the photo below with the new node that is working well, and as you see all the fields are populated.


<Cattura9.JPG>

Re: Telnet #n1mm

Pete Smith
 

Alex, please DON'T advise people to connect to the telnet.reverse beacon.net:server.  That server is designed for feeding "retail" DX clusters such as NC7J, W9PA, VE7CC and W3LPL, as well as literally hundreds of nodes across the world.  The reversebeacon feed is stripped down for speed, and has absolutely no filters, such as spot origin by zone, country  or state

I have no idea what you encountered, but I think it is fantasy to think that Microsoft somehow changed things at the DNS level.  In fact, all of the nodes you mentioned are operating as expected right now.  I believe that what you were seeing from W9PA is an inter-node protocol, and it should not surprise anyone that the Available window is not displaying spots from it - the format is all "wrong" for the user level.  I don't know how you got into that - perhaps an incorrect port number?

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 12/8/2019 4:51 PM, InMiami Ale wrote:

Good evening to all, in recent days there have been changes on telnet links with some nodes the most used during the contests especially with the nodes nc7j, and w9ap. after several investigations I came to the conclusion that Microsoft changed something at the DNS level in fact the nodes mentioned above seem to work only in the United States but in Europe and other countries of South America did not telnet connect but it was not possible to see the online stations. I consulted with several emails with some friends of the n1mm team and with friend Dave w9ap and therefore to solve the problem will be required an update to the cluster dx of n1mm. For the moment I solved it in this way, connecting telnet to a reverse beacom node which is what it takes to us when we make contests and also serves for daily dx. So who still has problems as I understand for example in countries of South America and Central America to connect telnet of n1mm to the following node: telnet.reversebeacon.net:7000

open the telnet list editor and add the new node, Cluster Name, Telnet, URL: telnet.reversebeacon.net:7000

73 Ale
The photo above attached to the w9pa node as you see the fields on the right window are not populated.
the photo below with the new node that is working well, and as you see all the fields are populated.


Re: install folder error #solved

Pete Smith
 

Eliot. I am by no means an expert; it's been 7-8 years since I did user support.  You need to ask on the <N1mmLoggerplus@groups.io> reflector

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 12/8/2019 1:36 PM, Eliot Mayer, W1MJ via Groups.Io wrote:

Hi Pete N4ZR et al,

I tried your suggestion, but the error message did not change.  I finally found that the unwanted User Data path was "stuck" in the Windows Registry, and it looked like I fixed that problem.  But now N1MM+ is completely non-functional!  I put some screen shots of the error message and other details here:

www.w1mj.com/N1MM_Installation_Issue.pdf
Appreciate any help getting me up and running again.

73 DE W1MJ

Re: TS890 USB CW and PTT Operaton

ve3ki
 

There seem to be a lot of things mixed up here. Here is my attempt to unsnarl them:

First, if you have two radios, both using the Silicon Labs CP210x driver and with each radio supporting two COM ports, then there should be four Silicon Labs serial ports showing up in the Windows Device Manager, two for each radio. Each radio would have its own separate radio control port, that would have to be configured for that radio, and each radio would also have its own separate CW/PTT port created by the Silicon Labs driver.

With other radios using a Silicon Labs driver, as I understand it the "standard" port is the one that is used for CW and PTT, and the "enhanced" port is the one that is used for radio control. I suspect that the problem you are having with PTT might be caused by having the ports reversed. On the other hand, perhaps Kenwood has chosen to reverse the terminology used by Icom and Yaesu -- but why would they do that?

Regardless, the settings in the radio and in the Configurer need to match. On the port that is used for radio control with the Kenwood  radio, in the radio's menu DTR would be set to Off and RTS would be set to Handshake. TxD and RxD are used for radio control commands on this port. In the N1MM+ Configurer, for the same port the Radio would be set to Kenwood and the CW/Other check box would *not* be checked. DTR would be set to Always Off and RTS would be set to Handshake. If you have only one radio, or for the first radio in an SO2R setup, the Radio Nr would be 1. Radio Nr = 2 is used for the second radio in an SO2R setup.

On a port (the other one, not the radio control port) that is used for direct keying from the computer to the radio (*not* through an SO2R controller), in the radio's menu DTR would be set to CW and RTS would be set to PTT. TxD and RxD are not used on this port. In the N1MM+ Configurer, for the same port the Radio would be set to *None* and the CW/Other check box would be checked. DTR would be set to CW and RTS would be set to PTT. The Radio Nr would be the same as for the radio control port. The Two Radio Protocol would be set to None on any port that is connected directly to a radio. If this is how you are doing CW and PTT keying, there would be four ports in the Configurer - one for radio control for each radio (with the Radio set corresponding to the radio type and with CW/Other unchecked), and a second one for CW/PTT for each radio (with the Radio set to None and the CW/Other check box checked).

If you have two radios, and if you are controlling CW and PTT through an SO2R controller, you would not use the CW/PTT ports in each radio. Instead, CW and PTT would be controlled by physical connections between the SO2R controller and the radios. While there would be five ports showing up in the Windows Device Manager (two for each radio plus a separate one for the SO2R controller), only three of them would appear in the N1MM+ Configurer, namely the radio control port for each radio plus the separate control port for the SO2R controller. The SO2R controller's port would have whatever settings are needed for it (Radio Nr = Both, Two Radio Protocol set according to the needs of the controller), but this has nothing to do with the ports created by the Silicon Labs driver for the two radios.

73,
Rich VE3KI



Re: Thanks for WSJT in N1MM+

Andrew O'Brien
 

You solved the issue Rick!  I checked that box and works fine!
Andy K3UK

On Sun, Dec 8, 2019 at 8:25 PM Rick Ellison <rellison@...> wrote:

I do have one question for any one that the decode list was not clickable..

In WSJT-X on the Settings/Reporting tab In the Group box in the middle that says UDP Server do you have the box checked that says Accept UDP Requests??

If you do not have that box checked then the clicking in the decode list will be disabled. WSJT-X will block anything that N1MM tries to send to it..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Andrew O'Brien
Sent: Sunday, December 8, 2019 8:04 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Thanks for WSJT in N1MM+

 

Yes,  Rick.  Nothing happened when I clicked or double click on a call sign in the decoded list.  The list did tell me whether a station in the list was a mult or not, so still very useful.

Andy. 

 

On Sun, Dec 8, 2019 at 7:57 PM Rick Ellison <rellison@...> wrote:

Hi Andy..
"decode list was not clickable for shifting the N1MM focus but"

Do you mean shifting the entry window focus??

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Andrew O'Brien
Sent: Sunday, December 8, 2019 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Thanks for WSJT in N1MM+


Thanks to all those involved in the integration of WJSTX in N1MM+ . This
weekend was the first time I have used these features . It was a lot of fun
and worked well. The decode list was not clickable for shifting the N1MM
focus but was not really needed in my casual effort .
Andy K3UK.









--

Andy



--
Andy

Re: TS890 USB CW and PTT Operaton

Jim W7RY
 

I get the same error as below with the setup posted from the TS-890 group.

Any idea why I get this?


I was able to get it to work and stop the error, by taking PTT out of the USB port, and selecting PTT by radio command in CW. Anytime PTT was used on the radio port, or the virtual port, the error text would pop up.

Thanks
73
Jim W7RY
On 12/8/2019 7:27 PM, Jim W7RY via Groups.Io wrote:



I tried this setup from the TS-890 group and no joy either.

Thanks
73
Jim W7RY





Jim Vilbert
11/17/18   #630  

SUCCESS with connecting.  Here are the settings I am using to connect in CW and radio keying.

On the TS-890 - Advanced menu

17 - Stnd Com Port RTS = Flow Control
18 - Stnd Com Port DTS = Off
19 - Enhanced Com Port RTS = PTT
20 - Enhanced Com Port DTS = CW

My settings in N1MM

Com 23 (standard) generic Kenwood.  38,400, N, 8, 1. Radio 2
               Handshake.   Handshake
               PTT delay = 100. 2 radio protocol = None. Polling = Normal

Com 24 (Enhanced) for keying. DTR = CW. RTS = PTT
              PTT delay = 100. 2 radio protocol = MK2R

I am sure that there are others who know better than I how to make these connections.  My biggest issue was thinking that the Enhanced port was for rig control when it really is the Standard Port.  

Hope this helps with others trying to connect their new TS-890.

Jim
K3WU

On Sat, Dec 7, 2019 at 6:51 PM Jim W7RY <jimw7ry@...> wrote:
Trying to set  up my new TS890 for USB keying. I get this error shown below.


When I say ok to this window, the rig then transmits and sends the desired CW.

I have not loaded any Kenwood drivers. Just kept the Icom ones from my IC7610.



Ideas?
Thanks 73
Jim W7RY


image.png

N1MMLogger.net - Version 1.0.8018.0
Built: 11/26/2019 7:57:32 AM
Microsoft Windows NT 10.0.17763.0,64:1,en-US,en-US
Error occurred at: 12/7/2019 6:48:04 PM in Thread:
---------------------------------------------------------------------------------------
System.IO.IOException: A device attached to the system is not functioning.

   at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
   at System.IO.Ports.InternalResources.WinIOError()
   at System.IO.Ports.SerialStream.set_RtsEnable(Boolean value)
   at System.IO.Ports.SerialPort.set_RtsEnable(Boolean value)
   at N1MMLogger.Net.PortManager.udp_RTSEnable(Int32 PortNr, Boolean aBool) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\PortManager.vb:line 538
   at N1MMLogger.Net.UDPClass.RTSEnableEventHandler.Invoke(Int32 PortNr, Boolean aBool)
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 430
HRESULT = '8007001F'
---------------------------------------------------------------------------------------


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 N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 490
   at N1MMLogger.Net.UDPClass.DistributeXML(String aString) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 318
   at N1MMLogger.Net.CWIFInterfaceClass.SendXMLPortString(Int16& PortNr, String& groupname, String& p1name, String& p1value, String& p2name, String& p2value, String& p3name, String& p3value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\CWIFInterface.vb:line 463
   at N1MMLogger.Net.N1MMComm.set_RTSEnable(Boolean Value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMComm.vb:line 220
   at N1MMLogger.Net.N1MMPort.SetXmit(Boolean& aBoolean, PrinterPort& RadioControlPort, Boolean& IsSSBMode) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPort.vb:line 524
   at N1MMLogger.Net.N1MMPortManager.SetXmit(Boolean& aBoolean, Int16& aRadioNr, PrinterPort& RadioControlPort) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPortManager.vb:line 647
   at N1MMLogger.Net.RadioInterface.SetXmit(Boolean& aBoolean) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\RadioInterface.vb:line 6585
   at N1MMLogger.Net.StationClass.SetXmit(Boolean aBool, String FKeyCaption) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\Station.vb:line 1590
   at N1MMLogger.Net.EntryWindow.SendCW(String& aString, Int16& Index, String& msg) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2704
   at N1MMLogger.Net.EntryWindow.SendInfo2(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2387
   at N1MMLogger.Net.EntryWindow.SendInfo(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2069
   at N1MMLogger.Net.EntryWindow.EWSendBtn_OnClick(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 1613
   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 N1MMLogger.Net.My.MyApplication.Main(String[] Args) in :line 82

New TS-890 PTT and CW on USB Port

Jim W7RY
 

After I get the large error as posted below, when I click OK, the rig sends the CW that I did intended on sending from the CW message button. (I can hit the escape key on the keyboard and it stops sending).Then the error shows up again, and I click ok to get rid of it.

Ideas?


Thanks 73
Jim W7RY


On Sat, Dec 7, 2019 at 7:07 PM Jim W7RY <jimw7ry@...> wrote:
I tried this setup from the TS-890 group and no joy either.

Thanks
73
Jim W7RY





Jim Vilbert
11/17/18   #630  

SUCCESS with connecting.  Here are the settings I am using to connect in CW and radio keying.

On the TS-890 - Advanced menu

17 - Stnd Com Port RTS = Flow Control
18 - Stnd Com Port DTS = Off
19 - Enhanced Com Port RTS = PTT
20 - Enhanced Com Port DTS = CW

My settings in N1MM

Com 23 (standard) generic Kenwood.  38,400, N, 8, 1. Radio 2
               Handshake.   Handshake
               PTT delay = 100. 2 radio protocol = None. Polling = Normal

Com 24 (Enhanced) for keying. DTR = CW. RTS = PTT
              PTT delay = 100. 2 radio protocol = MK2R

I am sure that there are others who know better than I how to make these connections.  My biggest issue was thinking that the Enhanced port was for rig control when it really is the Standard Port.  

Hope this helps with others trying to connect their new TS-890.

Jim
K3WU

On Sat, Dec 7, 2019 at 6:51 PM Jim W7RY <jimw7ry@...> wrote:
Trying to set  up my new TS890 for USB keying. I get this error shown below.

When I say ok to this window, the rig then transmits and sends the desired CW.

I have not loaded any Kenwood drivers. Just kept the Icom ones from my IC7610.



Ideas?
Thanks 73
Jim W7RY


image.png

N1MMLogger.net - Version 1.0.8018.0
Built: 11/26/2019 7:57:32 AM
Microsoft Windows NT 10.0.17763.0,64:1,en-US,en-US
Error occurred at: 12/7/2019 6:48:04 PM in Thread:
---------------------------------------------------------------------------------------
System.IO.IOException: A device attached to the system is not functioning.

   at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
   at System.IO.Ports.InternalResources.WinIOError()
   at System.IO.Ports.SerialStream.set_RtsEnable(Boolean value)
   at System.IO.Ports.SerialPort.set_RtsEnable(Boolean value)
   at N1MMLogger.Net.PortManager.udp_RTSEnable(Int32 PortNr, Boolean aBool) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\PortManager.vb:line 538
   at N1MMLogger.Net.UDPClass.RTSEnableEventHandler.Invoke(Int32 PortNr, Boolean aBool)
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 430
HRESULT = '8007001F'
---------------------------------------------------------------------------------------


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 N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 490
   at N1MMLogger.Net.UDPClass.DistributeXML(String aString) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 318
   at N1MMLogger.Net.CWIFInterfaceClass.SendXMLPortString(Int16& PortNr, String& groupname, String& p1name, String& p1value, String& p2name, String& p2value, String& p3name, String& p3value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\CWIFInterface.vb:line 463
   at N1MMLogger.Net.N1MMComm.set_RTSEnable(Boolean Value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMComm.vb:line 220
   at N1MMLogger.Net.N1MMPort.SetXmit(Boolean& aBoolean, PrinterPort& RadioControlPort, Boolean& IsSSBMode) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPort.vb:line 524
   at N1MMLogger.Net.N1MMPortManager.SetXmit(Boolean& aBoolean, Int16& aRadioNr, PrinterPort& RadioControlPort) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPortManager.vb:line 647
   at N1MMLogger.Net.RadioInterface.SetXmit(Boolean& aBoolean) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\RadioInterface.vb:line 6585
   at N1MMLogger.Net.StationClass.SetXmit(Boolean aBool, String FKeyCaption) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\Station.vb:line 1590
   at N1MMLogger.Net.EntryWindow.SendCW(String& aString, Int16& Index, String& msg) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2704
   at N1MMLogger.Net.EntryWindow.SendInfo2(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2387
   at N1MMLogger.Net.EntryWindow.SendInfo(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2069
   at N1MMLogger.Net.EntryWindow.EWSendBtn_OnClick(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 1613
   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 N1MMLogger.Net.My.MyApplication.Main(String[] Args) in :line 82
-- 
Thanks
73
Jim W7RY

TS890 USB CW and PTT Operaton

Jim W7RY
 



I tried this setup from the TS-890 group and no joy either.

Thanks
73
Jim W7RY





Jim Vilbert
11/17/18   #630  

SUCCESS with connecting.  Here are the settings I am using to connect in CW and radio keying.

On the TS-890 - Advanced menu

17 - Stnd Com Port RTS = Flow Control
18 - Stnd Com Port DTS = Off
19 - Enhanced Com Port RTS = PTT
20 - Enhanced Com Port DTS = CW

My settings in N1MM

Com 23 (standard) generic Kenwood.  38,400, N, 8, 1. Radio 2
               Handshake.   Handshake
               PTT delay = 100. 2 radio protocol = None. Polling = Normal

Com 24 (Enhanced) for keying. DTR = CW. RTS = PTT
              PTT delay = 100. 2 radio protocol = MK2R

I am sure that there are others who know better than I how to make these connections.  My biggest issue was thinking that the Enhanced port was for rig control when it really is the Standard Port.  

Hope this helps with others trying to connect their new TS-890.

Jim
K3WU

On Sat, Dec 7, 2019 at 6:51 PM Jim W7RY <jimw7ry@...> wrote:
Trying to set  up my new TS890 for USB keying. I get this error shown below.


When I say ok to this window, the rig then transmits and sends the desired CW.

I have not loaded any Kenwood drivers. Just kept the Icom ones from my IC7610.



Ideas?
Thanks 73
Jim W7RY


image.png

N1MMLogger.net - Version 1.0.8018.0
Built: 11/26/2019 7:57:32 AM
Microsoft Windows NT 10.0.17763.0,64:1,en-US,en-US
Error occurred at: 12/7/2019 6:48:04 PM in Thread:
---------------------------------------------------------------------------------------
System.IO.IOException: A device attached to the system is not functioning.

   at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)
   at System.IO.Ports.InternalResources.WinIOError()
   at System.IO.Ports.SerialStream.set_RtsEnable(Boolean value)
   at System.IO.Ports.SerialPort.set_RtsEnable(Boolean value)
   at N1MMLogger.Net.PortManager.udp_RTSEnable(Int32 PortNr, Boolean aBool) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\PortManager.vb:line 538
   at N1MMLogger.Net.UDPClass.RTSEnableEventHandler.Invoke(Int32 PortNr, Boolean aBool)
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 430
HRESULT = '8007001F'
---------------------------------------------------------------------------------------


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 N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.UDPClass.HandleGenericMessage(XmlReader reader, String cmd) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 490
   at N1MMLogger.Net.UDPClass.DistributeXML(String aString) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\UDPClass.vb:line 318
   at N1MMLogger.Net.CWIFInterfaceClass.SendXMLPortString(Int16& PortNr, String& groupname, String& p1name, String& p1value, String& p2name, String& p2value, String& p3name, String& p3value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\CWIFInterface.vb:line 463
   at N1MMLogger.Net.N1MMComm.set_RTSEnable(Boolean Value) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMComm.vb:line 220
   at N1MMLogger.Net.N1MMPort.SetXmit(Boolean& aBoolean, PrinterPort& RadioControlPort, Boolean& IsSSBMode) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPort.vb:line 524
   at N1MMLogger.Net.N1MMPortManager.SetXmit(Boolean& aBoolean, Int16& aRadioNr, PrinterPort& RadioControlPort) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\N1MMPortManager.vb:line 647
   at N1MMLogger.Net.RadioInterface.SetXmit(Boolean& aBoolean) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\RadioInterface.vb:line 6585
   at N1MMLogger.Net.StationClass.SetXmit(Boolean aBool, String FKeyCaption) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\Station.vb:line 1590
   at N1MMLogger.Net.EntryWindow.SendCW(String& aString, Int16& Index, String& msg) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2704
   at N1MMLogger.Net.EntryWindow.SendInfo2(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2387
   at N1MMLogger.Net.EntryWindow.SendInfo(Int16& Index, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 2069
   at N1MMLogger.Net.EntryWindow.EWSendBtn_OnClick(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 1613
   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 N1MMLogger.Net.My.MyApplication.Main(String[] Args) in :line 82

Re: Thanks for WSJT in N1MM+

Rick Ellison
 

I do have one question for any one that the decode list was not clickable..

In WSJT-X on the Settings/Reporting tab In the Group box in the middle that says UDP Server do you have the box checked that says Accept UDP Requests??

If you do not have that box checked then the clicking in the decode list will be disabled. WSJT-X will block anything that N1MM tries to send to it..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Andrew O'Brien
Sent: Sunday, December 8, 2019 8:04 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Thanks for WSJT in N1MM+

 

Yes,  Rick.  Nothing happened when I clicked or double click on a call sign in the decoded list.  The list did tell me whether a station in the list was a mult or not, so still very useful.

Andy. 

 

On Sun, Dec 8, 2019 at 7:57 PM Rick Ellison <rellison@...> wrote:

Hi Andy..
"decode list was not clickable for shifting the N1MM focus but"

Do you mean shifting the entry window focus??

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Andrew O'Brien
Sent: Sunday, December 8, 2019 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Thanks for WSJT in N1MM+


Thanks to all those involved in the integration of WJSTX in N1MM+ . This
weekend was the first time I have used these features . It was a lot of fun
and worked well. The decode list was not clickable for shifting the N1MM
focus but was not really needed in my casual effort .
Andy K3UK.









--

Andy

Re: Thanks for WSJT in N1MM+

Rick Ellison
 

I will try to figure out why the decode click is not working correctly. For me it is working correctly. I have not updated to the newest WSJT-X yet so that might be a possibility as to the problem why I can’t duplicate it here..

The decode window was not meant to shift the Entry Window focus as you really do not need to do anything with the N1MM Entry window. While WSJT is open it covers my Entry window so I’m not distracted by it and want to type in it.

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Andrew O'Brien
Sent: Sunday, December 8, 2019 8:04 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Thanks for WSJT in N1MM+

 

Yes,  Rick.  Nothing happened when I clicked or double click on a call sign in the decoded list.  The list did tell me whether a station in the list was a mult or not, so still very useful.

Andy. 

 

On Sun, Dec 8, 2019 at 7:57 PM Rick Ellison <rellison@...> wrote:

Hi Andy..
"decode list was not clickable for shifting the N1MM focus but"

Do you mean shifting the entry window focus??

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Andrew O'Brien
Sent: Sunday, December 8, 2019 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Thanks for WSJT in N1MM+


Thanks to all those involved in the integration of WJSTX in N1MM+ . This
weekend was the first time I have used these features . It was a lot of fun
and worked well. The decode list was not clickable for shifting the N1MM
focus but was not really needed in my casual effort .
Andy K3UK.









--

Andy

Re: Thanks for WSJT in N1MM+

Andrew O'Brien
 

Yes,  Rick.  Nothing happened when I clicked or double click on a call sign in the decoded list.  The list did tell me whether a station in the list was a mult or not, so still very useful.
Andy. 

On Sun, Dec 8, 2019 at 7:57 PM Rick Ellison <rellison@...> wrote:
Hi Andy..
"decode list was not clickable for shifting the N1MM focus but"

Do you mean shifting the entry window focus??

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Andrew O'Brien
Sent: Sunday, December 8, 2019 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Thanks for WSJT in N1MM+


Thanks to all those involved in the integration of WJSTX in N1MM+ . This
weekend was the first time I have used these features . It was a lot of fun
and worked well. The decode list was not clickable for shifting the N1MM
focus but was not really needed in my casual effort .
Andy K3UK.










--
Andy

Re: Thanks for WSJT in N1MM+

Rick Ellison
 

Hi Andy..
"decode list was not clickable for shifting the N1MM focus but"

Do you mean shifting the entry window focus??

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Andrew O'Brien
Sent: Sunday, December 8, 2019 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Thanks for WSJT in N1MM+


Thanks to all those involved in the integration of WJSTX in N1MM+ . This
weekend was the first time I have used these features . It was a lot of fun
and worked well. The decode list was not clickable for shifting the N1MM
focus but was not really needed in my casual effort .
Andy K3UK.

Re: FT Roundup, A Learning Experience

Bob, W3IDT
 

Hesitate to say 'sorry abt three copies".
This may result in three copies, too.

.............................
. Robert F. Teitel, W3IDT .
. .
. W3IDT@... .
. W3IDT@... .
.............................

On 12/8/2019 7:38 PM, Bob, W3IDT wrote:
My notes, as sent to PVRC membership:
After many hours, I still don't quite understand how to operate FT4 and FT8 in HF contest conditions.
345 QSOs in the log, but many sequential duplicates, and some false positives. Only 40m and 20m; both FT4 and FT8, running and S&P.
1. Couldn't get N1MM+ and WSJT-x to play nice together.
So used just plain WSJT-x.
2. Hence have no clue re NET QSOs, nor Countries/States/Provinces.
Will have to figure out how to move log from WSJT-x to N1MM+
before 3830 entry and log submission.
3. When running,
a. don't know when to send RRR vs. RR73;
the latter logs the contact, but the other op may not get it, and we may never finish the contact.
b. scramble things badly when two callers, and really want the 2nd.
(either because it's much stronger; or about equal and a multiplier.)
Really same coordination problem, I think, as next item.
4, When trying S&P, my eye to brain and brain to hand coordination is too slow: By the time I double-click on a CQer, I'm almost always late, usually 1 or 2 seconds.
5. Couldn't figure out how to send something akin to
"TU; CQ RU W3IDT FM19" after a run contact as a number of ops were sending. Perhaps they were using JTDX (or whatever the other FTx program is called; does it play nice with N1MM+?)
Anyway, had "fun" trying.
Bob, w3idt
.............................
. Robert F. Teitel, W3IDT   .
.                           .
. W3IDT@...            .
. W3IDT@...         .
.............................
On 12/8/2019 8:11 AM, Andrew O'Brien wrote:
Thanks   , will check.

Andy


On Dec 8, 2019, at 7:49 AM, ve3ki <ve3iay@...> wrote:

What is the Mode Category in the contest setup window set to? If it is set to RTTY, the program will assign zero points to FTx QSOs. Change the RTTY to DIGITAL in the contest setup and then do a Tools > Rescore Current Contest.

73,
Rich VE3KI

On Sun, Dec 8, 2019 at 06:56 AM, Andrew O'Brien wrote:

    Same learning experience here.  I'm intrigued that N1MM+ is not
    scoring the contest .  Each of my QSOs has a value of zero points
    despite being listed as a SEC or a DXC.
    Andy K3UK

    On Sun, Dec 8, 2019 at 6:18 AM Mike K2MK <k2mk.mike@...
    <mailto:k2mk.mike@...>> wrote:

        [Edited Message Follows]

        I think this contest has been a learning experience for many
        of us. At the start of the contest, calling CQ resulted in
        many dupes calling me. I reviewed the WSJT online guide
        examples and realized that many people probably did not
        understand that only one person sends 73. After 73 is sent the
        contact is over. I too found it strange, especially on FT4
        that the full contact was completed so quickly followed by a
        loss of the Enable TX red indication. A few hours later the
        problem seemed to resolve itself. Hardly any dupes. I can only
        assume that everybody began to understand the 73 concept.

        It's also very nice to be able to switch back and forth
        between FT4 and FT8. It almost feels like switching bands as
        you find a new batch of potential contacts.

        I'm looking forward to the January VHF contest. FT8 on 6
        meters has, in the past, resulted in many dupes and some QSOs
        that never seemed to end. It was a good idea to have different
        frequencies for contest QSOs in the FT Roundup. I hope this
        idea is utilized for 6 meters in the VHF contest. I think many
        of the dupes, and the endless back-and-forth, may have been
        the result of mixing contest and non-contest operators.

        73,
        Mike K2MK



    --     Andy

Re: FT Roundup, A Learning Experience

Bob, W3IDT
 

My notes, as sent to PVRC membership:

After many hours, I still don't quite understand how to operate FT4 and FT8 in HF contest conditions.

345 QSOs in the log, but many sequential duplicates, and some false positives. Only 40m and 20m; both FT4 and FT8, running and S&P.

1. Couldn't get N1MM+ and WSJT-x to play nice together.
So used just plain WSJT-x.

2. Hence have no clue re NET QSOs, nor Countries/States/Provinces.
Will have to figure out how to move log from WSJT-x to N1MM+
before 3830 entry and log submission.

3. When running,
a. don't know when to send RRR vs. RR73;
the latter logs the contact, but the other op may not get it, and we may never finish the contact.
b. scramble things badly when two callers, and really want the 2nd.
(either because it's much stronger; or about equal and a multiplier.)
Really same coordination problem, I think, as next item.

4, When trying S&P, my eye to brain and brain to hand coordination is too slow: By the time I double-click on a CQer, I'm almost always late, usually 1 or 2 seconds.

5. Couldn't figure out how to send something akin to
"TU; CQ RU W3IDT FM19" after a run contact as a number of ops were sending. Perhaps they were using JTDX (or whatever the other FTx program is called; does it play nice with N1MM+?)

Anyway, had "fun" trying.

Bob, w3idt


.............................
. Robert F. Teitel, W3IDT .
. .
. W3IDT@... .
. W3IDT@... .
.............................

On 12/8/2019 8:11 AM, Andrew O'Brien wrote:
Thanks   , will check.
Andy

On Dec 8, 2019, at 7:49 AM, ve3ki <ve3iay@...> wrote:

What is the Mode Category in the contest setup window set to? If it is set to RTTY, the program will assign zero points to FTx QSOs. Change the RTTY to DIGITAL in the contest setup and then do a Tools > Rescore Current Contest.

73,
Rich VE3KI

On Sun, Dec 8, 2019 at 06:56 AM, Andrew O'Brien wrote:

Same learning experience here.  I'm intrigued that N1MM+ is not
scoring the contest .  Each of my QSOs has a value of zero points
despite being listed as a SEC or a DXC.
Andy K3UK

On Sun, Dec 8, 2019 at 6:18 AM Mike K2MK <k2mk.mike@...
<mailto:k2mk.mike@...>> wrote:

[Edited Message Follows]

I think this contest has been a learning experience for many
of us. At the start of the contest, calling CQ resulted in
many dupes calling me. I reviewed the WSJT online guide
examples and realized that many people probably did not
understand that only one person sends 73. After 73 is sent the
contact is over. I too found it strange, especially on FT4
that the full contact was completed so quickly followed by a
loss of the Enable TX red indication. A few hours later the
problem seemed to resolve itself. Hardly any dupes. I can only
assume that everybody began to understand the 73 concept.

It's also very nice to be able to switch back and forth
between FT4 and FT8. It almost feels like switching bands as
you find a new batch of potential contacts.

I'm looking forward to the January VHF contest. FT8 on 6
meters has, in the past, resulted in many dupes and some QSOs
that never seemed to end. It was a good idea to have different
frequencies for contest QSOs in the FT Roundup. I hope this
idea is utilized for 6 meters in the VHF contest. I think many
of the dupes, and the endless back-and-forth, may have been
the result of mixing contest and non-contest operators.

73,
Mike K2MK



--
Andy