The default mount-point on the NSLU2 is /mnt/1wire/ . This means that you
should look under that directory if you want to find your devices. ("ps"
didn't should the whole path)
Finally to test on the NSLU:
ls -l /tmp/1wire/
echo 1 > /tmp/1wire/05.24202C000000/PIO
echo 0 > /tmp/1wire/05.24202C000000/PIO
/Christian
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Alfille
Sent: den 6 januari 2008 05:55
To: [email protected]; [EMAIL PROTECTED]
Subject: [Owfs-developers] Fwd: What I did exactly now
Hello Bernd,
We're getting closer to a solution, I suspect. Seeing multiple copies of the
program is an artifact of how Linux handles threads. They are threads of the
same program, each ready to process data.
So to summarize, you have OWFS installed on an NSLU and can see DS18B20s and
DS2405s on the line. You can read temperature, but haven't been able to
switch the DS2405.
>From your laptop, you should be able to see the network:
URL: 192.168.1.77:3001 (this is only a guess, the configuration file should
have the correct port)
If you can install the owshell programs on your laptop, you can try (on your
laptop)
owdir -s 192.168.1.77:4304 /
to see all the devices.
to switch the DS2405, type
owwrite -s 192.168.1.77:4304 05.24202C000000/PIO 1
or
owwrite -s 192.168.1.77:4304 05.24202C000000/PIO 0
You can also run these commands on the NSLU:
owdir
owwrite 05.24202C000000/PIO 1
owwrite 05.24202C000000/PIO 0
Finally to test on the NSLU:
ls /tmp
echo 1 > /tmp/05.24202C000000/PIO
echo 0 > /tmp/05.24202C000000/PIO
What we're doing to trying to see if the problem is just the owhttpd program
(earlier version didn't handle PIO values properly) or owserver itself.
Paul Alfille
On Jan 5, 2008 5:44 PM, <[EMAIL PROTECTED]> wrote:
Hello Paul!
When I login, it says:
Welcome to Unslung V2.3R63-uNSLUng-6.8-beta
BusyBox v0.60.4 (2005.03.22-06:52-0000) Built-in shell (ash)
Then, I typed what you say ("ps ax | grep ow"), and these things are
running:
414 root 1196 S /usr/sbin/CheckPowerButton <= I guess, this is because
of the "ow" in the word "Power".
460 root 3936 S owserver -P /opt/var/run/owserver.pid -u -p <= This
line three times, with different numbers, e.g. 469. Then:
476 root 4460 S owfs -P /opt/var/run/owfs.pid -s 4304 /tmp/ <= This
line also 3 times.
486 root 5972 S owftpd -P /pt/var/run/owftpd.pid -s 4304 <= This line
also 3 times.
497 root 3892 S owhttpd -P /opt/var/run/owhttpd.pid -s 4304 <= This line
also 3 times. And then of course:
530 ttyp0 root 2668 S grep ow
Does this help you? What can I do next?
Many, many thanks,
Bernd
--- antwort auf ---
von:: Paul Alfille
an:: cettl
betreff:: Re: What I did exactly now
datum:: 05.01.08 01:09
I guess the first question is whether owserver and owhttpd were already
started by the initialization scripts.
When you telnet in to the NSLU, can you type:
ps ax | grep ow
that should show you all the running ow... programs.
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
