Date   
Re: CW Interface

Dave
 

fldigi tests to see the connected device is performing as a Winkeyer using the Immediate Admin command for echo test:

Immediate Admin Commands

Admin
<00><nn>

nn is a value from 0 to 8

After power-up the host interface is closed, serial status, echo, or pot change data will be not be sent to the
host. The only commands WK2 will accept are Admin commands.  Admin commands are received,
processed and any return status or data will be sent back immediately.  Admin commands calibrate the
interface, reset WK, obtain debug information and open the interface.  With the exception of the Amin:Close
command, all Admin commands should only be issued while the host interface is closed.  Following are
descriptions of the Admin commands:

0: Calibrate This is an historical command preserved for WK1 compatibility. It is no longer required for
the more accurate PIC the WK2 is implemented on. You can issue the command and it
will not cause ill effects, but it is not processed by WK2. The command syntax is:
<00><00> pause 100 mSec <FF>

1: Reset Resets the Winkeyer2 processor to the power up state. Do not send this as part of the
initialization sequence. Only send this if you want to do a cold reboot of WK2.

2: Host Open Upon power-up, Winkeyer2 initializes with the host mode turned off. To enable host mode,
the PC host must issue the admin:open command. Upon open, Winkeyer2 will respond by
sending the revision code back to the host. The host must wait for this return code before
any other commands or data can be sent to Winkeyer2. Upon open, WK1 mode is set.

3: Host Close Use this command to turn off the host interface. Winkeyer2 will return to standby mode
after this command is issued. Standby settings will be restored.

4: Echo Test Used to test the serial interface. The next character sent to Winkeyer2 after this command
will be echoed back to the host.

After establishing the serial connection the serial data stream x00 x04 'U' is sent.  Fldigi then waits up to 5 seconds for the echo response 'U'.

The K3NG sketch is not responding to the echo test, so fldigi code declares it as not responsive.

You might want to look over the K3NG sketch code to see if it designed to perform the echo test.

73, David, W1HKJ

Re: CW Interface

Robie
 

Dave,

I'll take a look, just for my own education as this type of work is a bit "over my pay grade".  

Thanks,

Robie - AJ4F

On Sun, Apr 14, 2019 at 6:31 PM Dave <w1hkj@...> wrote:
fldigi tests to see the connected device is performing as a Winkeyer using the Immediate Admin command for echo test:

Immediate Admin Commands

Admin
<00><nn>

nn is a value from 0 to 8

After power-up the host interface is closed, serial status, echo, or pot change data will be not be sent to the
host. The only commands WK2 will accept are Admin commands.  Admin commands are received,
processed and any return status or data will be sent back immediately.  Admin commands calibrate the
interface, reset WK, obtain debug information and open the interface.  With the exception of the Amin:Close
command, all Admin commands should only be issued while the host interface is closed.  Following are
descriptions of the Admin commands:

0: Calibrate This is an historical command preserved for WK1 compatibility. It is no longer required for
the more accurate PIC the WK2 is implemented on. You can issue the command and it
will not cause ill effects, but it is not processed by WK2. The command syntax is:
<00><00> pause 100 mSec <FF>

1: Reset Resets the Winkeyer2 processor to the power up state. Do not send this as part of the
initialization sequence. Only send this if you want to do a cold reboot of WK2.

2: Host Open Upon power-up, Winkeyer2 initializes with the host mode turned off. To enable host mode,
the PC host must issue the admin:open command. Upon open, Winkeyer2 will respond by
sending the revision code back to the host. The host must wait for this return code before
any other commands or data can be sent to Winkeyer2. Upon open, WK1 mode is set.

3: Host Close Use this command to turn off the host interface. Winkeyer2 will return to standby mode
after this command is issued. Standby settings will be restored.

4: Echo Test Used to test the serial interface. The next character sent to Winkeyer2 after this command
will be echoed back to the host.

After establishing the serial connection the serial data stream x00 x04 'U' is sent.  Fldigi then waits up to 5 seconds for the echo response 'U'.

The K3NG sketch is not responding to the echo test, so fldigi code declares it as not responsive.

You might want to look over the K3NG sketch code to see if it designed to perform the echo test.

73, David, W1HKJ

Re: CW Interface

Dave
 

I've tested the K3NG sketch in my MORTTY with the echo test code removed from fldigi.   Works equally well with the original WinKeyer and the MORTTY with the K3NG sketch.  You can test for yourself using this alpha version:

which contains these changes from fldigi version 4.1.02 released yesterday.

    Fake WinKeyer
   
      * Disable WinKey Admin echo test.
        - K3NG Arduino sketch fails tests as implemented
          in the MORTTY interface

    MACRO <MODEM:
   
      * Add code to correctly recognize OLIVIA submodes

