Date   
Re: CWT Tip of the Day

Ed W2LCQ
 

Wow that’s a huge tip. Thanks a lot Art!

Ed

73, Ed Jones W2LCQ 

                          Frankford Radio Club
CWops 701 - SKCC 5474T - FISTS 12294 - LICWC
                        

  

On Apr 1, 2020, at 7:25 PM, ART W2NRA <w2nra2@...> wrote:

Hi Ed,

In the Telnet window select Filter tab and check Call History over on the right side, 2nd line I think (my memory?).  Keep your Call History file current and you’ll be in business.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 7:13 PM, Ed W2LCQ via groups.io <w2lcq@...> wrote:

Hi Art,

What is the CHF Telnet filter? I use the CHF but not as a Telnet filter. I use NC7J but I do not see CWT spots on my AW, Band map or Spectrum Display. The only spots I see are stations I’ve worked or EW calls that have been wiped. Thanks a lot. 

Best, Ed

73, Ed Jones W2LCQ 

Frankford Radio Club
CWops 701 - SKCC 5474T - FISTS 12294 - LICWC
                        

  

On Apr 1, 2020, at 5:45 PM, ART W2NRA <w2nra2@...> wrote:

In the 1900z CWT I did use N1MM Logger+'s Call-History file Telnet filter.  The best part of that was it doesn't post busted callsigns.  I don't have the problem of not being able to find Ops who are not in the Call-History file because I'm using dual vertical Spectrum Displays, one for each VFO, in place of the Bandmaps and I easily see those Ops as Spectrum spikes. Cool!

FYI  I had my highest score ever in the 1900z CWOPS CWT.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 11:54 AM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

No

On 4/1/2020 11:52 AM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?

Dave K1ZZ




On Wednesday, April 1, 2020, 11:23:34 AM EDT, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:


No.  The call history file is updated *very* frequently. Newbies don't
CQ much, and they would not see that they were missing from others'
bandmaps.

It helps them more than anyone, if they use it. It takes them longer to
determine a CQing station is not in the CWT.

Tom - N1MM

On 4/1/2020 10:40 AM, Dave Sumner wrote:
Seems like a fine way to discourage new participants.

Dave K1ZZ


On Wednesday, April 1, 2020, 10:22:05 AM EDT, Doug, VE3MV
<dougve3mv@... <mailto:dougve3mv@...>> wrote:


GM Tom and many thanks for this update.  The really nice part of the
new feature is that all of the many permutations of the proper call
from the CH file are no longer in the band map - wonderful.

Tnx & 73

Doug  VE3MV
CWops #1642

On 2020-Apr-01, at 7:19 AM, Tom - N1MM <Tom@... <mailto:Tom@...>
<mailto:Tom@... <mailto:Tom@...>>> wrote:

You can limit callsigns in the bandmap/spectrum/available windows to
only those that are in call history.

Since in CWT virtually everyone who operates it is in CH, this will
limit the displays to those who are likely operating in the event.
Those who try the option, like it. Because this can be a very
confusing option if you don't know it is turned on, it is NOT saved
on exit. You will need to check it each time you want to use it.

See the attached screen shot for where in the Telnet window to enable
this behavior.

73,
Tom - N1MM <Annotation 2020-04-01 071455.png>











Re: CWT Tip of the Day

ART W2NRA
 

Hi Ed,

In the Telnet window select Filter tab and check Call History over on the right side, 2nd line I think (my memory?).  Keep your Call History file current and you’ll be in business.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 7:13 PM, Ed W2LCQ via groups.io <w2lcq@...> wrote:

Hi Art,

What is the CHF Telnet filter? I use the CHF but not as a Telnet filter. I use NC7J but I do not see CWT spots on my AW, Band map or Spectrum Display. The only spots I see are stations I’ve worked or EW calls that have been wiped. Thanks a lot. 

Best, Ed

