On 04/06/2016 09:43 AM, Andy Carter wrote:
>> The fact that a lot of distros lags behind is another problem though..
> debian stable particularly in my case which many use with perl based fhem :/
true, but you can easily install a newer version of owfs manually.
I did so a while ago myself and wr
On Wednesday 06 Apr 2016 08:26:46 Johan Ström wrote:
> On 03/04/16 22:32, Andy Carter wrote:
> > On Friday 18 Mar 2016 21:49:49 Johan Ström wrote:
> >> I've patched OWNet.pm in master now, to not send a null-terminated
> >> payload.
> >
> > Sorry to come back to this one but I wonder if I could su
On 03/04/16 22:32, Andy Carter wrote:
> On Friday 18 Mar 2016 21:49:49 Johan Ström wrote:
>> I've patched OWNet.pm in master now, to not send a null-terminated
>> payload.
> Sorry to come back to this one but I wonder if I could suggest/request a human
> readable version no. or date stamp in OWNet.
On Friday 18 Mar 2016 21:49:49 Johan Ström wrote:
> I've patched OWNet.pm in master now, to not send a null-terminated
> payload.
Sorry to come back to this one but I wonder if I could suggest/request a human
readable version no. or date stamp in OWNet.pm, perhaps even a comment to use
with 2.9
Cool, this code is working, i did een fresh pull, the revert and a new
compile,
My display is working anyway, but other versions?
Thanks,
Nico
Johan Ström wrote:
> On 29/03/16 18:52, Nico Bouthoorn wrote:
>> Update; i've copied module/owlib/src/c/ow_2408.c file from the 2.8p15
>> source
On 29/03/16 18:52, Nico Bouthoorn wrote:
> Update; i've copied module/owlib/src/c/ow_2408.c file from the 2.8p15
> sources to the 3.1 version, recompiled it again.
> It is working now
Great pinpointing! I suspect the following change:
https://sourceforge.net/p/owfs/code/ci/85dd9650cea1dcd8
Update; i've copied module/owlib/src/c/ow_2408.c file from the 2.8p15 sources
to the 3.1 version, recompiled it again.
It is working now
Paul is maintainer of the code?, i've not knowledge how to debug this further.
Thanks,
Nico
Johan Ström wrote:
>
> On 27/03/16 11:49, Nico Bouthoorn
On 27/03/16 11:49, Nico Bouthoorn wrote:
> Hi Johan,
>
> I've setup nieuw beaglebone system, if i use the version 2.8 included in de
> debian 7 repo the display works, the version 3.1 from the git don't. I'm
> using now a DS9097U/ds2409 as interface, but no difference
There was a bunch of chang
Hi Johan,
I've setup nieuw beaglebone system, if i use the version 2.8 included in de
debian 7 repo the display works, the version 3.1 from the git don't. I'm using
now a DS9097U/ds2409 as interface, but no difference
owwrite /1F.17710200/aux/29.09C21100/LCD_H/clear 1
owwrite /1F.
On 24/03/16 08:54, Andy Carter wrote:
> On Wednesday 23 Mar 2016 23:58:56 Johan Ström wrote:
>>> On Tuesday 22 Mar 2016 22:30:50 Johan Ström wrote:
To nail this properly, I'm going to try to write some unittests for
this, so it is reproducible and works for all side-cases (wrong lengths
On Wednesday 23 Mar 2016 23:58:56 Johan Ström wrote:
> > On Tuesday 22 Mar 2016 22:30:50 Johan Ström wrote:
> >> To nail this properly, I'm going to try to write some unittests for
> >> this, so it is reproducible and works for all side-cases (wrong lengths
> >> etc).
>
> So, I've gotten around to
Hi,
sounds like a great idea. Not sure who should take the lead as project
owner though (seems to me someone needs to register etc). Paul Allfille
would be the obvious one, but he haven't been very active lately.
Johan
On 23/03/16 08:15, Markus Gaugusch wrote:
Hi,
Looking at this huge disc
On 23/03/16 21:39, Nico Bouthoorn wrote:
> Because my system is also being used for my central heating, i've got a
> temperature runaway in my house now. My wife is complaining
> I've have to setup my spare first for experimenting
When you have the opportunity, can you please try with
On 23/03/16 08:09, Andy Carter wrote:
> On Tuesday 22 Mar 2016 22:30:50 Johan Ström wrote:
>> To nail this properly, I'm going to try to write some unittests for
>> this, so it is reproducible and works for all side-cases (wrong lengths
>> etc).
So, I've gotten around to write some tests for this
Because my system is also being used for my central heating, i've got a
temperature runaway in my house now. My wife is complaining
I've have to setup my spare first for experimenting
Nico
Andy Carter wrote:
> On Wednesday 23 Mar 2016 20:01:43 Nico Bouthoorn wrote:
>
>> /opt/owfs/bin/
On Wednesday 23 Mar 2016 20:01:43 Nico Bouthoorn wrote:
> /opt/owfs/bin/owwrite /29.09C21100/LCD_H/clear 1
How about
/opt/owfs/bin/owwrite /29.09C21100/LCD_H/clear 11
> Easy for me to say, i'm not a c programmer. But i'm wondering has the code
> changed a lot since 2.8?
2.8 was 2010
Sorry for the delay, i've tested it also with the latest git, but it still
doesn't work anymore,
Even the clear command:
/opt/owfs/bin/owwrite /29.09C21100/LCD_H/clear 1
Easy for me to say, i'm not a c programmer. But i'm wondering has the code
changed a lot since 2.8?
Nico
Nico Bout
regards,
Markus
On Mar 23, Andy Carter wrote:
Date: Wed, 23 Mar 2016 08:09:53
From: Andy Carter
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] Louis Swart LCD issues
On Tuesday 22 Mar 2016 22:30:50 Johan Ström wrote:
On 22/03/16 21:56, Andy Carter wrote:
statement
On Tuesday 22 Mar 2016 22:30:50 Johan Ström wrote:
> On 22/03/16 21:56, Andy Carter wrote:
> > statement. Changing this to
> >
> > if (extension == elements - 1) {// last element
> >
> > entry_length = end - buffer_position - element - 1 ;
Typo, that should of course have been
if (ex
On 22/03/16 21:56, Andy Carter wrote:
> On Monday 21 Mar 2016 22:27:21 Johan Ström wrote:
>> I'm quite sure the error is at ow_parseinput.c line 462:
>>
>> // shorten the buffer length by the comma and discarded chars
>> end -= entry_length - allowed_length - 1 ;
>>
>> The purpose is to move the
On Monday 21 Mar 2016 22:27:21 Johan Ström wrote:
> I'm quite sure the error is at ow_parseinput.c line 462:
>
> // shorten the buffer length by the comma and discarded chars
> end -= entry_length - allowed_length - 1 ;
>
> The purpose is to move the endpointer, but the logic is wrong, and the
>
On Tuesday 22 Mar 2016 08:16:44 Johan Ström wrote:
> Try
>
> owwrite -- /path/line20.ALL -aaa,bbb,ccc,ddd
That works as expected
> -aaa is probably interpretted as a specific option (like -x), and
> owwrite does not complain on wrong options. Using '--' marks "rest of
> options are non-option ar
On 21/03/16 23:11, Andy Carter wrote:
> On Monday 21 Mar 2016 22:27:21 Johan Ström wrote:
>> On 21/03/16 20:59, Andy Carter wrote:
> I think I've found another too :(
>
> Both
>
> owwrite "/FF.87090100/line20.0" -
> owwrite "/FF.87090100/line20.ALL" -aaa,bbb,ccc,ddd
>
> display nothi
On Monday 21 Mar 2016 22:27:21 Johan Ström wrote:
> On 21/03/16 20:59, Andy Carter wrote:
> >> Now build, and see if this works.
> >
> > Almost, I now have
> > aaa
> > bbb
> > ccc
> > ||
> >
> > that's 5 double pipes
> >
> > owwrite "/FF.87090100/line20.ALL" aaa,bbb,ccc,ddd
> >
On 21/03/16 20:59, Andy Carter wrote:
> On Monday 21 Mar 2016 19:34:51 Johan Ström wrote:
>> I commited a fix in a separate branch for testing. Please try:
>>
>> git pull
>> git checkout ALL_size_fix
>> (running git log now would show ac62579ecbfe7acebb2873a9a089bc5b9814cd86
>> as latest commit)
>
On Monday 21 Mar 2016 19:34:51 Johan Ström wrote:
> I commited a fix in a separate branch for testing. Please try:
>
> git pull
> git checkout ALL_size_fix
> (running git log now would show ac62579ecbfe7acebb2873a9a089bc5b9814cd86
> as latest commit)
>
> Now build, and see if this works.
Almost
On 21/03/16 15:37, Andy Carter wrote:
> Really sorry, I have another I think.
No need to be sorry, especially since you provide a good bug report!
Thank you, this nailed (or at least uncovered) another bug.
>
> I thought I had better check through the other commands for this LCD.
>
> Its a new dev
Really sorry, I have another I think.
I thought I had better check through the other commands for this LCD.
Its a new device to me but all seemed to be as expected until I got to
Line20.ALL
It's probably not a command I'll ever use but someone is bound to come along
sometime with an issue wi
On Sunday 20 Mar 2016 12:23:23 Matthias Urlichs wrote:
> > My very limited experience of git has been with all files for a build - I
> > didn't try bootstrap so perhaps that's the secret
> >
> >
>
> It's widely considered bad form to check generated files into a source
> archive.
Yes, I should
On 19.03.2016 14:16, Andy Carter wrote:
> On Friday 18 Mar 2016 05:49:28 Andy Carter wrote:
>>> "git bisect" is your friend.
>>
>> Thanks, looks very useful. I'll try that over the weekend, won't have time
>> today.
>
> Well, I tried, got a useful looking set of files but had no idea what to do
On Wednesday 16 Mar 2016 14:44:56 Johan Ström wrote:
> If you are familiar with programming in general you could always skim
> over the changes and see if you see anything standing out:
>
> git log v2.9p3..v2.9p5 -p
>
> shows every row changed between 2.9p3 and 2.9p5.
A little coding experience
On 18/03/16 09:03, Johan Ström wrote:
>
> On 17/03/16 12:17, Andy Carter wrote:
>> On Wednesday 16 Mar 2016 22:25:30 Johan Ström wrote:
>>> When testing these old versions, you may have to build with ./configure
>>> --enable-debug --enable-traffic (or something similar, cannot recall
>>> exactl
On Friday 18 Mar 2016 04:45:05 Matthias Urlichs wrote:
> On 16.03.2016 14:44, Johan Ström wrote:
> > git log v2.9p3..v2.9p5 -p
> >
> > shows every row changed between 2.9p3 and 2.9p5.
> > I don't have time this second to go through this myself, may find some
> > timer later if you haven't found an
Am 16.03.2016 um 13:29 schrieb Andy Carter:
> I've built a number of versions this morning. Results are...
>
> 2.8p15 OK
> 2.9p0 OK
> 2.9p2 OK
> 2.9p3 OK
> 2.9p5 not OK
>
> 2.9p4 sources don't seem to be available
>
There is not much of a change between 2.9p4 and 2.9p5, so I think i
On 16/03/16 22:11, Andy Carter wrote:
> On Wednesday 16 Mar 2016 21:10:24 Johan Ström wrote:
>> So.. Just to sum things up before digging further.
>>
>> We have a 0x29 (DS2408-based) LCD, which works in 2.8p15, but not on 3.1p1
>> We have a 0xFF (L. Swart-based) LCD, which works in 2.9p3, but no
If you are familiar with programming in general you could always skim
over the changes and see if you see anything standing out:
git log v2.9p3..v2.9p5 -p
shows every row changed between 2.9p3 and 2.9p5.
I don't have time this second to go through this myself, may find some
timer later if you hav
On Wednesday 16 Mar 2016 14:52:04 Jan Kandziora wrote:
> Am 16.03.2016 um 13:29 schrieb Andy Carter:
> There is not much of a change between 2.9p4 and 2.9p5, so I think it
> would be "not OK" either.
I guessed that to be the case.
> > I have no idea where to look for a possible cause but willing
On 16.03.2016 14:44, Johan Ström wrote:
> git log v2.9p3..v2.9p5 -p
>
> shows every row changed between 2.9p3 and 2.9p5.
> I don't have time this second to go through this myself, may find some
> timer later if you haven't found anything until then.
"git bisect" is your friend.
--
-- Matthias
Just a simple point:
with owwrite you are writing ‘/FF.xxx’ but with perl 'uncached/FF.xx’, so your
test are not 100% equivalent.
Please check if this is the reason for the different behaviour (which could
give a clue on the bug).
S.
> On 17 Mar 2016, at 12:17, Andy Carter wrote:
>
> On We
On 18/03/16 09:00, Stefano Miccoli wrote:
I spotted another difference:
owwrite messages are NOT null terminated, but perl OWNet ones yes.
I remember a short discussion on this list in which I asked if
owserver messages should be null terminated. I think that Paul changed
the code to reflect
I spotted another difference:
owwrite messages are NOT null terminated, but perl OWNet ones yes.
I remember a short discussion on this list in which I asked if owserver
messages should be null terminated. I think that Paul changed the code to
reflect my observation, see the thread:
https://sou
ds2482-800 i2c
see https://fstab.nl/en/beaglebone
Andy Carter wrote:
> On Wednesday 16 Mar 2016 18:24:25 Nico Bouthoorn wrote:
>> I've the same issue.
>
> Guess it would have been useful to ask what 1-wire host adapter you are using
> in my previous reply :/
>
> Andy
>
>
On Wednesday 16 Mar 2016 22:25:30 Johan Ström wrote:
> When testing these old versions, you may have to build with ./configure
> --enable-debug --enable-traffic (or something similar, cannot recall
> exactly), as these was not default until just a few releases ago.
>
> With that, can you please
On Wednesday 16 Mar 2016 21:26:43 Johan Ström wrote:
> On 16/03/16 21:10, Johan Ström wrote:
> > For L.Swart-LCD, do you have the issue when writing to both screenXX and
> > lineXX? Please include full commands used when writing.
Should have mentioned that LS LCD doesn't have those exact commands
On Friday 18 Mar 2016 05:49:28 Andy Carter wrote:
> > "git bisect" is your friend.
>
> Thanks, looks very useful. I'll try that over the weekend, won't have time
> today.
Well, I tried, got a useful looking set of files but had no idea what to do
with them.
My very limited experience of git ha
On Saturday 19 Mar 2016 10:51:53 Johan Ström wrote:
> > I've just tried reinstating the raspbian jessie owfs etc. to check that
> > also works with the new OWNet.pm but I seem to have a broken system -
> > back later :/
> >
> > Many thanks for this
>
> Great! Let's hope this solves it for Nico to
On Wednesday 16 Mar 2016 21:10:24 Johan Ström wrote:
> So.. Just to sum things up before digging further.
>
> We have a 0x29 (DS2408-based) LCD, which works in 2.8p15, but not on 3.1p1
> We have a 0xFF (L. Swart-based) LCD, which works in 2.9p3, but not in 2.9p5
> Both use DS2482-800-based i2c co
Hello,
> You've come a far bit by pinpointing which version it broke in (2.9p4 or
> p5), let's see if we can fix this :)
As 2.9p5 is only an bugfix-realease for the damaged version 2.9p4
(Regarding information on the changelog), the fault should to be
found between 2.9p3 and 2.9p5. Version 2.9p
On 19/03/16 10:27, Andy Carter wrote:
> On Friday 18 Mar 2016 21:49:49 Johan Ström wrote:
>> I've patched OWNet.pm in master now, to not send a null-terminated
>> payload. The main issue was that that the payload field held the
>> null-terminated length of full payload, but the size field held the
On Friday 18 Mar 2016 21:49:49 Johan Ström wrote:
> I've patched OWNet.pm in master now, to not send a null-terminated
> payload. The main issue was that that the payload field held the
> null-terminated length of full payload, but the size field held the
> non-null-terminated length (of the dat
On 16/03/16 21:10, Johan Ström wrote:
> For L.Swart-LCD, do you have the issue when writing to both screenXX and
> lineXX? Please include full commands used when writing.
>
Actually, if you can run this it would probably help even more:
Use the latest version of owfs (either git or latest releas
So.. Just to sum things up before digging further.
We have a 0x29 (DS2408-based) LCD, which works in 2.8p15, but not on 3.1p1
We have a 0xFF (L. Swart-based) LCD, which works in 2.9p3, but not in 2.9p5
Both use DS2482-800-based i2c controller.
Both exhibit the same issue: the first character wri
I've the same issue. Version owfs 2.8p15-1 is working fine, running Debian
GNU/Linux 7 on a beaglebone.
This schematic: https://fstab.nl/en/lcd_owfs
When i switch to version owfs-3.1p1 it doesn't work anymore.
Commands like this:
owwrite /29.09C21100/LCD_H/clear 1
owwrite /29.09C21
On Wednesday 16 Mar 2016 18:24:25 Nico Bouthoorn wrote:
> I've the same issue.
Guess it would have been useful to ask what 1-wire host adapter you are using
in my previous reply :/
Andy
--
Transform Data into Opportuni
On Wednesday 16 Mar 2016 18:24:25 Nico Bouthoorn wrote:
> I've the same issue. Version owfs 2.8p15-1 is working fine, running Debian
> GNU/Linux 7 on a beaglebone.
It's sort of reassuring that someone else has problems :(
> This schematic: https://fstab.nl/en/lcd_owfs
That appears to be a 0x29
On Friday 18 Mar 2016 08:27:51 Stefano Miccoli wrote:
> Just a simple point:
>
> with owwrite you are writing ‘/FF.xxx’ but with perl 'uncached/FF.xx’, so
> your test are not 100% equivalent.
>
> Please check if this is the reason for the different behaviour (which could
> give a clue on the bug)
On 17/03/16 12:17, Andy Carter wrote:
> On Wednesday 16 Mar 2016 22:25:30 Johan Ström wrote:
>> When testing these old versions, you may have to build with ./configure
>> --enable-debug --enable-traffic (or something similar, cannot recall
>> exactly), as these was not default until just a few
I've built a number of versions this morning. Results are...
2.8p15 OK
2.9p0OK
2.9p2OK
2.9p3OK
2.9p5not OK
2.9p4 sources don't seem to be available
I have no idea where to look for a possible cause but willing to try any
suggestions
Andy
PS. As a matter of interest each bui
On Tuesday 15 Mar 2016 22:11:00 Arnout Vandecappelle wrote:
> On 03/15/16 21:48, Johan Ström wrote:
> > Between 2.8p15 (6df9cf6d15b7d2aa73edfcdb5a64b0e8df13eaad) and 2.9p8
> > (ef28fa555bf5371c30f951cf8df3a25de9c67a98) there has been a lot of
> > changes, but none at all which are specific to the L
On Tuesday 15 Mar 2016 21:48:56 Johan Ström wrote:
> On 15/03/16 20:08, Andy Carter wrote:
> > I assume the debian 3.1p1-2 should be close enough to the current/latest
> > release to prove something is wrong somewhere, otherwise I could make an
> > amateur attempt at building from source - but tha
On 03/15/16 21:48, Johan Ström wrote:
> Between 2.8p15 (6df9cf6d15b7d2aa73edfcdb5a64b0e8df13eaad) and 2.9p8
> (ef28fa555bf5371c30f951cf8df3a25de9c67a98) there has been a lot of
> changes, but none at all which are specific to the LCD interface (or at
> least of any importance, from what I can see
On 15/03/16 20:08, Andy Carter wrote:
> On Tuesday 15 Mar 2016 19:25:04 Johan Ström wrote:
> Thanks for the reply.
>
>> first of all I would try with the latest release of OWFS.
>> Both 2.8p15 and 2.9p8 are pretty old (May 2015, Oct 2014).
> I realise they are quite old having looked around a lot
On Tuesday 15 Mar 2016 19:25:04 Johan Ström wrote:
Thanks for the reply.
> first of all I would try with the latest release of OWFS.
> Both 2.8p15 and 2.9p8 are pretty old (May 2015, Oct 2014).
I realise they are quite old having looked around a lot in the last few days
but 2.9p8 is the latest
Hi,
first of all I would try with the latest release of OWFS.
Both 2.8p15 and 2.9p8 are pretty old (May 2015, Oct 2014). 3.1p1 is the
latest release version from January 2016.
I have no idea about what is available for RPi though. You may have to
build yourself, but search the owfs-developers a
64 matches
Mail list logo
