Date   
Re: Use of operator callsign

Don Poaps
 

Tactical address. Base call = call sign used under the Tatical address shelter 1

Don va7dgp 


On Thu, May 3, 2018 at 21:50 James Stafford AJ5BS <aj5bs@...> wrote:
Ed, Tactical Callsigns are call signs used during an event to designate a place or position. They are used during an event so that other operators do not have to remember the call sign of the operator manning the station, such as EOC during an emergency situation where the EOC operator may change every 2 - 4 hours. Or, Shelter 1 during an emergency where there are multiple shelters in operation. 
 
James B Stafford


On Thursday, May 3, 2018 11:40 PM, Ed W3NR <autek@...> wrote:


On Fri, 4 May 2018 04:30:58 +0000 (UTC)
"James Stafford AJ5BS" <aj5bs@...> wrote:

> Ed, Randy was talking about when messages are sent during an activity
> where Tactical Callsigns are used vice an Operator's Callsign are
> used when sending messages.  James B Stafford

I have no idea what a "tactical callsign " is or is it for some covert
operation ? Unless the FCC has changed there is no such thing as an
operator callsign, just a station callsign. Maybe after 40 years I'm
behind times.

Ed W3NR




--
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU   VOICE


Winlink: va7qu@...
Subject://wl2k           



                    
  




 

Re: Use of operator callsign

Randy
 

My question was not what the call sign fields are but rather this.  Why is the operator call sign which for all intent is the real station call sign and the one required for ID not appended to the end of the transmission by default?  There is nothing in the flmsg transmission that legally identifies the station.  The operator call sign required by the FCC is not even available to build an ID macro in fldigi.  The operator call sign only exists as a configuration item not linked to anything.

Randy


On Thu, May 3, 2018 at 08:32 pm, Randy wrote:
Fldigi configuration includes a station call sign and an operator call sign.  I have not seen anywhere that the operator call sign is transmitted and I do not find it available as a macro field.  Shouldn't the operator call sign be transmitted for ID when a tactical station call sign is used?  Should the operator call sign be available for custom macro definition? 

When using flmsg only the flmsg configured call sign is used and may not correspond to the operator tasked to transmit.  Am I incorrect to say transmissions should include the correct operator call sign at the end?

Randy

Re: Use of operator callsign

Al Massaro
 

Tactical Call Signs

Topic 12: FCC Rules on Emergency Communications

Tactical call signs are often adopted during an emergency, or during large public-service activities. Names like “Med Tent,” “Fire 1,” “Shelter 2,” and “Red Cross Staging” quickly identifies each function or location, and eliminates confusion when working with other agencies for which Amateur call signs are meaningless. They also help prevent confusion when several operators may take turns at a position.

 

The use of tactical call signs is a good idea, but it in no way relieves you of the obligation to identify your station under the FCC’s Rules for normal station identification. You must still give your FCC-assigned call sign at the end of your communication, and at least every 10 minutes during the contact [97.119]. This doesn’t mean that every ten-minutes everyone has to give their callsign – in an emergency net operation where tactical calls are being used, if it has been more than ten minutes since you last legally identified your station, you simply need to do so the next time you transmit.
IMHO, adding your call to the end of the message satisfies this requirement, and voice ID every ten satisfies the rest.

Re: Use of operator callsign

Dave
 

24 operators participate in a multi-operator / multi-transmitter field day entry.  The callsign used for ID is the station callsign ... not each operator callsign.  The same goes for special event station, operating a club, or a friends station. 

73, David, W1HKJ

P.S.  what is your call sign Randy?

On 05/07/2018 08:24 AM, Randy wrote:
My question was not what the call sign fields are but rather this.  Why is the operator call sign which for all intent is the real station call sign and the one required for ID not appended to the end of the transmission by default?  There is nothing in the flmsg transmission that legally identifies the station.  The operator call sign required by the FCC is not even available to build an ID macro in fldigi.  The operator call sign only exists as a configuration item not linked to anything.

Randy


On Thu, May 3, 2018 at 08:32 pm, Randy wrote:
Fldigi configuration includes a station call sign and an operator call sign.  I have not seen anywhere that the operator call sign is transmitted and I do not find it available as a macro field.  Shouldn't the operator call sign be transmitted for ID when a tactical station call sign is used?  Should the operator call sign be available for custom macro definition? 

When using flmsg only the flmsg configured call sign is used and may not correspond to the operator tasked to transmit.  Am I incorrect to say transmissions should include the correct operator call sign at the end?

Randy

Re: Use of operator callsign

Randy
 

