Re: [Owfs-developers] python ow

I think the recommended approach is to go with some of the other python libraries, such as https://pypi.org/project/pyownet/ (using myself, works very good) or https://github.com/python-trio/trio-owfs (have not tried). These communicate with pure python code & sockets towards owserver,

Re: [Owfs-developers] owfs.org expired?

FYI, I have not received any update on this yet. On 2019-05-17 10:41, Johan Ström wrote: I have received a screenshot from Mike showing that he had the possibility to renew the expired domain. According to enom's FAQ it should be possible to perform a transfer of expired domain, but it must

Re: [Owfs-developers] owfs.org expired?

I have received a screenshot from Mike showing that he had the possibility to renew the expired domain. According to enom's FAQ it should be possible to perform a transfer of expired domain, but it must go through their support who can provide the transfer code. So, I have asked Mike if he

Re: [Owfs-developers] website

Hi, nice work! Yes, too bad owfs.org is lost.. we'll see if people can find their way to this new site. Any thoughts on making it a Github page, is it possible to dump contents to some format suitable for that? Perhaps add a link to github site? I couldn't find any Johan On 2019-05-09

Re: [Owfs-developers] owfs.org is down

generation are using? Anyway, there are currently 4 Members with full rights to the Github organization (/owfs): Jan Kandziora aka ianka Stefano Miccoli aka miccoli Matthias Urlichs aka smurfix Johan Ström aka stromnet, (me) These are currently the persons who are free to commit and merge PRs.

Re: [Owfs-developers] owfs.org is down

The old whois information: https://github.com/owfs/owfs/issues/35#issuecomment-480738656 Interestingly enough it seems to be the same if I do a whois right now, and Registry expiration date is May 13th? As for the contents, Mike has previously posted a dropbox link with a full raw dump (mysql db

Re: [Owfs-developers] owfs.org is down

11, 2019 at 8:11 PM Alastair D'Silva mailto:alast...@d-silva.org>> wrote: > > I'm happy to chip in to keep the domain. I can also secondary dns & email. > > Where is the mailing list hosted? That probably needs to live somewhere too... > &

Re: [Owfs-developers] owfs.org is down

Thanks, downloaded it. Looks like a PHP site based on something "cmsmadesimple" with pages in a mysql DB dump. This rings a bell, think someone mentioned it before. Question is, whats easiest, create something from that, or just use archive.org

Re: [Owfs-developers] owfs.org is down

nt I guess! On 2019-04-11 20:22, Mike Kalist wrote: Space: 642.11 MB/ 3.91 GB (16.05%) Bandwidth is  average 15 GB  per month On Thu, Apr 11, 2019 at 11:45 AM Johan Ström <mailto:jo...@stromnet.se>> wrote: Personally I'm voting for a technical solution such as described in https://g

Re: [Owfs-developers] owfs.org is down

...@kalist.ca> On Wed, Apr 10, 2019 at 3:54 AM Nico Bouthoorn <mailto:n...@cuora.nl>> wrote:     I can host the website if it is a problem,  i host more websites.  The number of hits and storage will not that big, i guess?     Nico     Johan Ström schreef: > Hi, >   

Re: [Owfs-developers] owfs.org is down

full github format? > > > Paul Alfille > > ---- > *From:* Johan Ström > *Sent:* Tuesday, April 9, 2019 6:37:59 AM > *To:* OWFS (One-wire file system) discussion and help; > mike.kal...@gmail.com >

Re: [Owfs-developers] owfs.org is down

Not sure if we have any contact details to anyone who is/was in charge of the site/domain/servers. Unfortunately https://sourceforge.net/p/owfs/mailman/message/35247513/ & https://sourceforge.net/p/owfs/mailman/message/35353958/ kind of ran into the sand, when it comes to the homepage. The GIT

Re: [Owfs-developers] OWFS 3.2p3 released

