I use the TMEX file as the primary (readable) device. It can reader or writer.
I notice that the lines
DETAIL: TAI8570 reader=12 DD 98 3B 00 00 00 5A writer=04 00 00 00 06 00
DETAIL: TAI8570 reader=12 DD 98 3B 00 00 00 5A writer=54 3E F6 B7 3F 00
DETAIL: TAI8570 reader=12 DD 98 3B 00 00 00 5A writer=54 3E F6 B7 3F 00

occurs in your error log. I get: DETAIL: TAI8570 reader=12 95 CF 1B 00 00 00 3A writer=12 E4 D2 1B 00 00 00 05
which is expected. (Simple TMEX parsing)

AHHA! The answer.
ow_2406.c line 622
    if ( pow ) {
        memcpy( tai->writer, pn->sn  , 8 ) ;
        memcpy( tai->reader, &data[1], 8 ) ;
    } else {
        memcpy( tai->reader, pn->sn  , 8 ) ;
        memcpy( tai->reader, &data[1], 8 ) ;
    }

Yup, we follow different branches and the "else" branch is wrong.
Changed to:
    if ( pow ) {
        memcpy( tai->writer, pn->sn  , 8 ) ;
        memcpy( tai->reader, &data[1], 8 ) ;
    } else {
        memcpy( tai->reader, pn->sn  , 8 ) ;
        memcpy( tai->writer, &data[1], 8 ) ;
    }

You can pull it from the CVS.
Tell me if this works, and thanks for your persistence!!!

Paul Alfille





On 8/15/06, Dave Torrey < [EMAIL PROTECTED]> wrote:
And here's the other device.  Out of curiosity, which device should give
readings in TAI8570?  The one with power=1 or power=0?  I notice one
device has a memory file with pertinent information in it, while the
other does not:

od -x memory
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000200

Maybe that's the issue?  But do I need to care about the TMEX info if I
know the device pairing already?

unique: 90, opcode: LOOKUP (1), nodeid: 8, insize: 49
LOOKUP /uncached/12.DD983B000000/TAI8570/pressure
   CALL: FSTAT path=/uncached/12.DD983B000000/TAI8570/pressure
   CALL: PARSENAME path=[/uncached/12.DD983B000000/TAI8570/pressure]
  DEBUG: Get from cache sn 12 DD 98 3B 00 00 00 5A in=(nil) index=-1
size=8615936
  DEBUG: Found in cache
  DEBUG: Expired in cache
DETAIL: Checking presence of /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction verify = 0
  DEBUG: Add to cache sn 12 DD 98 3B 00 00 00 5A in=(nil) index=-1
size=4
   CALL: ATTRIBUTES path=/uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: ParsedName_destroy /uncached/12.DD983B000000/TAI8570/pressure
   NODEID: 9
   unique: 90, error: 0 (Success), outsize: 136
unique: 91, opcode: OPEN (14), nodeid: 9, insize: 48
   CALL: OPEN path=/uncached/12.DD983B000000/TAI8570/pressure
OPEN[0] flags: 0x8000
   unique: 91, error: 0 (Success), outsize: 32
unique: 92, opcode: READ (15), nodeid: 9, insize: 64
READ[0] 4096 bytes from 0
   CALL: READ path=/uncached/12.DD983B000000/TAI8570/pressure size=4096
offset=0   CALL: PARSENAME
path=[/uncached/12.DD983B000000/TAI8570/pressure]
  DEBUG: Get from cache sn 12 DD 98 3B 00 00 00 5A in=(nil) index=-1
size=8615936
  DEBUG: Found in cache
  DEBUG: READ_POSTPARSE /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: READ_POSTPOSTPARSE /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: READSEEK
  DEBUG: READSEEK2 pid=10224 not found in cache
   CALL: FS_parse_read: format=4 s=4096 offset=0
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction select = 0
  DEBUG:   Transaction send = 0
  DEBUG:   Transaction readin = 0
DETAIL: Tmex page 0 bad length 255
  DEBUG: READ_POSTPOSTPARSE: /uncached/12.DD983B000000/TAI8570/pressure
return -2
DETAIL: Checking presence of /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction verify = 0
  DEBUG: Add to cache sn 12 DD 98 3B 00 00 00 5A in=(nil) index=-1
size=4
  DEBUG: READ_POSTPOSTPARSE /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: READSEEK
  DEBUG: READSEEK2 pid=10224 not found in cache
   CALL: FS_parse_read: format=4 s=4096 offset=0
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction select = 0
  DEBUG:   Transaction send = 0
  DEBUG:   Transaction readin = 0
DETAIL: Tmex page 0 bad length 255
  DEBUG: READ_POSTPOSTPARSE: /uncached/12.DD983B000000/TAI8570/pressure
return -2
DETAIL: Checking presence of /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction verify = 0
  DEBUG: Add to cache sn 12 DD 98 3B 00 00 00 5A in=(nil) index=-1
size=4
  DEBUG: READ_POSTPOSTPARSE /uncached/12.DD983B000000/TAI8570/pressure
  DEBUG: READSEEK
  DEBUG: READSEEK2 pid=10224 not found in cache
   CALL: FS_parse_read: format=4 s=4096 offset=0
  DEBUG: Selecting a path (and device)
path=/uncached/12.DD983B000000/TAI8570/pressure SN=12 DD 98 3B 00 00 00
5A last path=00 00 00 00 00 00 00 00
  DEBUG:   Transaction select = 0
  DEBUG:   Transaction send = 0
  DEBUG:   Transaction readin = 0
DETAIL: Tmex page 0 bad length 255
  DEBUG: READ_POSTPOSTPARSE: /uncached/12.DD983B000000/TAI8570/pressure
return -2
  DEBUG: READ_POSTPARSE /uncached/12.DD983B000000/TAI8570/pressure
return -2
  DEBUG: ParsedName_destroy /uncached/12.DD983B000000/TAI8570/pressure
   unique: 92, error: -2 (No such file or directory), outsize: 16
unique: 93, opcode: RELEASE (18), nodeid: 9, insize: 56
RELEASE[0] flags: 0x8000
   CALL: RELEASE path=/uncached/12.DD983B000000/TAI8570/pressure
   unique: 93, error: 0 (Success), outsize: 16


On Tue, 2006-08-15 at 21:44 -0400, Paul Alfille wrote:
> Can you try with "error_level=9". A lot of the chatter we want will
> come from that.
>
> Paul
>

>

-------------------------------------------------------------------------
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

-------------------------------------------------------------------------
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