KG5KZF is my call sign.  The difference I see is that a club or event is a real, coordinated call sign but if we use HOSP1, SHELTER NORTH or some other handy local descriptive call sign we technically need to ID periodically in a separate transmission.  I expected to be able to attach and use the operator call sign entered into the fldigi configuration but I did not find it available for transmit anywhere in the system and that caused me to question further as to why it is entered and never used.  Attaching the ID to a transmission would prevent extra stand alone call sign ID's in net traffic. A button to turn it on or off similar to RSID or CW ident and or a field to insert operator call sign into a macro for ID purposes seem logical to me.

Randy

Re: Use of operator callsign

Howard Rob
 

This problem is solved in the Outpost program. If a tactical call sign is defined for a station, that is used for To: and From: and so appears as the call sign for the station.  At the end of a transaction, the operator's call sign is sent as text (for ID) and not part of the message.
In the case of an Flmsg message, the operator's call sign could be sent after the [wrap:end].

FWIW.

73

Bob   VE3YX

Re: Use of operator callsign

Dave
 

Correct me if I misunderstand, but it seems you want a third identifier

<MYCALL> - station call sign
<OPCALL> - operator call sign
<UNIT> - unit identifier

with the ability to use any of the three within a macro.

The OPCALL is saved in the logbook



73, David, W1HKJ

Re: Use of operator callsign

Larry Levesque
 

I think he at least wants the <OPCALL> to have a macro tag you can send.
But I do think a tactical call would also be good. That way you would not have to re-arrange your call signs for different uses (contest versus emergency / ARES).

On Mon, May 07, 2018 at 05:43:13PM -0500, w1hkj wrote:
Correct me if I misunderstand, but it seems you want a third identifier

<MYCALL> - station call sign
<OPCALL> - operator call sign
<UNIT> - unit identifier

with the ability to use any of the three within a macro.

The OPCALL is saved in the logbook



73, David, W1HKJ
--
Larry Levesque
KA1VGM

Re: Use of operator callsign

David Aitcheson KB3EFS <kb3efs.dave@...>
 

Dave W1HKJ,

I am of the mindset that "Randy" should just turn on the CW-Id at end of transmission option and be happy.

73
Dave
KB3EFS


On 05/07/2018 06:43 PM, Dave wrote:
Correct me if I misunderstand, but it seems you want a third identifier

<MYCALL> - station call sign
<OPCALL> - operator call sign
<UNIT> - unit identifier

with the ability to use any of the three within a macro.

The OPCALL is saved in the logbook



73, David, W1HKJ


Re: Use of operator callsign

Randy
 

No not a third call sign and not the CW ID.

 

Fldigi  operator setup inputs a station call sign which I see tracking into the standard macros, the <MYCALL> macro field and the CW ID if transmitted. 

 

Fldigi operator setup also inputs the operator call sign which is not available for or ever used in a transmission. Why?

 

Flmsg config  inputs CALL and this is the only one transmitted with an flmsg transmission.

 

During a contingency, let’s say we use HOSPITAL and EOC as tactical ID then the flmsg and fldigi station calls should match these for message sorting by origination reasons.  The operator call sign in fldigi then could become the legal ID for transmissions but I can not use it anywhere in a transmission.  I can of course voice ID or hard code my own macro to play as required but an option to map the operator call sign into the transmissions would cover ID without extra traffic.  The CW ID currently can not be used because it is linked to the station tactical call in this configuration. 

 

Randy

 

Sent from Mail for Windows 10

 

From: David Aitcheson KB3EFS
Sent: Monday, May 7, 2018 7:04 PM
To: nbems@groups.io
Subject: Re: [nbems] Use of operator callsign

 

Dave W1HKJ,

I am of the mindset that "Randy" should just turn on the CW-Id at end of transmission option and be happy.

73
Dave
KB3EFS

On 05/07/2018 06:43 PM, Dave wrote:

Correct me if I misunderstand, but it seems you want a third identifier

<MYCALL> - station call sign
<OPCALL> - operator call sign
<UNIT> - unit identifier

with the ability to use any of the three within a macro.

The OPCALL is saved in the logbook



73, David, W1HKJ

 

 

Re: Use of operator callsign

Michael Pittaro
 

Dave's proposal makes sense to me.

Station and Operator call are already well defined by the FCC (and
probably other international agencies.) Unit identifier could be
used for a tactical call.

mike, kj6vcp

Re: Use of operator callsign

Dave
 

May I suggest that you can use the <FILE:[fname]> macro tag to achieve the end result you are seeking:
  • create a file named TACTICAL_CALL.txt, to contain the information specific to the site, ie:
    • "MITCHELL, SD HOSP"
  • modify the macros substituting the <FILE:...> macro tage where <MYCALL> would have been used, ie:
    • <URCALL> de <FILE:"C:\Users\randy\fldigi.files\files\TACTICAL_CALL.txt">
Not as simple as <URCALL> de <UNIT>, but it does get the job done.  It also allows you to be as succinct or verbose as needed.

