Re: [Owfs-developers] bus interface statistics

Lowpowerlab sells some nice power management boards that use an Uno clone. Good support, lots of existing code. C > On Jul 14, 2019, at 03:15, Stefano Miccoli via Owfs-developers > wrote: > > > >> On 13 Jul 2019, at 22:36, Mick Sulley wrote: >> >> Thank you both for your input. I

[Owfs-developers] DS2483/DS2482 python help

Hello all, This a bit of a hail mary, and not 100% germane to the group, but I figured that at least a few of you here may have enough relevant knowledge to point me somewhere helpful. I am attempting to communicate with a DS2483 bus master from an ESP32 using micropython, and having some

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

Somewhat related to the python conversation -- has anyone considered a light-weight owfs for micropython? Or at least porting the C and python bindings? The onewire support on micropython is about where arduino was/is in its infancy. I'm in a place right now where I need to write functions for

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

e: >>> owfs.info and owfs.it forexample is still free, owfs.io also but >>> expensive. i can registrar a domain. If someone still has the >>> content of the old webiste? >>> >>> Nico >>> >>> Colin Reese schreef: >>>> Who wa

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

Who was the registrar? > On May 1, 2019, at 23:19, Nico Bouthoorn via Owfs-developers > wrote: > > Thats a pitty... i volunteered > > Matthias Urlichs via Owfs-developers schreef: >>> On 01.05.19 10:38, Nico Bouthoorn via Owfs-developers wrote: >>> Who owns the domains now?, it looks like it

Re: [Owfs-developers] Suggestions of Microcontrollers for 1-wire use.

