from:"Paul Alfille"

Re: [Owfs-developers] Many-port bus master

2017-08-01 Thread Paul Alfille

owlib does have support for that kind of device -- (multiple buses) -- The
DS2482-800 is a good example. It has one "port" and multiple buses. The
port gets locked for just the message (e.g. serial communication) and the
individual 1-wire bus and slave gets locked for the 1-wire "conversation".
Each of those buses can have independent conversations (e.g. do temperature
conversions independently).

On Tue, Aug 1, 2017 at 11:24 AM, Jan Kandziora  wrote:

> Am 01.08.2017 um 16:01 schrieb Alastair D'Silva:
> > Hi folks,
> >
> > I'm currently designing an open-hardware 32 port 1wire bus master for
> part
> > of my home automation system, and would like your input.
> >
> > The design is based around an STM32F412ZG microcontroller, with MOSFET
> > active pullups & drive transistors. It will present as a hat for the
> Orange
> > Pi Prime (other Pis may also fit). My plan is to connect over the serial
> > port, but I've also wired through I2C & SPI just in case.
> >
> A hat employing standard connectors is going to be more useful to
> average users. This limits the number of channels because of the size of
> the hat.
>
> And nearly no one would need 32 channels. The 8 channels the DS2482-800
> offers are already too much for most applications.
>
> What would be incredibly useful is a chip that does have separated RX
> and TX lines for each channel so one could use optocouples for totally
> isolated onewires. People using Onewire for building a weather station
> will love you for such a thing. Your hat should employ these, as well as
> an optional isolating DC-DC converter!
>
> What would be also useful is a device that offloads e.g. the search
> algorithm as the DS2490 does. That chip is now unavailable outside of
> the DS9490U device.
>
>
> > I'm currently considering how the device should present to OWlib:
> >
> I found it most useful if you wrote a w1 kernel driver for it instead,
> so one could also use the DS28E17 Onewire-to-I²C bridge with your chip.
>
>
> > Option 1: Maintain an internal hashtable mapping devices to ports, and
> > present as a single bus master. This has the downside of limiting the
> > potential number of devices, as well as monopolising all the buses during
> > long events, such as a firmware update. This would be annoying, as my
> light
> > switches won't respond across the whole house if I have to update the
> > firmware on any device.
> >
> > Option 2: Present as a single multi-bus master. I'm not sure if OWlib has
> > such a concept, if not, there may be significant infrastructure work
> > required. If it does, great, as hopefully OWlib will keep track of which
> bus
> > a device belongs to.
> >
> Just look at the DS2482-800 host adapter code.
>
>
> > Option 3: Present as many bus-masters. I think this would be a reasonable
> > solution, as other buses should continue to operate even if one is
> > monopolised by a firmware update. In this situation, only a single room
> will
> > stop responding, rather than the whole house.
> >
> On the OWFS level? Better not, it would make the configuration awfully
> complicated and require an awful lot of work.
>
>
> >
> > PS. Would it be possible to get my current work reviewed? I'm not quite
> > ready to push it upstream, but it would be good to know early if there is
> > anything there that would prevent it from being merged. My repo is here:
> > https://github.com/InfernoEmbedded/owfs/tree/infernoembedded
> >
> Please do not use the same source file for both your upcoming host and
> your current LED controller and relay boards.
>
>
> If you are happy with your current devices **and have them tested
> against the current version of owfs**, prepare a patch and I will push
> it into master. You are the only one who can test it anyway as long
> noone else has this hardware.
>
> Kind regards
>
> Jan
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Turning OWFS website into a Wiki. Was: owfs is DISABLED

2016-07-28 Thread Paul Alfille

I'm sorta gone. How can I help the transition?

Paul

On Tue, Jul 26, 2016 at 4:18 AM, Jan Kandziora <j...@gmx.de> wrote:

> Am 26.07.2016 um 08:36 schrieb Martin Patzak (GMX):
> > who else thinks the following should find it's way onto the owfs
> web-site?
> >
> Guys, face it: Paul Alfille has GONE. I hope he's okay, doing family
> business, something like that. But I'm afraid he will not come back and
> tidy up things in any case.
>
> We are a bit disorganised because of this at the moment.
>
>
> If I had to decide, I would take all the content of the web site, throw
> out all the out-of-date information and feed the rest into a Mediawiki,
> where you and others can maintain it yourself. Then shutdown the old
> website.
>
>
> OWFS developers, OWFS users: should we do that?
>
>
> Kind regards
>
> Jan
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> 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

Re: [Owfs-developers] first build on beaglebone black debian

2015-06-13 Thread Paul Alfille

So is the problem the parsing of the line in the config file?

On Wed, Jun 10, 2015 at 2:42 PM, Jerry Scharf 
sch...@lagunawayconsulting.com wrote:

 Don't you hate it when someone replies to them selves on the list. I was
 trying to get them using the device variable in a config file. I
 couldn't figure out the syntax to get it to do something similar to the
 --i2c=port:ALL function. Once I went to the command line form, it found
 all three.

 thanks,
 jerry

 On 06/09/2015 07:38 PM, Jerry Scharf wrote:
  Hi,
 
  One more question. I got the server going, but it only saw 1 of the 3
  ds2482-100s. The I2C scan code shows all three devices.
 
  It looks from the log like it didn't even try anything else after it
  found one. Is there something I need to do to have it find all three?
  With over 350 1-wire devices, it seemed better to have multiple masters.
 
  jerry
 
  On 06/09/2015 07:20 PM, Jerry Scharf wrote:
  Hi,
 
  I just pulled a3.1p0 from sourceforge and am building it on a beaglebone
  black w/ debian 7.8. I ran into some things I don't understand while
  running configure.
 
  When I try to enable fuse for owfs, I pass it the include path. The test
  program blows up during compile with an undefined size_t in the stdio.h.
  Has anyone found a way around this?
 
  I have also run into some configure problems around usb as well. It is
  looking for the file libusb-1.0.pc, which is not on the system despite
  libusb-dev being installed.
 
 
  Also, I can probably work through the documents, but if someone has the
  commands to have owserver look at I2C#2 for the converter chips, that
  would be a big help. The I2C scan tool sees the three chips.
 
  thanks in advance,
  jerry
 
 
 
 --
  ___
  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



 --
 ___
 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

Re: [Owfs-developers] what's a type 11 device

2015-06-13 Thread Paul Alfille

Is that family code 11 decimal or hex? Family 0x0B is a DS1985.

http://owfs.org/index.php?page=ds1985

On Tue, Jun 2, 2015 at 5:01 PM, Jerry Scharf sch...@lagunawayconsulting.com
 wrote:

 Hi,

 I am helping someone reverse engineer some power supply tips that use
 1-wire devices to code them . Most of them read fine (ds2502 type
 eeproms,) but there is one from a dell 65W supply that comes up with a
 family 11 device when we try to read it.

 Does anyone know what this is and how to read the device?

 thanks,
 jerry



 --
 ___
 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

Re: [Owfs-developers] possible bus search modification

2015-06-13 Thread Paul Alfille

Are you talking about the presence pulse when the device is connected?
OWFS doesn't monitor that directly (it's possible some hubs might have
internal detection).



On Thu, Jun 11, 2015 at 11:09 AM, Howell, Larry (Contractor) 
larry.how...@stryker.com wrote:

 Hi list,



 Our project is developing an embedded system running Linux 2.6.35 on an
 i.MX53.  The system utilizes data from DS2505s through DS2482-800 bus
 master.  We’re using owfs-2.8p15 and the initialization parameters are
 ‘i2c=/dev/i2c-2:0 –m mnt/1wire --allow_other’.



 Physically disconnecting the DS2505 from the system requires 0.5-2
 seconds.  OWFS has generally performed well with the application code
 reading uncached data.  However, system noise is causing bus search errors
 when the read Serial Number (SN) on a bus doesn't match the first time read
 and stored SN, which results in a logical disconnection of DS2505.  The
 system noise doesn’t seem to corrupt the presence pulse due to its pulse
 width.



 A suggested fix is to only do a bus presence check to maintain the DS2505
 is connected after the first read.  If bus presence is not detected, then
 next time bus presence and reading of SN to be implemented to restart the
 process.  Suggested fix is shown as a sequence below:

 First time - Read bus presence and 64-bit SN - Result success - Read
 memory - check integrity - Result success

 Second time - Read bus presence  - Result success

 |  |

 Nth time - Read bus presence  - Result failure

 N+1th time - Read bus presence and 64-bit SN … (Repeat as if it is first
 time)



 I'm requesting suggestions about the best way to implement the suggested
 fix.  Any pointers or suggestions on handling the noise problem would be
 greatly appreciated.



 Thanks,



 Larry Howell


 --

 ___
 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

Re: [Owfs-developers] deleting /mnt/1wire folders and files.

2015-06-13 Thread Paul Alfille

To expand on Colin's point, the files in owfs are created on the fly by the
program. They don't exist on disk. When you read a temperature, the
system makes it look like the file contains a number, but actually the
program reads data from the 1-wire bus to get the value.

The UNIX file system needs a place to hang the top of the filesystem,
/mnt/1wire seems to be what you are using. Everything below that is
virtual and doesn't exist until the owfs is run. (Actually any real files
below that point are masked over by owfs and would be unmasked when owfs
isn't running -- but that just confuses things).

On Sat, Jun 6, 2015 at 11:29 AM, Colin Reese colin.re...@gmail.com wrote:

Just search grey boxes here for what I use for ds9490r and i2c:

http://www.cupidcontrols.com/2014/01/owfs-owserver-owhttp-owpython-and-a-little-1wire-pi/

On Jun 6, 2015, at 6:05 AM, Reid r...@whyreid.co.uk wrote:

Thanks Colin, can you point me to any good examples of the use of
owserver
with the USB D9490R interface.

Regards

George

-Original Message-
From: Colin Law [mailto:clan...@gmail.com]
Sent: 06 June 2015 11:15
To: OWFS (One-wire file system) discussion and help
Subject: Re: [Owfs-developers] deleting /mnt/1wire folders and files.

On 6 June 2015 at 11:06, Reid r...@whyreid.co.uk wrote:
Thanks Mick, I had rebooted but when I saw the file /mnt/1wire I
thought the other files would still be there. When I checked all the
subfolders had magically disappeared. This is good news but a little
alarming that files can disappear when you reboot. I guess pseudo
directories have different properties. Something else I have to learn!

They are not real files that actually exist on disc anywhere. Owfs just
uses simulated folders and files to make it easy to access the 1-wire
data.
Personally I find it much simpler and less confusing to use owserver.

Colin

--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Issues with owfs reading humidity

2015-06-13 Thread Paul Alfille

Hi,

I wonder if the rate of reading is overwhelming the capacitor charging in
the circuit. The DS2438 humidity sensor design creates Vdd from the data
line, if I remember correctly.

Do the problems resolve if you delay readings by, say, 60 seconds
intervals? I doubt your humidity really changes that fast.

Paul

On Fri, Jun 12, 2015 at 6:28 AM, Michele Marcon m.mar...@riello-ups.com
wrote:

 Hello Mr. Alfille,
 I'm using owfs for monitoring the DS2438 device over 1-wire with I2C bus.

 I've noticed some errors in reading the humidity value; here is an extract
 of my log:

 Fri Jun 12 11:15:39 CEST 2015: hum 41  1.92 4.66  t_ist 311.562 t_avg 311
 t_max 312 312
 Fri Jun 12 11:15:41 CEST 2015: hum 41  1.92 4.66  t_ist 311.562 t_avg 311
 t_max 312 312
 Fri Jun 12 11:15:43 CEST 2015: hum 41  1.92 4.66  t_ist 311.562 t_avg 311
 t_max 312 312
 Fri Jun 12 11:15:45 CEST 2015: hum 41  1.92 4.66  t_ist 311.562 t_avg 311
 t_max 312 312
 Fri Jun 12 11:15:48 CEST 2015: hum 41  1.92 1.92  t_ist 312.812 t_avg 311
 t_max 312 312
 Fri Jun 12 11:15:50 CEST 2015: hum -119  1.92 1.92  t_ist 312.812 t_avg
 311 t_max 312 312
 Fri Jun 12 11:15:52 CEST 2015: hum -119  1.92 1.92  t_ist 312.812 t_avg
 312 t_max 312 312
 Fri Jun 12 11:15:54 CEST 2015: hum -119  1.92 1.92  t_ist 312.812 t_avg
 312 t_max 312 312
 Fri Jun 12 11:15:56 CEST 2015: hum -119  1.92 1.92  t_ist 312.812 t_avg
 312 t_max 312 312
 Fri Jun 12 11:15:59 CEST 2015: hum -119  1.92 1.91  t_ist 311.562 t_avg
 312 t_max 312 312
 Fri Jun 12 11:16:01 CEST 2015: hum -118  1.92 1.91  t_ist 311.562 t_avg
 312 t_max 312 312
 Fri Jun 12 11:16:03 CEST 2015: hum -118  1.92 1.91  t_ist 311.562 t_avg
 311 t_max 312 312
 Fri Jun 12 11:16:05 CEST 2015: hum -118  1.92 1.91  t_ist 311.562 t_avg
 311 t_max 312 312
 Fri Jun 12 11:16:07 CEST 2015: hum -118  1.92 1.91  t_ist 311.562 t_avg
 311 t_max 312 312
 Fri Jun 12 11:16:40 CEST 2015: hum 40  1.91 4.66  t_ist 310.938 t_avg 311
 t_max 312 312
 Fri Jun 12 11:16:42 CEST 2015: hum 40  1.91 4.66  t_ist 310.938 t_avg 311
 t_max 312 312
 Fri Jun 12 11:16:44 CEST 2015: hum 40  1.91 4.66  t_ist 310.938 t_avg 311
 t_max 312 312
 Fri Jun 12 11:16:46 CEST 2015: hum 40  1.91 4.66  t_ist 310.938 t_avg 311
 t_max 312 312
 Fri Jun 12 11:16:48 CEST 2015: hum 40  1.91 4.66  t_ist 310.938 t_avg 311
 t_max 312 312
 Fri Jun 12 11:16:51 CEST 2015: hum 41  1.92 4.66  t_ist 312.188 t_avg 311
 t_max 312 312


 In particular, I'd like to show you that the reading of VDD sometimes
 return 1.92 or similar values when it should be around 4.66. Do you
 have any explanation?

 Thanks for your help,


 Michele Marcon

 Centro Ricerche
 RPS SpA
 Viale Europa, 7
 37045 Legnago VR
 Tel. +39 0442 635811 Fax. +39 0442 635934
 Skype Id:  - Voip:
 E-mail: m.mar...@riello-ups.com
 Web: www.riello-ups.com
 --
 Per favore non stampare questo messaggio se proprio non è
 necessario
 Please consider the environment before printing this e-mail
 --





--
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] hobby-board 4 port master hub

2015-06-13 Thread Paul Alfille

The hub support is still in development. Which version do you have?

On Thu, Jun 11, 2015 at 3:53 PM, Lyle Giese l...@lcrcomputer.net wrote:

 On 6/11/2015 11:16 AM, Lyle Giese wrote:
  I have a 'new' Hobby-Board 4 port master hub.  It appears to be a
  working unit.  I connected it via USB to a OpenSuSE box and using
  minicom, I can talk to the unit and it responds.  However I am unable to
  get owfs to talk to it.
 
  The HB master hub is on /dev/ttyACM0  and I have used this command line
  to try to get this running:
 
  owfs -d /dev/ttyACM0 --baud=9600 --6bit -m /mnt/1wire
 
  I think the above is the proper syntax to get owfs to talk to this
  master hub.  Or is it?
 
  Since minicom talks to the board just fine, I am thinking it's an owfs
  command startup issue.  When I issue the above, it just hangs and does
  not return to the command prompt until I hit Ctrl-C. Nothing gets
  registered in /mnt/1wire.  But if I use a DS9490R (USB to 1wire adaptor)
  with one of HB's older hubs, it works fine.  But then it takes a
  different command line syntax for that setup.
 
  Or is it an access issue accessing ttyACM0?  Although minicom has no
  problem with it.
 
  Any pointers?
 
  Lyle
 
 
 --
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 Not answering my question, but just adding some more info.

 After leaving owfs in it's limbo state for about 20 or 30 minutes, it
 aborts leaving a message that it can not detect DS9097 (passive) on
 /dev/ttyACM0 and then 'No valid 1-wire buses found.

 Lyle



 --
 ___
 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

Re: [Owfs-developers] Discrepancy between owhttpd vs owserver/owhttpd first pages

2015-05-10 Thread Paul Alfille

I think this is expected behavior, if I understand your setup correctly.

Consider:

owserver - physical bus 0
   - physical bus 1
   ...
   - physical bus 7

but through owhttpd

owhttpd - owserver (bus 0 ) - physical bus 0, 1, 2, .. 7

The connection to owserver is considered a bus as well, since it can be
mixed in with physical busses.

Note that the bus numbers (and listing) are purely optional to let you
discover the underlying topology, if you desire.
Normal mode is to let owfs take care of the bus connections and use the
unified listing you see at the top level.

Paul Alfille

On Fri, May 8, 2015 at 7:24 PM, Gary Fariss g...@gizmology.com wrote:

 Hello...

 I have OWFS 3.1 installed on a Raspberry Pi 2 with Raspian Wheezy. I have
 a single DS2482-800 connected to --i2c=/dev/i2c-1:0 and several temp and
 PIO chips connected on 7 of the 8 1wire channels.

 When I am running owhttpd alone and access it with my browser, the first
 page I see includes a line for each of the 1wire channels (bus.0,
 bus.1,...bus.7) as expected.

 However, when I am running owhttpd connected through the owserver, the
 first page I see only includes one bus line; bus.0.  When I click on that
 line, I get a page that looks like the first page I got from owhttpd
 standing alone (e.g. all channels bus.0,...bus.7 shown on multiple lines.)

 It does not seem right that the first page should be different depending
 on whether the server is (or is not) being used

 What do you say, OWFS gurus, is this a bug?

 73,
   Gary Fariss


 ---
 This email has been checked for viruses by Avast antivirus software.
 http://www.avast.com



 --
 One dashboard for servers and applications across Physical-Virtual-Cloud
 Widest out-of-the-box monitoring support with 50+ applications
 Performance metrics, stats and reports that give you Actionable Insights
 Deep dive visibility with transaction tracing using APM Insight.
 http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Update OWFS

2015-04-02 Thread Paul Alfille

Just make install the new one.

Else, delete /opt/owfs

On Thu, Apr 2, 2015 at 5:13 AM, HRueck hru...@kabelbw.de wrote:

 Thanks to Jan and Paul for the info!

 I installed via make install.
 could you please advise how de-install properly without any corruptions?

 best regards, Herbert



 --
 View this message in context:
 http://owfs-developers.1086194.n5.nabble.com/Update-OWFS-tp11252p11259.html
 Sent from the OWFS Developers mailing list archive at Nabble.com.


 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for
 all
 things parallel software development, from weekly thought leadership blogs
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] installing owfs on raspberry pi

2015-04-02 Thread Paul Alfille

Yes, plug and play (as you put it).

You can disconnect the devices at will, and plug them in whenever you want.

A caveat: so improve performance, the device list is kept around 2 minutes
or so, before scanning again (the scan can be slow on a large bus). You can
ask for the /uncached/ directory to see more quickly if it's still there.



On Thu, Apr 2, 2015 at 10:12 AM, Gregg Levine gregg.drw...@gmail.com
wrote:

 Hello!
 I'm glad my advise worked for you Eric.

 Please write up more completely what you did. Paul we need what Eric
 collided with, both those road blocks, and this example of success for
 our website.

 Now as to your small question, sadly I can't answer that one, but I
 believe the others can do that.

 Do have a good holiday of course.
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature fought the Time Wars, time and again.


 On Thu, Apr 2, 2015 at 10:02 AM, Eric Baumann eric.mannb...@gmail.com
 wrote:
  Hi everyone :-)
 
  SUCCESS ! ! !
 
  Now compiled, installed and running smoothly !
 
  Thanks everyone such much !
 
  Please let me know if anyone of you wants a donation.
 
 
  Problem was:
 
  By not selecting the locals in raspi-config correctly, Perl was no
 running
  properly.
  This prevented the header files from the installation of libusb-dev
  to be placed in the right place. Thus I alway got the message after
  running ./configure that USB was disabled.
 
  After running
 
  sudo apt-get install libusb-dev
 
  again, and then /configure and make everything runns smoothly.
 
 
  By the way a small 1 Wire question:
 
  Am I correct in the understanding that 1 wire is 'plug and play'.
  Meaning that slaves can be disconnected at any point with no severe
  consequences despite a possible data loss of that slave?
 
  My love to,
 
  Eric
 
 
 --
  Dive into the World of Parallel Programming The Go Parallel Website,
  sponsored
  by Intel and developed in partnership with Slashdot Media, is your hub
 for
  all
  things parallel software development, from weekly thought leadership
 blogs
  to
  news, videos, case studies, tutorials and more. Take a look and join the
  conversation now. http://goparallel.sourceforge.net/
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 


 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for
 all
 things parallel software development, from weekly thought leadership blogs
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Update OWFS

2015-04-01 Thread Paul Alfille

I usually just build the new version on top of the old. That works as long
as you didn't install via package manager and direct source build, since
one usually installs in /usr/bin and the other in /opt/owfs/bin

The only other gotcha is that linux won't load the new shared library as
long as any of the owfs programs (owserver, owhttpd, owftpd, owfs, owperl,
...) are still running, pinning the old library version in memory. One they
are all closed, the new library can be loaded. A reboot is an easy way to
ensure a clean slate, but it's not essential.

Paul

On Wed, Apr 1, 2015 at 3:32 PM, Jan Kandziora j...@gmx.de wrote:

 Am 01.04.2015 um 16:15 schrieb HRueck:
  when I want to update to a newer version, do I have to just install the
 newer
  one or do I have to uninstall first the older one?
 
 This depends how you have installed owfs. If you have installed owfs
 through the package manager of your Linux distribution, that program
 will do exactly that, but automatically. No need to do it by hand.


 If you have installed owfs by compiling it yourself and using make
 install, installing a new version over it may lead to a mix of old and
 new components, depending on differences in configuration settings. So
 its better to remove the old components first. If you are sure the
 configuration is the same, no need to do that, though.


 Kind regards

 Jan


 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for
 all
 things parallel software development, from weekly thought leadership blogs
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] New Releases 3.0p2 and 3.1p0

2015-03-14 Thread Paul Alfille

I took the unusual step of 2 releases:

3.0p2 Adds minor changes to the K1WM Bus Master from Martin Rapavy for the
Kisler moification of the synthesized DS1WM Bus Master.

3.1p0 is a major change in linkage. We leave behind the legacy version of
libusb for the modern version. Libusb is used for the DS9490 Bus Master,
and the older version is actually no longer supported, except as a legacy
skin over the modern code.

Although I've been pleased with the new libusb function on linux and OSX, I
wanted a working version with the legacy mode in case there are problems.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Link 12/45/USB support for AUX line

2015-03-13 Thread Paul Alfille

Great idea!

On Fri, Mar 13, 2015 at 1:48 PM, Johan Ström jo...@stromnet.se wrote:

Indeed, one is read only and one is write only. The reasoning behind two
separate nodes is that the actual commands to the Link is either Set
high, Set low, or Put in Hi-Z mode and read. That is, reading means
any previous output will be invalidated as it will no longer supply a
high/low level.

How about auxctrl and auxsense, to avoid mixup with other power entries
(which indicates powered or parasite)?

On 3/13/15 17:17 , Paul Alfille wrote:

I love the idea, but not the names. In seems that one is read-only and one
write-only from the name.

How about auxpower and auxsense?

On Thu, Mar 12, 2015 at 12:37 PM, Johan Ström jo...@stromnet.se wrote:

Oops, early send... Trying again, this time writing the full mail!

The LINK adapter has an extra AUX line which can be used as a general I/O
port (somewhat limited though).

Some background, from LinkUSB manual page:
---

The LinkUSBTM supports the standard RJ45 type 1-Wire bus connection
wherein the center two contacts of the RJ connector are the data and ground
connections to the 1- Wire bus. However, another pin in the RJ connector is
also brought into play. This line is, by default, driven to the high
impedance state and left un-powered. It can be an output supplying a low
level (0 VDC) or a high level (5 VDC), or it can be an input sensing a 0-
5VDC logic level. When set to the 5V level by the “d” command, this line
can be used to provide power for DS2409 and DS2406/7 type 1-Wire switches.
However, the current available from this output is limited. The amount of
current that the Aux line can provide is limited to approximately 75 mA.
ASCII commands used by the host can cause the Auxiliary I/O pin to change
its behavior as needed.
--
The other Link devices have the same, somewhat different details though,
mainly with regards to power levels.

I've added some code to control this line via owfs, commited in branch
link-aux:

https://sourceforge.net/p/owfs/code/ci/fca93b164f8b5f0fd0f97bb66d0be7081c751384/

It basically adds two new points in the filesystem:

/bus.N/interface/settings/ link/auxin
/bus.N/interface/settings/link/auxout

This is visible for Link devices only. Auxin allows putting the AUX pin
in hi-z mode, and reading the current value. auxout puts the pin in high or
low mode.

Is this a good solution? It isn't really a setting, but it belongs
under /bus.0/interface.
Also, I didn't put auxin/out on the same node, since sending the read
aux command will actually put it in Hi-z mode rather than just read it.
Reading from auxout is not doable right now, it would only be able to
reply the latest written value, which may or may not be correct, so I
skipped support for reading.

Let me know how if you think this fits in with the rest of OWFS, or if it
should be solved differently.

Regards
Johan

--
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub
for all
things parallel software development, from weekly thought leadership
blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

___
Owfs-developers mailing
listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website

Re: [Owfs-developers] Link 12/45/USB support for AUX line

2015-03-13 Thread Paul Alfille

I love the idea, but not the names. In seems that one is read-only and one
write-only from the name.

How about auxpower and auxsense?

On Thu, Mar 12, 2015 at 12:37 PM, Johan Ström jo...@stromnet.se wrote:

  Oops, early send... Trying again, this time writing the full mail!

 The LINK adapter has an extra AUX line which can be used as a general I/O
 port (somewhat limited though).

 Some background, from LinkUSB manual page:
 ---

 The LinkUSBTM supports the standard RJ45 type 1-Wire bus connection
 wherein the center two contacts of the RJ connector are the data and ground
 connections to the 1- Wire bus. However, another pin in the RJ connector is
 also brought into play. This line is, by default, driven to the high
 impedance state and left un-powered. It can be an output supplying a low
 level (0 VDC) or a high level (5 VDC), or it can be an input sensing a 0-
 5VDC logic level. When set to the 5V level by the “d” command, this line
 can be used to provide power for DS2409 and DS2406/7 type 1-Wire switches.
 However, the current available from this output is limited. The amount of
 current that the Aux line can provide is limited to approximately 75 mA.
 ASCII commands used by the host can cause the Auxiliary I/O pin to change
 its behavior as needed.
 --
 The other Link devices have the same, somewhat different details though,
 mainly with regards to power levels.

 I've added some code to control this line via owfs, commited in branch
 link-aux:

 https://sourceforge.net/p/owfs/code/ci/fca93b164f8b5f0fd0f97bb66d0be7081c751384/

  It basically adds two new points in the filesystem:

 /bus.N/interface/settings/ link/auxin
 /bus.N/interface/settings/link/auxout

 This is visible for Link devices only. Auxin allows putting the AUX pin in
 hi-z mode, and reading the current value. auxout puts the pin in high or
 low mode.

 Is this a good solution? It isn't really a setting, but it belongs under
 /bus.0/interface.
 Also, I didn't put auxin/out on the same node, since sending the read
 aux command will actually put it in Hi-z mode rather than just read it.
 Reading from auxout is not doable right now, it would only be able to
 reply the latest written value, which may or may not be correct, so I
 skipped support for reading.

 Let me know how if you think this fits in with the rest of OWFS, or if it
 should be solved differently.

 Regards
 Johan




 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for
 all
 things parallel software development, from weekly thought leadership blogs
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Loosing Channels - help please

2015-03-04 Thread Paul Alfille

I assume we're talking about the DS2482-800 -- the 8 channel i2c-based bus
master.

The fact that a reboot doesn't fix the problem takes in issue out of owfs
(which should be entirely reset by a reboot) and to the hadware (which
might need a power cycle to fully reset).

The datasheet talks about a Device Reset command (0xF0) that completely
resets the device. We do that on startup, so clearly that's not sufficient.
There must be some enumeration that's done on power-up.

So, I'm at a loss. But how about obvious things -- anything in the system
logs? Possible power problems? Marginal bus design?

Paul

On Wed, Mar 4, 2015 at 9:31 AM, Mick Sulley m...@sulley.info wrote:

 I have had a problem probably 3 or 4 times over the last few months
 where I loose some channels on my 1-wire, this time channels 1, 4 and 5,
 which I think is the same channels as before but can't be sure.  If I
 reboot it doesn't help, just comes up with the same missing channels,
 but power cycle and all is well again.

 I am running version owfs 3.0 but the last time it happened was on 2.9
 with owserver with owfs  Running on Raspberry Pi with Sheepwalk RPi3
 adapter and RPI3a splitters to give the 8 channels.

 Any ideas?

 Thanks
 Mick


 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub for
 all
 things parallel software development, from weekly thought leadership blogs
 to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] New release 3.0p1

2015-02-27 Thread Paul Alfille

OWFS Release Notes
3.0p1
Feb 27, 2015

New Features.
1. owhttpd supports sparse arrays
   A. Based on feedback by Eugenio Torrini
   B. Sparse arrays allow the file extension to have any value, e.g. a
password in the case of the DS1991
   C. owhttpd now has an extension input field for sparse arrays
   D. web pages still don't require javascript or HTML5 features
   E. Fully backwards compatible
2. Preliminary DS1WM support
   A. This is the freely available 1-wire bus master design from Maxim
   B. Can be implemented in FPGA
   C. Preliminary feedback and testing from Martin Rapavy
   D. Needs a hardware address for mapping device registers
   E. Maps system memory directly -- root only
   F. Competes with an in-kernel w1 module

Fixes
1. Fixed DS1991 support
   A. Based on observations and testing by Eugenio Torrini
   B. Uses a different directory structure
  a. subkey0, subkey1, subkey2
   C. Follows datasheet more closely
   D. NOT BACKWARDS COMPATIBLE
  But the old way didn't work so clearly wasn't being used.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-25 Thread Paul Alfille

