Hi Paul - here's a screenshot of what I see on owfshttp
 
OWFS on 3002     Bus listing <http://192.168.1.77:3001/>         OWFS
homepage <http://owfs.sourceforge.net/>          Dallas/Maxim
<http://www.maxim-ic.com/>       by Paul H
<mailto:[EMAIL PROTECTED]> Alfille      

30.EB160A110000

  _____  


uncached  <http://192.168.1.77:3001/uncached/30.EB160A110000> version 
 <http://192.168.1.77:3001/> up  directory      
PIO      

address  30EB160A110000DF       
amphours         Error: Invalid argument        
cc       Error: Invalid argument        
ce       Error: Invalid argument        
coc      Error: Invalid argument        
crc8     DF     
current  Error: Invalid argument        
currentbias      Error: Invalid argument        
dc       Error: Invalid argument        
de       Error: Invalid argument        
defaultpmod      Error: Invalid argument        
defaultswen      Error: Invalid argument        
doc      Error: Invalid argument        
family   30     
id       160A110000DF   
locator  FFFFFFFFFFFFFFFF       
lock.ALL         Error: Invalid argument        
lock.0   Error: Invalid argument        
lock.1   Error: Invalid argument        
memory   Error: Invalid argument        
mstr     Error: Invalid argument        
ov       Error: Invalid argument        
pages    pages <http://192.168.1.77:3001/30.EB160A110000/pages>         
pmod     Error: Invalid argument        
present  YES    
ps       Error: Invalid argument        
r_address        DF0000110A16EB30       
r_id     0000110A16EB   
r_locator        FFFFFFFFFFFFFFFF       
sensed   Error: Invalid argument        
swen     Error: Invalid argument        
temperature      Error: Invalid argument        
type     DS2760 
typeB    typeB <http://192.168.1.77:3001/30.EB160A110000/typeB>         
typeE    typeE <http://192.168.1.77:3001/30.EB160A110000/typeE>         
typeJ    typeJ <http://192.168.1.77:3001/30.EB160A110000/typeJ>         
typeK    typeK <http://192.168.1.77:3001/30.EB160A110000/typeK>         
typeN    typeN <http://192.168.1.77:3001/30.EB160A110000/typeN>         
typeR    typeR <http://192.168.1.77:3001/30.EB160A110000/typeR>         
typeS    typeS <http://192.168.1.77:3001/30.EB160A110000/typeS>         
typeT    typeT <http://192.168.1.77:3001/30.EB160A110000/typeT>         
uv       Error: Invalid argument        
vbias    Error: Invalid argument        
vis      Error: Invalid argument        
volt     Error: Invalid argument        
volthours        Error: Invalid argument        

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Alfille
Sent: Thursday, 1 February 2007 1:04 AM
To: [email protected]
Subject: Re: [Owfs-developers] thermocouple device


There have been reports and testing of the DS2760 thrmocouples:
http://article.gmane.org/gmane.comp.file-systems.owfs.devel/2180
http://article.gmane.org/gmane.comp.file-systems.owfs.devel/93

The datasheet for the AAG thermocouple at
http://www.aagelectronica.com/pdf%20docs/Thermocouple(TAI8560).pdf
Looks pretty close to the circuit shown in
http://www.owfs.org/index.php?page=thermocouples

So the questions are:
1. Do the prior tested designs still work?
2. Is the AAG model different. (There is example code to compare in
Delphi and Java).

When you use the devices, do you see the normal DS2760 values?
Temperature, vis, etc?That would be helpful is tracking this down.

Paul Alfille


On 1/31/07, Lorenz Drack <[EMAIL PROTECTED]> wrote: 

Has anyone had any experience with the DS2760 based 1-wire AAG
thermocouple device? 
I have 4 of them and can get none to work with owfs - ie. they all give
"Error: Invalid argument" errors on all outputs
yet they all work with ddeview. The rest of my network works well with
owfs.
thanks
Lorenz

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Alfille
Sent: Wednesday, 31 January 2007 11:01 PM
To: [email protected]
Subject: Re: [Owfs-developers] Creating owlua...


If by path you mean something like "/10.23AD234523/temperature" the
answer is simple:
You use "get" for  the root path ("/" or actually just "") and build
from there.

The explanations for what devices support what properties, their format,
function, measurement units, etc is in the man files. That is
domain-specific information that the user must know indep[endently
(though we'endeavored to make function pretty transparent, and must data
is returned as straight ascii characters.)

Paul Alfille


On 1/31/07, Matthew Percival <[EMAIL PROTECTED]> wrote: 

G'Day,

        I have been trying to create a owlua using owcapi as a basis.
As far
as this is concerned, it has been a success --- I have an exact
equivalent to owcapi that can now be used from Lua.  I just cannot make 
any use of it!  I can use the OW_init() and OW_finish() equivalent
functions without any trouble, but I cannot for the life of me work out
how to use put/get.  In both cases I need to provide a path, and this is

where it feels like I am missing a function or two.

        How does a person writing their Lua script know what path is
needed?
Presumably they would need to call a function that tells them the
relevant paths or something.  For that matter, what devices are 
available and what can we do with them?

        I have been trying to work these things out from the source
code, but I
am just going around in circles.  I have a C library written similar to
owcapi that allows people to access the 1-Wire net from Lua, but no idea

how to make any practical application of this.  Can anyone direct me on
where to find the answers to this?

        Thanks,

        Matthew


------------------------------------------------------------------------
- 
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
<http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
EV> &p=sourceforge&CID=DEVDEV 
_______________________________________________ 
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
<https://lists.sourceforge.net/lists/listinfo/owfs-developers> 




------------------------------------------------------------------------
-
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
<http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
EV> &p=sourceforge&CID=DEVDEV

_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
<https://lists.sourceforge.net/lists/listinfo/owfs-developers> 





-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to