73, David, W1HKJ


RXID on FLDIGI

John Wilson
 

Looking at variations of digital modes that are out there, it can become very overwhelming to identify them and identifying them off the cuff is difficult when several modes show very similar characteristics in their pattern.

As I understand it, in FLIDIGI, with RXID on, it should display what mode is being transmitted for the modes checked on the ID tab in settings but as I put the bandwidth window on the signal, I don't always see the particular mode being transmitted. Rarely, if ever.

Is that because of poor reception or because the transmitted signal isn't providing the mode within its own transmission?

Re: RXID on FLDIGI

Al Massaro
 

John the RSID will change your RX mode for you, it will display a before RSID message for you only when it is received. Got to the user interface setup under ID to setup how you would like it to display and react.
AL M
KF5SMH

Re: RXID on FLDIGI

John Wilson
 

Al,

All the above... just intermittent in its identification. May not be letting it sit long enough to identify. I'll keep tinkering with it and see what happens.

Thanks for the reply.

73
John



On Mon, Apr 15, 2019 at 2:27 PM Al Massaro <almassaro@q.com> wrote:
John the RSID will change your RX mode for you, it will display a before RSID message for you only when it is received. Got to the user interface setup under ID to setup how you would like it to display and react.
AL M
KF5SMH

Re: RXID on FLDIGI

W2TLJ
 

Just a note, RXID does not work unless the transmitting station has TXID turned on. Normally I find this is the cause of the non identifying problem.

Tom W2TLJ

On Mon, Apr 15, 2019 at 4:02 PM John Wilson <kc4lzn@...> wrote:
Al,

All the above... just intermittent in its identification. May not be letting it sit long enough to identify. I'll keep tinkering with it and see what happens.

Thanks for the reply.

73
John



On Mon, Apr 15, 2019 at 2:27 PM Al Massaro <almassaro@q.com> wrote:
John the RSID will change your RX mode for you, it will display a before RSID message for you only when it is received. Got to the user interface setup under ID to setup how you would like it to display and react.
AL M
KF5SMH

Re: RXID on FLDIGI

John Wilson
 

Thanks Tom and because of the sporadic display of the different modes is telling me just that. Stations that I'm seeing with the mode identification have that turned on where the ones I'm not, don't. 

Thanks for the input.

73 John


On Mon, Apr 15, 2019 at 4:49 PM W2TLJ <tjoneson@...> wrote:
Just a note, RXID does not work unless the transmitting station has TXID turned on. Normally I find this is the cause of the non identifying problem.

Tom W2TLJ

On Mon, Apr 15, 2019 at 4:02 PM John Wilson <kc4lzn@...> wrote:
Al,

All the above... just intermittent in its identification. May not be letting it sit long enough to identify. I'll keep tinkering with it and see what happens.

Thanks for the reply.

73
John



On Mon, Apr 15, 2019 at 2:27 PM Al Massaro <almassaro@q.com> wrote:
John the RSID will change your RX mode for you, it will display a before RSID message for you only when it is received. Got to the user interface setup under ID to setup how you would like it to display and react.
AL M
KF5SMH

Re: RXID on FLDIGI

bobmary37 <bobmary37@...>
 

Well sort of! I have an iMac computer. Is there a Mac version of fldigi? I have an FT991, can I get cat control with my Mac?




On Monday, April 15, 2019, 18:21, John Wilson <kc4lzn@...> wrote:

Thanks Tom and because of the sporadic display of the different modes is telling me just that. Stations that I'm seeing with the mode identification have that turned on where the ones I'm not, don't. 

Thanks for the input.

73 John


On Mon, Apr 15, 2019 at 4:49 PM W2TLJ <tjoneson@...> wrote:
Just a note, RXID does not work unless the transmitting station has TXID turned on. Normally I find this is the cause of the non identifying problem.

Tom W2TLJ

On Mon, Apr 15, 2019 at 4:02 PM John Wilson <kc4lzn@...> wrote:
Al,

All the above... just intermittent in its identification. May not be letting it sit long enough to identify. I'll keep tinkering with it and see what happens.

Thanks for the reply.

73
John



On Mon, Apr 15, 2019 at 2:27 PM Al Massaro <almassaro@q.com> wrote:
John the RSID will change your RX mode for you, it will display a before RSID message for you only when it is received. Got to the user interface setup under ID to setup how you would like it to display and react.
AL M
KF5SMH

Re: CW Interface

Lee Garner
 

