Here is my init.d startup script. They should be separate but I wonder
if the server -u all could be causing a conflict since ttyUSB1 is
connected with a usb/rs232 adapter? In my perl program I use
OW::init('/dev/ttyUSB1');. Both programs are running at the same time
but should be using separate adapters and buses.
#DS9490R
/opt/owfs/bin/owserver -u all
/opt/owfs/bin/owhttpd -p 3001 -s 192.168.0.55:4304
#DS9097U
/opt/owfs/bin/owfs -d /dev/ttyUSB1 /mnt/1wire3
#CM11A
/usr/local/bin/heyu start
Paul Alfille wrote:
> The perl program (or ow.pm <http://ow.pm>) use the same library as
> owfs. It will also have the same constraints -- it needs access to the
> usb port.
>
> You aren't running the programs at the same time, are you? They can't
> both access the port.
>
> Well they can, but you have to use owserver
>
> so:
> sudo owserver -d /dev/ttyUSB1 -p 4304
> owfs -s 4304 -m /1wire3
> perl connects to -s 4304
>
>
> Note that only owserver needs root permissions in this setup.
>
> Paul
>
> On Mon, Jan 5, 2009 at 6:30 PM, William Brown <mahi...@earthlink.net
> <mailto:mahi...@earthlink.net>> wrote:
>
> My bad, I noticed I ran owfs without su so I tried again. It didn't
> work so I restarted the computer and created a third directory 1wire3
> and I was successful using owfs to read the DS9097U. So it's
> something
> in my Perl program that is choking. Perl program works ok with the
> DS9490R but not with the DS9097U
>
> /mnt/1wire3
> |-- bus.0
> | `-- interface
> | |-- settings
> | | |-- address
> | | |-- datasampleoffset
> | | |-- ds2404_compliance
> | | |-- flexible_timing
> | | |-- name
> | | |-- overdrive
> | | |-- pulldownslewrate
> | | |-- version
> | | `-- writeonelowtime
> etc
> > | |-- errors
> > | | |-- BUS_bit_errors
> > | | |-- BUS_byte_errors
> > | | |-- BUS_detect_errors
> > | | |-- BUS_echo_errors
> > | | |-- BUS_level_errors
> > | | |-- BUS_next_alarm_errors
> > | | |-- BUS_next_errors
> > | | |-- BUS_readin_data_errors
> > | | |-- BUS_status_errors
> > | | |-- BUS_tcsetattr_errors
> > | | |-- CRC16_errors
> > | | |-- CRC16_tries
> > | | |-- CRC8_errors
> > | | |-- CRC8_tries
> > | | |-- DS2480_level_docheck_errors
> > | | |-- DS2480_read_fd_isset
> > | | |-- DS2480_read_null
> > | | |-- DS2480_read_read
> >
> etc
>
> William Brown wrote:
> > When I try to access DS9097U serial adapter attached by HL-340
> usb to
> > rs232 adapter.
> > Only the DS9097U is attached, there are no other devices (should
> be OK?)
> >
> > $ sudo mkdir /mnt/1wire
> > $ sudo /opt/owfs/bin/owfs -d /dev/ttyUSB1 /mnt/1wire
> > $ tree -a /mnt/1wire
> >
> > /mnt/1wire [error opening dir]
> >
> > Paul Alfille wrote:
> >
> >> On Mon, Jan 5, 2009 at 4:45 AM, William Brown
> <mahi...@earthlink.net <mailto:mahi...@earthlink.net>
> >> <mailto:mahi...@earthlink.net <mailto:mahi...@earthlink.net>>>
> wrote:
> >>
> >> So now I'm getting this error:
> >>
> >> DEFAULT: Cannot detect DS9097 (passive) interface on
> /dev/ttyUSB1
> >>
> >> Can you tell me what it means? Will owfs pass through a
> rs232/usb
> >> converter?
> >>
> >> I general, yes.
> >> There is a difference between the DS9097 and the DS9097U (blame
> Maxim
> >> for that).
> >> One is a passive device that depends on the exact serial pulses to
> >> synthesize 1-wire pulses, the other (the 9097U) uses a IC
> called the
> >> DS2480B to manage the 1-wire communication.
> >>
> >> If you have a passive 9097 adapter, try --8bit. Some of the serial
> >> devices can't create 6-bit communication. That might be the case
> >> withthe USB convertor.
> >>
> >> You are using /dev/ttyUSB1. I assume you got that from dmesg
> output.
> >> The allocation can change each time and it's often not a
> symlink. The
> >> permissions might not be applied to the actual device.
> >>
> >> Can you try your code as root? sudo /opt/owfs/bin/....
> >>
> >> Paul Alfille
> >>
> >
> >
> >
>
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers@lists.sourceforge.net
> <mailto:Owfs-developers@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> <mailto:Owfs-developers@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