In the meantime, I will assume that you are requesting a program change to include a UNIT identifier control, whose contents can be referenced in a macro tag.  I will do the same for OPCALL.

73, David, W1HKJ

Re: Use of operator callsign

Randy
 

Hi Dave,

 

The file macro would be another solution equal to just creating a macro with the call sign text.  My thought would be to append the operator call sign to the end of a transmission with no need for a new field.  For example take this from my fldigi log file (below).  SDDOH3 and AQoP were tactical call signs.  After [WRAP:end] why not just send the operator call sign to meet FCC ID requirements.  Any operator or multiple operators supporting any or multiple locations or agencies would be covered with his own correct ID.  For personal use it could be turned off just as the CW ID can be switched off.  Another reply mentioned the Outpost program doing this.  I have not seen that program.  Creating a new field isn’t needed when there is already one not fully utilized or accessable.

 

1.213]<flmsg>4.0.5

RX 147346500 : MT63 (2018-04-27 20:22Z): :hdr_fm:42

RX 147346500 : MT63 (2018-04-27 20:22Z): SDDOH3 20182704201948

RX 147346500 : MT63 (2018-04-27 20:22Z): AQoP 20182704202213

>>>Cut out here

RX 147346500 : MT63 (2018-04-27 20:22Z): AQoP

RX 147346500 : MT63 (2018-04-27 20:22Z): [WRAP:chksum F58A][WRAP:end]     <Insert ID here using fldigi operator call sign>

RX 147346500 : MT63 (2018-04-27 20:22Z): ... end

RX 147346500 : MT63 (2018-04-27 20:22Z):

 

 

 

Randy

KG5KZF

http://mit.midco.net/rpratt

 

-----Original Message-----

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Dave
Sent: Monday, May 07, 2018 9:43 PM
To: nbems@groups.io
Subject: Re: [nbems] Use of operator callsign

 

May I suggest that you can use the <FILE:[fname]> macro tag to achieve the end result you are seeking:

·         create a file named TACTICAL_CALL.txt, to contain the information specific to the site, ie:

o        "MITCHELL, SD HOSP"

·         modify the macros substituting the <FILE:...> macro tage where <MYCALL> would have been used, ie:

o        <URCALL> de <FILE:"C:\Users\randy\fldigi.files\files\TACTICAL_CALL.txt">

Not as simple as <URCALL> de <UNIT>, but it does get the job done.  It also allows you to be as succinct or verbose as needed.

In the meantime, I will assume that you are requesting a program change to include a UNIT identifier control, whose contents can be referenced in a macro tag.  I will do the same for OPCALL.

73, David, W1HKJ

fldigi alpha posted

Dave
 

At www.w1hkj.com

and Source Forge

Changes post 4.0.16


fldigi 4.0.17.62

  tmpfile
    * tmpfile() on OS X is apparently not thread safe
      remove usage from SoundBase::format_supported(...)
    * this fixes exit hang up on OS X when audio
      capture, or record had been selected

  Serial port discovery
    * Add /dev/rfcomm? blue tooth serial device
      names to serial device list

  Log entries
    * Change mode entry for Olivia, MT63, Thor, Throb to
      include submode.
      - allows correct setting of mode / submode when
        retrieving a logbook entry.

  rx/tx
    * correct action of tx over rx toggle

  Documentation Update
    * Add nanoCW, nanoFSK, Navigator interface.
    * Update macro matrix display (48 macros in 4 rows)

  RTTY Quick pick
    * disable RTTY quick pick if using nanoIO or Navigator

  flarq appdir
    * change test for FL_APPS folder

  WinKey PTT
    * Enable winkey PTT

  CW/FSK I/O on start
    * restore last connect state of Nav / tinyCW / tinyFSK
      when starting program

  Default Lighted Button
    * Allow user to specify the default ON color for all
      lighted buttons not specifically configured.

  ST/PR macro tags
    * Add macro tags for State and Province

  Logbook read
    * Make Rx panel announcement of read user optional

  Navigator
    * Add Navigator terminal unit support for FSK
      - options setting panel

  nanoIO
    * nanoIO is the interface code for the device nanoIO, an Arduino
      project that provide hard line keying of CW and FSK
    * compatible with MORTTY (c)
    * nanoFSK
      - Add interface and support code for nanoIO / tinyFSK Arduino
        FSK keyers
      - Modify waterfall frequency display for transceiver FSK
      - Modify dxcluster qsy operations to provide correct QSY
        for transceiver FSK
      - Add TTY transceiver mode recognition if transceiver mode
        string contains RTTY or FSK
    *nanoCW
      - Add CW support using nanoIO
      - CW WPM 5 to 100
      - CW dash/dot ratio: 2.5 to 3.5

  quick pick rtty baud
    * add 100 Baud

  K2/K3/KX3 data modes
    * Add DATA / DATA-R as FSK type submodes if either tinyFSK,
      Navigator or Right-Channel FSK signaling interface is enabled.

  Modem start frequency
    * Change initialization of modem start up frequency
      - prevent unintended start @ 1000 Hz for every change in mode

  fsq/ifkp audit logs
    * Enable audit log open/close from configuration panel
    * Correct date-time stamp in logs

  RTTY browser decode
    * fix browser decoder sense when transceiver is in LSB
      type mode, i.e. FSK, LSB, LSB-D etc.

  8pskF
     * Fixed bug in 8psk 125F/250F init code
      - Bad constraint length was causing decoder to fail
    * New preamble for 8PSK FEC modes
      - FEC modes preamble is now a continuous tone at center-frequency
      - Gives reference for clicking &  selecting signal on waterfall.
      - Is backwards compatible with  previous-version 8psk preambles
    * Adjusted 8PSK-F modes flush/postamble length much longer
     - Can visually see the inlv flush and postamble "tail" on  waterfall
     - New flust/postamble extends beyond data, to prevent cutoff
    * Code, formatting, and comments cleaned-up for 8PSK code


