Date   

Re: Winkey PTT momentary dropout

Steve London
 

Could be an internal Winkey buffer issue with the long exchange. If it's reproducible, you might want to contact K1EL.

73,
Steve, N2IC

On 11/10/2015 07:13 AM, 'Dave Hachadorian' k6ll.dave@... [N1MMLoggerplus] wrote:
That’s exactly where mine was dropping out – between 59 and AZ!
N2IC’s description of Winkey PTT as more like a VOX doesn’t exactly fit
with reality here. Yesterday I made a macro with “1 2” That’s five
spaces between the 1 and the 2, and PTT did not drop out, even with tail
time of zero, which I have been using for a couple of years.
Dave Hachadorian, K6LL
Yuma, AZ

*From:* mailto:N1MMLoggerplus@...
*Sent:* Tuesday, November 10, 2015 5:40 AM
*To:* N1MMLoggerplus@...
<mailto:N1MMLoggerplus@...>
*Subject:* Re: [N1MMLoggerplus] Re: Winkey PTT momentary dropout

My Winkey was dropping PTT in RUN mode in the middle of my EXCH, between
"65" and "ENY". I'll fiddle with the Winkey settings but I don't
remember ever experiencing that before in a contest.
73, Barry N1EU
On Mon, Nov 9, 2015 at 8:51 PM, ve3ki@... <mailto:ve3ki@...>
[N1MMLoggerplus] <N1MMLoggerplus@...
<mailto:N1MMLoggerplus@...>> wrote:

__

Some things to look for: Did that only happen in run mode, or also
in S&P? Was the dropout perhaps between F5 and F2 in run mode? That
might help pin it down.

73,
Rich VE3KI


---In N1MMLoggerplus@...
<mailto:N1MMLoggerplus@...>, <k6ll.dave@...> wrote :

I noticed during SS that my Winkey PTT was momentarily dropping
out when I was sending my exchange. To get around the issue
during the contest, I just turned on VOX. Experimenting with it
today, I see that if I increase the Winkey Tail Time setting to
7, the PTT dropout no longer occurs. That setting had been zero
during the contest. I'll just leave it as 7, but I think
something has changed. My exchange macro is just the usual # U *
59 AZ. N1MM version is 5289.

Dave Hachadorian, K6LL
Yuma, AZ


Re: Winkey PTT momentary dropout

Dave Hachadorian
 

That’s exactly where mine was dropping out – between 59 and AZ!
 
N2IC’s description of Winkey PTT as more like a VOX doesn’t exactly fit with reality here.  Yesterday I made a macro with “1     2”  That’s five spaces between the 1 and the 2, and PTT did not drop out, even with tail time of zero, which I have been using for a couple of years.
 
Dave Hachadorian, K6LL
Yuma, AZ

 

Sent: Tuesday, November 10, 2015 5:40 AM
Subject: Re: [N1MMLoggerplus] Re: Winkey PTT momentary dropout
 
 

My Winkey was dropping PTT in RUN mode in the middle of my EXCH, between "65" and "ENY".  I'll fiddle with the Winkey settings but I don't remember ever experiencing that before in a contest.
 
73, Barry N1EU
 
On Mon, Nov 9, 2015 at 8:51 PM, ve3ki@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:
 

Some things to look for: Did that only happen in run mode, or also in S&P? Was the dropout perhaps between F5 and F2 in run mode? That might help pin it down.

 
73,
Rich VE3KI


---In N1MMLoggerplus@..., wrote :

I noticed during SS that my Winkey PTT was momentarily dropping
out when I was sending my exchange. To get around the issue
during the contest, I just turned on VOX. Experimenting with it
today, I see that if I increase the Winkey Tail Time setting to
7, the PTT dropout no longer occurs. That setting had been zero
during the contest. I'll just leave it as 7, but I think
something has changed. My exchange macro is just the usual # U *
59 AZ. N1MM version is 5289.

Dave Hachadorian, K6LL
Yuma, AZ
 


New file uploaded to N1MMLoggerplus

N1MMLoggerplus@...
 

Hello,


This email message is a notification to let you know that
a file has been uploaded to the Files area of the N1MMLoggerplus
group.


File : /USVE_SCP/MAS_SS.scp
Uploaded by : n7wy@... <n7wy@...>
Description : Conflation of US and Canada calls from the Arizona Outlaws history provided by N2IC and MASTER.SCP of Nov 2015


You can access this file at the URL:
https://groups.yahoo.com/neo/groups/N1MMLoggerplus/files/USVE_SCP/MAS_SS.scp


To learn more about file sharing for your group, please visit:
https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398


Regards,


n7wy@... <n7wy@...>


Re: New install problems

k3ui@...
 

Thank you. That solved the CW keying problem, but now I have a problem getting RTTY to work. I have reconnected the Rascal, but now it does nothing.
 
Richard
K3UI


