1-Wire Filesystem for Linux -- Accessing the Dallas 1-wire network for sensors, memory, identity ()

Paul Alfille | 1 Dec 2008 05:29

Re: ow(fs) in motorsports

Sounds like two problems. owfs/FUSE and the wiring.

You are right to test with owhttpd, since it has fewest failure modes. Hobby Boards has wiring diagrams on their website. I'd follow them. The hubs do need external power, and should show at least the 3 DS2409s.

As for the owfs/FUSE problem, if you start it with diagnostics (owfs --foreground --error_level=9 -m /mountpoint -d /dev/ttyS0) you'll get some information.

Paul Alfille

On Sun, Nov 30, 2008 at 12:34 PM, Jaap Struyk <japie <at> minimumrisk.nl> wrote:

Hello,

2 years ago I started here gathering information to use ow/fs for use as
datalogger in high power motor sports.
Finally it's coming together and the story continues but I ran into some
strange hardware trouble.
I don't know or this is the right place to post a cry for help about
hardware so if not please point me in the right direction...

I have owfs-2.7p8 on a intel micro-atx, kernel-2.6.27.4 without ow
drivers inside.
Got an one-wire 6-channel master hub from hobby-boards (ds9097) and some
thermocouple adapters TAI8560 from aag (ds2670?)

If I run ow(httpd,server,fs) with --fake=(chips above) I can see all
sensors in my browser, but if I do a ls /mountpoint the terminal hangs.
(not the system, just the terminal I am using at that time, opening a
new ssh session is working fine)
I tried a mountpoint on my (flash) harddrive and also a mountpoint on
tmpfs, both times no go with ls.

Second problem I have is that the sensors arent found, owhttpd show me
the ds9097 but no sensors, which is not odd since the leds on the hub
and thermocouples aren't lid.
I connected 2 wires only (docs from hardware told me only both ow wires
needed, no extra power supply) both in the middle of the connectors:
RJ11 pin 2 to RJ45 pin 4
RJ11 pin 3 to RJ45 pin 5
Are the docs fooling me and did I do a wrong wiring or did I screw up my
owfs build?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

Jaap Struyk | 1 Dec 2008 18:48

Re: ow(fs) in motorsports

Paul Alfille schreef:

> You are right to test with owhttpd, since it has fewest failure modes.
> Hobby Boards has wiring diagrams on their website. I'd follow them. The
> hubs do need external power, and should show at least the 3 DS2409s.

The extra power for the hub was there, a green LED is showing me that
the device is (should) function, owhttpd only is showing

> As for the owfs/FUSE problem, if you start it with diagnostics (owfs
> --foreground --error_level=9 -m /mountpoint -d /dev/ttyS0) you'll get
> some information.

# owfs --foreground --error_level=9 -m /tmp/owfs -d /dev/ttyS0
CONNECT: fuse mount point: /tmp/owfs
   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=2
--000: E3 C5
   <..>
Byte buffer Serial read:, length=1
--000: 81
   <.>
Byte buffer Attempt serial write:, length=1
--000: C5
   <.>
Byte buffer Attempt serial write:, length=1
--000: 45
   <E>
Byte buffer Serial read:, length=1
--000: 84
   <.>
CONNECT: Cannot detect DS2480 or LINK interface on /dev/ttyS0.
  DEBUG: COM_close: flush
  DEBUG: COM_close: restore
  DEBUG: COM_close: close
   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=1
--000: F0
   <.>
Byte buffer Serial read:, length=1
--000: 81
   <.>
  DEBUG: fuse_mnt_opt=[(null)]
  DEBUG: fuse_open_opt=[(null)]
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.9
flags=0x0000003b
max_readahead=0x00020000
   INIT: 7.8
   flags=0x00000001
   max_readahead=0x00020000
   max_write=0x00020000
   unique: 1, error: 0 (Success), outsize: 40

When I do ls now there are no hangs... ?

# cat /tmp/owfs/bus.0/interface/settings/name
DS9097

As long as the 2480's aren't found it's not odd that the thermocouples
aren't found, can this be related to com port settings?

# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
	Baud_base: 115200, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

headers

Paul Alfille | 1 Dec 2008 23:22

Re: ow(fs) in motorsports

Which version of owfs? 2.7p8 had the serial support broken. 2.7p9 is fixed.

Paul Alfille

On 12/1/08, Jaap Struyk <japie <at> minimumrisk.nl> wrote:

Paul Alfille schreef:

> You are right to test with owhttpd, since it has fewest failure modes.
> Hobby Boards has wiring diagrams on their website. I'd follow them. The
> hubs do need external power, and should show at least the 3 DS2409s.

The extra power for the hub was there, a green LED is showing me that
the device is (should) function, owhttpd only is showing

> As for the owfs/FUSE problem, if you start it with diagnostics (owfs
> --foreground --error_level=9 -m /mountpoint -d /dev/ttyS0) you'll get
> some information.

# owfs --foreground --error_level=9 -m /tmp/owfs -d /dev/ttyS0
CONNECT: fuse mount point: /tmp/owfs
  CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=2
--000: E3 C5
  <..>
Byte buffer Serial read:, length=1
--000: 81
  <.>
Byte buffer Attempt serial write:, length=1
--000: C5
  <.>
Byte buffer Attempt serial write:, length=1
--000: 45
  <E>
Byte buffer Serial read:, length=1
--000: 84
  <.>
CONNECT: Cannot detect DS2480 or LINK interface on /dev/ttyS0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
  CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=1
--000: F0
  <.>
Byte buffer Serial read:, length=1
--000: 81
  <.>
DEBUG: fuse_mnt_opt=[(null)]
DEBUG: fuse_open_opt=[(null)]
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.9
flags=0x0000003b
max_readahead=0x00020000
  INIT: 7.8
  flags=0x00000001
  max_readahead=0x00020000
  max_write=0x00020000
  unique: 1, error: 0 (Success), outsize: 40

When I do ls now there are no hangs... ?

# cat /tmp/owfs/bus.0/interface/settings/name
DS9097

As long as the 2480's aren't found it's not odd that the thermocouples
aren't found, can this be related to com port settings?

# setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
       Baud_base: 115200, close_delay: 50, divisor: 0
       closing_wait: 3000
       Flags: spd_normal skip_test

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

horn.beat | 2 Dec 2008 12:29

Re: Fwd: owserver, owhttpd - 1wire over ethernet problem


just installed the new version of owfs - but still the same problem. I think
it's a serial port redirector problem. I tried several other ways, as ttyd
but I wasn't able to create virtual tty ports. I also got a linux source
from lantronix but I couldn't compile ... (I have to admit that I don't have
much experience on linux ...) maybe somebody can help me. The needed
functionality is:  virtual tty port (ptyp0) redirecting to tcp (ip:port) so
ofws can send to and receive from this virtual port.
I'll try to attach the cpr-sources (they also have binaries - but they
didn't work either on my debian machine).

Another idea is maybe to integrate  this to owfs directly  (similar to
ha7net)  the xport direct module converts raw ethernet data stream directly
to RS232 - so it's maybe no big problem ...(?) 

rgds
Beat

http://www.nabble.com/file/p20733015/svr_tty.c svr_tty.c 

--

-- 
View this message in context: http://www.nabble.com/Fwd%3A-owserver%2C-owhttpd---1wire-over-ethernet-problem-tp20687055p20733015.html
Sent from the OWFS - Dev mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

headers

tiscali | 2 Dec 2008 13:04

Fwd: owserver, owhttpd - 1wire over ethernet problem

In the meantime I found some other posts in the archive concerning --link. Maybe some of these guys found a solution?

Possibly the rs232 signal has to be inverted? I am not using a inverting interface chip, as I am directly connecting the xport-module to to ds2480b (see the scm in first post)

I have to point out, that the hardware was already working with the described windows setup.

here my tests and debug outputs:

first I guessed that --LINK could do the job, The LinkE box probably uses the same xport module.

but I don't know about the internals ...

debian:/tmp/ttyredirector_sena-4.0.2# /opt/owfs/bin/owserver --foreground --error_level 9 --error_print 2 -p 3001 --LINK=192.168.1.41:10001

   CALL: PARSENAME path=[]
CONNECT: LinkE detect
CONNECT: TIMEOUT after 1 bytes
CONNECT: Cannot open LINK-HUB-E adapter at 192.168.1.41:10001
DEBUG: main_threadid = 3084142256
DEBUG: ServerProcessOut = 3083770768
DEBUG: OW_Announce: end
DEBUG: ServerProcessAccept 3001[3083770768] try lock 0
DEBUG: ServerProcessAccept 3001[3083770768] locked 0
^C DEBUG: ServerProcess: break signo=2
DEBUG: ow_net_server.c:ServerProcess() shutdown initiated
DEBUG: Shutting down 0 of 1 thread -1211196528
DEBUG: ow_net_server.c:ServerProcess() shutdown done
DEBUG: ow_exit 0
   CALL: Starting Library cleanup
   CALL: Clear Cache
   CALL: Closing input devices
DEBUG: FreeIn: busmode=16
   CALL: Closing outout devices
   CALL: Finished Library cleanup

here I am testing the virtual tty-port
********************************************************

debian:/tmp/ttyredirector_sena-4.0.2# /usr/local/sbin/ttyredirectord --start
debian:/tmp/ttyredirector_sena-4.0.2# trquery -tty ALL
tty:       mytty0
server:       192.168.1.41
port:       10001
protocol:   telnet
restore:   N
speed:       9600
auth:       none
ptydelayclose:   0

********************************************************
debian:/tmp/ttyredirector_sena-4.0.2# /opt/owfs/bin/owserver --foreground --timeout_network=60 --error_level 9 --error_print 2 -p 3001 -d /dev/mytty0

   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=2
--000: E3 C5
   <..>
Byte buffer Serial read:, length=1
--000: 26
   <&>
Byte buffer Attempt serial write:, length=1
--000: C5
   <.>
Byte buffer Attempt serial write:, length=1
--000: 45
   <E>
Byte buffer Serial read:, length=1
--000: 44
   <D>
Byte buffer Attempt serial write:, length=1
--000: 5B
   <[>
Byte buffer Serial read:, length=1
--000: 5A
   <Z>
Byte buffer Attempt serial write:, length=1
--000: 3F
   <?>
Byte buffer Serial read:, length=1
--000: 3E
   <>>
Byte buffer Attempt serial write:, length=1
--000: 29
   <)>
