[WT-support] microHam micro2R with WT
Bob Wilson, N6TV
n6tv at arrl.net
Thu May 13 13:12:13 CEST 2010
Thanks for posting the communications log. It's possible the new micro2R is
not completely compatible the the MK2R/MK2R+, and changes are required in
Win-Test, but I would start by asking microHAM support for assistance.
Did you try experimenting with the HANDSHAKE settings on the microHAM
control port? Try Always OFF, Always ON, or Handshake to see if that makes
any difference.
If that doesn't work, try the same with the WinKey port. The software seems
to be waiting for something, hence the delays.
73,
Bob, N6TV
On Thu, May 13, 2010 at 6:53 AM, <sm5ajv at qrq.se> wrote:
> Thanks for your advices.
>
> FIRST
> N6TV wrote:
> > 1-2 second delays are a common problem when using Win-Test with the
> microHAM
> > control protocol, even with the older MK2R+
>
> If this is a known issue, I would really like it to be solved.
> Having this delay makes SO2R almost useless. I didn't see any bug report of
> this. So please SW-guys. Look into this!
>
> MY FINDINGS
> I didn't get it working properly and I still have a delay of 1 seconds
> before the CW goes out. It looks like the CW part is going out when
> the RX focus is changing. The RX Focus is changing 1 seconds
> after TX focus is changed. I don't see any reason of this delay.
> See the dumps below.
>
>
> micro2R:
> 0014128234: H-TX: FT1 (set TX focus to R1)
> 0014129312: H-TX: FR1 (set RX focus to R1) <-- 1.078 ms late
> 0014129312: H-TX: FR2 (set RX focus to R2)
> 0014131468: H-TX: FR1 (set RX focus to R1)
>
>
>
> WinKey:
> 0014129312: H-TX: 53 S <-- CW STARTS at the same time as FR1 is sent,
> see above
> 0014129328: H-RX: C4 [status: WAIT=0, KEYDOWN=0, BUSY=1, BREAKIN=0,
> XOFF=0]
> 0014129546: H-RX: 53 S
> 0014129546: H-TX: 45 E <-- Messge is sent from WT character by
> character
> 0014129687: H-RX: 45 E
> 0014129687: H-TX: 35 5
> 0014130109: H-RX: 35 5
> 0014130109: H-TX: 45 E
> 0014130250: H-RX: 45 E
> 0014130250: H-TX: 20
> 0014130453: H-RX: 20
> 0014130453: H-TX: 54 T
> 0014130468: H-RX: C0 [status: WAIT=0, KEYDOWN=0, BUSY=0, BREAKIN=0,
> XOFF=0]
> 0014130484: H-RX: C4 [status: WAIT=0, KEYDOWN=0, BUSY=1, BREAKIN=0,
> XOFF=0]
> 0014130625: H-RX: 54 T
> 0014130640: H-TX: 45 E
> 0014130765: H-RX: 45 E
> 0014130765: H-TX: 53 S
> 0014131046: H-RX: 53 S
> 0014131046: H-TX: 54 T
> 0014131250: H-RX: 54 T
> 0014131250: H-TX: 20
> 0014131468: H-RX: 20
> 0014131484: H-TX: (postponed) 1E [Cancel Buffered Speed Change]
> 0014131484: H-RX: C0 [status: WAIT=0, KEYDOWN=0, BUSY=0, BREAKIN=0,
> XOFF=0]
> 0014131500: H-TX: postponed data sent
>
>
>
> COMPARISION WITH N1MM
> I have compared this behaviour with N1MM. In N1MM there is no delay
> before the CW gose out. So I think there is something wrong with WT.
>
> PTT HANDLING WITH WINKEY
> Another difference, which I have pointed out earlier when dealing
> with a WinKey USB, is that WinTest sends character by character
> to the WinKey chip. You can see this in the WK dump below.
> N1MM sends a chunk of characters. This may be related to the problem
> that the PTT-line drops between words if you don't put in a very long
> PTT Tail. I think it's better to make the WK:
>
> [PTT ON], [send all characters in the message] [PTT OFF]
>
> PTT delay should only be applied to the PTT ON in the beginning and
> PTT TAIL should only be applied to the PTT OFF at the end of the
> transmission. This is for "canned" messages.
> Normally you want to have PTT DELAY set to get all relays
> change over before you start sending. The PTT TAIL DELAY
> should be rather small for canned messages. Or only used when
> you use the PADDLE
>
>
> 73
> Ingo SM5AJV / SE5E
>
>
> > 1-2 second delays are a common problem when using Win-Test with the
> microHAM
> > control protocol, even with the older MK2R+.
> >
> > Make sure you don't have PTT lead/tail delays set to the default values.
> > Use the *minimum* numbers (e.g. 0.0 if possible). You have to set this
> in
> > both the Router program and in the Win-Test Winkey Configuration screen
> > (shortcut: WKSETUP [Enter]).
> >
> > Sometimes powering everything off and on in just the right sequence will
> > correct the problem, e.g.:
> >
> > 1. Power on computer
> > 2. Wait for Router program to start (yellow X)
> > 3. Power on microHAM box
> > 4. Wait for Router to detect microHAM (Green check mark)
> > 5. Turn on radios
> > 6. Wait for microHAM Ports tab to display rig freq.
> > 7. Start Win-Test
> > 8. Issue two or three messages to see if thing speed up (first few
> > messages may be delayed)
> >
> > If that doesn't help, verify that you are using the correct COM port
> > settings in Win-Test Interface Configuration, e.g.:
> >
> > - microHAM control port: 38400,N,8,1
> > - WinKey port: 1200,N,8,2 Handshake/Handshake
> > - Elecraft port: 4800,N,8,1 Always OFF/Always OFF
> > - Yaesu port: 4800,N,8,2 Always OFF/Always OFF
> >
> > For radios, press the "Use xxx defaults" button on the Win-Test COM port
> > setup screen. Make sure both Win-Test and the microHAM box are talking
> to
> > the rig with the same speed settings.
> >
> > 73,
> > Bob, N6TV
> >
> > On Wed, May 12, 2010 at 1:58 AM, <sm5ajv at qrq.se> wrote:
> >
> >> I am trying to get the new microHam micro2R (SO2R) box to work with WT
> >> and have run into some problems.
> >>
> >> When starting CQ by pushing F1 in WT it takes about 1 second
> >> before the actual CW output is started. Has anyone any hint
> >> on how to configure this new device with WT. I am using
> >> the MK2R setup for the Control Port.
> >>
> >> Pushing the test command for F1 on the router starts CW immediately.
> >>
> >> Any advices are most welcome!
> >>
> >> 73
> >> Ingo SM5AJV / SE5E
> >>
> >>
> >>
> >> _______________________________________________
> >> Support mailing list
> >> Support at win-test.com
> >> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
> >>
> > _______________________________________________
> > Support mailing list
> > Support at win-test.com
> > http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
> >
>
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20100513/99abeef9/attachment.htm>
More information about the support
mailing list