73, Ed Jones W2LCQ 

Frankford Radio Club
CWops 701 - SKCC 5474T - FISTS 12294 - LICWC
                        

  

On Apr 1, 2020, at 5:45 PM, ART W2NRA <w2nra2@...> wrote:

In the 1900z CWT I did use N1MM Logger+'s Call-History file Telnet filter.  The best part of that was it doesn't post busted callsigns.  I don't have the problem of not being able to find Ops who are not in the Call-History file because I'm using dual vertical Spectrum Displays, one for each VFO, in place of the Bandmaps and I easily see those Ops as Spectrum spikes. Cool!

FYI  I had my highest score ever in the 1900z CWOPS CWT.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 11:54 AM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

No

On 4/1/2020 11:52 AM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?

Dave K1ZZ




On Wednesday, April 1, 2020, 11:23:34 AM EDT, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:


No.  The call history file is updated *very* frequently. Newbies don't
CQ much, and they would not see that they were missing from others'
bandmaps.

It helps them more than anyone, if they use it. It takes them longer to
determine a CQing station is not in the CWT.

Tom - N1MM

On 4/1/2020 10:40 AM, Dave Sumner wrote:
Seems like a fine way to discourage new participants.

Dave K1ZZ


On Wednesday, April 1, 2020, 10:22:05 AM EDT, Doug, VE3MV
<dougve3mv@... <mailto:dougve3mv@...>> wrote:


GM Tom and many thanks for this update.  The really nice part of the
new feature is that all of the many permutations of the proper call
from the CH file are no longer in the band map - wonderful.

Tnx & 73

Doug  VE3MV
CWops #1642

On 2020-Apr-01, at 7:19 AM, Tom - N1MM <Tom@... <mailto:Tom@...>
<mailto:Tom@... <mailto:Tom@...>>> wrote:

You can limit callsigns in the bandmap/spectrum/available windows to
only those that are in call history.

Since in CWT virtually everyone who operates it is in CH, this will
limit the displays to those who are likely operating in the event.
Those who try the option, like it. Because this can be a very
confusing option if you don't know it is turned on, it is NOT saved
on exit. You will need to check it each time you want to use it.

See the attached screen shot for where in the Telnet window to enable
this behavior.

73,
Tom - N1MM <Annotation 2020-04-01 071455.png>











Re: CWT Tip of the Day

Ed W2LCQ
 

Hi Art,

What is the CHF Telnet filter? I use the CHF but not as a Telnet filter. I use NC7J but I do not see CWT spots on my AW, Band map or Spectrum Display. The only spots I see are stations I’ve worked or EW calls that have been wiped. Thanks a lot. 

Best, Ed

73, Ed Jones W2LCQ 

Frankford Radio Club
CWops 701 - SKCC 5474T - FISTS 12294 - LICWC
                        

  

On Apr 1, 2020, at 5:45 PM, ART W2NRA <w2nra2@...> wrote:

In the 1900z CWT I did use N1MM Logger+'s Call-History file Telnet filter.  The best part of that was it doesn't post busted callsigns.  I don't have the problem of not being able to find Ops who are not in the Call-History file because I'm using dual vertical Spectrum Displays, one for each VFO, in place of the Bandmaps and I easily see those Ops as Spectrum spikes. Cool!

FYI  I had my highest score ever in the 1900z CWOPS CWT.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 11:54 AM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

No

On 4/1/2020 11:52 AM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?

Dave K1ZZ




On Wednesday, April 1, 2020, 11:23:34 AM EDT, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:


No.  The call history file is updated *very* frequently. Newbies don't
CQ much, and they would not see that they were missing from others'
bandmaps.

It helps them more than anyone, if they use it. It takes them longer to
determine a CQing station is not in the CWT.

Tom - N1MM

On 4/1/2020 10:40 AM, Dave Sumner wrote:
Seems like a fine way to discourage new participants.

