Menu
▾
▴
owfs-developers
|
From: Zoff <zo...@zo...> - 2009-07-30 10:37:59
|
Hi!
can anyone read temp and or humidity from a DS1923?
i can read other devices. also i can see the filesystem of my DS1923.
but when i read i get:
cat: humidity: Invalid argument
:-(
i am using owfs-2.7p23
help please ...
cheers,
Zoff.
--
"My malpractice insurance doesn’t cover alien autopsies."
|
|
From: Zoff <zo...@zo...> - 2009-07-31 07:50:32
|
am I on the wrong mailling list? no answer :-( Zoff. Zoff wrote: > Hi! > > can anyone read temp and or humidity from a DS1923? > > i can read other devices. also i can see the filesystem of my DS1923. > but when i read i get: > > cat: humidity: Invalid argument > > :-( > > i am using owfs-2.7p23 > > help please ... > > cheers, > Zoff. > -- "My malpractice insurance doesn’t cover alien autopsies." |
|
From: Paul A. <pau...@gm...> - 2009-07-31 09:38:53
|
Correct mailing list. The DS1923 support is very impomplete. Are you interested in having it work? I can start work on it. Paul Alfille On Fri, Jul 31, 2009 at 3:50 AM, Zoff<zo...@zo...> wrote: > am I on the wrong mailling list? no answer :-( > > Zoff. > > Zoff wrote: >> Hi! >> >> can anyone read temp and or humidity from a DS1923? >> >> i can read other devices. also i can see the filesystem of my DS1923. >> but when i read i get: >> >> cat: humidity: Invalid argument >> >> :-( >> >> i am using owfs-2.7p23 >> >> help please ... >> >> cheers, >> Zoff. >> > > -- > "My malpractice insurance doesn’t cover alien autopsies." > > ------------------------------------------------------------------------------ > 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 > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > |
|
From: Paul A. <pau...@gm...> - 2009-07-31 09:51:56
|
Incomplete is what I meant to say. A couple of issues: We don't really have a good model for the password protection of the chip.OWFS uses filesystem symantics. 1. You could add the password as part of the pathname (like some URL hacks), 2. You could have a "virtual" file that you write the password to to unlock the chip (that password gets used for every access. A. The password file is not particularly secure -- how long it persists is unclear. And keeping state information means that restarting OWFS (which normally is transparent to you) will loose the password. B. OWFS can be a distributed system, with clients talking to a central owserver. Which entity keeps the password gets confusing. Does the p-assword unlock all the clients? If it doesn't, how do you deal with the light-weight clients that don't know enough about OWFS syntax to deal with passwords themselves? Paul Alfille On Fri, Jul 31, 2009 at 5:38 AM, Paul Alfille<pau...@gm...> wrote: > Correct mailing list. > > The DS1923 support is very impomplete. Are you interested in having it > work? I can start work on it. > > Paul Alfille > > On Fri, Jul 31, 2009 at 3:50 AM, Zoff<zo...@zo...> wrote: >> am I on the wrong mailling list? no answer :-( >> >> Zoff. >> >> Zoff wrote: >>> Hi! >>> >>> can anyone read temp and or humidity from a DS1923? >>> >>> i can read other devices. also i can see the filesystem of my DS1923. >>> but when i read i get: >>> >>> cat: humidity: Invalid argument >>> >>> :-( >>> >>> i am using owfs-2.7p23 >>> >>> help please ... >>> >>> cheers, >>> Zoff. >>> >> >> -- >> "My malpractice insurance doesn’t cover alien autopsies." >> >> ------------------------------------------------------------------------------ >> 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 >> Owf...@li... >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > |
|
From: Zoff <zo...@zo...> - 2009-07-31 10:35:17
|
Hi! thanks for the answer. basically i dont care about security. i (want) use it to have a small weather station at my house. all i need is reading temp and humdity values every couple of secs/minutes. i can also help u with some C-code, i just have no idea how ibuttons work (internally). it was my fault i thought it would be the quickest way without much assembly work if i just bought this ibutton und plug it into usb. only later i checked if it was supported :-) my bad ... i thought from reading through the source code and from google-ing a bit, that at least basic stuff was supported for ds1923? i dont know anything about password? what is the initial password? and do i need pwd protection, its just reading temp outside my house :-) not working for NASA or anything :-) cheers, Zoff. Paul Alfille wrote: > Incomplete is what I meant to say. > > A couple of issues: > > We don't really have a good model for the password protection of the > chip.OWFS uses filesystem symantics. > 1. You could add the password as part of the pathname (like some URL hacks), > 2. You could have a "virtual" file that you write the password to to > unlock the chip (that password gets used for every access. > A. The password file is not particularly secure -- how long it > persists is unclear. And keeping state information means that > restarting OWFS (which normally is transparent to you) will loose the > password. > B. OWFS can be a distributed system, with clients talking to a > central owserver. Which entity keeps the password gets confusing. Does > the p-assword unlock all the clients? If it doesn't, how do you deal > with the light-weight clients that don't know enough about OWFS syntax > to deal with passwords themselves? > > Paul Alfille > > On Fri, Jul 31, 2009 at 5:38 AM, Paul Alfille<pau...@gm...> wrote: >> Correct mailing list. >> >> The DS1923 support is very impomplete. Are you interested in having it >> work? I can start work on it. >> >> Paul Alfille >> >> On Fri, Jul 31, 2009 at 3:50 AM, Zoff<zo...@zo...> wrote: >>> am I on the wrong mailling list? no answer :-( >>> >>> Zoff. >>> >>> Zoff wrote: >>>> Hi! >>>> >>>> can anyone read temp and or humidity from a DS1923? >>>> >>>> i can read other devices. also i can see the filesystem of my DS1923. >>>> but when i read i get: >>>> >>>> cat: humidity: Invalid argument >>>> >>>> :-( >>>> >>>> i am using owfs-2.7p23 >>>> >>>> help please ... >>>> >>>> cheers, >>>> Zoff. >>>> >>> >>> -- >>> "My malpractice insurance doesn’t cover alien autopsies." >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> Owf...@li... >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >>> >> > > ------------------------------------------------------------------------------ > 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 > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers -- "My malpractice insurance doesn’t cover alien autopsies." |
|
From: Paul A. <pau...@gm...> - 2009-07-31 10:57:39
|
No. I think the password is only for using the buttons to track shipping/storage conditions and detect tampering. By microprocessor standards, the DS1923 isn't that complex, but it one of the most complex of the iButtons, with several modes (e.g. mission, immediate,...) alarms, logs, and sub modes (different resolutions, rollover, etc). It also is notorious for a software "feature" that allows it do be bricked by misprogramming. The real reason for the long lag in development is the complexity of the device, and the awkward fit with the filesystem paradigm. For instance, starting a mission involves checking current state, setting a bunch of parameters, and then starting the mission. Ideally this should be done as a atomic operation to prevent lockups and conflicts. Finding the right level of abstraction isn't easy. Until we had the machinery in owfs for internal cached state with multiple external representations, this was an awkward hack. It was overwhelming even for the DS1921. Paul Alfille On Fri, Jul 31, 2009 at 6:35 AM, Zoff<zo...@zo...> wrote: > Hi! > > thanks for the answer. basically i dont care about security. > i (want) use it to have a small weather station at my house. > all i need is reading temp and humdity values every couple of secs/minutes. > > i can also help u with some C-code, i just have no idea how ibuttons work (internally). > it was my fault i thought it would be the quickest way without much assembly work > if i just bought this ibutton und plug it into usb. only later i checked if it was supported :-) > my bad ... > > i thought from reading through the source code and from google-ing a bit, > that at least basic stuff was supported for ds1923? > i dont know anything about password? what is the initial password? and do i need pwd protection, > its just reading temp outside my house :-) not working for NASA or anything :-) > > cheers, > Zoff. > > Paul Alfille wrote: >> Incomplete is what I meant to say. >> >> A couple of issues: >> >> We don't really have a good model for the password protection of the >> chip.OWFS uses filesystem symantics. >> 1. You could add the password as part of the pathname (like some URL hacks), >> 2. You could have a "virtual" file that you write the password to to >> unlock the chip (that password gets used for every access. >> A. The password file is not particularly secure -- how long it >> persists is unclear. And keeping state information means that >> restarting OWFS (which normally is transparent to you) will loose the >> password. >> B. OWFS can be a distributed system, with clients talking to a >> central owserver. Which entity keeps the password gets confusing. Does >> the p-assword unlock all the clients? If it doesn't, how do you deal >> with the light-weight clients that don't know enough about OWFS syntax >> to deal with passwords themselves? >> >> Paul Alfille >> >> On Fri, Jul 31, 2009 at 5:38 AM, Paul Alfille<pau...@gm...> wrote: >>> Correct mailing list. >>> >>> The DS1923 support is very impomplete. Are you interested in having it >>> work? I can start work on it. >>> >>> Paul Alfille >>> >>> On Fri, Jul 31, 2009 at 3:50 AM, Zoff<zo...@zo...> wrote: >>>> am I on the wrong mailling list? no answer :-( >>>> >>>> Zoff. >>>> >>>> Zoff wrote: >>>>> Hi! >>>>> >>>>> can anyone read temp and or humidity from a DS1923? >>>>> >>>>> i can read other devices. also i can see the filesystem of my DS1923. >>>>> but when i read i get: >>>>> >>>>> cat: humidity: Invalid argument >>>>> >>>>> :-( >>>>> >>>>> i am using owfs-2.7p23 >>>>> >>>>> help please ... >>>>> >>>>> cheers, >>>>> Zoff. >>>>> >>>> >>>> -- >>>> "My malpractice insurance doesn’t cover alien autopsies." >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> Owf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >>>> >>> >> >> ------------------------------------------------------------------------------ >> 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 >> Owf...@li... >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > -- > "My malpractice insurance doesn’t cover alien autopsies." > > ------------------------------------------------------------------------------ > 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 > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > |
|
From: Zoff <zo...@zo...> - 2009-07-31 11:33:25
|
Hi! but is there a quick way (or hack) to just get the values for temp and humidity via owfs? this would be enough for me. i dont need missions/alarms and other stuff. cheers, Zoff. Paul Alfille wrote: > No. I think the password is only for using the buttons to track > shipping/storage conditions and detect tampering. > > By microprocessor standards, the DS1923 isn't that complex, but it one > of the most complex of the iButtons, with several modes (e.g. mission, > immediate,...) alarms, logs, and sub modes (different resolutions, > rollover, etc). It also is notorious for a software "feature" that > allows it do be bricked by misprogramming. > > The real reason for the long lag in development is the complexity of > the device, and the awkward fit with the filesystem paradigm. For > instance, starting a mission involves checking current state, setting > a bunch of parameters, and then starting the mission. Ideally this > should be done as a atomic operation to prevent lockups and > conflicts. Finding the right level of abstraction isn't easy. Until we > had the machinery in owfs for internal cached state with multiple > external representations, this was an awkward hack. It was > overwhelming even for the DS1921. > > Paul Alfille > > On Fri, Jul 31, 2009 at 6:35 AM, Zoff<zo...@zo...> wrote: >> Hi! >> >> thanks for the answer. basically i dont care about security. >> i (want) use it to have a small weather station at my house. >> all i need is reading temp and humdity values every couple of secs/minutes. >> >> i can also help u with some C-code, i just have no idea how ibuttons work (internally). >> it was my fault i thought it would be the quickest way without much assembly work >> if i just bought this ibutton und plug it into usb. only later i checked if it was supported :-) >> my bad ... >> >> i thought from reading through the source code and from google-ing a bit, >> that at least basic stuff was supported for ds1923? >> i dont know anything about password? what is the initial password? and do i need pwd protection, >> its just reading temp outside my house :-) not working for NASA or anything :-) >> >> cheers, >> Zoff. >> >> Paul Alfille wrote: >>> Incomplete is what I meant to say. >>> >>> A couple of issues: >>> >>> We don't really have a good model for the password protection of the >>> chip.OWFS uses filesystem symantics. >>> 1. You could add the password as part of the pathname (like some URL hacks), >>> 2. You could have a "virtual" file that you write the password to to >>> unlock the chip (that password gets used for every access. >>> A. The password file is not particularly secure -- how long it >>> persists is unclear. And keeping state information means that >>> restarting OWFS (which normally is transparent to you) will loose the >>> password. >>> B. OWFS can be a distributed system, with clients talking to a >>> central owserver. Which entity keeps the password gets confusing. Does >>> the p-assword unlock all the clients? If it doesn't, how do you deal >>> with the light-weight clients that don't know enough about OWFS syntax >>> to deal with passwords themselves? >>> >>> Paul Alfille >>> >>> On Fri, Jul 31, 2009 at 5:38 AM, Paul Alfille<pau...@gm...> wrote: >>>> Correct mailing list. >>>> >>>> The DS1923 support is very impomplete. Are you interested in having it >>>> work? I can start work on it. >>>> >>>> Paul Alfille >>>> >>>> On Fri, Jul 31, 2009 at 3:50 AM, Zoff<zo...@zo...> wrote: >>>>> am I on the wrong mailling list? no answer :-( >>>>> >>>>> Zoff. >>>>> >>>>> Zoff wrote: >>>>>> Hi! >>>>>> >>>>>> can anyone read temp and or humidity from a DS1923? >>>>>> >>>>>> i can read other devices. also i can see the filesystem of my DS1923. >>>>>> but when i read i get: >>>>>> >>>>>> cat: humidity: Invalid argument >>>>>> >>>>>> :-( >>>>>> >>>>>> i am using owfs-2.7p23 >>>>>> >>>>>> help please ... >>>>>> >>>>>> cheers, >>>>>> Zoff. >>>>>> >>>>> >>>>> -- >>>>> "My malpractice insurance doesn’t cover alien autopsies." >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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 >>>>> Owf...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >>>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> Owf...@li... >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> -- >> "My malpractice insurance doesn’t cover alien autopsies." >> >> ------------------------------------------------------------------------------ >> 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 >> Owf...@li... >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > > ------------------------------------------------------------------------------ > 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 > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers -- "My malpractice insurance doesn’t cover alien autopsies." |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X