Date   

Re: Change request, add morse characters #firmware #qcx

Richard
 

On Wed, Aug 12, 2020 at 03:03 PM, N7PH wrote:
I have trouble with 'CQ' sometimes sent as seperate letters and sometimes sent as one long 'prosign'.
Either is quite recognizable but which is correct?  -.-.--.-  or -.-.   --.-  ?
From some things I've read, techinically CQ is a prosign as per ITU-R M.1172


Re: Change request, add morse characters #firmware #qcx

Richard
 

On Wed, Aug 12, 2020 at 02:16 PM, Daniel Walter wrote:
While we're on the topic of prosigns, for a long time I thought BK was a proSign as a lot of people seem to run the two letters together and was -...-.- rather than -...  -.-  so maybe some were separating end-of-transmission as ...  -.- and some as ...-  .- instead of ...-.-  Jus' sayin...

BK is a prosign defined by ITU-R M.1172


Re: Change request, add morse characters #firmware #qcx

N7PH
 

I have trouble with 'CQ' sometimes sent as seperate letters and sometimes sent as one long 'prosign'.
Either is quite recognizable but which is correct?  -.-.--.-  or -.-.   --.-  ?

PJH, N7PH


Re: Adapt A Bioenno 24v LiFePO4 Battery To Run The QRPLabs 50 Watt PA?

Shane Justice <justshane@...>
 

Hi Allison! That's great! Congratulations on your retirement!

It would be fun to catch up with Marshall- perhaps we can all rg chew one of these days when I get my antenna(s) up at my new QTH.

73,
Shane


On Aug 12, 2020 at 11:52, ajparent1/KB1GMX <kb1gmx@...> wrote:

Shane,

Retired two years ago.  Marshall is local to me and still on the air W1HK.
Had a lot of good fun and worked on a lot of interesting projects like
the body loaded antennas.  Did a lot of field testing, antenna evaluation,
and prototype development.  

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: QCX Firmware change request: Validate CAT frequency values. #qcx #firmware #cat

Arv Evans
 

Jack

Yes, it would probably need a few more bytes of memory to compare actual 
frequency with EEPROM stored "upper limit" and "lower limit" that could be 
a user entered semi-fixed variable.  Multi-band rigs could have upper and lower 
user settable limits for each band.

The 1602 display can store an additional 32 bytes of memory if you enable the 
R/W lead.

_._

On Wed, Aug 12, 2020 at 12:51 PM jjpurdum via groups.io <jjpurdum=yahoo.com@groups.io> wrote:
That's still not cut-and-dried if out-of-band can vary among countries. The only alternative would be for Hans to offer specific 328 chips for each country for each band. That's a train just begging to leave the rails. I say this because, last I talked with Hans, he was down to less than 10 bytes of free memory.

Jcak, W8TEE

On Wednesday, August 12, 2020, 2:46:46 PM EDT, Arv Evans <arvid.evans@...> wrote:


Seems that all that is needed is for the QCX to inhibit keying for out-of-band 
frequencies.  This would leave it still able to listen to out-of-band stations.

_._


On Wed, Aug 12, 2020 at 11:04 AM Sheldon Hartling <ve1gpy@...> wrote:
Not sure there is sufficient program space go support this and it varies by location.
For sure about sufficient space!  I've developed firmware and am painfully award of the challenges trying to "shoe horn" additional features into very limited space. 

Even a range check that looks for reasonable (course) values for the band without following the specific regional band plan would be a help.  Right now, I threw my QCX into a sputtering fit by entering "70201" instead of "7020" in N1MM+. ☺︎

Sheldon VE1GPY


Re: Change request, add morse characters #firmware #qcx

Arv Evans
 

William

The FCC also gave the call sign "N0CLU"" which is among 
the more hilarious ones.

_,_


On Wed, Aug 12, 2020 at 12:22 PM William Fogel <wefogel@...> wrote:
Sheldon   Most of us here in the states have no idea what to think about the VA, either! (Veterans Administration) Thanks to all, this thread has been most entertaining. I would strongly suggest that you ask one of the teachers in the LI CW Club. FYI, there is a whole new/older group of us that read it as "SK".

But just remember the FCC saw fit to give me the call  "AG5SK", you think they were trying to tell me something??

--...  ...--  -.. . .- --. ..... ... -.-        


Re: Adapt A Bioenno 24v LiFePO4 Battery To Run The QRPLabs 50 Watt PA?

ajparent1/KB1GMX
 

Shane,

Retired two years ago.  Marshall is local to me and still on the air W1HK.
Had a lot of good fun and worked on a lot of interesting projects like
the body loaded antennas.  Did a lot of field testing, antenna evaluation,
and prototype development.  