From: "ve3ki@... [N1MMLoggerplus]" To: N1MMLoggerplus@...
Sent: Monday, November 9, 2015 8:44:03 PM
Subject: [N1MMLoggerplus] Re: New install problems

 

First, disconnect the Rascal temporarily from the radio. Now start N1MM+. In the Configurer, make sure that the only check mark in the CW/Other column is beside the Rascal's com port and not beside the radio control com port. In the setup for the radio port, make sure DTR and RTS are not set to PTT or CW. In the setup for the Rascal port, make sure DTR and RTS are not set to Always On; they should be set to CW and PTT respectively. Once you have done that and exited the Configurer, try reconnecting the Rascal to the radio.


73,
Rich VE3KI


---In N1MMLoggerplus@..., wrote :

I have had difficulty installing N1MM. When I perform a clean install my radio begins to key the moment the N1MM Logger+ program starts. I must be missing something simple, but I am missing something. I have an ICOM 756PROIII, using a Rascal for an interface device. I have a separate cable for rig control. Any pointers where to look?

 

 

     V/R

 

     Richard

     K3UI

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

 

 

 

 



Re: Macros and Choppy CW

Vytenis LY5T
 

A year or so ago I sent a message to this newsgroup with exactly same problem: ATEN USB-Serial converter, Prolific chip and choppy CW. Changing USB/Serial converter to true PCI COM port (that was a desktop PC) solved problem.
Beside that, updating driver from Prolific site was not possible. Only ATEN driver was applicable. And it was faulty.

Vytenis
ly5t


---In N1MMLoggerplus@..., <w2cdo@...> wrote :

Tom,

 

I’ve done a bit of sleuthing and found some interesting things: first, I’ve been using an ATEN USB-Serial device and a *Prolific* driver since the beginning.  This is something I didn’t know.  The WinKeyer USB uses the FTDI driver and chipset on COM4 and I must have been looking at that instead of the USB-Serial device on COM6 connected to the Mark V CAT.  That said and contrary to the experience of many, the Prolific driver has worked for me (HP 500-205t i3-4350 CUP @ 3.60 GHz, 8 GB RAM, Win 10/64) so far. (Yes, I know I’m jinxing myself by saying this out loud.) Testing with only the Mark V at ~ 30 Watts I had no problem going between F keys and the manual keying.  Kicking in the Alpha brought on the symptoms so the answer seems to be that RFI is affecting the device.  I’ll wrap the stuff in tinfoil and install toroids to protect the connection.  And replace most of my interconnect coax for good measure.  Just in case it all stops working, can you remind me which USB-Serial adapters use the FTDI chipset?

 

Thanks,

 

Peter W2CDO

 

p.s., Out of curiosity, can you tell me what this means: “Device USB\VID_0557&PID_2008\6&ba9edbb&0&1 requires further installation”?  It shows up in the Information window under the Port’s Events tab and the Event Viewer provides the following: “Driver Management concluded the process to install driver ser2at.inf_amd64_2208228bed2dedb3\ser2at.inf for Device Instance ID USB\VID_0557&PID_2008\6&BA9EDBB&0&1 with the following status: 0x0.”  The Event Log Online Help link goes to a “Page Not Found” on MS TechNet.

 

P.

 

Sent from Mail for Windows 10

 

 


From: N1MM tfwagner@... [N1MMLoggerplus]
Sent: Monday, November 9, 2015 3:33 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Re: Macros and Choppy CW

 

 

 

Please report your results, good or bad.

This article used to be linked in the doc and the link got broken.

http://knowledge.digi.com/articles/Knowledge_Base_Article/Optimizing-USB-to-serial-port-settings

Tom - N1MM

