You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(64) |
Sep
(106) |
Oct
(103) |
Nov
(85) |
Dec
(28) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(41) |
Feb
(87) |
Mar
(54) |
Apr
(23) |
May
(54) |
Jun
(86) |
Jul
(56) |
Aug
(35) |
Sep
(123) |
Oct
(98) |
Nov
(61) |
Dec
(83) |
2005 |
Jan
(192) |
Feb
(231) |
Mar
(114) |
Apr
(154) |
May
(45) |
Jun
(171) |
Jul
(123) |
Aug
(83) |
Sep
(95) |
Oct
(123) |
Nov
(56) |
Dec
(70) |
2006 |
Jan
(73) |
Feb
(84) |
Mar
(132) |
Apr
(186) |
May
(201) |
Jun
(121) |
Jul
(92) |
Aug
(108) |
Sep
(147) |
Oct
(156) |
Nov
(167) |
Dec
(279) |
2007 |
Jan
(159) |
Feb
(230) |
Mar
(61) |
Apr
(54) |
May
(89) |
Jun
(79) |
Jul
(57) |
Aug
(146) |
Sep
(123) |
Oct
(82) |
Nov
(56) |
Dec
(124) |
2008 |
Jan
(79) |
Feb
(64) |
Mar
(51) |
Apr
(119) |
May
(47) |
Jun
(37) |
Jul
(23) |
Aug
(44) |
Sep
(43) |
Oct
(53) |
Nov
(115) |
Dec
(93) |
2009 |
Jan
(85) |
Feb
(106) |
Mar
(56) |
Apr
(66) |
May
(114) |
Jun
(58) |
Jul
(120) |
Aug
(107) |
Sep
(17) |
Oct
(87) |
Nov
(36) |
Dec
(62) |
2010 |
Jan
(92) |
Feb
(121) |
Mar
(178) |
Apr
(115) |
May
(122) |
Jun
(33) |
Jul
(64) |
Aug
(168) |
Sep
(83) |
Oct
(67) |
Nov
(94) |
Dec
(98) |
2011 |
Jan
(240) |
Feb
(110) |
Mar
(183) |
Apr
(68) |
May
(47) |
Jun
(77) |
Jul
(72) |
Aug
(155) |
Sep
(93) |
Oct
(150) |
Nov
(110) |
Dec
(88) |
2012 |
Jan
(213) |
Feb
(148) |
Mar
(107) |
Apr
(105) |
May
(136) |
Jun
(94) |
Jul
(76) |
Aug
(29) |
Sep
(64) |
Oct
(60) |
Nov
(124) |
Dec
(71) |
2013 |
Jan
(79) |
Feb
(87) |
Mar
(87) |
Apr
(61) |
May
(100) |
Jun
(123) |
Jul
(106) |
Aug
(17) |
Sep
(44) |
Oct
(55) |
Nov
(40) |
Dec
(98) |
2014 |
Jan
(125) |
Feb
(160) |
Mar
(112) |
Apr
(61) |
May
(28) |
Jun
(50) |
Jul
(35) |
Aug
(49) |
Sep
(71) |
Oct
(115) |
Nov
(40) |
Dec
(48) |
2015 |
Jan
(51) |
Feb
(105) |
Mar
(58) |
Apr
(80) |
May
(69) |
Jun
(51) |
Jul
(24) |
Aug
(23) |
Sep
(62) |
Oct
(62) |
Nov
(201) |
Dec
(33) |
2016 |
Jan
(79) |
Feb
(83) |
Mar
(118) |
Apr
(40) |
May
(43) |
Jun
(113) |
Jul
(83) |
Aug
(54) |
Sep
(119) |
Oct
(79) |
Nov
(85) |
Dec
(60) |
2017 |
Jan
(65) |
Feb
(34) |
Mar
(25) |
Apr
(14) |
May
(10) |
Jun
|
Jul
(28) |
Aug
(49) |
Sep
(20) |
Oct
(4) |
Nov
(23) |
Dec
(28) |
2018 |
Jan
(14) |
Feb
|
Mar
(19) |
Apr
(8) |
May
|
Jun
|
Jul
(5) |
Aug
(15) |
Sep
(13) |
Oct
(17) |
Nov
(7) |
Dec
(3) |
2019 |
Jan
(2) |
Feb
(25) |
Mar
(16) |
Apr
(20) |
May
(34) |
Jun
(8) |
Jul
(26) |
Aug
(19) |
Sep
(17) |
Oct
(21) |
Nov
(3) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
(9) |
Apr
(4) |
May
(14) |
Jun
(7) |
Jul
|
Aug
(58) |
Sep
(4) |
Oct
(16) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Gregg L. <gre...@gm...> - 2024-07-08 02:48:51
|
Hello! A hasty P.S, to my earlier posting, This is a DS2484, not one of the other two that I was originally looking at, and indeed mentioned on the original Dot Org pages that we are busily migrating. The next question is one of, has anyone tried that chip out using existing software? Debian has the 3.2p4 and the 3.2p3 releases. And of course the Source Forge pages are lagging. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." On Fri, Jul 5, 2024 at 5:35 PM Gregg Levine <gre...@gm...> wrote: > > Hello! > Adafruit has gone and done something amazing, they've introduced a > module that connects the One-Wire bus to the I2C bus. Here, > https://tinyurl.com/ada5976 . > > So far the learn pages do not show anything regarding our efforts. > ----- > Gregg C Levine gre...@gm... > "This signature fought the Time Wars, time and again." |
From: Paul E. <re...@re...> - 2024-07-06 08:12:41
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I’ve been selling something that does exactly the same thing in the UK since 2010 :)<div><br></div><div>This is the current version:<br><div><br></div><div><div style="display: block;" class=""><a href="https://www.sheepwalkelectronics.co.uk/product_info.php?products_id=73&osCsid=cgmk6frce5p0v2vtcrqv90kj27">https://www.sheepwalkelectronics.co.uk/product_info.php?products_id=73</a><br></div></div><div><br id="lineBreakAtBeginningOfSignature"><div dir="ltr">Paul Everett</div><div dir="ltr"><br><blockquote type="cite">On 5 Jul 2024, at 22:36, Gregg Levine <gre...@gm...> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hello!</span><br><span>Adafruit has gone and done something amazing, they've introduced a</span><br><span>module that connects the One-Wire bus to the I2C bus. Here,</span><br><span>https://tinyurl.com/ada5976 .</span><br><span></span><br><span>So far the learn pages do not show anything regarding our efforts.</span><br><span>-----</span><br><span>Gregg C Levine gre...@gm...</span><br><span>"This signature fought the Time Wars, time and again."</span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>Owfs-developers mailing list</span><br><span>Owf...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/owfs-developers</span><br></div></blockquote></div></div></body></html> |
From: Gregg L. <gre...@gm...> - 2024-07-05 21:35:59
|
Hello! Adafruit has gone and done something amazing, they've introduced a module that connects the One-Wire bus to the I2C bus. Here, https://tinyurl.com/ada5976 . So far the learn pages do not show anything regarding our efforts. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." |
From: Gregg L. <gre...@gm...> - 2024-05-22 03:48:17
|
Hello! I just assembled a second DS2436 pod and connected the battery pack that the PiZero2W uses for power via Powerboost 1000C from Adafruit for power, and the program told what the battery voltage was, and the room temp as well. I also for this second one included a Time-In-A-Can device, in this case it holds a DS2415 one, it confirms the time of day as well. Some of you are wondering why I am doing this, there are two parts of obvious to this, the merely obvious is that I needed to confirm for myself that it works, and the incredibly obvious was one of, I can't recall if anyone had gotten these two or just the DS2436 part to work with these programs and on this platform. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." |
From: Gregg L. <gre...@gm...> - 2024-05-14 04:09:58
|
Hello! This list is too quiet so I thought I'd post my latest and greatest project. That of installing the owfs programs on a Raspberry Pi Zero. Currently I have a traditional serial adapter plugged into an FTDI based serial adapter with the DE9 connector. Basically the program is reporting the power running to a boost device from Adafruit at 3.68 (It shows 4.7 unloaded.) and the room temperature at 24C on a DS2436. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." |
From: Jan K. <jj...@gm...> - 2024-04-03 14:03:50
|
Am 02.04.24 um 06:16 schrieb Gregg Levine: > Hello! I've a new project taking shape at the moment. And it involves > making use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in > fact. And I recalled that when I enabled the GPIO settings such as > the Serial port there, and typically the I2C settings, I would see > but not enable the one for One-Wire. Now the question is one of which > GPIO one that the system selected. The website makes a reference to > someone's work, but does not provide references. > The bitbanging onewire host works with GPIO4 (pin 7 on the 40-pin connector) by default on the Raspberry Pi. Use dtoverlay=w1-gpio in /boot/config.txt. You can also select a different GPIO with dtoverlay=w1-gpio,gpiopin=4 with 4 being the GPIO you want. (Note those are called "gpiopin" but it's not the pin numbers on the 40-pin connector but the GPIO numbers.) The additional option pullup=1 may be used to enable the high-side transistor of the GPIO for a strong pullup during some operations. Note that the Raspberry Pi is a 3.3V device, so that Onewire is going to be a 3.3V Onewire. You have to wire a 1.5kΩ resistor to +3.3V to make it work correctly. If you need a 5V Onewire instead, use a level shifter as this one: | | +5V ----. ,-----+---- +3.3V | | | | | \ G | \ | / –––––' / | \ ––– – ––– \ | | | ^ | | | 5V bus line ---+-----' '--+-----+---- 3.3V bus line | D S | The transistor is a small signal N-channel enhancement mode MOSFET, e.g. a 2N7000, BS170 or MMBF170. The +5V pullup must be around 2.7kΩ. Kind regards Jan |
From: Gregg L. <gre...@gm...> - 2024-04-02 15:15:35
|
Hello! I returned this to the list, because I wanted everyone else to comment. Right now I'm busily creating my ideas. Your gadget, which I see is for sale from a good company, is a good idea, but I'm looking at this from the perspective of how Adafruit suggested it originally. Also I've enabled composite video output on the one I'm using today, and was using earlier to perfect the ideas behind composite video out from these devices. Now that's something worth writing about, elsewhere. Consider this, the original company developed a part for "smart battery packs", that's the direction I'm going in for this job. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." On Tue, Apr 2, 2024 at 8:14 AM Nico Bouthoorn <ni...@cu...> wrote: > > Hi, > > Do you have something like this? https://fstab.nl/Raspberry-Pi-zero > > my docs, this is working at my place. > > Succes, > > Nico > > > On 4/2/24 06:16, Gregg Levine wrote: > > Hello! > > I've a new project taking shape at the moment. And it involves making > > use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in fact. And > > I recalled that when I enabled the GPIO settings such as the Serial > > port there, and typically the I2C settings, I would see but not enable > > the one for One-Wire. Now the question is one of which GPIO one that > > the system selected. The website makes a reference to someone's work, > > but does not provide references. > > ----- > > Gregg C Levine gre...@gm... > > "This signature fought the Time Wars, time and again." > > > > > > _______________________________________________ > > Owfs-developers mailing list > > Owf...@li... > > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > -- > 0623391101 > |
From: Gregg L. <gre...@gm...> - 2024-04-02 04:17:25
|
Hello! I've a new project taking shape at the moment. And it involves making use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in fact. And I recalled that when I enabled the GPIO settings such as the Serial port there, and typically the I2C settings, I would see but not enable the one for One-Wire. Now the question is one of which GPIO one that the system selected. The website makes a reference to someone's work, but does not provide references. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." |
From: Michael H. <ow...@th...> - 2023-07-12 02:56:38
|
From the C API, can you connect to more than one owserver? -- Michael |
From: Mick S. <mi...@su...> - 2023-04-04 18:07:26
|
Hi People, I have some bits that are of no further use to me and wonder if they may be of use to anyone else. Qty 1 Embedded Data Systems HA7E serial to 1-wire adapter Qty 2 DS9097U Dallas Maxim Universal 1-Wire COM Port Adapter Qty 3 Hobby-boards 8 channel I/O Board All believed to be in working order. I am in the UK. Anyone interested? Cheers Mick |
From: Chris G. <cl...@is...> - 2022-05-08 13:54:37
|
On Sun, May 08, 2022 at 01:50:01PM +0100, Mick Sulley wrote: > If you have ow-shell installed then owdir should show all the devices on the > network > Well I didn't have ow-shell installed but I have now, just what I needed, thank you! -- Chris Green |
From: Mick S. <mi...@su...> - 2022-05-08 13:03:09
|
If you have ow-shell installed then owdir should show all the devices on the network Mick On 08/05/2022 13:11, Chris Green wrote: > I seem to have lost a couple of 1-wire devices, they were working a > while ago but now don't seem to be appearing. I've tried re-running > owfs but that has done no good. > > Is there some sort of debugging mode available and/or a way to list > devices on the 1-wire bus? > |
From: Chris G. <cl...@is...> - 2022-05-08 12:35:05
|
I seem to have lost a couple of 1-wire devices, they were working a while ago but now don't seem to be appearing. I've tried re-running owfs but that has done no good. Is there some sort of debugging mode available and/or a way to list devices on the 1-wire bus? -- Chris Green |
From: Gregg L. <gre...@gm...> - 2022-03-29 23:58:23
|
Hello! How'd you wire yours? He's got a strange view of that device. Well mostly as the ones I would use are all parasitic powered, which was of course not driven by a VCC3 line someplace. And the line he chose could be used for One-Wire communications via OWFS, as it's documented, someplace. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." On Tue, Mar 29, 2022 at 6:38 PM Mick Sulley <mi...@su...> wrote: > > I have just set up a Pi zero with a temp sensor following this - > > https://www.circuitbasics.com/raspberry-pi-ds18b20-temperature-sensor-tutorial/ > > It works OK but I am wondering if I can use the owfs modules with this? > If so what do I set as the server in /etc/owfs.conf > > I don't see anything in the docs > > Thanks > > Mick > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
From: Mick S. <mi...@su...> - 2022-03-29 22:38:05
|
I have just set up a Pi zero with a temp sensor following this - https://www.circuitbasics.com/raspberry-pi-ds18b20-temperature-sensor-tutorial/ It works OK but I am wondering if I can use the owfs modules with this? If so what do I set as the server in /etc/owfs.conf I don't see anything in the docs Thanks Mick |
From: Rainer D. <ml...@bo...> - 2021-12-29 19:22:37
|
Hi, unfortunately, I cannot repro the issue right now. Not sure what happened. I will follow-up if it comes back... Rainer Am Mittwoch, 29. Dezember 2021, 18:21:38 CET schrieb Rainer Dorsch via Owfs- developers: > Hi, > > I have an elabnet professional bus master (PBM) on Debian server (armhf, > cubox-i). After upgrading from Debian 10 to Debian 11 owserver does not work > anymore. If I boot the Debian 11 system with the older kernel 4.19.0 from > Debian 10, owserver works again. > > Is there any kernel dependency which I need to take care of when switching > from Kernel 4.19 to 5.10? > > Here are some logs: > > Kernel 5.10.0: > ============== > rd@home:~$ owget / > /bus.1 > /uncached > /settings > /system > /statistics > /structure > rd@home:~$ > > rd@home:~$ systemctl status owserver > ● owserver.service - Backend server for 1-wire control > Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor > preset: enabled) > Active: active (running) since Wed 2021-12-29 16:09:20 CET; 1h 21min > ago TriggeredBy: ● owserver.socket > Docs: man:owserver(1) > Main PID: 419 (owserver) > Tasks: 4 (limit: 4729) > Memory: 1.4M > CPU: 3min 42.672s > CGroup: /system.slice/owserver.service > └─419 /usr/bin/owserver --foreground -c /etc/owfs.conf > > Dec 29 16:08:58 home systemd[1]: Starting Backend server for 1-wire > control... Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(780) > systemd mode -- ignore foreground request > Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(670) systemd mode -- > ignore 'p' option > Dec 29 16:09:04 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM > detection error > Dec 29 16:09:14 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM > detection error > Dec 29 16:09:20 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM > detection error > Dec 29 16:09:20 home owserver[419]: DEFAULT: owlib.c:(208) Cannot open USB > bus master > Dec 29 16:09:20 home systemd[1]: Started Backend server for 1-wire control. > rd@home:~$ > > Restart owserver: > > Dec 29 17:31:35 home systemd[1]: Stopping Backend server for 1-wire > control... Dec 29 17:31:35 home systemd[1]: owserver.service: Succeeded. > Dec 29 17:31:35 home systemd[1]: Stopped Backend server for 1-wire control. > Dec 29 17:31:35 home systemd[1]: owserver.service: Consumed 3min 43.935s CPU > time. > Dec 29 17:31:35 home systemd[1]: Starting Backend server for 1-wire > control... Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(780) > systemd mode -- ignore foreground request > Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(670) systemd mode > -- ignore 'p' option > Dec 29 17:31:40 home owserver[20717]: DEFAULT: ow_elabnet.c:(145) PBM > detection error > Dec 29 17:31:41 home owserver[20717]: DEFAULT: owlib.c:(208) Cannot open USB > bus master > Dec 29 17:31:41 home systemd[1]: Started Backend server for 1-wire control. > > Kernel 4.19-0: > ============== > > rd@home:~$ owget / > /2D.8967C0120000 > /2D.F075C0120000 > /2D.FD6AC0120000 > /3A.C31626000000 > /3A.EDE537000000 > /3A.791426000000 > /3A.E98A25000000 > /3A.D11626000000 > /3A.51991C000000 > /3A.C16238000000 > /3A.017325000000 > /3A.1E2B26000000 > /3A.821626000000 > /3A.2CE537000000 > /3A.541826000000 > /3A.84DA37000000 > /3A.202A26000000 > /28.FF2741801604 > /28.FFF144801604 > /28.FFA666801603 > /28.FFA620841603 > /28.FFB843801604 > /bus.4 > /bus.3 > /bus.2 > /bus.1 > /uncached > /settings > /system > /statistics > /structure > /simultaneous > /alarm > rd@home:~$ > > rd@home:~$ systemctl status owserver > ● owserver.service - Backend server for 1-wire control > Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor > preset: enabled) > Active: active (running) since Wed 2021-12-29 17:46:54 CET; 6min ago > TriggeredBy: ● owserver.socket > Docs: man:owserver(1) > Main PID: 360 (owserver) > Tasks: 8 (limit: 4739) > Memory: 2.3M > CPU: 8.231s > CGroup: /system.slice/owserver.service > └─360 /usr/bin/owserver --foreground -c /etc/owfs.conf > > Dec 29 17:46:49 home systemd[1]: Starting Backend server for 1-wire > control... Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(780) > systemd mode -- ignore foreground request > Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(670) systemd mode -- > ignore 'p' option > Dec 29 17:46:54 home owserver[360]: DEFAULT: ow_elabnet.c:(145) PBM > detection error > Dec 29 17:46:54 home owserver[360]: DEFAULT: owlib.c:(208) Cannot open USB > bus master > Dec 29 17:46:54 home systemd[1]: Started Backend server for 1-wire control. > rd@home:~$ > > > Are three any additional useful logs? > > Thanks > Rainer -- Rainer Dorsch http://bokomoko.de/ |
From: Rainer D. <ml...@bo...> - 2021-12-29 18:06:09
|
Hi, I have an elabnet professional bus master (PBM) on Debian server (armhf, cubox-i). After upgrading from Debian 10 to Debian 11 owserver does not work anymore. If I boot the Debian 11 system with the older kernel 4.19.0 from Debian 10, owserver works again. Is there any kernel dependency which I need to take care of when switching from Kernel 4.19 to 5.10? Here are some logs: Kernel 5.10.0: ============== rd@home:~$ owget / /bus.1 /uncached /settings /system /statistics /structure rd@home:~$ rd@home:~$ systemctl status owserver ● owserver.service - Backend server for 1-wire control Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-12-29 16:09:20 CET; 1h 21min ago TriggeredBy: ● owserver.socket Docs: man:owserver(1) Main PID: 419 (owserver) Tasks: 4 (limit: 4729) Memory: 1.4M CPU: 3min 42.672s CGroup: /system.slice/owserver.service └─419 /usr/bin/owserver --foreground -c /etc/owfs.conf Dec 29 16:08:58 home systemd[1]: Starting Backend server for 1-wire control... Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(780) systemd mode -- ignore foreground request Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(670) systemd mode -- ignore 'p' option Dec 29 16:09:04 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection error Dec 29 16:09:14 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection error Dec 29 16:09:20 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection error Dec 29 16:09:20 home owserver[419]: DEFAULT: owlib.c:(208) Cannot open USB bus master Dec 29 16:09:20 home systemd[1]: Started Backend server for 1-wire control. rd@home:~$ Restart owserver: Dec 29 17:31:35 home systemd[1]: Stopping Backend server for 1-wire control... Dec 29 17:31:35 home systemd[1]: owserver.service: Succeeded. Dec 29 17:31:35 home systemd[1]: Stopped Backend server for 1-wire control. Dec 29 17:31:35 home systemd[1]: owserver.service: Consumed 3min 43.935s CPU time. Dec 29 17:31:35 home systemd[1]: Starting Backend server for 1-wire control... Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(780) systemd mode -- ignore foreground request Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(670) systemd mode -- ignore 'p' option Dec 29 17:31:40 home owserver[20717]: DEFAULT: ow_elabnet.c:(145) PBM detection error Dec 29 17:31:41 home owserver[20717]: DEFAULT: owlib.c:(208) Cannot open USB bus master Dec 29 17:31:41 home systemd[1]: Started Backend server for 1-wire control. Kernel 4.19-0: ============== rd@home:~$ owget / /2D.8967C0120000 /2D.F075C0120000 /2D.FD6AC0120000 /3A.C31626000000 /3A.EDE537000000 /3A.791426000000 /3A.E98A25000000 /3A.D11626000000 /3A.51991C000000 /3A.C16238000000 /3A.017325000000 /3A.1E2B26000000 /3A.821626000000 /3A.2CE537000000 /3A.541826000000 /3A.84DA37000000 /3A.202A26000000 /28.FF2741801604 /28.FFF144801604 /28.FFA666801603 /28.FFA620841603 /28.FFB843801604 /bus.4 /bus.3 /bus.2 /bus.1 /uncached /settings /system /statistics /structure /simultaneous /alarm rd@home:~$ rd@home:~$ systemctl status owserver ● owserver.service - Backend server for 1-wire control Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-12-29 17:46:54 CET; 6min ago TriggeredBy: ● owserver.socket Docs: man:owserver(1) Main PID: 360 (owserver) Tasks: 8 (limit: 4739) Memory: 2.3M CPU: 8.231s CGroup: /system.slice/owserver.service └─360 /usr/bin/owserver --foreground -c /etc/owfs.conf Dec 29 17:46:49 home systemd[1]: Starting Backend server for 1-wire control... Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(780) systemd mode -- ignore foreground request Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(670) systemd mode -- ignore 'p' option Dec 29 17:46:54 home owserver[360]: DEFAULT: ow_elabnet.c:(145) PBM detection error Dec 29 17:46:54 home owserver[360]: DEFAULT: owlib.c:(208) Cannot open USB bus master Dec 29 17:46:54 home systemd[1]: Started Backend server for 1-wire control. rd@home:~$ Are three any additional useful logs? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/ |
From: <han...@at...> - 2020-10-25 15:21:27
|
Hello! Thank you confirming that. I do not plan on using the kernel driver for the functions. -- Gregg Levine han...@at... "They were in the wrong place at the wrong time. Naturally they became heroes." Princess Leia -----Original Message----- From: Jan Kandziora <jj...@gm...> Sent: Saturday, October 24, 2020 5:37 PM To: OWFS (One-wire file system) discussion and help <owf...@li...> Subject: Re: [Owfs-developers] OWFS 3.2P4 will build on Raspberry Pi Am 24.10.20 um 06:31 schrieb han...@at...: > > Right now I'm working with Maxim to make arrangements to send a pair of > DS2484 devices, and then a pair of DS28E17 devices as well. (I might have > those.) > Be aware the DS28E17 is a 3.3V only device. It's not 5V tolerant. At first it appears to be but you will fry it instantly if a 5V onewire is connected while the power is disconnected. > We know from earlier discussions that the Pi will work to talk to a device > that uses the I2C methods. But what about those two? > The DS28E17 is only supported by the kernel driver. So you need to use it with one of the Onewire host adapters that is supported by the kernel. OWFS isn't involved but may be run in parallel with the --w1 option, or independently on other host adapters. Do not use both the ds2482 kernel driver and the --i2c option of OWFS on the same I²C Onewire hostadapter. This meant concurrent access on the DS2484 chip and leads to all kind of tricky malfunctions. Kind regards Jan _______________________________________________ Owfs-developers mailing list Owf...@li... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
From: Jan K. <jj...@gm...> - 2020-10-24 21:37:09
|
Am 24.10.20 um 06:31 schrieb han...@at...: > > Right now I'm working with Maxim to make arrangements to send a pair of > DS2484 devices, and then a pair of DS28E17 devices as well. (I might have > those.) > Be aware the DS28E17 is a 3.3V only device. It's not 5V tolerant. At first it appears to be but you will fry it instantly if a 5V onewire is connected while the power is disconnected. > We know from earlier discussions that the Pi will work to talk to a device > that uses the I2C methods. But what about those two? > The DS28E17 is only supported by the kernel driver. So you need to use it with one of the Onewire host adapters that is supported by the kernel. OWFS isn't involved but may be run in parallel with the --w1 option, or independently on other host adapters. Do not use both the ds2482 kernel driver and the --i2c option of OWFS on the same I²C Onewire hostadapter. This meant concurrent access on the DS2484 chip and leads to all kind of tricky malfunctions. Kind regards Jan |
From: Nico B. <ni...@cu...> - 2020-10-24 08:19:43
|
I'm using a raspberry zero with a ds2482-100 board. OWFS software is the one from the debian repo it's self 3.1p5. (debian 9) I's running stable for a couple of months now. Pi zero is in a greenhouse who has a ethernet connection (usb to ethernet) with ds2408 and ds2438 (humidity) https://fstab.nl/Raspberry-Pi-zero Nico han...@at... wrote: > Hello! > I've just downloaded and built the latest release of OWFS on the Raspberry > Pi device that I normally use for first tries of the OWFS system. All I saw > while doing so were the usual wonky warnings from the Debian based build > tools on the device. I haven't tried building this release on Slackware as I > do not have a 64 bit 14.2 system available so we can take this report as > factual for the Pi device. > > Hardware is a DS9097U device using an FTDI FT232 and MAX232A based adapter, > they are talking to a pair of DS2406 devices. > > Further studies will be on a Pi3 and a Pi Zero W Or a PI Zero in gadget zero > Ethernet mode talking to a regular Pi Zero. > > Right now I'm working with Maxim to make arrangements to send a pair of > DS2484 devices, and then a pair of DS28E17 devices as well. (I might have > those.) > > We know from earlier discussions that the Pi will work to talk to a device > that uses the I2C methods. But what about those two? > ----- > Gregg Levine han...@at... > "They were in the wrong place at the wrong time. Naturally they became > heroes." Princess Leia Organa of Alderann Senator > > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > -- 0623391101 |
From: <han...@at...> - 2020-10-24 04:32:01
|
Hello! I've just downloaded and built the latest release of OWFS on the Raspberry Pi device that I normally use for first tries of the OWFS system. All I saw while doing so were the usual wonky warnings from the Debian based build tools on the device. I haven't tried building this release on Slackware as I do not have a 64 bit 14.2 system available so we can take this report as factual for the Pi device. Hardware is a DS9097U device using an FTDI FT232 and MAX232A based adapter, they are talking to a pair of DS2406 devices. Further studies will be on a Pi3 and a Pi Zero W Or a PI Zero in gadget zero Ethernet mode talking to a regular Pi Zero. Right now I'm working with Maxim to make arrangements to send a pair of DS2484 devices, and then a pair of DS28E17 devices as well. (I might have those.) We know from earlier discussions that the Pi will work to talk to a device that uses the I2C methods. But what about those two? ----- Gregg Levine han...@at... "They were in the wrong place at the wrong time. Naturally they became heroes." Princess Leia Organa of Alderann Senator |
From: Martin P. <Martin.Patzak@GMX.de> - 2020-10-14 15:33:16
|
Maestro Stefano, questo sembra bellissimo! :-) On 14.10.20 16:13, Stefano Miccoli via Owfs-developers wrote: > A more succinct way would be: > > str(x).encode() > > In fact the outer call to ‘bytes’ in 'bytes(str.encode(str(x)))' is a > no-op, and python strings are objects which have an ‘encode' method, > so no need call the class method ’str.encode’. > > Another possible way is > > f"{x:d}".encode() > > or > > "{:d}".format(x).encode() > > which is more “defensive”, in the sense that the conversion fails if x > is not an integer. In fact “str(x)” is defined for almost any > imaginable object in python, and could return anything. Therefore it > is better to be a little more verbose, and be explicit on the fact > that here we are interested in a decimal integer. > > Another variant, in which we accept a float value could be > > f"{round(x):d}".encode() > > or > > f"{x:.0f}" > > but possibilities are endless. > > Bye and thank you for sharing. > > > Stefano > > >> On 14 Oct 2020, at 15:08, Mick Sulley <mi...@su... >> <mailto:mi...@su...>> wrote: >> >> I had a bit of trouble with this and thought it worth sharing the >> solution. >> >> With Python2 and pyownet I could use >> >> owp.write('/settings/timeout/directory', 60) >> >> but with Python3 that throws an error, TypeError: 'data' argument >> must be binary. I can use >> >> owp.write('/settings/timeout/directory', b'60') >> >> but if I want to use a variable for the data the format which works is - >> >> x = 60 >> owp.write('/settings/timeout/directory', bytes(str.encode(str(x)))) >> >> There may be other ways to do it but that works for me. >> >> Mick >> >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owf...@li... >> <mailto:Owf...@li...> >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
From: Mick S. <mi...@su...> - 2020-10-14 14:51:10
|
Thanks Stefano, that looks much better. On 14/10/2020 15:13, Stefano Miccoli via Owfs-developers wrote: > A more succinct way would be: > > str(x).encode() > > In fact the outer call to ‘bytes’ in 'bytes(str.encode(str(x)))' is a > no-op, and python strings are objects which have an ‘encode' method, > so no need call the class method ’str.encode’. > > Another possible way is > > f"{x:d}".encode() > > or > > "{:d}".format(x).encode() > > which is more “defensive”, in the sense that the conversion fails if x > is not an integer. In fact “str(x)” is defined for almost any > imaginable object in python, and could return anything. Therefore it > is better to be a little more verbose, and be explicit on the fact > that here we are interested in a decimal integer. > > Another variant, in which we accept a float value could be > > f"{round(x):d}".encode() > > or > > f"{x:.0f}" > > but possibilities are endless. > > Bye and thank you for sharing. > > > Stefano > > >> On 14 Oct 2020, at 15:08, Mick Sulley <mi...@su... >> <mailto:mi...@su...>> wrote: >> >> I had a bit of trouble with this and thought it worth sharing the >> solution. >> >> With Python2 and pyownet I could use >> >> owp.write('/settings/timeout/directory', 60) >> >> but with Python3 that throws an error, TypeError: 'data' argument >> must be binary. I can use >> >> owp.write('/settings/timeout/directory', b'60') >> >> but if I want to use a variable for the data the format which works is - >> >> x = 60 >> owp.write('/settings/timeout/directory', bytes(str.encode(str(x)))) >> >> There may be other ways to do it but that works for me. >> >> Mick >> >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owf...@li... >> <mailto:Owf...@li...> >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
From: Stefano M. <mo...@ic...> - 2020-10-14 14:13:56
|
A more succinct way would be: str(x).encode() In fact the outer call to ‘bytes’ in 'bytes(str.encode(str(x)))' is a no-op, and python strings are objects which have an ‘encode' method, so no need call the class method ’str.encode’. Another possible way is f"{x:d}".encode() or "{:d}".format(x).encode() which is more “defensive”, in the sense that the conversion fails if x is not an integer. In fact “str(x)” is defined for almost any imaginable object in python, and could return anything. Therefore it is better to be a little more verbose, and be explicit on the fact that here we are interested in a decimal integer. Another variant, in which we accept a float value could be f"{round(x):d}".encode() or f"{x:.0f}" but possibilities are endless. Bye and thank you for sharing. Stefano > On 14 Oct 2020, at 15:08, Mick Sulley <mi...@su...> wrote: > > I had a bit of trouble with this and thought it worth sharing the solution. > > With Python2 and pyownet I could use > > owp.write('/settings/timeout/directory', 60) > > but with Python3 that throws an error, TypeError: 'data' argument must be binary. I can use > > owp.write('/settings/timeout/directory', b'60') > > but if I want to use a variable for the data the format which works is - > > x = 60 > owp.write('/settings/timeout/directory', bytes(str.encode(str(x)))) > > There may be other ways to do it but that works for me. > > Mick > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
From: Mick S. <mi...@su...> - 2020-10-14 13:08:55
|
I had a bit of trouble with this and thought it worth sharing the solution. With Python2 and pyownet I could use owp.write('/settings/timeout/directory', 60) but with Python3 that throws an error, TypeError: 'data' argument must be binary. I can use owp.write('/settings/timeout/directory', b'60') but if I want to use a variable for the data the format which works is - x = 60 owp.write('/settings/timeout/directory', bytes(str.encode(str(x)))) There may be other ways to do it but that works for me. Mick |