[WT-support] Microham u2R behavior with Win-Test
Bob Wilson, N6TV
n6tv at arrl.net
Sat Dec 3 01:09:13 CET 2011
The WinKey log sent to me by CT1ILT clearly shows that $LOGGEDCALL is
always followed by a full word space (a blank sent the the WinKey after the
callsign characters), no matter that you do, and there is no way to send
that "space" at 50 WPM and everything else at 42 WPM.
That's nice if you're pressing F5 or F4 twice in a row, as you would want
to do occasionally, but if you want to send $LOGGEDCALL++++$RST$ZONE----,
it's not so nice.
73,
Bob, N6TV
On Fri, Dec 2, 2011 at 3:56 PM, Frank Grossmann <frank at grossmann.com> wrote:
> Win-Test seems to always have a rather lengthy space between the callsign
> and report if you're using winkey (I'm using a Microham MK2R+) - not 300ms
> as mentioned but it also feels a little bit too long if you're into fast CW
> runs.
> I've tried erasing all spaces in all CW messages and still was not able to
> shorten the delay.
> This is maybe not the same issue, but if the Win-Test team is already
> looking at the space between the callsign and the report maybe they can
> have a look into this.
>
> 73
> Frank DL2CC
>
>
>
> 1. Fwd: Microham u2R behavior with Win-Test (Filipe Lopes)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 29 Nov 2011 13:00:59 +0000
> From: Filipe Lopes <ct1ilt at gmail.com>
> To: Win-Test Reflector <support at win-test.com>, f6fvy at free.fr
> Subject: [WT-support] Fwd: Microham u2R behavior with Win-Test
> Message-ID:
> <CAFQcihQG_ydbyM_qoLTR4Bib69+SvGk3ykA5P+DU4DpQ_71Dcg at mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi everyone,
>
> can anyone at Win-Test say something regarding this issue?
>
> Thank you.
> Filipe Lopes CT1ILT aka CR6K
>
>
>
> Thanks anayway Joe.
>
> Maybe Win-Test team can help us out??
>
> 73's Filipe CT1ILT
>
>
>
> 2011/11/25 microHAM America - W4TV <support at microham.com>
>
> >
> > I have no idea but the data is being sent from Win-Test to Winkey.
> > micro2R does no processing of the data on the WinKey channel.
> >
> >
> > 73,
> >
> > ... Joe Subich, W4TV
> > microHAM America, LLC.
> > http://www.microHAM-USA.com
> >
> > http://groups.yahoo.com/group/**microHAM<http://groups.yahoo.com/group
> > /microHAM>
> >
> > support at microham.com
> >
> > This message, including any attachments, may contain proprietary,
> > confidential or privileged information for the sole use of the
> > specific
> > individual(s) to whom it is addressed. You are hereby notified that
> > any disclosure, copying, distribution, or use of this message is
> prohibited.
> > If you have received this message in error, please immediately notify
> > the sender by reply e-mail and delete it.
> >
> >
> >
> > On 11/25/2011 9:10 AM, Filipe Lopes wrote:
> >
> >> Thanks for reply Joe, I don't really know how to fix this, the only
> >> thing I know is that with an LPT interface with transistor and
> >> resistor I don't have such delay and with the u2R the delay is there.
> >> Could it be something with the Winkey?
> >>
> >> Filipe Lopes
> >> CT1ILT aka CR6K
> >>
> >>
> >> 2011/11/25 microHAM America - W4TV<support at microham.com>
> >>
> >>
> >>> I know I have asked this before but the delay that is created
> >>> either
> >>>
> >>>> by the u2R or Win-test keeps persisting.
> >>>>
> >>>> The delay occurs when INSERT ($LOGGEDCALL$F2) key is pushed ? (The
> >>>> delay happens between LOGGEDCALL and the "599").
> >>>>
> >>>>
> >>> This is most certainly a Win-Test issue. micro2R plays no role in
> >>> processing $LOGGEDCALL$F2
> >>>
> >>> 73,
> >>>
> >>> ... Joe Subich, W4TV
> >>> microHAM America, LLC.
> >>> http://www.microHAM-USA.com
> >>>
> >>> http://groups.yahoo.com/group/****microHAM<http://groups.yahoo.com/g
> >>> roup/**microHAM>
> >>> <http://groups.**yahoo.com/group/microHAM<http://groups.yahoo.com/gr
> >>> oup/microHAM>
> >>> >
> >>>
> >>>
> >>> support at microham.com
> >>>
> >>> This message, including any attachments, may contain proprietary,
> >>> confidential or privileged information for the sole use of the
> >>> specific
> >>> individual(s) to whom it is addressed. You are hereby notified that
> >>> any disclosure, copying, distribution, or use of this message is
> prohibited.
> >>> If you have received this message in error, please immediately
> >>> notify the sender by reply e-mail and delete it.
> >>>
> >>>
> >>>
> >>>
> >>> On 11/25/2011 7:18 AM, Filipe Lopes wrote:
> >>>
> >>> Hi everyone,
> >>>>
> >>>> I know I have asked this before but the delay that is created
> >>>> either by the u2R or Win-test keeps persisting.
> >>>>
> >>>> The delay occurs when INSERT ($LOGGEDCALL$F2) key is pushed ? (The
> >>>> delay happens between LOGGEDCALL and the "599").
> >>>>
> >>>> I remark that I don't have any additional space nor a ^ that could
> >>>> be causing this delay between the Call and the $F2.
> >>>>
> >>>>
> >>>> Jos? CT1BOH measured this delay (@40WPM) and the spacing between
> >>>> $LOGGEDCALL and $F2 is 300mS when it should be around 90mS!!
> >>>>
> >>>>
> >>>> Any help would be great.
> >>>>
> >>>> Thank you.
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>
> --
> Regards/Cumprimentos,
>
> Filipe Lopes CT1ILT aka CR6K
> http://www.rep.pt/ct1ilt
>
>
>
>
>
> --
> Regards/Cumprimentos,
> Filipe Lopes CT1ILT aka CR6K
> http://www.rep.pt/ct1ilt
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.f5mzn.org/pipermail/support/attachments/20111129/0757b4c7/attachment-0001.html
> >
>
> ------------------------------
>
> _______________________________________________
> Support mailing list
> Support at f5mzn.org
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
> End of Support Digest, Vol 87, Issue 20
> ***************************************
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20111202/117569fc/attachment.html>
More information about the Support
mailing list