procedure itself, something like RELEASE.md in the project root. Stefano On 3 Oct 2018, at 23:05, Johan Ström <mailto:jo...@stromnet.se>> wrote: Hi everyone, it has been a while since last release, and I number of improvements and fixes have been added since. Yesterday I got a patc

[Owfs-developers] OWFS 3.2p3 released

Hi everyone, it has been a while since last release, and I number of improvements and fixes have been added since. Yesterday I got a patch request for the FreeBSD port with some changes.. which was already in the git repo.. so I figured it was time for a new release! This is the first one

Re: [Owfs-developers] Where are the files findtype.h and temp10.h

Hi, a quick look through the owfs projects git history does not show either of those names: $ git log --numstat|grep findtype.h $ Perhaps someone else might be familiar with the names? Regards Johan On 07/08/18 22:39, Rowan Sylvester-Bradley wrote: I am trying to rebuild a 1Wire program

Re: [Owfs-developers] Moved to GitHub!

On 08/04/18 12:38, Matthias Urlichs via Owfs-developers wrote: On 08.04.2018 10:12, Johan Ström wrote: I have taken the liberty to make the move. Great, and thanks for adding me. I have taken the opportunity to start removing the obsolete SVN tags from owfs's files. There are still a couple

[Owfs-developers] Moved to GitHub!

As discussed numerous times before, SourceForge stability is suffering, prompting discussions to move the project GitHub. This has not meet any protests, so now I have taken the liberty to make the move. The following have been done: GIT: * GH: Pushed all code to GitHub, including some old

Re: [Owfs-developers] git pull returns 502 error message

On 07/03/18 07:40, Johan Ström wrote: On 06/03/18 07:47, Jan Kandziora wrote: Am 06.03.2018 um 07:23 schrieb Johan Ström: And no opinion against here either.. SF seems to have shaped up last day or two, but who know how long that will keep.. What are your suggestions? Move GIT only, and keep

Re: [Owfs-developers] Supporting custom probes