Just about done, but I'm not sure how to handle the clock divisor in the
DS1WM. It needs the actual clock speed input to the DS1WM. Is that standard
or must I ask the use to supply it.

I thought of self-discovery -- trying different divisors and timing the
actual reset pulse produced.

Paul

On Mon, Feb 23, 2015 at 2:25 PM, Martin Rapavy martin.rap...@kistler.com
wrote:

  I agree, it would make much more sense to fork your implementation of
 ds1wm. Could you estimate how long would it take you? I'm quite in a hurry
 with my project. Or could you perhaps answer the question how OWFS handles
 updates on that master structures. I suppose this will be essential to
 extend you DS1WM implementation to match my bus master (which is basically
 DS1WM with output multiplexer supporting multiple channels/buses).
 Is there any preliminary codebase I could start working on?

  Thank you for your support.

  Best regards,
 Martin
  --
 *From:* Paul Alfille [paul.alfi...@gmail.com]
 *Sent:* Monday, February 23, 2015 7:18 PM

 *To:* owfs-developers
 *Subject:* Re: [Owfs-developers] Add support for additional hardware bus
 master

   I'm working on the ds1wm support. Just got example code from Maxim. How
 about basing you modifications from that.

 Paul
 On Feb 23, 2015 10:46 AM, Martin Rapavy martin.rap...@kistler.com
 wrote:

  Hello Paul,



 so far I came to following conclusions about the parts of owlib which
 need to be extended in order to support new bus master type:

 · Write new module (.c file) which exports a detect function (
 K1WM_detect in my case)

 o I suppose this is the configuration/connection function you
 mentioned earlier

 o it creates mmap for the bus master device

 o it sets following pointers to functions inside interface_routines
 structure

 · Add new “master structure“ (master_uio) into ow_master.h which
 holds context of my bus master (active channel, base address of mentioned 6
 registers, pointer to mmap) and add that structure into master_union

 · Add some command line / configuration file parameters (up to
 now not sure where exactly, but I also didn’t pay much attention to it yet)



 As for the funtions which are pointed from interface_routines structure
 I implemented following:

 · detect (K1WM_detect)

 · reset – this resets the 1wire bus identified by channel stored
 in my master_uio structure

 · next_both – hardware assisted search rom (do you call this
 function repeatedly untill it returns search_done? So one execution of the
 function should set return one ROM in the device_search structure?)

 · sendback_data – transmit/receive of data pointed by its
 parameters

 · close – destroys memory mapping to the bus master

 Is that enough or should I implement more functions from that interface?
 What exactly is redetect supposed to do (I guess it’s different from
 close/detect combo)?

 I’m also not sure how to setup the flags attribute of interface_routines
 and bundling_length.



 As I said I expect the context of each call (like active channel, pointer
 to device memory map, etc.) to be stored in my master_uio structure.
 I suppose OWFS needs to know how to setup the context before calling
 functions from my module – could you please explain me how this should be
 done?



 Thanks in advance,

 Martin





 *From:* Paul Alfille [mailto:paul.alfi...@gmail.com]
 *Sent:* Friday, February 20, 2015 3:32 PM
 *To:* OWFS (One-wire file system) discussion and help
 *Subject:* Re: [Owfs-developers] Add support for additional hardware bus
 master



 Optimally the number of channels should be auto-discovered. I like to
 make the configuration as automatic as possible.



 So if the hardware can be safely probed for the number of channels, or
 announces the number of channels, that would be best.



 Otherwise a command line option would work.Perhaps:



 --rapavybus=0xf000:6



 The syntax i fairly arbitrary, but it should be relatively intuitive or
 consistent.



 Paul



 On Fri, Feb 20, 2015 at 7:47 AM, Martin Rapavy martin.rap...@kistler.com
 wrote:

 Yes, 6 registers in consecutive memory locations (offests 0 .. 5).
 I suppose we need to pass the base address as command line / configuration
 file parameter.



 How does owfs treat channels? Do we need to pass number of channels as
 command line / configuration file parameter as well?



 Thanks,
 Martin



 *From:* Paul Alfille [mailto:paul.alfi...@gmail.com]
 *Sent:* Friday, February 20, 2015 1:43 PM
 *To:* owfs-developers
 *Subject:* Re: [Owfs-developers] Add support for additional hardware bus
 master



 Do you map the 6 control registers to consecutive memory locations? Would
 we pass that location in a command line option?

 On Feb 19, 2015 12:16 PM, Jan Kandziora j...@gmx.de wrote:

 Am 19.02.2015 um 08:59 schrieb Martin Rapavy:
  Hi Paul,
 
  thanks for briefing me on the architecture of OWFS. My master chip
  has

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-25 Thread Paul Alfille

Ok the DS1WM preliminary version is in the git repository.
https://sourceforge.net/p/owfs/code/ci/master/tree/

1. I assume a 10MHz clock (not sure what to do with this option -- I guess
we could have it a command line option but that's messy for users).
2. The tunable parameters (long-line and pulse presence) aren't yet exposed.
3. Untested -- no hardware.
4. Assumes registers mapped and interrupt pin not wired up.
5. Conservative timing choices and little polling to reduce CPU overhead.

Incidentally, I'm suspicious of the w1 kernel module support for the DS1WM.
They don't even have the datasheet pinouts correct in the code.

Paul Alfille

On Tue, Feb 24, 2015 at 7:17 AM, Paul Alfille paul.alfi...@gmail.com
wrote:

 Just about done, but I'm not sure how to handle the clock divisor in the
 DS1WM. It needs the actual clock speed input to the DS1WM. Is that standard
 or must I ask the use to supply it.

 I thought of self-discovery -- trying different divisors and timing the
 actual reset pulse produced.

 Paul

 On Mon, Feb 23, 2015 at 2:25 PM, Martin Rapavy martin.rap...@kistler.com
 wrote:

  I agree, it would make much more sense to fork your implementation of
 ds1wm. Could you estimate how long would it take you? I'm quite in a hurry
 with my project. Or could you perhaps answer the question how OWFS handles
 updates on that master structures. I suppose this will be essential to
 extend you DS1WM implementation to match my bus master (which is basically
 DS1WM with output multiplexer supporting multiple channels/buses).
 Is there any preliminary codebase I could start working on?

  Thank you for your support.

  Best regards,
 Martin
  --
 *From:* Paul Alfille [paul.alfi...@gmail.com]
 *Sent:* Monday, February 23, 2015 7:18 PM

 *To:* owfs-developers
 *Subject:* Re: [Owfs-developers] Add support for additional hardware bus
 master

   I'm working on the ds1wm support. Just got example code from Maxim.
 How about basing you modifications from that.

 Paul
 On Feb 23, 2015 10:46 AM, Martin Rapavy martin.rap...@kistler.com
 wrote:

  Hello Paul,



 so far I came to following conclusions about the parts of owlib which
 need to be extended in order to support new bus master type:

 · Write new module (.c file) which exports a detect function (
 K1WM_detect in my case)

 o I suppose this is the configuration/connection function you
 mentioned earlier

 o it creates mmap for the bus master device

 o it sets following pointers to functions inside interface_routines
 structure

 · Add new “master structure“ (master_uio) into ow_master.h
 which holds context of my bus master (active channel, base address of
 mentioned 6 registers, pointer to mmap) and add that structure into
 master_union

 · Add some command line / configuration file parameters (up to
 now not sure where exactly, but I also didn’t pay much attention to it yet)



 As for the funtions which are pointed from interface_routines structure
 I implemented following:

 · detect (K1WM_detect)

 · reset – this resets the 1wire bus identified by channel
 stored in my master_uio structure

 · next_both – hardware assisted search rom (do you call this
 function repeatedly untill it returns search_done? So one execution of the
 function should set return one ROM in the device_search structure?)

 · sendback_data – transmit/receive of data pointed by its
 parameters

 · close – destroys memory mapping to the bus master

 Is that enough or should I implement more functions from that interface?
 What exactly is redetect supposed to do (I guess it’s different from
 close/detect combo)?

 I’m also not sure how to setup the flags attribute of interface_routines
 and bundling_length.



 As I said I expect the context of each call (like active channel,
 pointer to device memory map, etc.) to be stored in my master_uio
 structure. I suppose OWFS needs to know how to setup the context before
 calling functions from my module – could you please explain me how this
 should be done?



 Thanks in advance,

 Martin





 *From:* Paul Alfille [mailto:paul.alfi...@gmail.com]
 *Sent:* Friday, February 20, 2015 3:32 PM
 *To:* OWFS (One-wire file system) discussion and help
 *Subject:* Re: [Owfs-developers] Add support for additional hardware
 bus master



 Optimally the number of channels should be auto-discovered. I like to
 make the configuration as automatic as possible.



 So if the hardware can be safely probed for the number of channels, or
 announces the number of channels, that would be best.



 Otherwise a command line option would work.Perhaps:



 --rapavybus=0xf000:6



 The syntax i fairly arbitrary, but it should be relatively intuitive or
 consistent.



 Paul



 On Fri, Feb 20, 2015 at 7:47 AM, Martin Rapavy 
 martin.rap...@kistler.com wrote:

 Yes, 6 registers in consecutive memory locations (offests 0 .. 5).
 I suppose we need to pass

Re: [Owfs-developers] How to talk to an 1wire device

2015-02-21 Thread Paul Alfille

Writing slave code is quite easy, in fact. Most of the infrastructure is
built into macros.

Take a look at any similar slave e.g. modules/owlib/src/c/ow_2406.c

You add entries in the big structure near the top for the new properties,
include the name, type, length , read and write functions and perhaps
property-specific data (to use similar functions for different properties).

I'll be glad to help.
On Feb 20, 2015 3:41 PM, Matthias Urlichs matth...@urlichs.de wrote:

 Hello,

 for home automation I'm (finally) going to implement a couple of
 semi-intelligent 1wire slaves. Control the heating system, water the
 garden,
 and other things that can't be done by a central server and dumb 1wire
 slaves because the house will burn down and the yard'll get flooded. ;-)
 (Don't worry, there'll still be other safeguards.)

 However, to actually talk to these things will require some new if there's
 no closely-related existing chip to copy.

 So, is there some sort of howto to that process, do I just copy a device
 that sortof seems to do what I want and muddle through -- or do I simply
 email the specs of what I want to do to Paul and let him do it? ;-)

 Regards,
 -- Matthias



 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-20 Thread Paul Alfille

Do you map the 6 control registers to consecutive memory locations? Would
we pass that location in a command line option?
On Feb 19, 2015 12:16 PM, Jan Kandziora j...@gmx.de wrote:

 Am 19.02.2015 um 08:59 schrieb Martin Rapavy:
  Hi Paul,
 
  thanks for briefing me on the architecture of OWFS. My master chip
  has almost exactly the same register interface as Dallas DS1WM
  (http://datasheets.maximintegrated.com/en/ds/DS1WM.pdf). It only
  differs in one register: Clock divisor register (0x04) is missing and
  instead there’s Output Channel Multiplexer register on the same
  address (0x04). This register is used to enable handling of multiple
  channels (1wire busses) by single chip.
 
 Ohh, maybe we get native support for DS1WM? Swt!

 Kind regards

 Jan


 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-20 Thread Paul Alfille

Optimally the number of channels should be auto-discovered. I like to make
the configuration as automatic as possible.

So if the hardware can be safely probed for the number of channels, or
announces the number of channels, that would be best.

Otherwise a command line option would work.Perhaps:

--rapavybus=0xf000:6

The syntax i fairly arbitrary, but it should be relatively intuitive or
consistent.

Paul

On Fri, Feb 20, 2015 at 7:47 AM, Martin Rapavy martin.rap...@kistler.com
wrote:

  Yes, 6 registers in consecutive memory locations (offests 0 .. 5).
 I suppose we need to pass the base address as command line / configuration
 file parameter.



 How does owfs treat channels? Do we need to pass number of channels as
 command line / configuration file parameter as well?



 Thanks,
 Martin



 *From:* Paul Alfille [mailto:paul.alfi...@gmail.com]
 *Sent:* Friday, February 20, 2015 1:43 PM
 *To:* owfs-developers
 *Subject:* Re: [Owfs-developers] Add support for additional hardware bus
 master



 Do you map the 6 control registers to consecutive memory locations? Would
 we pass that location in a command line option?

 On Feb 19, 2015 12:16 PM, Jan Kandziora j...@gmx.de wrote:

 Am 19.02.2015 um 08:59 schrieb Martin Rapavy:
  Hi Paul,
 
  thanks for briefing me on the architecture of OWFS. My master chip
  has almost exactly the same register interface as Dallas DS1WM
  (http://datasheets.maximintegrated.com/en/ds/DS1WM.pdf). It only
  differs in one register: Clock divisor register (0x04) is missing and
  instead there’s Output Channel Multiplexer register on the same
  address (0x04). This register is used to enable handling of multiple
  channels (1wire busses) by single chip.
 
 Ohh, maybe we get native support for DS1WM? Swt!

 Kind regards

 Jan


 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Add support for additional hardware bus master

2015-02-18 Thread Paul Alfille

Adding support for a new bus-master chip is actually rather easy. OWFS only
requires a few functions be supported. This is actually the point of OWFS:
the bus master and slave functions are encapsulated easily. Since we
support so many different devices, the level of abstraction is very precise.

1. Detection/configuration step. This includes any hardware configuration
and setting up the communication channel (e.g. open the serial port and
setting baud rate).

2. Sending a set of bits or bytes and reading the bus ( works for reading,
too, when sending 0xFF's ).

3. Some kind of discovery to enumerate the 1-wire slaves. Often hardware
assisted.

4. Optional Power bit.

You'll also need to add a command line configuration option. If you can
describe your bus master to me, I can easily write a rough draft that you
can test and perfect. (Or send me a sample).

Paul Alfille
On Feb 18, 2015 3:59 PM, Martin Rapavy martin.rap...@kistler.com wrote:

  Am 18.02.2015 um 21:19 schrieb Martin Rapavy:
   I was exactly in favor of avoiding w1 because of bus polling. It is
   important for me not to use the bus frequently (the wire is also
   shared for reading out data from sensors). Do you think that the w1
   polling might be turned off using w1_master_search (w1 sysfs
   interface)?
  
  That's exactly the purpose of this node. OWFS sends an explicit search
  command through the netlink socket to the w1 driver at
 
  module/owlib/src/c/ow_w1.c, line 112ff
 
  so turning off w1_master_search only affects other services which rely
  on it. BUT: depending on your hardware, hot-plugging a battery may
  already rely on this! It's a bit of a pity this is a global flag and
  cannot be turned off by bus. Check your hardware whether it has other
  services on another onewire.

  Second pitfall: if your hardware has several buses, the w1 driver will
  all join them into one.
 I guess this is really a deal-breaker. There really might be multiple
 buses (onewire channels) connected to that piece of hardware.

  Nevertheless, patching the DS1WM w1 driver may be sufficient and easy
  enough.
 
 
   Option B  Write a fake I²C host adaptor kernel driver which
   creates a new I²C bus, with your onewire host adaptor the only
   device connected to that bus. This may be the easiest option if
   your device behaves very much like the original DS2482. OWFS drops
   in neatly, no strings attached.
  
   I like this approach but I guess I should have been more clear on
  similarity with DS2482 -- it is conceptually similar (hardware based
  multichannel bus master chip) but the interface is different. The
  interface of that custom chip closely matches DS1WM.
 
  Then this is *not* the way to go.
 
 
 
   Option C  Memory-mapped IO from userspace, which is *UGH!*.
   See module/owlib/src/c/ow/ow_ds2482.c for all the things to write
   and change. The disadvantage is owfs has to run as root to do
   MMIO.
   I don't mind running under root. I suppose this is the only feasible
   option if I don't want to use Linux w1. I will have a look into that
   source.
  
  Well, if you don't show it to anyone... (^__^);
 I'm aware of non-reusability of that solution but on the other hand also
 quite specific piece of hardware and from your selection of choices I don't
 see any other way. Am I right?

 Best regards,
 Martin

  Kind regards
 
  Jan

 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Problems with DS2413

2015-02-15 Thread Paul Alfille

Very strange. The devices you see look like /sys entries from the operating
system. Nothing that owfs would generate.

What you should see is:
home/paul/1w/3A.F2FBE3467CC2/
├── address
├── alias
├── crc8
├── family
├── id
├── locator
├── PIO.A
├── PIO.ALL
├── PIO.B
├── PIO.BYTE
├── r_address
├── r_id
├── r_locator
├── sensed.A
├── sensed.ALL
├── sensed.B
├── sensed.BYTE
└── type

0 directories, 18 files

Could there be some strange links or mount options in play?

Paul

On Sun, Feb 15, 2015 at 12:39 PM, Sven probl...@proxyma3.eu wrote:

 Hi Paul,

 sorry for the delay. Yes my device has family code 3A.

 These are my devices:

 cd /sys/bus/w1/devices/
 pi@hauspi /sys/bus/w1/devices $ ls -l
 insgesamt 0
 lrwxrwxrwx 1 root root 0 Jan 12 20:18 28-061549ec -
 ../../../devices/w1_bus_master1/28-061549ec
 lrwxrwxrwx 1 root root 0 Jan 12 20:18 28-061553a9 -
 ../../../devices/w1_bus_master1/28-061553a9
 lrwxrwxrwx 1 root root 0 Jan 12 20:22 28-0615584b -
 ../../../devices/w1_bus_master1/28-0615584b
 lrwxrwxrwx 1 root root 0 Jan 12 20:22 28-061578d2 -
 ../../../devices/w1_bus_master1/28-061578d2
 lrwxrwxrwx 1 root root 0 Feb 15 18:31 3a-00132aa6 -
 ../../../devices/w1_bus_master1/3a-00132aa6
 lrwxrwxrwx 1 root root 0 Feb 15 18:31 w1_bus_master1 -
 ../../../devices/w1_bus_master1
 pi@hauspi /sys/bus/w1/devices $ cd 3a-00132aa6
 pi@hauspi /sys/bus/w1/devices/3a-00132aa6 $ ls -l
 insgesamt 0
 lrwxrwxrwx 1 root root0 Feb 15 18:33 driver -
 ../../../bus/w1/drivers/w1_slave_driver
 -r--r--r-- 1 root root 4096 Feb 15 18:33 id
 -r--r--r-- 1 root root 4096 Feb 15 18:33 name
 drwxr-xr-x 2 root root0 Feb 15 18:33 power
 -rw-r--r-- 1 root root 4096 Feb 15 18:33 rw
 lrwxrwxrwx 1 root root0 Feb 15 18:33 subsystem - ../../../bus/w1
 -rw-r--r-- 1 root root 4096 Feb 15 18:33 uevent
 pi@hauspi /sys/bus/w1/devices/3a-00132aa6 $


 As you can see I have some temperature sensors. They work great.

 Do I need to have the pioa and piob ports connected to have the files?
 I just wanted to try if I can see the device before soldering things to
 it.

 Do you need more information?



 Thank you for your work by the way!
 Sven



 Am 2015-02-02 05:00, schrieb Paul Alfille:
  Hi Sven,
 
  I'll have to locate a DS 2413 to test, but there have been no recent
  changes to the code.
 
  Does your device have family code 3A?
 
  Paul
 
  On Mon, Jan 26, 2015 at 6:57 AM, Sven probl...@proxyma3.eu wrote:
 
  Hallo Mailinglist,
 
  I have problems with a DS2413 device.
  I do not have files like
 
  |-- PIO.A
  |-- PIO.ALL
  |-- PIO.B
  |-- PIO.BYTE
 
  in my OWFS tree. I only see files like
 
  driver
  id
  name
  power
  rw
  subsystem
  uevent
 
  Was there a change in how to read/write to DS2413?
 
  Other devices like DS18B20 work fine on the same bus.
 
  I use 1-Wire bus connected to GPIO of a raspberry pi with OWFS.
 
  Thanks a lot
  Sven
 
 
 
 --
  Dive into the World of Parallel Programming. The Go Parallel
  Website,
  sponsored by Intel and developed in partnership with Slashdot
  Media, is your
  hub for all things parallel software development, from weekly
  thought
  leadership blogs to news, videos, case studies, tutorials and more.
  Take a
  look and join the conversation now.
  http://goparallel.sourceforge.net/ [1]
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers [2]
 
 
 
  Links:
  --
  [1] http://goparallel.sourceforge.net/
  [2] https://lists.sourceforge.net/lists/listinfo/owfs-developers
 
 
 --
  Dive into the World of Parallel Programming. The Go Parallel Website,
  sponsored by Intel and developed in partnership with Slashdot Media, is
  your
  hub for all things parallel software development, from weekly thought
  leadership blogs to news, videos, case studies, tutorials and more.
  Take a
  look and join the conversation now. http://goparallel.sourceforge.net/
 
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] iButton - n00b question

2015-02-15 Thread Paul Alfille

Hi Daniel,

Gregg answered the more general philosophy of 1-wire architecture. Let me
address your questions narrowly.

All the 1-wire chips (well, almost all except the DS1821) have a unique ID
that can be queried by the 1-wire discovery protocol. When you ask for a
directory listing in OWFS it has all the 1-wire devices enumerate
themselves.

You can ask for a directory listing periodically (preferably uncached) to
check the available devices. Although plugging in  new device will send a
presence pulse it's unreliable (easily lost in other bus traffic) and
thus not used by OWFS. Periodic polling is the best way.

Paul

On Sun, Feb 15, 2015 at 2:14 PM, Gregg Levine gregg.drw...@gmail.com
wrote:

 Hello!
 A good question. One I've asked myself countless times, before Paul
 wrote his excellent tool set and realized there was a better way to
 manage certain storage methods.

 Let's say you own an iButton of the type who contains a DS2401
 electronic serial number. Inserting it into the reader will prompt the
 computer to examine it, and add it to the list of displayed devices.
 The serial number on it, will be the displayed along with everything
 else known about it.

 For example one of the many ideas that the company who originated them
 had was to contain a standard real time clock that would contain all
 of the features their real time clocks have and indeed that was the
 case.

 A third party company makes a specialty reader who when pressed
 against one of them is told the time of day and encloses it in its
 files. Further it can be used in place of the recording clocks that
 watchmen used for an eternity of walking around buildings. And in fact
 my food store uses them for their day-to-day activities as applied to
 that one.

 At one point the company was working with a company to make up
 doorlocks that would only open when a matching button was shown to it.

 It gets even stranger.

 At the height of the Java business, they even made a button who would
 contain an application, and indeed the fun one was to have the thing
 send the host computer to show the owner's website in all its
 (typically badly) written glory.

 Incidentally those numbers that each device wears have a story behind
 them. It seems that during the process of development someone there
 discovered that they resembled the codes worn by Ethernet cards so
 they made arrangements with the authorities behind that to register
 them accordingly. They are as seemingly random as the UUID entries
 that can be created using the appropriate software, but that's where
 the two part company.
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature fought the Time Wars, time and again.


 On Sun, Feb 15, 2015 at 1:04 PM, Daniel MacKay dan...@bonmot.ca wrote:
  OK, I'm going to come across as really stunned here, but if I don't ask,
 I won't learn.
 
  I am accustomed to having devices -- mostly temperature sensors -- on my
 1W bus, getting a catalog of them by hand, and then entering the serial
 numbers into a configuration file in my sofware, which then queries them
 once every five minutes.
 
  So with an iButton, some guy comes up to the iButton base, sticks the
 iButton in and... what happens?
 
  How does the software (mine is in Perl) know that:
  a) something has happened on the bus that it should do something and,
  b) what the number of the iButton that just got stuck in, is?
 


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] iButton - n00b question

2015-02-15 Thread Paul Alfille

Wouldn't once per second be enough?

You can also partition the problem -- set up a separate 1-wire bus just for
the polling -- wouldn't be interfering with your sensors. Also these days,
just have a Raspberry Pi or something like that do the polling and 1-wire
work and use your main CPU for data collection and work.

Paul

On Sun, Feb 15, 2015 at 3:16 PM, Daniel MacKay dan...@bonmot.ca wrote:

 Paul:

  Periodic polling is the best way.

 So are you saying that if I have an iButton base on my network, I have to
 be constantly running through a 1-Wire directory search and looking for the
 button?

 So if I wanted to use this to open a door, and wanted reasonable response
 time I’d have to be doing a 1-W directory search multiple times per
 second?  It sounds unreasonably CPU intensive.




 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] DS2484 support ?

2015-02-09 Thread Paul Alfille

I carefully diff-ed the DS2483 and DS2484 data sheets. There are no
substantive differences. The DS2483 seems to be a little fussier about
having Strong Pull-up (SPU) stopped before a reset.

Thus, I would have expected the DS2484 to work fine. Can you check your
hardware setup?

Paul

On Mon, Feb 9, 2015 at 5:22 PM, Lukasz Salwinski luk...@mbi.ucla.edu
wrote:

On 02/09/2015 02:16 PM, Colin Reese wrote:
Yes, I use DS2483 all over the place for years. See here for commands I
use:

http://www.cupidcontrols.com/2014/01/owfs-owserver-owhttp-owpython-and-a-little-1wire-pi/

ok.. I'll get myself some DS2483s...

thanks,
lukasz

On Mon, Feb 9, 2015 at 2:13 PM, Lukasz Salwinski luk...@mbi.ucla.edu
wrote:

On 02/09/2015 01:20 PM, Colin Reese wrote:
Interesting. So the only thing different here is the level translation
goes
down to 1.8V vs. 3.3V compared to the DS2483?

it looks like this is the only difference in the specs I can find...
Is DS2483 supported ? owfs documentation mentions only DS2482-100 and
DS2482-800 chips.

I've used 3.3V for both Vcc SLPZ. I'd guess can try to set Vcc to 5V
and
see what happens...

lukasz

On Mon, Feb 9, 2015 at 12:59 PM, Lukasz Salwinski luk...@mbi.ucla.edu

wrote:

Hello,
does owfs support DS2484 (I2C/1-wire bridge) ? I've just hooked
it
up to raspberry pi and I can see it on the i2c bus but no matter how
I connect 18B20 sensor to it (with or without explicit power line)
they don't show up in the 1 wire directory :o/

thanks,
lukasz

-
Lukasz Salwinski PHONE:
310-825-1402
UCLA-DOE Institute for Genomics Proteomics FAX:
310-206-3914
UCLA, Los AngelesEMAIL:
luk...@mbi.ucla.edu

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is
your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more.
Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is
your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take
a
look and join the conversation now. http://goparallel.sourceforge.net/

___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
-
Lukasz Salwinski PHONE:310-825-1402
UCLA-DOE Institute for Genomics Proteomics FAX:310-206-3914
UCLA, Los AngelesEMAIL: luk...@mbi.ucla.edu
-

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is
your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] DS1991 with owfs

2015-02-05 Thread Paul Alfille

Eugenio,

I looked at the code for the DS1991 and I think I'll rewrite it. I'll send
you some versions to test.

One thing that will change is how the password field is entered for each
read and write.

If the password is 0x1112131415161718 to read in subkey 1 you will read and
write to

subkey1/data.1112131415161718

It's a general problem with the simple file approach that owfs uses --
there isn't an easy way to add an extra field (like password). Adding it to
the filename is the easiest approach.

Paul

On Wed, Feb 4, 2015 at 12:58 PM, Jan Kandziora j...@gmx.de wrote:

 Am 04.02.2015 um 09:23 schrieb Torrini, Eugenio:
  We are using Owfs in Linux to access a DS1991 and DS1995 through the USB
 DS9490R reader.
  Everything is ok for DS1995.
  For DS1991 we are not able to make it work. Maybe we are doing something
 wrong.
  We know the password of the 3 pages of the iButton because we can set it
 with another tool in Windows.
 
  We tried with different approaches this one for example should be right:
 
  1) Create a pwd.hex file with (in hex) 0x31 0x32 0x33 0x34 0x35 0x36
 0x37 0x38
  2) Check the file with hexedit in windows
  3) Chech the file with hexdump in Linux
  4) cat ./pwd.hex  /disk/1wire/02.12B0CE00/pages/password.0
  5) hexdump -Cv /disk/1wire/02.12B0CE00/pages/page.0
 
 Read

 /disk/1wire/uncached/02.12B0CE00/pages/page.0

 instead. Setting a password doesn't invalidate the cache IIRC.

 Kind regards

 Jan


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Hobby Boards (reply to Vol 105, Issue 2)

2015-02-04 Thread Paul Alfille

Well, to read about it you can look at the documentation, test it out, or
look at the code.

The documentation is organized by the specific 1-wire slave. So the
hobbyboards humidity sensor used to be DS2438-based:
http://owfs.org/index.php?page=ds2438

The newer version are microprocessor based:
http://owfs.org/index.php?page=eeef

All that being said, everything should be fairly self-documenting.

So for one of the Hobbyboards devices, I'd just try it out, see the
directory structure that gets shown, and match it to the Datasheet.

You were asking about how to send specific byte sequences to 1-wire device.
OWFS works at a different level of abstraction -- the functions (like a
temperature reading or limit setting) are shown, but the specific byte
codes are handled behind the scenes.

This is entirely open-source software, so I'll be happy to show you exactly
where in the code something is done,

Did I answer your question?

Paul

On Wed, Feb 4, 2015 at 5:00 PM, Eric Baumann eric.mannb...@gmail.com
wrote:

 Hi

 Thanks a lot for your replies :-)

 @ Paul Alfille:
 No, I haven't.

 It's just that I want to READ about it first.
 My question is, where to do so?

 Is there a documentation?

 @ Thorsten:

 Thanks a lot for your help.

 In your example you used:

 cat /mnt/1wire/26.xyzxyz00/
 HIH4000/humidity

 That's great. Do I understand correctly?
 Somebody has already written code for owfs
 to access the humidity data from HB devices?
 And your code is the command?

 If so, that great!
 Could you lead me to that code?
 Because I would like to study it further.

 @ Paul Alfille:
 I think I didn't respond correctly right?
 How do I do respond appropriately?

 @ all:
 My 1 wire experience so far:
 Logging temperature from DS1820 with raspberry pi.
 Using the commands on boot:

 sudo modprobe w1-gpio pullup=1
 sudo modprobe w1-therm

 and then:

 cd /sys/bus/w1/devices
 cd 10-000801b5*
 cat w1_slave

 :-) fell in love with it, now want to expand knowledge with OWFS :-)

 Yours faithfully,

 Eric




 I am glad you guys help me :-)

 Greetings,

 Eric






 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] hobby boards

2015-02-02 Thread Paul Alfille

Eric,

Have you actually tried the devices? I've worked with Hobbyboards to
support most of their devices.

Can you give name of the devices? I can give a more definitive answer then.