Allison
-------------------------------
Please reply on list so we can share.
No private email, it goes to a bit bucket due address harvesting


Re: QCX Firmware change request: Validate CAT frequency values. #qcx #firmware #cat

jjpurdum
 

That's still not cut-and-dried if out-of-band can vary among countries. The only alternative would be for Hans to offer specific 328 chips for each country for each band. That's a train just begging to leave the rails. I say this because, last I talked with Hans, he was down to less than 10 bytes of free memory.

Jcak, W8TEE

On Wednesday, August 12, 2020, 2:46:46 PM EDT, Arv Evans <arvid.evans@...> wrote:


Seems that all that is needed is for the QCX to inhibit keying for out-of-band 
frequencies.  This would leave it still able to listen to out-of-band stations.

_._


On Wed, Aug 12, 2020 at 11:04 AM Sheldon Hartling <ve1gpy@...> wrote:
Not sure there is sufficient program space go support this and it varies by location.
For sure about sufficient space!  I've developed firmware and am painfully award of the challenges trying to "shoe horn" additional features into very limited space. 

Even a range check that looks for reasonable (course) values for the band without following the specific regional band plan would be a help.  Right now, I threw my QCX into a sputtering fit by entering "70201" instead of "7020" in N1MM+. ☺︎

Sheldon VE1GPY


Re: QCX Firmware change request: Validate CAT frequency values. #qcx #firmware #cat

Arv Evans
 

Seems that all that is needed is for the QCX to inhibit keying for out-of-band 
frequencies.  This would leave it still able to listen to out-of-band stations.

_._


On Wed, Aug 12, 2020 at 11:04 AM Sheldon Hartling <ve1gpy@...> wrote:
Not sure there is sufficient program space go support this and it varies by location.
For sure about sufficient space!  I've developed firmware and am painfully award of the challenges trying to "shoe horn" additional features into very limited space. 

Even a range check that looks for reasonable (course) values for the band without following the specific regional band plan would be a help.  Right now, I threw my QCX into a sputtering fit by entering "70201" instead of "7020" in N1MM+. ☺︎

Sheldon VE1GPY


Re: Change request, add morse characters #firmware #qcx

Michael.2E0IHW
 

Using either can result in confusion for non-professional CW ops.
An extra  microsecond or two  to confirm end-of-message would facilitate clarity,
especially for those of us who are sub-perfect and hope for
inclusion and encouragement.

Michael 2E0IHW

On Mi..12.August 17:06, mike mccarthy wrote:
When doing yachtmasters in 76 weather reports were in morse and VA was used. Sarasota Florida, club which helped me study for my US licence VA was used.
UK licence course in about 84 used set book "Amateur Radio" by Robert L. Sharader W6BNB (Former chairman of Electronics Laney College) US publication, used both VA and SK. (pg296).
SK always suggests someone has died to me and gives me the shivers. Please lets use VA.


Re: Change request, add morse characters #firmware #qcx

Daniel Walter
 

Anyway the real issue is not whether it is SK or VA (or EEETET), but whether they have a bar over the letters to signify that they are sent as one character. I don't know that there is any easy way to do that with the 1602 character display. Even if there is a way to define a new character, that would probably take up a significant amount of memory on the '328P chip, of which I hear is in short supply. 
--
73, Dan  NM3A


Re: Change request, add morse characters #firmware #qcx

William Fogel
 

Sheldon   Most of us here in the states have no idea what to think about the VA, either! (Veterans Administration) Thanks to all, this thread has been most entertaining. I would strongly suggest that you ask one of the teachers in the LI CW Club. FYI, there is a whole new/older group of us that read it as "SK".

But just remember the FCC saw fit to give me the call  "AG5SK", you think they were trying to tell me something??

--...  ...--  -.. . .- --. ..... ... -.-        


Re: Change request, add morse characters #firmware #qcx

Daniel Walter
 

While we're on the topic of prosigns, for a long time I thought BK was a proSign as a lot of people seem to run the two letters together and was -...-.- rather than -...  -.-  so maybe some were separating end-of-transmission as ...  -.- and some as ...-  .- instead of ...-.-  Jus' sayin...
--
73, Dan  NM3A


Re: Change request, add morse characters #firmware #qcx

John Rabson
 

In journalism, "no 30" meant “Filing not finished. More to come”.

John F5VLF

On 12 Aug 2020, at 19:24, Bruce K1FFX <rosen.bruce@...> wrote:

From the IARU's "Ethics and Operating Procedures for the Radio Amateur" (found at arrl.org):

SK: end of QSO: is used to end a QSO (SK = Stop Keying).

‘DIT DIT DIT DAH DIT DAH’ is the prosign ‘SK’ (from ‘stop keying’) and not ‘VA’ as published in some places (SK sent without inter letter spacing sounds the same as VA sent without inter letter spacing).