On 11/9/2015 3:29 PM, Peter Alterman w2cdo@... [N1MMLoggerplus] wrote:
>
> Will do, Tom. Thanks.
>
> Peter
>
> Sent from Mail <http://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
> *From: *N1MM tfwagner@... [N1MMLoggerplus]
> *Sent: *Monday, November 9, 2015 3:08 PM
> *To: *N1MMLoggerplus@...
> *Subject: *Re: [N1MMLoggerplus] Re: Macros and Choppy CW
>
> Try fiddling with the advanced settings in the FTDI driver for that
> "serial" port.
>
> Try very low receive/transmit bytes and 1 msec for the latency timer. I
> doubt timeout or the checkbox options will help.
>
> If you don't see any change, reset to defaults.
>
> 73,
> Tom - N1MM
>
> On 11/9/2015 2:52 PM, Peter Alterman w2cdo@... [N1MMLoggerplus]
> wrote:
> >
> > I’m one of those having trouble with choppy CW the first few
> > characters I send. Then it settles down after that. I use the FTDI
> > chip and current driver and Winkeyer. Have had this problem from the
> > very beginning of use of +. I figure it’s got to be a setting on the
> > virtual com port.
> >
> > Peter W2CDO
> >
> > Sent from Mail <http://go.microsoft.com/fwlink/?LinkId=550986> for
> > Windows 10
> >
> >
> > *From: *drew.vonadasmith@... [N1MMLoggerplus]
> > *Sent: *Monday, November 9, 2015 1:50 PM
> > *To: *N1MMLoggerplus@...
> > *Subject: *RE: [N1MMLoggerplus] Re: Macros and Choppy CW
> >
> > Audio might be the most obvious preemptive Windows event, but it isn't
> > the only one. Serial CW generation works fine for you, and probably
> > works for most people, but it does not work for everyone, audio or
> > otherwise.
> >
> > Winkey is the gold standard for good reasons.
> >
> > 73,
> >
> > Drew K3PA
> >
> >
> >
> > ---In N1MMLoggerplus@..., <aldermant@...> wrote :
> >
> > Being very polite --- That is total hogwash Rick!!
> >
> > For years, I have run 100 + wpm QSO's using Windows 95 to the current
> > Windows 10 and I never have problems with NL+ macros nor with choppy
> > CW, no matter what CW generation application I use.
> >
> > Understand how a computer works! The reason the serial port (or any PC
> > I/O port) will cause CW generation to be 'choppy' or to 'stutter' is
> > simply because when a CPU generates audio, it shuts all I/O ports
> > (meaning serial/parallel ports) OFF, generates the audio, and then
> > turns the I/O port ON again. The simple solution is to go into Windows
> > set-up and turn OFF the PC's internally generated audio.
> >
> > The under informed will spend their nickel's to 'go buy a solution'; I
> > prefer to save my nickel to buy another bottle of wine. YMMV!!
> >
> > 73,
> > Tom - W4BQF
> >
> >
> > -----Original Message-----
> > From: N1MMLoggerplus@...
> > <mailto:N1MMLoggerplus@...>
> > [mailto:N1MMLoggerplus@...
> > <mailto:N1MMLoggerplus@...>]
> > Sent: Monday, November 9, 2015 11:56 AM
> > To: k4ie_tom@... <mailto:k4ie_tom@...>
> > Cc: N1MMLoggerplus@...
> <mailto:N1MMLoggerplus@...>
> > Subject: [N1MMLoggerplus] Re: Macros and Choppy CW
> >
> >
> >
> > Sending CW through any serial port - real or USB-adapted - is hit or
> > miss. Some versions of some logging programs will work with some ports
> > on some releases of some operating systems at some maximum system load
> > that depends on the CPU type, the nature of other programs running at
> > the same time, and the amount of I/O they are performing. (Most
> > notable here is Telnet spotting in a contest like SS in which many
> > operators spot every S&P QSO they make! The load is huge.)
> >
> > Please, bite the bullet and get an external keyer that accepts ASCII
> > characters from the logger and forms dots and dashes outside the
> > computer CPU. Generating Morse Code is a real-time computing activity.
> > Windows was never intended to do real-time computing and, when asked,
> > doesn't do it very well. MM is one of the best at taming the beast but
> > some combinations of the factors listed above will confound even MM.
> > External keyers are nearly timing-independent. A Winkeyer USB is cheap
> > and reliable and will save you hours of frustration. There are many
> > alternative external keyers as well. I use a YCCC SO2R Box Plus.
> > Microham and other keyers and SO2R boxes work fine, too.
> >
> > GL & 73,
> >
> > /Rick N6XI
> >
> >
> > --
> >
> > Rick Tavan N6XI
> > Truckee, CA
> >
> >
>
>

 

 


Re: Winkey PTT momentary dropout

Barry N1EU
 

My Winkey was dropping PTT in RUN mode in the middle of my EXCH, between "65" and "ENY".  I'll fiddle with the Winkey settings but I don't remember ever experiencing that before in a contest.

73, Barry N1EU

On Mon, Nov 9, 2015 at 8:51 PM, ve3ki@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:
 

Some things to look for: Did that only happen in run mode, or also in S&P? Was the dropout perhaps between F5 and F2 in run mode? That might help pin it down.


73,
Rich VE3KI


---In N1MMLoggerplus@..., wrote :

I noticed during SS that my Winkey PTT was momentarily dropping
out when I was sending my exchange. To get around the issue
during the contest, I just turned on VOX. Experimenting with it
today, I see that if I increase the Winkey Tail Time setting to
7, the PTT dropout no longer occurs. That setting had been zero
during the contest. I'll just leave it as 7, but I think
something has changed. My exchange macro is just the usual # U *
59 AZ. N1MM version is 5289.

Dave Hachadorian, K6LL
Yuma, AZ



Re: Macros and Choppy CW

Peter Alterman W2CDO
 

Tom,

 