Paul
On Feb 2, 2015 5:56 PM, Eric Baumann eric.mannb...@gmail.com wrote:

 Hi :-)

 I am new to OWFS.

 I just bought pretty much all the devices available from
 Hobby Boards:
 - Anemometer Inspeed
 - 1-Wire USB Adaptor
 - Moisture Meter
 - Rain Gauge w/Counter
 - Lightning Detector
 - Barometer
 - Humidity / Temp

 The following devices seem to use Costum-1-wire chips:
 - Moisture Meter
 - Barometer
 - Humidity / Temp

 In the manual of these devices, one can read the following excerpt:

 The following standard 1-Wire commands are supported:
 SEARCH ROM (0 X F0)
 MATCH ROM (0 X 55)
 READ ROM (0 X 33)
 SKIP ROM (0 X CC)

 My question:

 Where can I read / learn how to issue such commands on OWFS?

 The goal is to run OWFS on a Raspberry Pi with Raspian.

 Thanks for your help. :-)


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] New Release 3.0p0

2015-02-02 Thread Paul Alfille

Don't read too much into the major number change, although I've been doing
some major updating.

This version is about being better on the Mac, and a better systemd and
launchd client.

OWFS Release Notes 3.0p0 Feb 2, 2015 New Features. 1. Monitor configuration
file changes A. Use operating system to see if any othe configuration files
have been changed B. Restart the program if changes (owserver, owfs,
owhttpd, owftpd, owcapi) C. Let launchd and system restart for us -- just
exit 2. Launchd support. A. Launchd is sensed from the OS B. Avoids fork,
daemon. C. Gets socket from plist Fixes 1. OSX compiles cleanly 2. Cygwin
compiles cleanly
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Problems with DS2413

2015-02-01 Thread Paul Alfille

Hi Sven,

I'll have to locate a DS 2413 to test, but there have been no recent
changes to the code.

Does your device have family code 3A?

Paul

On Mon, Jan 26, 2015 at 6:57 AM, Sven probl...@proxyma3.eu wrote:

 Hallo Mailinglist,

 I have problems with a DS2413 device.
 I do not have files like

 |-- PIO.A
 |-- PIO.ALL
 |-- PIO.B
 |-- PIO.BYTE

 in my OWFS tree. I only see files like

 driver
 id
 name
 power
 rw
 subsystem
 uevent


 Was there a change in how to read/write to DS2413?

 Other devices like DS18B20 work fine on the same bus.

 I use 1-Wire bus connected to GPIO of a raspberry pi with OWFS.


 Thanks a lot
 Sven


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Basic Question

2015-01-23 Thread Paul Alfille

Colin, that's a great resource! I'll make sure its incorporated.

Paul
On Jan 22, 2015 10:16 PM, Colin Reese colin.re...@gmail.com wrote:

 I forgot. I wrote an app note for them:

 http://interfaceinnovations.org/ibuttonlinkmultisensors.html

 They are DS2438 based. Page three, byte one tells you how to interpret
 the data. I don't have the precise scaling on the app note above, but I
 will add it when I have a moment. Actually, I think most you can intuit
 from the second table, with the exception of Humidity, which is 0% at
 0.8-4.07VDC for 0-100%.

 Colin




 On 1/22/2015 18:49, Paul Alfille wrote:
  Hi Peter,
 
  The two devices listed, family code 10=DS18S20 and 5=DE2405 are not your
  sensor. I suspect you haven't edited the default configuration file
  generated by the ubuntu package. Probably /etc/owfs.conf
 
  The file is pretty well documented in the comments. You will probably
  want the bus master to be --link=/dev/ttyUSB0 though the exact name of
  your USB-serial device could be ttyUSB1 etc.
 
  Figuring out the correct ttyUSB device can be a bit tricky if your
  machine has a lot of devices. Look at 'dmesg' before and after plugging
  in the LinkUSB perhaps.
 
  As for the MS device. They have an ID in the memory region (they are
  DS2438-based I think). Many IDs are built in to OWFS but the
  documentation on the devices and ID has always been a bit spotty. I can
  help you figure it out (and improve OWFS) once we get to that stage.
 
  Basically the DS2438 measures a few voltages and temperature.
 
  Paul Alfille
 
  On Thu, Jan 22, 2015 at 9:11 PM, Peter Hollenbeck pwhb...@gmail.com
  mailto:pwhb...@gmail.com wrote:
 
  I have a LinkUSB and an MS-TV temperature and voltage sensor.
 
  http://localhost:2121/ shows:
 
  |*10.67C6697351FF*| http://localhost:2121/10.67C6697351FF
  |*05.4AEC29CDBAAB*| http://localhost:2121/05.4AEC29CDBAAB
  |*bus.0*| http://localhost:2121/bus.0
  and more
 
  How do I know where to go to find temperature and voltage readings.
 
  Ubuntu 12.04
  owfs installed today with apt-get
 
  Thanks for any input,
  Peter
 
 
 
  
 --
  New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
  GigeNET is offering a free month of service with a new server in
  Ashburn.
  Choose from 2 high performing configs, both with 100TB of bandwidth.
  Higher redundancy.Lower latency.Increased capacity.Completely
 compliant.
  http://p.sf.net/sfu/gigenet
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  mailto:Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 
 
 
 
 
 --
  New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
  GigeNET is offering a free month of service with a new server in Ashburn.
  Choose from 2 high performing configs, both with 100TB of bandwidth.
  Higher redundancy.Lower latency.Increased capacity.Completely compliant.
  http://p.sf.net/sfu/gigenet
 
 
 
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 


 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Basic Question

2015-01-22 Thread Paul Alfille

Hi Peter,

The two devices listed, family code 10=DS18S20 and 5=DE2405 are not your
sensor. I suspect you haven't edited the default configuration file
generated by the ubuntu package. Probably /etc/owfs.conf

The file is pretty well documented in the comments. You will probably want
the bus master to be --link=/dev/ttyUSB0 though the exact name of your
USB-serial device could be ttyUSB1 etc.

Figuring out the correct ttyUSB device can be a bit tricky if your machine
has a lot of devices. Look at 'dmesg' before and after plugging in the
LinkUSB perhaps.

As for the MS device. They have an ID in the memory region (they are
DS2438-based I think). Many IDs are built in to OWFS but the documentation
on the devices and ID has always been a bit spotty. I can help you figure
it out (and improve OWFS) once we get to that stage.

Basically the DS2438 measures a few voltages and temperature.

Paul Alfille

On Thu, Jan 22, 2015 at 9:11 PM, Peter Hollenbeck pwhb...@gmail.com wrote:

 I have a LinkUSB and an MS-TV temperature and voltage sensor.

 http://localhost:2121/ shows:

 *10.67C6697351FF* http://localhost:2121/10.67C6697351FF
 *05.4AEC29CDBAAB* http://localhost:2121/05.4AEC29CDBAAB
 *bus.0* http://localhost:2121/bus.0
 and more

 How do I know where to go to find temperature and voltage readings.

 Ubuntu 12.04
 owfs installed today with apt-get

 Thanks for any input,
 Peter



 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] OWFS random failure issue

2015-01-21 Thread Paul Alfille

Hi Larry,

The owfs --debug option adds -d to the fuse command line to enable
debugging. I typically see the error messages intermixed.

One thing to look at is in the /statistics directory. Perhaps there is line
noise that is causing more retries and a delay.

Paul

On Wed, Jan 21, 2015 at 8:56 AM, Howell, Larry (Contractor) 
larry.how...@stryker.com wrote:

 Hi list,



 I'm an embedded software engineer working on a project that uses DS2430A
 and DS2505 slave devices to store run-time and configuration data.  I'm
 building everything from source and have installed them under Linux 2.6.35
 running on a Freescale i.MX53 (ARM Cortex-A8) CPU. Only 5 channels of the
 ds2482-800 bus master are used.  The application accesses uncached data.
 The slave device are in attachments that can be connected to the embedded
 system via a 5 m cable.  The attachments contain brushless DC motors.  The
 embedded system is a DC power supply/motor controller.  The 1-wire
 generally functions well, but randomly a physically connected attachments'
 slave devices disappear from the owfs file system for some random period
 (a few ms to a few seconds).  Mounting owfs with --debug --error_level=9
 shows no errors, but has provided confirmation that owfs is acting as
 expected on the data that fuse.ko/libfuse provides.  This suggests the
 issue is occurring with fuse or in kernel space.  Is it possible to pass
 parameters to fuse to enable fuse debug output?  Any suggestions on
 debugging this issue would be appreciated.



 General details:

 Bus Master:ds2482-800 channels 0-4 connected, 5-7 not
 connected

 Slave devices: ds2430a and ds2505

 Fuse version: 2.9.2

 OWFS version: 2.8p15

 Typical OWFS mount command-line: /usr/bin/owfs --i2c=/dev/i2c-0:0 -m
 mnt/1wire --allow_other



 Thanks in advance!



 Larry Howell (Contractor)

 Software Design Engineer


 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New Release 2.9p9

2015-01-13 Thread Paul Alfille

Sorry about that.

A quick patch for module/owlib/src/c/ow_browse_monitor.c:

@@ -19,6 +19,7 @@ static GOOD_OR_BAD browse_in_use(const struct
connection_in * in_selected) ;

/* Device-specific functions */

GOOD_OR_BAD Browse_detect(struct port_in *pin)

{

+#if OW_ZERO

struct connection_in * in = pin-first ;

in-iroutines.detect = Browse_detect;

in-Adapter = adapter_browse_monitor; /* OWFS assigned value */

@@ -56,6 +57,10 @@ GOOD_OR_BAD Browse_detect(struct port_in *pin)

OW_Browse(in);

}

return gbGOOD ;

+#else /* OW_ZERO */

+ (void) pin ;

+ return gbBAD ;

+#endif /* OW_ZERO */

}

 static GOOD_OR_BAD browse_in_use(const struct connection_in * in_selected)





Basically hiding the guts of that function if OW_ZERO is not defined.

On Tue, Jan 13, 2015 at 1:42 PM, Roland Franke fl...@franke-prem.de wrote:

   Hello,
 can it be that the version 2.9p9 cannot be build with an –disable-zero?
 I will get on my build system (Based on µclib - buildroot) an fault, when
 i have set –disable-zero.
 The message is, that in ow_browse_monitor.c an fault is by Browse_detect

 Best regards,
 Roland

  *From:* Paul Alfille paul.alfi...@gmail.com
 *Sent:* Tuesday, January 06, 2015 9:28 PM
 *To:* brucek bru...@valinet.com ; OWFS (One-wire file system)
 discussion and help owfs-developers@lists.sourceforge.net
 *Subject:* Re: [Owfs-developers] New Release 2.9p9

  I think the file upload was a little flakey. Did it a couple times more
 and now I see the files listed. Sorry for the premature announcement.

 On Tue, Jan 6, 2015 at 1:56 PM, brucek bru...@valinet.com wrote:

   Hey Paul,
 As of 2pm EST I still do not see 2.9p9 on Sourceforge, just the 2.9p8
 download, and an empty owfs/2.9p9 folder.
 As always, thanks for keeping this going
 Bruce

  *From:* Paul Alfille paul.alfi...@gmail.com
 *Sent:* Tuesday, January 06, 2015 8:59 AM
 *To:* owfs-developers owfs-developers@lists.sourceforge.net
 *Subject:* [Owfs-developers] New Release 2.9p9

   Minor improvement -- basically fixes the owfs problem for Markus
 Gaugusch's report:

 cat: temperature: Message too long

 The problem is that some tools (like cat) ask for an arbitrary (but
 large) read to gather all the data. It used to be 64K but now seems to be
 128K which passes some internal limits.

 We now trim the read request before processing.

 Paul Alfille
 --

 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net
 --
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers



 --

 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net

 --
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers



 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New Release 2.9p9

2015-01-06 Thread Paul Alfille

I think the file upload was a little flakey. Did it a couple times more and
now I see the files listed. Sorry for the premature announcement.

On Tue, Jan 6, 2015 at 1:56 PM, brucek bru...@valinet.com wrote:

   Hey Paul,
 As of 2pm EST I still do not see 2.9p9 on Sourceforge, just the 2.9p8
 download, and an empty owfs/2.9p9 folder.
 As always, thanks for keeping this going
 Bruce

  *From:* Paul Alfille paul.alfi...@gmail.com
 *Sent:* Tuesday, January 06, 2015 8:59 AM
 *To:* owfs-developers owfs-developers@lists.sourceforge.net
 *Subject:* [Owfs-developers] New Release 2.9p9

  Minor improvement -- basically fixes the owfs problem for Markus
 Gaugusch's report:

 cat: temperature: Message too long

 The problem is that some tools (like cat) ask for an arbitrary (but large)
 read to gather all the data. It used to be 64K but now seems to be 128K
 which passes some internal limits.

 We now trim the read request before processing.

 Paul Alfille

 --

 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net

 --
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers



 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Error Message too long when using owfs

2015-01-04 Thread Paul Alfille

I don't have the answer yet, but it happens only with cat or cp, not
less,head or tail.
It also happens only with owfs-owserver-bus, since owfs-bus is ok.

There must be something different in the tcp protocol handling. I'll
investigate further.

Paul

On Sun, Jan 4, 2015 at 1:20 PM, Jacob Joseph ja...@jjoseph.org wrote:

 I recently moved my OWFS setup to a new installation (on Funtoo,
 should it matter), and have noticed that I do have the issue Markus
 mentioned.

 I haven't spent much time debugging quite yet.  Curiously, though,
 while 'cat' doesn't work, other methods of reading such as 'head' or
 opening the file in Python seem unaffected.

 ~Jacob


 On Sun, 04 Jan 2015 10:59:08 +0100
 Stefano Miccoli mo...@icloud.com wrote:

  It seems that your question is still unanswered, so I will try to
  help you, although I___m not able to replicate your setup (and I___m no
  expert of the internal workings of owfs).
 
  From your message it seems that the problem is limited to owfs, and
  not in owserver, but let me double-check.
 
  1) Do you have an owserver running and owfs is quering owserver?
  (You can check by inspecting owfs.conf and running ___sudo netstat
  -tlp___. If there is an owserver deamon running there should be a line
  like
 
  Active Internet connections (only servers)
  Proto Recv-Q Send-Q Local Address   Foreign Address
  State   PID/Program name tcp0  0
  *:4304  *:* LISTEN
  31595/owserver
 
  2) If you have an owserver running can you confirm that
  ___owread /10.FE771D020800/temperature___ gives you a sensible answer
  while ___cat /mnt/1wire/10.FE771D020800/temperature___ yields an error?
 
 
  If the problem is only in owfs a workaround would be using
  owdir/owread/owwrite in the shell, and one of the clients in
  module/ownet for other languages.
 
  Bye
 
  Stefano
 
   On 30 Dec 2014, at 22:15, Markus Gaugusch mar...@gaugusch.at
   mailto:mar...@gaugusch.at wrote:
  
   Hi,
  
   Symptom:
   monitor:/mnt/1wire/10.FE771D020800 # cat temperature
   cat: temperature: Message too long
  
   I've updated my monitoring server from openSUSE 13.1 to 13.2, which
   broke owfs. I had 2.9p5 before and also tried to update to 2.9p8,
   but the problem stayed the same. Access using owdir, owget and
   owwrite works fine. I've started owfs in debug mode, leading to the
   following output (error at the bottom).
  
 DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 2.00 seconds
 DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
 DEBUG: ow_tcp_read.c:(63) attempt 8 bytes Time: 2.00 seconds
 DEBUG: ow_tcp_read.c:(113) read: 8 - 0 = 8
 DEBUG: ow_buslock.c:(54) pthread_mutex_lock 9A270CC begin
 DEBUG: ow_buslock.c:(54) pthread_mutex_lock 9A270CC done
 DEBUG: ow_buslock.c:(56) pthread_mutex_lock B779D9A0 begin
 DEBUG: ow_buslock.c:(56) pthread_mutex_lock B779D9A0 done
 DEBUG: ow_buslock.c:(56) pthread_mutex_unlock B779D9A0 begin
 DEBUG: ow_buslock.c:(56) pthread_mutex_unlock B779D9A0 done
 DEBUG: ow_buslock.c:(76) pthread_mutex_lock B779D9A0 begin
 DEBUG: ow_buslock.c:(76) pthread_mutex_lock B779D9A0 done
 DEBUG: ow_buslock.c:(79) pthread_mutex_unlock B779D9A0 begin
 DEBUG: ow_buslock.c:(79) pthread_mutex_unlock B779D9A0 done
 DEBUG: ow_buslock.c:(81) pthread_mutex_unlock 9A270CC begin
 DEBUG: ow_buslock.c:(81) pthread_mutex_unlock 9A270CC done
 DEBUG: ow_presence.c:(269) Presence of 10 FE 77 1D 02 08 00 3A
   FOUND on bus 127.0.0.1
 DEBUG: ow_cache.c:(546) Adding device location 10 FE 77 1D 02 08
   00 3A bus=0
 DEBUG: ow_cache.c:(635) Add to cache sn 10 FE 77 1D 02 08 00 3A
   pointer=0xb779d914 index=0 size=4
 DEBUG: ow_cache.c:(667) pthread_mutex_lock B779D9A0 begin
 DEBUG: ow_cache.c:(667) pthread_mutex_lock B779D9A0 done
 DEBUG: ow_cache.c:(670) pthread_mutex_unlock B779D9A0 begin
 DEBUG: ow_cache.c:(670) pthread_mutex_unlock B779D9A0 done
 DEBUG: ow_cache.c:(336) pthread_mutex_lock B779D9A0 begin
 DEBUG: ow_cache.c:(336) pthread_mutex_lock B779D9A0 done
 DEBUG: ow_cache.c:(336) pthread_mutex_unlock B779D9A0 begin
 DEBUG: ow_cache.c:(336) pthread_mutex_unlock B779D9A0 done
 DEBUG: ow_read.c:(88) pthread_mutex_lock B779D9A0 begin
 DEBUG: ow_read.c:(88) pthread_mutex_lock B779D9A0 done
 DEBUG: ow_read.c:(95) pthread_mutex_unlock B779D9A0 begin
 DEBUG: ow_read.c:(95) pthread_mutex_unlock B779D9A0 done
 DEBUG: ow_read.c:(96) /10.FE771D020800/temperature return -90
 DEBUG: ow_parsename.c:(61) /10.FE771D020800/temperature
  unique: 140, error: -90 (Message too long), outsize: 16
   unique: 141, opcode: RELEASE (18), nodeid: 41, insize: 64, pid: 0
   release[0] flags: 0x8000
  CALL: owfs_callback.c:(135) RELEASE
   path=/10.FE771D020800/temperature unique: 141, success, outsize: 16
  
  
  
   It might be related to the new kernel, but I'm not sure ...
   monitor:~ # uname -a
   Linux monitor

Re: [Owfs-developers] DS2482-800 long wire problem

2015-01-02 Thread Paul Alfille

Have you tried another channel on the DS2482-800 for the long run? The 8
channels are electrically separate.

I assume you've looked at some of the resources for 1-wire bus topology,
like http://www.maximintegrated.com/en/app-notes/index.mvp/id/148

Paul

On Fri, Jan 2, 2015 at 10:08 AM, Jan Sennesael jan.sennes...@skynet.be
wrote:

 I have a plugin board running on top of my pi containing a DS2482-800 and
 an
 2482-100 master. Both are connected through I2C.
 The DS18b20's that are connected are connected in bus layout and are
 powered
 (not parasite)
 Everything was running fine, but when i tried to add a couple of sensors i
 run into some troubles: Since these sensors are on the other side of the
 house, is added a long utp cat5e cable (long= 25m a 30m) to the first
 sensor. However, if i connect the sensor the whole channel of the
 DS2482-800
 stops working. If i disconnect it, the rest works again.
 I guess that there is already around 30m active. (so the total distance
 between the master and the new sensor is around 60m

 Since the cabling is ok i am guessing the total cable length is to long.
 Is there anything to solve this problem? (pull up resistor or cap?)  Would
 the 2482-100 be better at this? I didn't use it since this one draws power
 from the pi and the -800 is externally powered (board layout issue...)

 Thanks
 Jan



 --
 Dive into the World of Parallel Programming! The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Building OWFS on Archlinux

2014-12-16 Thread Paul Alfille

Hi. I'm sorry there build isn't working. Did you do the ./bootstrap,
./configure, make sequence?

One of the messages:
configure.ac:52: warning: AM_INIT_AUTOMAKE: two- and three-arguments
forms are deprecated. For more info, see:
configure.ac:52:

Is benign. (For that matter, what type of idiots change the format of
functions between versions, especially in a package meant to paper over
version differences!)

The build works on fedora and ubuntu and opensuse. Did the automake
--add-missing your error output mentions do anything?

Paul

On Mon, Dec 15, 2014 at 4:56 PM, joep j...@naturalmethods.org wrote:

Hi All,
I'm trying to build OWFS on a recent version of Archlinux
(3.12.34-1-ARCH #1 PREEMPT) running on a RaspberryPi but am having
various difficulties (I've been running owfs on Raspbian for close to 2
years now without any problems). There is an OWFS package in Arch but
it's failing to run (using --debug and fake devices does not help). I've
already identified that it needs additional libraries installed (eg
libusb-compat and a host of build environment packages). I also got
around (I think) around the python version issues (version 3 vs version
4) by using the configure script call specified in Arch's PKGBUILD
package file.

The OWFS configure script also seems to require version 1.13
(am__api_version='1.13') of some of the build tools. Arch has other
versions of these tools (a lot are at version 1.14). I've changed the
configure script to 1.14 but still am having issues. The last build
attempt gave ...

[pi_1@RasPi_1 owfs-2.9p7]$ sudo make install
[sudo] password for pi_1:
cd . /bin/sh
/home/pi_1/MyFiles/owfs/owfs-2.9p7/src/scripts/install/missing
automake-1.14 --foreign
configure.ac:52: warning: AM_INIT_AUTOMAKE: two- and three-arguments
forms are deprecated. For more info, see:
configure.ac:52:

http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:76: error: required file 'src/scripts/install/compile' not
found
configure.ac:76: 'automake --add-missing' can install 'compile'
Makefile:491: recipe for target 'Makefile.in' failed
make: *** [Makefile.in] Error 1

I have found a OWFS build guide on Arch at
http://sourceforge.net/p/owfs/mailman/message/27811887/ but that's from
2011. Any more recent guides or pointers?

--
Regards
Joe P.

http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Development status of owexternal

2014-11-26 Thread Paul Alfille

I think you have the right idea.

owexternal is a protocol to use non 1-wire devices as 1-wire slaves.

Obviously we can't use normal 1-wire reading, writing, IDs or selection.
Instead the device is described in a file with links to programs that do
the actual communication and return the result.

owexternal is actually already built into owserver. It isn't well tested
since I had no actual use case, so your help will be very appreciated.

This is the documentation:
http://owfs.org/index.php?page=external-sensor-design


On Wed, Nov 26, 2014 at 3:25 PM, Sven Giermann sven.gierm...@gmail.com
wrote:

 Hi,

 I just thought about writing my own owserver to support a simple relay
 card with a serial connection. I already have a binary to read and set
 relay states but need a way to access it from other software.
 Now the idea was to clone owserver by providing the same interface to
 allow use of every owfs capable client. While starting to read the code I
 stunbled across owexternal and found some threads in this list.

 But nothing I could really understand to try it on my own.
 So I wanted to ask: what is the current development status of owexternal?

 Even if it's still unstable/untested I would be interested in contributing
 to it - but I need a starting point. What needs to be configured and where?
 What does the (Perl?) script need to support?

 Any ideas where to start?

 Thx, Sven.


 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] 3.3V bus master

2014-11-21 Thread Paul Alfille

The DS2482 (i2c bus master) suggests that it can run at 3.3V level.

http://datasheets.maximintegrated.com/en/ds/DS2482-100.pdf

Paul

On Fri, Nov 21, 2014 at 4:53 PM, Jan Kandziora j...@gmx.de wrote:

 Am 21.11.2014 um 19:56 schrieb Jerry Scharf:
  Hi,
 
  I am looking at using the MAX31850 chip for my test setup. It is a 3.3V
  only device (will not take 5V on power.) Are there any bus masters
  and/or switches that support 3.3V for the power and data lines?
 
 I'd say, don't use parasite power, run the bus on 5 volts and just put a
 kiloohms voltage divider right before the DQ pin of the slave. The
 slaves are open-drain on their DQ output, so this should be sufficient.

 Kind regards

 Jan




 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE

 http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Custom 1-wire addresses

2014-11-12 Thread Paul Alfille

As Jan points out, the official source of 1-wire numbers is Maxim. In
general they reserve 0x00 to 0x80 and use the upper half of the family code
space for special runs and 3-rd party.

Some people have just chosen a number on their own -- Luis Swart took 0xFF
years ago and even proposed splitting the range for other 3rd party
developers.

Hobby Boards bought EE and EF and has type fields within the device to
identify different slaves.

EDS purchased and uses 7E similarly.

So if this slave is only for your own use, choose any number. If you want a
commercial product, investigate purchasing a family code.

In any case, think about the architecture. At the very least, there should
be a consistently accessed type and version field that can be read to allow
you to offer new versions and different types. i.e. OWFS will see your
family code, read the always available type field and then know which
special techniques are needed.

Paul


On Wed, Nov 12, 2014 at 3:25 PM, Jan Kandziora j...@gmx.de wrote:

 Am 12.11.2014 um 08:36 schrieb Andrey:
  Hello.
  I'm developing custom 1-wire devices, based on MSP430 chips.
  Those chips can implement ds2406 + ds1820 + ds2438 in one 1-wire slave.
 
 Oh, and to prevent you reinventing the wheel: there are Pascal Baertens
 BAE0910 and BAE0911 chips, which are really good - they even have an
 interpreter for on-board pre-processing firmware on board.

 (Plus, there are various AVR and PIC based onewire-slave solutions
 available.)

 If your chip isn't anything different from Pascal's, I would rather
 stick with these.

 Kind regards

 Jan


 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.

 http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Config owfs to use server?

2014-10-29 Thread Paul Alfille

Hi Roland,

Maybe I can help you understand the process.

Say you want to run owfs, owserver and owhttpd with a USB device and
Fahrenheit temperature scale.

Purely from the command line you would run:

owserver -F -u -p 4304 # reads from USB, serves port 4304
owfs -F -m /var/temp/1wire -s 4304 # reads from owserver, mounts
/var/temp/1wire
owhttpd -F -s 4304 -p  # reads from owserver, web serves localhost:
# notice that only owserver talks directly to the hardware bus master,
everything else talks to owserver

You could write a configuration file (/etc/owfs.conf) like this:
-F
!server: -s 4304
server: -u
server: -p 4304
owfs: -m /var/temp/1wire
owfs: --allow-other
owhttpd: -p 

The advantage is that all the programs can simply be run with
owserver -c /etc/owfs.conf
owfs -c /etc/owfs.conf
owhttpd -c /etc/owfs.conf

Note that many options apply to all ( like -F)
Some apply to owserver and some to the all others
Some are program-specific
Also the name /etc/owfs.conf is conventional, but completely arbitrary.
None of the programs look for any file unless explicitly specified. No
magic files.

Often the distribution packages set up a skeleton configuration file, and
run all the programs. They usually are pretty well documented.

Paul

On Wed, Oct 29, 2014 at 3:54 PM, Roland Franke fl...@franke-prem.de wrote:

 Hallo again,
 can you show here your complete config (/etc/owfs.conf)?
 May it be, that you have not set by the server the specific port and IP
 address?

 Like by me is here:
 server: usb - Where is the
 hardware connected (By you w1)
 server: port = 127.0.0.1:4304- What IP address and
 port
 should the server use for connecting from other modules
 server: pid_file = /var/run/owsever.pid- you can specific also the
 place where the .pid file will be stored and must not been seperately

 been set in the owfs.conf

 Best regards,
 Roland

 -Ursprüngliche Nachricht-
 From: Loren Amelang
 Sent: Wednesday, October 29, 2014 7:59 PM
 To: owfs-developers@lists.sourceforge.net
 Subject: [Owfs-developers] Config owfs to use server?

 I'm still trying to understand whether I have a possible conflict with both
 owfs and server trying to read my hardware. Something was updating the
 filesystem while server and httpd were not running...  My config is part of
 the default Ubuntu distribution for 14.04, with just the w1 added to
 point
 to my hardware.

 I notice in Roland's config he has set
 server: usb
 like I have set
 server: w1
 but he also sets
 owfs: server = 127.0.0.1:4304
 and I have no equivalent line.

 I don't even see an owfs process running:
 ---
 root  1151  0.0  0.1  20036   836 ?Ssl  Oct19   1:56
 /usr/bin/owftpd -c /etc/owfs.conf --pid-file /var/run/owfs/owftpd.pid
 root 13064  0.0  0.1  11828  1000 ?Ss   Oct26   0:00
 /usr/bin/owhttpd -c /etc/owfs.conf --pid-file /var/run/owfs/owhttpd.pid
 root 13605  0.0  0.2  53804  1168 ?Ssl  Oct26   0:00
 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid
 ---
 It seems owfs can be used without the ftp/http/server modules, so it must
 exist on its own somehow. But where?

 Should I add that owfs: server = 127.0.0.1:4304 line to my config? Or
 does
 ! server: server = localhost:4304
 do the same thing, since it supposedly applies to everything except server?

 What about owfs: pid_file = /var/run/owfs.pid? I don't have an owfs.pid
 file on my system...  Just the ftpd/httpd/server pid files.

 I see many configs with lines like owfs: mountpoint = /mnt/1wire. I don't
 understand why one would mount at /mnt/1wire when everything is already
 visible at /sys/devices/.

 Maybe the default Ubuntu install has done some of this for me, in some file
 I haven't found yet? I tend to assume that whoever made the official Ubuntu
 distribution knows much more than I do. But I do get occasional bad reads
 and bogus temperature values, and as I said, the filesystem was getting
 updated even while server was stopped.

 Loren

 | Loren Amelang | lo...@pacific.net |


 On Wednesday, October 29, 2014 at 9:27 AM,
 owfs-developers-requ...@lists.sourceforge.net wrote:


  From: Roland Franke fl...@franke-prem.de
  Subject: Re: [Owfs-developers] Missing data
  To: Roland Franke fl...@franke-prem.de, OWFS \(One-wire file
  system\) discussion and help   owfs-developers@lists.sourceforge.net
  Message-ID: 32224CCF5ADA40D38212CB7E0D3E7E8E@rolandAMD64
  Content-Type: text/plain; charset=utf-8
 
  Here is my configuration (As i now will be at home )
  owfs.conf is:
  error_print = 3
  error_level = 0
  format = f.i
  cache_size = 0
  Celsius
  foreground
  allow_root
  owfs: server = 127.0.0.1:4304
  owfs: pid_file = /var/run/owfs.pid
  owfs: mountpoint = /mnt/1wire
  server: usb
  server: port = 127.0.0.1:4304
  server: pid_file = /var/run/owsever.pid
  http: server = 127.0.0.1:4304
  http: port = 8080
  http: pid_file =

Re: [Owfs-developers] Missing data

2014-10-26 Thread Paul Alfille

Well there's always the possibility that there is a wiring problem, but
also there could be two processes competing for the same resource.

Is owserver and owfs running at the same time? Your configuration file
would have them both grabbing the same serial devices and stepping on each
other.

If they both run at the same time, owfs should connect to owserver and have
owserver make the exclusive hardware connection.

Paul

On Sat, Oct 25, 2014 at 2:58 PM, Coudy co...@chovan.net wrote:

 Hi,
 I'm using owfs with 19x DS18B20 temperature sensor with 2x DS9097 passive
 adapter. I have split my installation to two buses. Everything is running
 on my home NAS server (Core2Duo). I have problem with missing data.
 Sometimes data are not received.
 I have tried it running as owserver and read data with owread/owget, and
 running as fuse mount point and read data with cat commad. Result is same.
 To store values I use Zabbix.
 Here is my screenshot:
 data missing: https://dl.dropboxusercontent.com/u/7883291/owfs-bad.pdf
 data ok: https://dl.dropboxusercontent.com/u/7883291/owfs-ok.pdf

 What is wrong, what should I change ? Is it issue with timeout or what ?

 Thanks for any help.

 Here are my system infos:
 -
 this is my owfs.conf
 #ALL
 passive=/dev/ttyr00
 passive=/dev/ttyr01
 timeout_serial=5

 #OwFS
 mountpoint=/mnt/1wire
 allow_other

 # Display
 format = f.i.c # 1-wire address f amily i d code c rc
 alias=/etc/owfs.alias


 -
 list of sensor on buses:
 ls -l /mnt/1wire/bus.0
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_bojler
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_juzna
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_kurenie
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_kurenie_spiatocka
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_severna
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_tepla_voda
 drwxrwxrwx 1 root root 4096 okt 25 20:35 pivnica_tepla_voda_spiatocka
 drwxrwxrwx 1 root root 4096 okt 25 20:35 podkrovie_chodba
 drwxrwxrwx 1 root root 4096 okt 25 20:35 podkrovie_spalna
 drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_hostovska
 drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_chodba
 drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_obyvacka_jv
 drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_spajza_dole
 drwxrwxrwx 1 root root 4096 okt 25 20:35 prizemie_spajza_hore

 ls -l /mnt/1wire/bus.1
 drwxrwxrwx 1 root root 4096 okt 25 20:36 garaz
 drwxrwxrwx 1 root root 4096 okt 25 20:36 pivnica_rack
 drwxrwxrwx 1 root root 4096 okt 25 20:36 podkrovie_detska_j
 drwxrwxrwx 1 root root 4096 okt 25 20:36 podkrovie_detska_s
 drwxrwxrwx 1 root root 4096 okt 25 20:36 vonku




 --

 ___
 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

Re: [Owfs-developers] New Hobby Board barometer and humidity sensors

2014-10-25 Thread Paul Alfille

Can you tell me the type_number and version for the two devices? (Reading
from the owfs entries)? Both will show selected properties based on the
type number which Hobbyboards (and owfs) uses to distinguish the different
available sensors.

Paul

On Fri, Oct 24, 2014 at 10:57 PM, David Lazarou dlazaro...@gmail.com
wrote:

 Hi All,

 I recently purchased a new Hobby Board barometer and humidity sensor to
 add to my 1-wire network which uses a 1-wire USB adapter. However, while I
 do get data back from these devices, I see no barometric or humidity
 readings. I'm running the most recent code (owfs-2.9p8) which I noted
 supports these devices.
 This is what I see when I do a directory listing of the devices:

 barometer:

 # ls -l /tmp/1-wire/EF.F6962015
 total 0
 -r--r--r-- 1 root root  16 Oct 25 13:16 address
 -rw-rw-rw- 1 root root 256 Oct 25 13:16 alias
 -r--r--r-- 1 root root   2 Oct 25 13:16 crc8
 -r--r--r-- 1 root root   2 Oct 25 13:16 family
 -r--r--r-- 1 root root  12 Oct 25 13:16 id
 -r--r--r-- 1 root root  16 Oct 25 13:16 locator
 -r--r--r-- 1 root root  16 Oct 25 13:16 r_address
 -r--r--r-- 1 root root  12 Oct 25 13:16 r_id
 -r--r--r-- 1 root root  16 Oct 25 13:16 r_locator
 -r--r--r-- 1 root root  32 Oct 25 13:16 type
 -r--r--r-- 1 root root  12 Oct 25 13:17 type_number
 -r--r--r-- 1 root root   7 Oct 25 13:17 version

 humidity:

 # ls -l /tmp/1-wire/EF.A05F2015/
 total 0
 -r--r--r-- 1 root root  16 Oct 25 13:16 address
 -rw-rw-rw- 1 root root 256 Oct 25 13:16 alias
 -r--r--r-- 1 root root   2 Oct 25 13:16 crc8
 -r--r--r-- 1 root root   2 Oct 25 13:16 family
 -r--r--r-- 1 root root  12 Oct 25 13:16 id
 -r--r--r-- 1 root root  16 Oct 25 13:16 locator
 -r--r--r-- 1 root root  16 Oct 25 13:16 r_address
 -r--r--r-- 1 root root  12 Oct 25 13:16 r_id
 -r--r--r-- 1 root root  16 Oct 25 13:16 r_locator
 -r--r--r-- 1 root root  32 Oct 25 13:16 type
 -r--r--r-- 1 root root  12 Oct 25 13:18 type_number
 -r--r--r-- 1 root root   7 Oct 25 13:18 version

 I have both devices connected to a Hobby Board 4 channel hub.
 I have tried running the owfs server from a Raspberry Pi running Archlinux
 and from a laptop running Fedora 19. However, I get exactly the same
 results.
 I am successfully using other 1-wire devices on the network, so I don't
 thing there is any problems with the hardware.
 Can any one confirm that they have successfully used these devices?

 Thanks
 David


 --

 ___
 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

Re: [Owfs-developers] Bug: owfs crashes when browsing the the folder with dolphin

2014-10-18 Thread Paul Alfille

Sorry. Known bug in 2.9p7 with owfs. Fixed and new release later today.

Paul
On Oct 18, 2014 6:07 AM, Thomas Zimmermann m...@vdm-design.de wrote:

 Hi,
 I'm currently packaging owfs for openSUSE and got a bug report that in the
 package with systemd enabled owfs crashes as soon as one browses the
 /run/owfs
 folder with dolphin (KDE file manager).
 Browsing the folder with ls works just fine.

 To reproduce this I started owfs with the following parameters:
 /usr/bin/owfs -u --server=127.0.0.1 --allow_other /run/owfs

 The Backtrace looks like the following:

 
 [New Thread 0x7658c700 (LWP 20156)]
 [New Thread 0x75d8b700 (LWP 20158)]
 1413624377 DEFAULT: ow_parsename.c:(316) debug_crash 1413624377.190662

 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x7658c700 (LWP 20156)]
 0x77b684d3 in FS_ParsedName_setup (pn=0x76588b60,
 path=0x7af0
 /, pp=0x76587ae0) at ow_parsename.c:316
 316 CONNIN_RLOCK;
 (gdb) bt
 #0  0x77b684d3 in FS_ParsedName_setup (pn=0x76588b60,
 path=0x7af0 /, pp=0x76587ae0) at ow_parsename.c:316
 #1  FS_ParsedName_anywhere (path=0x7af0 /,
 remote_status=remote_status@entry=parse_pass_pre_remote,
 pn=pn@entry=0x76588b60) at ow_parsename.c:104
 #2  0x77b68cea in FS_ParsedName (path=optimized out,
 pn=pn@entry=0x76588b60) at ow_parsename.c:81
 #3  0x77b5ba3c in FS_fstat (path=optimized out,
 stbuf=0x7658bc30) at
 ow_fstat.c:25
 #4  0x778a197d in ?? () from /lib64/libfuse.so.2
 #5  0x778ab895 in ?? () from /lib64/libfuse.so.2
 #6  0x778abdd6 in ?? () from /lib64/libfuse.so.2
 #7  0x778a8be9 in ?? () from /lib64/libfuse.so.2
 #8  0x7767f0db in start_thread () from /lib64/libpthread.so.0
 #9  0x773b058d in clone () from /lib64/libc.so.6
 (gdb) l
 311 /* -- be added by Browse so  -- */
 312 /* -- a reader/writer lock is - */
 313 /* -- held until ParsedNameDestroy */
 314 /*  */
 315
 316 CONNIN_RLOCK;
 317 pn-selected_connection = NO_CONNECTION ; // Default bus
 assignment
 318
 319 return 0 ; // success
 320 }
 (gdb) p *pp
 $2 = {pathcpy = '\000' repeats 3448 times..., pathnow = 0x0, pathnext =
 0x76587ae0 , pathlast = 0x0}
 (gdb) p *path
 $3 = 47 '/'
 (gdb) p *pn
 $4 = {path = /, '\000' repeats 8192 times, path_to_server = /, '\000'
 repeats 4096 times, device_name = 0x0, known_bus = 0x0, type = ePN_root,
 state = ePS_normal,
   sn = \000\000\000\000\000\000\000, selected_device = 0x0,
 selected_filetype
 = 0x0, extension = 0, sparse_name = 0x0, subdir = 0x0, dirlength = 1,
 ds2409_depth = 0, bp = 0x0,
   selected_connection = 0x0, control_flags = 330, lock = 0x0, return_code
 = 0,
 detail_flag = 0, tokens = 0, tokenstring = 0x0}


 --

 It's compiled with the following options:


 --
 ./configure \
 --prefix=/usr \
 --libdir=/usr/lib64 \
 --disable-static \
 --enable-usb \
 --enable-owfs \
 --enable-owhttpd \
 --enable-owcapi \
 --enable-ownetlib \
 --enable-owftpd \
 --enable-owserver \
 --enable-owtap \
 --enable-owmon \
 --enable-owperl \
 --enable-owpython \
 --enable-owphp \
 --enable-owtcl \
 --with-systemdsystemunitdir=/usr/lib/systemd/system

 --

 The package can be found here:

 https://build.opensuse.org/package/show/home:Heinervdm:branches:home:Heinervdm:BGO-OD/owfs

 If any further information is needed, i saved a core dump so that I can
 try to
 provide them.

 Greetings,
 Thomas



 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://p.sf.net/sfu/Zoho
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push