Dave K1ZZ


On Wednesday, April 1, 2020, 10:22:05 AM EDT, Doug, VE3MV
<dougve3mv@... <mailto:dougve3mv@...>> wrote:


GM Tom and many thanks for this update.  The really nice part of the
new feature is that all of the many permutations of the proper call
from the CH file are no longer in the band map - wonderful.

Tnx & 73

Doug  VE3MV
CWops #1642

On 2020-Apr-01, at 7:19 AM, Tom - N1MM <Tom@... <mailto:Tom@...>
<mailto:Tom@... <mailto:Tom@...>>> wrote:

You can limit callsigns in the bandmap/spectrum/available windows to
only those that are in call history.

Since in CWT virtually everyone who operates it is in CH, this will
limit the displays to those who are likely operating in the event.
Those who try the option, like it. Because this can be a very
confusing option if you don't know it is turned on, it is NOT saved
on exit. You will need to check it each time you want to use it.

See the attached screen shot for where in the Telnet window to enable
this behavior.

73,
Tom - N1MM <Annotation 2020-04-01 071455.png>











Re: More info....please !

Jim W7RY
 

One more suggestion.

REPLY with ALL of the text of the email chain. These 3 word emails with no context, just contribute to the noise!


Thanks
73
Jim W7RY
On 4/1/2020 9:40 AM, Steve London wrote:

Folks,

Recently, there have been a few postings like these:

- I installed the program and it isn't working right.  What's up with that?
- Installing the latest full installer of N1MM Logger + into my PC followed by the latest update produces that same run time error continually.

It's great that more folks are using N1MM+, but these kind of postings do not provide the development team or the 6000+ readers with any useful information to help you.

A few tips:

1) Include your callsign in all postings. The development team will not respond to anonymous requests.

2) Attach a screenshot or file showing any real time errors or other anomalies.

3) A complete description of what you did, just prior to the error occurring.

73,
Steve, N2IC







Re: CWT Tip of the Day

ART W2NRA
 

In the 1900z CWT I did use N1MM Logger+'s Call-History file Telnet filter. The best part of that was it doesn't post busted callsigns. I don't have the problem of not being able to find Ops who are not in the Call-History file because I'm using dual vertical Spectrum Displays, one for each VFO, in place of the Bandmaps and I easily see those Ops as Spectrum spikes. Cool!

FYI I had my highest score ever in the 1900z CWOPS CWT.

73, Art W2NRA
CWOPS #1955

On Apr 1, 2020, at 11:54 AM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

No

On 4/1/2020 11:52 AM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?

Dave K1ZZ




On Wednesday, April 1, 2020, 11:23:34 AM EDT, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:


No. The call history file is updated *very* frequently. Newbies don't
CQ much, and they would not see that they were missing from others'
bandmaps.

It helps them more than anyone, if they use it. It takes them longer to
determine a CQing station is not in the CWT.

Tom - N1MM

On 4/1/2020 10:40 AM, Dave Sumner wrote:
Seems like a fine way to discourage new participants.

Dave K1ZZ


On Wednesday, April 1, 2020, 10:22:05 AM EDT, Doug, VE3MV
<dougve3mv@... <mailto:dougve3mv@...>> wrote:


GM Tom and many thanks for this update. The really nice part of the
new feature is that all of the many permutations of the proper call
from the CH file are no longer in the band map - wonderful.

Tnx & 73

Doug VE3MV
CWops #1642

On 2020-Apr-01, at 7:19 AM, Tom - N1MM <Tom@... <mailto:Tom@...>
<mailto:Tom@... <mailto:Tom@...>>> wrote:

You can limit callsigns in the bandmap/spectrum/available windows to
only those that are in call history.

Since in CWT virtually everyone who operates it is in CH, this will
limit the displays to those who are likely operating in the event.
Those who try the option, like it. Because this can be a very
confusing option if you don't know it is turned on, it is NOT saved
on exit. You will need to check it each time you want to use it.