I’ve done a bit of sleuthing and found some interesting things: first, I’ve been using an ATEN USB-Serial device and a *Prolific* driver since the beginning.  This is something I didn’t know.  The WinKeyer USB uses the FTDI driver and chipset on COM4 and I must have been looking at that instead of the USB-Serial device on COM6 connected to the Mark V CAT.  That said and contrary to the experience of many, the Prolific driver has worked for me (HP 500-205t i3-4350 CUP @ 3.60 GHz, 8 GB RAM, Win 10/64) so far. (Yes, I know I’m jinxing myself by saying this out loud.) Testing with only the Mark V at ~ 30 Watts I had no problem going between F keys and the manual keying.  Kicking in the Alpha brought on the symptoms so the answer seems to be that RFI is affecting the device.  I’ll wrap the stuff in tinfoil and install toroids to protect the connection.  And replace most of my interconnect coax for good measure.  Just in case it all stops working, can you remind me which USB-Serial adapters use the FTDI chipset?

 

Thanks,

 

Peter W2CDO

 

p.s., Out of curiosity, can you tell me what this means: “Device USB\VID_0557&PID_2008\6&ba9edbb&0&1 requires further installation”?  It shows up in the Information window under the Port’s Events tab and the Event Viewer provides the following: “Driver Management concluded the process to install driver ser2at.inf_amd64_2208228bed2dedb3\ser2at.inf for Device Instance ID USB\VID_0557&PID_2008\6&BA9EDBB&0&1 with the following status: 0x0.”  The Event Log Online Help link goes to a “Page Not Found” on MS TechNet.

 

P.

 

Sent from Mail for Windows 10

 

 


From: N1MM tfwagner@... [N1MMLoggerplus]
Sent: Monday, November 9, 2015 3:33 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Re: Macros and Choppy CW

 

 

 

Please report your results, good or bad.

This article used to be linked in the doc and the link got broken.

http://knowledge.digi.com/articles/Knowledge_Base_Article/Optimizing-USB-to-serial-port-settings

Tom - N1MM

On 11/9/2015 3:29 PM, Peter Alterman w2cdo@... [N1MMLoggerplus] wrote:
>
> Will do, Tom. Thanks.
>
> Peter
>
> Sent from Mail for
> Windows 10
>
>
> *From: *N1MM tfwagner@... [N1MMLoggerplus]
> *Sent: *Monday, November 9, 2015 3:08 PM
> *To: *N1MMLoggerplus@...
> *Subject: *Re: [N1MMLoggerplus] Re: Macros and Choppy CW
>
> Try fiddling with the advanced settings in the FTDI driver for that
> "serial" port.
>
> Try very low receive/transmit bytes and 1 msec for the latency timer. I
> doubt timeout or the checkbox options will help.
>
> If you don't see any change, reset to defaults.
>
> 73,
> Tom - N1MM
>
> On 11/9/2015 2:52 PM, Peter Alterman w2cdo@... [N1MMLoggerplus]
> wrote:
> >
> > I’m one of those having trouble with choppy CW the first few
> > characters I send. Then it settles down after that. I use the FTDI
> > chip and current driver and Winkeyer. Have had this problem from the
> > very beginning of use of +. I figure it’s got to be a setting on the
> > virtual com port.
> >
> > Peter W2CDO
> >
> > Sent from Mail for
> > Windows 10
> >
> >
> > *From: *drew.vonadasmith@... [N1MMLoggerplus]
> > *Sent: *Monday, November 9, 2015 1:50 PM
> > *To: *N1MMLoggerplus@...
> > *Subject: *RE: [N1MMLoggerplus] Re: Macros and Choppy CW
> >
> > Audio might be the most obvious preemptive Windows event, but it isn't
> > the only one. Serial CW generation works fine for you, and probably
> > works for most people, but it does not work for everyone, audio or
> > otherwise.
> >
> > Winkey is the gold standard for good reasons.
> >
> > 73,
> >
> > Drew K3PA
> >
> >
> >
> > ---In N1MMLoggerplus@..., wrote :
> >
> > Being very polite --- That is total hogwash Rick!!
> >
> > For years, I have run 100 + wpm QSO's using Windows 95 to the current
> > Windows 10 and I never have problems with NL+ macros nor with choppy
> > CW, no matter what CW generation application I use.
> >
> > Understand how a computer works! The reason the serial port (or any PC
> > I/O port) will cause CW generation to be 'choppy' or to 'stutter' is
> > simply because when a CPU generates audio, it shuts all I/O ports
> > (meaning serial/parallel ports) OFF, generates the audio, and then
> > turns the I/O port ON again. The simple solution is to go into Windows
> > set-up and turn OFF the PC's internally generated audio.
> >
> > The under informed will spend their nickel's to 'go buy a solution'; I
> > prefer to save my nickel to buy another bottle of wine. YMMV!!
> >
> > 73,
> > Tom - W4BQF
> >
> >
> > -----Original Message-----
> > From: N1MMLoggerplus@...
> >
> > [mailto:N1MMLoggerplus@...
> > ]
> > Sent: Monday, November 9, 2015 11:56 AM
> > To: k4ie_tom@...
> > Cc: N1MMLoggerplus@...
>
> > Subject: [N1MMLoggerplus] Re: Macros and Choppy CW
> >
> >
> >
> > Sending CW through any serial port - real or USB-adapted - is hit or
> > miss. Some versions of some logging programs will work with some ports
> > on some releases of some operating systems at some maximum system load
> > that depends on the CPU type, the nature of other programs running at
> > the same time, and the amount of I/O they are performing. (Most
> > notable here is Telnet spotting in a contest like SS in which many
> > operators spot every S&P QSO they make! The load is huge.)
> >
> > Please, bite the bullet and get an external keyer that accepts ASCII
> > characters from the logger and forms dots and dashes outside the
> > computer CPU. Generating Morse Code is a real-time computing activity.
> > Windows was never intended to do real-time computing and, when asked,
> > doesn't do it very well. MM is one of the best at taming the beast but
> > some combinations of the factors listed above will confound even MM.
> > External keyers are nearly timing-independent. A Winkeyer USB is cheap
> > and reliable and will save you hours of frustration. There are many
> > alternative external keyers as well. I use a YCCC SO2R Box Plus.
> > Microham and other keyers and SO2R boxes work fine, too.
> >
> > GL & 73,
> >
> > /Rick N6XI
> >
> >
> > --
> >
> > Rick Tavan N6XI
> > Truckee, CA
> >
> >
>
>

 

 


