Re: [Owfs-developers] Plug Computer Recommendation?
Our lab (Washington State University Smarthome lab) has purchased all models of plug computers made by GlobalScale (eg, the Sheeva, Guru, and Dream Plug). We use them to run OWFS and other middleware at remote sites and send that data back to our central DB. We've purchased 5 Sheeva's, 1 Guru, and 21 Guru's. The general hardware spec is very good and would be a good match for your application. Unfortunately, GlobalScale's quality control is nearly non-existant. Our order of 21 Guru's (and my 1 personal purchase) experienced 6 RMA-required plugs. Some arrived with an internal rattle; one with defective RAM, two had their ethernet PHY's fail shortly after going into production. GlobalScale has replaced all the failed units so far, but it does take a lot longer than they say, and it did require several reminder phone calls. Also note that the WiFi/Bluetooth chip used in the guru is not exactly what the part number claims, and as a result, drivers are a pain and in our experiences for our applications, the wifi chip+drivers was too unstable for use. The guru was a total engineering failure, do not buy. The sheeva was very solid. We don't have many in production anymore, but aside from one PSU failure (our first one), they've all been rock solid. They also include the JTAG/serial interface for initial configuration (its ~$40 for the guru and dreamplug). E-mail me if you want more specific details. Oh, and we run Gentoo on all plug varieties. --Jim Lab Manager On Wed, Nov 2, 2011 at 8:47 PM, Peter Hollenbeck pwhb...@gmail.com wrote: Let me know if this is too far off track. At a remote, unattended site I use gphoto2 to capture images from two cameras and soon will use owfs to capture weather data. Images and weather data are posted to my web site (http://www.hbeck.net). Am using openSUSE 11.1 on a Jetway MB with Via Nano CPU. But no data needs to stay on the PC as everything is sent to the web site. So it seems a plug or similar computer with no HD would do the job. On this list I have seen references to Sheeva, BeagleBoard, and maybe others. I would appreciate any comments. Thanks, Peter -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 2.8p6 Error
We have pulled u6 from our production systems because of this very
error. We see it too, mostly when we make a simultaneous call. It
also doesn't happen reliably.
In past posts, I posted the specific version that this came about.
This also seems to only occur with USB adapters, the DS9490R. That's
all we use, so I don't have anything else to compare to.
For us, everything worked fine until a specific update, then we got
that issue. We can kill the u6 and start the u2 (I think), and all
works well, so its not hardware or OS configuration. It also doesn't
happen right when we start it; we can often get some data from it
before it dies. If memory serves, calling simultaneous/temperature
will kill it nearly every time. But it will also show up other times
as well.
--Jim
On Sun, Feb 27, 2011 at 5:59 AM, Norman Elliott normanelli...@gmail.com wrote:
I also have 2.8p6 in both of my laptops and they are both fine.
I found that the udev rules syntax changes from time to time and had to
edit the rule to this :
cat /etc/udev/rules.d/90-ds2490.rules
SYSFS{idVendor}==04fa, SYSFS{idProduct}==2490, GROUP=ow, MODE=0664
#SUBSYSTEMS==usb, ATTRS{idVendor}==04fa, ATTRS{idProduct}==2490,
PROGRAM=/bin/sh -c 'K=%k; K=$${K#usbdev}; printf bus/usb/%%03i/%%03i
$${K.*} $${K#*.}', NAME=%c, GROUP=ow, MODE=0666
and make sure I was in the ow group as well as ensuring that
SYSFS{idVendor}==04fa and SYSFS{idProduct}==2490
matched my device ids
Hope that helps.
On 27 February 2011 12:39, Mick Sulley m...@sulley.info wrote:
Hi Colin,
I have 2.8p6 running on my laptop and it seems to work OK. Is there any
info I can provide to help?
Cheers
Mick
On Sun, 2011-02-27 at 11:56 +, Colin Tinker wrote:
Hi
This is the 3 rd time asking what causes this error?
No valid 1-wire buses found any
idea what causes it?
It happens in the last 2 versions meaning I cannot upgrade from p4.
Anyone?
Colin
--
Free Software Download: Index, Search Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data
generated by your applications, servers and devices whether physical,
virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
--
Free Software Download: Index, Search Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data
generated by your applications, servers and devices whether physical,
virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
--
Free Software Download: Index, Search Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New Release 2.8p6
We've tested this version in our lab, and it still has the same issue we reported with p5; specifically, when using a DS-9490 and a bus with a few temperature sensors, writing 1 to simultaneous/temperature or simultaneous/voltage returns Error: No such device. This has been confirmed as working fine with p4, but broke with p5 and p6. --Jim On Tue, Jan 25, 2011 at 7:38 PM, Paul Alfille paul.alfi...@gmail.com wrote: RELEASE NOTES OWFS 2.8p6 1. DS2436 Automatic lock handling for memory access 2. DS2436 Counter support 3. DS2450 8bit support 4. OW-SERVER-ENET telnet support complete. 5. LINK over serial, telnet (ser2net) and LinkHub-E 6. DS9097U (DS2480B based) support in serial and telnet (ser2net) 7. DS9097 (passive) supprt in serial and ser2net 8. HA5 fixes -- works with checksum mode. 9. Simultaneous fixes from Jim Kuszmir Typical use of ser2net: sudo ser2net -C :telnet:0:/dev/ttyUSB0:9600 1STOPBIT 8DATABITS remctl Then use or host: instead of /dev/ttyS0 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Error reading 1-wire
We get the same problem, if we downgrade to p4 (I think...I don't have that system in front of me), it works. Go before p4, and it gets worse for a couple versions. I think p2 is stable (but the python code has a typo in it on spacing, this goes all the way back to the p0 release). So yea, we've had to pull all versions of p5 from production because of this error. At the moment, p4 is the the most stable version we've found. --Jim On Fri, Jan 21, 2011 at 1:10 AM, Marcus Priesch mar...@priesch.priv.at wrote: Hi Mick, + you could take a look at the dmesg output for any errors on your serial port + try reloading the serial modules (ist it usb-serial?) + are you using owserver - and connecting remotely ? - then restarting owserver could also help + other things would involve tyring owhttpd and see if it has the same behaviour - and then use --debug on it and ... maybe post the relevant parts here ... regards, m. Am Freitag, den 21.01.2011, 00:04 + schrieb Mick Sulley: Hi, I have python code reading my 1-wire network using pyowfs and a DS9097 connected via a serial port. Sometimes when I start up it cannot see anything and I get the error ow_reconnect.c:TestConnection(52) Failed to reconnect DS9097 bus master! This is then a consistent problem, re-running the code just generates the same error. However if I reboot, changing nothing at all, it works fine again! Any ideas what can cause this and how to fix it? Running Ubuntu 10.10 64 bit and owfs version 2.8p4 Thanks Mick -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owfs in owfs-2.8p5
We are seeing variants of this problem; it was introduced in p5; p4 does work more stably in this regard. --Jim On Tue, Jan 11, 2011 at 3:11 PM, Colin Tinker g1...@me.com wrote: Hi In the latest version owfs refuses to start with the error no 1-wire interfaces found when I am connecting it to the owfs server which is running fine. It has worked ok in the last 2 release I have used with the same command line syntax. Colin -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release OWFS 2.8p5
This version seems to have introduced a new bug: one cannot write into uncached/simultaneous/temperature (It returns a bash error, although it is there). All other operations we've tested work fine (we can individually read temperatures, we can set the alarming values, etc.). The same command works by stopping p5 and starting our modified p4. --Jim On Thu, Jan 6, 2011 at 7:53 PM, Paul Alfille paul.alfi...@gmail.com wrote: Release note for OWFS 2.8p5 1. Fixes from Jim Kaszmir for DS18x20 temperature alarms and simultaneous reads 2. Fixes based on test environment from Achim Hennies for LinkHubE -- Proper telnet parsing, baud rate, and even Xport control port reset if needed 3, Improvements in timeouts, dropped connections, and reconnections for all serial and network interfaces. 4. Start of implementation based on Roberto Spadim's recommendation that we support telnet serial connection RFC2217 Use ser2net as the device: e.g. sudo ser2net -C :telnet:0:/dev/ttyUSB0:9600 1STOPBIT 8DATABITS remctl 5. Add some bit-level commends for future BAE function and some Dallas security chip support 6. Fix remote BAE over owserver problem. Link: https://sourceforge.net/projects/owfs/ -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release OWFS 2.8p5
To follow up, the errors we're seeing may be tied to our specific bus master (the Dallas blue USB master). When we turn debugging way up, we get a no bus master found. We also found if we write f to the temperature scale, we get the same message and our terminal that wrote that hangs. --Jim On Fri, Jan 7, 2011 at 9:37 AM, Jim Kusznir jkusz...@gmail.com wrote: This version seems to have introduced a new bug: one cannot write into uncached/simultaneous/temperature (It returns a bash error, although it is there). All other operations we've tested work fine (we can individually read temperatures, we can set the alarming values, etc.). The same command works by stopping p5 and starting our modified p4. --Jim On Thu, Jan 6, 2011 at 7:53 PM, Paul Alfille paul.alfi...@gmail.com wrote: Release note for OWFS 2.8p5 1. Fixes from Jim Kaszmir for DS18x20 temperature alarms and simultaneous reads 2. Fixes based on test environment from Achim Hennies for LinkHubE -- Proper telnet parsing, baud rate, and even Xport control port reset if needed 3, Improvements in timeouts, dropped connections, and reconnections for all serial and network interfaces. 4. Start of implementation based on Roberto Spadim's recommendation that we support telnet serial connection RFC2217 Use ser2net as the device: e.g. sudo ser2net -C :telnet:0:/dev/ttyUSB0:9600 1STOPBIT 8DATABITS remctl 5. Add some bit-level commends for future BAE function and some Dallas security chip support 6. Fix remote BAE over owserver problem. Link: https://sourceforge.net/projects/owfs/ -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Alarming problems in the DS18B20 (and probably other temps)
We did some hacking on the source code. With a very basic hack to change the delay on a simultanous temperature command, alarming on bus-powered 18b20's now work. I think this hack is not production-ready, but it does appear to be a fairly easy fix. --Jim On Tue, Jan 4, 2011 at 3:34 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I've been reporting for a while that alarming was not working with DS18B20 temperature chips. Today we have finally gotten the traces and compared to the Dallas data sheets to figure out exactly why they're not working. Thanks to the relatively new bus traffic debug feature, we were able to get this. It appears that all the alarming setup stuff works. We did find a bug in the reading of the alarm values: owfs only reads from the scratchpad; it does NOT first copy from the alarm EEPROM to the scratchpad. Therefore, unless you just set the alarm value, the value OWFS reads out is actually not correct. After setting Thigh and Tlow, we entered into a loop of echo 1 simultaneous/temperature followed by a ls of the alarm directory. In our case, the temperature chip always shows up in the alarm directory, even when it should not. However, if we cat fasttemp for a chip, it will disappear from the alarm directory. Today's research revealed that the issue is that OWFS is NOT handling the bus powered situation correctly. It looks like the alarming function would work perfectly if all of our DS18B20s were externally powered. However, we run all of ours parasitic. I suspect that some logic needs to be added to OWFS to know if it has at least one bus-powered chip (there's a simple OW command that can be run to do this, IIRC), and then it would need to execute the strong pullup after a convert command. Thanks! (BTW: our test version of OWFS 2.8p3 with owtraffic, used with the dallas USB bus master blows up randomly with cannot reconnect errors; 2.8p2 worked stably. We did not check 2.8p4.) --Jim CASAS Lab Manager @ Washington State University -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Alarming problems in the DS18B20 (and probably other temps)
Hi all: I've been reporting for a while that alarming was not working with DS18B20 temperature chips. Today we have finally gotten the traces and compared to the Dallas data sheets to figure out exactly why they're not working. Thanks to the relatively new bus traffic debug feature, we were able to get this. It appears that all the alarming setup stuff works. We did find a bug in the reading of the alarm values: owfs only reads from the scratchpad; it does NOT first copy from the alarm EEPROM to the scratchpad. Therefore, unless you just set the alarm value, the value OWFS reads out is actually not correct. After setting Thigh and Tlow, we entered into a loop of echo 1 simultaneous/temperature followed by a ls of the alarm directory. In our case, the temperature chip always shows up in the alarm directory, even when it should not. However, if we cat fasttemp for a chip, it will disappear from the alarm directory. Today's research revealed that the issue is that OWFS is NOT handling the bus powered situation correctly. It looks like the alarming function would work perfectly if all of our DS18B20s were externally powered. However, we run all of ours parasitic. I suspect that some logic needs to be added to OWFS to know if it has at least one bus-powered chip (there's a simple OW command that can be run to do this, IIRC), and then it would need to execute the strong pullup after a convert command. Thanks! (BTW: our test version of OWFS 2.8p3 with owtraffic, used with the dallas USB bus master blows up randomly with cannot reconnect errors; 2.8p2 worked stably. We did not check 2.8p4.) --Jim CASAS Lab Manager @ Washington State University -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Bug in memory read
Hi all: I reported a problem a while ago with strange memory reads coming out on the DS2406. We have conducted more tests in my lab, and have more information. First, the problem: When one reads memory on a DS2406 since the 2.8pX series (all released patch levels so far), the first 1-2 characters are munged. By munged, I mean that the character is something else than it is supposed to be; there is still something in that location though. This happens through both the fuse interface and the python module. Strangely enough, if one reads pages.ALL, then the read is correct. As I said, this occurred with the first release of 2.8 and is still present with 2.8p2. --Jim -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] regression? python bad indent
Hi all: We just did a clean install of the latest owfs from the sf website: 2.8p2, and it had the python indent problem. I seem to recall that was committed prior to the most recent announcement on patch level release...perhaps its not out yet, but I thought I'd point out that problem is still occurring. --Jim -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] OWFS 2406 memory read issue
Hi all:
I'm not sure if this is specifically a python problem or a larger
underlying memory problem. Since upgrading to Python2.6, we have not
yet gotten owfs working again. This most recent test was from a
2.7p2x build and python 2.5. The second snippit is from 2.8p2 and
python 2.6.
We burn a brief ID into our 2406's for our software to identify what
type of device it is. We use XML as much of our data elsewhere is
xml:
Python 2.6.4 (r264:75706, Jun 9 2010, 17:25:01)
[GCC 4.1.2 (Gentoo 4.1.2 p1.3)] on linux2
Type help, copyright, credits or license for more information.
import ow
ow.init('uall')
print ow._OW.get(/uncached)
20.C7860D00/,28.429D3101/,12.50325F00/,81.95642900/,bus.0/,setti
ngs/,system/,statistics/,structure/,simultaneous/,alarm/
print ow._OW.get(/uncached/12.50325F00)
PIO.BYTE,PIO.ALL,PIO.A,PIO.B,T8A/,TAI8570/,address,alias,channels,crc8,family,fl
ipflop.BYTE,flipflop.ALL,flipflop.A,flipflop.B,id,latch.BYTE,latch.ALL,latch.A,l
atch.B,locator,memory,pages/,power,present,r_address,r_id,r_locator,sensed.BYTE,
sensed.ALL,sensed.A,sensed.B,set_alarm,type
print ow._OW.get(/uncached/12.50325F00/memory)
FAMILY=ITEMVERSION=01���
Python 2.6.5 (release26-maint, Aug 27 2010, 02:36:52)
[GCC 4.4.3] on linux2
Type help, copyright, credits or license for more information.
import ow
ow.init('uall')
print ow._OW.get(/uncached)
28.90923101/,28.C88E3101/,28.72913101/,28.698C3101/,28.697F3101/,12.88804600/,12.C8AC4B00/,12.687D4600/,12.687F4600/,12.387D4600/,12.447E4600/,12.647E4600/,12.543D5F00/,12.B4824600/,12.F4824600/,12.CC7A4600/,12.2C804600/,12.6C7B4600/,12.6C7F4600/,12.527F4600/,12.327C4600/,12.6A7F4600/,12.46804600/,12.C6794600/,12.967F4600/,12.D67A4600/,12.F6B24B00/,12.0E814600/,12.8E7B4600/,12.9E814600/,12.9E7D4600/,12.017C4600/,12.417C4600/,12.21794600/,12.317B4600/,12.C9804600/,12.197E4600/,12.457C4600/,12.C57B4600/,12.257D4600/,12.2D7C4600/,12.D37D4600/,12.6B7B4600/,12.277A4600/,12.A77F4600/,12.577D4600/,12.8F7F4600/,12.2F7C4600/,12.1F7D4600/,12.9F824600/,81.38192900/,bus.0/,settings/,system/,statistics/,structure/,simultaneous/,alarm/
print ow._OW.get(/uncached/12.527F4600)
PIO.BYTE,PIO.ALL,PIO.A,PIO.B,T8A/,TAI8570/,address,alias,channels,crc8,family,flipflop.BYTE,flipflop.ALL,flipflop.A,flipflop.B,id,latch.BYTE,latch.ALL,latch.A,latch.B,locator,memory,pages/,power,r_address,r_id,r_locator,sensed.BYTE,sensed.ALL,sensed.A,sensed.B,set_alarm,type
print ow._OW.get(/uncached/12.527F4600/memory)
0FAMILY=MOTIONVERSION=01�
print ow._OW.get(/uncached/12.457C4600)
PIO.BYTE,PIO.ALL,PIO.A,PIO.B,T8A/,TAI8570/,address,alias,channels,crc8,family,flipflop.BYTE,flipflop.ALL,flipflop.A,flipflop.B,id,latch.BYTE,latch.ALL,latch.A,latch.B,locator,memory,pages/,power,r_address,r_id,r_locator,sensed.BYTE,sensed.ALL,sensed.A,sensed.B,set_alarm,type
print ow._OW.get(/uncached/12.457C4600/memory)
0FAMILY=MOTIONVERSION=01�
Note that the XML on the second one, the leading has become a 0.
That appears to be what's breaking things currently. Any ideas what's
causing this and/or how to fix it?
Thanks!
--Jim
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Crash accessing memory
It appears to only effect memory; other sensor values with 2406, as well as all tested values of 18b20 and 2450's are working fine. Its only accessing the RAM. We're using the Dallas USB adapter (9190? I forget exactly; its the blue plastic usb to RJ-11 adapter). We do have one system running 2.8p0 that's been in production for a while (although it just dropped offline this weekend; I haven't gotten to the site to figure out why yet; its probably unrelated to owfs). The two systems we just did a major upgrade on with current versions of all support libraries from gentoo effective last week is what broke. I suspect its a specific dependency failure, not an OWFS one, but I don't even know what dependency to look...As I said, it appears to ONLY break 2406 memory reads (and the methods we're using used to work fine). Thanks! --Jim On Fri, Aug 27, 2010 at 1:41 PM, Paul Alfille paul.alfi...@gmail.com wrote: No, assuming you were able to read a possibly non-text file with your test. What bus master do you use? (I'm looking to see if the fault is with a library like libusb, or possibly with serial port parameters). Is this problem isolated? Do other sensors or properties work? On Fri, Aug 27, 2010 at 4:32 PM, Jim Kusznir jkusz...@gmail.com wrote: We have tested with an owfs mount, and it returned nothing in memory (when we know there is something there), so its also broke at that level. Will owhttpd give us any more info? --Jim -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Crash accessing memory
Hi all: I've got something wrong with my local system, but can't figure out what. I'm running gentoo on an Via C3 Eden and OWFS 2.8p1 (plus indent fix). I recently did a major update, rebuilding the system to bring it up to current versions of stuff. However, right now, whenever one tries to read memory from a DS2406, it blows up. We are using the python interface for our stuff, but I believe we've checked and traced it, and found it happens outside of python. We're running this version (2.8 p1) at other installations, and its working fine. What we don't get is why / where this is coming from. Clearly, some package or something on the system is unhappy. Any suggestions greatly appreciated! This system is supposed to be going into production on Monday morning, and I've been trying to fix this problem for the last two weeks... --Jim -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Crash accessing memory
No, I recompiled *every* package to make sure it was all consistantly linked against the new versions of everything. It turns out that at the moment, we don't have a known good working install of 2.8 p1; I'm going to try and roll back to 2.8p0 + patch, which is currently operating somewhere. --Jim On Fri, Aug 27, 2010 at 11:37 AM, Paul Alfille paul.alfi...@gmail.com wrote: When you say you rebuilt the system, did you pull the OWFS code from the CVS (which is evolving) or from the release? Paul On Fri, Aug 27, 2010 at 1:30 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I've got something wrong with my local system, but can't figure out what. I'm running gentoo on an Via C3 Eden and OWFS 2.8p1 (plus indent fix). I recently did a major update, rebuilding the system to bring it up to current versions of stuff. However, right now, whenever one tries to read memory from a DS2406, it blows up. We are using the python interface for our stuff, but I believe we've checked and traced it, and found it happens outside of python. We're running this version (2.8 p1) at other installations, and its working fine. What we don't get is why / where this is coming from. Clearly, some package or something on the system is unhappy. Any suggestions greatly appreciated! This system is supposed to be going into production on Monday morning, and I've been trying to fix this problem for the last two weeks... --Jim -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Crash accessing memory
Ok, so more testing: We have 2 systems (arm-based) with 2.8p0 + patch, and they work. We have 2 other systems, one arm and one Via C3 (x86-almost), and they don't work. We've tried 2.8p0 + patch and 2.8p1 + indent fix Both of the failed systems recently had a major OS upgrade (gentoo, recompile all packages with current versions), and that's what seems to be causing them to blow up. However, there's insufficient information on the failure as to what might be causing this. Here's the full backtrace: Traceback (most recent call last): File casas_OneWireAgent.py, line 254, in connect self.xmpp.connect(self.username, self.password) File /usr/local/CASAS/casas/xmpp.py, line 114, in connect self.reactor.run() File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 1166, in run self.mainLoop() File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 1175, in mainLoop self.runUntilCurrent() --- exception caught here --- File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 779, in runUntilCurrent call.func(*call.args, **call.kw) File casas_OneWireAgent.py, line 291, in initOneWire self.sensors.addSensor(x) File casas_OneWireAgent.py, line 44, in addSensor type = new.memory File /usr/lib/python2.6/site-packages/ow/__init__.py, line 347, in __getattr__ return owfs_get(object.__getattribute__(self, '_attrs')[name]) File /usr/lib/python2.6/site-packages/ow/__init__.py, line 159, in _get raise exUnknownSensor(path) ow.exUnknownSensor: '/uncached/12.30824600/memory' If you could recommend a list of packages that are involved in this, we can try different versions to fix it. --Jim On Fri, Aug 27, 2010 at 11:57 AM, Jim Kusznir jkusz...@gmail.com wrote: No, I recompiled *every* package to make sure it was all consistantly linked against the new versions of everything. It turns out that at the moment, we don't have a known good working install of 2.8 p1; I'm going to try and roll back to 2.8p0 + patch, which is currently operating somewhere. --Jim On Fri, Aug 27, 2010 at 11:37 AM, Paul Alfille paul.alfi...@gmail.com wrote: When you say you rebuilt the system, did you pull the OWFS code from the CVS (which is evolving) or from the release? Paul On Fri, Aug 27, 2010 at 1:30 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I've got something wrong with my local system, but can't figure out what. I'm running gentoo on an Via C3 Eden and OWFS 2.8p1 (plus indent fix). I recently did a major update, rebuilding the system to bring it up to current versions of stuff. However, right now, whenever one tries to read memory from a DS2406, it blows up. We are using the python interface for our stuff, but I believe we've checked and traced it, and found it happens outside of python. We're running this version (2.8 p1) at other installations, and its working fine. What we don't get is why / where this is coming from. Clearly, some package or something on the system is unhappy. Any suggestions greatly appreciated! This system is supposed to be going into production on Monday morning, and I've been trying to fix this problem for the last two weeks... --Jim -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Crash accessing memory
We have tested with an owfs mount, and it returned nothing in memory (when we know there is something there), so its also broke at that level. Will owhttpd give us any more info? --Jim On Fri, Aug 27, 2010 at 1:14 PM, Paul Alfille paul.alfi...@gmail.com wrote: How about a simple test from the other end. owhttpd and look in a browser and see if you have problems. (Or owserver and owread). If you can read DS2406 memory, the python code might be the problem. I know I've been using DS2406 memory reads for testing in the OWFS current version (still in testing) and it works well. Paul Alfille On Fri, Aug 27, 2010 at 3:36 PM, Jim Kusznir jkusz...@gmail.com wrote: Ok, so more testing: We have 2 systems (arm-based) with 2.8p0 + patch, and they work. We have 2 other systems, one arm and one Via C3 (x86-almost), and they don't work. We've tried 2.8p0 + patch and 2.8p1 + indent fix Both of the failed systems recently had a major OS upgrade (gentoo, recompile all packages with current versions), and that's what seems to be causing them to blow up. However, there's insufficient information on the failure as to what might be causing this. Here's the full backtrace: Traceback (most recent call last): File casas_OneWireAgent.py, line 254, in connect self.xmpp.connect(self.username, self.password) File /usr/local/CASAS/casas/xmpp.py, line 114, in connect self.reactor.run() File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 1166, in run self.mainLoop() File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 1175, in mainLoop self.runUntilCurrent() --- exception caught here --- File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 779, in runUntilCurrent call.func(*call.args, **call.kw) File casas_OneWireAgent.py, line 291, in initOneWire self.sensors.addSensor(x) File casas_OneWireAgent.py, line 44, in addSensor type = new.memory File /usr/lib/python2.6/site-packages/ow/__init__.py, line 347, in __getattr__ return owfs_get(object.__getattribute__(self, '_attrs')[name]) File /usr/lib/python2.6/site-packages/ow/__init__.py, line 159, in _get raise exUnknownSensor(path) ow.exUnknownSensor: '/uncached/12.30824600/memory' If you could recommend a list of packages that are involved in this, we can try different versions to fix it. --Jim On Fri, Aug 27, 2010 at 11:57 AM, Jim Kusznir jkusz...@gmail.com wrote: No, I recompiled *every* package to make sure it was all consistantly linked against the new versions of everything. It turns out that at the moment, we don't have a known good working install of 2.8 p1; I'm going to try and roll back to 2.8p0 + patch, which is currently operating somewhere. --Jim On Fri, Aug 27, 2010 at 11:37 AM, Paul Alfille paul.alfi...@gmail.com wrote: When you say you rebuilt the system, did you pull the OWFS code from the CVS (which is evolving) or from the release? Paul On Fri, Aug 27, 2010 at 1:30 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I've got something wrong with my local system, but can't figure out what. I'm running gentoo on an Via C3 Eden and OWFS 2.8p1 (plus indent fix). I recently did a major update, rebuilding the system to bring it up to current versions of stuff. However, right now, whenever one tries to read memory from a DS2406, it blows up. We are using the python interface for our stuff, but I believe we've checked and traced it, and found it happens outside of python. We're running this version (2.8 p1) at other installations, and its working fine. What we don't get is why / where this is coming from. Clearly, some package or something on the system is unhappy. Any suggestions greatly appreciated! This system is supposed to be going into production on Monday morning, and I've been trying to fix this problem for the last two weeks... --Jim -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d
Re: [Owfs-developers] How can i get a slave serial number allocated?
So, I guess I should update everyone as well... Our lab got someone's (from this list, but I forgot who's -- I don't have it in front of me) AVR onewire slave code, and have been augmenting and improving it. Right now, it just emulates existing Dallis chips, so no explicit support is required. I think we have 3 or 4 chips fully supported, but have had to briefly suspend operations due to a higher priority project coming up. We do wish to share what we have; next Monday with the author comes in I can have him write up a bit about it. I believe he stopped in the middle of getting a 2450 emulated (having to deal with the A2D scaling, as OWFS used a 16bit A2D and the atmel has a 12bit A2D IIRC). Where should such code be archived? I think we got it from a git archive, so perhaps it should go back to that author. Our plans were once we get things a bit more ironed out was to make a special family code and self-describing chip for OWFS to read and configure appropriately. The idea being that the chip could specify to OWFS what names to use for readings (aka, hot_water, cold_water for 2 a2d values, etc). Basically, this description would simply define a name, address range, and type to OWFS, and OWFS would read this from a standard, defined address upon discovery. --Jim On Tue, Aug 10, 2010 at 3:37 PM, Michael Markstaller m...@elabnet.de wrote: Am Sonntag, den 21.02.2010, 08:15 +0200 schrieb tmk: Well, first I have to give it capabilities. Right now it just does the ROM commands. It should be straightforward to expose most of the AVR functionality (pwm, adc, pio, counter) or user defined stuff. Oh, I'd *love* an AVR 1-Wire slave! Yes really ;) Do you want this supported under OWFS? Paul Alfille Once settled (although I wasnt asked ;)): YES best regards Michael -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problem running Python examples
Yep, your file...Our python guys aren't as good as you :) --Jim On Tue, Aug 10, 2010 at 2:24 PM, Joshua J. Kugler jos...@azariah.com wrote: On Tuesday 10 August 2010, Joshua J. Kugler elucidated thus: On Tuesday 10 August 2010, Jim Kusznir elucidated thus: The attached patch file did the job, I recommend it be applied to the main branch! erm...no patch file attached. :) j Oh! You mean the file *I* attached to my e-mail. Sorry...sigh. j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problem running Python examples
The attached patch file did the job, I recommend it be applied to the main branch! Thanks! (Sorry for the delay; I lost my dev platform for a while; just got it back up) --Jim On Tue, Aug 3, 2010 at 10:19 PM, Joshua J. Kugler jos...@azariah.com wrote: On Saturday 31 July 2010, Paul Alfille elucidated thus: If you find a solution, I'll add it to the next release. OK, I found the solution. What was happening was this: 1. Class had defined a custom __getattr__ 2. Then in __getattr__, the class tried to access an attribute via self._attribute_name 3. This then, of course, called __getattr__ again. I'm not 100% sure why it's not finding _attrs in the instance variables. You might want to run the fix against the test suite. Why this did not blow up before Python 2.6, I don't know. And here is the output before the fix (no sensors attached, just a USB key): DEFAULT: ow_ds9490.c:DS9490_detect(457) Unclear what means in USB specification, will use first adapter. DEFAULT: ow_ds9490.c:DS9490_open(1238) Opened USB DS9490 bus master at 003:002. DEFAULT: ow_ds9490.c:DS9490_ID_this_master(600) Set DS9490 003:002 unique id to 81 4B C9 2C 00 00 00 94 DS9490 - / Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS1420 - /81.4BC92C00 And after: DEFAULT: ow_ds9490.c:DS9490_detect(457) Unclear what means in USB specification, will use first adapter. DEFAULT: ow_ds9490.c:DS9490_open(1238) Opened USB DS9490 bus master at 003:002. DEFAULT: ow_ds9490.c:DS9490_ID_this_master(600) Set DS9490 003:002 unique id to 81 4B C9 2C 00 00 00 94 DS9490 - / DS1420 - /81.4BC92C00 Hope that helps! Feedback welcome! j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A --- __init__.py.orig 2010-08-03 20:55:50.0 -0800 +++ __init__.py 2010-08-03 21:10:59.0 -0800 @@ -343,14 +343,11 @@ and thr PIO.0 might be 1. #print 'Sensor.__getattr__', name - if name in self._attrs: - attr = owfs_get( self._attrs[ name ] ) - else: + try: + return owfs_get(object.__getattribute__(self, '_attrs')[name]) + except KeyError: raise AttributeError, name - return attr - - def __setattr__( self, name, value ): Set the value of a sensor attribute. This is accomplished by -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release 2.8p0
that fixed it, thanks! --Jim On Mon, Aug 2, 2010 at 6:06 PM, Paul Alfille paul.alfi...@gmail.com wrote: Ahh, sorry Can you change line 81 of module/owserver/src/c/to_client.c from TrafficOutFD(to server data,io[1].iov_base,io[1].iov_leng,file_descriptor); to TrafficOutFD(to server data,io[1].iov_base,io[1].iov_len,file_descriptor); (That is, change the iov_leng to iov_len.) On Mon, Aug 2, 2010 at 3:54 PM, Jim Kusznir jkusz...@gmail.com wrote: My attempts to build it so far on my dev machine fail: gcc -DHAVE_CONFIG_H -I. -I../../../../src/include -I../include -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -g -O2 -m64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT from_client.o -MD -MP -MF .deps/from_client.Tpo -c -o from_client.o from_client.c mv -f .deps/from_client.Tpo .deps/from_client.Po gcc -DHAVE_CONFIG_H -I. -I../../../../src/include -I../include -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -g -O2 -m64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT to_client.o -MD -MP -MF .deps/to_client.Tpo -c -o to_client.o to_client.c to_client.c: In function ‘ToClient’: to_client.c:81: error: ‘struct iovec’ has no member named ‘iov_leng’ make[4]: *** [to_client.o] Error 1 make[4]: Leaving directory `/root/owfs-2.8p0/module/owserver/src/c' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/root/owfs-2.8p0/module/owserver/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/owfs-2.8p0/module/owserver' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/owfs-2.8p0/module' make: *** [all-recursive] Error 1 This one is not obvious to me as to what module is failing to build. My configure options are: ./configure --disable-zero --disable-parport --enable-owtraffic --prefix=/opt/owfs-2.8p0 --Jim On Mon, Aug 2, 2010 at 11:59 AM, Jim Kusznir jkusz...@gmail.com wrote: You use the same options you would use on the command line in the in options when the bus is initialized through the python command. --Jim On Sun, Aug 1, 2010 at 9:39 PM, Joshua J. Kugler jos...@azariah.com wrote: On Sunday 01 August 2010, Paul Alfille elucidated thus: Release notes 2.8p0 1. W1 (the linux kernel module now called wire) that handles several types of 1wire bus masters is now supported as a surrogate bus master. A. Includes usb, i2c and some architecture-specific gpio (OMAP and ARM) B. Bus masters are added and removed dynamically based on netlink messages from the kernel C. Need Kernel version 2.6.31+ for best performance D. Use --w1 on the command line E. Linux-specific F. Must be run as root. G. using -usb will supercede the w1 usb (since the ds2490.ko module is unloaded) This meas that there are now 3 means of dynamically adding bus masters: A. --uscan (via a libusb scanning loop) B. --w1 (via the kernel module and netlink messages) C. --zero (via Avahi or Bonjour for owservers) Not being intimately familiar with owfs, this might be obvious to some (or documented somewhere), but: how would one select the type of busmaster to use from, say, the Python API. j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release 2.8p0
You use the same options you would use on the command line in the in options when the bus is initialized through the python command. --Jim On Sun, Aug 1, 2010 at 9:39 PM, Joshua J. Kugler jos...@azariah.com wrote: On Sunday 01 August 2010, Paul Alfille elucidated thus: Release notes 2.8p0 1. W1 (the linux kernel module now called wire) that handles several types of 1wire bus masters is now supported as a surrogate bus master. A. Includes usb, i2c and some architecture-specific gpio (OMAP and ARM) B. Bus masters are added and removed dynamically based on netlink messages from the kernel C. Need Kernel version 2.6.31+ for best performance D. Use --w1 on the command line E. Linux-specific F. Must be run as root. G. using -usb will supercede the w1 usb (since the ds2490.ko module is unloaded) This meas that there are now 3 means of dynamically adding bus masters: A. --uscan (via a libusb scanning loop) B. --w1 (via the kernel module and netlink messages) C. --zero (via Avahi or Bonjour for owservers) Not being intimately familiar with owfs, this might be obvious to some (or documented somewhere), but: how would one select the type of busmaster to use from, say, the Python API. j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release 2.8p0
My attempts to build it so far on my dev machine fail: gcc -DHAVE_CONFIG_H -I. -I../../../../src/include-I../include -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -g -O2 -m64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT from_client.o -MD -MP -MF .deps/from_client.Tpo -c -o from_client.o from_client.c mv -f .deps/from_client.Tpo .deps/from_client.Po gcc -DHAVE_CONFIG_H -I. -I../../../../src/include-I../include -I../../../owlib/src/include -L../../../owlib/src/c -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -g -O2 -m64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT to_client.o -MD -MP -MF .deps/to_client.Tpo -c -o to_client.o to_client.c to_client.c: In function ‘ToClient’: to_client.c:81: error: ‘struct iovec’ has no member named ‘iov_leng’ make[4]: *** [to_client.o] Error 1 make[4]: Leaving directory `/root/owfs-2.8p0/module/owserver/src/c' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/root/owfs-2.8p0/module/owserver/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/owfs-2.8p0/module/owserver' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/owfs-2.8p0/module' make: *** [all-recursive] Error 1 This one is not obvious to me as to what module is failing to build. My configure options are: ./configure --disable-zero --disable-parport --enable-owtraffic --prefix=/opt/owfs-2.8p0 --Jim On Mon, Aug 2, 2010 at 11:59 AM, Jim Kusznir jkusz...@gmail.com wrote: You use the same options you would use on the command line in the in options when the bus is initialized through the python command. --Jim On Sun, Aug 1, 2010 at 9:39 PM, Joshua J. Kugler jos...@azariah.com wrote: On Sunday 01 August 2010, Paul Alfille elucidated thus: Release notes 2.8p0 1. W1 (the linux kernel module now called wire) that handles several types of 1wire bus masters is now supported as a surrogate bus master. A. Includes usb, i2c and some architecture-specific gpio (OMAP and ARM) B. Bus masters are added and removed dynamically based on netlink messages from the kernel C. Need Kernel version 2.6.31+ for best performance D. Use --w1 on the command line E. Linux-specific F. Must be run as root. G. using -usb will supercede the w1 usb (since the ds2490.ko module is unloaded) This meas that there are now 3 means of dynamically adding bus masters: A. --uscan (via a libusb scanning loop) B. --w1 (via the kernel module and netlink messages) C. --zero (via Avahi or Bonjour for owservers) Not being intimately familiar with owfs, this might be obvious to some (or documented somewhere), but: how would one select the type of busmaster to use from, say, the Python API. j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design jos...@azariah.com - Jabber: pedah...@gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problem running Python examples
I've been seeing the same problem. It showed up when I switched from
Python2.5 to Python2.6. After spending some time working with some
Python experts, it appears there's some incompatibilities with
python2.6 in the libraries. A previous post of mine on this list
shows the line that the python experts identified. Unfortunately,
nobody in our lab is sufficiently skilled to fix the problem, only
help identify it.
--Jim
On Thu, Jul 29, 2010 at 11:04 PM, Joshua J. Kugler jos...@azariah.com wrote:
So I compiled and installed owfs 2.7p38 and am trying to use the Python
scripts in the examples/ directory, but I'm getting some odd errors.
~/src/owfs-2.7p38/module/swig/python/examples$ ./temperature.py u
DEFAULT: ow_ds9490.c:DS9490_detect(457) Unclear what means in USB
specification, will use first adapter.
DEFAULT: ow_ds9490.c:DS9490_open(1238) Opened USB DS9490 bus master at
004:003.
DEFAULT: ow_ds9490.c:DS9490_ID_this_master(600) Set DS9490 004:003
unique id to 81 4B C9 2C 00 00 00 94
Exception RuntimeError: 'maximum recursion depth exceeded while calling
a Python object' in type 'exceptions.AttributeError' ignored
~/src/owfs-2.7p38/module/swig/python/examples$ ./tree.py u
DEFAULT: ow_ds9490.c:DS9490_detect(457) Unclear what means in USB
specification, will use first adapter.
DEFAULT: ow_ds9490.c:DS9490_open(1238) Opened USB DS9490 bus master at
004:003.
DEFAULT: ow_ds9490.c:DS9490_ID_this_master(600) Set DS9490 004:003
unique id to 81 4B C9 2C 00 00 00 94
DS9490 - /
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.3086A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.0889A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.5877A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.D482A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.B27DA802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.7190A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.C783A802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.376FA802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS18B20 - /28.F76AA802
Exception RuntimeError: 'maximum recursion depth exceeded in
__subclasscheck__' in type 'exceptions.AttributeError' ignored
DS1420 - /81.4BC92C00
iPython output:
In [1]: import ow
In [2]: ow.init('u')
DEFAULT: ow_ds9490.c:DS9490_detect(457) Unclear what means in USB
specification, will use first adapter.
DEFAULT: ow_ds9490.c:DS9490_open(1238) Opened USB DS9490 bus master at
004:003.
DEFAULT: ow_ds9490.c:DS9490_ID_this_master(600) Set DS9490 004:003
unique id to 81 4B C9 2C 00 00 00 94
In [3]: s = ow.Sensor('/')
Exception RuntimeError: 'maximum recursion depth exceeded while calling
a Python object' in type 'exceptions.AttributeError' ignored
Certainly not good. Everything compiled and installed fine when I did
the configure and make dance.
Any ideas?
j
--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
jos...@azariah.com - Jabber: pedah...@gmail.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] More disable bugs in build scripts
Hi: I've been doing a lot of building of owfs, trying to strip it down to just what we need. So far, I've found that if I disable-mt (multithreading), the compile blows up with an undefined refeence. Similarly, disabling W1 gives me: ow_w1_monitor.c: In function 'W1_monitor_detect': ow_w1_monitor.c:26: error: 'W1_detect' undeclared (first use in this function) --Jim -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] python bug (owfs + python 2.6)
Well, I'm stuck in a predicament where I have to get this code working by this thurs at 1pm, and my python dev insists the bug is inside owfs, and therefore is not doing anything else. I'm not proficient in python yet myself, so I'm having difficulty proving/disproving anything in this case. So, I'm looking for any help/suggestions. I did some googling, and found this samle code online (owfs sf faq site): def tree( sensor ): print '%7s - %s' % ( sensor._type, sensor._path ) for next in sensor.sensors( ): if next._type in [ 'DS2409', ]: tree( next ) else: print '%7s - %s' % ( next._type, next._path ) if __name__ == __main__: if len( sys.argv ) == 1: print 'usage: tree.py u|serial_port_path' sys.exit( 1 ) else: ow.init( sys.argv[ 1 ] ) tree( ow.Sensor( '/' ) ) This program (from http://owfs.sourceforge.net/faq.html ) should simply list all the devices in the tree. Instead, what I get is this: casasdbu...@debug /usr/local/CASAS $ python2.6 ~/ow-test.py u DS9490 - / Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS2406 - /12.74804600 Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS2406 - /12.DD365F00 Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS1420 - /81.05412A00 The above devices are accurate; I have two DS2406 devices hooked into a USB 2490 master. However, the maximum recursion depth is a major problem, and causes our code to blow up. I'd greatly appreciate any help in fixing this. I'm also curious to hear from others that are using owpython, especially with python2.6. Thanks! --Jim On Tue, Jul 20, 2010 at 2:08 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: Our lab has been fighting against a problem recently with owfs and python 2.6. We had been happily using python 2.5 and owfs p22 for quite some time. Its been nice and stable, and life was good. Unfortunately, we had a new piece of code that required us to upgrade our python system. Ever since upgrading to 2.6, our attempts at running our software blow up. Our software engineer on the project traced the blow-up to when he called an owfs function. The blow-up is a recursion depth problem,a nd in the process, it only sees one OW device on our network now. So, first thing we did: upgraded to the latest version of owfs (p39), and retry. Unfortunately, the behavior is the same. We're at a loss, as we have stripped out as much of our code as possible. I'm currently trying to get a dev machine going on python2.5 again to try and concretely nail down the problem, but for the moment, this is what I have. Any suggestions? Here's sample output: casasdbu...@debug /usr/local/CASAS $ ./casas_OneWireAgent.py authenticated raw = 12.74804600/,12.DD365F00/,81.05412A00/,bus.0/,settings/,system/,statistics/,structure/ ['12.74804600/', '12.DD365F00/', '81.05412A00/', 'bus.0/', 'settings/', 'system/', 'statisti see: 12.74804600/ addSensor( 12.74804600/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.74804600/] see: 12.DD365F00/ addSensor( 12.DD365F00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.DD365F00/] see: 81.05412A00/ addSensor( 81.05412A00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att see: bus.0/ addSensor( bus.0/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(bus.0/) see: settings/ addSensor( settings/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(settings/) see: system/ addSensor( system/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(system/) see: statistics/ addSensor( statistics/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(statistics/) see: structure/ addSensor( structure/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(structure/) see: alarm/ addSensor( alarm/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(alarm/) OneWire Network Initialized Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'excep Exception RuntimeError
Re: [Owfs-developers] python bug (owfs + python 2.6)
I think I found the function that's going recursive, but I don't know why its going recursive. In the module, near line 345, there is: def __getattr__( self, name ): Retreive an attribute from the sensor. __getattr__ is called only if the named item doesn't exist in the Sensor's namespace. If it's not in the namespace, look for the attribute on the physical sensor. Usage: s = ow.Sensor( '/1F.5D0B0100' ) print s.family, s.PIO_0 will result in the family and PIO.0 values being read from the sensor and printed. In this example, the family would be 1F and thr PIO.0 might be 1. print 'Sensor.__getattr__', name if name in self._attrs: attr = owfs_get( self._attrs[ name ] ) else: raise AttributeError, name return attr (the print statement was there, but commented. I uncommented it for debugging). This is in the sensor class. This function is definitely being called recursively. --Jim On Wed, Jul 21, 2010 at 9:47 AM, Jim Kusznir jkusz...@gmail.com wrote: Well, I'm stuck in a predicament where I have to get this code working by this thurs at 1pm, and my python dev insists the bug is inside owfs, and therefore is not doing anything else. I'm not proficient in python yet myself, so I'm having difficulty proving/disproving anything in this case. So, I'm looking for any help/suggestions. I did some googling, and found this samle code online (owfs sf faq site): def tree( sensor ): print '%7s - %s' % ( sensor._type, sensor._path ) for next in sensor.sensors( ): if next._type in [ 'DS2409', ]: tree( next ) else: print '%7s - %s' % ( next._type, next._path ) if __name__ == __main__: if len( sys.argv ) == 1: print 'usage: tree.py u|serial_port_path' sys.exit( 1 ) else: ow.init( sys.argv[ 1 ] ) tree( ow.Sensor( '/' ) ) This program (from http://owfs.sourceforge.net/faq.html ) should simply list all the devices in the tree. Instead, what I get is this: casasdbu...@debug /usr/local/CASAS $ python2.6 ~/ow-test.py u DS9490 - / Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS2406 - /12.74804600 Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS2406 - /12.DD365F00 Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.AttributeError' ignored DS1420 - /81.05412A00 The above devices are accurate; I have two DS2406 devices hooked into a USB 2490 master. However, the maximum recursion depth is a major problem, and causes our code to blow up. I'd greatly appreciate any help in fixing this. I'm also curious to hear from others that are using owpython, especially with python2.6. Thanks! --Jim On Tue, Jul 20, 2010 at 2:08 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: Our lab has been fighting against a problem recently with owfs and python 2.6. We had been happily using python 2.5 and owfs p22 for quite some time. Its been nice and stable, and life was good. Unfortunately, we had a new piece of code that required us to upgrade our python system. Ever since upgrading to 2.6, our attempts at running our software blow up. Our software engineer on the project traced the blow-up to when he called an owfs function. The blow-up is a recursion depth problem,a nd in the process, it only sees one OW device on our network now. So, first thing we did: upgraded to the latest version of owfs (p39), and retry. Unfortunately, the behavior is the same. We're at a loss, as we have stripped out as much of our code as possible. I'm currently trying to get a dev machine going on python2.5 again to try and concretely nail down the problem, but for the moment, this is what I have. Any suggestions? Here's sample output: casasdbu...@debug /usr/local/CASAS $ ./casas_OneWireAgent.py authenticated raw = 12.74804600/,12.DD365F00/,81.05412A00/,bus.0/,settings/,system/,statistics/,structure/ ['12.74804600/', '12.DD365F00/', '81.05412A00/', 'bus.0/', 'settings/', 'system/', 'statisti see: 12.74804600/ addSensor( 12.74804600/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.74804600/] see: 12.DD365F00/ addSensor( 12.DD365F00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.DD365F00/] see: 81.05412A00/ addSensor( 81.05412A00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att see: bus.0/ addSensor( bus.0
[Owfs-developers] python bug (owfs + python 2.6)
Hi all: Our lab has been fighting against a problem recently with owfs and python 2.6. We had been happily using python 2.5 and owfs p22 for quite some time. Its been nice and stable, and life was good. Unfortunately, we had a new piece of code that required us to upgrade our python system. Ever since upgrading to 2.6, our attempts at running our software blow up. Our software engineer on the project traced the blow-up to when he called an owfs function. The blow-up is a recursion depth problem,a nd in the process, it only sees one OW device on our network now. So, first thing we did: upgraded to the latest version of owfs (p39), and retry. Unfortunately, the behavior is the same. We're at a loss, as we have stripped out as much of our code as possible. I'm currently trying to get a dev machine going on python2.5 again to try and concretely nail down the problem, but for the moment, this is what I have. Any suggestions? Here's sample output: casasdbu...@debug /usr/local/CASAS $ ./casas_OneWireAgent.py authenticated raw = 12.74804600/,12.DD365F00/,81.05412A00/,bus.0/,settings/,system/,statistics/,structure/ ['12.74804600/', '12.DD365F00/', '81.05412A00/', 'bus.0/', 'settings/', 'system/', 'statisti see: 12.74804600/ addSensor( 12.74804600/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.74804600/] see: 12.DD365F00/ addSensor( 12.DD365F00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att ERROR: Sensor Initialization [12.DD365F00/] see: 81.05412A00/ addSensor( 81.05412A00/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att see: bus.0/ addSensor( bus.0/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(bus.0/) see: settings/ addSensor( settings/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(settings/) see: system/ addSensor( system/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(system/) see: statistics/ addSensor( statistics/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(statistics/) see: structure/ addSensor( structure/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(structure/) see: alarm/ addSensor( alarm/ ) Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.Att Error in addSensor(alarm/) OneWire Network Initialized Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'excep Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'excep Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in type 'excep ^Ccleaning up Traceback (most recent call last): File ./casas_OneWireAgent.py, line 375, in module mycon.finish() File ./casas_OneWireAgent.py, line 274, in finish self.xmpp.disconnect() File /usr/local/CASAS/casas/xmpp.py, line 122, in disconnect self.reactor.stop() File /usr/lib/python2.6/site-packages/twisted/internet/base.py, line 553, in stop Can't stop reactor that isn't running.) twisted.internet.error.ReactorNotRunning: Can't stop reactor that isn't running. - Failure occurred at new = ow.Sensor(newsensor); class Sensors: def __init__(self): self.data = dict() self.valid = [DS2406,DS18B20,DS2450] self.publish = None return def addSensor(self, sensor): print addSensor( %s ) % sensor newsensor = /%s % sensor[:-1] try: new = ow.Sensor(newsensor) except: print Error in addSensor(%s) % sensor return snip Any suggestions on this? Thanks! --Jim -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New Release 2.7p39
I'm having trouble building this at the moment. Here's the error: ./include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prot otypes -Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -O2 -pipe -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC 99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ow_browse_resolve.lo -MD -MP -MF .deps/ow_browse_resolve.Tpo - c ow_browse_resolve.c -o ow_browse_resolve.o /dev/null 21 mv -f .deps/ow_browse_resolve.Tpo .deps/ow_browse_resolve.Plo /bin/sh ../../../../libtool --tag=CC --mode=compile armv5tel-softfloat-linux-gnueabi-gcc -DHAVE_CONFIG _H -I. -I../../../../src/include-I../include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes -Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 - D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -O2 -pipe -D_ XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ow_browse_monitor.lo - MD -MP -MF .deps/ow_browse_monitor.Tpo -c -o ow_browse_monitor.lo ow_browse_monitor.c libtool: compile: armv5tel-softfloat-linux-gnueabi-gcc -DHAVE_CONFIG_H -I. -I../../../../src/include -I ../include -fexceptions -Wall -W -Wundef -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prot otypes -Wredundant-decls -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ ISOC99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -pthread -O2 -pipe -D_XOPEN_SOURCE=500 -D_BSD_SOURCE=1 -D_ISOC 99_SOURCE=1 -D_POSIX_C_SOURCE=200112L -MT ow_browse_monitor.lo -MD -MP -MF .deps/ow_browse_monitor.Tpo - c ow_browse_monitor.c -fPIC -DPIC -o .libs/ow_browse_monitor.o ow_browse_monitor.c: In function 'Browse_detect': ow_browse_monitor.c:41: error: 'struct connin_browse' has no member named 'bonjour_browse' ow_browse_monitor.c:43: error: 'struct connin_browse' has no member named 'avahi_browser' ow_browse_monitor.c:44: error: 'struct connin_browse' has no member named 'avahi_poll' ow_browse_monitor.c:45: error: 'struct connin_browse' has no member named 'avahi_client' ow_browse_monitor.c: In function 'Browse_close': ow_browse_monitor.c:72: warning: unused parameter 'in' make[4]: *** [ow_browse_monitor.lo] Error 1 - config excerp: Compile-time options: Caching is enabled USB is enabled I2C is enabled HA7Net is enabled W1 is enabled Multithreading is enabled Parallel port DS1410E is DISABLED TAI8570 barometer is enabled Thermocouple is enabled Zeroconf/Bonjour is DISABLED Debug-output is DISABLED Profiling is DISABLED Tracing memory allocation is DISABLED Module configuration: owlib is enabled owshell is enabled owfs is DISABLED owhttpd is enabled owftpd is DISABLED owserver is enabled ownet is enabled ownetlib is enabled owtap is enabled owmon is enabled owcapi is enabled swig is enabled owperl is enabled owphp is DISABLED owpython is enabled owtcl is DISABLED --- I'm confused by the fact that I disabled zeroconf/bonjour, and yet am getting errors relating to it. OSes: Gentoo and CentOS 5.4 Arches: arm and x86-64 (verified on two different systems) If I don't disable zeroconf, it builds successfully (at least, on my x86_64 system; I don't have zeroconf support libs on my arm system). --Jim On Sun, Jul 18, 2010 at 11:23 AM, Paul Alfille paul.alfi...@gmail.com wrote: Release OWFS 2.7p39 Major addition is the usb scanning funtion. Command line option -uscan or --usb_scan or --usb_scan=10 Every time interval (default 10 seconds) the OWFS program will scan the USB bus for a new DS9490R adapter and add it to the list of bus masters. Even the case where no USB devices exist at startup will be handled, the program will scan and wait. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
[Owfs-developers] debug mode: bus traffic?
Hi all: I've got a programmer working on making the AVR slave code for owfs-compatible slaves. It would be very helpful for him if there was a way one can get owfs to print out everything it sends and receives over the wire. Neither him nor I have figured out the magic debug statement or such to accomplish this. Is it possible? if so, what command options? Thanks! --Jim -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] debug mode: bus traffic?
I was looking for the actual hex commands sent and received over a usb adapter. Thanks! --Jim On Mon, Jul 19, 2010 at 1:20 PM, Paul Alfille paul.alfi...@gmail.com wrote: What kind of information and which bus? I think the serial bus already shows the bytes sent and recieved (with --error_level=6) Perhaps this should be a compile-time option (like the memory messages) with traffic for all the busses. Paul On Mon, Jul 19, 2010 at 2:49 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I've got a programmer working on making the AVR slave code for owfs-compatible slaves. It would be very helpful for him if there was a way one can get owfs to print out everything it sends and receives over the wire. Neither him nor I have figured out the magic debug statement or such to accomplish this. Is it possible? if so, what command options? Thanks! --Jim -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Alarming problems on DS2450
Hi all: I've finally started revisiting the alarming problems we've been having, and started with the A2D (DS2450 -- quad channel A2D). Here's my setup of the chip: In set_alarm: echo 0 unset echo 0,0,0,0 high.ALL echo 0,0,1,0 low.ALL echo 0.0001 voltlow.C cat ../volt.ALL 2.56004, 0.0742199, 0.0678917,0.067501 cat ../alarm/*.ALL 1,0,0,00,1,0,0 So clearly, something isn't working. This is just a test case; I've spent hte last ~2 hours, not managing to get it out of the alarming state any way except explicitly writing 0 into the alarm/* files (eg, explicitly unsetting the alarm). I then write a 1 to simultaneous/voltage, and it resets to some random alarm state. My suspicion is that the alarm set points are not being written in properly. All the above was done in the uncached folder (we haven't been able to make much/any use of the cached folder). Alarming on the DS2406's works fine, but so far we haven't managed to make it work on the DS18B20's (temperature), although I haven't done a through investigation yet (that's next). We're running at this site: owfs version: 2.7p22 libow version: 2.7p22 (although any version we've tested over the past couple years has had similar results...we haven't upgraded much past P22, as its worked, and we run our sites in production and generally don't fix stuff that isn't broke). --Jim -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] DS18B20 alarming problems
Hi all: I completed my testing of the DS18B20 Temperature chips. It turns out that alarming almost works there. If I set temphigh and templow, then cat temperature (or fasttemp, or temperature*), then read the alarm folder, it works correctly. However, if I echo 1 simultaneous/temperature, all my temperature sensors on the bus go into alarming mode. Even when they aren't. If I then go and read any temperature reading on the chip, it will promptly disappear from the alarming list. If I have to querry each temperature sensor and read its temp, it seems alarming is much less useful Thanks! --Jim -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Battery Backup of 1wire network.
Umm..maybe?? Its a standard owfs build. I just did a custom OS build, I need services like ejabberd and some python libs that can be a bit more difficult to find pre-compiled for the arm arch. Basically, the flexibility of many/most gentoo packages just working for the arm (with the time to compile taken into account) was attractive, and so I did that. If someone is interested in more details or the OS image, I can share. I'm not sure it would be that much more helpful than just the instructions and someone doing their own build...It would save a few hours of compile on the sheeva, but that's about it. I would be glad to provide more details to anyone interested, feel free to e-mail me off list, unless there is sufficient interest for this to continue on list. --Jim On Wed, May 12, 2010 at 12:56 PM, Paul Alfille paul.alfi...@gmail.com wrote: would your custom build be useful to others? On May 12, 2010 2:34 PM, Jim Kusznir jkusz...@gmail.com wrote: It may also be noteworthy that I have several sites running in production, so some of our decisions were influenced by that. We have 5 sheeva plugs on hand, and are installing and removing sites semi-regularly, so spending the time once to make a gentoo build and duplicate that several times was a timesaver for us. The SD card decision was also based around that, and has served us well in that respect. I also use one personally for serving up weather data and doing some basic home network serving, and it has been good too. The only issue there seems to be hardware compatibility with a cheap USB 2.0 hub that has to be plugged in AFTER the plug powers up or it won't initialize correctly. --Jim On Wed, May 12, 2010 at 11:30 AM, Jim Kusznir jkusz...@gmail.com wrote: The Sheeva Plugs have b... -- ___ 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] 1wire slave codebase (AVR)
Hmm...I thought that's basically what I was saying...a string or other description in standard format at a standard address that OWFS could download and use to configure itself for that device. BTW: it looks like I just got funding for an embedded systems programmer for the summer to work on this (part-time, about 150hrs total), so my lab will be able to contribute to the effort. --Jim On Wed, Apr 21, 2010 at 1:13 AM, Matthias Urlichs matth...@urlichs.de wrote: On Wed, 21 Apr 2010 08:28:36 +1000, Dr Nathan Hurst wrote: What's wrong with a simple string in a 1-wire accessible location. It's just not what Jim wrote about. :-P -- Matthias Urlichs -- ___ 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] 1wire slave codebase (AVR)
My $0.02: I don't think this approach (unique ID numbers/families/subfamilies for capabilities) is a good approach. This means for each new configuration, a new ID needs to be registered, OWFS needs to be patched to support, etc. As you suggested, this process would only be used on devices/configurations generally available. I think that there's a cleaner, easier, more capable method: Have the device identify itself. I don't think it would take much...just have a chip have a well-known address that OWFS does a read on to describe what data types are available, where they are, and what to call them. Perhaps this can even be in a form similar to what OWFS currently uses in its code... This way, there is only one family code, and OWFS handles it the same, and yet supports essentially infinite device configurations. This even means that devices electrically identical can have different values assigned. Instead of having volts.A, volts.B, etc, it could actually be temperature, batteryVolts, etc. And a second identical chip could be configured with completely different names for the inputs/features available. All this without having to modify OWFS for each new configuration. I think the most serious implication is for those designers experimenting with chips, or doing very custom / not publicly available configurations. In the case suggested in this thread, they'd need to maintain their own patch against OWFS, for some unregistered device ID range that they've selected. Each time they want to upgrade OWFS, they need to make sure their own personal patch applies, or make mods to it, etc. --Jim On Sat, Apr 17, 2010 at 10:13 AM, Jerry Scharf sch...@lagunawayconsulting.com wrote: Given that most of these devices are not so likely to have 4B created over their lifetime, would you be willing to allow the device designer to designate more bits of subtype (subsubtype) to identify functional capability within the device? This would be purely the choice of the designer. As an example: I don't expect more that 1M of my beasts to be built, so I will allocate the other 12 bits for function sets. If I allocate function sets from the top and ids from the bottom of the 32 bits this can be a pretty soft split. The device specific code needs to understand the function sets... I would still recommend that the device id part be unique over the device and not use the function set to disambiguate. This is not quite like the generalized I have x capability discussion, but it is a worthwhile intermediate. thanks, jerry Paul Alfille wrote: Aggreed. I think Louis Swart's technique (at least as expressed in the LCD datasheet) is that FF.0001 is LCD So there are 64 bits - 8 bits CRC8 - 8 bits family code (FF) -16 bits 0001 subtype = 32 bits for the particular device (40 unique devices) That also allows 2^16 potential subtypes (64000) As far as OWFS is concerned, this is extremely easy to implement. Paul Alfille On Fri, Apr 16, 2010 at 6:38 PM, Dr Nathan Hurst n...@njhurst.com wrote: On Fri, Apr 16, 2010 at 09:21:40PM +, Matthias Urlichs wrote: Hi, I wrote: However, I do think that I'd rather implement a 'tell me what you can do' feature command, than allocate a new ID for every crazy ^w interesting idea I might have. On the flip side, Louis Swart lo...@louisswart.co.za replied that he'd be amenable to delegating sub-ID of 'his' 0xFF device ID range to people if they send him a short description of what the code is supposed to be doing. I presume that this way would fit into owfs somewhat more easily. Given the 2^56 ids available under 0xff, I suspect that would do us for the time being. The real problem is overallocation of the space (thus using it up for non-existant instantiations). I suggest that we allocate 32 bit ranges at a time allowing for a wildly successful project to go to everyone on the net, and still allowing 16M projects. njh -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
Re: [Owfs-developers] Hello and AVR based slave device
I've got a (very crude, basic) temperature logging/graphing system running at: http://eme106-temperature.eecs.wsu.edu It monitors and logs our temperatures for 11 points. We used DS18B20's for temperature sensing (which we also use in other projects). I highly recommend them for temperature sensing. I also strongly recommend avoiding the older, but compatible 18S20 -- they are several times slower and are more finicky. The DS18B20's cost in the $2-3 range if I recall correctly. They're a single-chip solution in a TO-92 case. One pin OW, one pin GND, and one pin either tied to ground for parasitic mode, or hooked up to +5 for self-powered mode. Its device family 28 for ID's. We're running this particular system on a P3-700Mhz tower that was laying around; for our main research projects we use the Sheeva Plugs, which I do recommend...the sheeva's are a great device for things such as this. For logging, we are using a perl script and owperl to sleep for 5 min, then read fasttemp from the uncached directory on all of our sensors, storing the values into a mysql db. After the collection run finishes, it calls a php script that generates the main cart and temp table. When you load it, there's a bit of php code to ensure the data is current (the little check at the top), but otherwise its a static page (it used to create all the images on page load, but due to bad programming and weak hardware, this was pretty hard on the server; the static content is much nicer, and I now have no qualms about sending out the URL here...I wouldn't have done that before!). --Jim Manager, WSU Artificial Intelligence Lab On Fri, Mar 26, 2010 at 3:18 AM, Paul Alfille paul.alfi...@gmail.com wrote: On Fri, Mar 26, 2010 at 3:21 AM, Alex Shepherd list...@ajsystems.co.nz wrote: Just joined the list, so - hello everyone! Welcome! Last year I've had some custom PCB's made (min order of 100 actually) for the DS28EA00 sensor to use in my new house to monitor the floor/room temperatures and control my underfloor heating system, that's powered by a The DS28EA00 is supported in OWFS for temperature and PIO. Chain mode hasn't been implemented, since there was no demand and since it fits a little awkwardly in our filesystem metaphor. Having a background in industrial automation and control system I thought I'd try and be a bit smarter with the controls side of things and sprinkle a bunch of sensors around the house to have a better idea of the thermal load characteristics of the house and hopefully control it a bit better than with just a simple thermostat on the wall. However I did run some mains cables to where thermostats on the wall could go in case my grand plans fail... :( There is a DS1821 thermostat chip. It's only sort of a 1-wire device, with no ID and needing external circuitry to return to 1-wire control. You would be better off using a microprocessor 1-wire slave. I have run 2 separate microLAN's using Cat5e UTP cable that will have about 20-30 sensors on each LAN. These LAN's run back to my central comms rack. I decided to keep the LAN's simple and linear as I need robustness and so I avoided going down the path of hubs etc to manage what would become a star network with it's associated impedance problems. Very nice. Even if your wire runs didn't return to the same location, you could have joined the 1-wire networks with owserver over TCP/IP. I have 3 x LinkUSB adaptors (1 spare for a while) and an old Compaq Thin Client with a 2.5 80G disk and Debian LXDE Linux installed. I'll use this initially to get things going and host a web server to display the various room temperatures on a nice graphs to assist with commissioning the system. Hopefully I will be able to move some or all of this to a diskless NSLU2 once things are all working. The NSLU2 certainly works. Something more recent like the SheevaPlug is the same price and power consumption and has 512MB ram vs 32MB. Initially I need to get my head around how to configure owfs to interface the 2 LinkUSB adaptors and get the temperatures stored in a database somewhere on my LAN and display the temperatures on graphs via a web browser. Once I get the measurement system in place I'll move on to controlling it. I'd use owserver as the interface to the LINK adapters, and then communicate with owserver using the various OWFS programs. This allows ad-hoc queries and debugging, while also running a data collection and control process separately. The general syntax is /opt/owfs/bin/owserver -d serial_port -p tcp_port (default tcp_port of 4304 is used if -p is omitted) Linking the two adapters is effortless, just list them both on the command line. /opt/owfs/bin/owserver --LINK /dev/ttyS0 --LINK /dev/ttyS1 (Here I used the LINKs in LINK mode rather than DS9097U emulation mode, and used the default port of 4304) Depending on serial port permissions, this may have to be run as root. To see your network:
Re: [Owfs-developers] My wish list for implementing Intelligent Slave Devices
This is my thought, yes. I was thinking something along the lines of read an int at addres and call it temperature type commands. --Jim On Mon, Mar 8, 2010 at 10:13 AM, Paul Alfille paul.alfi...@gmail.com wrote: So if I understand correctly, the firmware upload not only programs the slave, it also contains information for OWFS to parse and create the devices? On Mon, Mar 8, 2010 at 11:31 AM, Jim Kusznir jkusz...@gmail.com wrote: Yes, I was intending on this being stored in eeprom on the slave device. I believe in most cases, the slave device will be soldered on a board with its support electronics for whatever task it is doing. As such, its task is not going to change. I am NOT (currently) proposing that information such as where the sensor is located or what its monitoring the temperature of, for example, are stored...Just information as to what it is (its a temperature and light detector, for example) and how to get data from it. So, in my use case below, a hobbyist who doesn't have the microprocessor development kit / JTAG cable / etc, could take a chip that has been flashed with the base, build his device, and plug it into a onewire bus. At that point it will show up, but only have one or so functions in OWFS: a file for firmware load that they can then cp the personality file to. That will transfer the personality to the chip. Once complete, the user then unplugs the OW device, then plugs it back in. When OWFS discovers the device, it will have more info in its configuration space that will tell OWFS 1) what address locations to read on the slave; 2) what type of value its reading (how long it is); and 3) what text description to call it in its directory tree. As such, this would allow OWFS to NOT need any special configuration for individual slaves. It would allow a completely flexible slave, even for hobbyists who don't know/want to get into the full microprocessor development. It would even allow such people to write/modify their own personalities (compiling with GCC, hopefully, or some other SDK freely downloadable) and upload them, or choose from a set of standard or example personalities provided by the open source project that's designing / producing the code for the chip. Of course, people wishing to commercialize this can sell chips pre-programmed with the base (or those who have sufficient microprocessor facilities can buy their own devices from the manufacturer and flash the base on them with JTAG/etc themselves). These individuals can even make their own personalities that are commercial/copyrighted and people can buy those from the individual/company. I'm sure individuals would also want to contract with an expert to write personalities for them, too. I do think its critically important that the core of the project be open source. Right now, the fact that the only slave devices available are commercial / closed source are a major damper on the hobbyist's and researcher/experimenter's ability to grow and use OW / OWFS for even cooler things. I know that I need custom work, and I'm not going to pay someone else to develop a custom chip that I'd then have to buy individually from them and not own the source code. I already have a staff of programmers here, and due to university policies and procedures, its very difficult if not impossible to pay for such services. --Jim -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] My wish list for implementing Intelligent Slave Devices
Yes, I was intending on this being stored in eeprom on the slave device. I believe in most cases, the slave device will be soldered on a board with its support electronics for whatever task it is doing. As such, its task is not going to change. I am NOT (currently) proposing that information such as where the sensor is located or what its monitoring the temperature of, for example, are stored...Just information as to what it is (its a temperature and light detector, for example) and how to get data from it. So, in my use case below, a hobbyist who doesn't have the microprocessor development kit / JTAG cable / etc, could take a chip that has been flashed with the base, build his device, and plug it into a onewire bus. At that point it will show up, but only have one or so functions in OWFS: a file for firmware load that they can then cp the personality file to. That will transfer the personality to the chip. Once complete, the user then unplugs the OW device, then plugs it back in. When OWFS discovers the device, it will have more info in its configuration space that will tell OWFS 1) what address locations to read on the slave; 2) what type of value its reading (how long it is); and 3) what text description to call it in its directory tree. As such, this would allow OWFS to NOT need any special configuration for individual slaves. It would allow a completely flexible slave, even for hobbyists who don't know/want to get into the full microprocessor development. It would even allow such people to write/modify their own personalities (compiling with GCC, hopefully, or some other SDK freely downloadable) and upload them, or choose from a set of standard or example personalities provided by the open source project that's designing / producing the code for the chip. Of course, people wishing to commercialize this can sell chips pre-programmed with the base (or those who have sufficient microprocessor facilities can buy their own devices from the manufacturer and flash the base on them with JTAG/etc themselves). These individuals can even make their own personalities that are commercial/copyrighted and people can buy those from the individual/company. I'm sure individuals would also want to contract with an expert to write personalities for them, too. I do think its critically important that the core of the project be open source. Right now, the fact that the only slave devices available are commercial / closed source are a major damper on the hobbyist's and researcher/experimenter's ability to grow and use OW / OWFS for even cooler things. I know that I need custom work, and I'm not going to pay someone else to develop a custom chip that I'd then have to buy individually from them and not own the source code. I already have a staff of programmers here, and due to university policies and procedures, its very difficult if not impossible to pay for such services. --Jim On Sat, Feb 27, 2010 at 11:40 AM, Jerry Scharf sch...@lagunawayconsulting.com wrote: Jim, Is this going into EEPROM? I was thinking you were saying this happened each time the slave came up. jerry Jim Kusznir wrote: Jerry others: I was thinking that a personality could be loaded into the chip via owfs (just as a memory write, basically). While I haven't worked on this enough to know the size, I also envision this being an infrequent task (when you first set up a new device, or when you do a major re-purpose of the device, connecting it to different hardware, etc). Of course, for larger or more complicated processors, this could always be done offline (typical microprocessor load such as USB/JTAG, etc). I wasn't saying that all these devices need to be done via 1-wire, or even that it is a requirement; I was just thinking of an easy way for people to change the personality of the chip without having to invest in a microprocessor programming environment. This isn't strictly required, but it appeared to be fairly doable, and thus I proposed it :) In a production environment, one might want to have a second OW network for testing and programming the chip. --Jim On Fri, Feb 26, 2010 at 8:51 AM, Jerry Scharf sch...@lagunawayconsulting.com wrote: Jim, You are closer to my view of control systems. I generally want susbsystems to be able to act autonomously with the brains doing the more complex work. So it's more like a hierarchy than a pure mesh. I also think about redundancy. Just because 1wire is low cost doesn't mean it can't be used in more demanding control systems. I have lots of sensors, but use multiple masters to help with the isolation and bandwidth problems. One of the big down sides for this approach is the debugging environment on the uC side is far poorer and harder to do. I think this is where people get to wanting to buy something that someone else has worked out. One question I have is about the bootstrapping. It seems like this is outside the scope of OWFS. I love
Re: [Owfs-developers] My wish list for implementing Intelligent Slave Devices
A PC is definitely more powerful, and its programming paradigms are easier to address, true. However, we've played those games in our OW setup, and have been going back to the do-it-on-hardware side. For us, we have a large network of OW devices (often 50+), a PC software suite written by a couple different people that needs to collect all the data, and we're looking at control. Of course, timeliness is also an issue. We found that often, we ran into OW bus saturation issues. Something as simple as alarming on the 2450 not working almost took down our bus, as we had to poll it. Now, not only are we wasting a lot of bus bandwidth (which was delaying other devices and messing with our project in a negative sense), but we were also not getting our analog data as timely and precisely as we wanted. We're also looking at other activities, such as a OW-based thermostat/heating control system. For this, we definitely want a local thermostat, as if the OW system goes down, so does heat...Out here, that can mean frozen / broken pipes. Combine that with people living in the space who are not familiar with the innards of the technology (i.e., not able to restart/diagnose the OW system), and you've got a fixed requirement for local backup control. We're also looking at some new motion sensors (our primary OW device is a motion sensor equipped with an DS2406), that would need a fair bit more processing and would be producing a much richer data format. For us, its important that 1) the device identify that it is a rev xx motion sensor and provide the richer data in such a way as to not saturate our bus. This requires local pre-processing and decisions on when to raise the alarm. In addition, auto-identifying systems is important for us. We have several of these large-ish deployments, and often have limited time to set them up. We take great lengths to try and make the system as automated as possible, especially in the setup phase. To this end, we use the EEPROM in the 2406's to burn in a device type ID to further distinguish between the various devices we have that use 2406's. If we go to a microprocessor model to replace or provide input types not available in dallas chips, it would also be critical that the chip identify its function to the system. That was a major headache we have with the 2450 presently...We don't know how to treat its values (we see we have 4 analog readouts now, but what are they? Some we only have A hooked up, we don't even care about B, C, or D...Others have ranges on the various pins that mean different things and in some cases we have to change how we read certain pins for precision, etc). To us, hard-coding this at the PC is an absolute mess of a hack that we wish to avoid. So, for us it would be wonderful to have a microprocessor which we could configure to do any preprocessing we want it to, put in some id string that the OW master can read, and support custom data types, ideally including the scaling and precision type settings in the chip. To this end, it seems to me that a wonderful solution would be a microprocessor with a base code (USB flashed, etc) that would have its OW ID and a basic bootloader code in it. I could then select a code function (either supplied by others or written by myself), and cat it to the right OWFS file to program that personality. I've spoken to some local ATMEL experts, and they say that's very doable with the atmel line of chips. I would also like to suggest that the code is available open source. I've already encountered a few other commercial projects similar to the BAE which have about 70% of what we need for a project or experiment. But, as the source is closed, our only option is to use it as is, or pay them to develop what we want. We already have the programmers on staff who are more connected with the problem and have the proper environment to test, so it doesn't make sense to pay for their development services. Much of what we do will be highly custom, so source access is very important to us. That said, I think there's still a commercial market for devices pre-programmed. While we're perfectly happy with buying stock microcontrollers and flashing them with custom code, many people won't be. While we can write our own functions and such, some people would want to select from x channel A2D or pwm controller, etc. Some people may even want to pay someone to program custom modules for their application. However, if we end up with another closed-source solution where groups like us can't get the source and modify it for our custom applications, I think its doing a disservice to the OW community. By opening up the source, I think we'll quickly see a wide variety of new applications and functionalities that were not previously thought of, or exceed the resources of an individual to develop and commercialize. So, to answer tmk's thoughts on why not just do it in a PC, that's an appropriate answer for some applications, but
Re: [Owfs-developers] My wish list for implementing Intelligent Slave Devices
Jerry others: I was thinking that a personality could be loaded into the chip via owfs (just as a memory write, basically). While I haven't worked on this enough to know the size, I also envision this being an infrequent task (when you first set up a new device, or when you do a major re-purpose of the device, connecting it to different hardware, etc). Of course, for larger or more complicated processors, this could always be done offline (typical microprocessor load such as USB/JTAG, etc). I wasn't saying that all these devices need to be done via 1-wire, or even that it is a requirement; I was just thinking of an easy way for people to change the personality of the chip without having to invest in a microprocessor programming environment. This isn't strictly required, but it appeared to be fairly doable, and thus I proposed it :) In a production environment, one might want to have a second OW network for testing and programming the chip. --Jim On Fri, Feb 26, 2010 at 8:51 AM, Jerry Scharf sch...@lagunawayconsulting.com wrote: Jim, You are closer to my view of control systems. I generally want susbsystems to be able to act autonomously with the brains doing the more complex work. So it's more like a hierarchy than a pure mesh. I also think about redundancy. Just because 1wire is low cost doesn't mean it can't be used in more demanding control systems. I have lots of sensors, but use multiple masters to help with the isolation and bandwidth problems. One of the big down sides for this approach is the debugging environment on the uC side is far poorer and harder to do. I think this is where people get to wanting to buy something that someone else has worked out. One question I have is about the bootstrapping. It seems like this is outside the scope of OWFS. I love the design you propose, but I am wondering if it lives next to OWFS rather than within it. Are you saying that we would use OWFS to do the bootstrapping at the user level? It seems like that could really saturate the bus for a more complex device. jerry Jim Kusznir wrote: A PC is definitely more powerful, and its programming paradigms are easier to address, true. However, we've played those games in our OW setup, and have been going back to the do-it-on-hardware side. For us, we have a large network of OW devices (often 50+), a PC software suite written by a couple different people that needs to collect all the data, and we're looking at control. Of course, timeliness is also an issue. We found that often, we ran into OW bus saturation issues. Something as simple as alarming on the 2450 not working almost took down our bus, as we had to poll it. Now, not only are we wasting a lot of bus bandwidth (which was delaying other devices and messing with our project in a negative sense), but we were also not getting our analog data as timely and precisely as we wanted. We're also looking at other activities, such as a OW-based thermostat/heating control system. For this, we definitely want a local thermostat, as if the OW system goes down, so does heat...Out here, that can mean frozen / broken pipes. Combine that with people living in the space who are not familiar with the innards of the technology (i.e., not able to restart/diagnose the OW system), and you've got a fixed requirement for local backup control. We're also looking at some new motion sensors (our primary OW device is a motion sensor equipped with an DS2406), that would need a fair bit more processing and would be producing a much richer data format. For us, its important that 1) the device identify that it is a rev xx motion sensor and provide the richer data in such a way as to not saturate our bus. This requires local pre-processing and decisions on when to raise the alarm. In addition, auto-identifying systems is important for us. We have several of these large-ish deployments, and often have limited time to set them up. We take great lengths to try and make the system as automated as possible, especially in the setup phase. To this end, we use the EEPROM in the 2406's to burn in a device type ID to further distinguish between the various devices we have that use 2406's. If we go to a microprocessor model to replace or provide input types not available in dallas chips, it would also be critical that the chip identify its function to the system. That was a major headache we have with the 2450 presently...We don't know how to treat its values (we see we have 4 analog readouts now, but what are they? Some we only have A hooked up, we don't even care about B, C, or D...Others have ranges on the various pins that mean different things and in some cases we have to change how we read certain pins for precision, etc). To us, hard-coding this at the PC is an absolute mess of a hack that we wish to avoid. So, for us it would be wonderful to have a microprocessor which we could configure to do any
Re: [Owfs-developers] My wish list for implementing Intelligent Slave Devices
On Fri, Feb 26, 2010 at 9:13 AM, Pascal Baerten pascal.baer...@gmail.com wrote: my thoughts within the text... 2010/2/26 Jim Kusznir jkusz...@gmail.com A PC is definitely more powerful, and its programming paradigms are easier to address, true. However, we've played those games in our OW setup, and have been going back to the do-it-on-hardware side. For us, we have a large network of OW devices (often 50+), a PC software suite written by a couple different people that needs to collect all the data, and we're looking at control. Of course, timeliness is also an issue. I consider that 1wire slaves should have autonomous capabilities where master play the role of orchestrator giving consigns to slaves and getting reports from them. Our approach is slightly different. We want the devices to tell the master what they are, eliminating any site-specific custom configuration for the OWFS master software. For example, I do NOT want to have to type in a list of OW serial numbers and that this device is handled this way, etc. Instead, I want the OW device to tell the OW master what type of device it is (specifically), so then the OW master knows how to handle it (the standard way all devices of type/configuration X are). I realize some people have smaller networks and/or don't care, but there are larger networks, especially when more people are involved, where it makes more sense to make the devices able to identify themselves a bit better. In addition, auto-identifying systems is important for us. We have several of these large-ish deployments, and often have limited time to set them up. We take great lengths to try and make the system as automated as possible, especially in the setup phase. To this end, we use the EEPROM in the 2406's to burn in a device type ID to further distinguish between the various devices we have that use 2406's. If we go to a microprocessor model to replace or provide input types not available in dallas chips, it would also be critical that the chip identify its function to the system. That was a major headache we have with the 2450 presently...We don't know how to treat its values (we see we have 4 analog readouts now, but what are they? Some we only have A hooked up, we don't even care about B, C, or D...Others have ranges on the various pins that mean different things and in some cases we have to change how we read certain pins for precision, etc). To us, hard-coding this at the PC is an absolute mess of a hack that we wish to avoid. I proposed to Paul during development of BAE0910 to have the chip itself publishing field mapping to dynamically present fixed/configured features to owfs. But currently owfs don't support dynamic properties. I'm not exactly sure on what 'dynamic properties' entails in this case. To be clear, I am NOT proposing the devices' properties change while it is online. I envision a situation where when the device discovery is run, it finds a serial number with family code, say, 99. OWFS knows that means its run with chip driver uC, and that driver knows to go read memory address x, parse the output, and then pass on to OWFS the list of fields that are valid. As long as that device serial number remains on the network, that's all it exposes. If one wants to reconfigure it, the device goes offline, then gets re-discovered and re-enumerated. In my vision of this, the devices do NOT change personality very often. In fact, I envision many devices never changing personality...but they can. The more important aspect to me is that I can load custom personalities on the device, and I can keep one device on hand, and use that for many different applications, including designing new hardware devices and prototyping. It may also note that I don't intend on OWFS to support doing conversions in the software (aka map this 0-5VDC number into a temperature using this formula)...To me, that's part of a chip's personality and job. However, the chip can tell the OWFS driver that 'memory address x should be exposed as Temperature1 and is read-only; memory address is heat_setpoint and is read/write.' To this end, it seems to me that a wonderful solution would be a microprocessor with a base code (USB flashed, etc) that would have its OW ID and a basic bootloader code in it. I could then select a code function (either supplied by others or written by myself), and cat it to the right OWFS file to program that personality. I've spoken to some local ATMEL experts, and they say that's very doable with the atmel line of chips. I would also like to suggest that the code is available open source. I've already encountered a few other commercial projects similar to the BAE which have about 70% of what we need for a project or experiment. But, as the source is closed, our only option is to use it as is, or pay them to develop what we want. We already have the programmers on staff who are more connected
Re: [Owfs-developers] DS2450 alarm thresholds
We've attempted to do this for our own uses (somewhat similar). Unfortunately, owfs appears to have bugs in this area and does not perform correctly. I hope to have time to do some low-level debugging with the 2450 datasheet to figure out where the problem is and submit a specific bug report. In general, you need to set the alarm criteria for the high and low, then you have to do an ls in the alarming folder (preferably in the uncached folder). We use alarming extensively on the 2406 for detecting pio transitions (used to detect relay-based motion detector's activity). Alarming has made the onewire system a feesable bus for our purposes, and we have run into major issues trying to simulate alarming on 2450's with bus saturation. As soon as I have time to look into this more, I will post my findings to this list. As far as we've been able to extrapolate so far, the 2450 is not properly set up for alarming by owfs. --Jim On Thu, Feb 25, 2010 at 4:15 PM, Paul Alfille paul.alfi...@gmail.com wrote: When in alarm condition, the device should appear in the /alarm directory. OWFS won't automatically poll the device, you need to do this in your program. (It can be as simple as a shell script with a loop and a sleep command). Paul Alfille On Thu, Feb 25, 2010 at 6:40 PM, Alessio Sangalli ale...@manoweb.com wrote: Just a question: in what way I can use DS2450's alarm threshold feature? Basically, I want to monitor and detect overvoltages coming on the Vin. Say I want to report everytime the voltage goes above 20VDC (when the nominal is 14VCD). I could setup a voltage divider so that I can measure up to say, 75V and still be in the range of the 5.12VDC the DS2450 can sample from. And this is all under control. How do I use the software to notify when I get this overvoltage? This is what I do not understand, right now :( Thank you Alessio -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Announcement for a new 1-wire slave device BAE0910
I've been thinking about this issue off and on for a couple years now, and I like a large part of what I see so far, but also want to throw in some thoughts. After reading some details on the BAE chip as well as talking to some embedded designers and thinking about applications, I envisioned something a bit different and simpler. I'm coming from the perspective of a middleware designer, who's most recent masterpiece was a setup where simpler is better was the focus, and the results were pretty surprising (thesis in progress :) ). My thoughts were to build a sort of 2-stage microprocessor code (open source so it can be adapted to different chips as needed). The bottom stage or boot loader would contain the base OWFS communication libraries (including the devices unique ID), and support for the fimrware load function. The firmware load would allow one to upload new firmware to the chip. This firmware is the phase 2 code, and would enable functions of the processor as desired. Specifically, EVERY USER would load a fimrware module that would configure the remaining capabilities of the microprocessor they want to use, do whatever control/computation work they want to do, and tell the phase 1 fimrware what types of data they're exposing. I believe this needs to be done in a memory mapped function, and perhaps it could be as simple as a configuration block that OWFS can read. This would provide information such as memory address, size, type, read/write status, and plaintext name. Using this, OWFS can populate a directory with whatever capabilities that chip has enabled. An important detail here is that the chip would NOT expose all possible I/O by default. As was previously pointed out, there are often different capabilities of a processor that share pins. They can't all be available at all times, and what makes sense is going to be highly dependent on how its wired. As such, it seems that its reasonable to load custom fimrware to configure the microprocessor to do what is needed. And I'd rather have that functionality. Even if it isn't a 2-stage code for the microprocessor, but a framework that I tweak for my application. That way, if I am just using the adc as a thermocouple input, I can tell OWFS that its temperature, and I can internally convert the reading as appropriate. I prefer to leave the naming, typing, etc. of data to the entity that has the greatest authority as to what that data is. That's why I belive this responsibility lies with the microprocessor, not OWFS. I also try to think about as many of the different application as I can think of, and then apply the various proposals of how to make it work. Then, take the results and look at what result was simplest or most natural. Some of the more recent OWFS text-file configuration and special module-loading sounds like making things overly complicated...Why configure your device in two places and make sure to keep them in sync when you can just do it in one and not have a sync/config issue? --Jim -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Announcement for a new 1-wire slave device BAE0910
We've intermittently worked on this. I have one student who has made the beginnings of PIC code for OW slave interface, although has implemented very few of the commands so far. I also have some C code intended for compiling for the Atmel to implement the timings and raw read/write for slave devices on the OW bus. This hasn't been tested at all yet. I'm responsible for the Artificial Intelligence lab at Washington State University, and currently the OW bus is our main sensor bus. So far, our work has focused on using the 2406 to do open/close-style measurement of various devices (motion detector, micro-switches, security-style door sensors, etc). We would like to be able to make a OW thermostat that would allow control of our heating system (both analog and digital output) as well as provide an LCD interface for users to view and set the desired thermostat (they can be different devices, although our early intentions are to integrate in a single package to provide failover capability...don't want to freeze anyone out because our OW host/bus crashes!). In any case, I may be able to get someone on this over the summer. --Jim On Mon, Feb 22, 2010 at 8:24 AM, tmk nufan_...@comcast.net wrote: I am writing a 1 wire slave library for the AVR series of microcontrollers. That should allow you to do all the stuff you want. Hooking into OWFS might be a little tricky if everyone implements their own functionality though. If a standard set of functionalities can be agreed on, (counter, pwm, tri state pio, temp sensor, ADC, memory access), then almost anything could be done Anyone have other suggestions for functionality? I figure that should cover most cases, and other stuff could be done with the memory access. In fact I will most likely implement it all with memory commands. Off topic: I have also considered making a complete clone of the DS2490 (usb to 1 wire master) on an AVR chip. $30 is too much for a USB - 1wire adapter! An ATTiny chip should be able to handle it no problem Would this be interesting? Is there a datasheet on the 2490 usb interface? Owfs supports it, so I should be able to get what I need from the source code, worst case -tmk On Feb 22, 2010, at 7:38 AM, Benjamin Donnachie benja...@py- soft.co.uk wrote: On 22 February 2010 15:22, Pascal Baerten pascal.baer...@gmail.com wrote: But if for any reason I would stop this activity, I will pass the relay to someone else, or even open source the project... I'm a newcomer to 1-wire and was a bit disappointed to see the DS2423 phased out and joined this list to discuss the practicalities of building a counter replacement from a simple PIC. However, BAE0910 seems to be an excellent alternative and I'm hoping to order the board shortly. However, I'd be interested to know whether there is any interest in a simple open-source PIC-based counting device? Has anyone tried this approach already? Take care, Ben --- --- --- - Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Permissions problems with usb as root???
Hmm...It looks like the problem may have been a failed USB Onewire adapterI've never seen that before, but the same adapter on a different machine that was working failed in the same way. When I changed out its adapter, it worked. Guess I need to get a new adapter... --Jim On Fri, Dec 4, 2009 at 5:10 PM, Jim Kusznir jkusz...@gmail.com wrote: That's the wierd thing..I can't think of anything. Most of my working installs are on 64 bit machines, and this is a 32 bit machine, but I also have working installs on 32. They're the same versions of CentOS/patch level. They're different generations of hardware (Pentium D's vs P-3 or something similar). This current one was made with the latest released owfs; the other installs have been around longer and thus use other versions (but I don't know which...at the moment, they're powered down or in use for other stuff away from our onewire bus). --Jim On Thu, Dec 3, 2009 at 7:06 PM, Paul Alfille paul.alfi...@gmail.com wrote: Ok, let's be systematic. What are the differences between the new installation the the existing successful ones? Paul On Tue, Dec 1, 2009 at 5:07 PM, Jim Kusznir jkusz...@gmail.com wrote: Unfortunately, that was one of the first things I tried...I did not have any kernel modules ds* or *onewire* loaded anywhere...They're not even installed. --Jim On Mon, Nov 30, 2009 at 5:45 PM, Paul Alfille paul.alfi...@gmail.com wrote: On Mon, Nov 30, 2009 at 4:47 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I'm trying to get a machine running the latest owfs (owfs-2.7p26.tar.gz, downloaded this morning). I've configured it with defaults except --enable-owfs. After building, installing, and modifying my path to include the install dir, I tried running: owfs u /mnt/owfs I learned something new. I was astonished to see that u works as well as the documented -u for USB. And it does work, at least on Ubuntu. My first thought was root permissions, but you've tried that. My next thought is the ds2490 kernel module. Can you try rmmod on that? Paul Alfille -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Permissions problems with usb as root???
I tried both of your find commands, and neither returned anything relevant (the first returned nothing; the second returned only firewire and wireless entries). --Jim On Mon, Nov 30, 2009 at 2:30 PM, Pascal Brugier pbrug...@aeon-hq.net wrote: On Mon, 30 Nov 2009 14:10:34 -0800, Jim Kusznir jkusz...@gmail.com wrote: [r...@eme206-guest ~]# uname -a Linux eme206-guest.eecs.wsu.edu 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:18:27 EST 2009 i686 i686 i386 GNU/Linux [r...@eme206-guest ~]# lsmod |grep ds [r...@eme206-guest ~]# lsmod |grep one Strange, my system load both modules, perharps problem is there. Can you try : undertow:~# find /lib/modules -name *ds2490* /lib/modules/$KERNEL_VERSION/kernel/drivers/w1/masters/ds2490.ko undertow:~# find /lib/modules -name *wire* /lib/modules/$KERNEL_VERSION/kernel/drivers/w1/wire.ko And compare your results with mine. It seems that you kernel have been compiled like on a mutualized server, perharps modules are not available. Pascal. -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Permissions problems with usb as root???
Unfortunately, that was one of the first things I tried...I did not have any kernel modules ds* or *onewire* loaded anywhere...They're not even installed. --Jim On Mon, Nov 30, 2009 at 5:45 PM, Paul Alfille paul.alfi...@gmail.com wrote: On Mon, Nov 30, 2009 at 4:47 PM, Jim Kusznir jkusz...@gmail.com wrote: Hi all: I'm trying to get a machine running the latest owfs (owfs-2.7p26.tar.gz, downloaded this morning). I've configured it with defaults except --enable-owfs. After building, installing, and modifying my path to include the install dir, I tried running: owfs u /mnt/owfs I learned something new. I was astonished to see that u works as well as the documented -u for USB. And it does work, at least on Ubuntu. My first thought was root permissions, but you've tried that. My next thought is the ds2490 kernel module. Can you try rmmod on that? Paul Alfille -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Permissions problems with usb as root???
Hi all: I'm trying to get a machine running the latest owfs (owfs-2.7p26.tar.gz, downloaded this morning). I've configured it with defaults except --enable-owfs. After building, installing, and modifying my path to include the install dir, I tried running: owfs u /mnt/owfs as user root, and I get: [r...@eme206-guest ~]# owfs u /mnt/owfs DEFAULT: ow_ds9490.c:DS9490_sub_open(552) Opened USB DS9490 adapter at 002/004. Could not open the USB adapter. Is there a problem with permissions? DEFAULT: ow_ds9490.c:DS9490_detect(310) Could not open the USB adapter. Is there a problem with permissions? DEFAULT: owlib.c:SetupInboundConnections(175) Cannot open USB adapter The system is CentOS 5.4 (RedHat Enterprise Linux 5.4). We have systems working with this and older versions of the owfs software, but I've never tried it on this box specifically. Suggestions? I'd know where to start looking if it worked for root, but not other users, but when not even root has permissions, I have no idea. I have checked, and selinux is disabled. Thanks! --Jim -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Permissions problems with usb as root???
Yep, it shows up exactly like that for me: [r...@eme206-guest ~]# lsusb Bus 001 Device 001: ID : Bus 002 Device 004: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Bus 002 Device 001: ID : --Jim On Mon, Nov 30, 2009 at 2:01 PM, Pascal Brugier pbrug...@aeon-hq.net wrote: Hello, On Mon, 30 Nov 2009 13:47:13 -0800, Jim Kusznir jkusz...@gmail.com wrote: [r...@eme206-guest ~]# owfs u /mnt/owfs DEFAULT: ow_ds9490.c:DS9490_sub_open(552) Opened USB DS9490 adapter at 002/004. Could not open the USB adapter. Is there a problem with permissions? DEFAULT: ow_ds9490.c:DS9490_detect(310) Could not open the USB adapter. Is there a problem with permissions? DEFAULT: owlib.c:SetupInboundConnections(175) Cannot open USB adapter Can you see adapter with lsusb ? Here mine : undertow:~# lsusb [...] Bus 002 Device 002: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter [...] Pascal -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] ds2490u and usb 2.0 hub?
Hi all: We've been moving our owfs data collection servers over to sheeva plugs, and have been experiencing really good results...except for one minor problem. Everything works perfectly if the 2490 is plugged directly into the sheeva's single USB 2.0 port. However, we wanted to connect additional devices, so we put a usb 2.0 hub in, but things have not worked correctly thereafter. We passed the option uall to try and get owfs to detect the device, but we still get errors indicating it has not found an adapter. lsusb reports it fine, and in fact when I filter out the other stuff (usb hubs, etc), the lsusb -v output for the 2490 is identical in the working and non-working conditions. We were able to get it to work fine when we plugged it into a usb 1.1 hub that was plugged directly into the sheeva. It did NOT work if we plugged a 2.0 hub into the sheeva, then a 1.1 hub into the 2.0 hub, and the 2490 into the 1.1 hub. We want to use a 2.0 hub, as this is the sheeva's only usb port, and we would like the ability to plug in hard drives and the like. Any suggestions? --Jim -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] New release eta?
Works great, thanks for the release. I'll be submitting a version bump request to Gentoo today... (Sorry for the delay, we wanted to give it some time to ensure it has actually fixed the memory leak). --Jim On Mon, Jun 29, 2009 at 6:13 PM, Paul Alfillepaul.alfi...@gmail.com wrote: Uploaded. Working for you? Paul On Mon, Jun 29, 2009 at 12:52 PM, Jim Kusznirjkusz...@gmail.com wrote: Any update on this? We have one of our production systems crashing about every 2-3 days due to the memory leak in p21. --Jim On Mon, Jun 22, 2009 at 9:10 AM, Paul Alfillepaul.alfi...@gmail.com wrote: Releaseforge seems to be gagging on my attempts to put in the newest version. I think sourceforge has subtly changed things. I'll try when I can get near a development system to build. Paul Alfille On Sun, Jun 21, 2009 at 2:19 AM, Jaap Struykja...@minimumrisk.nl wrote: On 19-06-09 20:08, Jaap Struyk wrote: 2.7p22 Where do I find p22, sf is only showing me p21 (dispite the message that p22 is released)? -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ 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] New release eta?
Any update on this? We have one of our production systems crashing about every 2-3 days due to the memory leak in p21. --Jim On Mon, Jun 22, 2009 at 9:10 AM, Paul Alfillepaul.alfi...@gmail.com wrote: Releaseforge seems to be gagging on my attempts to put in the newest version. I think sourceforge has subtly changed things. I'll try when I can get near a development system to build. Paul Alfille On Sun, Jun 21, 2009 at 2:19 AM, Jaap Struykja...@minimumrisk.nl wrote: On 19-06-09 20:08, Jaap Struyk wrote: 2.7p22 Where do I find p22, sf is only showing me p21 (dispite the message that p22 is released)? -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org ___ 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] New release eta?
Hi all: I mentioned a bit back the memory leak issue, which other threads indicate has been found and fixed and incorporated into cvs. Due to the number of installations I have to update, I'd really appreciate a release rather than just a cvs/svn checkout. Is a release coming soon, or should I set about making packages myself and pushing those out? Thanks for all the hard work! Our project relies very heavily on owfs; its the core of our infrastructure here! --Jim -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Memory Leak in 2.7 p21
Hi all: We seem to be suffering from a rather large memory leak in 2.7 p21. We've seen this behaviour both with perl and python libraries. We have not been able to isolate a specific operation that causes the memory leak. Our code makes extensive use of the alarming function and queries the bus several times a second. Our bus consists of ~40 DS2406 and ~5 DS18B20. We've observed this behavior on two different installations, yet with an older (2.6p7) release, we have no such problem. Currently, the memory leak amounts to around 200-350MB in a 24-hr span, forcing us to restart our code every 24hrs to avoid crashing the box. Any suggestions/ideas/bugfixes? --Jim Lab Manager, WSU SmartHome and AI Lab -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2406 support Broke in 2.7p4?
Michael beat me to it... We don't use the 2406's for switching at all; its all about detecting. I did not try the p8 build, but the 2.7p4 definately has the problem, and 2.6p7 does not. I tried to build the 2.7p8, but the gentoo ebuild failed (something appears to have changed in the configure script), and I haven't had the time to figure out what it is yet. --Jim On Mon, Nov 10, 2008 at 12:22 AM, Michael Weber [EMAIL PROTECTED] wrote: Hi Paul, I will check the new version later this week. But the problem was not with switching (PIO), but with sensing (sensed). Our switches work fine, but the one unit where we sense the current of the lamp (also using ds2406) always reports sensed.A=1 (and sensed.B for that matter, but nothing connected on that side). Michael On Mon, Nov 10, 2008 at 2:36 AM, Paul Alfille [EMAIL PROTECTED] wrote: I just checked the current version with a Ohm-meter (continuity). I can set and unset PIO.A just fine. That's 2.7p8 I think the problem you refer to was fixed in March. Paul Alfille On Sun, Nov 9, 2008 at 6:14 PM, Michael Weber [EMAIL PROTECTED] wrote: Same here, I thought our circuit somehow broke. If I set the PIO high, the sensed goes down, but in the normal mode (PIO low) I always get 1 for sensed. Our version is 2.7p2 (and it worked when I installed this bit of hardware), but I can't remember what we had before. I found the old packages 2.6p8 on that computer, so that is probably what I used when I tried it out. Michael On Sun, Nov 9, 2008 at 11:16 PM, Jim Kusznir [EMAIL PROTECTED] wrote: Hi all: We finally rebuilt our very-aged server for our SmartApartment facility. As part of that upgrade, we upgraded from owfs2.6 to 2.7. Now, all of our DS2406-based devices are very broke. Symptoms include: reading sensed.A is ALWAYS 1 (although alarms seem to work correctly). This has been confirmed both through the fuse access and through owperl. Any thoughts/suggestions/ideas? (I'm going to go grab an older version of owfs and see if its still around). Thanks! --Jim - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] DS2406 support Broke in 2.7p4?
Hi all: We finally rebuilt our very-aged server for our SmartApartment facility. As part of that upgrade, we upgraded from owfs2.6 to 2.7. Now, all of our DS2406-based devices are very broke. Symptoms include: reading sensed.A is ALWAYS 1 (although alarms seem to work correctly). This has been confirmed both through the fuse access and through owperl. Any thoughts/suggestions/ideas? (I'm going to go grab an older version of owfs and see if its still around). Thanks! --Jim - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] OW Weather Station suggestions?
Hi all: We would like to add a weather station to our onewire network, and I am looking for suggestions and warnings about the various versions available. We have an existing OW system (utilizing OWFS, of course!) with ~70 sensors/devices already on the network. --Jim - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] temperature control
My apologies; this message got buried If I recall correctly, we tried setting the alarm thresholds on the 18B20's, then execute a syncronous convert, and all the temp sensors show up in alarm, even though their temperature hasn't changed. We tried to continue, in case it was just a temporary error, but it is not; every conversion results in all temperature sensors being in alarm mode. One of our students worked with this in more detail, I can get more info from him. We were also hoping to build a One-wire protocol debugger this summer and use it to address the alarming on both the 18B20 and the 2450 (which has other alarming problems). Thanks! --Jim On Mon, Apr 28, 2008 at 1:21 PM, Paul Alfille [EMAIL PROTECTED] wrote: On Mon, Apr 28, 2008 at 1:10 PM, Jim Kusznir [EMAIL PROTECTED] wrote: And currently the temperature alarming is very, very broke. This is the first report on this problem. Can you tell me more? Looking through the data sheet (http://datasheets.maxim-ic.com/en/ds/DS18B20.pdf) the alarm should be set whenever the temperature is out of range. No explicit alarm activation or clearing is given. So either owfs isn't setting the Temperature limits correctly, or it isn't searching the alarm register correctly. I'll try some tests, but if you have more information that would be helpful. Thanks, Paul Alfille - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] temperature control
And currently the temperature alarming is very, very broke. We have a situation where we have many temperature sensors sharing a onewire bus with many other sensors, for which we're already using alarming (total of ~40-70 sensors per bus; collection of 2406, 18B20, and 2450). We'd like to use alarming with all of them, unfortunately OWFS only properly alarms 2406's. We already have our scripts set up to do conversions on a regular interval and do alarm searches continuously So for the moment, we're implementing alarms in software for our temperature and A/D readings. This is taking its toll on the bus, though, and currently we only have ~5 of these devices on our largest bus. This summer, if I get the time, I was going to do some bus-level analysis of what OWFS is sending out to the chips to figure out how its misconfiguring them. Don't know if I'll have time yet, though. --Jim. On Wed, Apr 23, 2008 at 3:50 AM, Paul Alfille [EMAIL PROTECTED] wrote: For a couple of sensors, you may as well just monitor directly. You can do more sophisticated temperature control that way as well (rate of change, etc) You will have to do temperature measurements in any case. The alarms only make sense if you have many non-parasitic sensors and do a simultaneous conversion and then use alarm to find the sensors out of range. Paul Alfille On Wed, Apr 23, 2008 at 6:43 AM, Alessio Sangalli [EMAIL PROTECTED] wrote: Hi, in my embedded application I want to monitor a couple of temperature sensors and, when the value goes below a certain amount, switch on some heaters using a pin of the DS2413. Now: what would you use? A simple script that polls the sensors with owread and turn on/off the heaters with a owwrite in case, or something more advanced using alarms and so on? - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] ds9490, usb_bulk_read timeout on RH ES5
I am running OWFS on several CentOS5 boxes without any issues. I was using owfs from the various repos (I believe I was using rpmforge as my repo). That was working fine, except for DS2406 EPROM Write support, so I now run SVN releases. In either case, it is fine, although requires tweaking udev to work as a non-root user. If you test as root and it still doesn't work, you've got other issues. --Jim SmartHome Lab Director School of EECS, WSU On Sat, Feb 23, 2008 at 1:58 PM, Gregg Levine [EMAIL PROTECTED] wrote: On Sat, Feb 23, 2008 at 4:26 PM, Chris Maresca [EMAIL PROTECTED] wrote: Just as an FYI, Centos is a free/open version of the corresponding RedHat Enterprise version. So Centos 5 is RHES 5, etc. It's exactly the same, including updates and patches. The reality is that RHES is composed of almost entirely Open Source licensed code, so they can't really keep it private. Centos is that same code with the trademarks and logos ripped out. So is Oracle Linux and there are probably others. So, if you are wondering about RHES, you can just download and use Centos. The reason why companies use RHES instead of Centos is that they need a single point of contact and a vendor for problems. It's also much easier to deal with in their software acquisition process. HTH, Chris. Gregg C Levine wrote: Hello! Yes, Paul, you are indeed correct concerning the version names. That's the latest incarnation of what RH was giving away for free once. Now you get a box of the code on one DVD or many separate CDs, and they require the user to arrange for support via a paid-for contract. The big problem is that the work station release rarely works properly as regards sound on one particular family of systems. George check the release versions of udev on your working system versus anything available from RH. Complain to them. And here's the really funny part. Anything that makes sense in the Fedora Core project's efforts as they create release after release as a rolling beta ends up getting released as a new version of the Enterprise series. -- Gregg C Levine [EMAIL PROTECTED] The Force will be with you always. Obi-Wan Kenobi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: Friday, February 22, 2008 10:19 PM To: George Follis Cc: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] ds9490, usb_bulk_read timeout on RH ES5 Hello George, I forwarded your note to the owfs-developers maillist. There are udev updates from Sven Geggus and Jan Kandziora summarized at http://owfs.org/index.php?page=udev-and-usb. I'm not familiar with ES[3-5] and google was too non-specific when I first saw your query. RedHat versions? Paul Alfille On Fri, Feb 22, 2008 at 3:56 PM, George Follis [EMAIL PROTECTED] wrote: Paul, your owfs project seems to be the most current code out there that attempts to access the Dallas Semiconductor devices. I'm getting desperate ... I have code from Dallas Semi that worked properly on ES3 / ES4 Red Hat now when compiled on ES5 it fails during a 'Get Status' call with a timeout error. The first request to DS was of no help - they simply replied that they were not aware of anyone having issues on ES5. If some one could point me in the proper direction - hopefully one that I didn't know existed. I think I could get this going. I discovered the udev changes and created the need scripts to change the access mode of the device. Anything else? Thanks. GRFollis Hello! Correct Chris. However Paul was curious about the term, and naturally I decided to explain that. In fact more shops use Centos instead of RHEL for non-specific jobs, those that they aren't worried about. In fact my distribution Slackware, is also getting ahead more then most people think. But that is an argument for a different place and time. -- Gregg C Levine [EMAIL PROTECTED] This signature was once found posting rude messages in English in the Moscow subway. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
Re: [Owfs-developers] Alarming in DS18B20 and DS2450 broke?
As far as we can tell, yes. We read the temp from the cached tree, issue a simultanous, and read from the cached tree again, and the temp is different. We don't really have a sure-fire way of knowing that its actually doing a conversion with the simultanous command, as its possible that its converting again when we read. We suspect the same is happening with the A2D, too. --Jim On Jan 16, 2008 6:03 PM, Paul Alfille [EMAIL PROTECTED] wrote: Does the simultaneous at least trigger new temperature reads? Paul Alfille On Jan 16, 2008 2:14 PM, Jim Kusznir [EMAIL PROTECTED] wrote: Hi all: Our group is having a lot of problems with alarming on the DS18B20 (temp sensors) and DS2450 (4-ch A to D). We are sucessfully using alarming in the DS2406. We set the alarm thresholds, then issue a symultanous convert, but then all chips alarm, even if they shouldn't have given their range. The datasheets of both claim alarm support, although the OWFS man pages are more questionable about alarm support (the 2450 contradicts itself). Has anyone else tried this? Thanks! --Jim - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Alarming in DS18B20 and DS2450 broke?
As we're doing other testing in the lab, we're finding some more problems with DS2450 alarming. Sending the simultanous seems to lock the bus for a whileBy that, we mean it gets really sluggish. It almost seems we're waiting for 5-25 seconds for it to finish conversion, and during that time, we can't talk to anything else on the bus. Its possible we haven't set it up correctly, as the owfs man page for the device isn't very clear when it comes to alarming. I'm guessing we're the first ones to really use this feature. To us, the A2D alarming is actually more important than alarming for the temperature at the moment. We're having to fail over to just polling and logging 1-sec interval readings, which will add a fair bit to our database bloat Thanks for all the hard work you guys have already put into the projectWe wouldn't even be where we are without OWFS! --Jim On Jan 17, 2008 11:15 AM, Jim Kusznir [EMAIL PROTECTED] wrote: As far as we can tell, yes. We read the temp from the cached tree, issue a simultanous, and read from the cached tree again, and the temp is different. We don't really have a sure-fire way of knowing that its actually doing a conversion with the simultanous command, as its possible that its converting again when we read. We suspect the same is happening with the A2D, too. --Jim On Jan 16, 2008 6:03 PM, Paul Alfille [EMAIL PROTECTED] wrote: Does the simultaneous at least trigger new temperature reads? Paul Alfille On Jan 16, 2008 2:14 PM, Jim Kusznir [EMAIL PROTECTED] wrote: Hi all: Our group is having a lot of problems with alarming on the DS18B20 (temp sensors) and DS2450 (4-ch A to D). We are sucessfully using alarming in the DS2406. We set the alarm thresholds, then issue a symultanous convert, but then all chips alarm, even if they shouldn't have given their range. The datasheets of both claim alarm support, although the OWFS man pages are more questionable about alarm support (the 2450 contradicts itself). Has anyone else tried this? Thanks! --Jim - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Alarming in DS18B20 and DS2450 broke?
Hi all: Our group is having a lot of problems with alarming on the DS18B20 (temp sensors) and DS2450 (4-ch A to D). We are sucessfully using alarming in the DS2406. We set the alarm thresholds, then issue a symultanous convert, but then all chips alarm, even if they shouldn't have given their range. The datasheets of both claim alarm support, although the OWFS man pages are more questionable about alarm support (the 2450 contradicts itself). Has anyone else tried this? Thanks! --Jim - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Hydroelectric Powerplant
We have been facing some of the same problems here with our SmartHome project. OneWire devices (currently primarily the DS2406, DS18B20, and DS2450) have been very useful and form the backbone of our sensor network. However, we're running into issues where we need local intelligence; for example, running a capicitave pressure sensor or a complete thermostat with analog voltage output, as well as a handful of other applications. We've been debating in our group how best to go about it, and I was thinking emulating a 1wire memory device might be best, but a custom device in OWFS could possibly be better. We plan to put some manpower on writing code for the ATMEL cpu's for this purpose, but haven't quite gotten there yet. I was wondering/fearing how hard it would be to do the slave-side 1-wire code, as I haven't found any mention of it yet. I'm really interested in this aspect, and am interested in working with anyone who is interested. Thanks again for such a wonderful project that has saved us tons of work!!! --Jim On Jan 3, 2008 9:29 AM, Paul Alfille [EMAIL PROTECTED] wrote: On website at http://owfs.org/index.php?page=hydroelectric-plant (I've included my responses). -- Forwarded message -- On Dec 13, 2007 3:44 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I have an old and small hydroelectric powerplant ( http://sundsvik.dnsalias.org/) run on a shoestring budget. It is remotely monitored and controlled by a system mainly based on 1-wire devices using OWFS. Thankyou for a very nice piece of software. The 1-wire devices have their limitations, they are for instance not very good at measuring precise intervals and totals and other things. Therefore I would like to design a flexible device based on a microcotroller for instance a PIC that can draw on the advantages of the 1-wire protocol and extend the capabilities of the devices offered by Maxim. The device to emulate that first comes to my mind is the DS18S20 which has a rather simple architecture with a read/write scratchpad memory area which is ideal for my purposes. My questions to you are: 1) Commands 0xBE and 0x4E: Can I in any simple way read and write whole or parts of the scratchpad memory with OWFS? Is there a one-to-one relationship between the reported temperature and the content of the temperature registers? Well, we read scratchpad internally, and it would be easy to make it externally visible. I don't currently, because it might overwhelm new users, and changing the scratchpad would make other aspects inaccurate (like temperature resolution). 2) Are you aware of any project for emulating the Dallas 1-wire devices? I hate to reinvent the wheel. Louis Swart's LCD uses a PIC to emulate a 1-wire device. Maxim in general is protective of the 1-wire device technology (for the slaves, the masters are fair game). A. Have you looked at the DS27xx chips? They have temperature, current, accumulators, timers, voltages, even a bit of memory. Pretty cheap. Look specifically at the DS2760 DS2751 DS2770 and DS2780 B. There is no reason to blindly emulate the DS1820 -- we can create an entry to your chip using the command codes you like. It has to speak 1-wire (reset, selection, etc) but the actual protocol needn't be constrained. C. If you really want to be different, we can make a unique adapter and chips that don't have to talk true 1-wire between them. We can work to make it fall generally in the same scheme. D. There might be other resources (smart people) if you ask this question ion the owfs-developer's list. E. Although Dallas is phasing them out, the DS2404 has dual inputs -- 1-wire and 3-wire and can serve as a bridge to the PIC. Thanks in advance Håkan Elmqvist - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Writing to DS2406
Greg: Yes, we did the programming with a modified DS9490R. We had to do two things to make it program-capable: Add an external VPP to the correct PIN of the controller chip (had to lift the pin from the pad it was on on the circuit board, attach a wire, etc) as well as ground; and had to remove a chip containing a zener diode restricting the onewire output voltage to no more than 8V. I cited that chip in a prior message. It may be noteworthy that in this configuration, the programming pulse on the onewire is 10.5V instead of 12, but it does seem sufficient to program 2406+ (only device on bus). We also have a pair of passive DS9097E's (DB25 passive interface with external 12V input). I was able to program using Dallas' windows software, but not with OWFS. With Dallas' software, I noticed I could only program a byte or two at a time. If I changed several bytes and tried to write, only the first byte or two actually got burned. In nearly all cases, the software reported a failure to burn. When I tried using this device with OWFS, it appeared that OWFS detected it as a related device without programming capability, as any attempts to write failed the same way the DS9490R did initially (throwing a write error at the filesystem level). Based on the problems I had with this interface in the windows world with Dallas' software and my perceived uncommonness of the interface, I didn't think it was worth pursuing programming with it. If you're interested, I can test though. Oh, as a side note: I have not been able to make these devices work with a USB-RS232 adapter; it seems to require an internal serial port. As to our application: We're making sensors for a SmartHome sensor network. Currently, many of our sensors are based on the DS2406, and we'd like to have a way for the device to identify what type of sensor it is so our software knows how to talk and use it. So we're using the PROM to store sensor family and version information. We're currently using the OWperl interfaces in our software and OWFS (fuse) for testing/debugging/experimenting by hand. --Jim On 10/1/07, Gregg C Levine [EMAIL PROTECTED] wrote: Hello! I believe I am missing something here. Jim you, and your staff (I presume you have one because of the EE and his scope.) did all of that with a DS9490R and successful. What about using the passive version of the DS9097? (And of course I do not recall the full number for this gizmo, just the specific name for it.) Of course this presupposes that you do have a legacy serial port available, and that one of the DS9097s for such a function is indeed available. I can see where installing specific information into a DS2406 or the Unique Ware devices for a specific project. And then including routines in your code to read them back and including functions for accessing them via both forms are also needful and necessary. But then again this is just me. -- Gregg C Levine [EMAIL PROTECTED] The Force will be with you. Always. Obi-Wan Kenobi - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Writing to DS2406
For some reason, I thought the DS2505's didn't have PROM. We have a few samples of those lying around; I'll give a test on those as well. --Jim On 10/2/07, Paul Alfille [EMAIL PROTECTED] wrote: On 10/1/07, Jim Kusznir [EMAIL PROTECTED] wrote: We actually found that the DS9490R includes a zener diode (in package DS9503P) that limited the output. We removed and properly bypassed it, and now get programming pulses to 10.5V, which appears sufficient to burn the prom. We are sucessfully burning the eprom in the 2506's! This is great news! Thanks for testing and confirming that EPROM programming can work. There are three other devices that use EPROM. (DS2502 DS2505 DS2506) I'll make sure they get updated as well. Paul Alfille - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Writing to DS2406
I got an EE to bring over an OScope, and we may have found out some more info. First, we have verified that it is sending programming pulses. Unfortunately, these pulses are only 8.5V for 480microseconds. We've viewed the +12 supply on VPP, and verifed it is 12V. From my understanding, VPP needs to be 12, and that the votage is supposed to be passed through from the VPP pin. Is this correct? Is there any setting that can effect this, or does this sound like a dead chip? Thanks! --Jim On 10/1/07, Jim Kusznir [EMAIL PROTECTED] wrote: I think we're getting close. It appeared to work from the command prompt, but when I read memory, nothing has been changed. I also noticed some owfs paths coming out in the memory readback, so there might be a bug there elsewhere, too: [EMAIL PROTECTED] 12.58863600 # echo -n A Long Test Into An OWFS Device. Not too long though. memory [EMAIL PROTECTED] 12.58863600 # cat memory ���y~ [EMAIL PROTECTED]@A��* [EMAIL PROTECTED] @A`�Ҫ�* @[EMAIL PROTECTED]@4` �Ҫ�*训��* @AM*h*3600/memory ����*READ path=/uncached/12.58863600/memory size=4096 offset=0 4���8 @���8 @A4([EMAIL PROTECTED] path=/uncached/12.58863600/pages/page.0 @A��� @[EMAIL PROTECTED]@[EMAIL PROTECTED] @A� @A @A 0 @A @A @[EMAIL PROTECTED]@[EMAIL PROTECTED]@A4*00� @[EMAIL PROTECTED]@A4*l���800 @[EMAIL PROTECTED]@Ax,@Aì°(r)ªª* 6 8 @Aþ£ë8 [EMAIL PROTECTED]@[EMAIL PROTECTED] @[EMAIL PROTECTED] �Ҫ�** ��*��*�*��*���*���* X�6 �Ѫ�*��Ѫ�*@@[EMAIL PROTECTED] [EMAIL PROTECTED];���p��* [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@֪�*P�l @[EMAIL PROTECTED]@[EMAIL PROTECTED]@A�! ��r�� @[EMAIL PROTECTED]@eme206-05 12.58863600 # here's the debug trace: Debug Trace --- unique: 103, opcode: LOOKUP (1), nodeid: 4, insize: 47 LOOKUP /uncached/12.58863600/memory CALL: FSTAT path=/uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/uncached/12.58863600/memory DEBUG: ParsedName_destroy /uncached/12.58863600/memory NODEID: 5 unique: 103, error: 0 (Success), outsize: 136 unique: 104, opcode: SETATTR (4), nodeid: 5, insize: 128 CALL: TRUNCATE path=/uncached/12.58863600/memory CALL: FSTAT path=/uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/uncached/12.58863600/memory DEBUG: ParsedName_destroy /uncached/12.58863600/memory unique: 104, error: 0 (Success), outsize: 112 unique: 105, opcode: OPEN (14), nodeid: 5, insize: 48 CALL: OPEN path=/uncached/12.58863600/memory unique: 105, error: 0 (Success), outsize: 32 OPEN[0] flags: 0x8001 /uncached/12.58863600/memory unique: 106, opcode: WRITE (16), nodeid: 5, insize: 118 WRITE[0] 54 bytes to 0 CALL: WRITE path=/uncached/12.58863600/memory size=54 offset=0 DEBUG: FS_OWQ_create of /uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache OWQ OneWireQuery structure of /uncached/12.58863600/memory OneWireQuery size=54 offset=0, extension=0 Byte buffer OneWireQuery buffer, length=54 -- 41 20 4C 6F 6E 67 20 54 65 73 74 20 49 6E 74 6F -- 20 41 6E 20 4F 57 46 53 20 44 65 76 69 63 65 2E -- 20 20 4E 6F 74 20 74 6F 6F 20 6C 6F 6E 67 20 74 -- 68 6F 75 67 68 2E A Long Test Into An OWFS Device. Not too long though. OneWireQuery I=54 U=54 F=2.66795E-322 Y=54 D=Wed Dec 31 16:00:54 1969 --- OneWireQuery done DEBUG: Selecting a path (and device) path=/uncached/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction CRC16 = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction end = 0 DEBUG: Wrote DS2406 byte 0 -- no errors DEBUG: Selecting a path (and device) path=/uncached/12.58863600/memory SN=12 58 86 36 00
Re: [Owfs-developers] Writing to DS2406
Thanks for the help! We actually found that the DS9490R includes a zener diode (in package DS9503P) that limited the output. We removed and properly bypassed it, and now get programming pulses to 10.5V, which appears sufficient to burn the prom. We are sucessfully burning the eprom in the 2506's! (Our power supply was a PC power supply, and we watched it on the OScope, and verified that it was not moving at all. The voltage limitation was internal to the module. Thanks for all the help!! --Jim On 10/1/07, njh [EMAIL PROTECTED] wrote: This is an obvious thing, but have you tried putting a capacitor right on the power supply leads to the chip? 0.1uF bypassing cap should do the trick I think? njh On Mon, 1 Oct 2007, Jim Kusznir wrote: I got an EE to bring over an OScope, and we may have found out some more info. First, we have verified that it is sending programming pulses. Unfortunately, these pulses are only 8.5V for 480microseconds. We've viewed the +12 supply on VPP, and verifed it is 12V. From my understanding, VPP needs to be 12, and that the votage is supposed to be passed through from the VPP pin. Is this correct? Is there any setting that can effect this, or does this sound like a dead chip? Thanks! --Jim On 10/1/07, Jim Kusznir [EMAIL PROTECTED] wrote: I think we're getting close. It appeared to work from the command prompt, but when I read memory, nothing has been changed. I also noticed some owfs paths coming out in the memory readback, so there might be a bug there elsewhere, too: [EMAIL PROTECTED] 12.58863600 # echo -n A Long Test Into An OWFS Device. Not too long though. memory [EMAIL PROTECTED] 12.58863600 # cat memory ÿÿy~ [EMAIL PROTECTED] @Aÿÿ ÿÿ* [EMAIL PROTECTED] @A`ÿÿ* @[EMAIL PROTECTED]@4` ÿÿ*ÿÿ* @AM*h*3600/memory ÿÿ ÿÿ*READ path=/uncached/12.58863600/memory size=4096 offset=0 4 ÿÿ8 @ÿÿ8 @A4 ([EMAIL PROTECTED] ÿÿ*RELEASE path=/uncached/12.58863600/pages/page.0 @Aÿÿ @A*@ [EMAIL PROTECTED]@ÿÿ @Aÿÿ @A@A 0 @A @A @[EMAIL PROTECTED]@ÿÿ *`ÿÿ*4*@ @A4*00ÿÿ @[EMAIL PROTECTED]@A4*lÿÿ800 @A[cÿÿ*68 *`ÿÿ*ÿÿ @[EMAIL PROTECTED],@Aì°(r)ªª* 6 8 @Aþ £ë8 [EMAIL PROTECTED] *ÿÿ * [EMAIL PROTECTED] *ÿÿ *ÿÿ 8ÿÿ [EMAIL PROTECTED] * ÿÿ*h*h* @[EMAIL PROTECTED] ÿÿ* * * * ÿÿ** ÿÿ *ÿÿ * Xÿÿ6 ÿÿ**@@ 0 * ll *ÿÿl4*ÿÿ @Ap * S G * #* P @A ;ÿÿp * ÿÿDÿÿ @0ÿÿlÿÿ @AP @AÿÿN*ÿÿ @AP @[EMAIL PROTECTED] @Aÿÿa`ÿÿ8@ @A@ @Aÿÿ! r @AP @[EMAIL PROTECTED] 12.58863600 # here's the debug trace: Debug Trace --- unique: 103, opcode: LOOKUP (1), nodeid: 4, insize: 47 LOOKUP /uncached/12.58863600/memory CALL: FSTAT path=/uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/uncached/12.58863600/memory DEBUG: ParsedName_destroy /uncached/12.58863600/memory NODEID: 5 unique: 103, error: 0 (Success), outsize: 136 unique: 104, opcode: SETATTR (4), nodeid: 5, insize: 128 CALL: TRUNCATE path=/uncached/12.58863600/memory CALL: FSTAT path=/uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/uncached/12.58863600/memory DEBUG: ParsedName_destroy /uncached/12.58863600/memory unique: 104, error: 0 (Success), outsize: 112 unique: 105, opcode: OPEN (14), nodeid: 5, insize: 48 CALL: OPEN path=/uncached/12.58863600/memory unique: 105, error: 0 (Success), outsize: 32 OPEN[0] flags: 0x8001 /uncached/12.58863600/memory unique: 106, opcode: WRITE (16), nodeid: 5, insize: 118 WRITE[0] 54 bytes to 0 CALL: WRITE path=/uncached/12.58863600/memory size=54 offset=0 DEBUG: FS_OWQ_create of /uncached/12.58863600/memory CALL: PARSENAME path=[/uncached/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18
Re: [Owfs-developers] Writing to DS2406
(and program pulse can get reset at same time). The code is now simpler, works for the standard case (reading data and temperatures) and might wirk for program pulses. Paul Alfille On 9/27/07, Jim Kusznir [EMAIL PROTECTED] wrote: Any news on this? My best reading of the output was that owfs didn't actually initiate the programming pulse. --Jim On 9/25/07, Jim Kusznir [EMAIL PROTECTED] wrote: Hi: Here's the debug dump from an attempt at: echo -n Testing memory -- unique: 103, opcode: LOOKUP (1), nodeid: 2, insize: 47 LOOKUP /12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory NODEID: 3 unique: 103, error: 0 (Success), outsize: 136 unique: 104, opcode: SETATTR (4), nodeid: 3, insize: 128 CALL: TRUNCATE path=/12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 104, error: 0 (Success), outsize: 112 unique: 105, opcode: OPEN (14), nodeid: 3, insize: 48 CALL: OPEN path=/12.58863600/memory unique: 105, error: 0 (Success), outsize: 32 OPEN[0] flags: 0x8001 /12.58863600/memory unique: 106, opcode: WRITE (16), nodeid: 3, insize: 71 WRITE[0] 7 bytes to 0 CALL: WRITE path=/12.58863600/memory size=7 offset=0 DEBUG: FS_OWQ_create of /12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache OWQ OneWireQuery structure of /12.58863600/memory OneWireQuery size=7 offset=0, extension=0 Byte buffer OneWireQuery buffer, length=7 -- 54 65 73 74 69 6E 67 Testing OneWireQuery I=7 U=7 F=3.45846E-323 Y=7 D=Wed Dec 31 16:00:07 1969 --- OneWireQuery done DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: FS_OWQ_destroy of /12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 106, error: -22 (Invalid argument), outsize: 16 unique: 107, opcode: RELEASE (18), nodeid: 3, insize: 64 RELEASE[0] flags: 0x8001 CALL: RELEASE path=/12.58863600/memory unique: 107, error: 0 (Success), outsize: 16 Thanks! --Jim On 9/25/07, Paul Alfille [EMAIL PROTECTED] wrote: Have you tried running owfs with debugging enabled? owfs --error_level=9 --foreground -m mountpoint -u
Re: [Owfs-developers] Writing to DS2406
Any news on this? My best reading of the output was that owfs didn't actually initiate the programming pulse. --Jim On 9/25/07, Jim Kusznir [EMAIL PROTECTED] wrote: Hi: Here's the debug dump from an attempt at: echo -n Testing memory -- unique: 103, opcode: LOOKUP (1), nodeid: 2, insize: 47 LOOKUP /12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory NODEID: 3 unique: 103, error: 0 (Success), outsize: 136 unique: 104, opcode: SETATTR (4), nodeid: 3, insize: 128 CALL: TRUNCATE path=/12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 104, error: 0 (Success), outsize: 112 unique: 105, opcode: OPEN (14), nodeid: 3, insize: 48 CALL: OPEN path=/12.58863600/memory unique: 105, error: 0 (Success), outsize: 32 OPEN[0] flags: 0x8001 /12.58863600/memory unique: 106, opcode: WRITE (16), nodeid: 3, insize: 71 WRITE[0] 7 bytes to 0 CALL: WRITE path=/12.58863600/memory size=7 offset=0 DEBUG: FS_OWQ_create of /12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache OWQ OneWireQuery structure of /12.58863600/memory OneWireQuery size=7 offset=0, extension=0 Byte buffer OneWireQuery buffer, length=7 -- 54 65 73 74 69 6E 67 Testing OneWireQuery I=7 U=7 F=3.45846E-323 Y=7 D=Wed Dec 31 16:00:07 1969 --- OneWireQuery done DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: FS_OWQ_destroy of /12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 106, error: -22 (Invalid argument), outsize: 16 unique: 107, opcode: RELEASE (18), nodeid: 3, insize: 64 RELEASE[0] flags: 0x8001 CALL: RELEASE path=/12.58863600/memory unique: 107, error: 0 (Success), outsize: 16 Thanks! --Jim On 9/25/07, Paul Alfille [EMAIL PROTECTED] wrote: Have you tried running owfs with debugging enabled? owfs --error_level=9 --foreground -m mountpoint -u That will give you lots of output. I don't think the DS2490 can tell if it has 12V available. It oes need the 12 Programing explicitly enabled (I think I did that), and the duration set (default 512 usec, the datasheet says 480usec, I use 480 but perhaps the default is more appropriate under real-world conditions). Can you post your debugging output? Paul Alfille On 9/24/07, Jim Kusznir [EMAIL PROTECTED] wrote: Hi Paul: Thanks
Re: [Owfs-developers] Writing to DS2406
Hi: Here's the debug dump from an attempt at: echo -n Testing memory -- unique: 103, opcode: LOOKUP (1), nodeid: 2, insize: 47 LOOKUP /12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory NODEID: 3 unique: 103, error: 0 (Success), outsize: 136 unique: 104, opcode: SETATTR (4), nodeid: 3, insize: 128 CALL: TRUNCATE path=/12.58863600/memory CALL: FSTAT path=/12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache CALL: ATTRIBUTES path=/12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 104, error: 0 (Success), outsize: 112 unique: 105, opcode: OPEN (14), nodeid: 3, insize: 48 CALL: OPEN path=/12.58863600/memory unique: 105, error: 0 (Success), outsize: 32 OPEN[0] flags: 0x8001 /12.58863600/memory unique: 106, opcode: WRITE (16), nodeid: 3, insize: 71 WRITE[0] 7 bytes to 0 CALL: WRITE path=/12.58863600/memory size=7 offset=0 DEBUG: FS_OWQ_create of /12.58863600/memory CALL: PARSENAME path=[/12.58863600/memory] DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache OWQ OneWireQuery structure of /12.58863600/memory OneWireQuery size=7 offset=0, extension=0 Byte buffer OneWireQuery buffer, length=7 -- 54 65 73 74 69 6E 67 Testing OneWireQuery I=7 U=7 F=3.45846E-323 Y=7 D=Wed Dec 31 16:00:07 1969 --- OneWireQuery done DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18 DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4 DEBUG: value found in cache DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: Selecting a path (and device) path=/12.58863600/memory SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction select = 0 DEBUG: Transaction send = 0 DEBUG: Transaction readin = 0 DATA: DS9490_level 2 (old = 0) DATA: DS9490_level 0 (old = 2) DATA: DS9490_HaltPulse DATA: DS9490_HaltPulse: loop DATA: DS9490_HaltPulse: ok DEBUG: Transaction program pulse = 0 DEBUG: Transaction readin = 0 DEBUG: Transaction end = 0 DEBUG: FS_OWQ_destroy of /12.58863600/memory DEBUG: ParsedName_destroy /12.58863600/memory unique: 106, error: -22 (Invalid argument), outsize: 16 unique: 107, opcode: RELEASE (18), nodeid: 3, insize: 64 RELEASE[0] flags: 0x8001 CALL: RELEASE path=/12.58863600/memory unique: 107, error: 0 (Success), outsize: 16 Thanks! --Jim On 9/25/07, Paul Alfille [EMAIL PROTECTED] wrote: Have you tried running owfs with debugging enabled? owfs --error_level=9 --foreground -m mountpoint -u That will give you lots of output. I don't think the DS2490 can tell if it has 12V available. It oes need the 12 Programing explicitly enabled (I think I did that), and the duration set (default 512 usec, the datasheet says 480usec, I use 480 but perhaps the default is more appropriate under real-world conditions). Can you post your debugging output? Paul Alfille On 9/24/07, Jim Kusznir [EMAIL PROTECTED] wrote: Hi Paul: Thanks for the fast responce! I pulled in the CVS version just about 20 minutes ago using: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/owfs co owfs (I couldn't figure out how to tell what revision I'm at...) I'm seeing the same behavior I was as before: [EMAIL PROTECTED] pages]# echo -n
Re: [Owfs-developers] Writing to DS2406
Hi Paul: Thanks for the fast responce! I pulled in the CVS version just about 20 minutes ago using: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/owfs co owfs (I couldn't figure out how to tell what revision I'm at...) I'm seeing the same behavior I was as before: [EMAIL PROTECTED] pages]# echo -n This is a test page.1 -bash: echo: write error: Invalid argument [EMAIL PROTECTED] pages]# cd .. [EMAIL PROTECTED] 12.58863600]# echo -n testing memory -bash: echo: write error: Invalid argument Unfortunately, I haven't found any debugging output, espicially wether or not it detected the 12V available. If you could point me toward how to get the debugging output, I'll get more information (and make sure owfs sees my hardware as I think it should :) ) Thanks! --Jim On 9/22/07, Paul Alfille [EMAIL PROTECTED] wrote: If you're willing to try the CVS version, I put in support. Untested, but should follow the datasheet closely. Paul Alfille On 9/21/07, Paul Alfille [EMAIL PROTECTED] wrote: Hi Jim, I don't think 12V eprom program has ever been tested. As you notice, it's hard to find an appropriate adapter. It looks only like the DS2406, DS2502 and DS2505 need the program pulse (480usec). The DS2490 datasheet does say that it supports 12V programming. http://datasheets.maxim-ic.com/en/ds/DS2490.pdf Only not in the DS9490 device. I'll try to add support and get you to test. Paul Alfille On 9/21/07, Jim Kusznir [EMAIL PROTECTED] wrote: Hi all: I've been trying for about a week to write to the DS2406's EPROM using OWFS. I realize that the bus master needs to have +12 VPP, and have been working on this. I currently am trying to write using: echo test memory from within my owfs chip's directory. I get an error message from echo. I have two bus masters: DS9490R (USB) and DS9097E (passive). The 9097E has the connecter for +12, which I've put on it. Unfortunately, it looks like OWFS doesn't see it as the E version, but a version which does not have +12 which I believe is responsible for it not allowing me to write. I have also opened up one of my 9094R's, lifted the VPP pin and applied +12 externally. Unfortunately, I am still unable to write through OWFS. In all my endevors to write so far, the only sucess I've had is to bring up my 9097E in windows (on a hardware serial port -- I found usb serial adaptors don't work), and writing one nibble at a time (more that that fail). Based on reading the data sheet for the DS2490 (the chip the 9094R is based on), it sounds like it may require a register or other setting to be set to enable programming. I looked and looked through owfs and read every piece of documentation I could find, but could not find any information on setting the programming enabled info, or even retreaving information on wether programming voltage is detected. So, my questions: 1) how do I write to EPROMS requiring the +12VPP? 2) What adaptors have others sucessfully used? 3) Can I configure an adaptor such as the 9094R as write-enabled after I physically modified it to include +12 VPP? Do I need to? Any other relevent comments? Thanks! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