See the attached screen shot for where in the Telnet window to enable
this behavior.

73,
Tom - N1MM <Annotation 2020-04-01 071455.png>


Spectrum window runtime error

Gregg Marco W6IZT
 

N1MMLogger.net - Version 1.0.8280.0

Built: 3/31/2020 12:39:22

Microsoft Windows NT 10.0.18363.0,64:1,en-US,en-US

Error occurred at: 4/1/2020 20:50:23 in Thread: Spectrum UI Thread - 628a1639-274a-498c-b779-c746ee31ce77

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

System.ApplicationException: Device got disconnected

   at N1MMLogger.Net.SDRSharp.FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166

   at N1MMLogger.Net.SpectrumWindow.SpyConnect() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4250

   at N1MMLogger.Net.SpectrumWindow.ConnectSpy() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4227

   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1327

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

 

 

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:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Library\Classes\SharedCode.vb:line 89

   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\SharedCode.vb:line 186

   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1374

   at N1MMLogger.Net.SpectrumWindow.SpectrumWindow_Load(Object sender, EventArgs e) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 123

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.OnCreateControl()

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WmShowWindow(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at N1MMLogger.Net.SpectrumWindow.WndProc(Message& m) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4402

   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.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)

   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)

   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)

   at System.Windows.Forms.Control.set_Visible(Boolean value)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.Run(Form mainForm)

   at N1MMLogger.Net.N1MMLoggerCommon.StartSpectrumWindow(Object aGuid) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\N1MMLoggerCommon.vb:line 11673

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart(Object obj)

Re: Grab M&Q for second radio

DanM
 

I will try a suggestion :)
ALT + A                  - radio 1 down
SHIFT + ALT + A   - radio 1 up
--------------------------
CTRL + ALT + A                - radio 2 down
CTRL + SHIFT + ALT + A  - radio 2 up
or
ALT + C
SHIFT + ALT + C

Re: SWL

Thieu Mandos
 

Dear SWL's 

Ive made a UDC for the SPDX contest to make it easy for SWL and enjoy all nice features of N1MMlogger.
It makes an extra entry field avalable for 2nd call/station worked, checks the exchange, offers a master file to suggest the stions heard,
and offers exchange suggestion from a history file (copied from the SPDX contest)
All is in a zip file, probably I'm too late to put it in the N1MM document download or files section here,
so mail me for a copy at NL199@... 
I hope this way to get a few beginning Hams active in contesting, advice: try it before the contest starts :)
success Thieu, NL199, PA0M

Re: Broadcast spot info

DanM
 

Thank you Peter for the suggestion and for the AR filters. I do have an AR cluster and I can use it between SDC Skimmer and N1MM. I will give it a try. Thank you !

73,
Dan, yo3irm

Re: Broadcast spot info

DanM
 

Hi Steve, thank you for your answer. I've talked to Yuri and he agreed to implement Blacklist based on the new XML UDP message.
Waiting for more details from you on the next N1MM versions. Thank you !
73,
Dan, yo3irm

Re: Error checking for new version

ve3ki
 

On your laptop, go to the N1MM Logger+ web site, find the update program for version 1.0.8280.0, download it onto your computer, and then run it to update the Logger on that computer to the current version.

73,
Rich VE3KI


On Wed, Apr 1, 2020 at 02:13 PM, Carol Szabo wrote:
Sorry, if the problem was already discussed, I am new member of this Group.
Trying to interconnect two computers with N1MM Logger+ on the same LAN, I installed the latest N1MM Logger + FullInstaller 1.0.7711.0 to my laptop. It is running OK, But I can not obtain the same version of the software on both computers, because on the day by day used computer I have Ver. 1.0.8280.0 (updated these days) and the recently installed laptop can not updates, giving the window: 
"Error checking for new version of the program" and the message 
"The requested security protocol is not supported."
On this laptop I have Vista.
What can I do, without reinstalling a newer Windows?
Thanks 
Carol - YO3RU
 