Byte buffer Serial read:, length=1
--000: 28
   <(>
Byte buffer Attempt serial write:, length=1
--000: 71
   <q>
Byte buffer Serial read:, length=1
--000: 70
   <p>
Byte buffer Attempt serial write:, length=1
--000: C5
   <.>
CONNECT: Select or timeout error serial port: /dev/mytty0
-> Success
CONNECT: Cannot detect DS2480 or LINK interface on /dev/mytty0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=1
--000: F0
   <.>
CONNECT: Select or timeout error serial port: /dev/mytty0
-> Success
DEBUG: main_threadid = 3084359344
DEBUG: ServerProcessOut = 3083987856
DEBUG: OW_Announce: end
DEBUG: ServerProcessAccept 3001[3083987856] try lock 0
DEBUG: ServerProcessAccept 3001[3083987856] locked 0
^C DEBUG: ServerProcess: break signo=2
DEBUG: ow_net_server.c:ServerProcess() shutdown initiated
DEBUG: Shutting down 0 of 1 thread -1210979440
DEBUG: ow_net_server.c:ServerProcess() shutdown done
DEBUG: ow_exit 0
   CALL: Starting Library cleanup
   CALL: Clear Cache
   CALL: Closing input devices
DEBUG: FreeIn: busmode=2
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
   CALL: Closing outout devices
   CALL: Finished Library cleanup

rgds

Beat

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

Paul Alfille | 2 Dec 2008 15:28

Fwd: [Owfs-forums] [owfs - Help] Problems reading switches of LCD terminal (DS

---------- Forwarded message ----------
From: SourceForge.net <noreply <at> sourceforge.net>
Date: Tue, Dec 2, 2008 at 3:08 AM
Subject: [Owfs-forums] [owfs - Help] Problems reading switches of LCD terminal (DS
To: noreply <at> sourceforge.net

Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=5746540
By: erichabg

Hello All!
Im using owfs on my NSLU2 with Unslung 6.10Beta
I have installed the following modules:
owcapi - 2.7p5-1
owfs - 2.7p5-1
owlib - 2.7p5-1
owshell - 2.7p5-1

I'm reading (with a shell script) 12xDS18B20, 2xDS2423, 1xDS2450 and some DS2405.
The datas are written into a RRD database. Depending on the input of some DS2405
(fire and water alarm) the output of some other DS2405 is set to give alarm
or not.
All works very well!

But now i wanted to add a Hobbyboard LCD terminal to show some of the readings
and to output some messages.
The output is not a problem is use the following command
owwrite $OWSERVER /uncached/29.142C0300000/LCD_H/message "text.." or the browser
via owhttpd.
But i can't read the three switches witch are connected to PIO.0 to PIO.2

I have measured the contacts of the switches and in most cases there is no voltage
(25mV). That means in my understanding that the PIO is set. But the browser
shows that PIO.0 to .7 and also latch0..7 are unset and unsensed. But the value
of PIO.byte is f.e. 103. If i set the value of PIO.byte to 0 (with the browser)
The voltage between the contacts of the switch raises to 5V. But when i shortcut
the contacts the browser furthermore shows all PIOs are not sensed.
I don't understand this behavior.
And after the next output of ..../message the voltage disappears again.

What's going wrong? How can i access the switches?
(I thougt i can detect a short press with the latch state)

Regards
Erich

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=292718

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-forums mailing list
Owfs-forums <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-forums

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

Paul Alfille | 2 Dec 2008 16:38

Re: Fwd: owserver, owhttpd - 1wire over ethernet problem

On Tue, Dec 2, 2008 at 7:04 AM, tiscali <horn.beat <at> vtxmail.ch> wrote:

In the meantime I found some other posts in the archive concerning --link. Maybe some of these guys found a solution?

Possibly the rs232 signal has to be inverted? I am not using a inverting interface chip, as I am directly connecting the xport-module to to ds2480b (see the scm in first post)

I have to point out, that the hardware was already working with the described windows setup.

I think the LINK guys use their much simpler ascii interface. The DS2480B interface chip probably requires a more faithful serial emulation. I know you found it works under Windows. I suspect that more effort and testing was put into that platform.

Here is the serial port setting code for the DS2480B (which I don't truly understand, but it is a modification of the PDkit code with contributions and fixes over time):

    // Set to non-canonical mode, and no RTS/CTS handshaking
    newSerialTio.c_iflag &= ~(BRKINT | ICRNL | IGNCR | INLCR | INPCK | ISTRIP | IXON | IXOFF | PARMRK);
    newSerialTio.c_iflag |= IGNBRK | IGNPAR;
    newSerialTio.c_oflag &= ~(OPOST);
    newSerialTio.c_cflag &= ~(CRTSCTS | CSIZE | HUPCL | PARENB);
    newSerialTio.c_cflag |= (CLOCAL | CS8 | CREAD);
    newSerialTio.c_lflag &= ~(ECHO | ECHOE | ECHOK | ECHONL | ICANON | IEXTEN | ISIG);
    newSerialTio.c_cc[VMIN] = 0;
    newSerialTio.c_cc[VTIME] = 3;

On the other hand, you ARE getting some responses from the device based on your transcript. The only tunable parameter is flextime for the DS2480B. I've added a command line parameter "--serial_flextime (the default) or --serial_regulartime (which may work in your case).

I'll upload it as 2.7p10

The known working network'ed bus masters are:

LinkHubE (ascii protocol)
HA7Net (http interface)
Etherweather (only one prototype as far as I know)
owserver (using an embedded device like the NSLU2 or OpenWRT router)

here my tests and debug outputs:

first I guessed that --LINK could do the job, The LinkE box probably uses the same xport module.

but I don't know about the internals ...

I'm sure if you hooked up a LINK adapter (rather than DS2480B) it would work (again untested). As --LINK= /dev/mytty0 since that initial "/" is the trigger to use serial rather than tcp LINK protocol.

debian:/tmp/ttyredirector_sena-4.0.2# /opt/owfs/bin/owserver --foreground --error_level 9 --error_print 2 -p 3001 --LINK=192.168.1.41:10001

CALL: PARSENAME path=[]
CONNECT: LinkE detect
CONNECT: TIMEOUT after 1 bytes
CONNECT: Cannot open LINK-HUB-E adapter at 192.168.1.41:10001
DEBUG: main_threadid = 3084142256

DEBUG: ServerProcessOut = 3083770768
DEBUG: OW_Announce: end
DEBUG: ServerProcessAccept 3001[3083770768] try lock 0
DEBUG: ServerProcessAccept 3001[3083770768] locked 0
^C DEBUG: ServerProcess: break signo=2
DEBUG: ow_net_server.c:ServerProcess() shutdown initiated
DEBUG: Shutting down 0 of 1 thread -1211196528
DEBUG: ow_net_server.c:ServerProcess() shutdown done
DEBUG: ow_exit 0
   CALL: Starting Library cleanup
   CALL: Clear Cache
   CALL: Closing input devices
DEBUG: FreeIn: busmode=16
   CALL: Closing outout devices
   CALL: Finished Library cleanup

here I am testing the virtual tty-port
********************************************************

debian:/tmp/ttyredirector_sena-4.0.2# /usr/local/sbin/ttyredirectord --start
debian:/tmp/ttyredirector_sena-4.0.2# trquery -tty ALL
tty:       mytty0
server:       192.168.1.41
port:       10001
protocol:   telnet
restore:   N
speed:       9600
auth:       none
ptydelayclose:   0

********************************************************
debian:/tmp/ttyredirector_sena-4.0.2# /opt/owfs/bin/owserver --foreground --timeout_network=60 --error_level 9 --error_print 2 -p 3001 -d /dev/mytty0

   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=2
--000: E3 C5
   <..>
Byte buffer Serial read:, length=1
--000: 26
   <&>
Byte buffer Attempt serial write:, length=1
--000: C5
   <.>
Byte buffer Attempt serial write:, length=1
--000: 45
   <E>
Byte buffer Serial read:, length=1
--000: 44
   <D>
Byte buffer Attempt serial write:, length=1
--000: 5B
   <[>
Byte buffer Serial read:, length=1
--000: 5A
   <Z>
Byte buffer Attempt serial write:, length=1
--000: 3F
   <?>
Byte buffer Serial read:, length=1
--000: 3E
   <>>
Byte buffer Attempt serial write:, length=1
--000: 29
   <)>
Byte buffer Serial read:, length=1
--000: 28
   <(>
Byte buffer Attempt serial write:, length=1
--000: 71
   <q>
Byte buffer Serial read:, length=1
--000: 70
   <p>
Byte buffer Attempt serial write:, length=1
--000: C5
   <.>
CONNECT: Select or timeout error serial port: /dev/mytty0
-> Success
CONNECT: Cannot detect DS2480 or LINK interface on /dev/mytty0.
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
   CALL: PARSENAME path=[]
Byte buffer Attempt serial write:, length=1
--000: F0
   <.>
CONNECT: Select or timeout error serial port: /dev/mytty0
-> Success
DEBUG: main_threadid = 3084359344
DEBUG: ServerProcessOut = 3083987856
DEBUG: OW_Announce: end
DEBUG: ServerProcessAccept 3001[3083987856] try lock 0
DEBUG: ServerProcessAccept 3001[3083987856] locked 0
^C DEBUG: ServerProcess: break signo=2
DEBUG: ow_net_server.c:ServerProcess() shutdown initiated
DEBUG: Shutting down 0 of 1 thread -1210979440
DEBUG: ow_net_server.c:ServerProcess() shutdown done
DEBUG: ow_exit 0
   CALL: Starting Library cleanup
   CALL: Clear Cache
   CALL: Closing input devices
DEBUG: FreeIn: busmode=2
DEBUG: COM_close: flush
DEBUG: COM_close: restore
DEBUG: COM_close: close
   CALL: Closing outout devices
   CALL: Finished Library cleanup

rgds

Beat

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

Jaap Struyk | 2 Dec 2008 18:40

Re: ow(fs) in motorsports

Paul Alfille schreef:

> Which version of owfs? 2.7p8 had the serial support broken. 2.7p9 is fixed.

I did have p8 and yust did a fresh build of p9, unfortunatly without
luck, I get the same output:

Cannot detect DS2480 or LINK interface on /dev/ttyS0.

owfs version:
	2.7p9
libow version:
	2.7p9

Which version can I use to make sure serial support isn't an issue?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

headers

Paul Alfille | 2 Dec 2008 19:09

Re: ow(fs) in motorsports

2.7p9 definitely works with a DS2480B-based serial adapter (DS9097U) since I just tried it.

Paul Alfille

On Tue, Dec 2, 2008 at 12:40 PM, Jaap Struyk <japie <at> minimumrisk.nl> wrote:

Paul Alfille schreef:

> Which version of owfs? 2.7p8 had the serial support broken. 2.7p9 is fixed.

I did have p8 and yust did a fresh build of p9, unfortunatly without
luck, I get the same output:

Cannot detect DS2480 or LINK interface on /dev/ttyS0.

owfs version:
2.7p9
libow version:
2.7p9

Which version can I use to make sure serial support isn't an issue?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Owfs-developers mailing list
Owfs-developers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

headers

Jaap Struyk | 2 Dec 2008 19:21

Re: ow(fs) in motorsports

Paul Alfille schreef:

> 2.7p9 definitely works with a DS2480B-based serial adapter (DS9097U)
> since I just tried it.

Sorry to hear that, it would be nice if it wasn't me 

I will do some tests with a prebuild environment (ubuntu or owfs-dsl) to
check or it's my build or hardware...

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

55	May 2013
62	April 2013
86	March 2013
87	February 2013
79	January 2013
71	December 2012
124	November 2012
60	October 2012
64	September 2012
29	August 2012
76	July 2012
95	June 2012
135	May 2012
106	April 2012
106	March 2012
149	February 2012
212	January 2012
88	December 2011
110	November 2011
150	October 2011
93	September 2011
157	August 2011
70	July 2011
77	June 2011
47	May 2011
68	April 2011
183	March 2011
113	February 2011
237	January 2011
99	December 2010
93	November 2010
67	October 2010
83	September 2010
167	August 2010
64	July 2010
34	June 2010
122	May 2010
115	April 2010
178	March 2010
121	February 2010
92	January 2010
62	December 2009
36	November 2009
85	October 2009
17	September 2009
107	August 2009
119	July 2009
58	June 2009
114	May 2009
66	April 2009
55	March 2009
106	February 2009
84	January 2009
92	December 2008
115	November 2008
53	October 2008
43	September 2008
44	August 2008
23	July 2008
37	June 2008
47	May 2008
117	April 2008
51	March 2008
64	February 2008
79	January 2008
123	December 2007
57	November 2007
82	October 2007
122	September 2007
141	August 2007
57	July 2007
79	June 2007
88	May 2007
54	April 2007
60	March 2007
231	February 2007
157	January 2007
281	December 2006
165	November 2006
130	October 2006
139	September 2006
106	August 2006
92	July 2006
121	June 2006
200	May 2006
186	April 2006
132	March 2006
84	February 2006
73	January 2006
70	December 2005
55	November 2005
119	October 2005
95	September 2005
69	August 2005
123	July 2005
169	June 2005
44	May 2005
154	April 2005
114	March 2005
231	February 2005
192	January 2005
83	December 2004
21	November 2004

Mon	Tue	Wed	Thu	Fri	Sat	Sun

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31