Re: SO2V and TS-590

Dmitry Nas
 

ok John, i will try connect sdr receiver to ts-590 for listen vfo-a
thanks for answers!

Dmitry UR4QRH

2015-11-10 13:10 GMT+02:00 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...>:

 

Dmitry,

 

Calling CQ on VFOA, switching to VFOB (no longer listening to VFOA for answer to your CQ), the radio switching back to VFOA after the CQ repeat time expires, then transmitting on VFOA again without listening first, is not supported.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 5:51 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] SO2V and TS-590

 

 

Thank you John for answer!

Yes 590 is only one receiver,
but it probably would make sense to work on searching on vfo-b during  pauses between cq on vfo-a ?

Dmitry UR4QRH

 

2015-11-10 12:35 GMT+02:00 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...>:

 

Dmitry,

 

I don’t think the TS-590 is a dual receiver radio. The transmitter moves to VFOB when you listen on VFOB. The SO2V features are not enabled for this radio.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 2:30 AM
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] SO2V and TS-590

 

 

Hello to all!

Can anybody used so2v mode and ts-590?
problem if i run CQ on vfo-A and time auto cq is 10s, change key "Pause" to vfo-B but auto CQ cannot continue on vfo-a after 10s. :(

Dmitry UR4QRH

 



1.0.5295

N1MM <tfwagner@...>
 

Version 1.0.5295 (November 10, 2015)

1. AutoHotkey integration: Added support for 64 bit installations
(W4BQF) (Coded by KU7T)
2. AutoHotKey integration: Don't allow a .exe to be an AHK file. (Coded
by N2IC)
3. AutoHotKey integration: Don't terminate existing AHK invocation when
N1MM+ is started and no N1MM+ AHK file is specified. (N6XI) (Coded
by N2IC)
4. WAG: ADIF import did not import the section field correctly.
(LX2BE)(Coded by K3CT)
5. PSK MultiRX: window was not reopening if program was closed by
closing the Entry Window. Corrected (Coded by N2AMG)


Re: Garbled SS exchange message

Irwin Darack
 

John,

Thanks. 

My computer is running Win 10 and this was an upgrade from Win 7.  No other programs were running at the time. 

See you tonight.

Irwin


On Tuesday, November 10, 2015, 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:
 

Irwin,

 

There are USB to COM converters that have unpredictable or uncontrollable latency. Use this article, let us know where the latency is currently set. If necessary, change it to 1ms.


http://knowledge.digi.com/articles/Knowledge_Base_Article/Optimizing-USB-to-serial-port-settings

 

Describe your computer (CPU speed & type, memory).
Is Windows the native OS?

Were you running any other software on this computer at the same time?

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Monday, November 09, 2015 6:38 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Garbled SS exchange message

 

 

John,

 

Keying CW straight from my computer to my Elecraft K3S. No intermediate device. I am using the sound card and USB interface  built into the new K3S. I am not sure if this is the problem as its the first time I have used the new radio in a CW contest. My old radio was a K3. For some reason N1MM+ would send a garbled letter. It could be a timing a effect between my computer and the K3S? 

 

Operating system is a Win 10. 

 

Irwin KD3TB

 


On Monday, November 9, 2015, 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Irwin & Steve,

 