Error checking for new version

Carol Szabo
 

Sorry, if the problem was already discussed, I am new member of this Group.
Trying to interconnect two computers with N1MM Logger+ on the same LAN, I installed the latest N1MM Logger + FullInstaller 1.0.7711.0 to my laptop. It is running OK, But I can not obtain the same version of the software on both computers, because on the day by day used computer I have Ver. 1.0.8280.0 (updated these days) and the recently installed laptop can not updates, giving the window: 
"Error checking for new version of the program" and the message 
"The requested security protocol is not supported."
On this laptop I have Vista.
What can I do, without reinstalling a newer Windows?
Thanks 
Carol - YO3RU

Re: More info....please !

Ken - K4XL
 

I assumed that the post by N1MM that said "I installed the program and it isn't working right.  What's up with that?" was a question for this annual special day!
73,
Ken - K4XL

On Wed, Apr 1, 2020 at 10:40 AM Steve London <n2ic@...> wrote:
Folks,

Recently, there have been a few postings like these:

- I installed the program and it isn't working right.  What's up with that?
- Installing the latest full installer of N1MM Logger + into my PC followed by
the latest update produces that same run time error continually.

It's great that more folks are using N1MM+, but these kind of postings do not
provide the development team or the 6000+ readers with any useful information to
help you.

A few tips:

1) Include your callsign in all postings. The development team will not respond
to anonymous requests.

2) Attach a screenshot or file showing any real time errors or other anomalies.

3) A complete description of what you did, just prior to the error occurring.

73,
Steve, N2IC








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

Re: band button in entry window, fixed

gksmith_1
 

John,

Thank you.

73 de WA3ZSC - Jerry

Re: Broadcast spot info

Peter Krüger
 

Well - using a AR - Cluster using the CT1BOH filter routine should help a lot.

It deletes "Busted" calls and do a quality check for spots and reduces such bad spots a real lot.

Connect to a AR Cluster and do:
set dx ext skimmerquality
Activate the CT1BOH algorythm
set dx filter not skimdupe and not skimbusted and not skimqsy
Filter the busted calls from being reported

A real good extended one is
set dx filter not skimdupe and not skimbusted and not skimqsy and not skimunknown and spottercont=eu and mode=cw and comment<>*beacon* and comment<>*ncdxf* and (band=160 or band=80 or band=40 or band=20 or band=15 or band=10)

I believe, this will help you a lot - but of course I now understand why you may need such new way of UDP traffic.


--
---
N1mm+Toolbox -> see at  https://df1lx.darc.de
---

Adding a Second Airspy HF+ - All the way there.

Tony Gasperino
 

 

 

Followimg N1MM’s suggestions and the Manual’s Spectrum Display section, I was able to activate two Displays using two Airspy HF+ SDRs attached to two TS590s, respectively. The source for the Display on Radio-1 was I/Q via ExtIO.dll and for Radio-2 was Airspy HF+ running spyserver from a separate folder.

 

Thanks N1MM and all the crew.

 

Tony, WS7V

Re: CWT Tip of the Day

VE9AA - Mike
 

P.S.-Not to mention, not everyone is assisted, nor using N1MMLogger Plus, or possibly any logging software at all ! ( I use paper/pencil in the Mini or when parked using my Harley.) I know others operate this way as well at times. K9MA/bicycle mobile comes to mind.

I think a lot will benefit from this option.  I don't envision too many real CWTers being locked out.

Mike VE9AA


On Wed, Apr 1, 2020 at 12:52 PM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?
 
Dave K1ZZ

 
--
Mike VE9AA

Re: Broadcast spot info

Steve London
 

As the developer on the N1MM+ team who implemented the spot broadcast, I have a few comments and questions.

