Subject: | Re: device-xbee-api |
Date: | Thu, 11 Sep 2014 09:58:14 -0400 |
To: | jeagle [...] cpan.org, bug-device-xbee-api [...] rt.cpan.org |
From: | Raj <thukral [...] pobox.com> |
Hey John
Just a small bug report, I have had this error crop up twice now - seems to
happen rarely, with a few weeks of continuous running between the
occurrences
Invalid type '-' in unpack at
/usr/local/share/perl/5.14.2/Device/XBee/API.pm line 329.
Any thoughts as to what it might be or what else you need to try and debug
it? Using version v0.7 of Device-Xbee-Api on linux
cheers!
--Raj.
On Tue, Aug 19, 2014 at 4:57 PM, Raj <thukral@pobox.com> wrote:
Show quoted text
> Hey John
>
> I've been playing with device-xbee-api (0.7) over the last few days.
> First, thank you! I was looking for an easy way to handle data from my
> xbee network and while I managed to get it working with xig, I found it way
> too much of an overkill for what I really needed to do + I am not a python
> programmer. This module allows me to do what I need with very little
> overhead. I'm just testing out the various pieces now and will transition
> from the xig to my perl code soon. I'm running this on a beaglebone btw,
> so its not like I have a ton of spare resources to play with :)
>
> Second, an interesting note for you - I was trying to set parameters on my
> zigbee coordinator using the at command, and I found that the data field
> for the at command is being interpreted as a character regardless of the
> actual data type.. so for example, if I try to set AO to 1, this fails with
> "invalid parameter":
>
> my $at_frame_id = $api->at('AO',1 );
>
> however, this work:
>
> my $at_frame_id = $api->at('AO',chr(1) );
>
> No biggie, now that I have figured it out, but might be worth documenting.
> I suspect at_remote would work similarly, though I haven't tested it yet
>
> cheers!
> --Raj.
>
>
>