73, David, W1HKJ

fldigi 4.0.17.63 alpha posted

Dave
 

On 05/16/2018 04:07 PM, Ron wrote:
Hi Cliff,

The sweet spot is not checked.  If it's working okay for you then it has to be something in my setup.  I even changed the name of the pref and def files.  Fldigi 4.0.16 doesn't do it.

73, Ron NY3J

On 05/16/2018 05:00 PM, Cliff wrote:
Ron,

What do you have for “Sweet Spot” settings. I ask because I don’t see that here at all. As a matter of fact I haven’t seen the problem except for very occasionally for quite some time so your comments surprised me. Hopefully Dave has an answer.

73,
Cliff, AE5ZA

On May 16, 2018, at 15:12, Ron <rwenig@...> wrote:

Hi Dave,

I just installed 4.0.17.62 and it looks like it's still forcing the start frequency to 1000 Hz on the waterfall for all modes except 8PSK.  If I am on the waterfall frequency of 1000 and I change to any 8PSK mode the frequency will change to 1500.

73, Ron NY3J

fldigi 4.0.17.64 alpha posted

Dave
 

At http://www.w1hkj.com
and Source Forge.

Fixes to 4.0.17.63 test result reports from Ron and Cliff.

Dave

Re: fldigi 4.0.17.64 alpha posted

Ron
 

Dave,

That did the trick.  It remembers the last waterfall frequency, RsID frequency change works and sweet spot works.  Both Windows 10 and Ubuntu.  Putting in the overtime tonight.  That's double time for an emergency call out correct :-)

Thanks Dave.  A great program is now working even greater.

73, Ron NY3J

On 05/18/2018 10:35 PM, Dave wrote:
At http://www.w1hkj.com
and Source Forge.

Fixes to 4.0.17.63 test result reports from Ron and Cliff.

Dave


fldigi-4.0.17.65 alpha posted

Dave
 

FLDIGI Direct CW Keying w/ hamlib

Joel Vazquez, WE0DX
 

Hello everyone,

Hopefully I'm sending this message to the right group.  I have a question on FLDIGI, while on CW, can I key my Kenwood TS-2000 directly via hamlib like I do with CQRLOG?  I mean, I dont want to use a second serial port for the CW key, I want hamlib to tell my radio what to key (this is how I currently use CQRLog).  So basically FLDigi would pass the text string to hamlib to be managed by the radio.

Thanks in advance,
Joel Vazquez - WE0DX
Amateur Extra Class Ham Radio

Re: FLDIGI Direct CW Keying w/ hamlib

Ed W3NR
 

On Sun, 20 May 2018 18:40:39 -0700
"Joel Vazquez, WE0DX" <@WE0DX> wrote:

Hello everyone,

Hopefully I'm sending this message to the right group.  I have a
question on FLDIGI, while on CW, can I key my Kenwood TS-2000
directly via hamlib like I do with CQRLOG?  I mean, I dont want to
use a second serial port for the CW key, I want hamlib to tell my
radio what to key (this is how I currently use CQRLog).  So basically
FLDigi would pass the text string to hamlib to be managed by the
radio.

Thanks in advance,

*Joel Vazquez - WE0DX*
Amateur Extra Class Ham Radio
E // @WE0DX
 
W // https://www.we0dx.us
You really need to read the user manual for fldigi ::

http://www.w1hkj.com/FldigiHelp/

and then the chapter on the CW modem::

http://www.w1hkj.com/FldigiHelp/cw_page.html

Ed W3NR