[Dxspider-support] Adding ^mode^?

[Michael G. Carper]

One more quick thing.

 

Some programs are already stuffing QSX into the comment field.  Is there a
character limit for the comment field?

 

From: Michael G. Carper [mailto:mike at wa9pie.net] 
Sent: Wednesday, January 22, 2014 11:03 PM
To: 'The DXSpider Support list'
Subject: RE: [Dxspider-support] Adding ^mode^?

 

Let me ask a different question then.

 

On CC Cluster, there are currently 25 fields (whereas CC11 on DX Spider has
20).  The 21st field is unused on CC Cluster. though all 25 are propagated.
Is there anything that prevents someone from using the unused 21st field for
any purpose?

 

Or. what I could do. is just change the code in HRD to automatically
populate mode in the comment field like this ^MODE: Comment^ and we'll
always parse the comment field for ^MODE: to get mode.  In that case, I
suppose it would only benefit 20,000 HRD users. I was hoping for something
more universally beneficial.

 

Mike

 

From: dxspider-support-bounces at dxcluster.org
[mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Lee Sawkins
Sent: Wednesday, January 22, 2014 4:09 PM
To: The DXSpider Support list
Subject: Re: [Dxspider-support] Adding ^mode^?

 

Mike, FYI the CC11 data is not exchanged between cluster nodes.  Cluster
nodes exchange PC11/PC61 data, which contains a bare minimum of information.

 

I am against having a separate ^mode^ field.  Having the mode in the
comments allows this data to easily pass through all existing cluster nodes.
It is easy to detect and add mode to the comments field.  It is best if it
is the first word, but even if not, it still is easy to find.

 

With a separate PC11/PC61 ^mode^ field, this field would be dropped by all
nodes that do not support ^mode^.  So even if the originating node included
^mode^ and other nodes could use this data, it is possible that the ^mode^
could be dropped before it got to all of them.  

 

The CC11 data is currently sent in only one direction.  From the cluster
node to the user.  It does not support user to cluster.  This can of course
be fixed, but requires software changes.  These changes always end up being
more difficult than they first appear. 

 

Lee

 

---- Original Message ----- 

From: Michael Carper <mailto:mike at wa9pie.net>  

To: maudeij at gmail.com ; The DXSpider Support list
<mailto:dxspider-support at dxcluster.org>  

Sent: Wednesday, January 22, 2014 8:25 AM

Subject: Re: [Dxspider-support] Adding ^mode^?

 

We'll know the mode in the same way (in general) that we know the frequency.
We'll read the mode from the software that the user is using to submit the
spot. 

 

No one really spots manually anymore (I'm not sure I can remember the syntax
for it).  Most of our users have never seen the telnet console (even though
it's in a dropdown).

 

But when they're spotting a station, we grab the call and frequency from the
UI (where frequency is either read from the radio or entered by the user)...
and the comment field (which the user gets in a dialog box).

 

I'm simply suggesting that we offer up Field 21 for the purpose of mode.
In this case, we'll do exactly the same thing there that we do with other
fields... we'll read the mode from the UI and send it in Field 21.  If the
field is blank, we'll pretty much ignore it... as we do the comment field.


This would be a dramatic improvement.

 

This doesn't prevent folks from putting it in the comment field... if that's
what they're doing now.  But that approach is rather inconsistently
utilized... certainly not universal.

 

Mike, WA9PIE


 

 

  _____  


 <http://www.avast.com/> 

This email is free from viruses and malware because avast! Antivirus
<http://www.avast.com/>  protection is active. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20140122/7426fc5c/attachment.html>