Re: [Owfs-developers] Bug in DS2409 code, patch included
Am Donnerstag, 14. Dezember 2006 23:52 schrieb Jan Kandziora: > Am Donnerstag, 14. Dezember 2006 22:29 schrieb Paul Alfille: > > Jan, > > > > Thank you very much! > > I think I found another occurrence of this bug. As the discharge lines > command is not really needed for branch turnoff, I left it out. > Ahhh, forget the previous posting... 0xCC is required there. Kind regards Jan -- Linux - It's now safe to turn on your computer. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Donnerstag, 14. Dezember 2006 12:33 schrieb Jan Kandziora: > > But from the problems we encounter I think the following is done when > reading "1F./simultaneous/single" > > Byte 0 0x55 ROM Command (Match ROM) > Byte 1 0x1F Family Code (DS2409) > Byte 2..7 ID > Byte 8 CRC8 > Byte 9 0xCC Control Command (Smart-On Main) > Byte 10 0xFF Reset Timing for main branch > Byte 11 0xFF Reset Timing for main branch > > --- Additional reset for whole bus (so the previously selected DS2409 > branch AND the backbone are selected) > > Byte +0 0x33 ROM Command (valid only for previously reset main branch) > Byte +1 Garbage (wired AND of family codes) > Byte +2..+7 Garbage (wired AND of IDs) > Byte +8 Garbage (wired AND of CRC8s) > Paul, it's like I've written above. Each TRXN_START triggers "BUS_select", which, in lines 90 and 156 of module/owlib/src/c/ow_select.c issue at least one "BUS_reset". That way, we really shot our own foot, as the Smart-On function cannot be used properly. It's just the same result as Direct-On. I'm not sure what to do. I tested a little with BUS_send_data and BUS_readin_data in the DS2409 code, but I couldn't get Smart-On working at all. The DS2409 doesn't seem to respond to the "reset stimulus" byte by issuing a reset on its main output. Kind regards Jan -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Freitag, 15. Dezember 2006 03:05 schrieb Paul Alfille: > Jan, > > The DS2409 code has been quite a chore to implement. OWFS has the most > flexible of any implementation I know -- support for unlimitted branching, > interleaved bus usage, and lazy bus changes. I'll be interested in any > improvements you can make, but it isn't easy. > Before I'll rumble through that, I'd like to add another node to the DS2409 chip: "clearevent" just issues a 0x66 "disconnect all lines" control command and clears the DS2409s event flags. I know "discharge" does this, too, but I don't like the 100ms time needed there. I'll plan to use this "clearevent" node with my DS2409 driven locks. The event is triggered on connection of an iButton to the lock. Then one does only have to scan the "alarm" directory of the backbone to check for new keys. May I check in the change directly or should I send a patch? Kind regards Jan -- A truly stable environment would be a concrete basement with no windows! Computers are no different. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Freitag, 15. Dezember 2006 03:05 schrieb Paul Alfille:
> Jan,
>
> The DS2409 code has been quite a chore to implement. OWFS has the most
> flexible of any implementation I know -- support for unlimitted branching,
> interleaved bus usage, and lazy bus changes. I'll be interested in any
> improvements you can make, but it isn't easy.
>
I made some progress in catching the "smart-on" problem -- a "single"
implementation in the DS2409 code branch just works as expected, only the
iButton connected to the main branch of the DS2409 responds to a 0x33 "read
ROM" command. Example code is attached.
The needed changes in the BUS_select code could be quite simple, I think. Just
the final BUS_reset in ow_select.c, line 90 has to be replaced by a more
sophisticated reset method. Pseudocode:
iflast_branch_component(_path_) == "")
|| last_branch_component(_path_) == "bus.n")
{ BUS_reset(); }
else
{
Bus_select(last_branch_ds2409(_path_);
if last_branch_component(_path_) == "main")
{ DS2409_Smart_On_Main(_path_) }
else
{ DS2409_Smart_On_Aux(_path_) }
}
I'm digging deeper into the path functions next week, as the last_branch...
pseudofunctions may be the toughest part to implement.
Kind regards
Jan
--
Windows ist Kommunismus: Es hört sich gut an, funktioniert aber nicht.
/*
$Id: ow_2409.c,v 1.15 2006/06/16 22:15:19 alfille Exp $
OWFS -- One-Wire filesystem
OWHTTPD -- One-Wire Web Server
Written 2003 Paul H Alfille
email: [EMAIL PROTECTED]
Released under the GPL
See the header file: ow.h for full attribution
1wire/iButton system from Dallas Semiconductor
*/
/* General Device File format:
This device file corresponds to a specific 1wire/iButton chip type
( or a closely related family of chips )
The connection to the larger program is through the "device" data structure,
which must be declared in the acompanying header file.
The device structure holds the
family code,
name,
number of properties,
list of property structures, called "filetype".
Each filetype structure holds the
name,
estimated length (in bytes),
aggregate structure pointer,
data format,
read function,
write funtion,
generic data pointer
The aggregate structure, is present for properties that several members
(e.g. pages of memory or entries in a temperature log. It holds:
number of elements
whether the members are lettered or numbered
whether the elements are stored together and split, or separately and joined
*/
#include
#include "owfs_config.h"
#include "ow_2409.h"
/* --- Prototypes --- */
/* DS2409 switch */
yWRITE_FUNCTION( FS_discharge ) ;
uREAD_FUNCTION( FS_r_control ) ;
uWRITE_FUNCTION( FS_w_control ) ;
uREAD_FUNCTION( FS_r_sensed ) ;
uREAD_FUNCTION( FS_r_branch ) ;
uREAD_FUNCTION( FS_r_event ) ;
yWRITE_FUNCTION( FS_clearevent ) ;
aREAD_FUNCTION( FS_r_single ) ;
/* --- Structures --- */
struct aggregate A2409 = { 2, ag_numbers, ag_aggregate, } ;
struct filetype DS2409[] = {
F_STANDARD ,
{"discharge" , 1, NULL,ft_yesno , fc_stable , {v:NULL}, {y:FS_discharge} , {v:NULL}, } ,
{"control" , 1, NULL, ft_unsigned , fc_stable , {u:FS_r_control}, {u:FS_w_control} , {v:NULL}, } ,
{"sensed", 1,&A2409, ft_bitfield , fc_volatile, {u:FS_r_sensed} , {v:NULL} , {v:NULL}, } ,
{"branch", 1,&A2409, ft_bitfield , fc_volatile, {u:FS_r_branch} , {v:NULL} , {v:NULL}, } ,
{"event" , 1,&A2409, ft_bitfield , fc_volatile, {u:FS_r_event} , {v:NULL} , {v:NULL}, } ,
{"clearevent", 1, NULL,ft_yesno , fc_stable , {v:NULL}, {y:FS_clearevent}, {v:NULL}, } ,
{"aux" , 0, NULL, ft_directory, fc_volatile, {v:NULL}, {v:NULL} , {i: 1}, } ,
{"main" , 0, NULL, ft_directory, fc_volatile, {v:NULL}, {v:NULL} , {i: 0}, } ,
{"single" , 15, NULL, ft_ascii, fc_volatile, {a:FS_r_single} , {v:NULL}, {i: 0 } , } ,
{"single_ds2400", 15, NULL, ft_ascii, fc_volatile, {a:FS_r_single} , {v:NULL}, {i: 1 } , } ,
} ;
DeviceEntry( 1F, DS2409 ) ;
/* --- Functions */
/* DS2409 */
static int OW_r_control( BYTE * data, const struct parsedname * pn ) ;
static int OW_discharge( const struct parsedname * pn ) ;
static int OW_w_control( const UINT data , const struct parsedname * pn ) ;
static int OW_clearevent( const struct parsedname * pn ) ;
/* discharge 2409 lines */
static int FS_discharge(const int * y, const struct parsedname * pn) {
if ( (*y) && OW_discharge(pn) ) return -EINVAL ;
return 0 ;
}
/* Clear 2409 event bits (and alarm state) */
static int FS_clearevent(const int * y, const struct parsedname * pn) {
if ( (*y) && OW_clearevent(pn) ) return -EINVAL ;
return 0 ;
}
/* 2409 switch -- branch pin voltage */
static int FS_r_sensed(UINT * u , c
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Samstag, 16. Dezember 2006 02:11 schrieb Paul Alfille: > On 12/15/06, Jan Kandziora <[EMAIL PROTECTED]> wrote: > > Before I'll rumble through that, I'd like to add another node to the > > DS2409 chip: "clearevent" just issues a 0x66 "disconnect all lines" > > control command and clears the DS2409s event flags. I know "discharge" > > does this, too, but I don't like the 100ms time needed there. > > Sounds great, though the datasheet calls it "All Lines Off". Why choose > "clearevent" as the name? > Because it's effect to the user is to clear the event flags and alarm. The "all lines off" part of the 0x66 control command is ineffective in owfs as the next select may turn the lines off/on at its will. > > I'll plan to use this "clearevent" node with my DS2409 driven locks. The > > event is triggered on connection of an iButton to the lock. Then one does > > only have to scan the "alarm" directory of the backbone to check for new > > keys. > > There are some subtilties with deeper branching. OWFS kee[s trak of the > last selected path to reduce redundant path selection (you have to turn off > all sister DS2409s at each level). I'll add a flag that marks the stored > path as untrustworthy. > Ok. That marking has to be done in the "discharge" node, too. > > May I check in the change directly or should I send a patch? > > Please change directly. > Ok. Kind regards Jan -- Vor Onboard-Grafik sollte man mit Aufklebern wie auf Zigarettenschachteln warnen... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Samstag, 16. Dezember 2006 02:37 schrieb Paul Alfille:
> This is an ambitious, but tricky change. When you are happy with it, let me
> test it too. I can construct a 2 level network here.
>
My idea is to transfer the BUS_select_branch() from BUS_next into BUS_select.
This should do no harm -- BUS_next is the only place where it is called. That
way, we could put BUS_select_branch() directly after the BUS_reset().
As BUS_select_branch returns immediately for the backbone, nothing changes
when selecting the backbone. When selecting a branch, BUS_select_branch()
will trigger the Smart-On-Command of that DS2409 *again*, thus generating a
single reset pulse for the branch.
This should work independent on how deep the DS2409 is located, as with the
previous algorithm, all switches of the DS2409 up to that last DS2409 in the
row are already set-up correctly, and all the chips in that branch (and the
backbone) could receive the previously thrown BUS_reset() and
BUS_select_branch().
As the BUS_next function and therefore, the 'uncached' directories always
used this method to list nodes on branches, I think the attached minimalistic
patch is safe. I'm not sure how it affects caching, though.
If the thermostat handling is broken now (don't have one to test), I think
BUS_select_branch() could be called safely after it, too. I didn't do it just
to keep the possiblity to attach the thermostat to a branch, too. Maybe it
works that way?
Kind regards
Jan
--
DOS: n., A small annoying boot virus that causes random spontaneous
system crashes, usually just before saving a massive project.
Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS.
diff -Naur owfs.orig/module/owlib/src/c/ow_bus.c owfs/module/owlib/src/c/ow_bus.c
--- owfs.orig/module/owlib/src/c/ow_bus.c 2006-12-14 20:50:04.0 +0100
+++ owfs/module/owlib/src/c/ow_bus.c2006-12-17 00:05:00.0 +0100
@@ -110,7 +110,7 @@
int BUS_next( struct device_search * ds, const struct parsedname * pn) {
int ret ;
-if ( BUS_select(pn) || BUS_select_branch( pn ) ) return 1 ;
+if ( BUS_select(pn) ) return 1 ;
ret = BUS_next_both( ds, pn ) ;
LEVEL_DEBUG("BUS_next return = %d "SNformat"\n",ret,SNvar(ds->sn)) ;
if (ret && ret!=-ENODEV) {
diff -Naur owfs.orig/module/owlib/src/c/ow_select.c owfs/module/owlib/src/c/ow_select.c
--- owfs.orig/module/owlib/src/c/ow_select.c2006-12-14 20:50:04.0 +0100
+++ owfs/module/owlib/src/c/ow_select.c 2006-12-17 00:02:54.0 +0100
@@ -88,6 +88,7 @@
/* proper path now "turned on" */
/* Now select */
if ( BUS_reset(pn) ) return 1 ;
+if ( BUS_select_branch(pn) ) return 1 ;
if ( pn->dev && (pn->dev != DeviceThermostat) ) {
//printf("Really select %s\n",pn->dev->code);
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Proposed Enhancement: "read_ROM" node in simultaneous directories
Am Samstag, 16. Dezember 2006 02:11 schrieb Paul Alfille: > There are some subtilties with deeper branching. OWFS kee[s trak of the > last selected path to reduce redundant path selection (you have to turn off > all sister DS2409s at each level). I'll add a flag that marks the stored > path as untrustworthy. > There seem to be a problem with this flag now. As we have now a "discharge" and a "clearevent" node in the DS2409 code, I'll just left out setting this flag in the latter one to demonstrate the following: janskiste:~ # tclsh % package require ow ; OW::init /dev/i2c-1 ; OW::get uncached bus.7/,bus.6/,bus.5/,bus.4/,bus.3/,bus.2/,bus.1/,bus.0/,29.A7410100/,29.8F410100/,1F.141B0500/,1F.0F1B0500/,alarm/ % OW::get alarm 29.A7410100/,29.8F410100/ --- Connect keys in both keylocks --- % OW::get alarm 29.A7410100/,29.8F410100/,1F.141B0500/,1F.0F1B0500/ % OW::put 1F.141B0500/discharge 1 % OW::get alarm 29.A7410100/,29.8F410100/ % Huh? Both alarms were cleared? --- Connect keys in both keylocks again --- % OW::get alarm 29.A7410100/,29.8F410100/,1F.141B0500/,1F.0F1B0500/ % OW::put 1F.141B0500/clearevent 1 % OW::get alarm 29.A7410100/,29.8F410100/,1F.0F1B0500/ % Ahh, that's better. It seems to me the entire state of the DS2409 in the level directly *below* the discharged line is invalidated, too. Kind regards Jan -- Microsoft should switch to the vacuum cleaner business where people actually want products that suck. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] PHP Class for OWServer
Am Mittwoch, 20. Dezember 2006 13:16 schrieb Paul Alfille: > Hello Roberto, > > Very nice work. > > I found the documentation at the end of the file (as you had said) and have > a few comments: > > A. I dont believe there is a default port for owserver. > Should we issue a request for a "registered port" (port 1024-49151) at IANA? http://www.iana.org/cgi-bin/usr-port-number.pl I'm pretty sure a formal application would be granted, as owserver 1. is stable 2. has a relativly wide user-base 3. is not undead, like many other protocols which occupy port numbers Kind regards Jan -- Windows 2000: Designed for the Internet. The Internet: Designed by UNIX. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] PHP Class for OWServer
Am Mittwoch, 20. Dezember 2006 15:17 schrieb Paul Alfille: > Sounds fine. We also have an mdns protocol registered. > Do you want to submit the request? > If you are ok with it, I will. It may take some time until I collected the neccessary information for the application (protocol details etc), though. Kind regards Jan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] PHP Class for OWServer
Am Mittwoch, 20. Dezember 2006 17:13 schrieb Roberto Spadim: > any idea on what port should we use as default today?! > As IANA will choose the port number alone, just waiting for the application result seems to be a wise idea -- I expect it to be through first week after new year's eve. In the interim time, why don't you choose one -- we'll have to change it by an at least 99,9979% chance anyway. ^__^ Kind regards Jan -- There are three schools of magic. One: State a tautology, then ring the changes on its corollaries; that's philosophy. Two: Record many facts. Try to find a pattern. Then make a wrong guess at the next fact; that's science. Three: Be aware that you live in a malevolent Universe controlled by Murphy's Law, sometimes offset by Brewster's Factor; that's engineering. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] usage of 1wire sensors in motor-sports
Am Sonntag, 24. Dezember 2006 16:41 schrieb Japie: > On Sun, 24 Dec 2006 14:17:18 +0200, Paul Alfille wrote: > >> Can owfs/1wire read in mili-seconds? > > > > That might be pushing it.10 to 100 msec. > > That would do, 10.000rpm ~ 180 pulses per second, but if I take a pulse > > >from the cams it wil be 90 p/sec. so 10ms. will do. > > Is that speed limited by the sensor or the fs? > The speed is limited by the onewire bus system. The bitrate for adressing a remote sensor is 16kBit, which limits sampling speed to ~10..30ms. To count pulses, you can use the DS2423 counter chip, which gets you around that limitation. Just sample the total amount of pulses counted by this chip once a second, and you'll get an exact (but delayed) readout. > >> Are there pressure sensors up to 10bar? > > > > Not currently, though I'm they could be built, there are voltage > > sensors with temperature compensation. > > Could something be home-brew? > There are plenty electric pressure sensors around, maybe they can be > hoocked-up to a 1wire. > Yes. You can use either the voltage (e.g. DS2450) or the current sensor (e.g. DS27xx) chips for that purpose. > Actualy my project is similar to a weather station, only the readings are > a bit higher but we need: rpm, temp, pressure and humidity only "abnormal" > thing would be a way to collect data from our trothle control (100K > potentiometer) > The main difference to a weather station is the sampling rate needed. Weather in "open air" doesn't change as drastically as in intake and exhaust pipes of an engine. Kind regards Jan -- You can make it illegal, but you can't make it unpopular. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] usage of 1wire sensors in motor-sports
Am Montag, 25. Dezember 2006 12:10 schrieb Japie: > > Data logging has 2 objectives, first is to find out why and where > something went terrebly wrong, second goal is to show us why the engine > was running so much bether one match than the other. > For the "something went terrebly wrong" part we need accurate and fast > timings. > temp. readings and humidity are for engine adjustements so 500ms. will do, > pressure readings for turbo boost and oil can contain info about a engine > crash so 100ms. at least. > Possible with the A/D converters and very small thermocouples, I think. Pressure sensors like this http://www.datasheetcatalog.com/datasheets_pdf/M/P/X/5/MPX5100.shtml may fit, too. The conversion time of the DS2450 is about 1ms, so it fits these sensors. > As for rpm readings it's problematic, if the engine is running 10.000rpm > the camshaft is doing 5000 so the "slowest" pulse I can get of it is 90 > times per second, but I would like to know both the speed of the > crankshaft as the camshaft because after a blow-up it would be nice to now > if the engine was damaged because the cambelt broke or that the cambelt > broke because of the damage... > Are you really sure it works that way? I would expect the cambelt to jump a few teeth in any case before you can measure any speed change in cambelt and shafts. My idea would be to have markings on the belt and the shafts, so one could check if the positions still fit. That would give a more meaningful result than checking for a secondary derived value like acceleration. Second, instead of checking speed of the engines shafts, I would check gas pressures to look for that situation. Gas pressure is directly joined with the engine's current situation, so is torque (but torque is hard to measure), speed in contrary is just a derived value. Maybe I'm wrong in details -- I'm just an electronics and energy engineer, not a mechanical engineer. If you have more insight, please let me know... > > In the project I want to read the owfs with rrdtool and writing the rrd-db > to an usb-stick. > This stick can be copied after a run for later use. > I'am planning on using the ASUS WL-HDD2.5 with openwrt/owfs/rrdtool, only > donwfall is that it has only one usb port so a hub is needed. (on the > other hand thats positive since I have all the hubs ports for 1wire so I > can use a single one for the fast timings of the crankshaft one for the > camshaft and another for temp. and pressure readings.) On openwrt I like > to place a webpage with rrd-images of the run so we can read-out the > values via wlan right after a run (or crash). > As I found out, USB is a problem in environments where big EMC pulses from magnetic coils are present. It's twisted-pair, but still easy to break. > As for the sensors, DS2423 sounds great using a sample rate of 50ms. I > could use both crank and cam on one wire. > Are there any shematics around on how to hook it up to an magnetical or > optical pulse signal? > Just put a photo transistor between GND and the input line, and a 10k resistor between the Vdd and the input line, that should work. The chip counts negative edges, this way it will trigger on dark->light changes. Some debouncing is done inside the DS2423, if you need more, put a 1nF capacitor in parallel to the transistor. > As for humidity is there something usable available for that (since it's > placed inside the inlet channel wich is under 7bar pressure) or should > that be homebrew also? > Hm. As the common humidity sensors don't have any gases in them, pressure should not destroy them. However, their measurement results may be inaccurate as humid air behaves differently under low and high pressure conditions. > And does anyone of you guys know some great documentation on how to hookup > and setup a 1wire system? (owfs itself is well documented as is openwrt) > Read the official application nodes on the Maxim website. http://www.maxim-ic.com/an_prodline2.cfm/prodline/21 This one is especially useful for you, I think: http://www.maxim-ic.com/appnotes.cfm/appnote_number/148 Kind regards Jan -- People get annoyed when you try to debug them. -- Larry Wall - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Switching a voltage other then a low voltage DC one
Am Montag, 1. Januar 2007 19:47 schrieb Gregg Levine: > Hello! > New project starting up. It will be a single camera CCTV system. I'd > like the camera's P/S to be switchable via a DS2406. > > Problem is that this one uses AC at 24 volts to activate itself. Has > anyone found the right combination of other components to act as an > appopriate one for this voltage? > Use e.g. a MOC3023 optocouple with triac output to switch a power triac e.g. TIC206D (easy to get) or BTA10 (insulated mounting tab). http://www.datasheetcatalog.com/datasheets_pdf/M/O/C/3/MOC3023-M.shtml That datasheet cointains application circuits for 110 and 220V. For 24V, extrapolate a bit. Kind regards Jan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Interpreting counter values from ds2423
Am Donnerstag, 18. Januar 2007 15:24 schrieb Gene Dio: > > I am in pure testing mode with this, so I am triggering the counters with a > pair of simple momentary contact switches (interpet that to mean a pair of > $2 doorbell switches from the local hardware store). The final use for > this will be much more complex, but I am using this approach to get my > system setup and test my code. > Simple switches "bounce" -- that means produce loose connection after pressing them because of the springiness of the metal contacts. You have to ged rid of those spikes, as the DS2423 think they are valid pulses. With simple doorbell switches, a RC circuit (or better, a monoflop) for each switch is neccesary. To increase the rise time, connect an additional capacitor in parallel to the switch. Increase the capacitor value in *10 units until no bounces appear. The correct values must be probed with the actual switch +5V+ | +-+ | | | | 100k | | +-+ | INPUT--o---+ | | --- o / 1n/ --- o/ | | GNDo---+ Kind regards Jan -- 1) Never draw what you can copy. 2) Never copy what you can trace. 3) Never trace what you can cut out and paste down. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: [IANA #50010] Application for port-number: owserver (Assigned-4304)
Am Dienstag, 23. Januar 2007 02:16 schrieb Paul Alfille: > Great news, 4304 is out default port. I'll modify the programs and examples > to use it. In general, if no port is specified, 4304 will be assumed. > That's indeed great news. owserver has a default port now and will be put into /etc/services files soon... ^__^; I think, owserver should be modified that way the port option is checked first, then it looks for an owserver entry in /etc/services, and if that entry is not present it uses the hardcoded port number 4304. Kind regards Jan -- Moore's Gesetz: Alle 18 Monate halbiert sich die Größe der Hardware, und ihre Geschwindigkeit verdoppelt sich. Gates' Gesetz: Alle 18 Monate verdoppelt sich die Größe der Software, und ihre Geschwindigkeit halbiert sich. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2480B based adapter
Am Donnerstag, 1. Februar 2007 00:39 schrieb George M. Zouganelis: > Simon Natterer wrote on 1/2/2007 01:16: > > George M. Zouganelis wrote: > >> Today I built a DS2480 serial adapter (schematic attached) after > >> failing to work with > >> a orginal Elektor schematic (wich had no RS232 level Driver)(Issue > >> Apr/2004 By Luc Lemmens) > > > > I have almost the same schematic, but with a MAX232 and there I have to > > tie the POL pin to +5V (VDD). I don't know what is the difference of > > your ADM232. > > Arg ^ > > Remind me to pay you a beer! :D > In the DS2480 datasheet, the following is stated: 6 POL RXD/TXD Polarity Select. RXD/TXD polarity select; tied to GND for RS232 (12V or 5V) connection; tied to VDD for direct connection to UART chip. Sorry I lead to certain misconception with the eagle library you used (I think). There I've written: The RxD and TxD lines are operated at 0V/5V. The POL pin selects the RxD and TxD "polarity", that means straight-through or inverted. If POL is connected to GND, RxD and TxD behave properly for connection to inverted RS232 drivers, like the MC1488/1489 or MAX23x chips. If POL is connected to Vdd, RxD and TxD behave properly for direct connection to a 0V/5V UART chip. So the POL pin should be connected to GND if a simple diode/transistor/resistor network is is used as the RS232 "interface", like the Elektor schematic presumably does. If inverted drivers are used in the peripheral, they are used on *both* sides (computer and peripheral), so the inversion is gone and POL need to be connected to Vdd. Hmmm. Maybe I should update the library. Could anyone of the native english speakers here come up with an unambiguous text? Kind regards Jan -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- D. Knuth - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2480B based adapter
Am Donnerstag, 1. Februar 2007 16:57 schrieb George M. Zouganelis: > > Hmmm. Maybe I should update the library. Could anyone of the native > > english speakers here come up with an unambiguous text? > > btw, do you know where I can find a good walkthrough tutorial on editing > library components for Eagle (Schematic and PCB)? I need to modify some > components (mainly resizing/relocating their PADs) > http://www.cadsoft.de/cgi-bin/download.pl?page=/home/cadsoft/html_public/download.htm.de&dir=eagle/program/4.1 The four items at the bottom are the eagle manuals. Section 8 covers library design. Kind regards Jan -- We are Linux. Resistance is measured in Ohms. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] i2c
Am Dienstag, 6. Februar 2007 08:30 schrieb Stuart Poulton: > Dear All, > > Does anyone have experience of working i2c interfaces for either > > DS2482-100 , DS2482-800, initially something parallel port based would > be ideal. > I posted a schematic a while ago. To avoid cluttering the list, I mailed it directly to you. Kind regards Jan -- I'm not in favor of senseless Micro$oft bashing. I'm in favor of bashing Micro$oft senseless. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS Logo...where is it
Am Montag, 12. Februar 2007 06:59 schrieb Roberto Spadim: > > every thing could be OWSuite, i'm making some logos check the animated gif > Huh, that's kind of cool! Altough I usually abhor animated pictures (lets me think of ads), I like your logo idea. However, there could arise some problems with the other projects starting with "OW", like George's OWTF or the OWW kernel driver. For a newbie, it's not distinguishable which project the logo is representing and which it does not. Another problem is on media where the animation could not be seen, e.g. pdf documents, schematics etc. To avoid this, I recommend to drop the animation in favor of a bullet list like this one: lib * fs * ftpd Net * httpd Kind regards Jan -- Where do you want Bill Gates to go today? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Some thoughts on logos, etc.
Am Montag, 12. Februar 2007 22:01 schrieb David Lissiuk: > Standards are a good thing. And OWFS has become a major player in terms > of 1-Wire work. As an end user, I'd like to know that my hardware is > fully supported and tested by OWFS and uses a wiring standard like > 1WRJ45 when I buy the product along with knowing any enclosures IP > rating. (Weather proof level). Seeing this on packaging and advertising > would be a real plus to me. > I don't think OWFS (as a pure *software*) should address hardware specs. At least to the moment we'll implement the global hardware database we talked about last month. An "owfs hardware compatiblity" in my view means, owfs knows the *semantics* of the certified board, e.g. like the humidity sensor board or the DS2408 driven LCDs. For such boards, a logo program would be nice. Things like connectors, wire layout etc. shouldn't be adressed by the logo in my view, as the software can't identify them and too many other specs for connectors exist. To be honest: For my boards, I will specify connectors myself, depending on the mounting situation. Kind regards Jan -- Ein Rechner tut genau das, was der erfahrenste Nutzer auf dem System will. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Cable length when connecting a 18B20 sensor to a USB dongle
Am Samstag, 3. März 2007 21:14 schrieb Pedro Côrte-Real: > Do I need to power the 18B20 with Vcc for this distance? > No. Power requirement of the DS18B20 is max. 1.5mA, which causes only a voltage drop in the mV range even on long and thin 1W and GND lines. Check for contact problems at the connectors. > In general what should I look out for in distances over 10 meters? > If you power a lot of onewire chips (and peripheals) over a thin, long cable, the GND niveau at the end of the cable may reach 0.7V due to the current through it. This disturbs the onewire function for chips at the end of the cable a lot. Kind regards Jan -- A closed mouth gathers no foot. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] e: line distance
Am Sonntag, 4. März 2007 00:53 schrieb Wizard: > > > > If you power a lot of onewire chips (and peripheals) over a thin, long > > cable, the GND niveau at the end of the cable may reach 0.7V due to the > > current through it. This disturbs the onewire function for chips at the > > end of the cable a lot. > > > > Kind regards > > > > Jan > > Hey i have my DS18s20's all over the house my line length is about 300 > feet in total it was difficult but i have 32 ds18s20 and 4 DS2408 all > on the same network > just add one step at a time. > The problems start whith currents >100mA and cables as thin as flat telephone cable. And with lots of intermedient connectors. A DS2408 driving 8 20mA LEDs is limiting cable length to ~20m when using 0.07mm² wire gauge phone cable. This problem is arising any time you are using the GND line as power return. If you plan to power devices over such a cable, it is wise not only to provide a separate power wire and *one* additional GND wire, but as much GND wires as possible. 5V or 12V over a thin cable will be subject to voltage drop, too, but there it is not crucial, as you can apply a slighty higher voltage at the start of the cable. That trick is not possible with elevated GND potentials. Kind regards Jan -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Cable length when connecting a 18B20 sensor to a USB dongle
Am Sonntag, 4. März 2007 00:38 schrieb Pedro Côrte-Real: > > Any idea what the usable range will be using Cat6? > Cat6 may have different wire gauge. As the cable length is limited by wire gauge, you'll have to be more specific. Kind regards Jan -- People get annoyed when you try to debug them. -- Larry Wall - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] HELP Using DS2405 as Digital Inputs (NSLU2) and some great I/O boards
Am Donnerstag, 5. April 2007 14:31 schrieb Rob Conway: > > NOW MY PROBLEM > The digital input board uses DS2405 and I just read the sense parameter. > It seems that regardless of how fast I scan these (2 sec or 20 sec) it > takes 2 (sometimes 3) reads of the sense parameter before the state > changes. Again if I physically turn off the input, the 1st read no change > the 2nd read it will show a change. > > I am now approaching 20 devices on the network and do not particulary want > to scan these Digital inputs twice as fast as nessecary. I am going to use > some inputs as "momentary buttons and a high level alarm" thus wanting to > read the status on every scan. > Aside from using a microcontroller as the host, the DS2405 is unsuitable for momentary buttons. To catch a single keypress, you have to scan right at the moment the key is pressed. With a multi-process OS like Linux, this is not feasible. It's likely your application is currently suspended due to some other process occupying the processor, so you lose the keypress. Other problems like key chatter get in your way, too. Use the DS2408 as a keyboard input. It has internal edge detector and latches, and a alarm function triggered as soon as an edge is detected. With this chip, you eleminate the problems you have with the DS2405 and may use the conditional search function (alarm directory) to check if any button was pressed since last check. Kind regards Jan -- A bureaucrat's idea of cleaning up his files is to make a copy of everything before he destroys it. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OT: 1-wire Relais Output
Am Samstag, 7. April 2007 13:05 schrieb Sven Geggus: > Hello, > > not exactly a Software Question but anyway. I intend to switch mains > connected devices by 1-wire. Any suggestion for a suitable circuit? > Solid state relays, e.g. by OptoZZ or similar behave as a LED on low voltage side. If you like to build such a thing yourself, try e.g. MOC3043. Kind regards Jan -- ...very few phenomena can pull someone out of Deep Hack Mode, with two noted exceptions: being struck by lightning, or worse, your *computer* being struck by lightning. -- Matt Welsh - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OT: 1-wire Relais Output
Am Samstag, 7. April 2007 15:50 schrieb Sven Geggus: > Jan Kandziora <[EMAIL PROTECTED]> wrote: > > Solid state relays, e.g. by OptoZZ or similar behave as a LED on > > low voltage side. If you like to build such a thing yourself, try > > e.g. MOC3043. > > I think that a mechanical Relay Output would better suited for my purpose > than a solid state relay. > > I would like to be able to switch full 230V/16A european mains supply > without an additional fuse added thus a solid state relay solution would > require the installation of a very big heat sink. > Sure. Rule of thumb says 1 W/A. > All I need is a suggestion for some working PNP transistor circuit. > NPN, please. Interfacing NPN and PNP logic requires additional magic. In addition, PNP is no help in any case. +Vrel -+---+---+ | | | | | --- 10k REL ^ 1N4001 | | | | | | | +--- | | | |/C Vout --+-| BD237 |\E | GND ---+ Note the inverted logic. If you need positive logic, you have to add another 10k-Transistor circuit: +Vrel -+---+---+---+ | | | | | | | --- 10k 10k REL ^ 1N4001 | | | | | | | | | | +--- | | | | | |/C | +-| BD237 | | |\E | | | | |/C | Vout --+-| | BC547 |\E | | | GND ---+---+ Kind regards Jan -- Je tiefer der Abgrund, desto höher der Himmel. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] attaching microcontrollers to OW
Am Samstag, 21. April 2007 20:45 schrieb njh: > On Sat, 21 Apr 2007, Paul Alfille wrote: > > The problem isn't technical -- Louis Swart does it (PIC based) in his LCD > > controller. > > > > Dallas/Maxim restricts 1-wire slaves (their patents, intellectual > > property, and "quality assurance"), while making bus master design freely > > available and unrestricted. I think it's a poor business decision, > > limitting their market, mindshare, etc, but they seem to have the right. > > I agree, this seems rather stupid (and probably explains the lack of new > products built around it). > To guarantee unique slave adresses, Dallas Semi's choice is just an obvious one... > > The DS2408 can also talk to a microprocessor a byte at a time, with a > > strobe line to coordinate data transfer. We'd have to do some additions > > to OWFS to support that mode, but it's quite doable. > > Yes, my friend is prototyping this approach. But it's ugly, uses up 9 > port pins, requires the PIC to interrupt to handle data (rather than > reading from shared memory as with the 2404) and requires another layer of > checksumming. The 2404 based approach was very elegant (although allowing > bus mastering would make it the ultimate low cost sensor/actuator > networking interface). > Ouch. The DS2404 was a useful chip for such appliances. I planned to use it in a future design, too. I have a datasheet from last year without "Do not use for new designs" printed over it... > I don't suppose dallas/maxim are amenable to listening to us mere > hobiests... > Not being a mere hobbyist, I'll ask at Maxim about the discontinuation of DS2404... maybe there will be a substitute for this. Kind regards Jan -- Linux, Playboy Edition: nichts als die nackte Kommandozeile... - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] attaching microcontrollers to OW
Am Sonntag, 22. April 2007 00:25 schrieb Jan Kandziora: > > Ouch. The DS2404 was a useful chip for such appliances. I planned to use it > in a future design, too. I have a datasheet from last year without "Do not > use for new designs" printed over it... > > > I don't suppose dallas/maxim are amenable to listening to us mere > > hobiests... > > Not being a mere hobbyist, I'll ask at Maxim about the discontinuation of > DS2404... maybe there will be a substitute for this. > Ok. I asked Maxim Europe headquarters about this and got the response DS2404S and DS2404B are still available in quantities 1000 and up within 5 weeks after order. Don't think this will change soon. There is no replacement part for the DS2404 yet, it was cancelled because the factory producing it changed its machinery and a resonable stock was build up already. I think, for mere hobbyist needs, the available stock is more than sufficient. Don't know if they still give away samples of that device... Kind regards Jan -- "And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank." -- Matt Welsh - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS on Kamikaze OpenWrt
Am Freitag, 11. Mai 2007 02:02 schrieb njh: > > Bit bashing i2c is easy - use the i2c 1-wire bus master chips. > And there is already a bunch of bit banging drivers for that. The i2c-parport driver can be adapted to work with any 3-Pin GPIO, I think. Bit-banging i2c consumes a lot of cpu time, though. Don't update the onewire data too often. Kind regards Jan -- Be warned that typing "killall name" may not have the desired effect on non-Linux systems, especially when done by a privileged user. -- killall manual page - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Fwd: Faster-than-cron polling ideas?
Am Samstag, 19. Mai 2007 22:50 schrieb Paul Alfille: > -- Forwarded message -- > From: Brian Fahrlander <[EMAIL PROTECTED]> > Date: May 19, 2007 7:03 PM > Subject: Faster-than-cron polling ideas? > To: [EMAIL PROTECTED] > Schnipp > > Most of the things I poll will be in the 'per minute' range, though; > too fast for cron. And I think I've worked out a way for some small > processes to work metaphorically like OWFS, storing values in a > directory tree, for other processes to share when needed. > > What I'd like to find is something that the system clock and kick > off every second, whether polling happens then, or not. I've never used > interrupt-driven Unix programming, and my C experience was in 1989. Do > you have any resources you point to folks like me, with this situation? > There is no need for special "interrupt driven programming" in Linux, as Un*x -- in opposition to DOS -- is a multi-tasking OS by nature. It handles *all* tasks as "interrupt-driven". Set up a shell script with an endless loop, poll, sleep a second, poll ... Other tasks will run during the sleeping automatically. myscript.sh: === #!/bin/sh while : do poll_ow_sensors... sleep 1 done $ chmod 755 myscript.sh If you start that script in the background, $ ./myscript.sh & the controlling shell won't wait for the myscript.sh process to end, but immediately continue with a new prompt. $ Kind regards Jan -- Your fault: core dumped - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owtcl broken in 2.6p5!
Am Freitag, 1. Juni 2007 22:22 schrieb Sven Geggus: > While owserver, owhttpd and owfs are working fine owtcl seems to be > broken :( > > ::OW::put works fine but ::OW::get seems to be broken! > > When try to use the following code in owfs 2.6p5: > --cut-- > #!/usr/bin/tclsh > package require ow > > ::OW::init localhost:5 > ::OW::get /uncached/10.B963D4000800/type > > --cut-- > > I get: > ::OW::get returns "Operation not permitted" > Try inserting "::OW::get uncached" inbetween. Does it work now? Kind regards Jan -- Neue Erfindungsbäume für Civilisation: Internet | | Cola--+ +--Tiefkühlpizza - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Usb problem with DS2490
Am Montag, 4. Juni 2007 11:07 schrieb Vortex: > > This is all very strange to me and i'm a bit helpless where to search the > error. Hardware? Notebook? The DS2490 surrounding hardware? Kernel? > libusb? owfs itself? > > Some ideas? > Your interface may drain too much power on power-on from your notebook's USB port. Try inserting choke coils into the +5V and GND lines (a few µH). Jan -- BASIC is to computer programming as QWERTY is to typing. -- Seymour Papert - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Usb problem with DS2490
Am Montag, 4. Juni 2007 14:29 schrieb Sven Geggus: > Jan Kandziora <[EMAIL PROTECTED]> wrote: > > Your interface may drain too much power on power-on from your notebook's > > USB port. Try inserting choke coils into the +5V and GND lines (a few > > µH). > > He might also be able to work around this Problem at least for testing > purposes using an active USB HUB. > The OP tried that already, and it worked. Therefore my advice. Kind regards Jan -- "And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank." -- Matt Welsh - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Usb problem with DS2490
Am Montag, 4. Juni 2007 15:42 schrieb Vortex: > > > The OP tried that already, and it worked. Therefore my advice. > > OP? Does that mean it's a known issue? > OP: original posting/poster. > But i can't imagine that this > usb-port which is capable of 500mA should have a problem with a few > mA. Spikes and something like that on the power lines should be > sufficiently blocked by Capacitors and RF-Chokes which i already > placed there. And due to your recommends i increased the > Capacitors now. Without any improvement. > Increasing the capacitors make things *worse*, not better! Empty capacitors are like short circuits. You have to limit the current flowing into empty capacitors by applying a resistor or (better) a choke coil to the supply lines. USB circuits are powered on on detection/driver-reload, so this power-on problem is more inconvenient than with other devices. Even a "quick melt" 100mA fuse (your other posting) sure doesn't melt if a 1A current is flowing for a few µs. Melting is a energy -- not current -- related process, and ~1A*0,1V*100µs=10µJ is too few energy to melt even a thin stanniol wire .There are fuse deratings to calculate the neccessary current for a given time. This is why melting fuses are useless as soon as high-speed electronic switches should be protected. Your fuse protects the onewire cable, not the interface circuit. Most USB interfaces in desktop computers doesn't have appropiate current limiting switches (MIC2075 or TPS2024) to limit the current to the specified 500mA, but instead use a 1A fuse. Your laptop however, may use such a switch -- because a molt fuse is inconvenient in a laptop -- and thus, cause problems. Kind regards Jan -- Microsoft and its customer are addicted to backwards compatibility in a way that makes a heroin addict look silly. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Usb problem with DS2490
Am Dienstag, 5. Juni 2007 09:48 schrieb Vortex: > > Increasing the capacitors make things *worse*, not better! Empty > > capacitors are like short circuits. You have to limit the current flowing > > into empty capacitors by applying a resistor or (better) a choke coil to > > the supply lines. > > But i think the usb power supply isn't switched on or off. So the > Capacitors have to be loaded only if i plug in the device. And that's > not the problem. > USB Power is usually switched, besides from non-standard ports on certain desktop mainboards. The capacitors are *not* loaded as soon as you plug in the device in that case. As soon the host controller detects the device speed resistor -- the 1.5k resistor between D+ and +5V if you built your adapter as the DS2490 data sheet suggests -- it reports that incident to the driver and the USB host controller driver turns on power for that port (or not, if no driver is loaded). In case a device has a failure, the usb driver can turn off the power for the specific port. It may do so if the device is to be powered off due to power saving issues. E.g. a laptop could turn off all USB devices but an external USB keyboard or card reader during STR state. The power is switched off if the presence resistor is there but the device does not respond to the initiation handshake, too. > The failure happens after a few successful > transactions. > Ok. so the problem isn't strictly related to power-on. It may be a related issue, though. > If the power supply would be switched the choke coils > would make bad things too. > At least if they are large enough to store > reasonable amounts of energy. (Wasn't there something like u_L=di_L/dt? > At least there would be large voltage peaks then) > They would induce an additional voltage, but this is low with reasonable small coils as the switch chips don't turn off too fast. > > > USB circuits are powered on on detection/driver-reload, so this power-on > > problem is more inconvenient than with other devices. > > Are you sure? Of course the peripheral device may be in some sort oft > sleep mode until it's initialized by a driver. But the power supply on > the usb-bus is on all the time. At least in my experiences. > For some mainboards, that may be true -- but it is non-standard. See above. The reason may be that absurd USB "devices" like this http://www.bitmark.com/giftmugs/sampler/various/Mug-Boss/Coffee-Mug-Warmer.html won't work with switched ports, as they have no USB device controller for cost reasons. > > The facts about burning the fuse are certainly right. But this current > peaks should be blocked by the capacitors in the usb power supply lines > (33pF, 100nF, 4,7uF). If this is not sufficient i guess i would need > a choke coil instead which is larger than the whole circuit itself :-). > Capacitors can block current peaks if they are *fully loaded*. If they are empty, they cause additional current flow. That's why you need an LC or RC circuit, not a capacitor alone. The choke coil is there to *limit* the current flowing into the empty capacitor, not to provide energy to the circuit. You could use an 1..6 Ohms resistor, too, but a ~µH coil has the advantage of >>6 Ohms resistance on power-on and nearly zero resistance as soon the power flow is at steady state. If you want to try with a series resistor: A 6 Ohms resistor will limit the current at 5V short circuit to about 833mA. That may be low enough not to trigger any overcurrent circuit in the host adapter. Why 6 Ohms? Because it will too lower the supply voltage about 0.6 Volts at 100mA. 4.4 Volts is the maximum tolerable for the DS2490 to operate. If your circuit draws lower current, you may increase the resistor, though. Kind regards Jan -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Usb problem with DS2490
Am Mittwoch, 13. Juni 2007 06:50 schrieb Vortex: > Hello! > > I investigated the setup again at last weekend. > > Somebody on linux-usb Mailinglist explaind the "failed with status > 50" message. And so i decided to check the waveforms on D+ and D-. > I've discovered that there is a complete impedance missmatch between > the ds2490 and the usb-port of this laptop. > In the datasheet from dallas there are 30pF capacitors recomended > on D+ and D-. But on the Notebook side there are at least 300pf > expected. So i have added capacitors to my circuit at D+ > and D- and everything works well now. > Hm. The DS2490 datasheet lists these capacitors as optional on page 33. > The +5V Power Supply on the Notebook (and all other USB hosts > reachable) is turned on as soon as the notebook is powered up. > Ok. > > Wouldn't this be a chicken and egg problem? The 1.5k resistor couldn't > be detected if the +5V power isn't turned on. And the +5V power wouldn't > be turnd on if the 1.5k resistor isn't detected. > I had in memory the +5V line is not cut but tied to GND in that case. I'm maybe wrong with this. However, the host may cut the power to a USB port. But now I'm not longer sure when this happens (besides from overcurrent). Kind regards Jan - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Weathervane using DS2450. Volt.ALL query.
Am Mittwoch, 4. Juli 2007 03:45 schrieb Matt: > I'm using owserver and python to take reading of a 1wire weathervane. > It uses some reed switches to determine the direction. > > Here's some output from owhttpd > > typeDS2450 > volt.ALL0.0597665, 4.38921, 4.53233, 1.11635 > volt.A0.770246 > volt.B4.38741 > volt.C4.5278 > volt.D4.65609 > > I've been using volt.ALL thinking it was a comma separated catenation of > A, B,C, D, but the output does show that. > > Can anyone help explain what I'm seeing ? > Reading a volt.* node triggers a separate reading. The input voltages may have changed between the readings. Kind regards Jan -- There's light at the other end of the the Windows. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] owtcl: More meaningful error messages
Dear Serg, as my project's focus again moved to owfs and owtcl, I'd like to make some improvements to the tcl binding, especially getting rid of the notorious "Unknown error 4294967295" message and in general, return more meaningful error messages and codes to the tcl program. Is it ok if I check in changes into CVS or should I send patches to you? Kind regards Jan -- ELIZA: You have a tendency to feel you are superior to most computers. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] owtcl: More meaningful error messages
Am Mittwoch, 18. Juli 2007 10:34 schrieb Jan Kandziora: > Dear Serg, > > as my project's focus again moved to owfs and owtcl, I'd like to make some > improvements to the tcl binding, especially getting rid of the > notorious "Unknown error 4294967295" message and in general, return more > meaningful error messages and codes to the tcl program. > Done. > Is it ok if I check in changes into CVS or should I send patches to you? > Well, if noone shouts NO, I'll commit tomorrow. Ok? Kind regards Jan -- A Law of Computer Programming: Make it possible for programmers to write in English and you will find the programmers cannot write in English. - 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] owtcl: More meaningful error messages
Am Mittwoch, 18. Juli 2007 10:34 schrieb Jan Kandziora:
>
> as my project's focus again moved to owfs and owtcl, I'd like to make some
> improvements to the tcl binding, especially getting rid of the
> notorious "Unknown error 4294967295" message and in general, return more
> meaningful error messages and codes to the tcl program.
>
I checked in my changes. All the OW::... procs now report an errorCode like
OWTCL ENOENT {no such file or directory} on error.
As it may break legacy code which relies on the buggy old error messages, I
changed owtcl version to 0.2.
Kind regards
Jan
--
.vbs = Virus Bearing Script?
-
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] DS2480B and owhttpd
Am Samstag, 28. Juli 2007 19:35 schrieb Tilman Glotzner: > > I build myself a serial->1Wire adapter using a DS2480B and a MAX232. I have > a 18B20 (temperature sensor) connected to the bus. I am supplying 5 V > externally -- I am not using the parasitic mode. > > Now, I am trying to commission it using owhttp: > ./owhttpd -d /dev/ttyS0 -p192.168.1.1:3000 --error_level=3 > > The adapter seems not to be recognized (see log below). > Did you try to change the voltage to the DS2480 POL pin? Kind regards Jan -- "...Deep Hack Mode -- that mysterious and frightening state of consciousness where mortal users fear to tread. -- Matt Welsh - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 2.6 kernels and OWFS
Am Mittwoch, 1. August 2007 08:21 schrieb Matthias Urlichs: > > The simple solution is to blacklist the module (and/or unload it before > starting owserver) -- and ask your distro not to compile that module by > default. I have no idea if anybody uses it; it doesn't even support > hubs. > Well, from my point of view, the w1 kernel modules are in some kind of limbo, it hasn't changed much the last month. We discussed some minor items on this list a long time before with the w1 author, Evgeniy Polyakov. Evgeniy is still active in linux kernel development, but his latest project was the distributed storage subsystem. I'm unsure if he has interest in w1 any more. If not, we could change the linux w1 subsystem so it doesn't interfere with owfs or make it an actually *useful* basic layer for owfs. Paul, could you ask him about that? From our last discussion, I had the impression I can't find the right words to talk to him. Kind regards Jan Kandziora -- "And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank." -- Matt Welsh - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 2.6 kernels and OWFS
Am Mittwoch, 1. August 2007 12:58 schrieb Paul Alfille: > > So that is the status of the w1 interface. It's very linux-specific, and > even at best won't add any new function. I was more interested before we > managed to get I2C working, since there is a kernel module for that as > well. > > In short, just unload the ds9490r and everything will work. User-space > drivers are the way to go! > Well, first I'd like to backup user space drivers are the way to go. They are just more flexible. Where a linux kernel driver comes in handy is sharing bus ressources between different applications. Ok, we have owserver for that but then, all the applications have to use owfs. I specifically think of onewire chips built into laptop batteries. As soon a user encounters such a device, wants to monitor it through the usual kernel hardware monitoring interfaces *and* connects some devices to the laptop through owfs (e.g. servicing my vending machine), he will run into a "deadlock". Ok, as far as I read it, w1 isn't connected to the hardware sensor facility so far, but it may come up. Kind regards Jan -- Who is General Protection Fault and why is he reading my hard disk? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 2.6 kernels and OWFS
Am Mittwoch, 1. August 2007 14:41 schrieb Matthias Urlichs: > Hi, > > Jan Kandziora: > > I specifically think of onewire chips built into laptop batteries. As > > soon a user encounters such a device, wants to monitor it through the > > usual kernel hardware monitoring interfaces *and* connects some devices > > to the laptop through owfs (e.g. servicing my vending machine), he will > > run into a "deadlock". > > A conflict would exist only if those are connected through the same > interface. > > I think that's exceedingly unlikely. A laptop battery's monitor would be > connected via I²C, I'd assume. There's no reason at all to sacrifice an > internal USB port plus pay for an expensive USB->1wire adapter. > No, but the problem exists for the i2c<->1w bridge as well. And that chip is cheap enough. > I also assume that nobody who's remotely sane would add put an externally- > accessible I²C or 1wire interface into their laptop … and even if so, > using the same wire that's carrying the battery monitor data would be > deadly. :-/ > Ok, you have a point here. USB<->remote 1W is the most likely configuration. Kind regards Jan -- DOS: n., A small annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] How should we chain?
Am Donnerstag, 2. August 2007 12:55 schrieb Paul Alfille: > > I can see the argument both ways. Part of the problem is that our > filesystem model really matched the 1-wire design -- no inherent order to > the entries. > > Do you think rewiring is likely/possible on the fly? Could we do both > methods? Something like: > > / -- 42.001 > -- 42.002 > -- simultaneous > \ -- temperature > --- voltage > -- chain_list > -- chain > \ -- 0 > -- 1 > A related question: What about symlinks, so one can see the target node when listing "chain" with ls? I know a decent program could always check .../0/address, but "ls" isn't that clever. Symlinks can be also useful for the / and uncached directory, so one can see the target bus of the device when listing / or uncached. Kind regards Jan -- Ich vertonne Spam immer in /dev/dsp statt in /dev/null. Ich mag die Schreie. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2423 - "Data Error"
Am Donnerstag, 9. August 2007 07:02 schrieb Gregg C Levine: > Hello! > Paul, David, (welcome to the group by the way.), the DS2423 counter chip is > a strange animal. It requires an external power supply to run it. > The RAM is not 1W powered, but Vdd powered only. So Vdd acts as an -RESET input, too. > Also it > requires specialized devices attached to its counter inputs, the data sheet > specifies them, but essentially a mechanical reed switch will do that. > For speed reasons the counter inputs have *no* Schmitt trigger! That means, if you leave the inputs open, they will float to about 1/2 Vdd and count the athmosperic noise in the meantime. To avoid this, one have to pullup the input with an resistor to Vdd. This is not done internally as such a resistor either limits counting speed or presents too low input impedance -- and it's just not needed for connecting the usual push-pull outputs, just for switches. Kind regards Jan -- There's light at the other end of the the Windows. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Announcing owtap
Am Mittwoch, 15. August 2007 04:57 schrieb Paul Alfille: > Ok, I've been hinting for a while, but here is is: owtap > > There is extensive documentation (man pages, screen shots, etc) at > http://www.owfs.org/index.php?page=owtap > > Basically it is a program that displays the traffic to and from owserver. > Importantly, owtap knows the owserver protocol and can intelligently show > the messages. > That's some useful piece of software. Thanks, Paul. Kind regards Jan -- Die beste Methode, Windows zu beschleunigen, arbeitet mit 9,81 m/s². - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2423 question
Am Montag, 8. Oktober 2007 22:09 schrieb Paul Alfille: > > Someone is kindly sending me a DS2423 counter device. I'll test this > hypothesis. > Please tell me your postal address and I'll send one. Kind regards Jan -- There's light at the other end of the the Windows. pgpOuUHOdXuVp.pgp Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] DS2450 A/D has offset..nothing really to do with owfs !
Am Freitag, 23. November 2007 11:28 schrieb Rob Conway: > Just wondering if anybody else has used the DS2450 for a long time. I am > using one of these A/D's and I have found that after a while ~6-8 months > all channels have a ~0.3 volt offset from zero. ie all 4 channel readings > go up by ~.3 volts. Its like the chips internal reference voltage somehow > gets screwed up. It's happened twice now over the last 18 months. The > voltage being measured by the inputs are isolated voltages and I have > placed a cap across the inputs. > Then, how about the ground potential? How did you power-cycle you device -- pulling and plugging a connector? Kind regards Jan -- Zero Defects, n.: The result of shutting down a production line. pgp3Zxdmkz7Fy.pgp Description: PGP signature - 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] DS2450 A/D has offset..nothing really to dowith owfs !
Am Freitag, 23. November 2007 13:48 schrieb Rob Conway: > > Isolated is probably the wrong word, as the neg of all inputs is tied to > the neg of the 1wire supply. > No, I really asked about the ground potential. If there is a connector between the DS2450 GND pin and the input's GND, it's likely that connector causes the 0.3V voltage drop. Kind regards Jan -- A bug in the code is worth two in the documentation. pgpphHJ7l2hx9.pgp Description: PGP signature - 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] Problem with temperature reading
Am Donnerstag, 6. Dezember 2007 19:02 schrieb decibels.drop: > cat ~/1wire/uncached/1F.66BD0400/main/10.381755010800/temperature > Just curious: Have you tried cat ~/1wire/uncached/1F.66BD0400/main/uncached/10.381755010800/temperature ,too? Kind regards Jan -- A recent study has found that concentrating on difficult off-screen objects, such as the faces of loved ones, causes eye strain in computer scientists. Researchers into the phenomenon cite the added concentration needed to "make sense" of such unnatural three dimensional objects ... pgpyFgE1knbgV.pgp Description: PGP signature - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] New OWFS non-root access USB udev rule
Hello,
I recently tried again to set up non-root access to the DS2490 adapter.
I failed with the solution showed up at http://owfs.org/index.php?page=udev
It seems the config syntax of udev has changed again. However, I came up
with a much simpler solution: I set up a file
/etc/udev/rules.d/46-ds2490.rules with the line
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="0664"
No helper script neccessary, this line is enough to make it work. Tested
with udev-103-12 of openSuSE 10.2.
Maybe the website should be changed to refelct this change in udev?
Kind regards
Jan
--
A bureaucrat's idea of cleaning up his files
is to make a copy of everything before he destroys it.
pgpBFVzH1ONiP.pgp
Description: PGP signature
-
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] New OWFS non-root access USB udev rule
Am Sonntag, 10. Februar 2008 19:28 schrieb Paul Alfille: > The website now includes both methods: > http://owfs.org/index.php?page=udev-and-usb > > Tell me if I got the details correct. > You got it right. I hope people will read "the line" above the code box with the actual udev line. May I suggest to change this "the line" to "one line" to make it clear that there must not be any line break inbetween? Kind regards Jan -- I'm not in favor of senseless Micro$oft bashing. I'm in favor of bashing Micro$oft senseless. pgpku8aczYmK7.pgp Description: PGP signature - 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] owtcl build broken?
Hello, I just tried to compile the latest CVS and it seems something with owtcl has changed. I've done $ ./bootstrap $ /configure --disable-static --enable-shared --enable-swig --enable-owtcl --disable-debug --disable-owperl --disable-owpython --disable-owphp --disable-owfs --with-tcl=/usr/lib $ make $ make install and got a directory /usr/lib/owtcl-/ with the content drwxr-xr-x 2 root root 184 14. Feb 23:21 ./ drwxr-xr-x 180 root root 86464 14. Feb 23:21 ../ -rwxr-xr-x 1 root root 929 14. Feb 23:21 ow.la* -rwxr-xr-x 1 root root 27606 14. Feb 23:21 ow--shared.so* lrwxrwxrwx 1 root root13 14. Feb 23:21 ow.so -> ow--shared.so* -rw-r--r-- 1 root root 580 14. Feb 23:21 ow.tcl -rw-r--r-- 1 root root 111 14. Feb 23:21 pkgIndex.tcl (instead of the expected owtcl-0.2/ow-0.2-shared and so on...). It seems something inside the build environment is buggy. As I don't know so much about autotool builds, I would be glad if someone could help. Kind regards Jan -- MSDOS didn't get as bad as it is overnight ...it took over ten years of careful development. pgpFdT9UXJAt4.pgp Description: PGP signature - 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] Another build quirk (not severe, though)
Hello, I found another bug in the current owfs build scripts. It seems the ./configure options --disable-ownet and --disable-owmon do not work. Though in the summary ./configure notices they are disabled, ownet and owmon are built and installed. (I found that out because I'm doing a lot of fresh builds with rpmbuild. It checks for files that are present but not noted in the specfile.) Kind regards Jan -- Ein Statistiker, ein Mathematiker und ein Informatiker gehen auf Fotosafari. Der Führer zeigt ihnen ein weißes Zebra inmitten einer Zebraherde. Der Statistiker: Na und, ein einziges weißes Zebra macht nicht viel aus. Der Mathematiker: Wir wissen lediglich, dass es auf einer Seite weiß ist. Der Informatiker: Oh nö, wieder so ein Spezialfall... pgpT24UI8mPpS.pgp Description: PGP signature - 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] Yet another build quirk with owtcl.
Hi Serg, while doing my fresh builds of current CVS, I found another bug in owtcl build. It seems owtcl's ow-0.2.so is still linked to libowcapi-2.6.so.5, while the CVS contains libowcapi-2.7.so.3. Maybe it is possible to link to libowcapi.so instead? Kind regards Jan -- Ein Statistiker, ein Mathematiker und ein Informatiker gehen auf Fotosafari. Der Führer zeigt ihnen ein weißes Zebra inmitten einer Zebraherde. Der Statistiker: Na und, ein einziges weißes Zebra macht nicht viel aus. Der Mathematiker: Wir wissen lediglich, dass es auf einer Seite weiß ist. Der Informatiker: Oh nö, wieder so ein Spezialfall... pgpEaMYuzRSL7.pgp Description: PGP signature - 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] owtcl build broken?
Am Freitag, 15. Februar 2008 09:02 schrieb Serg Oskin: > Fixed in CVS. > That was fast! Many thanks, Serg! Kind regards Jan -- Always remember: Failure is not an option! ...It comes bundled with Windows. pgphinu5bNC0s.pgp Description: PGP signature - 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] Yet another build quirk with owtcl.
Am Freitag, 15. Februar 2008 23:59 schrieb Serg Oskin: > Hmm.. > Try "make clean" before "make"... > rpmbuild even does rm..., tar xzf owfs-tar.gz, ./bootstrap etc.. But ok, I build it by hand again. > Show output "ldd ow-0.2.so"... > linux-gate.so.1 => (0xb7fba000) libtcl8.4.so => /usr/lib/libtcl8.4.so (0xb7ee) libow-2.7.so.3 => /home/jan/cvs/owfs.new/module/owlib/src/c/.libs/libow-2.7.so.3 (0xb7e84000) libowcapi-2.7.so.3 => /home/jan/cvs/owfs.new/module/owcapi/src/c/.libs/libowcapi-2.7.so.3 (0xb7e8) libdl.so.2 => /lib/libdl.so.2 (0xb7e7c000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7e63000) libc.so.6 => /lib/libc.so.6 (0xb7d35000) libm.so.6 => /lib/libm.so.6 (0xb7d0f000) libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb7d06000) /lib/ld-linux.so.2 (0x8000) Hmm. It seems a compile run by hand works as expected but within a fakeroot environment it doesn't. I will investigate this further tomorrow. G'night. Jan -- F: Wieviele Surrealisten braucht man, um eine Glühlampe einzuschrauben? A: Zwei. Einer hält die Giraffe fest und der andere füllt die Badewanne mit buntem Werkzeug. pgpsgESikdABG.pgp Description: PGP signature - 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] [CLOSED] Yet another build quirk with owtcl.
Am Samstag, 16. Februar 2008 09:48 schrieb Christian Magnusson: > You can't have it running in both normal installed environment AND in a > fakeroot. Have you seen any other dynamic linked applications which work > this way? > I'm unsure why the rpmbuild failed yesterday. Maybe I just installed the wrong rpm after building it? Today it works as expected. I think I made a false report. Case closed (I hope). Kind regards Jan -- Ich vertonne Spam immer in /dev/dsp statt in /dev/null. Ich mag die Schreie. pgpBQzWtp3LRT.pgp Description: PGP signature - 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] Fwd: Simple perl program
Am Sonntag, 9. März 2008 20:43 schrieb Paul Alfille: > -- Forwarded message -- > From: <[EMAIL PROTECTED]> > Date: Sun, Mar 9, 2008 at 3:29 PM > Subject: Simple perl program > To: Paul Alfille <[EMAIL PROTECTED]> > > > Dear owfs-developers! > > As recommended by you, Paul, I googled "cgi shell tutorial" and I found > some things. I get sites with "CGI" with "Rebol" or "Apache" and I wrote a > program like > > #!/usr/bin/perl > print "Content-type: text/html\n\n"; > print "Hello, World."; > > and put this into the folder "/var" into the NSLU2. Then, I gave it an > execute right and started it from the command shell. I get > " > Content-type: text/html > > Hello, World. > " > > O.k.Then, I entered the following URL in my web browser " > http://192.168.1.77/var/hello_world.pl";, but of course it did not work. Do > I have to add a port or do I have to save it onto the hard-disc of my > computer and call it remote from the NSLU > > ANYWAY, I'M WILLING TO LEARN AND UNDERSTAND THE SYSTEM, BUT I HAVE ABSOLUTE > NO IDEA ABOUT ANY BASICS OF THIS "CGI" AND I HAVE NO IDEA IF I HAVE TO USE > THE "REBOL" OR THE "APACHE" CODE OR WHATEVER IT IS OR WHATEVER ELSE AND I > HAVE ABSOLUTELY NO IDEA WHERE TO START THE PROGRAM AND WHERE TO SEARCH IN > THE INTERNET FOR IT. > No need to yell. CGI basics: 1. Write an executable program that produces a "Content-Type:..." header and two newlines. CHECK 2. Give executable permissions for the webserver (usually wwwrun) to it. Making it executable to anyone works, too. 3. Place the executable in a place where the web server finds it. If you run apache, this usually is /cgi-bin/ 4. Enable CGI extension and the /cgi-bin/ path in the webserver config. You should read the web servers documentation to find out how to do it. 5. Restart the Webserver/make it reload it's configuration. 6. Type http:///cgi-bin/hello_world.pl BTW: CGI does work with any programming language -- it's named *C*ommon *G*ateway *I*nterface. If you don't feel comfy with perl, you can choose any other language you like. Kind regards Jan -- We are Linux. Resistance is measured in Ohms. pgpiB5P3FUP6V.pgp Description: PGP signature - 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] Fwd: Simple perl program
Am Donnerstag, 13. März 2008 02:07 schrieb Paul Alfille: > > Jan, sorry, I didn't understand anything you tried to explain to me. > 1. What's a "Content-Type:..." header and what does mean "CHECK". > That's what you already have done. CHECK -- to check -> "abhaken". > 2. What is "wwwrun", a certain file in a certain folder and if so, where it > is placed in the NSLU or on my PC? > This is a user name. The web server usually runs with a user different than root for security concerns. On the NSLU, it may be root -- check the NSLU documentation. > 3. As far as I know, I have no web SERVER, do I? I have only a web BROWSER > named Firefox. By the way, I don't know what "Apache" is. > You need a web server to give your browser data. Otherwise, the browser would just display an error page when trying to access the NSLU with http:///... Apache is a popular web server. On the NSLU, apache is not used for size reasons, it's rather big -- sorry for the wrong info. Instead, the "cherokee" (pun intended!) web server is used. The configuration syntax is nearly identical, though. See http://www.cherokee-project.com/doc/ > 4. What do you mean by "enable an extension"? I'm used to files which HAVE > a certain extension, the thing after the full stop, e.g. ".mp3" or ".jpg". > Did you mean I should create an extension, that the file gets the name > "test.cgi" for instance? > A web server extension -- this is a small program part loaded on demand (for size reasons). Throw away all the MS windows terms you know when working with Linux -- they will lead you into utter confusion. > So, after all, do you have a more concrete example for me? As I said, I > have this "Unslung 6.8" running on my "NSLU2" with also a running "OWFS > 2.7" on it. It's IP address is "192.168.1.77". Over Ethernet I'm connected > to a PC with Windows XP and Firefox. Does this help you? > First, add Linux to your PC and learn some Linux basics. It's possible to *use* the NSLU distribution without knowing Linux, but if you want to tweak it, e.g. to do some OWFS magic, you have to know the basics. Otherwise, we'll be spinning around easy stuff explaining Linux basics and get exhausted before we come to the interesting topics. Once you installed Linux, the *very* first lesson is to feed a search engine with the right questions and read the documentation. Kind regards Jan -- Das Schöne an Windows NT ist: Es stürzt nicht einfach ab. Es zeigt einen Dialog an und lässt dich den Absturz mit 'OK' bestätigen. pgpQsAwfCVdlJ.pgp Description: PGP signature - 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] Udev rules for openSuSE 11
Hello,
I recently had time again to focus my efforts on owfs. I found out the Udev
rules I once posted do no longer work on openSuSE 11.
I made up the following new rule, which has to be placed into a new file
/etc/udev/rules.d/46-ds2490.rules or similar (just make sure it's before
50-udev-default.rules)
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
ATTRS{idVendor}=="04fa", ATTRS{idProduct}=="2490",
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", GROUP="ow", MODE="0664"
All on one line, as before.
I think the owfs wiki page http://owfs.org/index.php?page=udev-and-usb
should be changed/extended to reflect this change in openSuSE udev.
Kind regards
Jan
--
beta test, v:
To voluntarily entrust one's data, one's livelihood and one's
sanity to hardware or software intended to destroy all three.
In earlier days, virgins were often selected to beta test volcanos.
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] OWFS "forgets" chips after a while.
Hello, I found a problem (at least for me) with owfs' cache a while ago I'd like to fix. Tried with owtcl: % OW::get uncached 29.E5340100/,bus.0/,bus.1/,bus.2/,bus.3/,bus.4/,bus.5/,bus.6/,bus.7/,settings/,system/,statistics/,structure/,alarm/ % OW::put 29.E5340100/PIO.BYTE 161 % OW::put 29.E5340100/PIO.BYTE 161 Ok, now I wait a long while... % OW::put 29.E5340100/PIO.BYTE 161 invalid argument % OW::get uncached/29.E5340100 LCD_H/,LCD_M/,PIO.BYTE,PIO.ALL,PIO.0,PIO.1,PIO.2,PIO.3,PIO.4,PIO.5,PIO.6,PIO.7,address,crc8,family,id,latch.BYTE,latch.ALL,latch.0,latch.1,latch.2,latch.3,latch.4,latch.5,latch.6,latch.7,locator,por,power,present,r_address,r_id,r_locator,sensed.BYTE,sensed.ALL,sensed.0,sensed.1,sensed.2,sensed.3,sensed.4,sensed.5,sensed.6,sensed.7,set_alarm,strobe,type % OW::put 29.E5340100/PIO.BYTE 161 invalid argument % OW::put uncached/29.E5340100/PIO.BYTE 161 invalid argument % OW::get uncached/29.E5340100/PIO.ALL invalid argument % OW::get uncached 29.E5340100/,bus.0/,bus.1/,bus.2/,bus.3/,bus.4/,bus.5/,bus.6/,bus.7/,settings/,system/,statistics/,structure/,alarm/ % OW::put 29.E5340100/PIO.BYTE 161 % OW::get uncached/29.E5340100/PIO.ALL 1,0,0,0,0,1,0,1 % Hmm. It seems it's neccessary to issue OW::get uncached once in a while. That's not good, as I have a DS2482 adapter here and scanning the bus takes a couple of seconds with even only a few chips connected. I'd like to have it the way OWFS never "forgets" which chips are on the bus. Which setting do I have to tune? I tried Kind regards Jan -- I will never trust someone called GATES that sells WINDOWS. -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS "forgets" chips after a while.
Am Samstag, 7. Februar 2009 schrieb Jan Kandziora: > > I'd like to have it the way OWFS never "forgets" which chips are on the > bus. Which setting do I have to tune? I tried > Ok, I found out writing a large value to /settings/timeout/presence will disable this feature. Setting it to "0" for "off" or to -1 seems more straighforward to me. Seems the updated manpages have not been installed when I typed "make install". Must investigate. Kind regards Jan -- "When you say 'I wrote a program that crashed Windows', people just stare at you blankly and say 'Hey, I got those with the system, *for free*'." -- Linus Torvalds -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS "forgets" chips after a while.
Am Montag, 9. Februar 2009 schrieb Paul Alfille: > > What version are you using? > Latest CVS. I made an update recently. > The expected response is that calling OW::put 29.E5340100/PIO.BYTE 161 > would check the presence of 29.E5340100 (rebuilding the presence in > cache) before doing the write. > Originally, I expected that, too. Kind regards Jan -- Linux, Playboy Edition: nichts als die nackte Kommandozeile... -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Bugs with I2C
Hello Paul (and others), I'm currently testing my onewire installation with owtcl and an I2C adapter. It works more or less. I found out there is a nasty bug which is triggered by OW::finish, but *only* for the DS2482 I2C adapter, not DS9490 or DS9097U, which I tested, too. So I doubt it's a problem with owtcl, should be inside owlib. Please see the attached Tcl script and log. Start with ./ow_finish_bug /dev/i2c-6 or similar to try yourself. /dev/ttyS0 or usb for other adapter work, too, and don't show the bug. I used CVS from last week for this test. Kind regards Jan -- Es ist zehn Uhr abends... Wissen Sie, wo ihre Quellcodes sind? DEBUG: FS_OWQ_create of uncached CALL: PARSENAME path=[uncached] DEBUG: In FS_dir(uncached) CALL: DIRECTORY path=uncached DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=0 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=7 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=1 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=2 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=3 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=4 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached d
Re: [Owfs-developers] Fwd: [Owfs-forums] [owfs - Help] Problem with DS2482-800 and cable >50meters
Am Dienstag, 10. Februar 2009 schrieb Paul Alfille: > > I looked at the DS2482-100 Datasheet > http://datasheets.maxim-ic.com/en/ds/DS2482-800-DS2482S-800.pdf > > I see the discussion on page 6 of Active Pullup. I must admit I didn't > realize APU didn't require external hardware. > On DS2482-100, it does! The DS2482-100 has an output for driving an external power MOSFET which does the active pullup in any strength you like. The DS2482-800 has active pullup circuits, too, but they are limited in strength due to the power dissipation of the chip. > Activating APU is trivial, just changing a bit in the code. Is there any > reason to make this an option? What is the downside to APU? Will it break > existing implementations? > Active pullup should introduce more reflections into short-range networks, that's why the datasheet says it's only for long lines. If active pullup is activated, one may need a "long line simulator" (resistor/capacitator). > We could create a command line option, but I like to add options only if > there is a reason to choose. > I would generally activate it. If there were any problems, the should have arised with the DS9490 adapter. Kind regards Jan -- A bug in the code is worth two in the documentation. signature.asc Description: This is a digitally signed message part. -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Bugs with I2C
Am Dienstag, 10. Februar 2009 schrieb Jan Kandziora: > Hello Paul (and others), > I found another bug with I2C. % package require ow % OW::init /dev/i2c-6 % OW::set_error_level 9 % OW::set_error_print 2 % OW::get alarm gives DEBUG: FS_OWQ_create of alarm CALL: PARSENAME path=[alarm] DEBUG: In FS_dir(alarm) CALL: DIRECTORY path=alarm DEBUG: ALARM directory DEBUG: Selecting a path (and device) path=alarm SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=7 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: FS_alarmdir BUS_first_alarm = -19 DEBUG: Return from ALARM is 0 DEBUG: FS_dir_both out ret=0 Speicherzugriffsfehler (Segmentation fault) Again, I'm able to reproduce this only for I2C adapter, not DS9490 or DS9097U. It's irregardless whether there is any alarmed chip or not. I can reproduce it with owserver, too: $ /opt/owfs/bin/owserver --error_level=9 --error_print=2 --foreground /dev/i2c-6 gives the attached log whenever I'm reading "alarm". Kind regards Jan -- "When you say 'I wrote a program that crashed Windows', people just stare at you blankly and say 'Hey, I got those with the system, *for free*'." -- Linus Torvalds CONNECT: Found an i2c device at /dev/i2c-6 address 24 DEBUG: DS2482 read status ok CONNECT: i2c device at /dev/i2c-6 address 24 appears to be DS2482-x00 CONNECT: DS2482-800 (Eight channels). DEBUG: main_threadid = 3083720384 DEBUG: ServerProcessOut = 3083332496 DEBUG: Wait for output device 0 to setup. DEBUG: OW_Announce: end DEBUG: Output device setup is done. index=0 DEBUG: ServerProcessAccept [3083332496] try lock 0 DEBUG: ServerProcessAccept [3083332496] locked 0 DEBUG: Output device 0 setup done. DEBUG: ServerProcessAccept [3083332496] accept 0 fd=9 DEBUG: ServerProcessAcceptUnlock: unlock 3083332496 DEBUG: ServerProcessAcceptUnlock: unlock 3083332496 done DEBUG: ServerProcessAccept [3083332496] unlock 0 DEBUG: NetRead attempt 24 bytes Time:(10,0) Byte buffer NETREAD, length=24 --000: 00 00 00 00 00 00 00 09 00 00 00 04 00 00 01 05 --016: 00 00 00 00 00 00 00 00 <> DEBUG: tcp_read n=24 nleft=0 n-nleft=24 DEBUG: FromClient payload=9 size=0 type=4 sg=0x105 offset=0 DEBUG: FromClient (no servermessage) payload=9 size=0 type=4 sg=0x105 offset=0 DEBUG: NetRead attempt 9 bytes Time:(10,0) Byte buffer NETREAD, length=9 --000: 75 6E 63 61 63 68 65 64 00 DEBUG: tcp_read n=9 nleft=0 n-nleft=9 DEBUG: Persistence requested CALL: DataHandler: parse path=uncached DEBUG: FS_OWQ_create of uncached CALL: PARSENAME path=[uncached] CALL: Directory message (one at a time) CALL: DirHandler: pn->path=uncached DEBUG: OWSERVER SpecifiedBus=0 path=uncached DEBUG: In FS_dir_remote(uncached) CALL: DIRECTORY path=uncached DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DEBUG: DS2482 read status ok ServerProcessAccept = 3083332496 CLOSING DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: ServerProcessAccept [3083332496] try lock 0 DEBUG: ServerProcessAccept [3083332496] locked 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=0 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and device) path=uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: DS2482 read status ok DEBUG: DS2482 read status ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DEBUG: DS2482 read status ok DEBUG: DS2482 Reset DEBUG: BUS_next return = -19 | 00 00 00 00 00 00 00 00 DEBUG: Cache_Add_Device 00 00 00 00 00 00 00 00 bus=1 DEBUG: Add to cache sn 00 00 00 00 00 00 00 00 pointer=(nil) index=-1 size=4 DEBUG: Start of directory path=uncached device=00 00 00 00 00 00 00 00 DEBUG: BUS_first: Empty bus -- no presence pulse DEBUG: Selecting a path (and d
Re: [Owfs-developers] Bugs with I2C
Am Dienstag, 10. Februar 2009 schrieb Paul Alfille: > Found a rather embarrassing error. The cleanup routine didn't have a break > at the end of the switch for the i2c adapter, so tried to clean up a > different adapter as well. > Ok. Thanks for fixing it so quickly. > I'll make a new release. > Today I found another I2C related bug. Please see my other posting in this thread. Maybe the same error source? Should I test more? Kind regards Jan -- Who is General Protection Fault and why is he reading my hard disk? -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Bugs with I2C
Am Mittwoch, 11. Februar 2009 schrieb Paul Alfille: > You log file doesn't show the Speicherzugriffsfehler. > Yes. Unlike with the other bug, I did not get a trace from glibc. I just have made a valgrind --leak-check=full --show-reachable=yes ./ow_alarm_bug.tcl /dev/i2c-6 Please see the attached script and log. Kind regards Jan -- There's light at the other end of the the Windows. #!/usr/bin/tclsh package require ow eval OW::init $argv OW::set_error_level 9 OW::set_error_print 2 OW::get alarm ==15309== Memcheck, a memory error detector. ==15309== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==15309== Using LibVEX rev 1804, a library for dynamic binary translation. ==15309== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==15309== Using valgrind-3.3.0, a dynamic binary instrumentation framework. ==15309== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==15309== For more details, rerun with: -v ==15309== ==15309== Conditional jump or move depends on uninitialised value(s) ==15309==at 0x401623A: (within /lib/ld-2.8.so) ==15309==by 0x42875C3: (within /lib/libc-2.8.so) ==15309==by 0x4287989: _dl_sym (in /lib/libc-2.8.so) ==15309==by 0x4159DE7: (within /lib/libdl-2.8.so) ==15309==by 0x400DE25: (within /lib/ld-2.8.so) ==15309==by 0x415A0DB: (within /lib/libdl-2.8.so) ==15309==by 0x4159D72: dlsym (in /lib/libdl-2.8.so) ==15309==by 0x413494C: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40E990D: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40EFB57: (within /usr/lib/libtcl8.5.so) ==15309==by 0x407625A: (within /usr/lib/libtcl8.5.so) ==15309==by 0x4076E4E: (within /usr/lib/libtcl8.5.so) ==15309== ==15309== Conditional jump or move depends on uninitialised value(s) ==15309==at 0x4016245: (within /lib/ld-2.8.so) ==15309==by 0x42875C3: (within /lib/libc-2.8.so) ==15309==by 0x4287989: _dl_sym (in /lib/libc-2.8.so) ==15309==by 0x4159DE7: (within /lib/libdl-2.8.so) ==15309==by 0x400DE25: (within /lib/ld-2.8.so) ==15309==by 0x415A0DB: (within /lib/libdl-2.8.so) ==15309==by 0x4159D72: dlsym (in /lib/libdl-2.8.so) ==15309==by 0x41349B2: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40E990D: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40EFB57: (within /usr/lib/libtcl8.5.so) ==15309==by 0x407625A: (within /usr/lib/libtcl8.5.so) ==15309==by 0x4076E4E: (within /usr/lib/libtcl8.5.so) ==15309== ==15309== Conditional jump or move depends on uninitialised value(s) ==15309==at 0x4016251: (within /lib/ld-2.8.so) ==15309==by 0x42875C3: (within /lib/libc-2.8.so) ==15309==by 0x4287989: _dl_sym (in /lib/libc-2.8.so) ==15309==by 0x4159DE7: (within /lib/libdl-2.8.so) ==15309==by 0x400DE25: (within /lib/ld-2.8.so) ==15309==by 0x415A0DB: (within /lib/libdl-2.8.so) ==15309==by 0x4159D72: dlsym (in /lib/libdl-2.8.so) ==15309==by 0x413494C: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40E990D: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40EFB57: (within /usr/lib/libtcl8.5.so) ==15309==by 0x407625A: (within /usr/lib/libtcl8.5.so) ==15309==by 0x4076E4E: (within /usr/lib/libtcl8.5.so) ==15309== ==15309== Conditional jump or move depends on uninitialised value(s) ==15309==at 0x401625C: (within /lib/ld-2.8.so) ==15309==by 0x42875C3: (within /lib/libc-2.8.so) ==15309==by 0x4287989: _dl_sym (in /lib/libc-2.8.so) ==15309==by 0x4159DE7: (within /lib/libdl-2.8.so) ==15309==by 0x400DE25: (within /lib/ld-2.8.so) ==15309==by 0x415A0DB: (within /lib/libdl-2.8.so) ==15309==by 0x4159D72: dlsym (in /lib/libdl-2.8.so) ==15309==by 0x413494C: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40E990D: (within /usr/lib/libtcl8.5.so) ==15309==by 0x40EFB57: (within /usr/lib/libtcl8.5.so) ==15309==by 0x407625A: (within /usr/lib/libtcl8.5.so) ==15309==by 0x4076E4E: (within /usr/lib/libtcl8.5.so) ==15309== ==15309== Invalid read of size 4 ==15309==at 0x4016230: (within /lib/ld-2.8.so) ==15309==by 0x4159C0E: (within /lib/libdl-2.8.so) ==15309==by 0x400DE25: (within /lib/ld-2.8.so) ==15309==by 0x415A0DB: (within /lib/libdl-2.8.so) ==15309==by 0x4159B40: dlopen (in /lib/libdl-2.8.so) ==15309==by 0x4755F53: DL_open (ow_dl.c:23) ==15309==by 0x47560AE: OW_Load_dnssd_library (ow_dnssd.c:117) ==15309==by 0x4781CDE: LibSetup (ow_lib_setup.c:28) ==15309==by 0x476DD4A: API_setup (ow_api.c:48) ==15309==by 0x470D885: OW_init (owcapi.c:59) ==15309==by 0x4709184: Owtcl_Connect (ow.c:120) ==15309==by 0x407625A: (within /usr/lib/libtcl8.5.so) ==15309== Address 0x45f1998 is 56 bytes inside a block of size 58 alloc'd ==15309==at 0x4024D5E: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==15309==by 0x400DF47: (within /lib/ld-2.8.so) ==15309==by 0x4008B1D: (within /lib/ld-2.8.so) ==15309==by 0x4012026: (within /lib/ld-2.8.so) ==15309==by 0x400DE25:
Re: [Owfs-developers] Bugs with I2C
Am Mittwoch, 11. Februar 2009 schrieb Paul Alfille: > I looked at the log -- nothing remarkable. A memory leak of 36 bytes was > nice to find. > > Can you test the newer version and see if the problem persists? > With latest CVS from CET 17:00 I get: % OW::get uncached 29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,bus.7/,bus.6/,bus.5/,bus.4/,bus.3/,bus.2/,bus.1/,bus.0/,settings/,system/,statistics/,structure/,alarm/ The chip is surely only on bus.0, I'm using a DS2482-800. The "alarm" bug seems to have gone "a little". I can list "alarm" % OW::get alarm 29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,29.E5340100/,uncached/ % OW::put 29.E5340100/por 0 % OW::get alarm uncached/ % OW::get alarm/uncached Segmentation fault Uh oh. And OW::finish still segfaults. Result snipped now: DEBUG: ParsedName_destroy uncached/structure CALL: PARSENAME path=[uncached/alarm] DEBUG: ParsedName_destroy uncached/alarm DEBUG: FS_dir_both out ret=0 DEBUG: FS_OWQ_destroy of uncached DEBUG: ParsedName_destroy uncached CALL: Clear Cache CALL: Closing input devices *** glibc detected *** /usr/bin/tclsh: double free or corruption (fasttop): 0x09066a60 *** === Backtrace: = /lib/libc.so.6[0xb7e72fc4] /lib/libc.so.6(cfree+0x9c)[0xb7e7495c] /opt/owfs/lib/libow-2.7.so.14(FreeIn+0x8c)[0xb7d35b2c] /opt/owfs/lib/libow-2.7.so.14(FreeInAll+0x34)[0xb7d35e84] /opt/owfs/lib/libow-2.7.so.14(LibStop+0x72)[0xb7d44f92] /opt/owfs/lib/libow-2.7.so.14(API_finish+0x3f)[0xb7d30e2f] /opt/owfs/lib/libowcapi-2.7.so.14(OW_finish+0x17)[0xb7dc41e7] /usr/lib/tcl/owtcl-0.2/ow.so(Owtcl_Delete+0x26)[0xb80836b6] /usr/lib/libtcl8.5.so[0xb7f9c25b] /usr/lib/libtcl8.5.so[0xb7f9ce4f] /usr/lib/libtcl8.5.so(Tcl_EvalEx+0x2e)[0xb7f9d6fe] /usr/lib/libtcl8.5.so(Tcl_FSEvalFileEx+0x14f)[0xb800db5f] /usr/lib/libtcl8.5.so(Tcl_Main+0x392)[0xb8016962] /usr/bin/tclsh(main+0x39)[0x8048759] /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e1d5f5] /usr/bin/tclsh[0x8048621] Kind regards Jan -- Vor Onboard-Grafik sollte man mit Aufklebern wie auf Zigarettenschachteln warnen... -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Bugs with I2C
Am Mittwoch, 11. Februar 2009 schrieb Paul Alfille: > Just fixed the error in the DS2482_channel_select logic. Can you retry from > the CVS? > I found a stray character in CVS code, fixed it myself, uploaded it. Bus selection just works fine now, the other errors remain. Next one: % OW::get bus.0/alarm segfaults, too. Kind regards Jan -- Neue Erfindungsbäume für Civilisation: Internet | | Cola--+ +--Tiefkühlpizza -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] OWFS "forgets" chips after a while.
Am Mittwoch, 11. Februar 2009 schrieb Paul Alfille: > > and I need to re-read it several times with owhttpd to make it > > available. All other devices are retained. When the 2408 disappears it > > is no longer available to php or perl. Any suggestions? Also how can I > > Suggestions? I need to fix it. Is it only "writes" that are a problem? > I'd tested some more with my setup. Exactly 600 seconds after reading "uncached", writing to a node by % OW::put 29.xx/PIO.BYTE 255 fails (which a catchable error). I set % OW::put settings/timeout/presence 1000 % OW::put settings/timeout/directory 1000 or to even larger numbers, but the 600 seconds remain. Which timeout do I have to change? Kind regards Jan -- Alles Schwere kommt von oben... -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Problem with /alarm and latest CVS
Hello, I recently returned to the onewire part of my project and I'm still hunting bugs... With latest CVS version, /alarm or even /alarm/uncached are always empty. I *know* the DS2408 connected to the bus *must* be in alarm state after power up, so there has to be something wrong with my software setup or recent owfs (it worked with CVS from January). I checked with # /opt/owfs/bin/owserver --foreground --error_level=9 --error_print=2 /dev/ttyS0 2>alarm_log and # /opt/owfs/bin/owget alarm/uncached Please see the attached log. Anyone else having problems with this? Adapter is DS9097U, if that matters. Kind regards Jan -- Linux, Playboy Edition: nichts als die nackte Kommandozeile... CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[] DEBUG: owlib.c:SetupTemperatureLimits(83) Globals temp limits 0C 100C (for simulated adapters) CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[] Byte buffer Attempt serial write:, length=1 --000: C1 <.> Byte buffer Attempt serial write:, length=1 --000: 71 Byte buffer Attempt serial write:, length=1 --000: 0F <.> Byte buffer Serial read:, length=1 --000: 00 <.> Byte buffer Attempt serial write:, length=1 --000: C5 <.> Byte buffer Serial read:, length=1 --000: CD <.> Byte buffer Attempt serial write:, length=1 --000: 71 Byte buffer Attempt serial write:, length=1 --000: 0F <.> Byte buffer Serial read:, length=1 --000: 00 <.> Byte buffer Attempt serial write:, length=1 --000: C5 <.> Byte buffer Serial read:, length=1 --000: CD <.> Byte buffer Attempt serial write:, length=1 --000: 45 Byte buffer Serial read:, length=1 --000: 44 Byte buffer Attempt serial write:, length=1 --000: 5B <[> Byte buffer Serial read:, length=1 --000: 5A Byte buffer Attempt serial write:, length=1 --000: 3F Byte buffer Serial read:, length=1 --000: 3E <>> Byte buffer Attempt serial write:, length=1 --000: 29 <)> Byte buffer Serial read:, length=1 --000: 28 <(> Byte buffer Attempt serial write:, length=1 --000: 95 <.> Byte buffer Serial read:, length=1 --000: 97 <.> Byte buffer Attempt serial write:, length=1 --000: C5 <.> Byte buffer Serial read:, length=1 --000: CD <.> DEBUG: owserver.c:main(158) main_threadid = 3085231808 DEBUG: ow_net_server.c:ServerProcessOut(252) 3084843920 DEBUG: ow_zero.c:OW_Announce(150) end DEBUG: ow_net_server.c:ServerProcess(321) Wait for output device 0 to setup. DEBUG: ow_net_server.c:ServerProcessOut(273) Output device setup is done. index=0 DEBUG: ow_net_server.c:ServerProcessAccept(189) [3084843920] try lock 0 DEBUG: ow_net_server.c:ServerProcessAccept(195) [3084843920] locked 0 DEBUG: ow_net_server.c:ServerProcess(324) Output device 0 setup done. DEBUG: ow_net_server.c:ServerProcessAccept(203) [3084843920] accept 0 fd=8 DEBUG: ow_net_server.c:ServerProcessAcceptUnlock(177) unlock 3084843920 DEBUG: ow_net_server.c:ServerProcessAcceptUnlock(179) unlock 3084843920 done DEBUG: ow_net_server.c:ServerProcessAccept(216) [3084843920] unlock 0 DEBUG: ow_tcp_read.c:tcp_read(60) attempt 24 bytes Time:(10,0) Byte buffer NETREAD, length=24 --000: 00 00 00 00 00 00 00 0F 00 00 00 07 00 00 01 0A --016: 00 00 00 00 00 00 00 00 <> DEBUG: ow_tcp_read.c:tcp_read(108) n=24 nleft=0 n-nleft=24 DEBUG: from_client.c:FromClient(65) FromClient payload=15 size=0 type=7 sg=0x10A offset=0 DEBUG: from_client.c:FromClient(73) FromClient (no servermessage) payload=15 size=0 type=7 sg=0x10A offset=0 DEBUG: ow_tcp_read.c:tcp_read(60) attempt 15 bytes Time:(10,0) Byte buffer NETREAD, length=15 --000: 61 6C 61 72 6D 2F 75 6E 63 61 63 68 65 64 00 DEBUG: ow_tcp_read.c:tcp_read(108) n=15 nleft=0 n-nleft=15 CALL: data.c:DataHandler(102) DataHandler: parse path=alarm/uncached DEBUG: ow_parseobject.c:FS_OWQ_create(26) alarm/uncached CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[alarm/uncached] CALL: data.c:DataHandler(145) Directory message (all at once) DEBUG: dirall.c:DirallHandler(66) OWSERVER Dir-All SpecifiedBus=0 path = /alarm/uncached DEBUG: ow_dir.c:FS_dir_remote(74) path=/alarm/uncached CALL: ow_dir.c:FS_dir_both(102) path=/alarm/uncached DEBUG: ow_select.c:BUS_select(71) Selecting a path (and device) path=/alarm/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(78) Clearing root branch Byte buffer Attempt serial write:, length=1 --000: C5 <.> DEBUG: ow_net_server.c:ServerProcessAccept(243) 3084843920 CLOSING DEBUG: ow_net_server.c:ServerProcessAccept(189) [3084843920] try lock 0 DEBUG: ow_net_server.c:ServerProcessAccept(195) [3084843920] locked 0 Byte buffer Serial read:, length=1 --000: CD <.> Byte buffer Attempt serial write:, length=3 --000: E1 CC 66 <..f> Byte buffer Serial read:, length=2 --000: CC 66 <.f> DEBUG: ow_transaction.c:BUS_transaction_single(98) send = 0 DEBUG: ow_transaction.c:BUS_transaction_
Re: [Owfs-developers] Problem with /alarm and latest CVS
Am Freitag, 8. Mai 2009 schrieb Jan Kandziora: > > I recently returned to the onewire part of my project and I'm still hunting > bugs... With latest CVS version, /alarm or even /alarm/uncached are always > empty. I *know* the DS2408 connected to the bus *must* be in alarm state > after power up, so there has to be something wrong with my software setup > or recent owfs (it worked with CVS from January). I checked with > To my curiosity, today it works as expected. What the heck...? If anyone could explain from the log what went wrong yesterday, I'd be very happy. Kind regards Jan -- 1) Never draw what you can copy. 2) Never copy what you can trace. 3) Never trace what you can cut out and paste down. signature.asc Description: This is a digitally signed message part. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problem with /alarm and latest CVS
Am Samstag, 9. Mai 2009 schrieb Jan Kandziora: > > To my curiosity, today it works as expected. What the heck...? If anyone > could explain from the log what went wrong yesterday, I'd be very happy. > I think I have it now: If one is reading the alarm/ directory and no chip is in alarm state, OWFS returns EIO. owtcl returns that EIO instead of an empty reply. Is that expected behavior? I would find it more useful to have an empty reply to distinguish from "real I/O errors". Kind regards Jan -- ...very few phenomena can pull someone out of Deep Hack Mode, with two noted exceptions: being struck by lightning, or worse, your *computer* being struck by lightning. -- Matt Welsh signature.asc Description: This is a digitally signed message part. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] Revisited: OWFS "forgets" chips after a while.
Hello, A while ago, I found out owfs "forgets" chips after exactly 600 seconds, regardless which timeouts I set, and how. Now I found out this only happens with my DS2482-800 i2c adapter, not with a DS9097U I tried recently. Odd. Any idea what's different with DS2482-800? Kind regards Jan -- I will never trust someone called GATES that sells WINDOWS. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Revisited: OWFS "forgets" chips after a while.
Am Montag, 11. Mai 2009 schrieb Paul Alfille: > Is it possible to list a short log? > > Also, is settings/timeout/presence set to what you expect? > I'll provide a test case and log tomorrow. Kind regards Jan -- A closed mouth gathers no foot. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Montag, 11. Mai 2009 schrieb Paul Alfille:
> Is it possible to list a short log?
>
> Also, is settings/timeout/presence set to what you expect?
>
Pew, it was a hard time to catch that bug... It does *not* happen with
DS9097U, only with my DS2482 adapter. Please see the following tcl script. I
run it 10 minutes before it shows "invalid argument" instead of "OK".
--
#!/usr/bin/tclsh
package require ow
set CHIP 29.D43E0100
OW::init /dev/i2c-6
OW::put settings/timeout/presence 1200
OW::put settings/timeout/directory 1200
puts stderr [ OW::get uncached ]
while { true } \
{
puts -nonewline stderr "[ clock format [ clock seconds ] ]: "
OW::get /uncached/simultaneous/single_ds2400
if {[ catch { OW::put $CHIP/PIO.ALL 0,0,0,0,0,0,0,0 } ERR ]} \
{ puts stderr $ERR } \
{ puts stderr "OK" }
after 1
}
--
If I leave out the "OW::get /uncached/simultaneous/single_ds2400" line, the
bug does not appear. "invalid argument" is then showed after 1200s, as noted
in the initialisation. Adding
OW::put settings/timeout/stable 1200
OW::put settings/timeout/volatile 1200
after OW::init makes no difference.
I could not take a log with owserver, as it would ignore my timeout settings
completely and fail after 2 minutes.
Kind regards
Jan
--
A bureaucrat's idea of cleaning up his files
is to make a copy of everything before he destroys it.
signature.asc
Description: This is a digitally signed message part.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Donnerstag, 14. Mai 2009 schrieb Paul Alfille: > I found an obscure bug in the device cache code. Can you test? > I tried it, but no change. Kind regards Jan -- TkKasse will not run on any kind of MS-Windows. It can be adapted to do so but I won't do it, as most Microsoft customers are expecting software to be broken, and TkKasse isn't. I can't break it just for the sake of compatibility to these people's mindset. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 1-wire wiring question -- hope it's not OT
Am Donnerstag, 14. Mai 2009 schrieb Rob Fugina: > I need to get some 1-wire weather instruments mounted away from my > house, on a post about 75 ft away. This worries me because of how the > system basically becomes an antenna. Nearby lightning strikes would > wreak havok back at the bus master. > A lightning striking a pole only ~25m away would shift earth level very much and damage most of your computer equipment anyway. It makes no sense just to protect one input -- You'll have to protect all inputs, especially the mains. Where exactly do you live? A single house or an urban area? Are thunderstorms frequent? How dry is the soil at your area? These are important questions if you ask how to protect your equipment from lightning. Kind regards Jan -- You cannot achieve the impossible without attempting the absurd. signature.asc Description: This is a digitally signed message part. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] 1-wire wiring question -- hope it's not OT
Am Donnerstag, 14. Mai 2009 schrieb Rob Fugina: > > Ok, you're right, and I'm not really trying to protect myself from a > direct strike. But having a 75m antenna sticking out into my back > yard > 75m band, I think? If it is really 75m high, someone should already have done deep thinking about lightning... > does seem to be asking for nearby lightning, or overhead > lightning, to induce significant current in that wire -- or am I > wrong? > No, you are pretty right. But it's just the way a direct lightning strike will damage any electronic equiment in a range of ~50m, regardless of protective circuits. It just runs over any surface and grasps any kind of conductor. Optocouplers are no match for lightning -- it just made it about 2kms down to earth, so 2mm would be no problem, right?. The only chance to protect against direct strikes is proper earthing. Wet soil and rings of metal buried deep into the ground, if possible connected to ground water. That way, the "range of destruction" can be shrinked to about ~10m around the pole. So I don't think the optocouplers in the AAG equipment are for lightning protection. They are for ground separation -- otherwise there would be a noise-inducing ground loop between the PC, which *always* connects signal ground to protective earth (major design flaw) and an auxiliary-powered sensor outside. Kind regards Jan -- Williams and Holland's Law: If enough data is collected, anything may be proven by statistical methods. signature.asc Description: This is a digitally signed message part. -- 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] 1-wire wiring question -- hope it's not OT
Am Donnerstag, 14. Mai 2009 schrieb Rob Fugina: > > It'll be about 4m up. > A 4m pole made of wood will without much doubt *never* been hit by lightning... It's much more likely a 20m high tree nearby is hit (which alone is very unlikely) If you use a metal pole, a halved, tin foiled ball on the top of the pole should be enough to avoid any corona discharge and thus, lightning strikes. Kind regards Jan -- "The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language." -- 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] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Donnerstag, 14. Mai 2009 schrieb Paul Alfille: > I found an obscure bug in the device cache code. Can you test? > I managed to take a log with owserver /opt/owfs/bin/owserver --timeout_directory=1200 --timeout_presence=1200 --foreground --error_level=9 --error_print=2 /dev/i2c-6 1>log 2>&1 The first 10 actions result in "ok", the last two actions result in "invalid argument" Kind regards Jan -- The number of arguments is unimportant unless some of them are correct. -- Ralph Hartley log.gz Description: GNU Zip compressed data -- 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] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Montag, 18. Mai 2009 schrieb Paul Alfille: > Jan, I'm still analyzing your logs. I did find a bug in the > simultaneous/single code, and fixed it in the CVS. Can you try a quick test > of the newest code to see if the problem persists? > The problem is still there. Please see the new log (10 times ok, last time failed). Kind regards Jan -- beta test, v: To voluntarily entrust one's data, one's livelihood and one's sanity to hardware or software intended to destroy all three. In earlier days, virgins were often selected to beta test volcanos. log.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part. -- 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] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Montag, 18. Mai 2009 schrieb Paul Alfille: > I really appreciate the time and effort you spend testing and filing bug > reports! > Oh, once I nailed a problem down to a simple test case, I always hope my work is nearly done... It took several hours to find out the /simultaneous/... was the culprit, as the bug originally happened in a far bigger program. If I can do some more quick tests, feel free to send code snippets to me, I will patch them into my CVS image. I just feel a little awkward when I try to understand the whole caching code, it's very hard to get through it. Kind regards Jan -- Vor Onboard-Grafik sollte man mit Aufklebern wie auf Zigarettenschachteln warnen... -- 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] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Samstag, 23. Mai 2009 schrieb Paul Alfille: > Jan, can you try again? I've cleaned up the handling of device presence, I > think any read/write error was causing problems. Still, I don't have your > setup to test. > Now I get a segmentation fault in the client application after 10 minutes. Please see the new owserver log (10 times ok, one time fail). Kind regards Jan -- Linux, Playboy Edition: nichts als die nackte Kommandozeile... log.gz Description: GNU Zip compressed data -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Rev isited: OWFS "forgets" chips after a whil e.
Am Sonntag, 24. Mai 2009 schrieb Christian Magnusson: > I haven't follows all latest updates, but I found one pointer bug in > ow_presence.c:ReCheckPresence() CheckThisConnection() should not have an > integer as in input-argument, it should be a connection_in pointer. I > haven't checked in the fix, but this might fix the problem. Perhaps Paul > can verify if this is how it was supposed to work. > Christian, Paul, we get nearer to function. I've added Christian's patch today and now I get an ENOENT after 10 minutes, while after 11 minutes, it works again. Same after 20 minutes and so on. Please see the log. Kind regards Jan -- Nice female voice: "You have *junk* mail." log.gz Description: GNU Zip compressed data -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Mittwoch, 27. Mai 2009 schrieb Paul Alfille: > > You are using simultaneous/single_ds2400 to get the single chip (a DS2408) > on the bus. > No. I'm actually looking for an iButton lock connected to the same bus. This way I can connect an arbitrary amount of "normal" onewire slaves and one single iButton to each bus without having them interfere and without (slow) scanning. Scanning is ultimately slow with DS2482. > That said, I wasn't properly checking the return result. Until now. > Ugh. Ok. > Can you try the newest code? > I will try tomorrow. Kind regards Jan -- Statistik ist eine Religion für alle, die so richtig überhaupt nichts in sich haben -- nicht einmal Verstand. -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Mittwoch, 27. Mai 2009 schrieb Paul Alfille: > > Can you try the newest code? > Ok. Two results: Good The OW::put $CHIP/PIO.ALL 0,0,0,0,0,0,0,0 works as expected now. Bad === The OW::get /uncached/simultaneous/single_ds2400 fails with EINVAL if no iButton is connected to the lock. The previous behaviour was returning an empty string in that case. I think it's not really an error if no iButton is connected to a lock. As EINVAL is given if something went wrong with the host adapter (e.g. pulled from the host), too, those errors are then obscured by catching the "no key connected" EINVAL. When caching is considered, things get even more complicated. One could argue, a failed read of /uncached/simultaneous/single should update the presence cache as no chips are connected to that bus. Anyway, for /uncached/simultaneous/single_ds2400 it should *not*, because only DS2400 and DS2401 (and iButtons) respond to that code. I really need it the way it is: Don't touch the presence cache. What do you think? Also bad OW::get alarm segfaults. Kind regards Jan -- ELIZA: You have a tendency to feel you are superior to most computers. -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Sonntag, 31. Mai 2009 schrieb Paul Alfille: > I'm not getting the OW::get problem on simple testing. > > We need to find the difference: > 1. What devices? > None. I found out the bug only appears if no device is in alarm state. I don't have the bug if there is a device to list. > 2. Which version of perl > I use owtcl-0.2 from latest CVS. With latest CVS, asking for uncached from owserver results in EIO, asking for alarm results in SIGSEGV. With direct connection to the interface, reading uncached works, reading alarm segfaults. > 3. Do you have a debug log from owserver? > Is attached. Kind regards Jan -- "If the future navigation system [for interactive networked services on the NII] looks like something from Microsoft, it will never work." -- Chairman of Walt Disney Television & Telecommunications CALL: ow_parsename.c:FS_ParsedName_anywhere(115) path=[] DEBUG: owlib.c:SetupTemperatureLimits(83) Globals temp limits 0C 100C (for simulated adapters) CONNECT: ow_ds2482.c:DS2482_detect_single(378) Found an i2c device at /dev/i2c-6 address 24 DEBUG: ow_ds2482.c:DS2482_readstatus(489) ok CONNECT: ow_ds2482.c:DS2482_detect_single(409) i2c device at /dev/i2c-6 address 24 appears to be DS2482-x00 CONNECT: ow_ds2482.c:HeadChannel(658) DS2482-800 (Eight channels). DEBUG: owserver.c:main(158) main_threadid = 3084379840 DEBUG: ow_net_server.c:ServerProcessOut(252) 3083991952 DEBUG: ow_zero.c:OW_Announce(150) end DEBUG: ow_net_server.c:ServerProcess(321) Wait for output device 0 to setup. DEBUG: ow_net_server.c:ServerProcessOut(273) Output device setup is done. index=0 DEBUG: ow_net_server.c:ServerProcessAccept(189) [3083991952] try lock 0 DEBUG: ow_net_server.c:ServerProcessAccept(195) [3083991952] locked 0 DEBUG: ow_net_server.c:ServerProcess(324) Output device 0 setup done. DEBUG: ow_net_server.c:ServerProcess(346) break signo=2 DEBUG: ow_net_server.c:ServerProcess(354) shutdown initiated DEBUG: ow_net_server.c:ServerProcess(358) Shutting down 0 of 1 thread 3083991952 DEBUG: ow_net_server.c:ServerProcess(372) pthread_kill (0 of 1) tid=3083991952 signo=15 rc=0 [Success] DEBUG: ow_net_server.c:ServerProcess(378) all threads cancelled DEBUG: ow_net_server.c:ServerProcess(382) join 3083991952 DEBUG: owserver.c:exit_handler(71) exit_handler: for signo=15, errno 0, code -6, pid=4152, self=3083991952 main=3084379840 DEBUG: owserver.c:exit_handler(76) exit_handler: shutdown already in progress. signo=15, self=3083991952, main=3084379840 DEBUG: ow_net_server.c:ServerProcessAccept(200) shutdown_in_progress [3083991952] accept 0 DEBUG: ow_net_server.c:ServerProcessAcceptUnlock(177) unlock 3083991952 DEBUG: ow_net_server.c:ServerProcessAcceptUnlock(179) unlock 3083991952 done DEBUG: ow_net_server.c:ServerProcessAccept(216) [3083991952] unlock 0 DEBUG: ow_net_server.c:ServerProcessAccept(220) [3083991952] shutdown_in_progress 0 return DEBUG: ow_net_server.c:ServerProcessOut(282) 3083991952 CLOSING () DEBUG: ow_net_server.c:ServerProcessOut(284) Normal exit. DEBUG: ow_net_server.c:ServerProcess(386) join 3083991952 done DEBUG: ow_net_server.c:ServerProcess(394) shutdown done DEBUG: owserver.c:main(163) ServerProcess done DEBUG: owserver.c:ow_exit(51) ow_exit 0 CALL: ow_lib_close.c:LibClose(21) Starting Library cleanup CALL: ow_lib_stop.c:LibStop(23) Clear Cache CALL: ow_lib_stop.c:LibStop(25) Closing input devices -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] /simultaneous bug was: Revisited: OWFS "forgets" chips after a while.
Am Sonntag, 31. Mai 2009 schrieb Paul Alfille: > Ahha. That's owcapi. Found the problem. Try it now. > Great, the alarm bug is away, too. The problem with reading uncached through owserver was just a misspelling, my failure. Case closed -- Thank You! Kind regards Jan -- The first law of demos: - never try to actually use the system for anything -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] I2C and One-Wire and OWFS
Am Donnerstag, 25. Juni 2009 schrieb Gregg C Levine: > > Now my question, how did one of us make use of the features on the DS2482 > on or around a motherboard to control the One-Wire access methods? > I use the Kontron KEEX-4000 motherboard as the base for my cash register. This board has the internal (SPD, sensors etc.) I2C bus available on one of its internal pin headers. I designed an adapter board which adds a DS2482 and four RJ-12 connectors which lead to my dispenser boards (featuring DS2423 counters and DS2408 for controlling valves). The most important feature for me was multiple ports. One port of the DS2482 is reserved for the local keylock, the other ports can be used for connecting buses for three different directions. It makes cabling easier than having several lobes. Then, a keylock can be identified on any of the 4 ports without using a link-locator or a DS2409 network coupler. I2C is also useful. The serial and USB ports on the cash register are already occupied by touchscreen, printers, coffee maker etc. I don't like to incorporate an USB hub into the machine just for having onewire. Kind regards Jan -- Berüchtigte Euphemismen: "Industriestandard" -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] I2C and One-Wire and OWFS
Am Freitag, 26. Juni 2009 schrieb Gregg C Levine: > That is as I remembered it, regarding the motherboard and its attachment. > But of course not the reasoning behind it. I, myself personally, haven't > chosen an appropriate motherboard for this project. > If your mainboard doesn't have a pin header for I2C, you can use the VGA or DVI output of your graphics adapter for that purpose. The DDC on that connector is plain I2C/SMBus. On the VGA connector, Pin 12 is SDA, Pin 15 is SCL and Pin5 is GND. On the DVI connector, Pin 7 is SDA, Pin 6 is SCL and Pin 15 is GND. As a bonus, +5V is on Pin 14 on this connector. Kind regards Jan -- "Are [Linux users] lemmings collectively jumping off of the cliff of reliable, well-engineered commercial software?" -- Matt Welsh -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Strange DS2450 behaviour
Am Freitag, 10. Juli 2009 schrieb Steinar Midtskogen: > None of the anemometers have external power. > Simultaneous conversion is not possible when on parasitic power. That's a limitation of the hardware. If OWW works, it just doesn't use simultaneous conversion. Kind regards Jan -- "...Deep Hack Mode -- that mysterious and frightening state of consciousness where mortal users fear to tread. -- Matt Welsh -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] USb adpater -fails every 2-3 weeks
Am Freitag, 31. Juli 2009 schrieb Rob Conway: > Does anyone else run owfs 24/7 with a USB 1wire and > experienced similar problems ? > I do. Before Paul has implemented USB reconnects, it was far worse. Kind regards Jan -- You cannot achieve the impossible without attempting the absurd. signature.asc Description: This is a digitally signed message part. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] how many 18b20s on a bus
Am 01.10.2014 um 20:57 schrieb Jerry Scharf: > > I was planning on a large power supply and using simultaneous mode, but > I know, this is my pet passion, but having done a number of larger networks with central powering delivered through the bus cable, I strongly advise you to have a thick GND line (>1mm²) to avoid ground lift on the far end, resulting in random bus errors. 300 DS18B20 take about 500mA when fired simultaneous. Kind regards Jan -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Missing data
Am 27.10.2014 um 18:08 schrieb Coudy: > I have in Zabbix Timeout 15 seconds. I want to try restart server every > hour, then I'll post results > Sampling 19 temperature sensors one-by-one takes up to 19 seconds. This is due to the lengthy A/D conversion process. Either increase the timeout, sample 9-bit or 10-bit only, or power the sensors, then do a simultaneous conversion and read the values after the conversion is done on all sensors. The latter takes about 2 seconds for 20 sensors in 12-Bit mode on a DS9097. Kind regards Jan -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Missing data
Am 28.10.2014 um 15:06 schrieb Coudy: > > If temperature sensor is powered, then reading is faster compared to > parasitic power ? > No, but it's the only way you can do a simultaneous conversion for all chips, and this 19 times faster if you have 19 chips. You cannot do a simultaneous conversion on parasitic power, because all the chips on the bus start conversion at the same time and draw more power than parasitic powering can supply. Owfs is aware of that and refuse to do a simulatenous conversion if one or more temperature sensors on the bus are parasitically powered (they have a flag indicating that.) Oh, and please use a recent version of owfs. IIRC some bugs with the simultaneous temperature conversion had been fixed lately. Kind regards Jan -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Missing data
Am 29.10.2014 um 21:42 schrieb Coudy: > Thank You Jan, > I'll try to switch my sensors from parasitic power to regular power. > How to enable simultaneous conversion for all chips ? > this way ? echo 1 > /mnt/1wire/simultaneous/temperature ? > Yes, this starts the temperature conversion on all buses. Wait at least one second, after that you can read the result from the chips the usual way - owfs will not start another conversion while a result is pending. If you don't wait for the conversion to complete, owfs will do that for you when reading the first chip - but in the past, there had been some bugs with that IIRC. Kind regards Jan -- ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