What are you guys using to send CW?

If a WinKey, tell us the type (genuine K1EL WinKey, 3rd party, etc).

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, November 08, 2015 10:17 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Garbled SS exchange message

 

 

I have a few hundred contacts in the SS CW. In perhaps four instances the 5 was dropped from my check of 65.

Steve, K8JQ

On 11/7/2015 11:07 PM, Irwin Darack idarack@... [N1MMLoggerplus] wrote:

 

Bud,

I have noticed that N1MM+ is having problems with sending CW. I replaced {MYCALL} with my actual call in the macro and this seemed to solve the problem. Not sure why this is happening as it has not happened in the past.

Irwin KD3TB

 

On Sat, Nov 7, 2015 at 7:04 PM, Tom Wagner tfwagner@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Try # B {MYCALL} 70 EPA

On 11/7/2015 6:46 PM, aa3b.bud@... [N1MMLoggerplus] wrote:

 

I am having an intermittent but frequent issue with the "Run" exchange message in SSCW.

 

My F2 exchange message is as follows: {#} B {MYCALL} 70 EPA

 

The message transmits ok through 70, but then gets garbled.  The typical garbled character stream is 70 0 E which is shown in the logging window.

 

N1MM+ Logger plus V1.0.5289.0
Windows 10
MK2R+
IC7800

 

I have only seen the problem on the "RUN" exchange message.  All others are ok so far.

 

Any help?

 

73, Bud AA3B

 

 

 




--

Irwin KD3TB

 



--
Irwin KD3TB



--
Irwin KD3TB


Re: SO2V and TS-590

John Bednar
 

Dmitry,

 

Calling CQ on VFOA, switching to VFOB (no longer listening to VFOA for answer to your CQ), the radio switching back to VFOA after the CQ repeat time expires, then transmitting on VFOA again without listening first, is not supported.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 5:51 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] SO2V and TS-590

 

 

Thank you John for answer!

Yes 590 is only one receiver,
but it probably would make sense to work on searching on vfo-b during  pauses between cq on vfo-a ?

Dmitry UR4QRH

 

2015-11-10 12:35 GMT+02:00 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...>:

 

Dmitry,

 

I don’t think the TS-590 is a dual receiver radio. The transmitter moves to VFOB when you listen on VFOB. The SO2V features are not enabled for this radio.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 2:30 AM
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] SO2V and TS-590

 

 

Hello to all!

