|
On 4/13/19 11:06 AM, Robie wrote:
All,
I'm a new user and would like to know it if FLDIGI supports
the MORTTY device for a CW interface?
Robie - AJ4F
_._,_._,_
http://www.w1hkj.com/FldigiHelp/nanoIO_page.html
I tested this using the nanoIO
Ed W3NR
|
|
|
Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
-- Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
Lee,
Not the audio port, the virtual serial port (USB connection).
Robie - AJ4F
On Sat, Apr 13, 2019 at 4:09 PM Lee Garner < Wa0uig@...> wrote: So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
Ok, good info. It's the virtual USB/Serial interface - recognized and accessed but does not stay selected in the GUI.
On Sat, Apr 13, 2019 at 12:59 PM Robie < ruler55@...> wrote: Lee,
Not the audio port, the virtual serial port (USB connection).
Robie - AJ4F
On Sat, Apr 13, 2019 at 4:09 PM Lee Garner < Wa0uig@...> wrote: So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
-- Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
toggle quoted messageShow quoted text
On Sat, Apr 13, 2019 at 6:15 PM Lee Garner < Wa0uig@...> wrote: Ok, good info. It's the virtual USB/Serial interface - recognized and accessed but does not stay selected in the GUI.
On Sat, Apr 13, 2019 at 12:59 PM Robie < ruler55@...> wrote: Lee,
Not the audio port, the virtual serial port (USB connection).
Robie - AJ4F
On Sat, Apr 13, 2019 at 4:09 PM Lee Garner < Wa0uig@...> wrote: So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
Ok! Are you FLDigi Windows based? and tell us what you have tried so far.
On Sat, Apr 13, 2019 at 1:17 PM Robie < ruler55@...> wrote:
On Sat, Apr 13, 2019 at 6:15 PM Lee Garner < Wa0uig@...> wrote: Ok, good info. It's the virtual USB/Serial interface - recognized and accessed but does not stay selected in the GUI.
On Sat, Apr 13, 2019 at 12:59 PM Robie < ruler55@...> wrote: Lee,
Not the audio port, the virtual serial port (USB connection).
Robie - AJ4F
On Sat, Apr 13, 2019 at 4:09 PM Lee Garner < Wa0uig@...> wrote: So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
-- Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
Lee,
Here's some info that will help you understand what I'm doing and what is happening:
1. I use windows 10 operating system. 2. I use N1MM + for contesting and DXLabs as my master logging program 3. I use a WinKeyer for my logging program to rig CW interface - all programs 4. I built a MORTTY to evaluate as a possible replacement for the winkeyer due to its small size and lower cost. I have successfully used it with N1MM+ and DXLabs 5. The "sketch" that is loaded into my MORTTY is a "winkeyer emulator" as I understand. It is named CW Keyer sketch on the MORTTY web page. 6, N1MM+ and DXLabs recognize the MORTTY as a "winkeyer" and work well 7. I am evaluating FLDIGI (4.0.02) as a possible program to put in my "tool kit" of ham radio software. I saw that FLDIGI will connect to a winkeyer, so I figured that it would recognize my MORTTY like the other programs do, so I tried it. and have some issues. 8. With FLDIGI configured for winkeyer on COM 3, I get the following on startup of the program
9. I close the window that shows this message and open configure/operating/winkeyer and find that the port has been set to NONE
10. I change NONE to COM 3, press connect and close
11. the MORTTY responds properly and sends CW correctly. Macros, keyboard CW and speed control all work properly.
12. I have to repeat steps 8-11 each time I open FLDIGI.
Please let me know if you have any questions,
Robie - AJ4F
On Sun, Apr 14, 2019 at 7:24 AM Lee Garner < Wa0uig@...> wrote: Ok! Are you FLDigi Windows based? and tell us what you have tried so far.
On Sat, Apr 13, 2019 at 1:17 PM Robie < ruler55@...> wrote:
On Sat, Apr 13, 2019 at 6:15 PM Lee Garner < Wa0uig@...> wrote: Ok, good info. It's the virtual USB/Serial interface - recognized and accessed but does not stay selected in the GUI.
On Sat, Apr 13, 2019 at 12:59 PM Robie < ruler55@...> wrote: Lee,
Not the audio port, the virtual serial port (USB connection).
Robie - AJ4F
On Sat, Apr 13, 2019 at 4:09 PM Lee Garner < Wa0uig@...> wrote: So it works with FLDIGI, but won't load the correct audio port on FLDIGI boot?
On Sat, Apr 13, 2019 at 11:02 AM Robie < ruler55@...> wrote: Lee,
Thanks for the feedback. Yes, I'm aware of the info you provided. I have an assembled MORTTY that is loaded with the sketch that emulates WinKeyer. It works with FLDIGI, but only if I manually reassign the port to which the mortty is connected and reconnect it each time I start FLDIGI. Is this expected behavior with this sketch installed?
I could modify the MORTTY (small physical change required to support nanoIo) and install the nanoio sketch. However, I'm not interested in that approach at this time.
Robie-AJ4F
On Sat, Apr 13, 2019 at 3:28 PM Lee Garner < Wa0uig@...> wrote: I mean....Robie
Hi Robby, at hamprojects.info. not a secure site. Mortty is a Do-It-Yourself construction project that provides a miniature enclosure and a computing platform for K0SM’s TinyFSK RTTY Keyer software or K3NG’s CW Keyer software. It optionally can be configured to run W1HKJ’s nanoIO software using fldigi.
On Sat, Apr 13, 2019 at 10:07 AM Robie < ruler55@...> wrote: All,
I'm a new user and would like to know it if FLDIGI supports the MORTTY device for a CW interface?
Robie - AJ4F
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
--
Lelia Garner | WA0UIG ARRL IA Section Manager ARRL IA Section Traffic Manager Net Manager Iowa Traffic and Emergency Net (ITEN) 3970 kHz Sunday 2300 UTC (6 PM CDT)
|
|
|
Dave
The sketch is not completely emulating the WinKeyer. It should echo the sent data string.
This is the auto startup exchange between fldigi 4.1.02 and a real WinKeyer (version 3.1):
I: WKCW_connect: WKCW_connect(ON)
I: close_wkeyer: WKEY RESET : 0x00 0x01
I: close_wkeyer: HOST CLOSE : 0x00 0x03
I: WK_start_wkey_serial:
Serial port:
Port : /dev/cu.usbserial-A600e2pL
Baud : 1200
Stopbits : 2
Timeout : 1
DTR : true
RTS/CTS : false
I: open_wkeyer: NULL_CMD : 0x13 0x13 0x13
I: WK_sendString: Sent 2: 00 01
I: WK_sendString: Sent 3: 13 13 13
I: open_wkeyer: ECHO_TEST : 0x00 0x04 0x55
I: WK_sendString: Sent 3: 00 04 55
I: WK_echo_test: passed echo test
I: open_wkeyer: Echo response in 38 msec
I: open_wkeyer: HOST_OPEN : 0x00 0x02
I: WK_sendString: Sent 2: 00 02
I: load_defaults:
mode register .... c4
CW speed ......... 24
side tone ........ 6
weight ........... 50
lead in time ..... 0
tail time ........ 0
min wpm .......... 10
rng wpm .......... 25
first ext ........ 0
key comp ......... 0
farnsworth wpm ... 0
paddle setpoint .. 50
dit dah ratio .... 50
pin config ....... 4
don't care ....... 255
hex string ....... 0x0f 0xc4 0x18 0x06 0x32 0x00 0x00 0x0a 0x19 0x00 0x00 0x00 0x32 0x32 0x04 0xff
I: WK_sendString: Sent 16: 0F C4 18 06 32 00 00 0A 19 00 00 00 32 32 04 FF
I: load_defaults: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: load_defaults: SETWPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: load_defaults:
mode register .... c4
CW speed ......... 24
side tone ........ 6
weight ........... 50
lead in time ..... 0
tail time ........ 0
min wpm .......... 10
rng wpm .......... 25
first ext ........ 0
key comp ......... 0
farnsworth wpm ... 0
paddle setpoint .. 50
dit dah ratio .... 50
pin config ....... 4
don't care ....... 255
hex string ....... 0x0f 0xc4 0x18 0x06 0x32 0x00 0x00 0x0a 0x19 0x00 0x00 0x00 0x32 0x32 0x04 0xff
I: WK_sendString: Sent 16: 0F C4 18 06 32 00 00 0A 19 00 00 00 32 32 04 FF
I: load_defaults: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: load_defaults: SETWPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: WKCW_init: GET_SPEED_POT : 0x07
I: WK_sendString: Sent 1: 07
I: WKCW_init: SET_WPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: WKCW_init: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: WKCW_init: GET_SPEED_POT : 0x07
I: WK_sendString: Sent 1: 07
73, David, W1HKJ
|
|
|
Dave,
Thanks for the feedback.
I'll move on with my evaluation.
Robie - AJ4F
On Sun, Apr 14, 2019 at 2:09 PM Dave < w1hkj@...> wrote: The sketch is not completely emulating the WinKeyer. It should echo the
sent data string.
This is the auto startup exchange between fldigi 4.1.02 and a real
WinKeyer (version 3.1):
I: WKCW_connect: WKCW_connect(ON)
I: close_wkeyer: WKEY RESET : 0x00 0x01
I: close_wkeyer: HOST CLOSE : 0x00 0x03
I: WK_start_wkey_serial:
Serial port:
Port : /dev/cu.usbserial-A600e2pL
Baud : 1200
Stopbits : 2
Timeout : 1
DTR : true
RTS/CTS : false
I: open_wkeyer: NULL_CMD : 0x13 0x13 0x13
I: WK_sendString: Sent 2: 00 01
I: WK_sendString: Sent 3: 13 13 13
I: open_wkeyer: ECHO_TEST : 0x00 0x04 0x55
I: WK_sendString: Sent 3: 00 04 55
I: WK_echo_test: passed echo test
I: open_wkeyer: Echo response in 38 msec
I: open_wkeyer: HOST_OPEN : 0x00 0x02
I: WK_sendString: Sent 2: 00 02
I: load_defaults:
mode register .... c4
CW speed ......... 24
side tone ........ 6
weight ........... 50
lead in time ..... 0
tail time ........ 0
min wpm .......... 10
rng wpm .......... 25
first ext ........ 0
key comp ......... 0
farnsworth wpm ... 0
paddle setpoint .. 50
dit dah ratio .... 50
pin config ....... 4
don't care ....... 255
hex string ....... 0x0f 0xc4 0x18 0x06 0x32 0x00 0x00 0x0a 0x19
0x00 0x00 0x00 0x32 0x32 0x04 0xff
I: WK_sendString: Sent 16: 0F C4 18 06 32 00 00 0A 19 00 00 00 32 32 04 FF
I: load_defaults: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: load_defaults: SETWPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: load_defaults:
mode register .... c4
CW speed ......... 24
side tone ........ 6
weight ........... 50
lead in time ..... 0
tail time ........ 0
min wpm .......... 10
rng wpm .......... 25
first ext ........ 0
key comp ......... 0
farnsworth wpm ... 0
paddle setpoint .. 50
dit dah ratio .... 50
pin config ....... 4
don't care ....... 255
hex string ....... 0x0f 0xc4 0x18 0x06 0x32 0x00 0x00 0x0a 0x19
0x00 0x00 0x00 0x32 0x32 0x04 0xff
I: WK_sendString: Sent 16: 0F C4 18 06 32 00 00 0A 19 00 00 00 32 32 04 FF
I: load_defaults: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: load_defaults: SETWPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: WKCW_init: GET_SPEED_POT : 0x07
I: WK_sendString: Sent 1: 07
I: WKCW_init: SET_WPM 24 : 0x02 0x18
I: WK_sendString: Sent 2: 02 18
I: WKCW_init: SET_SPEED_POT : 0x05 0x0a 0x19 0xff
I: WK_sendString: Sent 4: 05 0A 19 FF
I: WKCW_init: GET_SPEED_POT : 0x07
I: WK_sendString: Sent 1: 07
73, David, W1HKJ
|
|
|
On 4/14/19 9:36 AM, Robie wrote:
Lee,
Here's some info that will help you understand what I'm
doing and what is happening:
1. I use windows 10 operating system.
2. I use N1MM + for contesting and DXLabs as my master
logging program
3. I use a WinKeyer for my logging program to rig CW
interface - all programs
4. I built a MORTTY to evaluate as a possible replacement
for the winkeyer due to its small size and lower cost. I have
successfully used it with N1MM+ and DXLabs
5. The "sketch" that is loaded into my MORTTY is a
"winkeyer emulator" as I understand. It is named CW Keyer sketch on the MORTTY web page.
6, N1MM+ and DXLabs recognize the MORTTY as a "winkeyer"
and work well
7. I am evaluating FLDIGI (4.0.02) as a possible program to
put in my "tool kit" of ham radio software. I saw that FLDIGI
will connect to a winkeyer, so I figured that it would
recognize my MORTTY like the other programs do, so I tried it.
and have some issues.
8. With FLDIGI configured for winkeyer on COM 3, I get the
following on startup of the program
9. I close the window that shows this message and open
configure/operating/winkeyer and find that the port has been
set to NONE
10. I change NONE to COM 3, press connect and close
11. the MORTTY responds properly and sends CW correctly.
Macros, keyboard CW and speed control all work properly.
12. I have to repeat steps 8-11 each time I open FLDIGI.
Please let me know if you have any questions,
Robie - AJ4F
Try Save and then Close. Under the Configuration tab select Save
Config.
Ed W3NR
|
|
|
Ed,
I've tried that and the result is generation of the same error as shown above
Robie - AJ4F
On Sun, Apr 14, 2019 at 2:19 PM Ed W3NR < autek@...> wrote:
On 4/14/19 9:36 AM, Robie wrote:
Lee,
Here's some info that will help you understand what I'm
doing and what is happening:
1. I use windows 10 operating system.
2. I use N1MM + for contesting and DXLabs as my master
logging program
3. I use a WinKeyer for my logging program to rig CW
interface - all programs
4. I built a MORTTY to evaluate as a possible replacement
for the winkeyer due to its small size and lower cost. I have
successfully used it with N1MM+ and DXLabs
5. The "sketch" that is loaded into my MORTTY is a
"winkeyer emulator" as I understand. It is named CW Keyer sketch on the MORTTY web page.
6, N1MM+ and DXLabs recognize the MORTTY as a "winkeyer"
and work well
7. I am evaluating FLDIGI (4.0.02) as a possible program to
put in my "tool kit" of ham radio software. I saw that FLDIGI
will connect to a winkeyer, so I figured that it would
recognize my MORTTY like the other programs do, so I tried it.
and have some issues.
8. With FLDIGI configured for winkeyer on COM 3, I get the
following on startup of the program
9. I close the window that shows this message and open
configure/operating/winkeyer and find that the port has been
set to NONE
10. I change NONE to COM 3, press connect and close
11. the MORTTY responds properly and sends CW correctly.
Macros, keyboard CW and speed control all work properly.
12. I have to repeat steps 8-11 each time I open FLDIGI.
Please let me know if you have any questions,
Robie - AJ4F
Try Save and then Close. Under the Configuration tab select Save
Config.
Ed W3NR
|
|
|
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
|
|
|
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
|
|
|
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
|
|
|
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?
|
|
|
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
|
|
|
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
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
|
|
|
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
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
|
|
|
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
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
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
|
|
|