On 16/03/18 18:45, Laurent FAILLIE via Owfs-developers wrote: Well well, I tried all aftertoon long to clone the GIT repo but got "remote end hangs unexpectively" everytime :( SourceForce is worst and worst :( Hence the github mirror (soon to be main repo perhaps?) which Jan linked to.. :)

Re: [Owfs-developers] git pull returns 502 error message

On 06/03/18 07:47, Jan Kandziora wrote: > Am 06.03.2018 um 07:23 schrieb Johan Ström: >> And no opinion against here either.. SF seems to have shaped up last day >> or two, but who know how long that will keep.. >> >> What are your suggestions? >> >> Mov

Re: [Owfs-developers] git pull returns 502 error message

And no opinion against here either.. SF seems to have shaped up last day or two, but who know how long that will keep.. What are your suggestions? Move GIT only, and keep site + mailinglist on sourceforge? Releases on Github I guess? (https://help.github.com/articles/creating-releases/) Anyway,

Re: [Owfs-developers] git pull returns 502 error message

On 02/03/18 01:48, Gregg Levine wrote: > Hello! > I have the most recent numbered release on a Pi3 (now on a Pi Zero W) > running and working. However since I previously also released the > newest code via a git clone when setting up the directory. > > Now however I need to update things, and it

Re: [Owfs-developers] Releases and Slackware-11.0

Hi, please shared with the list the problems you are having, hopefully they can be solved. My guess is that it's missing dependency or non-working detection of dependencies, and if not it would be interesting to see what breaks. Regards Johan On 15/12/17 06:10, Gregg Levine wrote: > Hello! > I

Re: [Owfs-developers] DS2423 questions

And also the M-o-a-T project: https://github.com/M-o-a-T/owslave I'm running 3 moat owslaves (37 devices total on bus) with perfect track record: one with a counter, one with some ADCs, and one with custom LED PWM since a few weeks ago (not yet pushed, X-mas lights!). It might be a bit tricky to

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

0505E-323 Y=16 D=Wed Dec 31 16:00:16 1969 --- OneWireQuery done On Nov 17, 2017, at 8:27 AM, Johan Ström <jo...@stromnet.se> wrote: On 17/11/17 16:10, Andrew Brownsword wrote: Decided to try owcapi through owserver with my application (I had opted against owserver because it seems qui

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

On 17/11/17 16:10, Andrew Brownsword wrote: Decided to try owcapi through owserver with my application (I had opted against owserver because it seems quite flakey at startup when the system reboots), just to see how it works.  Unfortunately it appears to discover even fewer of the sensors than

Re: [Owfs-developers] [GIT PULL] Fix race conditions in ow_regcomp

Changes have been merged to master, thanks for contribution! On 12/11/17 18:55, Justin Brewer wrote: Thanks for the review. On Sun, Nov 12, 2017 at 04:19:00PM +0100, Johan Ström wrote: Looks good to me, much cleaner indeed! Given that pthread_once is available everywhere? pthread_once

Re: [Owfs-developers] [GIT PULL] Fix race conditions in ow_regcomp

Looks good to me, much cleaner indeed! Given that pthread_once is available everywhere? On 11/11/17 18:53, Justin Brewer wrote: I have been experiencing crashes, or other random failures, while developing an application using libowcapi. Backtracing shows that these issues occur during

Re: [Owfs-developers] problems starting owserver on a LinkUSB with option link

# serial mode --link = ftdi:AK0048A0    # FTDI direct communication mode Thank you, Martin On 11.09.2017 21:50, Johan Ström wrote: Hi, just took a closer look at the patch Hans-Frieders sent earlier. The only thing it (effectively) does, when applied to the current owfs version

Re: [Owfs-developers] problems starting owserver on a LinkUSB with option link

Hi, just took a closer look at the patch Hans-Frieders sent earlier. The only thing it (effectively) does, when applied to the current owfs version, is to do more identical probes: It sets baud/flow to something, then calls LINK_detect_serial(..). If it fails, it does this with a few

Re: [Owfs-developers] problems starting owserver on a LinkUSB with option link

On 06/08/17 22:17, Martin Patzak (GMX) wrote: On 04.08.2017 11:09, Johan Ström wrote: Main reason for using the --link option would be the increased performance by factor 2! Not 100% correct. LinkUSB can be used through regular serial device just fine without libftdi & libusb. How

Re: [Owfs-developers] problems starting owserver on a LinkUSB with option link

On 25/07/17 20:16, Martin Patzak (GMX) wrote: > > > > On 07/25/17 15:36, Marcus Priesch wrote: >> ... >> no, i dont see any extra things you need when talking to a linkusb in >> native mode - it's also ascii, however maybe thats implemented >> differently in owfs, because configure says something

Re: [Owfs-developers] Problem to enable USB support

That looks wierd, since it reports that ftdi is enabled.. And that depends on libusb. Can you upload the config.log somewhere please (gist.github.com or similar)? On 04/04/17 17:13, samuix wrote: > Hello, > after a power failure, I have to re-install the Raspberry PI. > Unfortunately, I cannot

Re: [Owfs-developers] libusb-1.0 required version

Unfortunately FreeBSD advertises it's libusb-1.0 layer (which have libusb_strerror) as 1.0.9, so just bumping the requirement to 1.0.16 will break build on FreeBSD. A quick but ugly solution would just be to #ifdef out the calls to libusb_strerror. Other suggestions? On 11/02/17 10:51,

Re: [Owfs-developers] FTDI problem on pi

Hi, no suggestion on what it could be, but it looks like you are using the serial device layer, not the libftdi layer. I'm not sure it will make a difference, or behave more reliable, but you could try to use direct ftdi access, make sure to compile with libftdi support (or if if that is on by

Re: [Owfs-developers] Hiding incompatible device variants

On 11/02/17 09:12, Colin Reese wrote: > If you could point me to a known working hardware/software configuration on > or offline I would be quite grateful. > > Thanks, > Colin > Ok, so here is a pretty much copy-paste solution which should work: I'm running with a Mega88 with the internal 8Mhz

Re: [Owfs-developers] Hiding incompatible device variants

On 11/02/17 06:16, Alastair D'Silva wrote: > By the way, if you do an onewire LED driver, the feature I adore most is >> synchronous control over a whole bus. So multiple LED units can be pre- >> programmed to dim in a controlled fashion starting at a single point in > time. >> You had to

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

On 06/12/16 13:38, Martin Patzak (GMX) wrote: > >> By using the /latesttemp mentioned earlier, you only perform the read, >> and should thus not suffer from timeouts (given that the bus is not >> already backed up with previous queries). >> Note that a convert must always be triggered by using the

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

Hm, I thought the idea of latesttemp was to never interefere with the 85C reading. A value of 1 would mean it denies 85C today? enum temperature_problem_flag { allow_85C, deny_85C, } ; Allow = 0, deny = 1.. And deny in latesttemp means returning error instead of gbGOOD. On 06/12/16 12:17,

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

On 06/12/16 12:07, Martin Patzak (GMX) wrote: > > On 12/06/2016 11:31 AM, Colin Law wrote: >> In my code (in a node-red environment) if I get a value of 85 then I >> retry after a timeout (1 sec I think) and only if I get three 85 in a >> row do I accept it as 85. > my problem is, that I cannot

Re: [Owfs-developers] [PATCH] fix sequence number bug in w1 host adaptor code

On 18/11/16 00:24, Jan Kandziora wrote: > Am 17.11.2016 um 21:15 schrieb Enrico Hoepfner: >> Hi Jan, >> >> } >> - if ( NL_SEQ(nlp.nlm->nlmsg_seq) != (unsigned int) seq ) { >> + if ( NL_SEQ(nlp.nlm->nlmsg_seq) != NL_SEQ(seq) ) { >>

Re: [Owfs-developers] New site

On 14/09/16 10:02, Jan Kandziora wrote: > Am 14.09.2016 um 07:21 schrieb Johan Ström: >> Colin, Jan, Colin, and everyone else: Besides the above, what do you >> guys think of the GitHub wiki? Would it be an acceptable way to go >> forward? It certainly has a few d

Re: [Owfs-developers] New site

o find out. > > > On 11/09/16 21:50, Johan Ström wrote: >> On 11/09/16 22:39, Mick Sulley wrote: >> >>> I just added a new page and it seems pretty easy to me to do that, but I >>> don't see any way to create a page hierarchy, is that possible? I think &g

Re: [Owfs-developers] New site

On 10/09/16 14:02, Jan Kandziora wrote: > Am 10.09.2016 um 11:22 schrieb Colin Law: >> Is there really a need for two? Why >> not just have everything in one? >> > Because of access rights. GitHub only allows full developer access to > anything or no rights at all. Not Wiki-alone. > > We could

Re: [Owfs-developers] New site

On 10/09/16 14:54, Colin Law wrote: > On 10 September 2016 at 11:52, Johan Ström <jo...@stromnet.se> wrote: >> On 10/09/16 12:13, Colin Law wrote: >>> On 10 September 2016 at 10:21, Johan Ström <jo...@stromnet.se> wrote: >>>> ... >>>> I su

Re: [Owfs-developers] New site

On 10/09/16 14:23, Colin Law wrote: > On 10 September 2016 at 13:02, Jan Kandziora wrote: >> Am 10.09.2016 um 11:22 schrieb Colin Law: >>> Is there really a need for two? Why >>> not just have everything in one? >>> >> Because of access rights. GitHub only allows full developer

Re: [Owfs-developers] New site

On 10/09/16 12:13, Colin Law wrote: > On 10 September 2016 at 10:21, Johan Ström <jo...@stromnet.se> wrote: >> ... >> I suggest the following: >> >> a) For public site, use Github Pages with Jekyll. >> We (the developer community) would use git to push

Re: [Owfs-developers] New site

On 10/09/16 11:21, Johan Ström wrote: > > On 10/09/16 02:00, Jan Kandziora wrote: > Just as a demo on how Jekyll works: The files pushed to: https://github.com/owfs/owfs.github.io Renders into this: https://owfs.github.io/ So for example, the src of the introduction page l

Re: [Owfs-developers] New site

On 10/09/16 02:00, Jan Kandziora wrote: > Am 08.09.2016 um 22:32 schrieb Johan Ström: >> .. what else? >> > First: I'd love to get rid of are these personal blogs who give stray > information bites which are quickly outdated and totally out of control. > This is the s

Re: [Owfs-developers] New site

First of, I agree that writing all content in HTML, even if ever so basic HTML, is tedious when I just want to write text. Having to write italic instead of just *italic* does become quite tiresome in the long run.. Also, I don't want to be forced to click buttons to make my text bold, or to

Re: [Owfs-developers] New site

haps basic info & best practices on Page, and have non-collaborator contributions on wiki, where articles evolve into best practices, which goes to the site? > > Colin > > > On 9/7/2016 3:03 PM, Jan Kandziora wrote: >> Am 07.09.2016 um 21:23 schrieb Johan Ström: >>&

[Owfs-developers] New site

On 07/09/16 10:48, Jan Kandziora wrote: > Am 07.09.2016 um 07:15 schrieb Johan Ström: >> How did it go with the earlier discussed new homepage/wiki where we can >> document these things?.. :) Seems every other day these questions pop up >> on the list. >> > I think

Re: [Owfs-developers] owfs-3.1p2 - error during make

On 09/08/16 07:38, Andy Carter wrote: > On Monday 08 Aug 2016 22:45:15 Johan Ström wrote: >> Apparently libusb_strerror was added in libusb v1.0.16. Seems raspbian >> only has libusb1.0-0. > debian stable/jessie too > >> Try to uninstall libusb-devel, and install

Re: [Owfs-developers] owfs-3.1p2 - error during make

Apparently libusb_strerror was added in libusb v1.0.16. Seems raspbian only has libusb1.0-0. Try to uninstall libusb-devel, and install libusb2-devel instead. owfs should be compatible with that as well. On 08/08/16 22:27, sancho privat wrote: Hi, it works fine now when I disable USB during

Re: [Owfs-developers] Python Access to ow-shell

r "owdir", which THEN connects to owserver) for *every* *single* read/write/dir. Very inefficient. > Thanks > > Mick > > On 27/07/16 20:31, Johan Ström wrote: >> On 27/07/16 21:26, Mick Sulley wrote: >>> Looking at converting my current Python code from owfs to ow

Re: [Owfs-developers] Python Access to ow-shell

On 27/07/16 21:26, Mick Sulley wrote: > Looking at converting my current Python code from owfs to ow-shell. I > have found a few different Python bindings, any opinions on which one to > use? Also there does not seem to be much documentation on any of them, > can anyone point me in the right

Re: [Owfs-developers] Turning OWFS website into a Wiki. Was: owfs is DISABLED

On 26/07/16 10:18, Jan Kandziora wrote: > Am 26.07.2016 um 08:36 schrieb Martin Patzak (GMX): >> who else thinks the following should find it's way onto the owfs web-site? >> > Guys, face it: Paul Alfille has GONE. I hope he's okay, doing family > business, something like that. But I'm afraid he

Re: [Owfs-developers] Communication to DS9097U not working

On 27/06/16 23:39, Jan Kandziora wrote: > Am 27.06.2016 um 18:47 schrieb samuix: >> Hi, >> with the help of digitemp_DS9097U we found following: >> In the module ow_ds9097u.c is a parameter missing, we modified a line and it >> seems to work. >> we patched the module locally: ow_ds9097u.c

Re: [Owfs-developers] Communication to DS9097U not working

On 25/06/16 20:27, Jan Kandziora wrote: > Am 25.06.2016 um 15:20 schrieb samuix: > > >> DEBUG: ow_com.c:(45) Auto initialization of ftdi:i:0x0403:0x6001 >> DEBUG: ow_net_client.c:(28) Called with ftdi:i:0x0403:0x6001 >> default=10001 >> DEBUG: ow_regex.c:(201) 0: 0->20 found <><> >>

Re: [Owfs-developers] How to use eservice LCD

On 20/06/16 16:12, Jan Kandziora wrote: > Am 20.06.2016 um 07:39 schrieb Dr. Trigon: >> Hello >> >> I bought an eservice LCD [1] but it does not work. Can somebody give me some >> advice what to do? >> >> [1] https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/ >> Dr. Trigon >>

Re: [Owfs-developers] Raspberry pi Jessie, owfs-3.1.p1 not returning correct temperatures from w1 driver

On 27/04/16 17:46, John Bass wrote: > > I get tons of debug output, how is the best way of capturing it, is there a > dump debug to file option hidden somewhere? > The easiest way is to pipe to the tee' command: owserver --debug . | tee owserver-debug.log This will write the output to

Re: [Owfs-developers] DS2408 / HD44780 LCD_H regression

Great! :) On 07/04/16 20:33, Nico Bouthoorn wrote: > I've pulled the latest master, in a fresh install.It is working! > > thanks, > > Nico > > Johan Ström wrote: >> Since this HW is out there in unknown number of deployments, it makes more >> sense to ad