Re: [Owfs-developers] Bugreport for ow-shell

2014-10-17 Thread Paul Alfille

Thank you. I had overlooked that masking bit. Will be included in p8

Paul

On Fri, Oct 17, 2014 at 1:30 AM, Vincent Danjean vdanjean.p...@free.fr
wrote:

   I forgot to add my personal repo to test new packages in the
 previous mail

 On 17/10/2014 07:21, Vincent Danjean wrote:
Hi
 
  On 17/10/2014 00:05, Mario Gruenwald wrote:
  Hi
 
  I tried reportbug and reportbug-ng, but it was too difficult for me.
  Therefore i write an simple Email.
 
  I have an USB-1wire-Adapter and some DS18S20 temprature sensors. After
 my
  last upgrade of ow-shell from 2.8p15-1 to 2.9p5-1.1 my temperature
 graphs had
  steps. You can see the effect in a graph at:
http://blaeser.vc-graz.ac.at/1wire.png
  After downgrade the problem disappeared. You can see it at
http://blaeser.vc-graz.ac.at/ow-shell-bug.png
  starting from 19:00.
 
  I guess it is the same problem as here:
  http://developer.mbed.org/users/snatch59/notebook/onewirecrc/
  citation begin -
  I have an DS1820 and my values looked quite the same.
 
  I think the problem is with the calculation of the enhanced 9bit
 calculation
  in  DS18S20::calculateTemperature(BYTE* data)
 
  Indeed, it seems similar to effects describe in comments.
 
  The manual of my DS1820 says:
 
  After reading the scratchpad, the TEMP_READ value is obtained by
 truncating
  the 0.5C bit (bit 0) from the temperature data...
 
  This truncation was missing in the code.
 
  I extended like this - which can be done better, I'm sure :-)   :
  citation end -
 
  It would be cool, if you can fix the current package for jessie or
 guide me,
  where and how to report the problem.
 
  I just uploaded yesterday the last version (2.9p7). It is on my personnal
  repo (see my signature) or in the NEW/BYHAND QUEUE (new library
 packages).
Please look if these new packages fix your problem. Else, I'm putting
  owfs developers in copy so that they can try to fix this bug.
 
Regards,
  Vincent
 
  kindly regards
  Mario
 
 

 --
 Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
 GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
 Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
 APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main



 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://p.sf.net/sfu/Zoho
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owhttpd - get clean output

2014-10-14 Thread Paul Alfille

If you add /text to the path the result is easier to parse.

For that matter, owhttpd isn't the easiest way to get pure data (as opposed
to a nice display). The file system, shell utilities, ownet within your own
program all give pure text.
On Oct 14, 2014 4:25 PM, somewire ung...@gmail.com wrote:

 Nevermind, I managed to find a way to get those temperatures. I take the
 whole answer (html headers, links, text) as a big string then I extract the
 only interesting part (from character 1000 to 1004, by example), knowing
 that the lenghth of the answering string is constant.




 --
 View this message in context:
 http://owfs-developers.1086194.n5.nabble.com/owhttpd-get-clean-output-tp10885p10886.html
 Sent from the OWFS Developers mailing list archive at Nabble.com.


 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://p.sf.net/sfu/Zoho
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Building the latest numbered release

2014-10-11 Thread Paul Alfille

Hi Gregg,

Most of the development is done on 64-bit systems. Not slackware, though,
so your work and testing is appreciated.

As for extensive testing -- clearly the recent spate of bugs after the last
release shows it wasn't extensive enough.

Paul

On Fri, Oct 10, 2014 at 11:54 PM, Gregg Levine gregg.drw...@gmail.com
wrote:

 Hello!
 Good news here. I've gotten Slackware 14.1 on 64 bit systems, to build
 properly.

 This Slackware 64 bit running on this laptop via a live CD, well in
 this case its a USB disk. I'll know more as I run the usual tests
 concerning the different programs for OWFS.

 Paul was the collection extensively tested on 64 bit systems? And
 using Slackware as opposed to the others?
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature fought the Time Wars, time and again.


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://p.sf.net/sfu/Zoho
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] 2.9p7 release

2014-10-08 Thread Paul Alfille

Ok, that was embarrassing.

I hadn't tested building from a fresh directory the download file rather
than just packaging up the development directory with make dist

Basically I commented the lint stuff from the two Makefiles.

OWFS 2.9p7
Release Notes

Oct 8, 2014

Fix build problems, otherwise no changes.

---

OWFS 2.9p6
Release Notes

Oct 7, 2014

One Wire File System
www.owfs.org

New Features
1. HobbyBoards Masterhub
A. New 4-port hub
 B. USB suport
C. Ethernet not yet implemented
D. Autodiscovery not yet implemented
2. New HobbyBoards Sensors
A. Updated Moisture Meter
B. Humidity
C. Barometer
3. Improved systemd support -- Tomasz Torcz

Fixes
1. Mutex errors and checking, including read-write lock error -- Christian
Magnusson
2. Longer timeput needed for FTDI serial adapters -- Johan Ström
3. FreeBSD fixes -- Johan Ström
4. mucl C library support -- der_tiger and Szabocls Nagy
5. Numerous fixes found by Coverity analysis
6. Configuration script fixes from Christian Magnusson and der_tiger
7. owcapi bug in OW_present -- Valery Grusdev
8. ownet payload size off by one -- Hans-Frieder Vogt
9. OSX mutex error -- Stefano Miccoli
10. Show HobbyBoard device version in decimal rather than hex
11. MAX31850 Termocouple correction -- Paul Panish
12. Endiaan fix for DS2408 -- Johan Ström
13. DS18B20 resolution fix -- Johan Ström
14. Python trouble with verion from CVS -- Johan Ström
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] tty2usb

2014-10-06 Thread Paul Alfille

I don't now. That's why I'm curious to hear about experiences. It should be
easy to build anywhere.

The algorithm used is simple:

1. Recursively search /sys/devices for busnum (which seems to indicate a
USB device)
2. Recursively search from each busnum directory for tty[A-Za-z]* (which
indicates a serial device)
3. Choose the longest path for a given tty device.

Paul


On Mon, Oct 6, 2014 at 3:47 AM, Colin Law clan...@gmail.com wrote:

 On 6 October 2014 04:30, Paul Alfille paul.alfi...@gmail.com wrote:
  After all the discussion about serial and usb pairing, I created a new
  little program that does it, called tty2usb
 
  http://sourceforge.net/projects/tty2usb
 
  Currently it only works on linux, but OSX and freebsd would be useful to
  add.
 
  Example use:
  paul@hz tty2usb-code$ tty2usb
  List tty - USB pairings
  TTY=ttyUSB0 bus=3 dev=3 USB=0403:6001
  TTY=ttyUSB1 bus=1 dev=6 USB=0403:6001
  TTY=ttyUSB2 bus=3 dev=14 USB=0711:0230
  TTY=ttyUSB7 bus=1 dev=7 USB=1A86:7523
  TTY=ttyUSB8 bus=1 dev=4 USB=10C4:EA60
 
 
  Once it works on all platforms, I'll incorporate is into owfs to help
 with
  serial tuning and auto-scanning.
 
  I'd really like testing and feedback. It's very easy to use --
  make
  sudo make install
  ttyusb

 Does it need udev or other service running?

 Colin


 --
 Slashdot TV.  Videos for Nerds.  Stuff that Matters.

 http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] tty2usb

2014-10-06 Thread Paul Alfille

Hi Michael,

There are two possible uses for the usb-tty mapping.

1. Discovery -- find a unique USB device (HobbyBoards, Eclo, etc) and then
find the tty port to use.
2. Tune a FTDI device when the /dev/tty port is passed to owfs.

You're right, of course. Probing an anonymous serial device is unsafe.

Paul

On Mon, Oct 6, 2014 at 6:13 PM, Michael Markstaller m...@elabnet.de wrote:

 Hi Paul,

 this is very interesting (one has 3x FTDI with 2-4 ports and 7x PL2303)
 and so I installed it straight away on several boxes.

 I suffer from this problem, that the kernel (or BIOS or whoever..)
 assigns different Bus/Device-IDs (and therefore tty) to the same device
 depending on:
 - cold(power-cycle) or a warm reboot
 - order of connection
 - Moon or Sun-Phase, I never found out :p

 My last conclusion was: only a device with a unique
 serial/name/description (like with FTxx) could be matched by a program
 (or udev-rule) to get onethe same /dev/xxx-Entry over all cases.
 It's even worse: Users change hubs, ports, ...

 The same might be sad but true for owfs  ttyUSBx, I wouldn't rely on that.
 That being said, I'll test; but my guess is: enumerate the device your
 looking for by other means, not bus/dev-id..

 Michael


 --
 Slashdot TV.  Videos for Nerds.  Stuff that Matters.

 http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] tty2usb

2014-10-06 Thread Paul Alfille

Hi Stefano,

/sys/bus/usb-serial/devices doesn't seem to pick up ttyACM? devices, but
does discover some devices I missed.

Actually the two methods give quite different results on my machine:

#-tty2usb output = 6 devices--

paul@hz tty2usb-code$ ./tty2usb
List tty - USB pairings
TTY=ttyACM0bus=1dev=10USB=04D8:F897
TTY=ttyUSB0bus=3dev=3USB=0403:6001
TTY=ttyUSB1bus=1dev=6USB=0403:6001
TTY=ttyUSB2bus=3dev=14USB=0711:0230
TTY=ttyUSB7bus=1dev=7USB=1A86:7523
TTY=ttyUSB8bus=1dev=4USB=10C4:EA60

#- /sys/bus/usb-serial/devices gives USB0-8 and no ACM0 and repeated
USB addresses 

paul@hz tty2usb-code$  for i in /sys/bus/usb-serial/devices/*; do echo
TTY=$(basename $i) bus=$( $i/../../busnum) dev=$( $i/../../devnum)
USB=$( $i/../../idVendor):$( $i/../../idProduct); done
TTY=ttyUSB0 bus=3 dev=3 USB=0403:6001
TTY=ttyUSB1 bus=1 dev=6 USB=0403:6001
TTY=ttyUSB2 bus=3 dev=14 USB=0711:0230
TTY=ttyUSB3 bus=3 dev=9 USB=06cd:010a
TTY=ttyUSB4 bus=3 dev=9 USB=06cd:010a
TTY=ttyUSB5 bus=3 dev=9 USB=06cd:010a
TTY=ttyUSB6 bus=3 dev=9 USB=06cd:010a
TTY=ttyUSB7 bus=1 dev=7 USB=1a86:7523
TTY=ttyUSB8 bus=1 dev=4 USB=10c4:ea60

#- lsusb shows -

paul@hz tty2usb-code$ lsusb | sort
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
UART Bridge / myAVR mySmartUSB light
Bus 001 Device 005: ID 0957:0718 Agilent Technologies, Inc.
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International,
Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 007: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial
adapter
Bus 001 Device 008: ID 047d:1003 Kensington Orbit TrackBall
Bus 001 Device 009: ID 077d:0410 Griffin Technology PowerMate
Bus 001 Device 010: ID 04d8:f897 Microchip Technology, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 004: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 0403:6001 Future Technology Devices International,
Ltd FT232 USB-Serial (UART) IC
Bus 003 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 003 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 006: ID 08bb:2904 Texas Instruments PCM2904 Audio Codec
Bus 003 Device 007: ID 0409:0050 NEC Corp. 7-port hub
Bus 003 Device 008: ID 0c45:1700 Microdia
Bus 003 Device 009: ID 06cd:010a Keyspan USA-49W serial adapter
Bus 003 Device 011: ID 07a6:8515 ADMtek, Inc. AN8515 Ethernet
Bus 003 Device 012: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 003 Device 013: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 003 Device 014: ID 0711:0230 Magic Control Technology Corp. MCT-232
Serial Port
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

It turns out the truth is somewhere in between. The keyspan 4-port serial
adapter was getting excluded by my logic, but is you were finding it
completely correctly. The ACM device is a valid 1-wire Bus Master (Hobby
Boards) that gets missed by your script.

I'll fix up tty2usb but still use the current algorithm unless you can help
me with ACM devices.

Paul

(disclaimer: I'm no linux kernel expert, so my post may turn out to be
inaccurate).


AFAIK sysfs is a linux kernel feature, independent of the availability of
udevd, so navigating /sys/ is the canonical way of obtaining info on
kernel objects and attributes. (And yes, it is the kernel that enumerates
USB devices and then notifies udevd)

However Tiger is right, the search heuristics should be more
accurate/simple.

On my linux system I have

$ tree /sys/bus/usb/devices
/sys/bus/usb/devices
|-- 1-0:1.0 - ../../../devices/pci:00/:00:1d.7/usb1/1-0:1.0
|-- 1-5 - ../../../devices/pci:00/:00:1d.7/usb1/1-5
|-- 1-5.2 - ../../../devices/pci:00/:00:1d.7/usb1/1-5/1-5.2
|-- 1-5.2:1.0 -
../../../devices/pci:00/:00:1d.7/usb1/1-5/1-5.2/1-5.2:1.0
|-- 1-5:1.0 - ../../../devices/pci:00/:00:1d.7/usb1/1-5/1-5:1.0
|-- 2-0:1.0 - ../../../devices/pci:00/:00:1d.0/usb2/2-0:1.0
|-- 3-0:1.0 - ../../../devices/pci:00/:00:1d.1/usb3/3-0:1.0
|-- 3-2 - ../../../devices/pci:00/:00:1d.1/usb3/3-2
|-- 3-2:1.0 - ../../../devices/pci:00/:00:1d.1/usb3/3-2/3-2:1.0
|-- 4-0:1.0 - ../../../devices/pci:00/:00:1d.2/usb4/4-0:1.0
|-- usb1 - ../../../devices/pci:00/:00:1d.7/usb1
|-- usb2 - ../../../devices/pci:00/:00:1d.0/usb2
|-- usb3 - ../../../devices/pci:00/:00:1d.1/usb3
`-- usb4 - ../../../devices/pci:00/:00:1d.2/usb4

and

$ tree

[Owfs-developers] tty2usb

2014-10-05 Thread Paul Alfille

After all the discussion about serial and usb pairing, I created a new
little program that does it, called tty2usb

http://sourceforge.net/projects/tty2usb

Currently it only works on linux, but OSX and freebsd would be useful to
add.

Example use:
paul@hz tty2usb-code$ tty2usb
List tty - USB pairings
TTY=ttyUSB0 bus=3 dev=3 USB=0403:6001
TTY=ttyUSB1 bus=1 dev=6 USB=0403:6001
TTY=ttyUSB2 bus=3 dev=14 USB=0711:0230
TTY=ttyUSB7 bus=1 dev=7 USB=1A86:7523
TTY=ttyUSB8 bus=1 dev=4 USB=10C4:EA60


Once it works on all platforms, I'll incorporate is into owfs to help with
serial tuning and auto-scanning.

I'd really like testing and feedback. It's very easy to use --
make
sudo make install
ttyusb

Paul Alfille
--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] how many 18b20s on a bus

2014-10-01 Thread Paul Alfille

I've done over 100 DS18S20's (passive) on passive, active, Link and DS9490
successfully. It isn't fast, but then your temperature changes aren't that
fast.

On Wed, Oct 1, 2014 at 4:53 PM, Roberto Spadim robe...@spadim.com.br
wrote:

 that what i stored here some years ago when testing ds1820 devices
 in other words 300*.01 = 3 seconds
 maybe less maybe more

 what update period you need?


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-30 Thread Paul Alfille

Ok, here is my code for mapping USB devices to tty devices. It's a script
and needs to be tested on various platforms.

---
#!/bin/sh

# find all directories with busnum (they are USB devices)
usbdirs=$(find /sys/devices -name busnum -printf %h\n)

# look at every USB
for f in $usbdirs
do
b=$(cat $f/busnum)
d=$(cat $f/devnum)
p=$(cat $f/idProduct)
v=$(cat $f/idVendor)
 # find tty devices under each usb
t=$(find $f -name tty[AU]* -prune -printf %f\n)
if [ -n $t ]
then
if [ $(echo $t | wc -w) == 1 ]
then
echo
echo $t
echo USB device number $d
echo $b:$d $v:$p
echo Full path: $f
fi
fi
done
---

On my desktop (Fedora with lots of devices:
ttyUSB6
USB device number 14
3:14 0711:0230
Full path:
/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3.2/3-3.2.1/3-3.2.1.7/3-3.2.1.7.2

ttyUSB6
USB device number 12
3:12 0451:2036
Full path:
/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3.2/3-3.2.1/3-3.2.1.7

ttyUSB6
USB device number 7
3:7 0409:0050
Full path: /sys/devices/pci:00/:00:14.0/usb3/3-3/3-3.2/3-3.2.1

ttyUSB0
USB device number 3
3:3 0403:6001
Full path: /sys/devices/pci:00/:00:14.0/usb3/3-4

ttyACM0
USB device number 39
1:39 04d8:f897
Full path: /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1

ttyUSB1
USB device number 33
1:33 0403:6001
Full path: /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.3

ttyUSB7
USB device number 37
1:37 1a86:7523
Full path: /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2.4

I'll need to remove duplicates caused by hubs being included.
It looks like choosing either the longer path name or higher device number
can select the device and not hub.

Paul


On Tue, Sep 30, 2014 at 9:50 AM, Stefano Miccoli mo...@icloud.com wrote:


 On 30 Sep 2014, at 08:32, Johan Ström jo...@stromnet.se wrote:

 Hi all,

 picking this up again. Lets summarize the main points:

 * auto-detection can only be relied on for certain pure USB devices
 * auto-detection can not be relied on when standard serial bridge chips
 are used
 * if we can resolve /dev/ttyUSB0 to a particular USB device, we can
 potentially select a smarter (i.e. improved FTDI) code path instead of
 regular read/write from the tty device.
 * /dev/ttyUSB0 is not stable, unless explicit devd setup is done.
 * this makes alterantive OWFS device addressing interesting, by specifying
 USB serial. this would avoid devd all together.


 excellent recap. Let me add another remark.

 It seems that Debian, and most of the developers like to run owserver and
 companion programs as root. Personally I do not like this: on production
 systems I run owserver without root privileges, so udev/devd is still
 necessary to set appropriate permissions to /dev files.

 Unfortunately this means that with serial emulators some manual setup is
 needed: inspecting syslog files, noting the device serial number, modifying
 the udev/devd script. Alternatively owserver and family should drop root
 privileges after startup.

 Stefano


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] How to tell if 1-wire hardware is plugged in?

2014-09-28 Thread Paul Alfille

'dmesg' is the command that shows the system messages, including USB
plug/unplug.
'lsusb' (if installed) will give a list of current USB devices.


On Sun, Sep 28, 2014 at 11:39 AM, Colin Law clan...@gmail.com wrote:

 On 28 September 2014 15:00, Chris Green c...@isbd.net wrote:
  I have a 1-wire installation which I am trying to diagnose remotely.
 
  A few days ago I had to replace the Beaglebone Black that was running
  with another one becuase I corrupted the memory on the original one
  and didn't have the ability to fix it there and then.
 
  So, I'm fairly sure I plugged in the 1-wire USB interface to the new
  system and also connected the two temperature measuring devices to it.

 If you look in syslog (or the equivalent) you should see the usb
 interface being recognised.

 Colin


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] How to tell if 1-wire hardware is plugged in?

2014-09-28 Thread Paul Alfille

As a wild guess, since this is a new machine, does /mnt/1-wire exist?

Yes owfs should be running. You can try it manually, with debugging, to get
more information.

First, try owserver from the command line:
owdir -s 4304

start up owfs:
owfs -s 4304 -m /mnt/1-wire --debug

and see if the debug messages give any information.

Paul

On Sun, Sep 28, 2014 at 5:04 PM, Chris Green c...@isbd.net wrote:

 On Sun, Sep 28, 2014 at 11:43:32AM -0400, Paul Alfille wrote:
 'dmesg' is the command that shows the system messages, including USB
 plug/unplug.
 'lsusb' (if installed) will give a list of current USB devices.

 Good point, I do have the adapter pluuged in:-

 chris@odin:~$ lsusb
 Bus 001 Device 002: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1
 Fob, 1-Wire adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 chris@odin:~$

 So where do I go from here?  I have a 1-wire device, I have owserver
 running but nothing at all is appearing at /mnt/1-wire.

 Should there be an owfs process running as well as owserver?  Because
 there isn't.

 --
 Chris Green


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-23 Thread Paul Alfille

Thank you Ekkehard, for your kind words.

To answer your last question first, you could use the feature request on
Sourceforge: https://sourceforge.net/p/owfs/feature-requests/ but few
people seem to do it. Most mention it here. What do you have in mind?

I think the problem with serial devices is not just listing them, but
rather the danger of randomly poking at them to see if they are a
recognized 1-wire bus master. I don't know of any agreed safe way to do it.
That's why USB with identifying fields is better -- reading those fields is
safe.

Paul Alfille

On Mon, Sep 22, 2014 at 3:51 PM, Ekkehard Pofahl ekkeh...@pofahl.de wrote:

 Hello OWFS team,

 first of all : Thank you, OWFS is great.

 2014-09-22 18:23 GMT+02:00 Paul Alfille paul.alfi...@gmail.com:

 but some USB-serial might be possible


 I think a very popular way to connect 1Wire is via the USB bus. I use
 LinkUSB with generic USB, and Link45 and the generic DS9097U via different
 USB to RS232 converters. I was very surprised, that OWFS even worked with
 the USB to RS232 converters.

 I use ttyUSB0.

 I think, many people (not only me) want to use ttyUSBn, either direct, or
 via converter to some other 1Wire stuff. It is also no problem to use USB
 Hubs in between. I did not use auxiliary power so far for 1Wire !

 No issues at all !

 Autodetect : Check out ttyUSBn, n= 0 to all, for the existence of an 1Wire
 device. I noticed, that the Maxim device does an autodetect for the devices
 on a PC. So it is defintely possible.

 The only help I can offer at the moment is to try it out, ;-) .

 Background : I have my heating controlled by an old PC, some 1Wire
 temperature sensors and a (serial) relais card. And I want to port it to a
 Raspberry Pi :

https://sites.google.com/site/raspihs1/

 I still have issues, what the best solution is. The only element which I
 can rely on is the OWFS server and Linux. The underlying system dies a slow
 death. After about 4 days it is dead. I hate the solution to reboot every
 day once. So there will be some further research.

 Before OWFS I tried out several other solutions. Including hand coding the
 1Wire protocol in Delphi.

 Allthough happy, I was looking for the OWFS additional feature wish list.
 I did not find one so far, ;-)

 Keep on the excellent work !

 Best regards
 Ekkehard Pofahl




 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-23 Thread Paul Alfille

Ok, I did some testing of various USB 1-wire bus masters:

LinkUSB -- 0403:6001 -- FTDI but no identifying charcteristics (Except
serial number, but that's probably not consecutive)
TAI603B -- 10c4:ea60 -- CP210x Unclear if it's generic or not
USB9097 --1a86:7523 -- HL-340 Seems generic
ECLO -- 0403:ea90 -- FTDI with UNIQUE product ID
MasterHub -- 04d8:f897 -- MTI with UNIQUE product ID
DS9490R -- 04fa:2490 -- Maxim with UNIQUE ID

So it looks like only  ECLO, the new Hobby Boards MasterHub, and the
DS9490R can be auto-detected by USB scanning. I had high hopes for the
LinkUSB, but perhaps I have an early version and the internal fields have
changed.

Paul Alfille




On Tue, Sep 23, 2014 at 3:40 PM, Johan Ström jo...@stromnet.se wrote:

  I'm all for auto-detection, when it is possible to do so reliably. As you
 mentioned in the other reply, randomly poking at stuff is neither reliable
 or safe..
 So, the question is what we can do to make it as smooth for the user as
 possible..

 A possibly a new approach, with OS-specific resolving you mentioned:

 If user specifies --link /dev/ttyS0, -d /dev/ttyS0 or other, we could try
 OS-specific lookups to find what serial hardware it is using. For example,
 if we can find out that it is a FTDI based device, we could try to use
 ft_ftdi instead of ft_serial. If we cannot find out, we just fall back to
 regular TTY access.

 If user specifies --link 2:3, -d 3:4, --link usb:NNSERIAL or such,  we
 look for that specific USB device. If it is a FTDI device, we use ft_ftdi.
 Else, we can either fail, or for device-types which are serial, we could
 try to reverse-lookup TTY using OS-specific approach.

 Note: on FreeBSD there are separate /dev permissions for accessing the TTY
 and the USB device. Not sure if Linux has the same.

 Or, a more intrusive approach, clean up all parameters and go a generic
 device-option: --device type[ port-or-address].
 Examples:
 --device link /dev/ttyS0 (would also possibly try to use OS specific
 resolving)
 --device link usb:3:4
 --device link usb:NNSERIAL
 --device ds9097 /dev/ttyS0
 --device ds9097 usb:3:4
 --device ds9097 usb:NNSERIAL
 --device ds9097u /dev/ttyS0
 --device i2c /dev/i2c-0
 --device masterhub /dev/ttyS0
 --device usb   (this would search for DS9490R or
 PuceBaboon or any other USb which we can *reliably* identify)

 What would your optimal owfs usage model look like?


 For the record, here are the usbconfig --dump_device_desc data for my two
 FTDI devices:

 ugen1.3: FT232R USB UART FTDI at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
 pwr=ON (90mA)
   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0200
   bDeviceClass = 0x
   bDeviceSubClass = 0x
   bDeviceProtocol = 0x
   bMaxPacketSize0 = 0x0008
   idVendor = 0x0403
   idProduct = 0x6001
   bcdDevice = 0x0600
   iManufacturer = 0x0001  FTDI
   iProduct = 0x0002  FT232R USB UART
   iSerialNumber = 0x0003  A9xD
   bNumConfigurations = 0x0001

 ugen2.3: USB FAST SERIAL ADAPTER FTDI at usbus2, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON (44mA)
   bcdUSB = 0x0110
   bcdDevice = 0x0400
   iManufacturer = 0x0001  FTDI
   iProduct = 0x0002  USB FAST SERIAL ADAPTER
   iSerialNumber = 0x0003  FTCDXXX
 (skipped all other attributes which are identical)



 Johan


 On 9/22/14 18:23 , Paul Alfille wrote:

 I notice in recent Linux (Fedora specifically) that USB devices get pretty
 consistently listed by a reasonably consistent and recognizable name in
 /dev/serial/by_id.

  I haven't looked to closely at all the USB fields yet, but some devices
 have unique identifiers rather than the generic USB/serial. I was hoping to
 scan for known patterns, apply any optimizations, and then connect. The
 upcoming USB HobbyBoards hub will have that.

  My dream is that owfs will be as automatic as possible. Currently we
 can automatically scan for:
 i2c
 DS9490R
 HA7Net
 OWSERVER-ENET
 w1

  Hardware serial will always be a problem, but some USB-serial might be
 possible.

  Paul

 On Mon, Sep 22, 2014 at 2:59 AM, Johan Ström jo...@stromnet.se wrote:


 On 22/09/14 00:21, Robin Gilks wrote:
  1. Trying to resolve a serial port TTY name (i.e. /dev/cuaU1 on
 FreeBSD)
  to a potential USB device is probably doable, but not without a lot of
  effort and OS specific code.
  I don't think it's worth trying to go down that road.
 
  How about using udev on Linux (is there an equivalent on other OSes?)
 that
  creates a symlink to a device node with a unique name from the type
 (FTDI)
  and bus number and OWFS looks for that specific device name.
 
  Just an idea (had to do that years ago with serial devices to sort out a
  connection to a weather station and an IR blaster, never sure what
 device
  names each would come up with!).
 
 

 I have a similar setup myself, using FreeBSD's devd. It uses my known,
 hard-coded USB serials to set up a symlink from /dev/cua-linkusb to
 /dev/cuaXXX when device is detected, to easier find which tty device I
 should be using

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-23 Thread Paul Alfille

Ok, I'm perplexed!

I need help mapping device name (e.g. /dev/ttyUSB0) to USB bus:devnum that
I get in libusb.

I can probably do it by parsing 'dmesg' but that's rather inelegant.
Perhaps the data is somewhere in /sys or /proc?

The problem is that after searching (and perhaps tuning) USB devices, I
then need to use them as a serial device.
I need to go in both directions -- both to not open use a bus master twice
and to check device names.

Paul

On Tue, Sep 23, 2014 at 5:37 PM, Dirk Opfer d...@do13.de wrote:

  Hi Paul,

 I have another one:

 Elabnet (PBM01)  -- 0403:6015 -- with UNIQUE product and manufacture ID

 Sorry for the delay. I'm still negotiating a sample for your.

 Thanks
 Dirk

 Am 23.09.2014 um 23:27 schrieb Paul Alfille:

 Ok, I did some testing of various USB 1-wire bus masters:

  LinkUSB -- 0403:6001 -- FTDI but no identifying charcteristics (Except
 serial number, but that's probably not consecutive)
 TAI603B -- 10c4:ea60 -- CP210x Unclear if it's generic or not
 USB9097 --1a86:7523 -- HL-340 Seems generic
 ECLO -- 0403:ea90 -- FTDI with UNIQUE product ID
 MasterHub -- 04d8:f897 -- MTI with UNIQUE product ID
 DS9490R -- 04fa:2490 -- Maxim with UNIQUE ID

  So it looks like only  ECLO, the new Hobby Boards MasterHub, and the
 DS9490R can be auto-detected by USB scanning. I had high hopes for the
 LinkUSB, but perhaps I have an early version and the internal fields have
 changed.

  Paul Alfille




 On Tue, Sep 23, 2014 at 3:40 PM, Johan Ström jo...@stromnet.se wrote:

  I'm all for auto-detection, when it is possible to do so reliably. As
 you mentioned in the other reply, randomly poking at stuff is neither
 reliable or safe..
 So, the question is what we can do to make it as smooth for the user as
 possible..

 A possibly a new approach, with OS-specific resolving you mentioned:

 If user specifies --link /dev/ttyS0, -d /dev/ttyS0 or other, we could try
 OS-specific lookups to find what serial hardware it is using. For example,
 if we can find out that it is a FTDI based device, we could try to use
 ft_ftdi instead of ft_serial. If we cannot find out, we just fall back to
 regular TTY access.

 If user specifies --link 2:3, -d 3:4, --link usb:NNSERIAL or such,  we
 look for that specific USB device. If it is a FTDI device, we use ft_ftdi.
 Else, we can either fail, or for device-types which are serial, we could
 try to reverse-lookup TTY using OS-specific approach.

 Note: on FreeBSD there are separate /dev permissions for accessing the
 TTY and the USB device. Not sure if Linux has the same.

 Or, a more intrusive approach, clean up all parameters and go a generic
 device-option: --device type[ port-or-address].
 Examples:
 --device link /dev/ttyS0 (would also possibly try to use OS specific
 resolving)
 --device link usb:3:4
 --device link usb:NNSERIAL
 --device ds9097 /dev/ttyS0
 --device ds9097 usb:3:4
 --device ds9097 usb:NNSERIAL
 --device ds9097u /dev/ttyS0
 --device i2c /dev/i2c-0
 --device masterhub /dev/ttyS0
 --device usb   (this would search for DS9490R or
 PuceBaboon or any other USb which we can *reliably* identify)

 What would your optimal owfs usage model look like?


 For the record, here are the usbconfig --dump_device_desc data for my two
 FTDI devices:

 ugen1.3: FT232R USB UART FTDI at usbus1, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON (90mA)
   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0200
   bDeviceClass = 0x
   bDeviceSubClass = 0x
   bDeviceProtocol = 0x
   bMaxPacketSize0 = 0x0008
   idVendor = 0x0403
   idProduct = 0x6001
   bcdDevice = 0x0600
   iManufacturer = 0x0001  FTDI
   iProduct = 0x0002  FT232R USB UART
   iSerialNumber = 0x0003  A9xD
   bNumConfigurations = 0x0001

 ugen2.3: USB FAST SERIAL ADAPTER FTDI at usbus2, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON (44mA)
   bcdUSB = 0x0110
   bcdDevice = 0x0400
   iManufacturer = 0x0001  FTDI
   iProduct = 0x0002  USB FAST SERIAL ADAPTER
   iSerialNumber = 0x0003  FTCDXXX
 (skipped all other attributes which are identical)



 Johan


 On 9/22/14 18:23 , Paul Alfille wrote:

 I notice in recent Linux (Fedora specifically) that USB devices get
 pretty consistently listed by a reasonably consistent and recognizable name
 in /dev/serial/by_id.

  I haven't looked to closely at all the USB fields yet, but some devices
 have unique identifiers rather than the generic USB/serial. I was hoping to
 scan for known patterns, apply any optimizations, and then connect. The
 upcoming USB HobbyBoards hub will have that.

  My dream is that owfs will be as automatic as possible. Currently we
 can automatically scan for:
 i2c
 DS9490R
 HA7Net
 OWSERVER-ENET
 w1

  Hardware serial will always be a problem, but some USB-serial might be
 possible.

  Paul

 On Mon, Sep 22, 2014 at 2:59 AM, Johan Ström jo...@stromnet.se wrote:


 On 22/09/14 00:21, Robin Gilks wrote:
  1. Trying to resolve a serial port TTY name (i.e. /dev/cuaU1 on
 FreeBSD)
  to a potential USB device

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-22 Thread Paul Alfille

I notice in recent Linux (Fedora specifically) that USB devices get pretty
consistently listed by a reasonably consistent and recognizable name in
/dev/serial/by_id.

I haven't looked to closely at all the USB fields yet, but some devices
have unique identifiers rather than the generic USB/serial. I was hoping to
scan for known patterns, apply any optimizations, and then connect. The
upcoming USB HobbyBoards hub will have that.

My dream is that owfs will be as automatic as possible. Currently we can
automatically scan for:
i2c
DS9490R
HA7Net
OWSERVER-ENET
w1

Hardware serial will always be a problem, but some USB-serial might be
possible.

Paul

On Mon, Sep 22, 2014 at 2:59 AM, Johan Ström jo...@stromnet.se wrote:


 On 22/09/14 00:21, Robin Gilks wrote:
  1. Trying to resolve a serial port TTY name (i.e. /dev/cuaU1 on FreeBSD)
  to a potential USB device is probably doable, but not without a lot of
  effort and OS specific code.
  I don't think it's worth trying to go down that road.
 
  How about using udev on Linux (is there an equivalent on other OSes?)
 that
  creates a symlink to a device node with a unique name from the type
 (FTDI)
  and bus number and OWFS looks for that specific device name.
 
  Just an idea (had to do that years ago with serial devices to sort out a
  connection to a weather station and an IR blaster, never sure what device
  names each would come up with!).
 
 

 I have a similar setup myself, using FreeBSD's devd. It uses my known,
 hard-coded USB serials to set up a symlink from /dev/cua-linkusb to
 /dev/cuaXXX when device is detected, to easier find which tty device I
 should be using for what (I think I have ~4 serial ports on my box)

 However, this doesn't solve the auto-deteciton problem, the user still
 needs to manually tell which USB device to be used, by serial-no or
 otherwise. And if that has to be done, it could just as well be done
 directly in owfs.


 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer

 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Issues with FTDI based USB-Serial dongle DS2480B

2014-09-19 Thread Paul Alfille

Thank you, Johan, for the detailed tests.

The idea of slurp was to collect any pending serial traffic and allow
communication with the bus master to be synchronized. I agree that matching
expected response exactly is optimal, but that supposes that you start from
a known clean state. I found in some of my early tests that old data was
still delivered with the system was restarted.

Obviously, testing is hardware-specific. The timing was adjusted based on
my tests -- not very scientific.

It sounds like you think we should adjust the slurp time-out, and perhaps
some of the FTDI timing parameters. Also there is a 0-baud issue which we
should look at fixing on our end as well. Is it the serial BREAK or baud
changed that does it?

Paul

On Fri, Sep 19, 2014 at 2:57 AM, Johan Ström jo...@stromnet.se wrote:

 Hi,

 I've noticed some problems using a FTDI based USB serial dongle together
 with a DS2480B based adapter (also known as DS9097U).
 On startup the device was not recognized at all, complaining about wrong
 responses. Anyone else seen these issues?

 I've debugged the problem and found the cause.
 On startup, this is what happens:


   DEBUG: ow_ds9097U.c:(287) Attempt 0 of 3 to initialize the DS9097U
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: C1
.
   DEBUG: ow_ds9097U.c:(381) Send the initial reset to the bus master.
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 71
q
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 0F
.
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.00 seconds
 TRAFFIC IN  NETREAD bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 70
p
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_ds9097U.c:(459) wrong response (70 not 00)


 After each TRAFFIC OUT byte above, a COM_Slurp() is issued to read and
 remove the response.

 The response to the 71 command should be 70.. Which is what we see..
 except that it fails to slurp those bytes, it's actually
 reading them as the response to the next command.

 After some further debugging and added printf statements, I realize that
 COM_slurp fails to read the bytes, and instead just timeouts (1ms).
 I've been working on my pure-ftdi-branch for the LinkUSB, where I've
 learned that the FTDI chips by default have a 16ms timeout for small
 transfers, making them not very efficient when dealing with few bytes
 like this.
 Manually changing my USB-serial dongle's setting to 1ms with libftdi,
 together with a slurp timeout of 2ms, seems to fix the problem. However,
 the slurp still times out, so I guess the accompanying COM_flush does
 the trick.. Running with default 16ms FTDI setting, and a slurp timeout
 of 100ms, DOES succeed with reading the slurped data [1], and all works
 fine.

 The proper way to solve this is probably to actually read the bytes we
 expect, not just hope that slurp catches them. However, this might be
 problematic when changing bitrates etc?
 The solution used above would  be to give the slurp a longer timeout.
 Besides that device init would take a few ms longer, would this have any
 other side effects?
 From the DS2480B code at least, it does not seem to slurp anywhere
 except on device init.

 For the record, the DS2480B works perfectly fine with my STLab 2 port
 dongle (MosChip mos78x0 chip).. except that the stable FreeBSD-10 kernel
 panics when setting baud rate 0, which happens sometimes in OWFS when
 trying to forcefully reset. This was patched in

 https://github.com/freebsd/freebsd/commit/120a212c4b16b5137d6acc436b8f5702a5f5bf35
 but until the fix hits the mainline kernel, I'll have to go with another
 dongle.

 Regards
 Johan


 [1]
 This is how a proper session looks, with the responses slurped (FTDI
 chip 16ms, COM_slurp timeout set to 100ms):

   DEBUG: ow_ds9097U.c:(287) Attempt 0 of 3 to initialize the DS9097U
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: C1
.
 TRAFFIC IN  slurp bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: CD
.
 Slurp timeout 10 us..
   DEBUG: ow_ds9097U.c:(381) Send the initial reset to the bus master.
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 71
q
 TRAFFIC IN  slurp bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 70
p
 Slurp timeout 10 us..
 TRAFFIC OUT write bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 0F
.
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.00 seconds
 TRAFFIC IN  NETREAD bus=0 (/dev/cua-labdesk)
 Byte buffer anonymous, length=1
 --000: 00
.
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_com_read.c:(83) COM_read, read 1 bytes.
 read_get=16302.00us, tcdrain=0.00us: 1



 --
 Slashdot TV.  Video for Nerds.  Stuff that Matters.

Re: [Owfs-developers] Owserver hang on TPLink WR703N with OpenWRT

2014-09-05 Thread Paul Alfille

Glad to hear there is a solution. I wonder if we can find a way to make
owfs handle USB problems more gracefully.

A description of getting owfs working on an embedded platform like the
WR703N would be great.

Paul


On Fri, Sep 5, 2014 at 6:23 AM, Colin Law clan...@gmail.com wrote:

 Thanks for the suggestions, after a nights sleep and some more
 experiments it seems that it is an issue with the USB hardware in the
 703.  If I use a non-powered usb hub between the router and the
 LinkUSB then all seems well (at least it has been running for a couple
 of hours without failure whereas without the hub it fails within a few
 minutes).  I have seen suggestions that the usb hardware can be a
 problem with USB1 devices and that an intervening hub fixes it, but I
 had not heard of a problem with a USB2 device.

 I will report back for the record when I am convinced whether this is
 a complete solution.

 I will also document how to get owfs and openWRT running on the
 router, I presume that would be considered useful for inclusion in the
 wiki.

 Cheers

 Colin

 On 5 September 2014 01:03, paul.alfille paul.alfi...@gmail.com wrote:
  Same version? The possible differences are version, endian status, usb
  hardware support, and c library.
 
 
  Sent via the Samsung Galaxy S™ III, an ATT 4G LTE smartphone
 
 
   Original message 
  From: Colin Law
  Date:09/04/2014 4:25 PM (GMT-05:00)
  To: OWFS (One-wire file system) discussion and help
  Subject: [Owfs-developers] Owserver hang on TPLink WR703N with OpenWRT
 
  Hi
 
  I have put OpenWRT (AA) on a TPLink WR703N and installed owserver from
  the openwrt repository (owserver version 2.8p13-1) with remarkably few
  problems.  Using a LinkUSB all seems well initially.  Unfortunately
  after a few minutes operation owserver hangs.  Running with log level
  9 the log contains:
  
  CALL: ow_parsename.c:FS_ParsedName_anywhere(95)
  path=[/28.601DE102/temperature12]
DEBUG: ow_cache.c:Cache_Get_Device(927) Looking for device 28 60 1D
  E1 02 00 00 C4
DEBUG: ow_cache.c:Cache_Get_Common(1083) Search in cache sn 28 60 1D
  E1 02 00 00 C4 pointer=0x77c8f900 index=0 size=4
DEBUG: ow_cache.c:Cache_Get_Common(1099) Value found in cache.
  Remaining life: 4 seconds.
DEBUG: ow_presence.c:CheckPresence(76) Found device on bus 0
DEBUG: ow_read.c:adjust_file_size(329) file_length=12 offset=0 size=1
DEBUG: ow_cache.c:Cache_Get_Common(1083) Search in cache sn 28 60 1D
  E1 02 00 00 C4 pointer=0x77c79130 index=0 size=8
DEBUG: ow_cache.c:Cache_Get_Common(1115) Value found in cache, but
  expired by 99 seconds.
DEBUG: ow_cache.c:Cache_Get_Simul_Time(986) Looking for conversion
  time 28 60 1D E1 02 00 00 C4
DEBUG: ow_cache.c:Cache_Get_Common(1083) Search in cache sn 00 00 00
  00 00 00 00 00 pointer=0x77c8f8f8 index=0 size=0
DEBUG: ow_cache.c:Cache_Get_Common(1119) Value not found in cache
DEBUG: ow_cache.c:Cache_Get_Internal(956) 28 60 1D E1 02 00 00 C4
 size=4
DEBUG: ow_cache.c:Cache_Get_Common(1083) Search in cache sn 28 60 1D
  E1 02 00 00 C4 pointer=0x77c78290 index=-2 size=4
DEBUG: ow_cache.c:Cache_Get_Common(1119) Value not found in cache
DEBUG: ow_select.c:BUS_select(66) Selecting a path (and device)
  path=/28.601DE102/temperature12 SN=28 60 1D E1 02 00 00 C4 last
  path=00 00 00 00 00 00 00 00
DEBUG: ow_select.c:BUS_select(79) Continuing root branch
DEBUG: loop.c:Ping_or_Send(112) Taking too long, send a keep-alive
 pulse
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0
 offset=0
DEBUG: to_client.c:ToClient(63) Send delay message
DEBUG: loop.c:Ping_or_Send(112) Taking too long, send a keep-alive
 pulse
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0
 offset=0
DEBUG: to_client.c:ToClient(63) Send delay message
DEBUG: loop.c:Ping_or_Send(112) Taking too long, send a keep-alive
 pulse
DEBUG: to_client.c:ToClient(56) payload=-1 size=0, ret=0, sg=0x0
 offset=0
DEBUG: to_client.c:ToClient(63) Send delay message
  ... ad infinitum  (or at least ad nauseam).
 
  It fails on two different 1-wire networks and two LinkUSB adaptors,
  one of which has been running with owserver on a Sheeva Plug for
  several years.
 
  Any suggestions gratefully accepted.
 
  Colin
 
 
 --
  Slashdot TV.
  Video for Nerds.  Stuff that matters.
  http://tv.slashdot.org/
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 
 
 --
  Slashdot TV.
  Video for Nerds.  Stuff that matters.
  http://tv.slashdot.org/
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net

Re: [Owfs-developers] [RESOLVED, PATCH] off-by-one bug in ownet/ow_server.c

2014-08-26 Thread Paul Alfille

Thank you Hans-Frieder. And Stafano as well for his recent patch.


On Sat, Aug 23, 2014 at 6:21 AM, Stefano Miccoli mo...@icloud.com wrote:

 For information only: the patch undoes a change introduced in

 commit 8af70c688c0d293ecb1e5d725b32f32f51d522fc
 Date:   Fri Apr 11 14:54:57 2014 +

 If possible I would suggest to tag the releases, just to make easier to
 identify commits tag -a r2.9p5 3e2cd99173d7277d714876abe710331c97d4eae5)
 (example only: double check if the commits is the actual one that
 corresponds to the given release.)

 Stefano

 On 23 Aug 2014, at 00:24, Hans-Frieder Vogt hfv...@gmx.net wrote:

  with 2.9p5, suddenly the ownetexample program does not work any more. I
 get
  the error message
  OWNET_dirprocess error: -5)
 
  The reaseon for this error is an off by one error, that was introduced
  somewhere between 2.9p0 (worked) and 2.9p5.
  The patch below restores the correct function of the ownet library.
 
  Kind regards,
  Hans-Frieder
 
  --- owfs-2.9p5.orig/module.orig/ownet/c/src/c/ow_server.c 2014-04-26
  17:48:46.0 +0200
  +++ owfs-2.9p5/module/ownet/c/src/c/ow_server.c   2014-08-23
 00:01:52.900939548
  +0200
  @@ -509,7 +509,7 @@ static int WriteToServer(int file_descri
io[nio].iov_base = (char *) sp-path ; // gives a spurious
 compiler
  error -- constant is OK HERE!
  #endif
io[nio].iov_len = strlen(sp-path) + 1;
  - payload =  io[nio].iov_len +1;
  + payload =  io[nio].iov_len;
nio++;
LEVEL_DEBUG(ToServer path=%s\n, sp-path);
}
 
  Hans-Frieder Vogt   e-mail: hfvogt at gmx .dot. net
 
 
 --
  Slashdot TV.
  Video for Nerds.  Stuff that matters.
  http://tv.slashdot.org/
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers



 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs can't write?

2014-08-07 Thread Paul Alfille

Indeed, Robin Gilks endian corrections were in 2.9p3

Can you try a newer version and see if the problem persists?

Paul


On Thu, Aug 7, 2014 at 2:45 AM, Robin Gilks g8...@gilks.org wrote:


  Hi Paul,
 
 
  On Wed, Aug 6, 2014 at 9:54 PM, Paul Alfille paul.alfi...@gmail.com
  wrote:
 
  Hi Akos,
 
  Can you clarify? Do some combinations of platform and version work and
  some not? Or do you have trouble in all circumstances.
 
 
  Normal PC with Linux (Ubuntu x64) works perfectly, regardless of version.
  That's why I think the hardware setup is fine.
  I use a HobbyBoards 8-relay board, everything is on factory default.
 
  PC environment is a bit more actual: 2.8p21
  Openwrt environment: temperature reading works from a 18S20.
  I try to write (and read back) PIO.x under owfs.
 
  Right now I encountered that writing to PIO.BYTE works as expected
  (appropriate relays will be turned on/off).
  Reading from PIO.BYTE also reflects the correct state.
  So the problem seems to be with PIO.x only.
 
  Maybe a big endian / little endian problem?

 That sounds like the endian problem I found on the 2413 dual output
 device. The fix I produced went into the main tree but I can't remember if
 it extends to the 2408.


 --
 Robin Gilks zl3rob/g8ecj
 Internet: g8...@gilks.orghttp://www.gilks.org





 --
 Infragistics Professional
 Build stunning WinForms apps today!
 Reboot your WinForms applications with our WinForms controls.
 Build a bridge from your legacy apps to the future.

 http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Limited Simultaneous Conversions?

2014-07-11 Thread Paul Alfille

Hi Colin,

I wonder if OWFS can already do what you want. If not, I have some ideas.

OWFS has a simultaneous command to trigger temperature conversion.

1. It works on all the sensors on a bus, using the trick that there is a
command to select the single slave on a 1-slave bus (for efficiency) but
that will actually select them all.
2. The sensors do need external power because temperature conversion is
power hungry and running many simultaneously can tax the data bus,
especially if other communication is being done.
3. OWFS remembers the time of the simultaneous and will wait long
enough before returning a temperature reading when temperature reading is
attempted. (A blocking read in other words).
4. Not all temperature sensors are involved. Many read temperature
continuously (Like DS2438, and 3rd party sensors) and all this fuss is
irrelevant.

You wanted to specify a list of sensors to do conversion on, rather than
all of them I guess. Is there a mix of passive and active sensors? Are you
worried about the total power budget or self-heating?

1. The command will be slower that the current simultaneous since each
sensor must be addressed independently.
2. I don't see an elegant way of implementing the interface to such a
command.
A. We could have a separate start temperature reading. We'd need a
separate timer for each and still block if read too early (or restart if
read too late).
B. We could write a list of slave addresses to a convert file, then
read the sorted results from another linked file, but this really bends our
syntax. (Variable-length fields). Doable, though.

Have you considered another approach? Use the threaded nature of OWFS and
just issue reads for each of your sensors in separate threads. Each will
return when done. They can run concurrently if the sensor is powered.

Paul Alfille



On Thu, Jul 10, 2014 at 2:09 PM, Colin Reese colin.re...@gmail.com wrote:

 Hello,

 After talking with iButtonLink, it was brought to my attention that without
 additional power, it is possible to have unsuccessful simultaneous read if
 too many sensors are on the network, due to current draw during the
 conversion.

 Using the TMEX API, I can perform a match ROM and then issue a conversion
 command, and then come back later to read the converted value. This way I
 can issue conversion commands for, say, 20 ROMs without waiting for
 conversion more than once.

 Is there an analogous feature in owfs, e.g. a 'simultaneous' with a
 specified group of ROMs?

 Thanks,
 Colin


 --
 Open source business process management suite built on Java and Eclipse
 Turn processes into business applications with Bonita BPM Community Edition
 Quickly connect people, data, and systems into organized workflows
 Winner of BOSSIE, CODIE, OW2 and Gartner awards
 http://p.sf.net/sfu/Bonitasoft
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Limited Simultaneous Conversions?

2014-07-11 Thread Paul Alfille

What interface do you you use for these reads? We could make owread (or the
owcapi interface) multithreaded.


On Fri, Jul 11, 2014 at 1:27 PM, Colin Reese colin.re...@gmail.com wrote:

 Hi Paul,

 Thanks for the detailed response.

 Yes, the concern is power draw. We find that converting groups of
 sensors simultaneously by ROM actually scales quite well. Using the TMEX
 API, you can easily issue a Skip ROM (xCC) followed by a Convert Temp
 (x44) to convert all devices simultaneously, but in the case that the
 user wants to manage both how many devices are converted (and which are
 currently being converted), it is nice to be able to send a list. Here
 is some raw data in a plot here (sorry if this appears spammy):
 http://interfaceinnovations.org/onewireoptimization.html

 In principle, I think you are right that threading is the way to go.
 I've not written code structured this way, so I'd have to learn myself
 how to. I assume you are describing a process where the calling code
 creates a thread for each owfs read operation, carries the reads out and
 returns them to the calling function (or puts them where they go).

 Thanks,
 Colin


 On 7/11/2014 05:14, Paul Alfille wrote:
  Hi Colin,
 
  I wonder if OWFS can already do what you want. If not, I have some ideas.
 
  OWFS has a simultaneous command to trigger temperature conversion.
 
  1. It works on all the sensors on a bus, using the trick that there is a
  command to select the single slave on a 1-slave bus (for efficiency) but
  that will actually select them all.
  2. The sensors do need external power because temperature conversion is
  power hungry and running many simultaneously can tax the data bus,
  especially if other communication is being done.
  3. OWFS remembers the time of the simultaneous and will wait long
  enough before returning a temperature reading when temperature reading
  is attempted. (A blocking read in other words).
  4. Not all temperature sensors are involved. Many read temperature
  continuously (Like DS2438, and 3rd party sensors) and all this fuss is
  irrelevant.
 
  You wanted to specify a list of sensors to do conversion on, rather
  than all of them I guess. Is there a mix of passive and active sensors?
  Are you worried about the total power budget or self-heating?
 
  1. The command will be slower that the current simultaneous since each
  sensor must be addressed independently.
  2. I don't see an elegant way of implementing the interface to such a
  command.
   A. We could have a separate start temperature reading. We'd need
  a separate timer for each and still block if read too early (or
  restart if read too late).
   B. We could write a list of slave addresses to a convert file,
  then read the sorted results from another linked file, but this really
  bends our syntax. (Variable-length fields). Doable, though.
 
  Have you considered another approach? Use the threaded nature of OWFS
  and just issue reads for each of your sensors in separate threads. Each
  will return when done. They can run concurrently if the sensor is
 powered.
 
  Paul Alfille
 
 
 
  On Thu, Jul 10, 2014 at 2:09 PM, Colin Reese colin.re...@gmail.com
  mailto:colin.re...@gmail.com wrote:
 
  Hello,
 
  After talking with iButtonLink, it was brought to my attention that
  without
  additional power, it is possible to have unsuccessful simultaneous
  read if
  too many sensors are on the network, due to current draw during the
  conversion.
 
  Using the TMEX API, I can perform a match ROM and then issue a
  conversion
  command, and then come back later to read the converted value. This
  way I
  can issue conversion commands for, say, 20 ROMs without waiting for
  conversion more than once.
 
  Is there an analogous feature in owfs, e.g. a 'simultaneous' with a
  specified group of ROMs?
 
  Thanks,
  Colin
 
 
 --
  Open source business process management suite built on Java and
 Eclipse
  Turn processes into business applications with Bonita BPM Community
  Edition
  Quickly connect people, data, and systems into organized workflows
  Winner of BOSSIE, CODIE, OW2 and Gartner awards
  http://p.sf.net/sfu/Bonitasoft
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  mailto:Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 
 
 
 
 
 --
  Open source business process management suite built on Java and Eclipse
  Turn processes into business applications with Bonita BPM Community
 Edition
  Quickly connect people, data, and systems into organized workflows
  Winner of BOSSIE, CODIE, OW2 and Gartner awards
  http://p.sf.net/sfu/Bonitasoft

Re: [Owfs-developers] MAX31850 code modifications

2014-07-09 Thread Paul Alfille

We care! And thank you.

I'll review and apply the changes.

Paul


On Wed, Jul 9, 2014 at 9:55 AM, ppanish ppan...@panishnet.com wrote:

 For anyone who cares,

 Attached is a new version of ow_1820.c with minor modifications to correct
 operation with the MAX31850 thermocouple sensor. I have checked operation
 with the device and this appears to function properly.

 Paul Panish





 --
 Open source business process management suite built on Java and Eclipse
 Turn processes into business applications with Bonita BPM Community Edition
 Quickly connect people, data, and systems into organized workflows
 Winner of BOSSIE, CODIE, OW2 and Gartner awards
 http://p.sf.net/sfu/Bonitasoft
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Humidity sensors

2014-07-06 Thread Paul Alfille

EDS
http://www.embeddeddatasystems.com/OW-ENV-TH--Temperature-Humidity-Sensor_p_168.html
iButtonLink: http://www.ibuttonlink.com/products/ms-th
CMCIEL:
http://www.cmciel.com/products-solutions/individual-products/relative-humidity-sensor-mrh001/
PCSensor: http://pcsensor.com/index.php?_a=productproduct_id=103

AAG seems to be out of business
Hobbyboards will be announcing a new humidity sensor, I'm told.


On Sat, Jul 5, 2014 at 8:37 PM, Daniel MacKay dan...@bonmot.ca wrote:

 Hey all!

 Does anyone have a source for cheap 1-wire humidity sensors?

 --
 Daniel MacKay
 Halifax, Nova Scotia, Canada





 --
 Open source business process management suite built on Java and Eclipse
 Turn processes into business applications with Bonita BPM Community Edition
 Quickly connect people, data, and systems into organized workflows
 Winner of BOSSIE, CODIE, OW2 and Gartner awards
 http://p.sf.net/sfu/Bonitasoft
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] t=-62 Errors?

2014-07-06 Thread Paul Alfille

Hi Loren,

As I understand, you are using the w1 interface and Beaglebone Black, but
I'm not sure what the bus-master is. A gpio pin?

-62 is not familiar to me. How often does it happen, and does the system
continue to work with occasional glitches or does it need reset? Note that
w1 errors might be reported by the system (dmesg).

I have a BBB and can try to see if I get the same errors if you describe
your setup a little more.

Paul Alfille


On Sat, Jul 5, 2014 at 8:32 PM, Loren Amelang lo...@pacific.net wrote:

 My problem with 12-bit reads degenerating to half-degree steps seems to be
 hiding since I built a new system with Ubuntu 14.04. I've only seen a few
 individual readings that looked stuck at the previous value since then,
 never full days of half-degree steps.

 But I still get two kinds of rare, occasional errors. There are the
 expected 85C errors, and these:
 ---
 Thu Jul 03 2014 22:15:01 GMT-0700 (PDT)
 cd 01 4b 46 7f ff 03 10 4a : crc=4a YES
 cd 01 4b 46 7f ff 03 10 4a t=28812
 Thu Jul 03 2014 22:20:02 GMT-0700 (PDT)
 ff ff ff ff ff ff ff ff ff : crc=c9 NO
 cd 01 4b 46 7f ff 03 10 4a t=-62
 Thu Jul 03 2014 22:25:02 GMT-0700 (PDT)
 c9 01 4b 46 7f ff 07 10 64 : crc=64 YES
 c9 01 4b 46 7f ff 07 10 64 t=28562
 ---
 Fri Jul 04 2014 13:55:01 GMT-0700 (PDT)
 c8 01 4b 46 7f ff 08 10 3f : crc=3f YES
 c8 01 4b 46 7f ff 08 10 3f t=28500
 Fri Jul 04 2014 14:00:02 GMT-0700 (PDT)
 ff ff ff ff ff ff ff ff ff : crc=c9 NO
 c8 01 4b 46 7f ff 08 10 3f t=-62
 Fri Jul 04 2014 14:05:02 GMT-0700 (PDT)
 cc 01 4b 46 7f ff 04 10 67 : crc=67 YES
 cc 01 4b 46 7f ff 04 10 67 t=28750
 ---

 I've never seen -62 errors before. All of them I've captured in detail
 match the above pattern, where the first byte string is all 'ff', and the
 second byte string matches the previous valid temperature exactly.

 What could be happening there? If the t= value is being derived from the
 byte string to the left of it, it should be the correct temperature. But it
 is always -62.

 Why are there two lines of bytes? Are they separate reads?


 Apparently there are supposed to be statistics somewhere, but I don't
 seem to have any. Here is all I find:
 ---
 ubuntu@arm:/sys/devices/w1_bus_master1$ ls
 28-008847d6  power  w1_master_add  w1_master_name
 w1_master_remove   w1_master_slaves
 28-00884d88  subsystem  w1_master_attempts w1_master_pointer
  w1_master_search   w1_master_timeout
 driver   uevent w1_master_max_slave_count  w1_master_pullup
 w1_master_slave_count
 ---

 Maybe the w1 interface doesn't provide statistics?


 Am I missing some source of deeper documentation than the web site
 provides?

 Loren

 | Loren Amelang | lo...@pacific.net |





 --
 Open source business process management suite built on Java and Eclipse
 Turn processes into business applications with Bonita BPM Community Edition
 Quickly connect people, data, and systems into organized workflows
 Winner of BOSSIE, CODIE, OW2 and Gartner awards
 http://p.sf.net/sfu/Bonitasoft
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-29 Thread Paul Alfille

Tomasz,

The systemd branch in owfs-code git is making progress.

I've added the socket initiation, and the sd-notify.
We stay in foreground more if systemd is the starting method, and ignore
port assignments from the configuration file and command line.
I do need to test and add more informative messages.

Can I add the .service files from your git repository to the base code?
They should be fairly universal.

A couple of things I'm not sure about:
1. encoding USB and i2c activation.
2. Can owfs (the filesystem) be activated on file access? I couldn't find
much on FUSE and systemd.
3. What's the best way to test and the monitor?

Paul


On Mon, Jun 9, 2014 at 7:01 AM, Tomasz Torcz to...@pipebreaker.pl wrote:

 On Thu, Jun 05, 2014 at 05:34:01PM -0400, Paul Alfille wrote:
  Tomasz,
 
  I'm having trouble visualizing how the systemd triggering works. When a
  program like owread tries to contact owserver, is owserver started? Is
 this
  done by monitoring the typical owserver port (4304)? How about other
  owserver friends?

   Hi Paul,

   Socket activation works is basically an inetd-like functionality.
 Systemd binds to 4304 port and listens.  When owread (or anything else)
 tries to connect to 4304, owserver is started (by systemd) and connection
 is
 handled to owserver.
   (in addition to TCP/UDP ports, systemd can also listen on UNIX sockets,
 FIFOs, netlink messages and few more sources; but it is not relevant to
 owfs).

   In Fedora, I treat owserver as a central multiplexer.  Other utilities
 (owhttpd, owftpd, fuse etc.) do not control 1-wire bus directly, but
 connect to owserver.  It's been working fine for few months (I did not
 receive any bugreports).  For the reference, here are *.service
 definition that I use: http://pkgs.fedoraproject.org/cgit/owfs.git/tree/
 With one central multiplexer, admin has only to customize owserver.service
 file and put his adapter settings there.

   Socket activation would let me simplify the dependencies encoded
 in *.service files - I would be able to drop
 Requires=/After=owserver.service lines.
 It would also make possible to restart owserver without dropping
 connections from owhttpd/owftpd/fuse etc.

  If you don't mind describing the process more, or giving pointers to
  documentation, perhaps we can assist in the implementation.
 
  I looked at the code you referenced (iodine), but it doesn't have any
  explanations. Is iodine an example client or the controlling code?

   Controlling code lies in systemd. iodine is a client. Traditionally,
 in order to accept network connections, you have to:
   - bind() socket
   - listen() on it
   - accept() incoming connections
   Those 3 steps are delegated to systemd.  When owserver is started by
 socket activation, it receives already connected file handles to sockets.
 The code in iodine represents how autodetection works: if there  are
 LISTEN_PID
 and LISTEN_FDS variables in environment, that means we are started under
 systemd socket-activation.
   If the are no LISTEN_* vars, code fallbacks to manually establishing
 sockets.

   Longer writeups are available:
   http://0pointer.de/blog/projects/socket-activation.html
   http://0pointer.de/blog/projects/socket-activation2.html
   I've personally used iodine patch as an example when implementing socket
 activation in some small utilities.

   Socket activation is inspired by Darwin's launchd feature. That's why
 I've asked about launchd in context of Mac porting.  I don't know launchd,
 but maybe some code can be shared?


 --
 Tomasz Torcz   72-|
 80-|
 xmpp: zdzich...@chrome.pl  72-|
   80-|



 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://www.hpccsystems.com
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Support for LinkUSB via libftdi

2014-06-23 Thread Paul Alfille

How about imbedding a list of known good vid/pid numbers and including a
command-line switch of --forceftdi to let people test others.

Or actually probe for the latency and buffer sizes you mentioned.

I'm not a big fan of command-line switches. They raise the barrier for new
users. I'd rather things just work perfectly. But since this would only
be an optional test it might be a good solution.

On Mon, Jun 23, 2014 at 1:54 AM, Johan Ström jo...@stromnet.se wrote:

Thank you! Looking forward to feedback from more experienced owfs-eyes..
:)

Scanning the USB bus for vid/pid should be no problem. However, the
DS9490R seems to use a special vid/pid, where the LinkUSB uses a generic
any-kind-of-ftdi-based-adapter-vid/pid. Unfortunately the dumped strings
doesn't seem to help much either:

My LinkUSB:

ugen4.2: FT232R USB UART FTDI at usbus4, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON (90mA)
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x
bDeviceSubClass = 0x
bDeviceProtocol = 0x
bMaxPacketSize0 = 0x0008
idVendor = 0x0403
idProduct = 0x6001
bcdDevice = 0x0600
iManufacturer = 0x0001 FTDI
iProduct = 0x0002 FT232R USB UART
iSerialNumber = 0x0003 A900fx3D
bNumConfigurations = 0x0001

Compared to another RS232-dongle (identical fields omited):
ugen3.3: USB FAST SERIAL ADAPTER FTDI at usbus3, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (44mA)
bcdUSB = 0x0110
iProduct = 0x0002 USB FAST SERIAL ADAPTER
iSerialNumber = 0x0003 FTCDDBSX

Not so much to go on.. the iProduct string is different, but I bet the
chip is not exactly the same, and that any FT232R based design identifies
itself as FT232R USB UART..

Johan

On 23/06/14 00:44, Paul Alfille wrote:

This is incredible work. Definitely will add to the master branch once the
final touches and test are done.

It's easy, using libusb, to read the vendor/product code. We do it for
DS9490R adapters now. Beyond vendor/product codes, there are many other USB
strings. One of them might be characteristic of all the relevant FTDI
adapters, even custom runs.

Paul

On Sun, Jun 22, 2014 at 5:20 PM, Johan Ström jo...@stromnet.se wrote:

I do have one thing on the todo list, and that is auto-detection.

Currently you have to explicitly specify a LinkUSB FTDI serial
number
(Linux: lsusb, FreeBSD: usbconfig). This is not very optimal. However,
at least my device uses the standard FTDI Vendor/product ID. This means
I cannot distinguish a random FTDI-based RS232-adapter and a LinkUSB,
without actually talking to the device. This can of course be done, but
I'm not sure it's acceptable to start writing to every FTDI adapter
found..

How is this solved with other auto-detected devices?

Looking forward to any and all feedback! :)
Johan

[1]

https://sourceforge.net/p/owfs/mailman/owfs-developers/thread/53905A08.40906%40stromnet.se/#msg32422357
[2] https://sourceforge.net/p/owfs/code/merge-requests/1/

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

___
Owfs-developers mailing
listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data

Re: [Owfs-developers] Support for LinkUSB via libftdi

2014-06-23 Thread Paul Alfille

I forgot that you are only dealing with linkUSB rather than DS9097U devices
on a usb-serial connection.

You're right, they should all have the same vid/pid and thus be
identifiable.

So we have several possibilities:
1. started as --link=/dev/ttyUSB0
A. We could use it as currently, with no libusb, just the USB-serial
driver provided by the kernel
B. We could use your modifications to the connection. Apparently you've
been able to connect and alter the device even when it's bound to the
serial driver?
2. started as -d /dev/ttyUSB0
A. linkUSB in DS9097U emulation more
B. Real DS9097U in a USB-serial slot
3. Scan for linkUSB devices

Clearly case 1B should use your speedup code.
We'd have to test if you can speed up 2A and 2B as well.

Case 3, the scan, is a little tricky. It's easy to scan, and even to test
(although we run the risk of confusing a non-llinkUSB device. It just gets
confusing for users explaining why they can scan for linkUSB but not other
serial 1-wire devices, nor links on serial connections, etc.

Scanning was never really possible in the old days of real serial ports.
Now that most ports are USB emulations, perhaps we can move to an
all-scanned solution (i2c, USB, USB/serial, some of the ethernet).



On Mon, Jun 23, 2014 at 9:09 AM, Johan Ström jo...@stromnet.se wrote:

  Afaik, the LinkUSB is only using a single VID/PID (0403/6001), which is
 shared by all FTDI serial adapters. The latency/buffer sizes are identical
 on power up as well. As far as I know, I have no way of knowing if the FTDI
 USB device is a LinkUSB or a random serial dongle connected to
 who-knows-what.
 The problem is thus not that we don't know the VID/PID, the problem is
 that OTHER things have the SAME VID/PID.

 With a regular link, the user has to specify --link=device.. correct?
 There is no autodetect for those. So the threshold would just be that we
 have another way of identifying the linkusb.


 Is the USB monitor code active by default if libusb is present, or do you
 have to enable it on startup with --usb-monitor or something?
 We could update the USB monitor code to scan for 0403/6001, and unless
 explicitly told (via --linkusb=serial or --linkusb=none), we send a  
 to all those FTDI devices and see what it might reply.
 * Most users will have one LinkUSB device, and it would be autodetected.
 * Users with LinkUSB devices, and non-LinkUSB ftdi devices, would have to
 use --linkusb=explicitserial to disable monitoring and only use that
 serial.
 * Users with NO LinkUSB devices, and non-LinkUSB ftdi devices, would have
 to use --linkusb=none to disable monitoring totally.

 Problems could arise in case user has a FTDI device which fails if a space
 is received.. which we cannot really know for sure.. :)

 An alternative would be to add a standalone scanner mode, which just
 outputs command line string with detected serials.

 Another barrier is that the user has to ensure that the running user has
 access to the device, or the bus scan won't find it at all. We cannot even
 tell the user We failed to find the device, unless explicitly told that
 we should be looking for one. If we are explicitly told which serial to use
 though, we can try to open it, but will get permission denied if that is
 the case (if I recall correct).



 On 23/06/14 14:39, Paul Alfille wrote:

 How about imbedding a list of known good vid/pid numbers and including a
 command-line switch of --forceftdi to let people test others.

  Or actually probe for the latency and buffer sizes you mentioned.

  I'm not a big fan of command-line switches. They raise the barrier for
 new users. I'd rather things just work perfectly. But since this would
 only be an optional test it might be a good solution.


 On Mon, Jun 23, 2014 at 1:54 AM, Johan Ström jo...@stromnet.se wrote:

  Thank you! Looking forward to feedback from more experienced owfs-eyes..
 :)

 Scanning the USB bus for vid/pid should be no problem. However, the
 DS9490R seems to use a special vid/pid, where the LinkUSB uses a generic
 any-kind-of-ftdi-based-adapter-vid/pid. Unfortunately the dumped strings
 doesn't seem to help much either:

 My LinkUSB:

 ugen4.2: FT232R USB UART FTDI at usbus4, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON (90mA)
   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0200
   bDeviceClass = 0x
   bDeviceSubClass = 0x
   bDeviceProtocol = 0x
   bMaxPacketSize0 = 0x0008
   idVendor = 0x0403
   idProduct = 0x6001
   bcdDevice = 0x0600
   iManufacturer = 0x0001  FTDI
   iProduct = 0x0002  FT232R USB UART
   iSerialNumber = 0x0003  A900fx3D
   bNumConfigurations = 0x0001

 Compared to another RS232-dongle (identical fields omited):
 ugen3.3: USB FAST SERIAL ADAPTER FTDI at usbus3, cfg=0 md=HOST spd=FULL
 (12Mbps) pwr=ON (44mA)
   bcdUSB = 0x0110
   iProduct = 0x0002  USB FAST SERIAL ADAPTER
   iSerialNumber = 0x0003  FTCDDBSX

 Not so much to go on.. the iProduct string is different, but I bet the
 chip is not exactly

Re: [Owfs-developers] Support for the DS2438 and the DS2436

2014-06-22 Thread Paul Alfille

The DS2438 is certainly supported and used in any number of devices
(humidity sensors, multifunction sensors from HobbyBoards and iButtonlink
among others).

he DS2436 is supported based on it's datasheet, but I can't recall if it's
been tested in real life. The command set is similar to the DS2438 so
should work well.


On Sun, Jun 22, 2014 at 4:25 AM, Gregg Levine gregg.drw...@gmail.com
wrote:

 Hello!
 New project time here. I'm busy trying to come up with something that
 will harness the amazing collection of parts here and I've got a batch
 of DS2436s that I want to apply, one of them certainly. Or the DS2438.
 I've got a batch of them as well.

 So I'm wondering. Am I correct in my belief that support for these
 parts is still included in our code series?
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature fought the Time Wars, time and again.


 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Support for LinkUSB via libftdi

2014-06-22 Thread Paul Alfille

This is incredible work. Definitely will add to the master branch once the
final touches and test are done.

It's easy, using libusb, to read the vendor/product code. We do it for
DS9490R adapters now. Beyond vendor/product codes, there are many other USB
strings. One of them might be characteristic of all the relevant FTDI
adapters, even custom runs.

Paul


On Sun, Jun 22, 2014 at 5:20 PM, Johan Ström jo...@stromnet.se wrote:

 Oops, git link fixes:

 https://sourceforge.net/u/stromnet/owfs/ci/ftdi-linkusb/tree/ (links to
 full tree, not only latest commit.. Click History to see all commits)

 And anonymous R/O clone command:
 git clone git://git.code.sf.net/u/stromnet/owfs owfs-stromnet

 On 6/22/14 23:09 , Johan Ström wrote:
  Hi,
 
  I've previously mentioned my work on LinkUSB performance improvements
  [1], and my goal to write a libftdi based implementation. The
  client-timings are generally cut about 2.5 times, depending on
  operation. A temp sensor is read in ~50ms instead of ~123ms.
 
  I now have some code which works fine, I'm running this with my LinkUSB
  1.5 on FreeBSD 9.2, performing temperature readings of 24 mixed
  temperature sensors, and 4 DS2406's. The temperature is read every 30
  seconds, and I (try to) scan for alarm ever 0.3 seconds. In other words,
  pretty heavy load. This has been running for a few days without any
  problems now.
 
  -(TL;DR below)-
  Some background (partly recap from earlier thread, but some new facts,
  and also repeating here to keep it gathered):
 
  This might be seen as micro-optimization, not really useful if you
  have a small net with few sensors. However, with a couple of DS2406's
  wired as inputs, I want as low reaction time as possible. This is quite
  a big step towards that goal. Other optimizations I'm doing is of course
  simultaneous conversions and using alarms etc, but that's another story.
 
  It all started with the random outages I wrote about in the other
  thread, in which I got some tips on the LinkUSB's different baudmodes.
  While looking into this, I also noticed that my DS2480B-based lab net
  performed much faster than the LinkUSB-based net. After some digging I
  found a few areas which could be improved.
 
  It boils down to mainly two things:
  * The FTDI FT232R (USB-RS232) chip which the LinkUSB utilizes, does
  not perform well with low amounts of data. The 64byte data buffer is by
  default flushed every 16ms, or when full. Most OWFS operations does not
  produce those amounts of data, so every transaction was delayed up to
  16ms. This has been mitigated by changing the FTDi chip timer to 1ms,
  and this is also the main reason libftdi is used. (FTDI docs calls this
  the latency timer)
  * The LinkUSB operated at 9600bps by default. Every sent byte on the
  1-wire bus is transmitted hex encoded, so 2 bytes is used for every
  single wire-byte. The DS2480B uses raw bytes, thus the LinkUSB yielded
  half the speed. This has been mitigated by using 19200bps instead of
  9600bps. Higher speed (38400) is not usable, since it overruns the
  1-Wire bus unless we take special care of rate-limiting. Could maybe be
  used to speed up the search functionality..
 
  A third thing I made some experiments on was the fact that OFWS jumps in
  and out of byte mode. However, trying to setting this mode explicitly
  and going in/out from it only when it was actually required, yielded
  worse timings in the end (with the above fixes applied).. Most likely
  since these changes where made in separate writes, taking up all the
  time which could potentially be gained. This experiment was ditched.
 
  I also noticed that there was some issues with using the BREAK condition
  to reset my device. The manual says a BREAK condition should be able to
  reset the device. I'm communicating with iButtonLink regarding this, and
  they are looking in to it, believing I've found a bug.
  Today I actually noticed that sending a break DOES work, but only when
  inside b mode (sending bytes to the wire). To be strict, the manual
  actually only talks about break support in the sections regarding the
  different data modes.. So might actually be working as intended.
 
  Anyway, one brute force way of resetting would thus be to send b, then
  break, then re-probe at 9600bps.. But I'll wait for further response
  from their developers before doing anything with this.
 
  ---
 
  The changes adds the following:
  * A LIBFTDI configure option: if not auto-detected/forced-yes, all ftdi
  related code is dropped out using similar conditionals as for example
  the W1 code.
  * A new device arg: --linkusb=serial which tells owfs to use libftdi
  to find a specific USB device with that serial.
  * Improved performance, if using the new device arg. Some examples:
  Reading a DS18S20 temperature (12bit, after simultaneous conversion. 9
  byte response):
  - Old LINK code: 123ms
  (- Old LINK code with FTDI latency timer externally set to 1ms:

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-12 Thread Paul Alfille

So can we have the situation where owserver waits for both

1. the USB device (say) to be available
2. a request to come in

and appear always available to the clients?


On Wed, Jun 11, 2014 at 7:59 AM, Jan Kandziora j...@gmx.de wrote:

 Am 11.06.2014 13:04, schrieb Paul Alfille:
 
  Also, in the documentation about systemd, there was a long passage about
  how the daemonizing should be done external to the program -- is that
 still
  the recommended policy? I guess the early testing could help there.
 
 Yeah, that's one of the key features of systemd. I daemonize you, you
 don't. The reason is by letting systemd daemonize the process it gets
 better control on the logging and situations when the child fails later
 on. This is often handled poorly by server applications and each of
 these re-implementations of daemonizing fails at some untested situations.

 owserver e.g. silently fails when the configured host adapter ist not
 present at the very beginning. Later on, it's not a problem when the
 host adapter goes missing - there's a technical reason for that
 behaviour, but from the admin's perspective, this is very odd behaviour
 which needs extra work to polish out.


 Kind regards

 Jan


 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-12 Thread Paul Alfille

You mention a couple of concepts: persistence and caching that I think
are orthogonal to the systemd -- at least in owfs's view of them.

1. Caching is the storing of 1-wire slave readings (in owserver) for a
short while to work around the relatively slow 1-wire bus speeds. It should
always be correct to refer back the the primary source -- the actual 1-wire
sensor. If systemd needs to restart an owserver, or wait until the server
is on line, the eventual data read would still be fresh.

2. The persistence we use is to reuse tcp connections to owserver, saving
the cost of the full tcp handshake. Clearly with an interruption in service
and restarting owserver, the tcp connection would be recreated. The design
is to fall back gracefully to non-persistent tcp connections if the
persistent connections are lost, timed out, or too many.

ownet is a client that talks to owserver, exclusively (it can't talk
directly to the 1-wire bus). All the caching would be on the owserver side.
If the ownet client handles data by saving it to disk, that should be
independent of systemd and owserver configuration.


On Thu, Jun 12, 2014 at 11:42 AM, Vajk Fekete vaj...@gmail.com wrote:

 Hi,

 How will this handle the persistent features? As I understand ownet does
 cache values for example. If the listener is handled externally and ownet
 is not running generally, would it have to use disk as persistence?

 Vajk


 On Thu, Jun 12, 2014 at 1:50 PM, Jan Kandziora j...@gmx.de wrote:

 Am 12.06.2014 12:38, schrieb Paul Alfille:
  So can we have the situation where owserver waits for both
 
  1. the USB device (say) to be available
  2. a request to come in
 
  and appear always available to the clients?
 
 As systemd handles the socket connection (and process start) alone, I
 think the only way to handle this both gracefully and not cluttering the
 systemd configuration with awkward workarounds is to support that
 situation that there is no host adaptor available when owserver is
 started.

 Kind regards

 Jan





 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers




 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-11 Thread Paul Alfille

Ok, I started a branch called systemd with the two files sd-daemon.c and
sd-daemon.h included.

A few things look a little strange -- systemd listen sockets are
automatically assigned as file descriptors number 3, 4, 5. I guess we'll
have to test systemd very early to make sure no other file descriptors have
been allocated.

Also, in the documentation about systemd, there was a long passage about
how the daemonizing should be done external to the program -- is that still
the recommended policy? I guess the early testing could help there.

Finally, as I understand it, systemd will present the listen socket to
owserver -- so we have to think about how command line parameters are
handled. (Or configuration files)

A typical owserver invocation:

# owserver usb bus master, Farenheit temperatures, connect to a remote
owserver as well
owserver -p 4304 -u -F -s otherhost:4304

We would ignore the  -p 4304 (actually all the -p parameters) but use
the other options?

The examples have only 1 LISTEN_FDS allocated, but hint that multiple could
be passed. That would be not problem for us.


On Mon, Jun 9, 2014 at 7:01 AM, Tomasz Torcz to...@pipebreaker.pl wrote:

 On Thu, Jun 05, 2014 at 05:34:01PM -0400, Paul Alfille wrote:
  Tomasz,
 
  I'm having trouble visualizing how the systemd triggering works. When a
  program like owread tries to contact owserver, is owserver started? Is
 this
  done by monitoring the typical owserver port (4304)? How about other
  owserver friends?

   Hi Paul,

   Socket activation works is basically an inetd-like functionality.
 Systemd binds to 4304 port and listens.  When owread (or anything else)
 tries to connect to 4304, owserver is started (by systemd) and connection
 is
 handled to owserver.
   (in addition to TCP/UDP ports, systemd can also listen on UNIX sockets,
 FIFOs, netlink messages and few more sources; but it is not relevant to
 owfs).

   In Fedora, I treat owserver as a central multiplexer.  Other utilities
 (owhttpd, owftpd, fuse etc.) do not control 1-wire bus directly, but
 connect to owserver.  It's been working fine for few months (I did not
 receive any bugreports).  For the reference, here are *.service
 definition that I use: http://pkgs.fedoraproject.org/cgit/owfs.git/tree/
 With one central multiplexer, admin has only to customize owserver.service
 file and put his adapter settings there.

   Socket activation would let me simplify the dependencies encoded
 in *.service files - I would be able to drop
 Requires=/After=owserver.service lines.
 It would also make possible to restart owserver without dropping
 connections from owhttpd/owftpd/fuse etc.

  If you don't mind describing the process more, or giving pointers to
  documentation, perhaps we can assist in the implementation.
 
  I looked at the code you referenced (iodine), but it doesn't have any
  explanations. Is iodine an example client or the controlling code?

   Controlling code lies in systemd. iodine is a client. Traditionally,
 in order to accept network connections, you have to:
   - bind() socket
   - listen() on it
   - accept() incoming connections
   Those 3 steps are delegated to systemd.  When owserver is started by
 socket activation, it receives already connected file handles to sockets.
 The code in iodine represents how autodetection works: if there  are
 LISTEN_PID
 and LISTEN_FDS variables in environment, that means we are started under
 systemd socket-activation.
   If the are no LISTEN_* vars, code fallbacks to manually establishing
 sockets.

   Longer writeups are available:
   http://0pointer.de/blog/projects/socket-activation.html
   http://0pointer.de/blog/projects/socket-activation2.html
   I've personally used iodine patch as an example when implementing socket
 activation in some small utilities.

   Socket activation is inspired by Darwin's launchd feature. That's why
 I've asked about launchd in context of Mac porting.  I don't know launchd,
 but maybe some code can be shared?


 --
 Tomasz Torcz   72-|
 80-|
 xmpp: zdzich...@chrome.pl  72-|
   80-|



 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://www.hpccsystems.com
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph

Re: [Owfs-developers] 1-wire communications information

2014-06-11 Thread Paul Alfille

I think differences between the 2 ARM platforms are at a lower level than
owfs. owfs basically uses the kernel-supplied i2c drivers for DS2482-X
communication. My guess is that one platform is using a dedicated i2c port,
and the other is using bit-banging GPIO support.

Paul Alfille

On Wed, Jun 11, 2014 at 8:36 AM, Michele Marcon m.mar...@riello-ups.com
wrote:

 Dear Sirs,
 We have discovered a strange behaviour of 1-wire devices with our two
 platforms.

 Platform A: Freescale i.MX27L (ARM926EJ-S rev 4 (v5l)), 64Mb RAM DDR,
 kernel 2.6.19.2 (with custom driver and patches), owfs 2.7p28, busybox

 Platform B: Freescale i.MX280 (ARM926EJ-S rev 5 (v5l)), 128Mb RAM DDR2,
 kernel 3.12.1 (with patches for device tree), Debian Wheezy 7.2


 The 1-wire communication is provided over I2C (with the DS2482S-100).

 We have tested 1-wire communication without external power (the power
 comes from the 1-wire bus) and we found that:

 1) the owfs process on platform B uses considerably more CPU usage than on
 platform A (on average 0.3% on platform A against 4% on platform B)

 2) the communication is much less reliable on platform B, and I read
 several bogus values (like: -121°C temperature)

 Since platform B is more advanced both in hardware and in software these
 results surprises us. Do you have any explanation?

 Thanks for your help,



 Michele Marcon

 Centro Ricerche
 RPS SpA
 Viale Europa, 7
 37045 Legnago VR
 Tel. +39 0442 635811 Fax. +39 0442 635934 - Mobile: +39 335 1233317
 Skype Id:  - Voip:
 E-mail: m.mar...@riello-ups.com
 Web: www.riello-ups.com
 --
 Per favore non stampare questo messaggio se proprio non è
 necessario
 Please consider the environment before printing this e-mail
 --

 Chi riceve il presente  messaggio e` tenuto a
 verificare se lo stesso non gli sia pervenuto per  errore.  In tal
 caso e` pregato di avvisare immediatamente il mittente  e,
 tenuto  conto  delle  responsabilita` connesse  all'indebito
 utilizzo e/o  divulgazione  del  messaggio  e/o
 delle  informazioni  in esso contenute,  voglia
 cancellare  l'originale  e distruggere  le varie copie  o
 stampe.

 The receiver  of this message is required to check
 if  he/she has received it erroneously.  If  so,  the
 receiver  is  requested to immediately inform the sender and - in
 consideration of the responsibilities  arising from undue use and/or
 disclosure of the message  and/or  the information contained therein -
 destroy the original message and any copy or printout thereof.




--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-05 Thread Paul Alfille

Tomasz,

I'm having trouble visualizing how the systemd triggering works. When a
program like owread tries to contact owserver, is owserver started? Is this
done by monitoring the typical owserver port (4304)? How about other
owserver friends?

If you don't mind describing the process more, or giving pointers to
documentation, perhaps we can assist in the implementation.

I looked at the code you referenced (iodine), but it doesn't have any
explanations. Is iodine an example client or the controlling code?

Paul


On Thu, Jun 5, 2014 at 4:19 PM, Tomasz Torcz to...@pipebreaker.pl wrote:

 On Thu, Jun 05, 2014 at 11:24:47AM -0700, Jerry Scharf wrote:
  Tomasz,
 
  This would need to be an option rather than the default operation mode.
  Not everyone can/will run owserver and friends from systemd.

   Systemd's socket activation design makes it very easy to gratefuly
 fallback into standard socket operation. In other words, it is
 easy to detect if systemd is being used and utilize systemd's
 features only in this situation. Running *without* systemd will
 make owserver transparently use current, stable and proven codepath.

   The biggest work is to make sure normal codepaths won't regress.
 This is what holds me from implementing systemd's socket activation now.
 But when I finish, systemd WILL NOT be required for owserver.
 owserver will continue to functions as it functions now, without the
 need for any special configurations.

  Also, the timeframe is quite distant.  I hope to make the patches
 this year, but I won't promise it.  I wouldn't mind if someone else
 implement systemd's feature before :)

 --
 Tomasz Torcz God, root, what's the difference?
 xmpp: zdzich...@chrome.pl God is more forgiving.



 --
 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/NeoTech
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-03 Thread Paul Alfille

Your changes were applied, Stefano.

Jan, I'd be happy to make any changes that ease package maintainer's work.


On Tue, Jun 3, 2014 at 9:08 AM, Stefano Miccoli mo...@icloud.com wrote:

 No, I do not think: I addressed only problems on Darwin.

 BTW I tested my patch under the assumption that manpages are installed in
 a tree which is distinct from the system one: I do not know how package
 maintainers will address this layout. The idea is to keep upstream as
 simple as possible and leave to package maintaners the decision of
 eventually remove the .so requests before packaging (e.g. by invocation of
 'soelim')

 S.

 On 03 Jun 2014, at 13:55, Jan Kandziora j...@gmx.de wrote:

  Am 03.06.2014 09:02, schrieb Stefano Miccoli:
  Do you mean installcheck?
 
  I was unaware of such a problem: both 'make check' and 'make
  installcheck' do nothing in src/man, since no test suite is defined.
 
  No, the checkinstall program which creates RPM and DEB packages just
  from a Makefile. It's not as good as packaging by hand, but very useful
  when you want to have an archive of different self-compiled versions or
  just abhor installing anything without crating a package of it.
 
  Usually, checkinstall works without problems, but with owfs-2.9, this
  had been broken somehow.
 
  Kind regards
 
Jan
 
 
 
 --
  Learn Graph Databases - Download FREE O'Reilly Book
  Graph Databases is the definitive new guide to graph databases and
 their
  applications. Written by three acclaimed leaders in the field,
  this first edition is now available. Download your free book today!
  http://p.sf.net/sfu/NeoTech
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers



 --
 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/NeoTech
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] patch: refactoring of src/man

2014-06-03 Thread Paul Alfille

Tomasz, would you use dbus for systemd? And would you send 1-wire data that
way or just program control.

Looking at dbus, it certainly looks like 1-wire data could map to it
easily. I'm just not sure if it would be useful.

Paul


On Tue, Jun 3, 2014 at 4:57 PM, Tomasz Torcz to...@pipebreaker.pl wrote:

 On Mon, Jun 02, 2014 at 09:27:05PM +0200, Stefano Miccoli wrote:
  Dear all:
 
  I tried to compile owfs on recent Darwin (OS X Mavericks), hitting
 against a number of problems, the biggest being how semaphores are
 implemented.
 
  I decided to tackle the problem starting from the simplest (trivial)
 issues: I will start with manpages.

   Are you going to step further and implement launchd socket activation
 for owserver and others?
 If so, I'd like to discuss it with you, as I plan to introduce socket
 activation for systemd
 environment in ow* tools sometime in future.

 --
 Tomasz Torcz   RIP is irrevelant. Spoofing is futile.
 xmpp: zdzich...@chrome.pl Your routes will be aggreggated. -- Alex
 Yuriev



 --
 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/NeoTech
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] VoCore remote 1-wire server?

2014-05-29 Thread Paul Alfille

I'll order one. I guess running 1-wire via one of the GPIO pins would be
the simplest solution. No mention of power source or budget that I could
find.

Paul


On Tue, May 27, 2014 at 12:20 PM, Colin Law clan...@gmail.com wrote:

 This might make a nice wifi remote 1-wire server if it gets off the ground.


 https://www.indiegogo.com/projects/vocore-a-coin-sized-linux-computer-with-wifi

 Colin


 --
 The best possible search technologies are now affordable for all companies.
 Download your FREE open source Enterprise Search Engine today!
 Our experts will assist you in its installation for $59/mo, no commitment.
 Test it for FREE on our Cloud platform anytime!

 http://pubads.g.doubleclick.net/gampad/clk?id=145328191iu=/4140/ostg.clktrk
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Everything is (apparently) running but nothing at /mnt/1-wire

2014-05-07 Thread Paul Alfille

I like that name owfsd but the program is confusingly called just owfs

Paul


On Wed, May 7, 2014 at 12:27 AM, Roberto Spadim robe...@spadim.com.brwrote:

 ops :P you are right, owfsd isn't running try starting it , you will need
 fuse filesystem support


 2014-05-07 1:24 GMT-03:00 Eloy Paris pe...@chapus.net:

 The owfs binary should also be run with a mount point of /mnt/1-wire so
 1-wire devices can show up at that directory. It doesn't seem like owfs is
 running.

 Cheers,

 Eloy Paris.-


 On May 7, 2014 12:44:11 AM GMT+04:00, Roberto Spadim 
 robe...@spadim.com.br wrote:
 more than one server is opening the usb port
 you should run the owserver, and others servers should connect to it
 
 
 2014-05-06 17:17 GMT-03:00 Chris Green c...@isbd.net:
 
  I'm running owfs on a Beaglebone Black (running Ubuntu 13.10), it was
  working OK previously but now, after some reboots, there's nothing
  appearing at /mnt/1-wire.
 
  The processes are running:-
 
  chris@beaglebone$ ps -ef | grep ow
  root   886 1  0 May04 ?00:00:18 /usr/bin/owftpd
 -c
  /etc/owfs.conf --pid-file /var/run/owfs/owftpd.pid
  root  1008 1  0 May04 ?00:00:00 /usr/bin/owhttpd
 -c
  /etc/owfs.conf --pid-file /var/run/owfs/owhttpd.pid
  root  1050 1  0 May04 ?00:00:00 /usr/bin/owserver
 -c
  /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid
 
 
  My owfs.conf file has only the following (apart from comments):-
 
  ! server: server = localhost:4304
  server: usb = all
 
  http: port = 2121
 
 
  ftp: port = 2120
 
 
  server: port = localhost:4304
 
 
  So what's going on (apart from very little!)?
 
  --
  Chris Green
 
 
 

 --
  Is your legacy SCM system holding you back? Join Perforce May 7 to
 find
  out:
  #149; 3 signs your SCM is hindering your productivity
  #149; Requirements for releasing software faster
  #149; Expert tips and advice for migrating your SCM now
  http://p.sf.net/sfu/perforce
  ___
  Owfs-developers mailing list
  Owfs-developers@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/owfs-developers
 


 --
 Eloy Paris




 --
 Roberto Spadim
 SPAEmpresarial
 Eng. Automação e Controle


 --
 Is your legacy SCM system holding you back? Join Perforce May 7 to find
 out:
 #149; 3 signs your SCM is hindering your productivity
 #149; Requirements for releasing software faster
 #149; Expert tips and advice for migrating your SCM now
 http://p.sf.net/sfu/perforce
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
#149; 3 signs your SCM is hindering your productivity
#149; Requirements for releasing software faster
#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New release 2.9p4

2014-05-02 Thread Paul Alfille

Good catch on the bug you patched.

I'd love to open a discussion of the UUID feature.

Let me state the problem area for background information:
1. owserver can be configured to send requests upstream -- to another
owserver
   A. This is done at the command line or via a configuration file
   B This cannot be done by a mear user
   C There is no limit on the length of the chain of owserver redirections.
2. Any chain of owserver redirections will eventually reach an end unless
there is a loop in the sequence.
   The solution: owserver adds a unique token (16 bytes of data) to the
end of messages passing upstream, and makes sure incoming messages don't
have it's unique token.

Potential problems:
1. owserver could be altered to not look for the token
  A. Well, any rogue program or shell script that you allow to be run can
be malicious.
 2. The tokens could be altered in transit.
   A. Again, if you don't have control of your network traffic, anyone can
inject any amount of traffic
3. The token might be non-unique
  A. The is a fail safe in terms of network traffic
  B Part of the 1-wire network would be inaccessible.

Based on my analysis, the only real risk is non-unique tokens, and given
the typically small extent of owserver networks, only modest uniqueness
guarantees are needed.

I thought of using an existing library (like UUID) but it's a nuisance for
users to find and build another package. Especially since we are
cross-platform and multiarchitecture. I try to reserve using libraries for
complex and essential functions (like USB access).

Still, I'm open to the debate.

Paul





On Thu, May 1, 2014 at 5:46 PM, Stefano Miccoli mo...@icloud.com wrote:

 Thanks for including my suggestions in p4!

 I found a small bug in the new antiloop code
 (module/owserver/src/c/owserver.c) please see the attached patch.

 Stefano




 PS:

 in my opinion, instead of the MD5 hash of some process data, a UUID  
 http://en.wikipedia.org/wiki/Universally_unique_identifier would be more
 appropriate for the antiloop feature.

 On 30 Apr 2014, at 02:35, Paul Alfille paul.alfi...@gmail.com wrote:

 Release Notes owfs 2.9p4
 4/30/2014

 New features
 1. Switch to git for source management
 Still hosted on sourceforge.net
  git clone git://git.code.sf.net/p/owfs/code owfs-code
 cvs history brought over.
 2. Clean and test DS2409 (Microlan) hubs
 Addressing problem found by Ors Tiszay
 Works well with passive devices
  Problems with powered slaves, but probably not a software issue.
 3. Improved and tested owserver protocol for server-to-server communication
 Use md5 hash for unique token
  Fixed byte counting issue in write messages
 Null-terminated string no longer required in path string
  (problem pointed out by Stefano Miccoli)
 4. Added /system/configuration/version
 Reports owserver version
 Request from Stefano Miccoli

 Fixes
 1. Double initialization of mutex fixed
 Show stopper in FreeBSD
 Found by Johan Strom


 --
 Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
 Instantly run your Selenium tests across 300+ browser/OS combos.  Get
 unparalleled scalability from the best Selenium testing platform available.
 Simple to use. Nothing to install. Get started now for free.

 http://p.sf.net/sfu/SauceLabs___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers




 --
 Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
 Instantly run your Selenium tests across 300+ browser/OS combos.  Get
 unparalleled scalability from the best Selenium testing platform available.
 Simple to use. Nothing to install. Get started now for free.
 http://p.sf.net/sfu/SauceLabs
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New release 2.9p4

2014-05-02 Thread Paul Alfille

Yes, I chose the second approach (hash of some relatively unique data) just
to avoid arbitrary limits, even if they are unlikely to be exceeded in
actual use. That's a general design objective throughout owfs.

I'm amused that you designed just about the same scheme, including the
hash, that is actually implemented. Part of the unique information is the
command line arguments, but Stefano found I botched the looping.


On Fri, May 2, 2014 at 11:00 AM, Stefano Miccoli mo...@icloud.com wrote:

 Actually your second option is exactly what is implemented in 2.9p4, with
 the md5 implementation from
 http://en.wikipedia.org/wiki/MD5#Simple_implementation, see SetupAntiloop
 in module/owserver/src/c/owserver.c

 My concerns about this approach are not linked to the security, but the
 robustness of the code. But of course, adding a dependency to a new library
 (like libuuid from util-linux) may not be the right answer.

 Stefano

 On 02 May 2014, at 16:30, Jerry Scharf sch...@lagunawayconsulting.com
 wrote:

  Paul,

 If all you are trying to do is loop detection, there are a couple ways I
 know to do it.

 The simplest way to do it is a time to live field like IP does it. Start
 it at some number (64 in standard for IP, but we would probably want it to
 be lower) and every time you forward it, decrement the TTL. When it hits 0,
 drop it (and possibly send an error back.) The number could be
 configurable, but something like 4 or 8 seems like a reasonable number.
 This requires no extra software and takes just a few lines to implement.

 The other way is to take a bunch of information like the IP address,
 owserver pid and a sequence number and run it through a cryptographic hash.
 The size is constant, the odds of duplication are vanishingly small and it
 discloses no information. You don't need anything secure, so 128 bit MD5 is
 fine and there may be even shorter ones. This requires having the crypto
 hash software available, which may be a challenge across the range of
 systems owserver can install.

 jerry

 On 05/02/2014 04:50 AM, Paul Alfille wrote:

 Good catch on the bug you patched.

  I'd love to open a discussion of the UUID feature.

  Let me state the problem area for background information:
 1. owserver can be configured to send requests upstream -- to another
 owserver
A. This is done at the command line or via a configuration file
B This cannot be done by a mear user
C There is no limit on the length of the chain of owserver redirections.
 2. Any chain of owserver redirections will eventually reach an end unless
 there is a loop in the sequence.
The solution: owserver adds a unique token (16 bytes of data) to the
 end of messages passing upstream, and makes sure incoming messages don't
 have it's unique token.

  Potential problems:
 1. owserver could be altered to not look for the token
   A. Well, any rogue program or shell script that you allow to be run can
 be malicious.
  2. The tokens could be altered in transit.
 A. Again, if you don't have control of your network traffic, anyone
 can inject any amount of traffic
 3. The token might be non-unique
   A. The is a fail safe in terms of network traffic
B Part of the 1-wire network would be inaccessible.

  Based on my analysis, the only real risk is non-unique tokens, and given
 the typically small extent of owserver networks, only modest uniqueness
 guarantees are needed.

  I thought of using an existing library (like UUID) but it's a nuisance
 for users to find and build another package. Especially since we are
 cross-platform and multiarchitecture. I try to reserve using libraries for
 complex and essential functions (like USB access).

  Still, I'm open to the debate.

  Paul





 On Thu, May 1, 2014 at 5:46 PM, Stefano Miccoli mo...@icloud.com wrote:

 Thanks for including my suggestions in p4!

  I found a small bug in the new antiloop code
 (module/owserver/src/c/owserver.c) please see the attached patch.

  Stefano




  PS:

  in my opinion, instead of the MD5 hash of some process data, a UUID  
 http://en.wikipedia.org/wiki/Universally_unique_identifier would be
 more appropriate for the antiloop feature.

  On 30 Apr 2014, at 02:35, Paul Alfille paul.alfi...@gmail.com wrote:

   Release Notes owfs 2.9p4
 4/30/2014

  New features
 1. Switch to git for source management
  Still hosted on sourceforge.net
  git clone git://git.code.sf.net/p/owfs/code owfs-code
  cvs history brought over.
 2. Clean and test DS2409 (Microlan) hubs
  Addressing problem found by Ors Tiszay
  Works well with passive devices
  Problems with powered slaves, but probably not a software issue.
 3. Improved and tested owserver protocol for server-to-server
 communication
  Use md5 hash for unique token
  Fixed byte counting issue in write messages
  Null-terminated string no longer required in path string
  (problem pointed out by Stefano Miccoli)
 4. Added /system/configuration/version
  Reports owserver version
  Request from Stefano

[Owfs-developers] New release 2.9p5 (replaces broken 2.9p4)

2014-05-02 Thread Paul Alfille

Thanks to quick testing by Stefano Miccoli and Johan Strom!

Release Notes owfs 2.9p5
5/2/2014

Fixes some show-stopper bugs in 2.9p4
Fixes:
1. Token creation problem from Stefano Miccoli
2. Select when no DS2409 (Microlan hub) present
Found by Johan Strom

Redacted release 2.9p4:

Release Notes owfs 2.9p4
4/30/2014

New features
1. Switch to git for source management
Still hosted on sourceforge.net
 git clone git://git.code.sf.net/p/owfs/code owfs-code
cvs history brought over.
2. Clean and test DS2409 (Microlan) hubs
Addressing problem found by Ors Tiszay
Works well with passive devices
 Problems with powered slaves, but probably not a software issue.
3. Improved and tested owserver protocol for server-to-server communication
Use md5 hash for unique token
 Fixed byte counting issue in write messages
Null-terminated string no longer required in path string
(problem pointed out by Stefano Miccoli)
4. Added /system/configuration/version
Reports owserver version
Request from Stefano Miccoli

Fixes
1. Double initialization of mutex fixed
Show stopper in FreeBSD
Found by Johan Strom
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New release 2.9p4

2014-05-02 Thread Paul Alfille

No aging needed. The token is generated once per owserver run and reused.
owserver only needs to see if a message is repeatedly coming in, and it
knows the direction (query or response) of the message.


On Fri, May 2, 2014 at 1:05 PM, Jerry Scharf sch...@lagunawayconsulting.com
 wrote:

  Paul,

 If you let the sender set the limit and it's something like a 8 or 16 bit
 value, it is effectively not limited. If the entire internet can work with
 64 router hops, it is really hard for me to imagine that owserver
 forwarding can't. With this, the state is in the forwarded message rather
 than owserver, which scales much better.

 I haven't looked at the code, but I would assume that each forwarding node
 needs to keep and age out a list of labels that it has forwarded and match
 every request against that list. Lots of complex code that has scaling
 issues. This has to be done on all the forwarding nodes because the loop
 may not include the originating node. That is a far greater limit than hop
 count, IMO.

 jerry


 On 05/02/2014 08:38 AM, Paul Alfille wrote:

 Yes, I chose the second approach (hash of some relatively unique data)
 just to avoid arbitrary limits, even if they are unlikely to be exceeded in
 actual use. That's a general design objective throughout owfs.

  I'm amused that you designed just about the same scheme, including the
 hash, that is actually implemented. Part of the unique information is the
 command line arguments, but Stefano found I botched the looping.


 On Fri, May 2, 2014 at 11:00 AM, Stefano Miccoli mo...@icloud.com wrote:

 Actually your second option is exactly what is implemented in 2.9p4, with
 the md5 implementation from
 http://en.wikipedia.org/wiki/MD5#Simple_implementation,
 see SetupAntiloop in module/owserver/src/c/owserver.c

  My concerns about this approach are not linked to the security, but the
 robustness of the code. But of course, adding a dependency to a new library
 (like libuuid from util-linux) may not be the right answer.

  Stefano

   On 02 May 2014, at 16:30, Jerry Scharf sch...@lagunawayconsulting.com
 wrote:

  Paul,

 If all you are trying to do is loop detection, there are a couple ways I
 know to do it.

 The simplest way to do it is a time to live field like IP does it.
 Start it at some number (64 in standard for IP, but we would probably want
 it to be lower) and every time you forward it, decrement the TTL. When it
 hits 0, drop it (and possibly send an error back.) The number could be
 configurable, but something like 4 or 8 seems like a reasonable number.
 This requires no extra software and takes just a few lines to implement.

 The other way is to take a bunch of information like the IP address,
 owserver pid and a sequence number and run it through a cryptographic hash.
 The size is constant, the odds of duplication are vanishingly small and it
 discloses no information. You don't need anything secure, so 128 bit MD5 is
 fine and there may be even shorter ones. This requires having the crypto
 hash software available, which may be a challenge across the range of
 systems owserver can install.

 jerry

 On 05/02/2014 04:50 AM, Paul Alfille wrote:

 Good catch on the bug you patched.

  I'd love to open a discussion of the UUID feature.

  Let me state the problem area for background information:
 1. owserver can be configured to send requests upstream -- to another
 owserver
A. This is done at the command line or via a configuration file
B This cannot be done by a mear user
C There is no limit on the length of the chain of owserver
 redirections.
 2. Any chain of owserver redirections will eventually reach an end unless
 there is a loop in the sequence.
The solution: owserver adds a unique token (16 bytes of data) to the
 end of messages passing upstream, and makes sure incoming messages don't
 have it's unique token.

  Potential problems:
 1. owserver could be altered to not look for the token
   A. Well, any rogue program or shell script that you allow to be run can
 be malicious.
  2. The tokens could be altered in transit.
 A. Again, if you don't have control of your network traffic, anyone
 can inject any amount of traffic
 3. The token might be non-unique
   A. The is a fail safe in terms of network traffic
B Part of the 1-wire network would be inaccessible.

  Based on my analysis, the only real risk is non-unique tokens, and
 given the typically small extent of owserver networks, only modest
 uniqueness guarantees are needed.

  I thought of using an existing library (like UUID) but it's a nuisance
 for users to find and build another package. Especially since we are
 cross-platform and multiarchitecture. I try to reserve using libraries for
 complex and essential functions (like USB access).

  Still, I'm open to the debate.

  Paul





 On Thu, May 1, 2014 at 5:46 PM, Stefano Miccoli mo...@icloud.com wrote:

 Thanks for including my suggestions in p4!

  I found a small bug in the new antiloop code

Re: [Owfs-developers] strange DS2762 persistence

2014-04-29 Thread Paul Alfille

Hi Ors,

After extensive testing I have mixed news.

I can replicate your findings -- the branches don't update and look
confused, but only with powered slaves. in this case I'm using the
Hobbyboards UVI sensor.

Using any number of passive devices works wonderfully. In fact I tested an
extensive network of over 100 passive devices.

Thus, I think the problem is hardware, but I can't tell you why. It could
be anything including ground loops or different ground levels.

Paul Alfille





On Fri, Apr 18, 2014 at 4:16 AM, Ors Tiszay listaku...@gmail.com wrote:

 Hi Paul,

 Yes, it's been sitting on my desk for a few days now. And still:


 # ls -al /mnt/owfs/1F.F96B0800/aux/

 total 0
 drwxr-xr-x 1 root root 8 Apr 16 09:34 .
 drwxrwxrwx 1 root root 8 Apr 18 10:10 ..

 # ls -la /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/
 total 0
 drwxrwxrwx 1 root root   8 Apr 18 10:11 .

 drwxr-xr-x 1 root root   8 Apr 16 09:34 ..
 --w--w--w- 1 root root   1 Apr 18 10:11 PIO
 drwxrwxrwx 1 root root   8 Apr 18 10:11 WS603

 -r--r--r-- 1 root root  16 Apr 16 09:34 address
 -rw-rw-rw- 1 root root 256 Apr 16 09:34 alias
 -rw-rw-rw- 1 root root  12 Apr 18 10:11 amphours
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 cc
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 ce
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 coc

 -r--r--r-- 1 root root   2 Apr 16 09:34 crc8
 -r--r--r-- 1 root root  12 Apr 16 09:34 current
 -rw-rw-rw- 1 root root  12 Apr 16 09:34 currentbias
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 dc
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 de
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 defaultpmod
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 defaultswen
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 doc

 -r--r--r-- 1 root root   2 Apr 16 09:34 family
 -r--r--r-- 1 root root  12 Apr 16 09:34 id
 -r--r--r-- 1 root root  16 Apr 16 09:34 locator
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 lock.0
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 lock.1
 -rw-rw-rw- 1 root root   3 Apr 18 10:11 lock.ALL

 -rw-rw-rw- 1 root root 256 Apr 16 09:34 memory
 -r--r--r-- 1 root root   1 Apr 18 10:11 mstr
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 ov
 drwxrwxrwx 1 root root   8 Apr 18 10:11 pages
 -r--r--r-- 1 root root   1 Apr 18 10:11 pmod
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 ps

 -r--r--r-- 1 root root  16 Apr 16 09:34 r_address
 -r--r--r-- 1 root root  12 Apr 16 09:34 r_id
 -r--r--r-- 1 root root  16 Apr 16 09:34 r_locator
 -r--r--r-- 1 root root   1 Apr 18 10:11 sensed
 -r--r--r-- 1 root root   1 Apr 18 10:11 swen
 -r--r--r-- 1 root root  12 Apr 18 10:11 temperature

 -r--r--r-- 1 root root  32 Apr 16 09:34 type
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeB
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeE
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeJ
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeK
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeN
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeR
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeS
 drwxrwxrwx 1 root root   8 Apr 18 10:11 typeT
 -rw-rw-rw- 1 root root   1 Apr 18 10:11 uv
 -rw-rw-rw- 1 root root  12 Apr 18 10:11 vbias
 -r--r--r-- 1 root root  12 Apr 18 10:11 vis
 -r--r--r-- 1 root root  12 Apr 18 10:11 volt
 -rw-rw-rw- 1 root root  12 Apr 18 10:11 volthours

 # cat /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/volt
 0

 # cat /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/type
 DS2760

 br,
 Ors


 On Thu, Apr 17, 2014 at 3:25 AM, Paul Alfille paul.alfi...@gmail.comwrote:

 Let me confirm that you physically disconnected the DS2762 rather than
 just external power?
 On Apr 16, 2014 4:05 AM, Ors Tiszay listaku...@gmail.com wrote:

 Hi,

 I have owfs running on a Gumstix Overo Earth, with a DS9490 bus master,
 which in turn is connected to a Hobby-Boards DS2409-based 8 channel hub
 (bought years ago when the DS2409 was still around, wish they still were).
 The bus then branches out to several directions, carrying a total of ~10
 sensors, mostly DS18.20 with the odd DS18S20/HIH3610 combo thrown in, so
 far using ch1 main and the aux of the hub.

 On ch2 aux I have a DS2762 based moisture meter board. Board was working
 fine for a few days in test, but when I disconnected it to be moved to its
 final location, I noticed that the script taking the readings every 30
 seconds kept returning values even after the board was disconnected. More
 precisely, the values read are either 0 or very close to 0 (-7.8125E-05 for
 current), but the surprising thing is that the whole file structure remains
 in place even days after the board is disconnected:

 This is what it looks like 3 days after disconnecting the moisture meter
 board:


 # ls -al /mnt/owfs/1F.F96B0800/aux   # - this is ch2 of the hub
 total 0
 drwxr-xr-x 1 root root 8 Apr 16 09:34 .
 drwxrwxrwx 1 root root 8 Apr 16 09:41 ..


 But reading the DS2762 as if it was still connected:

 # ls -al /mnt/owfs/1F.F96B0800/aux/30.4CF9B812
 total 0
 drwxrwxrwx 1 root root   8 Apr 16 09:49 .
 drwxr-xr-x 1 root root   8 Apr 16 09:34 ..
 --w--w--w- 1 root root

[Owfs-developers] New release 2.9p4

2014-04-29 Thread Paul Alfille

Release Notes owfs 2.9p4
4/30/2014

New features
1. Switch to git for source management
Still hosted on sourceforge.net
 git clone git://git.code.sf.net/p/owfs/code owfs-code
cvs history brought over.
2. Clean and test DS2409 (Microlan) hubs
Addressing problem found by Ors Tiszay
Works well with passive devices
 Problems with powered slaves, but probably not a software issue.
3. Improved and tested owserver protocol for server-to-server communication
Use md5 hash for unique token
 Fixed byte counting issue in write messages
Null-terminated string no longer required in path string
(problem pointed out by Stefano Miccoli)
4. Added /system/configuration/version
Reports owserver version
Request from Stefano Miccoli

Fixes
1. Double initialization of mutex fixed
Show stopper in FreeBSD
Found by Johan Strom
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] New release 2.9p4

2014-04-29 Thread Paul Alfille

Hi Gregg,

The transition (cvs-git) was recent (a couple of weeks). The biggest
barrier was teaching an old dog (me) new tricks.

You are right, there are many source management systems available, but it
adds complexity to use them simultaneously.

cvs was working fine, and I had some nice reporting tools that I haven't
been able to replicate. However, git seems to have a number of advantages:
1. renaming and reorganizing files doesn't lose all history.
2. it's easier to modify a version, experiment, and then submit the changes
back.
3. New developers are more used to git, have the tools and workflow already
at hand, and thus can participate more easily.

Although OWFS is stable, functional, and active, I'm currently the only one
committing code. I wondered if the development model was partly to blame,
and so decided to modernize the tools.

If I could only do something about autotools...

Paul




On Tue, Apr 29, 2014 at 8:47 PM, Gregg Levine gregg.drw...@gmail.comwrote:

 Hello!
 SF delivers both Git and CVS and probably SVN (still) and probably any
 others we can dream up. So when was CVS depreciated? I believe I
 managed to update the CVS one last night, and even tried to build the
 P3 release of 2.9 on my Slackware 13.37 system. (Currently the only
 one running.) It complained about libtool errors as related to age and
 so forth, it even insisted that I obtain a new release of such from an
 Ubuntu system.

 Paul is that where the original code is being built? (I'm on Slackware.)
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature fought the Time Wars, time and again.


 On Tue, Apr 29, 2014 at 8:35 PM, Paul Alfille paul.alfi...@gmail.com
 wrote:
  Release Notes owfs 2.9p4
  4/30/2014
 
  New features
  1. Switch to git for source management
  Still hosted on sourceforge.net
  git clone git://git.code.sf.net/p/owfs/code owfs-code
  cvs history brought over.
  2. Clean and test DS2409 (Microlan) hubs
  Addressing problem found by Ors Tiszay
  Works well with passive devices
  Problems with powered slaves, but probably not a software issue.
  3. Improved and tested owserver protocol for server-to-server
 communication
  Use md5 hash for unique token
  Fixed byte counting issue in write messages
  Null-terminated string no longer required in path string
  (problem pointed out by Stefano Miccoli)
  4. Added /system/configuration/version
  Reports owserver version
  Request from Stefano Miccoli
 
  Fixes
  1. Double initialization of mutex fixed
  Show stopper in FreeBSD
  Found by Johan Strom
 


 --
 Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
 Instantly run your Selenium tests across 300+ browser/OS combos.  Get
 unparalleled scalability from the best Selenium testing platform available.
 Simple to use. Nothing to install. Get started now for free.
 http://p.sf.net/sfu/SauceLabs
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] strange DS2762 persistence

2014-04-16 Thread Paul Alfille

Let me confirm that you physically disconnected the DS2762 rather than just
external power?
On Apr 16, 2014 4:05 AM, Ors Tiszay listaku...@gmail.com wrote:

 Hi,

 I have owfs running on a Gumstix Overo Earth, with a DS9490 bus master,
 which in turn is connected to a Hobby-Boards DS2409-based 8 channel hub
 (bought years ago when the DS2409 was still around, wish they still were).
 The bus then branches out to several directions, carrying a total of ~10
 sensors, mostly DS18.20 with the odd DS18S20/HIH3610 combo thrown in, so
 far using ch1 main and the aux of the hub.

 On ch2 aux I have a DS2762 based moisture meter board. Board was working
 fine for a few days in test, but when I disconnected it to be moved to its
 final location, I noticed that the script taking the readings every 30
 seconds kept returning values even after the board was disconnected. More
 precisely, the values read are either 0 or very close to 0 (-7.8125E-05 for
 current), but the surprising thing is that the whole file structure remains
 in place even days after the board is disconnected:

 This is what it looks like 3 days after disconnecting the moisture meter
 board:


 # ls -al /mnt/owfs/1F.F96B0800/aux   # - this is ch2 of the hub
 total 0
 drwxr-xr-x 1 root root 8 Apr 16 09:34 .
 drwxrwxrwx 1 root root 8 Apr 16 09:41 ..


 But reading the DS2762 as if it was still connected:

 # ls -al /mnt/owfs/1F.F96B0800/aux/30.4CF9B812
 total 0
 drwxrwxrwx 1 root root   8 Apr 16 09:49 .
 drwxr-xr-x 1 root root   8 Apr 16 09:34 ..
 --w--w--w- 1 root root   1 Apr 16 09:49 PIO
 drwxrwxrwx 1 root root   8 Apr 16 09:49 WS603
 -r--r--r-- 1 root root  16 Apr 16 09:34 address
 -rw-rw-rw- 1 root root 256 Apr 16 09:34 alias
 -rw-rw-rw- 1 root root  12 Apr 16 09:49 amphours
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 cc
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 ce
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 coc
 -r--r--r-- 1 root root   2 Apr 16 09:34 crc8
 -r--r--r-- 1 root root  12 Apr 16 09:34 current
 -rw-rw-rw- 1 root root  12 Apr 16 09:34 currentbias
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 dc
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 de
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 defaultpmod
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 defaultswen
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 doc
 -r--r--r-- 1 root root   2 Apr 16 09:34 family
 -r--r--r-- 1 root root  12 Apr 16 09:34 id
 -r--r--r-- 1 root root  16 Apr 16 09:34 locator
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 lock.0
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 lock.1
 -rw-rw-rw- 1 root root   3 Apr 16 09:49 lock.ALL
 -rw-rw-rw- 1 root root 256 Apr 16 09:34 memory
 -r--r--r-- 1 root root   1 Apr 16 09:49 mstr
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 ov
 drwxrwxrwx 1 root root   8 Apr 16 09:49 pages
 -r--r--r-- 1 root root   1 Apr 16 09:49 pmod
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 ps
 -r--r--r-- 1 root root  16 Apr 16 09:34 r_address
 -r--r--r-- 1 root root  12 Apr 16 09:34 r_id
 -r--r--r-- 1 root root  16 Apr 16 09:34 r_locator
 -r--r--r-- 1 root root   1 Apr 16 09:49 sensed
 -r--r--r-- 1 root root   1 Apr 16 09:49 swen
 -r--r--r-- 1 root root  12 Apr 16 09:49 temperature
 -r--r--r-- 1 root root  32 Apr 16 09:34 type
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeB
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeE
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeJ
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeK
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeN
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeR
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeS
 drwxrwxrwx 1 root root   8 Apr 16 09:49 typeT
 -rw-rw-rw- 1 root root   1 Apr 16 09:49 uv
 -rw-rw-rw- 1 root root  12 Apr 16 09:49 vbias
 -r--r--r-- 1 root root  12 Apr 16 09:49 vis
 -r--r--r-- 1 root root  12 Apr 16 09:49 volt
 -rw-rw-rw- 1 root root  12 Apr 16 09:49 volthours


 # cat /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/type
 DS2760

 # cat /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/volt
 0

 # cat /mnt/owfs/1F.F96B0800/aux/30.4CF9B812/current
 -7.8125E-05


 Trying the same thing (ie.reading them after they're disconnected) with
 any other sensor returns file not found, as expected.

 Just out of curiosity I took this a bit further and tried reading from 
 30.4CF9B812
 via a port it was never connected to:

 # ls -al /mnt/owfs/1F.B0680800/main/30.4CF9B812/
 total 0
 drwxrwxrwx 1 root root   8 Apr 16 09:59 .
 drwxr-xr-x 1 root root   8 Apr 16 09:34 ..
 --w--w--w- 1 root root   1 Apr 16 09:59 PIO
 drwxrwxrwx 1 root root   8 Apr 16 09:59 WS603
 -r--r--r-- 1 root root  16 Apr 16 09:34 address
 -rw-rw-rw- 1 root root 256 Apr 16 09:34 alias
 -rw-rw-rw- 1 root root  12 Apr 16 09:59 amphours
 -rw-rw-rw- 1 root root   1 Apr 16 09:59 cc
 -rw-rw-rw- 1 root root   1 Apr 16 09:59 ce
 -rw-rw-rw- 1 root root   1 Apr 16 09:59 coc
 -r--r--r-- 1 root root   2 Apr 16 09:34 crc8
 -r--r--r-- 1 root root  12 Apr 16 09:34 current
 -rw-rw-rw- 1 root root  12 Apr 16 09:34 currentbias
 -rw-rw-rw- 1 root root   1 Apr 16 09:59 dc

Re: [Owfs-developers] DS9490R 1-wire bus short circuit.

2014-04-14 Thread Paul Alfille

Page 5 of the datasheet (
http://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf) has a
schematic including the DS9503 diode that might be a problem.

On the other hand, it's probably not worth your time chasing this down,
rather than just buying another 9490R.

This doesn't seem to be too common an occurrence -- I have DS9490Rs that
have been in service for nearly a decade. You could always try an
alternative USB 1-wire adapter, though they won't be quite as fast.

Paul


On Mon, Apr 14, 2014 at 12:40 AM, vermus vermus.jab...@gmail.com wrote:

 Paul Alfille-2 wrote
  For reference I've included the initialization sequence for a functioning
  DS9490R:
 
  DEBUG MODE
  libow version:
  2.9p3
 
  .
 
  CONNECT: ow_usb_cycle.c:(68) Bus master found: 1:6
  DEFAULT: ow_usb_msg.c:(295) Opened USB DS9490 bus master at 1:6.
 CALL: ow_parsename.c:(99) path=[]
 CALL: ow_parsename.c:(99) path=[/uncached/bus.0]
DEBUG: ow_dir.c:(65) path=/uncached/bus.0
 CALL: ow_dir.c:(100) path=/uncached/bus.0
 CALL: ow_parsename.c:(99) path=[/uncached/bus.0/interface]
DEBUG: ow_usb_cycle.c:(125) Callback on /uncached/bus.0/interface
DEBUG: ow_parsename.c:(62) /uncached/bus.0/interface
DEBUG: ow_search.c:(32) Start of directory path=/uncached/bus.0
  device=00
  00 00 00 00 00 00 00
DEBUG: ow_ds9490.c:(607) Index 0
DEBUG: ow_select.c:(66) Selecting a path (and device)
  path=/uncached/bus.0 SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00
  00
  00 00
DEBUG: ow_select.c:(79) Continuing root branch
DEBUG: ow_ds9490.c:(495) DS9490 RESET. changed 15, flex: 1
 DATA: ow_ds9490.c:(942) set flexible speed
DEBUG: ow_ds9490.c:(546) DS9490_Reset: OK
DEBUG: ow_ds9490.c:(683) Got 8 bytes from USB search
DEBUG: ow_ds9490.c:(711) gulp. Adding element 0:81 09 03 30 00 00 00 3A
DEBUG: ow_ds9490.c:(625) SN found: 81 09 03 30 00 00 00 3A
DEBUG: ow_search.c:(74) Device found: 81 09 03 30 00 00 00 3A
DEBUG: ow_cache.c:(547) Adding device location 81 09 03 30 00 00 00 3A
  bus=0
DEBUG: ow_cache.c:(636) Add to cache sn 81 09 03 30 00 00 00 3A
  pointer=0x7fbec55f928c index=0 size=4
DEBUG: ow_cache.c:(547) Adding device location 81 09 03 30 00 00 00 3A
  bus=0
DEBUG: ow_cache.c:(636) Add to cache sn 81 09 03 30 00 00 00 3A
  pointer=0x7fbec55f928c index=0 size=4
 CALL: ow_parsename.c:(99) path=[/uncached/bus.0/81.09033000]
DEBUG: ow_usb_cycle.c:(125) Callback on /uncached/bus.0/81.09033000
DEBUG: ow_parsename.c:(62) /uncached/bus.0/81.09033000
DEBUG: ow_ds9490.c:(607) Index 1
DEBUG: ow_cache.c:(479) Adding directory for 00 00 00 00 00 00 00 00
  elements=1
DEBUG: ow_cache.c:(636) Add to cache sn 00 00 00 00 00 00 00 00
  pointer=0x7fbec55f9298 index=0 size=8
DEBUG: ow_dir.c:(195) ret=0
DEBUG: ow_usb_cycle.c:(155) Finished FS_dir
DEBUG: ow_parsename.c:(62) /uncached/bus.0
  DEFAULT: ow_usb_cycle.c:(191) Set DS9490 1:6 unique id to 81 09 03 30 00
  00
  00 3A
 
 
  --
 
  The short sequence comes from the DS9490R itself -- it tests the line
  and
  reports if the 1-wire line is shorted out. The fact that it is reporting
  says that the USB to DS2490 (the actual USB chip) connection is working.
 
  I presume you don't have anything connected to the bus master at this
  stage
  of testing? I.e. the socket is empty?

 Thanks again.  Yes, usb is OK:

 root@hostname:/usr/src# lsusb
  Bus 005 Device 003: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob,
 1-Wire adapter

 Yes, the rj11(12) socket is absolutely empty.

 I guess, i need to buy another one device. :(



 --
 View this message in context:
 http://owfs-developers.1086194.n5.nabble.com/DS9490R-1-wire-bus-short-circuit-tp10564p10568.html
 Sent from the OWFS Developers mailing list archive at Nabble.com.


 --
 Learn Graph Databases - Download FREE O'Reilly Book
 Graph Databases is the definitive new guide to graph databases and their
 applications. Written by three acclaimed leaders in the field,
 this first edition is now available. Download your free book today!
 http://p.sf.net/sfu/NeoTech
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] DS9490R 1-wire bus short circuit.

2014-04-14 Thread Paul Alfille

Off the top of my head:

Link-USB (ibuttonlink.com)

USB9097
http://www.ebay.com/itm/PCsensor-1-Wire-adapter-thermometer-replace-DS9097-DS9490-NEW-/281307951738?pt=US_Weather_Metershash=item417f42b27a

The latter uses the serial protocol and so is slightly slower for large
directories. The LINK is probably pretty close, buty I haven't checked. It
hardly matters, 1-wire isn't that fast.

On Mon, Apr 14, 2014 at 7:32 AM, vermus vermus.jab...@gmail.com wrote:

Paul Alfille-2 wrote
Page 5 of the datasheet (
http://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf) has a
schematic including the DS9503 diode that might be a problem.

On the other hand, it's probably not worth your time chasing this down,
rather than just buying another 9490R.

This doesn't seem to be too common an occurrence -- I have DS9490Rs that
have been in service for nearly a decade. You could always try an
alternative USB 1-wire adapter, though they won't be quite as fast.

Yes, as i said before, i tested this DS9503.

Hmm, what alternative adapter? Can you give link on ebay or aliexpress?

And what does that mean won't be quite as fast? 1-wire bus speed?

Thanks!

ps. Can you give a bus voltage from DS9490R ? In my case it ~ 1 Volt (3 and
4 pin), but AFAIK sensors on parasite power needs 3-5V...

--
View this message in context:
http://owfs-developers.1086194.n5.nabble.com/DS9490R-1-wire-bus-short-circuit-tp10564p10570.html
Sent from the OWFS Developers mailing list archive at Nabble.com.

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] DS9490R 1-wire bus short circuit.

2014-04-13 Thread Paul Alfille

For reference I've included the initialization sequence for a functioning
DS9490R:

DEBUG MODE
libow version:
2.9p3
  DEBUG: ow_daemon.c:(166) main thread id = 140457333811008
  DEBUG: ow_avahi_link.c:(71) Avahi support: libavahi-client loaded
successfully
  DEBUG: ow_avahi_link.c:(73) Avahi library function found:
avahi_client_errno
  DEBUG: ow_avahi_link.c:(74) Avahi library function found:
avahi_client_free
  DEBUG: ow_avahi_link.c:(75) Avahi library function found: avahi_client_new
  DEBUG: ow_avahi_link.c:(76) Avahi library function found:
avahi_client_get_domain_name
  DEBUG: ow_avahi_link.c:(77) Avahi library function found:
avahi_entry_group_add_service
  DEBUG: ow_avahi_link.c:(78) Avahi library function found:
avahi_entry_group_commit
  DEBUG: ow_avahi_link.c:(79) Avahi library function found:
avahi_entry_group_is_empty
  DEBUG: ow_avahi_link.c:(80) Avahi library function found:
avahi_entry_group_new
  DEBUG: ow_avahi_link.c:(81) Avahi library function found:
avahi_entry_group_reset
  DEBUG: ow_avahi_link.c:(83) Avahi library function found:
avahi_service_resolver_free
  DEBUG: ow_avahi_link.c:(84) Avahi library function found:
avahi_service_resolver_new
  DEBUG: ow_avahi_link.c:(85) Avahi library function found:
avahi_service_browser_free
  DEBUG: ow_avahi_link.c:(86) Avahi library function found:
avahi_service_browser_new
  DEBUG: ow_avahi_link.c:(98) Avahi support: libavahi-common loaded
successfully.
  DEBUG: ow_avahi_link.c:(100) Avahi library function found:
avahi_simple_poll_free
  DEBUG: ow_avahi_link.c:(101) Avahi library function found:
avahi_simple_poll_get
  DEBUG: ow_avahi_link.c:(102) Avahi library function found:
avahi_simple_poll_loop
  DEBUG: ow_avahi_link.c:(103) Avahi library function found:
avahi_simple_poll_new
  DEBUG: ow_avahi_link.c:(104) Avahi library function found:
avahi_simple_poll_quit
  DEBUG: ow_avahi_link.c:(105) Avahi library function found: avahi_strerror
   CALL: ow_parsename.c:(99) path=[]
  DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
CONNECT: ow_usb_cycle.c:(68) Bus master found: 1:6
DEFAULT: ow_usb_msg.c:(295) Opened USB DS9490 bus master at 1:6.
   CALL: ow_parsename.c:(99) path=[]
   CALL: ow_parsename.c:(99) path=[/uncached/bus.0]
  DEBUG: ow_dir.c:(65) path=/uncached/bus.0
   CALL: ow_dir.c:(100) path=/uncached/bus.0
   CALL: ow_parsename.c:(99) path=[/uncached/bus.0/interface]
  DEBUG: ow_usb_cycle.c:(125) Callback on /uncached/bus.0/interface
  DEBUG: ow_parsename.c:(62) /uncached/bus.0/interface
  DEBUG: ow_search.c:(32) Start of directory path=/uncached/bus.0 device=00
00 00 00 00 00 00 00
  DEBUG: ow_ds9490.c:(607) Index 0
  DEBUG: ow_select.c:(66) Selecting a path (and device)
path=/uncached/bus.0 SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00
00 00
  DEBUG: ow_select.c:(79) Continuing root branch
  DEBUG: ow_ds9490.c:(495) DS9490 RESET. changed 15, flex: 1
   DATA: ow_ds9490.c:(942) set flexible speed
  DEBUG: ow_ds9490.c:(546) DS9490_Reset: OK
  DEBUG: ow_ds9490.c:(683) Got 8 bytes from USB search
  DEBUG: ow_ds9490.c:(711) gulp. Adding element 0:81 09 03 30 00 00 00 3A
  DEBUG: ow_ds9490.c:(625) SN found: 81 09 03 30 00 00 00 3A
  DEBUG: ow_search.c:(74) Device found: 81 09 03 30 00 00 00 3A
  DEBUG: ow_cache.c:(547) Adding device location 81 09 03 30 00 00 00 3A
bus=0
  DEBUG: ow_cache.c:(636) Add to cache sn 81 09 03 30 00 00 00 3A
pointer=0x7fbec55f928c index=0 size=4
  DEBUG: ow_cache.c:(547) Adding device location 81 09 03 30 00 00 00 3A
bus=0
  DEBUG: ow_cache.c:(636) Add to cache sn 81 09 03 30 00 00 00 3A
pointer=0x7fbec55f928c index=0 size=4
   CALL: ow_parsename.c:(99) path=[/uncached/bus.0/81.09033000]
  DEBUG: ow_usb_cycle.c:(125) Callback on /uncached/bus.0/81.09033000
  DEBUG: ow_parsename.c:(62) /uncached/bus.0/81.09033000
  DEBUG: ow_ds9490.c:(607) Index 1
  DEBUG: ow_cache.c:(479) Adding directory for 00 00 00 00 00 00 00 00
elements=1
  DEBUG: ow_cache.c:(636) Add to cache sn 00 00 00 00 00 00 00 00
pointer=0x7fbec55f9298 index=0 size=8
  DEBUG: ow_dir.c:(195) ret=0
  DEBUG: ow_usb_cycle.c:(155) Finished FS_dir
  DEBUG: ow_parsename.c:(62) /uncached/bus.0
DEFAULT: ow_usb_cycle.c:(191) Set DS9490 1:6 unique id to 81 09 03 30 00 00
00 3A


--

The short sequence comes from the DS9490R itself -- it tests the line and
reports if the 1-wire line is shorted out. The fact that it is reporting
says that the USB to DS2490 (the actual USB chip) connection is working.

I presume you don't have anything connected to the bus master at this stage
of testing? I.e. the socket is empty?

Paul Alfille


On Sun, Apr 13, 2014 at 2:21 PM, vermus vermus.jab...@gmail.com wrote:

 A possible bug is a shorted DS9503 protective diode in the device. This
 happens after static overvoltage on the bus line, e.g. wrongly connected
 +12V to 1W. Static discharge is unlikely, the diode is designed to
 survive a short peak.

 Open the DS9450 (TX5 screw under the label, two clips at the side

Re: [Owfs-developers] Getting apparently random numbers from DS18S20

2014-04-11 Thread Paul Alfille

This is an interesting error -- I haven't seen it before.

For the record, the DS2405 isn't a bus master -- it's a one-pin quirky
switch.

I gather you are running the file system (owfs) and logging in remotely
with ssh.

There are a number of possibilities -- floating point endian errors might
be widely distributed like this. The catch is that temphigh and templow are
essentially constants unless you actively change them, so should give the
same value every time they are read. Even more, all these values are cached
briefly (15seconds for temperature by default) so a rapid re-read should
give the same value.

Perhaps other people have thoughts on this. I'm baffled.

If I needed to duplicate your setup, which bus-master and which owfs
version are you using?

Paul Alfille


On Fri, Apr 11, 2014 at 10:18 AM, Chris Green c...@isbd.net wrote:

 I have owfs running on a Beaglebone Black, apparently working OK.  The
 1-wire bus is connected via a DS2405 based USB device.  It all
 *appears* to be working OK and I get the expected directories as
 follows:-

 /mnt/1-wire/05.4AEC29CDBAAB for the DS2405
 /mnt/1-wire/10.67C6697351FF for the DS18S20

 The 'type' file in each directory is correct but the temperature,
 temphigh and templow files in the DS18S20 directory just jump all ove
 the place:-

 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  99.7799
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  5.40576
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
   87.054
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  7.23288
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
 0.416161


 The system is remote from me at the moment but I will be back there in
 the next few days.  What should I check?

 --
 Chris Green


 --
 Put Bad Developers to Shame
 Dominate Development with Jenkins Continuous Integration
 Continuously Automate Build, Test  Deployment
 Start a new project now. Try Jenkins in the cloud.
 http://p.sf.net/sfu/13600_Cloudbees
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test  Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Getting apparently random numbers from DS18S20

2014-04-11 Thread Paul Alfille

Ahha! Found the problem! (Rather embarrassing for me).

The default package for owfs ships with a fake configuration file.
Literally it uses the fake bus-master -- a bus master that returns random
results to test the software rather than hardware.

Clearly the change shouldn't be difficult -- the file is in /etc/owfs.conf
and needs to be modified for your bus-master.

Here is the default fake owfs.conf:
--
# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

 SOURCES 
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
#server: usb = all
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
# OWFS ##
#
#mountpoint = /mnt/1wire
#allow_other
#
### OWHTTPD #

http: port = 2121

### OWFTPD ##

ftp: port = 2120

### OWSERVER 

server: port = localhost:4304




On Fri, Apr 11, 2014 at 11:47 AM, Paul Alfille paul.alfi...@gmail.comwrote:

 This is an interesting error -- I haven't seen it before.

 For the record, the DS2405 isn't a bus master -- it's a one-pin quirky
 switch.

 I gather you are running the file system (owfs) and logging in remotely
 with ssh.

 There are a number of possibilities -- floating point endian errors might
 be widely distributed like this. The catch is that temphigh and templow are
 essentially constants unless you actively change them, so should give the
 same value every time they are read. Even more, all these values are cached
 briefly (15seconds for temperature by default) so a rapid re-read should
 give the same value.

 Perhaps other people have thoughts on this. I'm baffled.

 If I needed to duplicate your setup, which bus-master and which owfs
 version are you using?

 Paul Alfille


 On Fri, Apr 11, 2014 at 10:18 AM, Chris Green c...@isbd.net wrote:

 I have owfs running on a Beaglebone Black, apparently working OK.  The
 1-wire bus is connected via a DS2405 based USB device.  It all
 *appears* to be working OK and I get the expected directories as
 follows:-

 /mnt/1-wire/05.4AEC29CDBAAB for the DS2405
 /mnt/1-wire/10.67C6697351FF for the DS18S20

 The 'type' file in each directory is correct but the temperature,
 temphigh and templow files in the DS18S20 directory just jump all ove
 the place:-

 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  99.7799
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  5.40576
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
   87.054
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
  7.23288
 root@beaglebone:/mnt/1-wire/10.67C6697351FF# more temperature
 0.416161


 The system is remote from me at the moment but I will be back there in
 the next few days.  What should I check?

 --
 Chris Green


 --
 Put Bad Developers to Shame
 Dominate Development with Jenkins Continuous Integration
 Continuously Automate Build, Test  Deployment
 Start a new project now. Try Jenkins in the cloud.
 http://p.sf.net/sfu/13600_Cloudbees
 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers



--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test  Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] ownet / owserver null terminated strings in payload.

2014-04-09 Thread Paul Alfille

Thanks Stefano,

You are right, the code checks for the null-terminated string.

In theory this shouldn't be needed, the length of the data and the path are
also sent. I just have to make sure that all the ownet clients are rigorous
about filling out those fields correctly.

Paul


On Sat, Apr 5, 2014 at 6:43 PM, Stefano Miccoli mo...@icloud.com wrote:

 Hi all,

 it's a long time that I'm using owfs/owserver to read a network of 1-wire
 sensors in a server room, with great satisfaction for it's stability and
 ease of use.

 My main scripting language is python, and somehow I do not like the
 official python packages, so I decided to write my own implementation of
 the ownet protocol. If you are interested you can find my implementation on
 pypi https://pypi.python.org/pypi/pyownet or github
 https://github.com/miccoli/pyownet/ (The code should be pretty stable,
 I'm using it 24/7 in a production environment, but docs are scarce,
 therefore it is still marked as alpha development status.)

 While implementing the package, I found some problems and difficulties
 that I would like to share with you.


 1) Null terminated strings.

 The payload in most messages has to be null-terminated. While this can be
 regarded as natural for the C programmer, it is somehow unusual from the
 python point of view, where '/' and '/\x00' are different strings.

 Maybe this should be made more clear in
 http://owfs.org/index.php?page=tcp-messages where I read

 Payload: data string. Either just a filename path (for read or directory,
 or a null terminated path with data to be written afterwards


 It should be

 Payload: *null terminated* data string...

 just to make clear that the null terminator has to be always present, even
 when no data follows the path.


 2) Error codes / strings.

 Error messages associated with the error codes can be retrieved with
 owserver --help=error or read from '/settings/return_codes'. I use this
 error messages in the exceptions raised by my code, but there are some
 inconsistencies.

 a) when you try to access a non existent path, you get error
 1 'Startup - command line parameters invalid'
 while it should be
 2 'legacy - No such entity'

 b) all owserver/ownet error messages start with 'legacy - '... why?
 Shouldn't this be 'owserver - ...' or 'ownet - ...


 3) Server version

 I was not able to find any way to determine the owserver version from a
 client: couldn't be useful to add a '/settings/version' node to owfs?



 Bye and compliments to all for the excellent work

 Stefano




 --

 ___
 Owfs-developers mailing list
 Owfs-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/owfs-developers


--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test  Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1740 matches

Mail list logo