t; network this easily scales up to tens of nodes.) >>> >>> However the main point, in my opinion, is that for most application >>> you do not need the power of a full fledged linux system-on-chip >>> (with 8GB+ storage, 1GB ram, 4 cores, GPU, hdmi port, ethern

Re: [Owfs-developers] Suggestions of Microcontrollers for 1-wire use.

> applications it is just over kill. > > So if you are not going to use the distributed “intelligence” and compute > power sleeping in your SOC nodes, the µcontroller is for sure the way to go. > > Stefano > >> On 21 Feb 2019, at 06:29, Colin Reese wrote: >>

Re: [Owfs-developers] Suggestions of Microcontrollers for 1-wire use.

Joe, I transitioned from Pis to ESP32. I was all-in on Pis, trust me. I love linux. The issues: It's not just the power supply. SDCards in this environment will corrupt eventually, absolutely. There is nothing that can protect the operating system from eventual corruption. Yes, I too, have

Re: [Owfs-developers] Strange read failure

As long as 85 is never a valid temperature. Not sure why they put the error temp in a functional range. > On Feb 19, 2019, at 05:35, Mick Sulley wrote: > > The failure happened for about 10-20 minutes, reading about every 10 seconds > or so, then it recovered and is reading fine again. > >

Re: [Owfs-developers] Reliability and Robustness of the DS2482-100 or DS2482-800

You can directly run 1wire on digital io using existing libraries, but you’d need to build your own commands for devices. I’m about to do it for a few devices on ESP32 in MicroPython. DS18B20 works out of the box but search isn’t even implemented. Not too hard though. If you want to go bus

Re: [Owfs-developers] python-ow failure with new Raspbian Stretch

I do exclusively. I was using my own wrapper reading directories but now use pyownet. C > On Dec 17, 2017, at 8:45 AM, Gregg Levine wrote: > > Hello! > I'd go a bigger step further and make them optional by way of how the > configure script is managed. I manage three

Re: [Owfs-developers] USB-I2C-1-wire for Star Networking

ermanently damaged SD Cards > and PC's damaged by lightning strikes) and now have all IT equipment on a > UPS. The 1-wire controller will be part of a home automation server and won't > be remotely installed - it will be in the study on a UPS. > > Regards > Joe P. > >&

Re: [Owfs-developers] USB-I2C-1-wire for Star Networking

WRT power, USB power is still an issue, especially over long period with fluctuating power. I use a power-management board and battery backup for this reason. Non-graceful shutdowns not only corrupt the operating system, but also potentially the SDCards permanently. This is a bad situation,

Re: [Owfs-developers] USB-I2C-1-wire for Star Networking

of the network interfaces and restarts them if down (also records in a log file which interface went down and when - WiFi features prominently in the log file). Much rather have something intrinsically stable like a wired Ethernet interface. Regards Joe P. On 13/12/17 07:54, Colin Reese wrote: WiFi

Re: [Owfs-developers] USB-I2C-1-wire for Star Networking

WiFi connectivity is the crux for sure. I've written tons of code around keeping them connected in various circumstances. If you can get them on wired, they'll stay up forever. Otherwise, you'll need to write yourself a daemon to bring it down and back up when it loses connectivity. Netifaces

Re: [Owfs-developers] System Lock-up again

There's also this: http://www.mouser.com/Search/m_ProductDetail.aspx?Mean-Well%2FHDR-15-5%2F=pHY8AWQbqIPp9NNEfa6UOQ%3D%3D I use this: https://lowpowerlab.com/guide/mightyboost/ It requires a moteino (arduino clone) to run shutdown and power management apps (and RF comms if you get one with

Re: [Owfs-developers] System Lock-up again

So many problems come from there. I use a power management board with boost converter and lipo for this reason. Deals with outages as well with graceful shutdown. C > On Sep 24, 2017, at 7:56 AM, Matthias Urlichs via Owfs-developers > wrote: > >> On

Re: [Owfs-developers] DIY Arduino based Display (LCD, OLED)

No display picture! On 9/3/2017 8:23 AM, Dr. Trigon wrote: Hello Just wanted to share my display ("LCD") solution for 1-wire networks with you: http://www.instructables.com/id/Arduino-1-wire-Display-144-Chars/ This basically covers all my needs as it is open and adoptable to future needs.

Re: [Owfs-developers] Minimal Wi-Fi power?

A micro also has far better power-down options (nA) and shorter activity periods. It all adds up. > On Aug 2, 2017, at 5:29 PM, Loren Amelang wrote: > > On Wednesday, August 2, 2017 at 10:31 AM, > owfs-developers-requ...@lists.sourceforge.net wrote: >> 1. Re: Arduino yun as

Re: [Owfs-developers] Arduino yun as wifi 1wire master

They're great, but WiFi is terrible for power, and RF916 (or even LoRa) are great for range where Bluetooth is not. Pin compatibility with power module, a well-developed ecosystem ... I've done my research on this, and for low-power remote nodes these are the goods. They're also great for power

Re: [Owfs-developers] Arduino yun as wifi 1wire master

I reiterate that I think this is shoving a round peg into a square hole. You requirements scream to me that you should be using an RF node that beams your data into a gateway Pi behind closed doors and attached to the wall. Low power + existing libraries for 1Wire. This RF unit (I use Moteinos)

Re: [Owfs-developers] Arduino yun as wifi 1wire master

If you prefer no wifi and want to run on battery, I'd suggest something like a Moteino: RF arduino clones. You can bitbang 1W and they have very low power requirements. A central gateway node on your Pi to aggregate and you're set. How and if you shove this into owfs is up to you, but I've

Re: [Owfs-developers] Unsupported 1-wire device

Out of curiosity, why did you not use one of the supported avr 1Wire slave implementations? > On May 3, 2017, at 9:55 AM, Péter Zsembery wrote: > > Dear Members, > I have implemented a TX-20 anemometer in my home made 1-wire weather station. > Since TX-20 does not

Re: [Owfs-developers] Fine-tune timing against disappearing slaves

Sven, what code are you using on your attiny? > On Feb 15, 2017, at 7:27 AM, Jan Kandziora wrote: > >> Am 15.02.2017 um 08:25 schrieb Sven Giermann: >> >> I have several temperature sensors and 1 DS2423 counter in one room. All >> are connected with a Cat.5 network cable (about 30

Re: [Owfs-developers] Hiding incompatible device variants

net.se> wrote: > >> 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 pret

Re: [Owfs-developers] Hiding incompatible device variants

If you could point me to a known working hardware/software configuration on or offline I would be quite grateful. Thanks, Colin > On Feb 11, 2017, at 12:08 AM, Johan Ström wrote: > >> On 11/02/17 06:16, Alastair D'Silva wrote: >> By the way, if you do an onewire LED

Re: [Owfs-developers] Hiding incompatible device variants

I want so badly an avr owfs slave. There are no available ADCs, and the DIO are expensive and a pain to use. I never got MOAT to work. I would use ARM if it worked out of the box. Colin On 2/10/2017 4:07 PM, Jan Kandziora wrote: > Am 10.02.2017 um 22:04 schrieb Alastair D'Silva: >> Hi folks,

Re: [Owfs-developers] 85 degree reading means error, readout timing, error should be filtered

If there is no way to distinguish 85 error/power up from 85 valid, you cannot filter it. Period. It must all be done on the other side of owfs, and the user strategy for this depends on application and expected results. You could add flags like last_was_85, or a time stamp last_non_85, but

Re: [Owfs-developers] SS-WALL-TH

I've used (and have) a couple of these, but never used them with owfs. If you need a test let me know. > On Dec 9, 2016, at 3:48 AM, Nigel Titley wrote: > > OK, sounds as though no one has. I'll look at doing it myself. > > Thanks > > Nigel > > >> On 06/12/16 18:36,

Re: [Owfs-developers] Can the owserver be "overloaded"?

Maybe dumb question, but are the additional inputs floating or connected? I noticed some interesting behavior on these as well when in use recently. Colin > On Nov 18, 2016, at 1:45 AM, Arne Raaen wrote: > > Hi, > > I have a HobbyBoards relay card based on DS2408, used

Re: [Owfs-developers] New site

I added some things. I show up as Interface Innovations at the moment. C On 9/14/2016 12:08 PM, Johan Ström wrote: > 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

Re: [Owfs-developers] New site

As long as the word uncouth is used. When it comes to family codes I have an orphaned page here that may be helpful. I'll also be restructuring my site this week. Good timing. https://www.interfaceinnovations.org/onewirefamilycodes.html C > On Sep 14, 2016, at 1:02 AM, Jan Kandziora

Re: [Owfs-developers] New site

In this case, owfs and owfs-wiki repos seem to make sense. Would be nice if there were a blacklist feature. > On Sep 11, 2016, at 10:06 AM, Johan Ström <jo...@stromnet.se> wrote: > >> On 11/09/16 18:55, Colin Reese wrote: >> I see. I didn't see there was a restr

Re: [Owfs-developers] New site

for detaching it would be have a > non-publicy-editable, but with a different access list than the main repo. > > >> On 11/09/16 18:39, Colin Reese wrote: >> Why can't there be an 'any user' wiki attached to the real repo? What has >> detaching the wiki solved? >>

Re: [Owfs-developers] New site

Why can't there be an 'any user' wiki attached to the real repo? What has detaching the wiki solved? > On Sep 11, 2016, at 9:18 AM, Johan Ström wrote: > >> 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

Re: [Owfs-developers] New site

I think a distinctly themed user wiki is probably a good idea. A bunch of the content there will be useful, but not appropriate for docs. Also, other Colin, I can't think of a better way to merge content, e.g. what info I have on the Pi with whatever you're writing, than a wysiwyg editor. C

Re: [Owfs-developers] New site

Well, I have to say that the site looks outdated and is difficult to navigate. It does not make it easy to get information that appears useful or authoritative. When I was new to owfs, I could not find even the basic information I needed to explain how owfs and owserver interact. The best

Re: [Owfs-developers] New site

> On Sep 8, 2016, at 2:53 AM, Stefano Miccoli wrote: > > >> On 08 Sep 2016, at 10:20, Jan Kandziora wrote: >> >> Face it, simple markup alone will not give you any contributors. Hell, >> non-developer documentation contributors don't want to bother with >>

Re: [Owfs-developers] New site

Here is an example of pages made using Sphinx: https://pgm.readthedocs.io/en/develop/ C > On Sep 7, 2016, at 11:29 PM, Johan Ström <jo...@stromnet.se> wrote: > >> On 08/09/16 00:13, Colin Reese wrote: >> What are the cons for a github-hosted wiki again? > We

Re: [Owfs-developers] New site

What are the cons for a github-hosted wiki again? It really seems to make sense to have all of the source and the how-to hosted in one place, in an easy to use and modify format. Admin and source control is easy to use (it is designed for it, after all), managed, and attached to the repo for

Re: [Owfs-developers] Problem with owserver not starting at boot on raspbian jessie

There's a GPIO you can read for undervoltage. 35 IIRC. > On Aug 25, 2016, at 7:35 AM, Nigel Titley wrote: > > > >> On 25/08/16 15:27, Jan Kandziora wrote: >>> Am 25.08.2016 um 16:07 schrieb Nigel Titley: >>> On 25/08/16 13:47, Matthias Urlichs wrote: > On

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

Yes. I have content to contribute. > On Jul 26, 2016, at 1:18 AM, 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,

Re: [Owfs-developers] Datanab MAX31850 reading

; correct information for the hot junction temperature. I then modified > the code to present this data on a "temperature" query. Two years later > I don't really remember the specifics. > > If you're running a version prior to 2.9p6 I'd suggest you update at > least that

Re: [Owfs-developers] Datanab MAX31850 reading

In what rev were these made? I'm on 2.9 I believe and neither make sense. What is the possibility that scratchpad gets read wrong? I have no visibility into the code but the faults I am observing are suspect, considering everything reads fine using tmex. > On Jun 30, 2016, at 3:58 AM, Paul

Re: [Owfs-developers] Datanab MAX31850 reading

for temp and 236 for thermocouple. So ... should I just read the scratchpad and do my own conversion, or can someone rewrite this? Colin On 6/29/2016 1:49 PM, Jan Kandziora wrote: > Am 29.06.2016 um 21:56 schrieb Colin Reese: >> I just pulled off the hex and noted short VDD and al

Re: [Owfs-developers] Datanab MAX31850 reading

location. C > On Jun 29, 2016, at 1:49 PM, Jan Kandziora <j...@gmx.de> wrote: > >> Am 29.06.2016 um 21:56 schrieb Colin Reese: >> I just pulled off the hex and noted short VDD and also ground short >> faults. These also showed up in owfs. I'm waiting on a scratch

Re: [Owfs-developers] Datanab MAX31850 reading

incorrectly into owfs? Thanks, Colin On 6/29/2016 12:03 PM, Colin Reese wrote: > Hello all, > > I have a Datanab TC to 1Wire that uses a MAX31850: > > http://www.datanab.com/sensors/1wire-%20thermocouple-sensor-thrmcpl_k.php > > The device reads fine using a DS9490R on Windows u

[Owfs-developers] Datanab MAX31850 reading

Hello all, I have a Datanab TC to 1Wire that uses a MAX31850: http://www.datanab.com/sensors/1wire-%20thermocouple-sensor-thrmcpl_k.php The device reads fine using a DS9490R on Windows using a package I have written to read the device as in the datasheet (OneWire Viewer does not read

Re: [Owfs-developers] Rookie Mistake

Yeah you need to have a breakout and solder skills. I was going to mention this but you'd already ordered them. C > On Jun 18, 2016, at 7:19 PM, Peter Hollenbeck wrote: > > I bought 4 DS2483R ICs from DigiKey, two bucks each. > I thought I was getting something I could

Re: [Owfs-developers] AB Electronics

I second the ds2483. Incredibly cheap and reliable. > On Jun 13, 2016, at 2:43 AM, Jan Kandziora wrote: > >> Am 13.06.2016 um 04:11 schrieb Peter Hollenbeck: >> This article: >> https://www.packtpub.com/books/content/raspberry-pi-and-1-wire >> suggests using a 1-Wire DS2482-100

Re: [Owfs-developers] Cable Length

To clarify, I want a rating, not a statement from the vendor such as "water-resistant", which can mean anything. > On Jun 9, 2016, at 11:45 AM, Steinar Midtskogen <stei...@latinitas.org> wrote: > > Colin Reese <colin.re...@gmail.com> writes: > >> Y

Re: [Owfs-developers] Cable Length

Ip65 is fine. All rated that well are solder connectors that I found. Inconvenient for customers. C > On Jun 9, 2016, at 11:45 AM, Steinar Midtskogen <stei...@latinitas.org> wrote: > > Colin Reese <colin.re...@gmail.com> writes: > >> You have a source for ip

Re: [Owfs-developers] Cable Length

ectors. From posts I have >>> read here I was under the impression that 1wire would work over Cat5 up to >>> 100m. Not for me. I am testing with one sensor, a waterproof DS18B20 from >>> Adafruit. Longest cable that works is about 45 feet. I have tried a LinkUSB >&

Re: [Owfs-developers] Cable Length

here I was under the impression that 1wire would work over Cat5 up to >> 100m. Not for me. I am testing with one sensor, a waterproof DS18B20 from >> Adafruit. Longest cable that works is about 45 feet. I have tried a LinkUSB >> and a HobbyBoards powered master. Using a Raspberry P

Re: [Owfs-developers] New install of OWFS on RPi running Jessie

t;list...@ajsystems.co.nz> wrote: > > Hi Colin, > >> On 7/06/2016, at 9:33 AM, Colin Reese <colin.re...@gmail.com> wrote: >> >> I keep 2.9.5 in my repo and give it a make install on every automated build >> I do. I am on raspbian and also Jessie and both work gr

Re: [Owfs-developers] New install of OWFS on RPi running Jessie

I keep 2.9.5 in my repo and give it a make install on every automated build I do. I am on raspbian and also Jessie and both work great. I use ds2483, however, not linkusb. See here (swig lib-fuse et al at top and owfs down below)

Re: [Owfs-developers] Cable Length

t > even the cheapest XLR connectors seem to work well with basic humidity > protection. > > I made a couple of switchboxes using XLR connectors and put them in > metal mailboxes. They've worked well for about 10 years now. > > -Steinar > > Colin Reese

Re: [Owfs-developers] Cable Length

to solder really appreciate. I run 5V/Data/Gnd/Shield as a standard pinout. C On 6/1/2016 2:34 PM, Peter Hollenbeck wrote: > Colin, > Thanks very much, especially for the tip on Lumberg connectors. I have > been wanting such for a long time. > Peter > > On Wed, Jun 1, 2016 at 1:

Re: [Owfs-developers] Cable Length

Yes, in this case you will need to make your own 8P8C --> three conductor pigtail and butt-splice or screw-terminals on a piece of protoboard. No biggie. C On 6/1/2016 1:44 PM, Peter Hollenbeck wrote: > Am using a LinkUSB connected to a Raspberry Pi. > Not 1wire-smart, > Peter > > On Wed, Jun

Re: [Owfs-developers] Cable Length

Something like this is suitable: http://www.ebay.com/itm/Security-Alarm-Cable-22-3-7-Strand-Riser-CMR-Rated-Shielded-1000-Gray-ASC2-326-/361394994944?hash=item5424d1ff00:g:BYEAAOSw37tWAyLk For exterior connectors, I avoid at all costs, but if necessary:

Re: [Owfs-developers] Cable Length

: > Any thoughts on outdoor use? I will look online but thought I would ask. > Peter > > > On Wed, Jun 1, 2016 at 12:14 PM, Colin Reese <colin.re...@gmail.com > <mailto:colin.re...@gmail.com>> wrote: > > Don't use Cat5. Just get some good 22/3 or 22/4. It's che

Re: [Owfs-developers] Cable Length

Don't use Cat5. Just get some good 22/3 or 22/4. It's cheap and easy to find. C On 6/1/2016 12:07 PM, Peter Hollenbeck wrote: > My DS18B20 works over 34 feet of Cat5e but not over 160 feet. > Resistance for the 160 foot wire is 4.7 ohms, 0.29 ohms per foot. > Resistance for the 34 foot wire is

Re: [Owfs-developers] DS9097E# External Supply

Sorry, the data sheet I meant to reference is here: https://datasheets.maximintegrated.com/en/ds/DS9097-DS9097E.pdf C On Tue, Mar 15, 2016 at 5:47 PM, Colin Reese <colin.re...@gmail.com> wrote: > Hey all, > > This is not an owfs-specific question, but more 1Wire hardware rel

[Owfs-developers] DS9097E# External Supply

Hey all, This is not an owfs-specific question, but more 1Wire hardware related. Using the DB25 connector connected to a serial port as here; http://rosset.org/linux/datasheet/DS9097U.pdf Everything is fine until I plug in a 12V supply, at which time all devices disappear from the bus. The

Re: [Owfs-developers] DS18B20 Question

Check your connector. Those Rj12s can get squidgy with enough fussing about. On Tue, Mar 1, 2016 at 3:14 PM, Peter Hollenbeck wrote: > I must have it wired wrong. > Really odd that yesterday evening it worked and I got valid ocean > temperature values. > > Back to checking

Re: [Owfs-developers] To the people willing to look at what I am thinking about for control systems

For what it's worth, I have my own Python sql query abstraction that I find infinitely useful. I create/edit all action (if this then that) operations from a web interface where I reference values using a database value notation that is then interpreted by a sanitized Python eval. Pretty

Re: [Owfs-developers] To the people willing to look at what I am thinking about for control systems

I think that by specifying no center you make the problem hard, and unnecessarily so. Otherwise it is infinitely easier. Why must you have no center? If necessary, you can make a couple or few gateways that sync and talk to other dumb(er) nodes. C > On Feb 7, 2016, at 12:39 PM, Jerry Scharf

Re: [Owfs-developers] help me in building a next generation HVAC system

Jerry, I think database is still the way to go. It's not either or with messaging, and chronological data is great to have and in some cases necessary (e.g. for PID). It allows conditional abstraction for arbitrary logic, so a condition like this is automatically parsed and processed:

Re: [Owfs-developers] Devices listed multiple times

Can somebody explain to me why on earth people use so many 1wire buses? Do many use hundreds of devices and need to split them across buses? That thing has 17 1wire channels. I have never had need for more than 1, even with >100 sensors. The whole beauty of 1Wire is extendable single bus multi

Re: [Owfs-developers] Introduce support for DS28E17 (1-Wire-to-I2C Master Bridge)

I can see no reason for not using moat, aside from differences in failure state, if any. C > On Dec 29, 2015, at 10:43 AM, Jan Kandziora wrote: > >> Am 29.12.2015 um 16:39 schrieb Ursin Soler: >> >> By this year (initial release 7/15) Maxim released the DS28E17 [1] >> which is

Re: [Owfs-developers] Server side Commands

You will have permissions issues with the user www-data. Attempting to run system services from a web application is an attempt to subvert the security limitations of this user, which are there for good reason. The other issue is that this approach does not have a way of killing services, so

Re: [Owfs-developers] 3.1p1 release, anyone?

I see. I did not grasp that the sf repo was in fact a git repo. That is where I had been grabbing things from, but not with git. C On Mon, Nov 23, 2015 at 11:30 AM, Johan Ström <jo...@stromnet.se> wrote: > On 23/11/15 20:20, Jan Kandziora wrote: > > Am 23.11.2015 um 19:15 schr

Re: [Owfs-developers] 3.1p1 release, anyone?

Yes, I'm on master. Thanks, Colin On 11/23/2015 10:15 AM, Jan Kandziora wrote: > Am 23.11.2015 um 19:01 schrieb Colin Reese: >> To double check can you point me to it? I've lost things in this pile of >> mails. >> > I see now Matthias has merged the newest changes fr

Re: [Owfs-developers] 3.1p1 release, anyone?

. Colin On 11/23/2015 9:56 AM, Jan Kandziora wrote: > Am 23.11.2015 um 18:22 schrieb Colin Reese: >> I did not rebuild my slave. Everything else is nice and fresh as of last >> night. >> > Ok, I ask more specifically: Matthias' owfs archive clone is a bit > dated. Did y

Re: [Owfs-developers] 3.1p1 release, anyone?

I've got my DS490R up and recognizing my Moat device, with a DS18B20 also connected I get: 28.246A5005 alarm F0.18FDE6789C56 simultaneous structure uncached 81.D39F2D00 bus.0 settings statisticssystem Reading the directory gives the following: ls

Re: [Owfs-developers] 3.1p1 release, anyone?

Another datum: Same result on i2c with DS2483. C On 11/23/2015 12:51 AM, Colin Reese wrote: > I've got my DS490R up and recognizing my Moat device, with a DS18B20 > also connected I get: > > 28.246A5005 alarm F0.18FDE6789C56 simultaneous structure uncached > 81.D39F

Re: [Owfs-developers] 3.1p1 release, anyone?

I did not rebuild my slave. Everything else is nice and fresh as of last night. C > On Nov 23, 2015, at 5:42 AM, Jan Kandziora <j...@gmx.de> wrote: > >> Am 23.11.2015 um 09:51 schrieb Colin Reese: >> I've got my DS490R up and recognizing my Moat device, with a DS18B20

Re: [Owfs-developers] 3.1p1 release, anyone?

I checked out moat and merged. > On Nov 23, 2015, at 9:56 AM, Jan Kandziora <j...@gmx.de> wrote: > >> Am 23.11.2015 um 18:22 schrieb Colin Reese: >> I did not rebuild my slave. Everything else is nice and fresh as of last >> night. > Ok, I ask more specifica

Re: [Owfs-developers] 3.1p1 release, anyone?

To double check can you point me to it? I've lost things in this pile of mails. > On Nov 23, 2015, at 9:56 AM, Jan Kandziora <j...@gmx.de> wrote: > >> Am 23.11.2015 um 18:22 schrieb Colin Reese: >> I did not rebuild my slave. Everything else is nice and fresh as of las

Re: [Owfs-developers] 3.1p1 release, anyone?

I now have moat version built fine on both 14.04LTS and deb armhf and will do some testing this afternoon/evening with devices. Surely, however, Matthias, has a better idea of whether it's ready for release. C On 11/22/2015 12:39 PM, Jan Kandziora wrote: > Hi all, > > we have had some

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

; fact how's the entire configuration script written? That should answer > it. > > Meanwhile where's Paul, I'm surprised he hasn't commented by now. > - > Gregg C Levine gregg.drw...@gmail.com > "This signature fought the Time Wars, time and again." > >

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

Looks like same error: ./configure: line 16287: syntax error near unexpected token `LIBUSB,' ./configure: line 16287: ` PKG_CHECK_MODULES(LIBUSB, libusb-1.0 >= 0.9.1, ENABLE_USB=true,ENABLE_USB=false)' C On 11/20/2015 10:46 PM, Colin Reese wrote: standard owfs builds fine on amhf deb

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

kefile:1001: recipe for target 'ow_daemon.lo' failed C On 11/21/2015 6:29 AM, Matthias Urlichs wrote: > On 21.11.2015 07:46, Colin Reese wrote: >> standard owfs builds fine on amhf debian, with owfs-moat results >> previously reported. >> >> On ubuntu 14.04 LTS, owfs s

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

.c is static ZERO_OR_ERROR FS_r_alarm_status(struct one_wire_query *owq) i.e nothing fancy at all. On 16/11/15 01:10, Colin Reese wrote: After bootstrap and configure, I get the following on make: ow_moat.c:476:22: internal compiler error: in set_lattice_value, at tree-ssa-

[Owfs-developers] Programming pulse

While we are on adapter compatibility, I was looking at some DS1982 by request and noticed that it and a few other of its ilk (1985,1986) require a programming pulse of 12V. I also noted that the DS9490R, linkusb, and anything else without access to 12V are not compatible with this command.

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

github.com/M-o-a-T/owfs/blob/moat/module/owlib/src/include/ow_moat.h#L40 On 13/11/15 19:26, Colin Reese wrote: Super. So MOAT read and write are F2 and F4, respectively. Is there yet any documentation on what these will return by default, what additional data are required to specify wha

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

started, this is the actual code which this thread revolves around, adding support for those special ROM commands to the official owfs branch. On 13/11/15 06:53, Colin Reese wrote: First, I just noticed the HOWTO is much improved and has some details about using the uart. Thanks Matthias. I

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

.etc.. instead of doing install. Hopefully we can get some positive votes on merging this to mainline, and the above won't be necessary :) Johan On 13/11/15 20:35, Colin Reese wrote: Thanks Johan, My goal isn't to write an alternate master -- I just want to use the Atmega328 as a 1Wire s

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

Finally got it. Built it on a machine without the updated code. Thanks. C On 11/12/2015 9:06 PM, Colin Reese wrote: Understood. From what I can see, 1Wire should be on INT0 (D2) per 152 in world.cfg. With the world.cfg below, everything compiles fine and loads from my USBTiny. I verified my

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

, how would one read this data? Is there a modified command set? Thanks, C On 11/12/2015 9:06 PM, Colin Reese wrote: Understood. From what I can see, 1Wire should be on INT0 (D2) per 152 in world.cfg. With the world.cfg below, everything compiles fine and loads from my USBTiny. I verified my

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

rable properties. During build, it will write a device/$TARGET/dev_config.h which is then included in the actual code. On 12/11/15 18:17, Colin Reese wrote: I understand, but if not already defined, what is the default value? Or, why is this not defined in the code already? On Thu, Nov 12, 20

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

clock speed. If incorrectly configured, it won't be able to talk on the > 1wire net. > > > On 12/11/15 18:04, Colin Reese wrote: > > I see this in main: > > #elif defined (__AVR_ATmega168__) || defined (__AVR_ATmega88__) || > defined(__AVR_ATmega328__) > // Clock is set via fuse

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

for 16MHz it should probably be compatible (I'm > not familiar with any specific fuses the m328 might have). > > Thus, f_cpu: 1600 > > On 12/11/15 03:39, Colin Reese wrote: > > So to avoid trying to get WinAVR to behave, on a windows machine with > > avrdude I would d

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

a-T/owslave/commit/960a7decb26ee1aa792ef41400c306ec563e77ab > > but then this: > https://github.com/M-o-a-T/owslave/commit/e573863d5a62072945dd6c07eb4e6109a6108c16 > > Are you perhaps using either old revision of the owslave code, or > perhaps old AVR-libc headers? > >

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

our avr-libc package installs (check with your package > manager how to list installed files). > > On 11/11/15 11:04, Colin Reese wrote: >> I have tried on deb Linux (Ubuntu 14.04) with apt distros, also winavr. Just >> downloaded owslave and tried fresh with the exact cfg you liste

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

this is compatible. C On 11/11/2015 12:34 PM, Matthias Urlichs wrote: > On 11.11.2015 20:45, Colin Reese wrote: >> In the meantime, getting an updated libc from elsewhere than the apt repos >> is an option? > I'd be wary of compiler/libc or libc/header incompatibilities when > upgrading

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

In the meantime, getting an updated libc from elsewhere than the apt repos is an option? C > On Nov 11, 2015, at 11:40 AM, Matthias Urlichs wrote: > >> On 11.11.2015 13:42, Johan Ström wrote: >> Also try to search for pgm_read_ptr_near and/or pgm_read* in the include >>

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

I get a number of errors on compile similar to: /moat.c:182: undefined reference to `pgm_read_ptr_near' C On 11/10/2015 1:07 PM, Johan Ström wrote: > _include: world.cfg > devices: > _default: > _ref: defaults.target.m88 > types: > _ref: defaults.types > code: [] >

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

it on the mega8 and mega88 so far, running at 8Mhz with > internal oscillator with great success. > >> On 10/11/15 20:32, Colin Reese wrote: >> Is this still only for attiny? I've been limping along with code for >> atmega328 from elsewhere and would love if someone has time

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

Is this still only for attiny? I've been limping along with code for atmega328 from elsewhere and would love if someone has time to help me port it. I love the idea. > On Nov 10, 2015, at 11:10 AM, Johan Ström wrote: > > Hi, > > a ticket was opened a few days ago

  1   2   3   >