Re: [Owfs-developers] Louis Swart LCD issues

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 vers

Re: [Owfs-developers] DS2408 / HD44780 LCD_H regression

0-3 is not pulled up.) <0> DEBUG: ow_tcp_read.c:(113) read: 4 - 0 = 4 DEBUG: ow_transaction.c:(145) modify = 0 DEBUG: ow_transaction.c:(208) end = 0 DEBUG: ow_2408.c:(442) Error sending initial attention DEBUG: ow_2408.c:(406) Screen initialization error On 31/03/16 23:31, Johan

Re: [Owfs-developers] DS2408 / HD44780 LCD_H regression (was: Louis Swart LCD issues)

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 sources to the 3.1 version, recompiled it again. It is working now Great pinpointing! I suspect the following

Re: [Owfs-developers] Louis Swart LCD issues

ude expected vs actual behavior. > > Paul is maintainer of the code?, i've not knowledge how to debug this > further. I'd say the main one, but there are others as well. Unfortunately he has been unseen lately. > > Thanks, > > Nico > > > Johan Ström wrote: >> On

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Unittests

On 25/03/16 16:04, Stefano Miccoli wrote: Reviewing tha last commits I read a comment on the clean target in Makefile.am commit ce7d5e6ed7e4a033b5e59c681e0dcd7382ba6727 Author: Johan Strm > Date: Thu Mar 24 15:39:38 2016 +0100 clean target:

Re: [Owfs-developers] Unittests

On 24/03/16 19:52, Andy Carter wrote: > On Thursday 24 Mar 2016 16:12:49 Johan Ström wrote: > >> I just commited a very first unit-test, something which the codebase is >> lacking today. >> Also merged the fix for FS_input_ascii_array, and some other cleanups.

Re: [Owfs-developers] static analyzer (was Louis Swart LCD issues)

I just ran the LLVM static analyzer on the project. It found a few things, but not that many. Lots of false positives. I wonder how much more Coverity would find :) On 24/03/16 00:05, Johan Ström wrote: > Hi, > > sounds like a great idea. Not sure who should take the lead as projec

[Owfs-developers] Unittests

Hi, I just commited a very first unit-test, something which the codebase is lacking today. Also merged the fix for FS_input_ascii_array, and some other cleanups. The test is built with libcheck, a pretty simple C unittest library. It is by no means a decision on a lib to use, but it's a start.

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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 aroun

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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 ac62579ecbfe7acebb2873a9a08

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] [PATCH] compat.h: only include compat_netdb.h if needed

On 16/03/16 21:02, Arnout Vandecappelle wrote: > > On 03/16/16 00:00, Arnout Vandecappelle wrote: >> >> On 03/15/16 04:30, Matthias Urlichs wrote: >>> On 10.03.2016 09:38, Arnout Vandecappelle wrote: Unless of course we decide that a system-supplied getaddrinfo (and inet_ntop)

