Re: [Owfs-developers] Try to find bug in my slave DS2423 implementation

[Rotarn]

Hi,

 

I guess the reason for my problem is, that

 

I just took a look into the data sheet of the DS2423 on page 13 and try to program it.
Even I get a sample code from a other guy, working as well with this chip
by the following telegram (I go not get a feedback, if it really works)

 

00 0xA5 (read + Counter)
01 0xC0 (TA1)
02 0x01 (TA2)
03 now read 32 data bytes
... 
35 counterA
36 counterA
37 counterA
38 counterA
39 Zero Bits
40 Zero Bits
41 Zero Bits
42 Zero Bits
43 CRC
44 CRC

 

It looks like, that this is not correct. I will take a close look into the source code of the owserver,

which you told me before.

 

Do they read out the memory page by more than one block and uses the address byte as a offset ?

 

Best regards

R.

 

 

 

 

Gesendet: Donnerstag, 22. Oktober 2015 um 00:45 Uhr
Von: "Jan Kandziora" <j...@gmx.de>
An: "OWFS (One-wire file system) discussion and help" <owfs-developers@lists.sourceforge.net>
Betreff: Re: [Owfs-developers] Try to find bug in my slave DS2423 implementation

Am 21.10.2015 um 19:36 schrieb Ritchie:
>
> thanks for taking a closer look too it, but I may try to find a way,
> that the owserver will only send information on request.
>
> Creating extra builds it not needed...
>
> I just thought it was easy to get a dump.
>
> Is there maybe a other good documentation what commands are running from
> the owserver to get the readout of the DS2423.
>
Well, there is the OWFS sources. I can help you understanding the sources.

The relevant code for reading the DS2423 counter pages is in
owfs/module/owlib/src/c/ow_memory.c, line 142ff and
owfs/module/owlib/src/include/ow_transaction.h:


Actually, after selecting the DS2423 chip (e.g. by doing Match ROM + 1W
address) owfs writes 3 bytes

0x00 0xa5 (read memory+counter)
0x01 address low byte
0x02 address high byte

then reads 11 bytes

0x03 throw_away
0x04 data0
0x05 data1
0x06 data2
0x07 data3
0x08 data4
0x09 data5
0x0a data6
0x0b data7
0x0c CRC16 low byte
0x0d CRC16 high byte


Maybe you missed the throw_away byte in your implementation? I vaguely
remember others which had the same problem.


Kind regards

Jan

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------

_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers