Am 22.08.2016 um 00:59 schrieb Henrik Östman:
> I did a pull from the master branch and applied patch.
>
> Started owserver then did a "owread -s 192.168.10.110:4304
> /uncached/28.3F28AE06/latesttemp" which seems to work, got a
> "24.25" back.
>
> Restarted owserver in debug-mode and ran th
I did a pull from the master branch and applied patch.
Started owserver then did a "owread -s 192.168.10.110:4304
/uncached/28.3F28AE06/latesttemp" which seems to work, got a
"24.25" back.
Restarted owserver in debug-mode and ran this scenario:
owdir -s 192.168.10.110:4304 /uncached/28.
Am 21.08.2016 um 15:39 schrieb Jan Kandziora:
> Am 21.08.2016 um 13:38 schrieb Henrik Östman:
>> No rush for me, I can run with the patched version for now. Just so
>> that I know if I can use the next stable version, I'll monitor the
>> changelog.
>>
> I've put a cleaned up version of that patch i
Am 21.08.2016 um 13:38 schrieb Henrik Östman:
> No rush for me, I can run with the patched version for now. Just so
> that I know if I can use the next stable version, I'll monitor the
> changelog.
>
I've put a cleaned up version of that patch into the git archive. Could
you please
[owfs-code]$ g
Am 21.08.2016 um 13:25 schrieb Roland Franke:
>
>> .../latesttemp first reads data from the scratchpad, then looks
>> into data[4] to decide which resolution the data in data[0] and
>> data[1] have.
>
> Did by the first startup (When never something was read from am
> sensor with different res
No rush for me, I can run with the patched version for now. Just so that I know
if I can use the next stable version, I'll monitor the changelog.
> 21 aug. 2016 kl. 10:32 skrev Jan Kandziora :
>
>> Am 21.08.2016 um 09:25 schrieb Henrik Östman:
>> :-)
>> Thanks now it's working again!
>> Can we e
Hello,
one question in that matter:
>>
>> owread -s 192.168.10.110:4304 /uncached/28.3F28AE06/temperature12
>> // Switching to 12 bit resolution
>> owread -s 192.168.10.110:4304 /uncached/28.3F28AE06/lasttemp
>> owread -s 192.168.10.110:4304 /uncached/28.3F28AE06/lasttemp
>> owread -s
Am 21.08.2016 um 09:25 schrieb Henrik Östman:
> :-)
> Thanks now it's working again!
> Can we expect this fix in the next release?
>
Yes. But next release is still a while to go, having had the latest
release last week.
Or maybe not?
> And one more thing, since this is the first time for me wit
:-)
Thanks now it's working again!
Can we expect this fix in the next release?
And one more thing, since this is the first time for me with an sensor
that has multiple temperature resolutions.
Calling upon /lasttemp looks like its defaults to /temperature9?
So to switch between resolutions I c
Am 21.08.2016 um 02:21 schrieb Jan Kandziora:
> Am 20.08.2016 um 22:49 schrieb Henrik Östman:
>> I compiled Owfs with this patch and tried owread two times again, and
>> with the same result. I included the logfiles, I hope there is some new
>> clues inside that reveals the problem.
>> Can I verify
Am 20.08.2016 um 22:49 schrieb Henrik Östman:
> I compiled Owfs with this patch and tried owread two times again, and
> with the same result. I included the logfiles, I hope there is some new
> clues inside that reveals the problem.
> Can I verify somehow that the patch has been applied correctly?
I compiled Owfs with this patch and tried owread two times again, and
with the same result. I included the logfiles, I hope there is some new
clues inside that reveals the problem.
Can I verify somehow that the patch has been applied correctly?
// Henrik
Den 2016-08-20 kl. 11:16, skrev Jan Ka
I can't say for sure that they was not there before I started Owserver,
I didn't list the directory first. It could be some old junk lying
around, I don't know where they came from.
I re-ran owserver and only got a owserver.log file so I guess thats
proves it.
// Henrik
Den 2016-08-20 kl. 17:
Am 20.08.2016 um 16:27 schrieb Henrik Östman:
> When I run owserver with the --debug flag it created all those files,
>
Huh? I wonder how. Are you sure you hadn't some old log files around?
Kind regards
Jan
--
Am 20.08.2016 um 10:21 schrieb Henrik Östman:
> Thank you Jan for taking time too look at this!
>
> root@raspberrypi:~# owserver --debug -c /etc/owfs.conf 2>owserver.log
> DEBUG MODE
> libow version:
> 3.1p1
>
I bet you use the git version. Which is the commit I should prepare a
first patch a
Am 19.08.2016 um 20:44 schrieb Henrik Östman:
> One of my temp-sensors was defect so I switched it out for a new one,
> but then my application started to spew out exceptions when trying to
> read the temperature from the sensor.
> After some looking and scratching my head I noticed that the new
16 matches
Mail list logo