Re: [Owfs-developers] Louis Swart LCD issues

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 so

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] [PATCH] compat.h: only include compat_netdb.h if needed

On 17/03/16 07:46, fl...@franke-prem.de wrote: Hello, you can look a the following link by buildroot, where the packed owfs is now also include for an build with it. There is the patch already active:

Re: [Owfs-developers] Louis Swart LCD issues

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 def

Re: [Owfs-developers] [PATCH] owusbprobe: disable if !OW_USB

t the condition. > > Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arn...@mind.be> > Cc: Johan Ström <jo...@stromnet.se> > --- > module/owshell/src/c/owusbprobe.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/module/o

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Louis Swart LCD issues

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

Re: [Owfs-developers] Merging "moat" device specific code

With my "ftdi" branch now merged to master, I'm picking this up again, 5 months since I wrote the last message below. Any thoughts on the F0 family code, or other reasons for not merging? On 10/11/15 20:10, Johan Ström wrote: > Hi, > > a ticket was opened a few days ag

Re: [Owfs-developers] libftdi support: take 2

On 04/03/16 19:37, Jan Kandziora wrote: > Am 04.03.2016 um 19:00 schrieb Johan Ström: >> Anyone objecting to a merge? >> > You're testing better than anyone else I think, so let's finally have this. Most likely! Now it is merged, lets hope others benefits from this in the