The spot broadcast has many external users. A change to the purpose of an existing XML message will require changes by all external users. Not going to do that.

Would it work for UT4LW SDC if an additional XML message was sent if a call was blacklisted ? The delete XML message would also be sent.

Can you get a commitment from UT4LW that he will make changes to use this ?

73,
Steve, N2IC

On 04/01/2020 08:06 AM, DanM wrote:
I'm using a SunSDR2PRO transceiver. The SDR software (ExpertSDR2) can display spots on screen, see an example below.
There is a beautiful piece of software (SDC - Software Defined Connector written by Yuri, ut4lw)  that can act as a skimmer, among other features, and can also change the displayed spots color based on feedback from N1MM.
During  a contest, you can find bad spots on the N1MM bandmap, You have the solution to delete them but they will appear again if those spots were reported again by the cluster, or you can add them to the Blacklist, in this case those spots will not be displayed again on the N1MM bandmap.
SDC_Skm3.jpg
Now, the problem is that both N1MM operations, "Remove Selected Spot" and Blacklist a spot although have different behavior/result they will broadcast the same message <action>delete</action>.
You cannot take an action based on this message because you don't know if the user wanted to Blacklist that callsign or just deleted that spot or spots to clear the Bandmap for example. As Blacklist a spot has a different result (spot deleted and blocked to be displayed again) I would expect a different message like <action>Blacklisted</action> for example.
Having a different message, SDC can intercept that action, delete the spot from screen and prevent skimmer to send that spot again.
Thanks

Re: CWT Tip of the Day

VE9AA - Mike
 

Call me old school, but I often "spin the big knob" to get the most out of a band or to catch someone before they're spotted. Maybe their keying isn't perfect?
Once you've done a few CWT's Claudes CH file will include you.

Either way, I see the advantage and it's a good way to exclude the normal WEEKDAY daytime non-contesting ops  who won't know what hit them on their CQ when a bunch of CWTers call them at normally above avg speeds.

Good job Tom!

Mike VE9AA

On Wed, Apr 1, 2020 at 12:52 PM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?
 
Dave K1ZZ

 
--
Mike VE9AA

Re: CWT Tip of the Day

Tom Wagner (N1MM)
 

No

On 4/1/2020 11:52 AM, Dave Sumner wrote:
So if no one answers their CQs but they don't know why, they won't be discouraged?

Dave K1ZZ




On Wednesday, April 1, 2020, 11:23:34 AM EDT, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:


No.  The call history file is updated *very* frequently. Newbies don't
CQ much, and they would not see that they were missing from others'
bandmaps.

It helps them more than anyone, if they use it. It takes them longer to
determine a CQing station is not in the CWT.

Tom - N1MM

On 4/1/2020 10:40 AM, Dave Sumner wrote:
Seems like a fine way to discourage new participants.

Dave K1ZZ


On Wednesday, April 1, 2020, 10:22:05 AM EDT, Doug, VE3MV
<dougve3mv@... <mailto:dougve3mv@...>> wrote:


GM Tom and many thanks for this update.  The really nice part of the
new feature is that all of the many permutations of the proper call
from the CH file are no longer in the band map - wonderful.

Tnx & 73

Doug  VE3MV
CWops #1642

On 2020-Apr-01, at 7:19 AM, Tom - N1MM <Tom@...
<mailto:Tom@...>
<mailto:Tom@... <mailto:Tom@...>>> wrote:

You can limit callsigns in the bandmap/spectrum/available windows to
only those that are in call history.

Since in CWT virtually everyone who operates it is in CH, this will
limit the displays to those who are likely operating in the event.
Those who try the option, like it. Because this can be a very
confusing option if you don't know it is turned on, it is NOT saved
on exit. You will need to check it each time you want to use it.

See the attached screen shot for where in the Telnet window to enable
this behavior.

73,
Tom - N1MM <Annotation 2020-04-01 071455.png>