Am 30.11.2016 um 22:25 schrieb John Bass:
> Hello Jan,
>
> Found it a while back, and yep it works :-)
>
I've found time do develop a more generic approach to add support for
"secondary" family codes. Could you try the appended patch? Of course,
you had to remove your patch first.
Kind regards
Am 30.11.2016 um 23:32 schrieb John Bass:
>
> Yep the gpio 1w driver. I'm a little surprised the clock speed makes
> a difference, would have expected that to have been taken into
> consideration by the driver developers.
>
In theory all is timed but when the clock speed is out of bounds, the
c
Hello Jan,
Yep the gpio 1w driver. I'm a little surprised the clock speed makes a
difference, would have expected that to have been taken into consideration by
the driver developers.
How would you like me to generate the patch?
John
Sent from my iPhone
On 30 Nov 2016, at 22:28, Jan Kandzior
Am 30.11.2016 um 22:25 schrieb John Bass:
> Hello Jan,
>
> Found it a while back, and yep it works :-)
>
Do you have a patch?
> I have noticed one very interesting issue, if you over clock the pi,
> the 1w driver does not work correctly! Devices do not work reliably
> or with reduced functional
Hello Jan,
Found it a while back, and yep it works :-)
I have noticed one very interesting issue, if you over clock the pi, the 1w
driver does not work correctly! Devices do not work reliably or with reduced
functionality especially the 2438. I put the clock back to 700mhz and the 2438
works
Am 30.11.2016 um 16:52 schrieb John Bass:
>
> I have had a go at changing the code in ow_2438.c but can't seem to
> get it to work, I wondered if just changing the family id would do
> the trick. So I added a copy of the DS2438 section called it DS2438z
> etc with the new address family.. but it d
_DATA, },
{"S3-R1-A/gain", PROPERTY_LENGTH_PRESSURE, NON_AGGREGATE, ft_float,
fc_stable, FS_r_S3R1A_gain, FS_w_S3R1A_gain, VISIBLE, NO_FILETYPE_DATA, },
};
DeviceEntryExtended(a6, DS2438z, DEV_temp | DEV_volt, NO_GENERIC_READ,
NO_GENERIC_WRITE);
John
-Original Message-
F
Am 30.11.2016 um 11:18 schrieb Robin Gilks:
>
> I've been using DS2438 battery monitor devices for a number of years and
> they have a family code of 0x26 NOT 0xA6.
>
They can have both. See page 12 of the Book of iButton standards (sheet
19 of http://pdfserv.maximintegrated.com/en/an/AN937.pdf)
On 30/11/16 10:18, Robin Gilks wrote:
>> Hello,
>>
>>
>> I have just connected a DS2438, which seems to be reporting a A6 family
>> code, and thus not giving the correct input details.
>>
>>
>> w1_master_driver w1_bus_master1: Family a6 for a6.509b8f5f.f6 is not
>> registered.
>>
>>
>>
> Hello,
>
>
> I have just connected a DS2438, which seems to be reporting a A6 family
> code, and thus not giving the correct input details.
>
>
> w1_master_driver w1_bus_master1: Family a6 for a6.509b8f5f.f6 is not
> registered.
>
>
> On owfs 3.1p1
>
I've been using DS2438 battery mon
) /structure
DEBUG: ow_dir.c:(199) ret=0
DEBUG: ow_parsename.c:(63) /
DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
DEBUG: data.c:(207) DataHandler: cm.ret=0
DEBUG: to_client.c:(76) payload=82 size=81, ret=0, sg=0x10A offset=0
DEBUG: data.c:(226) Finished with client request
Am 29.11.2016 um 18:29 schrieb John Bass:
>
> I have just connected a DS2438, which seems to be reporting a A6 family code,
> and thus not giving the correct input details.
> w1_master_driver w1_bus_master1: Family a6 for a6.509b8f5f.f6 is not
> registered.
>
This is a message from the kern
12 matches
Mail list logo