Re: [Owfs-developers] libftdi support: take 2

, and gives recommended settings and potential USB-serial TTYs. Anyone objecting to a merge? Johan On 04/03/16 09:28, Stefano Miccoli wrote: kudos! everything is OK on my side (archlinux ARM on rPi). Stefano On 01 Mar 2016, at 22:43, Johan Ström <jo...@stromnet.se <mailto:jo...@strom

Re: [Owfs-developers] DS18B20 Question

On 01/03/16 22:38, Peter Hollenbeck wrote: > Raspberry Pi Ethernet to LinkUSB > Ethernet from LinkUSB to MS-TV > Ethernet from MS-TV to DS18B20 > > Ethernet connections to DS18B20: > DS18B20 +5V red connected to RJ45 pin 2 > DS18B20 ground blue to RJ45 pin 6 > DS18B20 data yellow to RJ45 pin 4

Re: [Owfs-developers] libftdi support: take 2

you give it a try? Also, can you check if the read/write lengths looks better now? I.e. not claiming it has written 4 million bytes...:) Johan On 01/03/16 22:24, Johan Ström wrote: On 01/03/16 14:11, Stefano Miccoli wrote: Really weird, since it should just use semi-low-level USB messages

Re: [Owfs-developers] DS18B20 Question

-wire devices. Where are cables from the 1w devices go? Directly to the Pi, or to the LinkUSB which is connected via USB to the Pi? Thanks for giving an old man some help. Peter On Tue, Mar 1, 2016 at 12:45 PM, Johan Ström <jo...@stromnet.se <mailto:jo...@stromnet.se>> wrote:

Re: [Owfs-developers] libftdi support: take 2

On 01/03/16 14:11, Stefano Miccoli wrote: Really weird, since it should just use semi-low-level USB messages to tell the device to send a Break; the OS should not interfere? Further weirdness. I just noticed that my main network (FreeBSD, same version, with LinkUSB v1.5) suffers from the

Re: [Owfs-developers] DS18B20 Question

In your initial post you wrote "I have a Raspberry Pi with LinkUSB and a MS-TV reading DC voltage." If you have a LinkUSB, you don't connect your 1-Wire devices to a GPIO pin, right? The LinkUSB should not require any pullup at all. On 01/03/16 21:16, Peter Hollenbeck wrote: It did not work

  1   2   >