Why is the owpython source not downloadable? I wish I'd known about it and
would be happy to contribute. First I need to download it...
On Wed, Dec 4, 2013 at 2:12 PM, Top-Dog <sean.ocon...@taitradio.com> wrote:
> Hi,
> I'm pretty new to the owfs and have been trying to get it working properly
> but have run into some issues. Basically my device (DS2431) and USB adapter
> (DS9490r) will disconnect and disappear from the 1-wire file system mount
> point. I'm using the python api (http://owfs.sourceforge.net/owpython.html
> )
>
> At start up I run: #sudo /opt/owfs/bin/owfs --allow_other -u
> /root/1-wire-EEPROM
> to mount the file system. This works and shows the USB an EEPROM device
> attached.
>
> I then run the python api and the following code, and get the output below:
> >>> import ow
> >>> ow.init('u')
>
> DEFAULT: ow_ds9490.c:(250) Unclear what <> means in USB specification, will
> use first adapter.
> DEFAULT: ow_usb_msg.c:(295) Opened USB DS9490 bus master at 1:2.
> DEFAULT: ow_usb_cycle.c:(191) Set DS9490 1:2 unique id to 81 82 DE 2A 00 00
> 00 B9
>
> Now, I couldn't find a function to read/write to the EEPROM in the python
> api so I created my own, but at any point I try to access the EEPROM page
> files inside of python they become inaccessible and can no longer be seen
> at
> the mount point.
>
> fileObject = open(pagePath, "rb") # Read only to a file in binary
>
> with fileObject as f:
> f.seek(offset, 0)
> readVal = f.read(chunkSize)
>
> >From the above segment of code the program breaks at the line: readVal =
> f.read(chunkSize). The file system is still intact up to this line when it
> suddenly dissapears. I have also observed in other cases that the file
> system disappears immediately after ow.init('u') is called. Upon exiting to
> the terminal I've tried
> #fusermount -u /root/1-wire-EEPROM/
> to reset the system, but either get the error; device or resource busy; or
> fuse: mountpoint is not empty,
> fuse: if you are sure this is safe, use the 'nonempty' mount option. I
> don't
> know how to get around this. Any help with finding out why the attached
> devices keep disappearing would be appreciated.
>
> I'm using Debian on a BeagleBone Black for development. I also found this
> thread, but can't seem to make it work:
>
> http://owfs-developers.1086194.n5.nabble.com/Diagnosing-disappearing-devices-td10001.html
>
>
>
>
> --
> View this message in context:
> http://owfs-developers.1086194.n5.nabble.com/Diagnosing-disappearing-devices-adapters-tp10045.html
> Sent from the OWFS Developers mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
