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