[WT-support] Fwd: Microham u2R behavior with Win-Test

Joe Subich, W4TV lists at subich.com
Fri Dec 2 23:43:31 CET 2011 

> You cannot download the versions I used from the microHAM web site;
> you have to ask W4TV to send them to you. Every user of Win-Test with
> a micro2R really needs them too.

Let me make one thing *absolutely* clear - "Router 7.7.5" is not
available to anyone at this time.  "Router 7.7.5" was developmental
software that contains debugging code and incomplete support for other
products that renders it unfit for general use.  It has issues that
impact other products and other software due to the developmental
code.  Finally, microHAM are finalizing the newest version of Router
(with support for additional products and updated drivers) which should
be available by the end of the month unless release is delayed by the
holidays.

Router 7.7.5 was offered to no more than four individuals on the basis
that they not disclose and not share the code with any other person
(including guest operators) but it seems that some of those individuals
are can not be trusted to live up to their agreements.

In general test code is provided to a very limited number of testers to
confirm resolution of a specific problem.  Fixes are not released on an
individual basis - particularly when it includes developmental code.
In general, a "fix" that applies to a single product and application
will not be released separately; it will be included with the next
general upgrade in order to assure that the change does not adversely
impact other products or other software, build the proper installer,
update documentation and certify the package.

73,

    ... Joe, W4TV


On 12/2/2011 1:54 PM, Bob Wilson, N6TV wrote:
> I did not experience any message delay issues when using the u2R firmware
> 2.05 and Router version 7.7.5 with Win-Test at W7RN during the ARRL
> Sweepstakes, but I wasn't sending at 40 WPM, and my log only had 1300 QSOs,
> and I was using $QSOB4 and NOWORKDUPE.
>
> Which version of u2R firmware and Router software are you using?  You
> cannot download the versions I used from the microHAM web site; you have to
> ask W4TV to send them to you.  Every user of Win-Test with a micro2R really
> needs them too.
>
> Does the INSERT message contain $LOGGEDCALL $QSOB4 $F2 or just $LOGGED
> something else?  Is Options CW Work Dupes *un*-checked?  Maybe it needs to
> be *checked*, especially if $QSOB4 is missing from the message, but I'm not
> sure.
>
> What is in the $F2 message?  $RST$ZONE or ++++$RST$ZONE----?  The WinKey
> does not handle speed jumps well when using Win-Test.  If you take away the
> "++++" and "----", or move them to the INSERT message, does the problem go
> away?
>
> Did you select Options | WinKey Configuration | Short spaces (CT space), in
> both Win-Test and the microHAM WinKey tab?  Is Auto space checked in both
> dialogs?  Is the WinKey PTT Lead/Tail both set to 0 in both places?
>
> 73,
> Bob, N6TV
>
> On Tue, Nov 29, 2011 at 5:00 AM, Filipe Lopes<ct1ilt at gmail.com>  wrote:
>
>> 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/group/**microHAM>
>>>>> <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 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
>>
>>
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>>
>
>
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support

More information about the Support mailing list