Dave, now I am interested in building this. Thanks :)

From: Dave
Sent: Sunday, April 14, 15:12
Subject: Re: [nbems] CW Interface
To: nbems@groups.io


I've tested the K3NG sketch in my MORTTY with the echo test code removed from fldigi.   Works equally well with the original WinKeyer and the MORTTY with the K3NG sketch.  You can test for yourself using this alpha version:
which contains these changes from fldigi version 4.1.02 released yesterday.
    Fake WinKeyer
   
      * Disable WinKey Admin echo test.
        - K3NG Arduino sketch fails tests as implemented
          in the MORTTY interface

    MACRO <MODEM:
   
      * Add code to correctly recognize OLIVIA submodes
73, David, W1HKJ



A Solution To The Digital Mode Recognition Issue

Dave
 

This response is being shared with the linuxham and nbems groups at groups.io.

"Sounds" like a perfect opportunity for someone to write a QST article, Digital Modes Operating Etiquette.  My own preference is to use RsID only when calling CQ and then not for commonly recognized modes such as BPSK31.  Use this macro text for your CQ macro.  It will turn on RsID for each CQ and disable it immediately thereafter.



Configure the transmit RsID as disabled for the commonly recognized modes:



I often see an Olivia 8/500 QSO without an RsID.  It is completely indistinguishable from a Contestia 8/500 signal.  The tone patterns and spacing of Olivia and Contestia look the same for the same number of tones and bandwidth.  I've even seen Olivia being used on the opposite sideband (or reversed).  I chalk those up to ignorance rather than a desire for an anonymous, private conversation.   Fldigi's RsID configuration items can help to avoid being interrupted by the operator calling CQ with the RsID enabled. 



During emergency communications or net operations it is probably not a good idea to casually transmit the RsID.  It does slow down the exchange, and it might inadvertently interrupt an existing data exchange.  The use of RsID in a net should be a part of the net operating procedures.

I will change the fldigi's default CQ macro to that shown above.  That will at least assist new digital operators using fldigi to be courteous and informative.

73, David, W1HKJ


On 4/17/19 10:59 PM, Tony wrote:
On 4/17/2019 10:41 PM, Charles Hargrove wrote:
I don't see what the difficulty is. I leave my RxID & TxID on all the time.

Charles:

Difficulty is not the problem, it's the lack of use. The reason is a mystery, but I can tell you that the problem has existed for many years.

I'm not aware of RS-ID being mentioned in the ham license question pool so that could part of the problem for new and old alike who are just getting started with digital.

Tony -K2MO

Software help

Randy Davenport
 

I am interested in the nbems program.. I am disabled and low income. I connect to the internet on my cell phone as I have no internet at my apartment. Can someone please help me out with a CD or thumb drive with all the install programs. I am also interested in Chirp, Rmsexpress, winlink,  wajt-x, jtalert with all programs, , fldigi and all programs needed.
Randy ka4nma
Im good on qrz

Re: Software help

Daniel Miranda
 

Hi, Randy! Please clarify: are you planning on connecting your mobile phone to the radio or using a regular Pc for that?

How are you planning to use these applications?

If your disability has to do with hearing or speaking, I think there are extra good things to enjoy from digital modes.

Best,
-- Daniel

Em qui, 18 de abr de 2019 10:21, Randy Davenport <pastor.spaceboy@...> escreveu:

I am interested in the nbems program.. I am disabled and low income. I connect to the internet on my cell phone as I have no internet at my apartment. Can someone please help me out with a CD or thumb drive with all the install programs. I am also interested in Chirp, Rmsexpress, winlink,  wajt-x, jtalert with all programs, , fldigi and all programs needed.
Randy ka4nma
Im good on qrz

Re: Software help

Randy Davenport
 

Im trying to learn them. I live in an no outside antenna apartment


On Thu, Apr 18, 2019, 9:45 AM Daniel Miranda <dumper.dam@...> wrote:
Hi, Randy! Please clarify: are you planning on connecting your mobile phone to the radio or using a regular Pc for that?

How are you planning to use these applications?

If your disability has to do with hearing or speaking, I think there are extra good things to enjoy from digital modes.

Best,
-- Daniel

Em qui, 18 de abr de 2019 10:21, Randy Davenport <pastor.spaceboy@...> escreveu:
I am interested in the nbems program.. I am disabled and low income. I connect to the internet on my cell phone as I have no internet at my apartment. Can someone please help me out with a CD or thumb drive with all the install programs. I am also interested in Chirp, Rmsexpress, winlink,  wajt-x, jtalert with all programs, , fldigi and all programs needed.
Randy ka4nma
Im good on qrz