And from arrl.org's Ham Radio History: Our familiar prosign SK also had its origin in landline Morse. In the Western Union company's "92 code" used even before the American Civil War, the number 30 meant "the end. No more." It also meant "good night." It so happens that in Landline Morse, 30 is sent didididahdit daaah, the zero being a long dash. Run the 30 together and it has the same sound as SK.

- Bruce K1FFX



QCX Firmware change request: XON/XOFF flow control for CAT. #qcx #firmware #cat

Sheldon Hartling
 

Knowing the answer is probably "there's no room" :-) I'll ask anyways ...

Hans,

It'd be nice to have XON/XOFF implemented for the CAT serial port as an option to facilitate sharing of the IC2 pin 2 and 3 lines.  Currently, in V1.5, a CAT command received by the QCX during an LCD write is ignored.

 

Before driving IC2 pin 25 high at the start of an LCD write operation, you'd need to send an XOFF character (DC3, 0x13, ctrl-S) to the CAT port.  Then, when the LCD write operation was complete, after restoring IC2 pin 25 low, you'd need to send an XON character (DC1, 0x11, ctrl-Q) to the CAT port.  To be most effective, the XOFF would have to be sent as early as possible during the LCD write operation.  Unlike CTS it takes a little time to work effectively.  The XOFF character has to be sent over the serial line at 38400 baud, received by the computer, decoded, and acted on by the computer's driver software.

 

Not all computers/applications will support XON/XOFF so this would likely need to be included as a new menu item.

 

Thanks and 73, Sheldon VE1GPY

 


Re: Change request, add morse characters #firmware #qcx

jjpurdum
 

Gees...I always thought <BT> was "break thought". The 1929 Navy manual someone posted earlier has:
   AR
   K
at the end of a message. I guess it's a whatever works kind of thing.

Jack, W8TEE


On Wednesday, August 12, 2020, 11:03:30 AM EDT, Richard <groups.io@...> wrote:


On Wed, Aug 12, 2020 at 10:35 AM, Shane Justice wrote:
We used VA as a signal to the receiving station that we were thinking of what to say next, so the operator on the other end would know we were still there (versus silence) while we were composing our thoughts.
Yet another difference.  I was taught that <BT> was used for this, as kind of an "um, ah" thing.


Re: Change request, add morse characters #firmware #qcx

Bruce K1FFX
 

From the IARU's "Ethics and Operating Procedures for the Radio Amateur" (found at arrl.org):

SK: end of QSO: is used to end a QSO (SK = Stop Keying).

‘DIT DIT DIT DAH DIT DAH’ is the prosign ‘SK’ (from ‘stop keying’) and not ‘VA’ as published in some places (SK sent without inter letter spacing sounds the same as VA sent without inter letter spacing).

And from arrl.org's Ham Radio History: Our familiar prosign SK also had its origin in landline Morse. In the Western Union company's "92 code" used even before the American Civil War, the number 30 meant "the end. No more." It also meant "good night." It so happens that in Landline Morse, 30 is sent didididahdit daaah, the zero being a long dash. Run the 30 together and it has the same sound as SK.

- Bruce K1FFX


Re: Change request, add morse characters #firmware #qcx

John AK4AT
 

<SK> stands for something (silent key/end of transmitting). Some key RR as E N  E N which makes no sense but has spread over time like the concept of VA instead of SK. Some key BK as a prosign.


Re: Change request, add morse characters #firmware #qcx

Rachael Sanders
 

👍

On Wed, 12 Aug 2020 at 18:03, Dave, W0DF <dfine100@...> wrote:
Been Hamming for 58 years, four years as a manual Morse intercept operator in the US Navy and have almost always seen it as VA, but I really don't care which one you use, so I'll leave it to the software programmer (Hans) to decide which he prefers.  Dave, W0DF


Re: QCX Firmware change request: Validate CAT frequency values. #qcx #firmware #cat

jjpurdum
 

Sheldon:

I think Hans is down to less than 10 bytes of unused memory. Another problem is that "out of band" likely varies at different places in the world. I'm not sure if Hans could use the EEPROM space, but that still means a change in the source code, and that's not going to happen.

Jack, W8TEE

On Wednesday, August 12, 2020, 12:38:25 PM EDT, Sheldon Hartling <ve1gpy@...> wrote:


Hi Hans,

 

Please consider validating the frequency values received in "FA" and "FB" CAT commands to confirm they are valid for the QCX's band.  Currently, in v1.5, out-of-band values are accepted and set the VFO to unsupported frequencies.  Easy to do, by accident, when hand-entering values in logging programs.

 

Thanks and 73, Sheldon VE1GPY

 

10421 - 10440 of 61096