Hello Jan,

First of all, thank you for feedback.

My mistake: I forgot the quote in the $owserver->write command.

More info about my install:

My Perl is the perl-5.14.2 with last CPAN update.
My OWFS is 2.8p15 (RPi default package) , running on Raspbian Raspberry Pi
(last update)

For debugging, strange, when I launch owserver

sudo owserver --debug --nozero --fake=FF.7D0800000100

I obtain

DEBUG MODE
libow version:
        2.8p15

If I launch a owdir i.e., I obtain correctly the list with fake 1-wire
node, but no debug info displayed.

Then owserver stops working. So for debugging, this is not easy at all.

I will try to send command to LCD via my sheevaplug instead of RPi tonight
fo a test

Thomas


2013/6/27 Jan Kandziora [via OWFS Developers] <
[email protected]>

> Am 27.06.2013 15:42, schrieb Thomas:
>
> >
> > Here is the way to reproduce this:
> >
> > #!/usr/bin/perl -w
> > use OWNet;
> > my $owserver = OWNet->new('localhost:4304 -v -C');
> > $owserver->write(uncached/FF.7D0800000100/line16.0,"Hello World");
> >
> >
> > it displays *Hello WorlX  *
> >
> > with the X replaced by strange character I cannot reproduce here...
> >
> Which perl and owfs version do you use? I've tried latest CVS with
>
> $ /opt/owfs/bin/owserver --debug --nozero --fake=FF.7D0800000100
>
> Your perl script then gives
>
>   CALL: data.c:(150) Write message
>   DEBUG: write.c:(51) WriteHandler: hd->sm.payload=46 hd->sm.size=11
> hd->sm.offset=0 OWQ_size=11 OWQ_offset=0
> OWQ OneWireQuery structure of /uncached/FF.7D0800000100/line16.0
>     OneWireQuery size=11 offset=0, extension=0
> Byte buffer OneWireQuery buffer, length=11
> --000: 48 65 6C 6C 6F 20 57 6F 72 6C 64
>    <Hello World>
>     Cleanup = 0002    OneWireQuery I=11 U=11 F=5.43472E-323 Y=11 D=Thu
> Jan  1 01:00:11 1970
>
> --- OneWireQuery done
>   DEBUG: ow_write.c:(111) Successful write to
> /uncached/FF.7D0800000100/line16.0
>
> for me in the owserver log, no bug. I had to place the onewire path in
> quotes as perl-5.14.2 otherwise complains about the dot in it.
>
> Could you try this, too and check the log from owserver whether the
> string is broken? If yes, it has to be your perl installation, if not it
> has to be something within your owserver.
>
> Kind regards
>
>         Jan
>
>
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Owfs-developers mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=9759&i=0>
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://owfs-developers.1086194.n5.nabble.com/Perl-script-to-control-Louis-Swart-LCD-tp9754p9759.html
>  To unsubscribe from Perl script to control Louis'Swart LCD, click 
> here<http://owfs-developers.1086194.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=9754&code=dHBhcnZhaXNAZ21haWwuY29tfDk3NTR8LTIwMTI2NzI5MTk=>
> .
> NAML<http://owfs-developers.1086194.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://owfs-developers.1086194.n5.nabble.com/Perl-script-to-control-Louis-Swart-LCD-tp9754p9760.html
Sent from the OWFS Developers mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to