Re: Software help

Randall M. Payne
 

You got the wrong Randy, not me who asked about NBEMS.

On 4/18/2019 9:45 AM, Daniel Miranda wrote:
Hi, Randy! Please clarify: are you planning on connecting your mobile phone to the radio or using a regular Pc for that?

How are you planning to use these applications?

If your disability has to do with hearing or speaking, I think there are extra good things to enjoy from digital modes.

Best,
-- Daniel

Em qui, 18 de abr de 2019 10:21, Randy Davenport <pastor.spaceboy@...> escreveu:
I am interested in the nbems program.. I am disabled and low income. I connect to the internet on my cell phone as I have no internet at my apartment. Can someone please help me out with a CD or thumb drive with all the install programs. I am also interested in Chirp, Rmsexpress, winlink,  wajt-x, jtalert with all programs, , fldigi and all programs needed.
Randy ka4nma
Im good on qrz

Virus-free. www.avg.com


--
Randy Payne K4EZM
Highlands County Florida ARES EC; WCF ASEC and ASM

Re: [winfldigi] A Solution To The Digital Mode Recognition Issue

Dave
 

The newinstall.cxx code has been changed so that the default CQ macro has been changed to:



shown on an OS-X test compilation.  CW, PSK-31, and RTTY RsID transmit are initialized to disabled for the new installation.

73, Dave, W1HKJ

On 4/18/19 1:35 PM, Tony wrote:
On 4/18/2019 3:23 AM, Dave wrote:
I will change the fldigi's default CQ macro to that shown above. That will at least assist new digital operators using fldigi to be courteous and informative.

Dave:

That's great news -- simple and effective.

Thank you.

Tony -K2MO

fldigi 4.1.03 posted

Dave
 

This is an important bug fix release.  It corrects the problem of excess CPU% usage on many h/w platforms.

You can download this version at http://www.w1hkj.com

or from Source Forge.

Version 4.1.03

  * Maintenance release

      wf updates
        correct wf update loop logic error caused fldigi/xorg cpu loading

      New install macros
        modify default CQ macro to include RsID on/off

      WinKeyer emulators
        Disable WinKey serial echo for emulators like K3NB Arduino sketch.
          - use internal timing vice waiting for sent char echo
          - may also be used with real Winkeyer h/w
          - save state of emulation in configuration file

      MACRO <MODEM:
        Add code to correctly recognize OLIVIA submodes

73, David
W1HKJ


Re: fldigi 4.1.03 posted

Frank Olaughlin
 

Dave,

 

Thanks for the update and all the work involved. I hope to have a group test this week.

 

Have a great weekend and Happy Easter.

 

73’

Frank

WQ1O

 

From: nbems@groups.io [mailto:nbems@groups.io] On Behalf Of Dave
Sent: Sunday, April 21, 2019 10:38 AM
To: Kamal Mostafa; Richard Shaw; Diane Bruce; Walter Fey; Richard
Subject: [nbems] fldigi 4.1.03 posted

 

This is an important bug fix release.  It corrects the problem of excess CPU% usage on many h/w platforms.

You can download this version at http://www.w1hkj.com

or from Source Forge.

Version 4.1.03

  * Maintenance release

      wf updates
        correct wf update loop logic error caused fldigi/xorg cpu loading

      New install macros
        modify default CQ macro to include RsID on/off

      WinKeyer emulators
        Disable WinKey serial echo for emulators like K3NB Arduino sketch.
          - use internal timing vice waiting for sent char echo
          - may also be used with real Winkeyer h/w
          - save state of emulation in configuration file

      MACRO <MODEM:
        Add code to correctly recognize OLIVIA submodes

73, David
W1HKJ

 

Re: [winfldigi] fldigi 4.1.03 posted

Dave
 

should correctly parse and execute the <MODEM:...><TX> sequence

Dave



On 4/23/19 7:11 AM, Ron via Groups.Io wrote:
Frank,

I think I've found a work around by adding a slight delay between the mode change and the TX like this.

<MODEM:THOR22>
<WAIT:00.1>
<TX>

Dave, was there a timing change that caused the modem not to change with a <TX>

73, Ron NY3J

On 4/22/19 6:31 PM, n3fll@... wrote:
I notice with version  4.1.03  that creating macro for  mode change and tx  doesn't change the mode as it does in previous versions, it
just transmits.

<MODEM:THOR22>

<TX>


Re: [winfldigi] fldigi 4.1.03 posted

Frank N3FLL
 

Dave, 

Yes it works as expected on my Win 10 computer,  thank you.  

73, 
Frank N3FLL