Re: [misterhouse-users] Errors in USB_UIRT.pm

[David N. <jud...@ad...>]

That post by Jon is all I have about the new learning interface, so you have 
the same info I have.  The new learning interface is much better than the 
old raw method, so your efforts are better placed there.  Plus, the code is 
already written; it's just broken  :)  I will help in any way I can.

David

----- Original Message ----- 
From: "Chris Barrett" <ch...@ba...>
To: <mis...@li...>
Sent: Monday, August 30, 2004 12:58 AM
Subject: Re: [misterhouse-users] Errors in USB_UIRT.pm


> The extra $ seems out of place to me but it doesn't affect me so I'm happy 
> for it to be left as is.
>
> Could you please send me the protocol spec.  I have a version that doesn't 
> cover it but I found a reference and description of it by Jon on the 
> usb-uirt developers forum that I've been using.  One option might be to do 
> the learning using the older RAW method.  I'll keep working on it and will 
> let the group know if I get it working.
>
> ----- Original Message ----- 
> From: "David Norwood" <jud...@ad...>
> To: <mis...@li...>
> Sent: Monday, August 30, 2004 7:02 AM
> Subject: Re: [misterhouse-users] Errors in USB_UIRT.pm
>
>
>>I agree with numbers 1 and 3, but I think the extra $ in the Windows DLL
>> code is correct.  I believe Brian Ujvary added that to make it work.
>>
>> I wrote the learning code for linux, but
>> never got around to debugging it.  Now, the USB ports aren't working on 
>> my
>> linux box.  If you would like to dive into that code, I have the protocol
>> spec for the usb-uirt including the more advanced learning interface 
>> added
>> in later firmware versions.
>>
>>
>>
>> David
>>
>> ----- Original Message ----- 
>> From: "Chris Barrett" <ch...@ba...>
>> To: <mis...@li...>
>> Sent: Saturday, August 28, 2004 9:47 PM
>> Subject: [misterhouse-users] Errors in USB_UIRT.pm
>>
>>
>>> I've recently bought a USB-UIRT and have been trying to get the learning
>>> to work.  Still no luck on that front but in the process I've discovered 
>>> a
>>> couple of errors.
>>>
>>> 1) There is a subroutine called "get_reponse" that should be
>>> "get_response". The 6 or so calls to it will also need to be fixed.
>>>
>>> 2) The middle line below has an extra '$' at the start of the line. It's
>>> in the "get_version" subroutine. Note: I run MH on Linux and this is
>>> within a segment of MSWin32 code so it may in fact not be a problem.
>>> <QUOTE>
>>> $protocol_major = $UirtInfo->{protVersion}>>8;
>>> $$protocol_minor = $UirtInfo->{protVersion}&0xff;
>>> $firmware_month = $UirtInfo->{fwDateMonth};
>>> </QUOTE>
>>>
>>> 3) None of the calls to usb_uir_send check to see that they get back a
>>> CMDOK (0x21).  Most calls to usb_uir_send are followed by a call to
>>> "get_reponse' (or "get_response" as it should be) but the result is just
>>> ignored.
>>>
>>> I'd like to recommend that each instance of the line:
>>>    my $ret = get_response(1);
>>> be followed with something like:
>>>    printf("USB_UIRT: <subroutine name> returned 0x%X\n",$ret) unless 
>>> ($ret
>>> == 0x21);
>>>
>>> Regards,
>>> Chris
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> ________________________________________________________
> To unsubscribe from this list, go to: 
> http://sourceforge.net/mail/?group_id=1365
>