Can anybody used so2v mode and ts-590?
problem if i run CQ on vfo-A and time auto cq is 10s, change key "Pause" to vfo-B but auto CQ cannot continue on vfo-a after 10s. :(

Dmitry UR4QRH

 


Re: Garbled SS exchange message

John Bednar
 

Irwin,

 

There are USB to COM converters that have unpredictable or uncontrollable latency. Use this article, let us know where the latency is currently set. If necessary, change it to 1ms.


http://knowledge.digi.com/articles/Knowledge_Base_Article/Optimizing-USB-to-serial-port-settings

 

Describe your computer (CPU speed & type, memory).
Is Windows the native OS?

Were you running any other software on this computer at the same time?

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Monday, November 09, 2015 6:38 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Garbled SS exchange message

 

 

John,

 

Keying CW straight from my computer to my Elecraft K3S. No intermediate device. I am using the sound card and USB interface  built into the new K3S. I am not sure if this is the problem as its the first time I have used the new radio in a CW contest. My old radio was a K3. For some reason N1MM+ would send a garbled letter. It could be a timing a effect between my computer and the K3S? 

 

Operating system is a Win 10. 

 

Irwin KD3TB

 


On Monday, November 9, 2015, 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

Irwin & Steve,

 

What are you guys using to send CW?

If a WinKey, tell us the type (genuine K1EL WinKey, 3rd party, etc).

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, November 08, 2015 10:17 AM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Garbled SS exchange message

 

 

I have a few hundred contacts in the SS CW. In perhaps four instances the 5 was dropped from my check of 65.

Steve, K8JQ

On 11/7/2015 11:07 PM, Irwin Darack idarack@... [N1MMLoggerplus] wrote:

 

Bud,

I have noticed that N1MM+ is having problems with sending CW. I replaced {MYCALL} with my actual call in the macro and this seemed to solve the problem. Not sure why this is happening as it has not happened in the past.

Irwin KD3TB

 

On Sat, Nov 7, 2015 at 7:04 PM, Tom Wagner tfwagner@... [N1MMLoggerplus]

 

Try # B {MYCALL} 70 EPA

On 11/7/2015 6:46 PM, aa3b.bud@... [N1MMLoggerplus] wrote:

 

I am having an intermittent but frequent issue with the "Run" exchange message in SSCW.

 

My F2 exchange message is as follows: {#} B {MYCALL} 70 EPA

 

The message transmits ok through 70, but then gets garbled.  The typical garbled character stream is 70 0 E which is shown in the logging window.

 

N1MM+ Logger plus V1.0.5289.0
Windows 10
MK2R+
IC7800

 

I have only seen the problem on the "RUN" exchange message.  All others are ok so far.

 

Any help?

 

73, Bud AA3B

 

 

 




--

Irwin KD3TB

 



--
Irwin KD3TB


Re: SO2V and TS-590

Dmitry Nas
 

Thank you John for answer!

Yes 590 is only one receiver,
but it probably would make sense to work on searching on vfo-b during  pauses between cq on vfo-a ?

Dmitry UR4QRH

2015-11-10 12:35 GMT+02:00 'John Bednar' k3ct@... [N1MMLoggerplus] <N1MMLoggerplus@...>:

 

Dmitry,

 

I don’t think the TS-590 is a dual receiver radio. The transmitter moves to VFOB when you listen on VFOB. The SO2V features are not enabled for this radio.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 2:30 AM
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] SO2V and TS-590

 

 

Hello to all!

Can anybody used so2v mode and ts-590?
problem if i run CQ on vfo-A and time auto cq is 10s, change key "Pause" to vfo-B but auto CQ cannot continue on vfo-a after 10s. :(

Dmitry UR4QRH



Re: SO2V and TS-590

John Bednar
 

Dmitry,

 

I don’t think the TS-590 is a dual receiver radio. The transmitter moves to VFOB when you listen on VFOB. The SO2V features are not enabled for this radio.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Tuesday, November 10, 2015 2:30 AM
To: n1mmloggerplus@...
Subject: [N1MMLoggerplus] SO2V and TS-590

 

 

Hello to all!

Can anybody used so2v mode and ts-590?
problem if i run CQ on vfo-A and time auto cq is 10s, change key "Pause" to vfo-B but auto CQ cannot continue on vfo-a after 10s. :(

Dmitry UR4QRH


SO2V and TS-590

Dmitry Nas
 

Hello to all!

Can anybody used so2v mode and ts-590?
problem if i run CQ on vfo-A and time auto cq is 10s, change key "Pause" to vfo-B but auto CQ cannot continue on vfo-a after 10s. :(


Dmitry UR4QRH


Re: No cw output from TS-590S using N1MM+

Jim W7RY
 

You could TRY a Winkeyer but don’t hold out much hope...  VMWare (player) on windows is touch and go when it comes to USB devices. Been there done that. DTMF wont decode in VMWare Player.
 
73
Jim W7RY
 
 
 

Sent: Monday, November 09, 2015 6:49 PM
Subject: [N1MMLoggerplus] No cw output from TS-590S using N1MM+
 
 

I’m using a Windows 8.1 virtual machine client (VMWare) with a 2012 Mac Mini for N1MM Plus. It is working well except that I don’t have any cw output. The PTT is keyed for varying lengths depending on the message size programmed to the F-Keys however. At this point I’m assuming I’ll need to use a FTDI USB to RS232 cable, break out the DTR line and use this to drive a 2N2222 or the like and output to the key jack. Searching around I’ve read this will and will not work. Just wondering if anyone out there has this setup working or knows the reason I’m not getting any output with my current setup?

73
Pete - kw9e


Re: Winkey PTT momentary dropout

gbyahoo@...
 

Joe,

My guess is that you have the radio set to control PTT for timeouts - eg) something VOX like.
(But then, I have always been poor at guessing!)

>> Gerald, VE1DT


---In N1MMLoggerplus@..., <nss@...> wrote :

Interesting because I have mine all at zero and have never had it drop out at the wrong time.

Joe WB9SBD


On 11/9/2015 8:10 PM, Steve London n2ic@... [N1MMLoggerplus] wrote:
On CW, N1MM+ has no direct control of the Winkey PTT, other than telling 
the Winkey the tail time that the Winkey should be using. After that, 
the Winkey autonomously drops PTT when it thinks there is a sufficiently 
long space between characters.

Personally, I don't like Winkey PTT. A better name for it would be 
Winkey VOX, since it can, and will, drop out between characters in the 
same message if the tail time is set too low. In that sense, tail time 
is really like VOX delay.

73,
Steve, N2IC

On 11/09/2015 06:51 PM, ve3ki@... [N1MMLoggerplus] wrote:
Some things to look for: Did that only happen in run mode, or also in
S&P? Was the dropout perhaps between F5 and F2 in run mode? That might
help pin it down.


73,
Rich VE3KI


---In N1MMLoggerplus@..., <k6ll.dave@...> wrote :

I noticed during SS that my Winkey PTT was momentarily dropping
out when I was sending my exchange. To get around the issue
during the contest, I just turned on VOX. Experimenting with it
today, I see that if I increase the Winkey Tail Time setting to
7, the PTT dropout no longer occurs. That setting had been zero
during the contest. I'll just leave it as 7, but I think
something has changed. My exchange macro is just the usual # U *
59 AZ. N1MM version is 5289.

Dave Hachadorian, K6LL
Yuma, AZ







Re: Winkey PTT momentary dropout

Joe WB9SBD
 

Interesting because I have mine all at zero and have never had it drop out at the wrong time.

Joe WB9SBD


On 11/9/2015 8:10 PM, Steve London n2ic@... [N1MMLoggerplus] wrote:
On CW, N1MM+ has no direct control of the Winkey PTT, other than telling 
the Winkey the tail time that the Winkey should be using. After that, 
the Winkey autonomously drops PTT when it thinks there is a sufficiently 
long space between characters.

Personally, I don't like Winkey PTT. A better name for it would be 
Winkey VOX, since it can, and will, drop out between characters in the 
same message if the tail time is set too low. In that sense, tail time 
is really like VOX delay.

73,
Steve, N2IC

On 11/09/2015 06:51 PM, ve3ki@... [N1MMLoggerplus] wrote:
Some things to look for: Did that only happen in run mode, or also in
S&P? Was the dropout perhaps between F5 and F2 in run mode? That might
help pin it down.


73,
Rich VE3KI


---In N1MMLoggerplus@...,  wrote :

I noticed during SS that my Winkey PTT was momentarily dropping
out when I was sending my exchange. To get around the issue
during the contest, I just turned on VOX. Experimenting with it
today, I see that if I increase the Winkey Tail Time setting to
7, the PTT dropout no longer occurs. That setting had been zero
during the contest. I'll just leave it as 7, but I think
something has changed. My exchange macro is just the usual # U *
59 AZ. N1MM version is 5289.

Dave Hachadorian, K6LL
Yuma, AZ



------------------------------------
Posted by: Steve London 
------------------------------------

N1MM+ FAQ: http://n1mmplus.hamdocs.com/tiki-index.php?page=Frequently+Asked+Questions&structure=N1MM+Logger+Documentation
------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/N1MMLoggerplus/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/N1MMLoggerplus/join
    (Yahoo! ID required)

<*> To change settings via email:
    N1MMLoggerplus-digest@... 
    N1MMLoggerplus-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    N1MMLoggerplus-unsubscribe@...

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/






Re: Sweepstakes

John Bednar
 

Sounds like your radio is not communicating well with the program. What radio model are you using? Did you set the time out to an excessive duration earlier to cover a problem?

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Monday, November 09, 2015 9:59 PM
To: n1mmloggerplus@...
Subject: Re: [N1MMLoggerplus] Sweepstakes

 

 

ditto !!!! first SS with Plus, as good as Classic was, Plus is super !!!!! The parsing feature is great..... used the latest version, only a few minor quirks.....when clicking on a call in the bandmap, it took two clicks....the first one looked like it worked, then the vfo and bandmap would pop back to where it was before the click.....and when manual tuning, when you came across a call, it didnt get highlighted above the space in the entry window, the old call remained.....


> On 11/9/2015 7:46:45 PM, Hank Garretson w6sx@... [N1MMLoggerplus] (N1MMLoggerplus@...) wrote:
> > Bravo and kudos to N2IC.
>
> Once again Sweepstakes Entry Window parsing, implemented by N2IC, worked
> flawlessly and was a pleasure to use. On-the-go correction painless.
>
> Thank you Steve.
>
> Contest Exuberantly,
>
> Hank, W6SX
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7163 / Virus Database: 4457/10971 - Release Date: 11/09/15
>


Re: Sweepstakes

Terry Glagowski / W1TR / AFA1DI
 

Steve,

Did you build the parser by specifying the syntax as a Non Deterministic Finite Automata (NFA) then convert to Deterministic (DFA) ? or just wing it…

Does it resolve ambiguity of 2 digit numbers depending on whether one has already been specified for the QSO (i.e. not specified à it is a number, specified à it is a check, number already provided).

A precedence following it can override to make it a number.

Can you enter a Callsign into the right textbox?  Or do you have to return to the left textbox to do the callsign?

 

Back in the early 80s I wrote such a parser in an MBasic logger, and had only ONE entry field for callsign and exchange for SS.

 

73, Terry / W1TR  :  )

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Monday, November 09, 2015 20:31
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Sweepstakes

 

 

Thanks for the kudos, but I believe that Tom, N1MM, deserves the credit
for that implementation.

73,
Steve, N2IC

On 11/09/2015 05:46 PM, Hank Garretson w6sx@... [N1MMLoggerplus] wrote:
> Bravo and kudos to N2IC.
>
> Once again Sweepstakes Entry Window parsing, implemented by N2IC, worked
> flawlessly and was a pleasure to use. On-the-go correction painless.
>
> Thank you Steve.
>
> Contest Exuberantly,
>
> Hank, W6SX
>
>