Menu
▾
▴
owfs-developers — Developer's list for OWFS
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
|
| 2025 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mick S. <mi...@su...> - 2019-09-11 12:02:21
|
A few weeks ago I reported a problem with some DS18B20 sensors, then found it was my mistake. I have just looked at all this again and it is not that simple! Having tidied my desk I found I had a lot of DS18B20 sensors and I have been testing them - 11 work as expected 21 work fine when powered but do not work in parasitic mode. These were bought from at least 2 different suppliers, but all have code 1827C4 +051AG marked on the body. Test results are at the end if anyone is interested. In summary the 'new' DS18B20 sensors that I have not only do not support parasitic mode, but they actually pull the whole network down when connected that way. I looked on the Maxim site and didn't see any reference to problems like this, so I contacted their support. They asked for the id's and body codes of some problem sensors, which they then checked and confirmed that these are actually counterfeit. They can do nothing about it as I did not purchase they from an authorised supplier. It amazes me that anyone would bother to counterfeit a device which sells for just over £1.00, but it seems that they do! I have never tested the accuracy of sensors, just assumed that they would be sufficiently accurate for my needs, but I now I think I will try to test that as well. I also wonder if these devices my contribute to other problems, no reads, 85 reads, etc. I have just ordered a bunch of sensors from Farnell, one of their authorised suppliers in the UK. It will probably take me a while but I will replace all of my temperature sensors and see if I notice any difference. I will also keep records of body markings and id's so I have traceability. Results --- Testing with Sheepwalk RPi2 adapter, good (old) DS18B20 Connect all 3 pins (powered) Vdd = 5.01V, DQ = 4.53V, working OK, displays Power = Yes Connect Vdd to Gnd DQ = 4.53V, working OK, displays Power = No Testing with Sheepwalk RPi2 adapter, suspect (new) DS18B20 Connect all 3 pins (powered) Vdd = 5.01V, DQ = 4.53V, working OK, displays Power = Yes Connect Vdd to Gnd DQ = 0.73V, Not working & no other sensors working, also simultaneous & alarm are not there Testing with DS9490 USB adapter, good (old) DS18B20 Connect all 3 pins Vdd =335mV, DQ = 5.04V, Working but 85 on temp 9 & 10,displays power = No Connect Vdd to Gnd DQ = 5.04V, Working OK, displays power = No Testing with DS9490 USB adapter, suspect (new) DS18B20 Connect all 3 pins Vdd = 4.32V, DQ = 4.99V, not visible on network but other sensors still work Connect Vdd to Gnd DQ = 20mV, Not working & no other sensors working, also simultaneous & alarm are not there |
|
From: Steinar M. <st...@la...> - 2019-08-29 17:58:46
|
Well, connecting pin 2 and 3 didn't work. The DS2438 appears dead too. There also was a DS18B20 on the board which I desoldered and tested separately, and it was dead. So I think it's safe to assume that the entire board is lost. I'm not sure what happened. There was a lightning strike causing some damage to other parts of the weather station this summer (some parts turned to ash), but this sensor was completely disconnected (and it worked when I disconnected it in May). Even disconnected, I guess there still is a possibility that a nearby lightning strike can cause damage. I've lost one of these sensors to lightning before, but then the whole box had gone up in flames so there was no doubt what the cause was. -Steinar Steinar Midtskogen <st...@la...> writes: > Matthias Urlichs via Owfs-developers > >> This might be a stupid question, but I do wonder why that board would >> need a DS2409 in the first place. >> >> Do you have a circuit diagram? >> >> I'd simply skip that chip. Just connect pads 2, 3 and 4. > > I don't have the circuit diagram, but I think you have a good point. I > only need to access the DS2438Z whih is on the main channel, so > connecting pin 2 and 3 should suffice. (I haven't yet tested whether > the DS2438Z is working, though, and that one might have to be replaced > as well). As far as I can tell, the only reasons why the board includes > a DS2409 would be for grouping the installed sensors (temperature, > humidity, solar), and to use pin 5 (CTRL) to light a led to indicate > traffic. > > There is one catch, however, I use pin 5 as well to trigger the > ultrasound sensor so that it only measures the distance when the DS2438Z > is accessed. I can work around this, however, by making triggering the > ultrasound sensor continously. > > I have a partial diagram, just showing what I did with the LP-THS when I > built the snowdepth sensor: > > http://voksenlia.net/met/snow.php |
|
From: Steinar M. <st...@la...> - 2019-08-29 13:49:09
|
Matthias Urlichs via Owfs-developers > This might be a stupid question, but I do wonder why that board would > need a DS2409 in the first place. > > Do you have a circuit diagram? > > I'd simply skip that chip. Just connect pads 2, 3 and 4. I don't have the circuit diagram, but I think you have a good point. I only need to access the DS2438Z whih is on the main channel, so connecting pin 2 and 3 should suffice. (I haven't yet tested whether the DS2438Z is working, though, and that one might have to be replaced as well). As far as I can tell, the only reasons why the board includes a DS2409 would be for grouping the installed sensors (temperature, humidity, solar), and to use pin 5 (CTRL) to light a led to indicate traffic. There is one catch, however, I use pin 5 as well to trigger the ultrasound sensor so that it only measures the distance when the DS2438Z is accessed. I can work around this, however, by making triggering the ultrasound sensor continously. I have a partial diagram, just showing what I did with the LP-THS when I built the snowdepth sensor: http://voksenlia.net/met/snow.php -- Steinar |
|
From: Matthias U. <mat...@ur...> - 2019-08-29 08:54:29
|
On 29.08.19 09:50, Nico Bouthoorn via Owfs-developers wrote: > Many years ago I built a snow depth sensor based on the LP-THS > temperature/humidity board, but it has now had a failure. I do have > some spare parts, including the DS2409 which apparently had failed on > the board This might be a stupid question, but I do wonder why that board would need a DS2409 in the first place. Do you have a circuit diagram? I'd simply skip that chip. Just connect pads 2, 3 and 4. -- -- mit freundlichen Grüßen -- -- Matthias Urlichs |
|
From: Nico B. <ni...@cu...> - 2019-08-29 07:50:18
|
Use a smd adapter board like? to repair? You need very tip to solder and thin solder 0,5 mm, almost needle like. http://www.hobbytronics.co.uk/prototyping/smd-adapter-boards Nico Steinar Midtskogen schreef: > Hi all, > > Many years ago I built a snow depth sensor based on the LP-THS > temperature/humidity board, but it has now had a failure. I do have > some spare parts, including the DS2409 which apparently had failed on > the board, but I've had to give up repairing. First, a pad came off > when I desoldered the faulty DS2409. Then I tried to solder wires on > the DS2409 so I could still connect it to the board, but at first > attempt one leg came off. On second attempt using a another DS2409 at > least one wire came off whenever I tried to solder it on the LP-THS > board. Well, my soldering skills are not up to the task... > > Since the maker shut down a few years ago, I'm reaching out here in case > somebody has one of two of these boards laying around and would be > interested in selling, or if anyone knows where to get these boards, > please let me know. A search on eBay gave nothing. > > -- > Steinar > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > -- 0623391101 |
|
From: Steinar M. <st...@la...> - 2019-08-28 19:29:15
|
Hi all, Many years ago I built a snow depth sensor based on the LP-THS temperature/humidity board, but it has now had a failure. I do have some spare parts, including the DS2409 which apparently had failed on the board, but I've had to give up repairing. First, a pad came off when I desoldered the faulty DS2409. Then I tried to solder wires on the DS2409 so I could still connect it to the board, but at first attempt one leg came off. On second attempt using a another DS2409 at least one wire came off whenever I tried to solder it on the LP-THS board. Well, my soldering skills are not up to the task... Since the maker shut down a few years ago, I'm reaching out here in case somebody has one of two of these boards laying around and would be interested in selling, or if anyone knows where to get these boards, please let me know. A search on eBay gave nothing. -- Steinar |
|
From: Nico B. <ni...@cu...> - 2019-08-28 13:15:37
|
Hi all, I've rewritten my perl script to control my greenhouse with python. It is was for me a learning project for the python language. It can measure and control temperatures and other sensors via ADC, timers with sensor dependencies etc. It has also a php frontend to configure. It's still work in progress: https://gitlab.com/ulterius/owcontrol If you any remarks etc let me know. Nico -- 0623391101 |
|
From: Colin L. <cl...@gm...> - 2019-08-05 07:36:56
|
On Sun, 4 Aug 2019 at 23:10, Mick Sulley <mi...@su...> wrote: > > I will repay him yes. So now you have a surfeit of devices. You will just have to find lots of other things to measure. :) Colin > > On 04/08/2019 20:27, Colin Law wrote: > > Have you re-paid the first guy? Or did you send them back? > > > > Colin > > > > On Sun, 4 Aug 2019 at 20:09, Mick Sulley <mi...@su...> wrote: > >> It was all very simple. I was connecting the sensors via breadboard > >> type connectors. My old one worked, the new ones didn't. I just tried > >> connecting via the screw terminals on a Sheepwalk RPi2 and they all work > >> fine. I guess the pins on the new ones must be a bit corroded and that > >> stopped it making a good connection. > >> > >> Thanks for your help, sorry it was a bum steer. > >> > >> Mick > >> > >> On 04/08/2019 11:16, Jan Kandziora wrote: > >>> Am 04.08.19 um 10:02 schrieb Mick Sulley: > >>>> Yes it does. I also have a DS18S20 inside the test box that I use, that > >>>> shows as well. I have just tried a different DS2401 and get the same > >>>> results. > >>>> > >>> Please take a photo from the label side of the DS18B20, as well as the > >>> front and bottom side so we can check if it's obviously counterfeit. > >>> > >>> Kind regards > >>> > >>> Jan > >>> > >>> > >>> > >>> _______________________________________________ > >>> Owfs-developers mailing list > >>> Owf...@li... > >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers > >> > >> _______________________________________________ > >> Owfs-developers mailing list > >> Owf...@li... > >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > _______________________________________________ > > Owfs-developers mailing list > > 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...> - 2019-08-04 22:10:40
|
I will repay him yes. On 04/08/2019 20:27, Colin Law wrote: > Have you re-paid the first guy? Or did you send them back? > > Colin > > On Sun, 4 Aug 2019 at 20:09, Mick Sulley <mi...@su...> wrote: >> It was all very simple. I was connecting the sensors via breadboard >> type connectors. My old one worked, the new ones didn't. I just tried >> connecting via the screw terminals on a Sheepwalk RPi2 and they all work >> fine. I guess the pins on the new ones must be a bit corroded and that >> stopped it making a good connection. >> >> Thanks for your help, sorry it was a bum steer. >> >> Mick >> >> On 04/08/2019 11:16, Jan Kandziora wrote: >>> Am 04.08.19 um 10:02 schrieb Mick Sulley: >>>> Yes it does. I also have a DS18S20 inside the test box that I use, that >>>> shows as well. I have just tried a different DS2401 and get the same >>>> results. >>>> >>> Please take a photo from the label side of the DS18B20, as well as the >>> front and bottom side so we can check if it's obviously counterfeit. >>> >>> Kind regards >>> >>> Jan >>> >>> >>> >>> _______________________________________________ >>> Owfs-developers mailing list >>> Owf...@li... >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> _______________________________________________ >> Owfs-developers mailing list >> 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: Colin L. <cl...@gm...> - 2019-08-04 19:27:36
|
Have you re-paid the first guy? Or did you send them back? Colin On Sun, 4 Aug 2019 at 20:09, Mick Sulley <mi...@su...> wrote: > > It was all very simple. I was connecting the sensors via breadboard > type connectors. My old one worked, the new ones didn't. I just tried > connecting via the screw terminals on a Sheepwalk RPi2 and they all work > fine. I guess the pins on the new ones must be a bit corroded and that > stopped it making a good connection. > > Thanks for your help, sorry it was a bum steer. > > Mick > > On 04/08/2019 11:16, Jan Kandziora wrote: > > Am 04.08.19 um 10:02 schrieb Mick Sulley: > >> Yes it does. I also have a DS18S20 inside the test box that I use, that > >> shows as well. I have just tried a different DS2401 and get the same > >> results. > >> > > Please take a photo from the label side of the DS18B20, as well as the > > front and bottom side so we can check if it's obviously counterfeit. > > > > Kind regards > > > > Jan > > > > > > > > _______________________________________________ > > Owfs-developers mailing list > > 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: Colin L. <cl...@gm...> - 2019-08-04 19:26:35
|
On Sun, 4 Aug 2019 at 20:05, Mick Sulley <mi...@su...> wrote: > > Thanks Colin, I had forgotten to enable i2c. It all works now. Excellent Colin > > > On 04/08/2019 12:13, Colin Law wrote: > > How are you connecting the devices to the pi? > > Have you run raspi-config and enabled/disabled the appropriate sections? > > > > You have to use sudo with systemctl. > > > > Colin > > > > On Sun, 4 Aug 2019 at 11:29, Mick Sulley <mi...@su...> wrote: > >> I'm trying to install on Raspbian Buster and failing! > >> > >> I did the usual updates, then installed owserver owhttpd ow-shell, it > >> has installed 3.2p3 > >> > >> owdir worked, but that was with the fake devices in owfs.conf. Edited > >> that out and added dtparam=i2c1=on > >> > >> sudo i2cdetect -y 1 > >> > >> gives me > >> > >> Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or > >> directory > >> > >> Searching suggested adding dtparam=i2c1=on to /boot/config.txt > >> > >> I did that and rebooted > >> > >> I still get Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': > >> No such file or directory > >> > >> Thought I might need to restart the service but > >> > >> pi@raspberrypi:~ $ systemctl restart owserver.service > >> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === > >> Authentication is required to restart 'owserver.service'. > >> Authenticating as: root > >> Password: > >> polkit-agent-helper-1: pam_authenticate failed: Authentication failure > >> ==== AUTHENTICATION FAILED === > >> Failed to restart owserver.service: Access denied > >> See system logs and 'systemctl status owserver.service' for details. > >> pi@raspberrypi:~ $ > >> > >> I think this is the section of the syslog file, but doesn't mean much to me > >> > >> Aug 4 11:14:06 raspberrypi OWFS[493]: DEFAULT: ow_arg.c:(127) Cannot > >> access device /dev/i2c-1 > >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with > >> result 'protocol'. > >> Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server > >> for 1-wire control. > >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Service > >> RestartSec=100ms expired, scheduling restart. > >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Scheduled > >> restart job, restart counter is at 5. > >> Aug 4 11:14:06 raspberrypi systemd[1]: Stopped Backend server for > >> 1-wire control. > >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Start request > >> repeated too quickly. > >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with > >> result 'protocol'. > >> Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server > >> for 1-wire control. > >> Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Activating via > >> systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' > >> requested by ':1.9' (uid=1000 pid=501 comm="/usr/bin/pkttyagent > >> --notify-fd 5 --fallback ") > >> Aug 4 11:15:15 raspberrypi systemd[1]: Starting Authorization Manager... > >> Aug 4 11:15:15 raspberrypi polkitd[504]: started daemon version 0.105 > >> using authority implementation `local' version `0.105' > >> Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Successfully > >> activated service 'org.freedesktop.PolicyKit1' > >> Aug 4 11:15:15 raspberrypi systemd[1]: Started Authorization Manager. > >> Aug 4 11:17:01 raspberrypi CRON[517]: (root) CMD ( cd / && run-parts > >> --report /etc/cron.hourly) > >> Aug 4 11:19:37 raspberrypi systemd[1]: Starting Cleanup of Temporary > >> Directories... > >> Aug 4 11:19:37 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: > >> Succeeded. > >> > >> > >> Any ideas? > >> > >> > >> > >> _______________________________________________ > >> Owfs-developers mailing list > >> Owf...@li... > >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > _______________________________________________ > > Owfs-developers mailing list > > 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...> - 2019-08-04 19:09:41
|
It was all very simple. I was connecting the sensors via breadboard type connectors. My old one worked, the new ones didn't. I just tried connecting via the screw terminals on a Sheepwalk RPi2 and they all work fine. I guess the pins on the new ones must be a bit corroded and that stopped it making a good connection. Thanks for your help, sorry it was a bum steer. Mick On 04/08/2019 11:16, Jan Kandziora wrote: > Am 04.08.19 um 10:02 schrieb Mick Sulley: >> Yes it does. I also have a DS18S20 inside the test box that I use, that >> shows as well. I have just tried a different DS2401 and get the same >> results. >> > Please take a photo from the label side of the DS18B20, as well as the > front and bottom side so we can check if it's obviously counterfeit. > > Kind regards > > Jan > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
From: Mick S. <mi...@su...> - 2019-08-04 19:05:10
|
Thanks Colin, I had forgotten to enable i2c. It all works now. On 04/08/2019 12:13, Colin Law wrote: > How are you connecting the devices to the pi? > Have you run raspi-config and enabled/disabled the appropriate sections? > > You have to use sudo with systemctl. > > Colin > > On Sun, 4 Aug 2019 at 11:29, Mick Sulley <mi...@su...> wrote: >> I'm trying to install on Raspbian Buster and failing! >> >> I did the usual updates, then installed owserver owhttpd ow-shell, it >> has installed 3.2p3 >> >> owdir worked, but that was with the fake devices in owfs.conf. Edited >> that out and added dtparam=i2c1=on >> >> sudo i2cdetect -y 1 >> >> gives me >> >> Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or >> directory >> >> Searching suggested adding dtparam=i2c1=on to /boot/config.txt >> >> I did that and rebooted >> >> I still get Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': >> No such file or directory >> >> Thought I might need to restart the service but >> >> pi@raspberrypi:~ $ systemctl restart owserver.service >> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === >> Authentication is required to restart 'owserver.service'. >> Authenticating as: root >> Password: >> polkit-agent-helper-1: pam_authenticate failed: Authentication failure >> ==== AUTHENTICATION FAILED === >> Failed to restart owserver.service: Access denied >> See system logs and 'systemctl status owserver.service' for details. >> pi@raspberrypi:~ $ >> >> I think this is the section of the syslog file, but doesn't mean much to me >> >> Aug 4 11:14:06 raspberrypi OWFS[493]: DEFAULT: ow_arg.c:(127) Cannot >> access device /dev/i2c-1 >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with >> result 'protocol'. >> Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server >> for 1-wire control. >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Service >> RestartSec=100ms expired, scheduling restart. >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Scheduled >> restart job, restart counter is at 5. >> Aug 4 11:14:06 raspberrypi systemd[1]: Stopped Backend server for >> 1-wire control. >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Start request >> repeated too quickly. >> Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with >> result 'protocol'. >> Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server >> for 1-wire control. >> Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Activating via >> systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' >> requested by ':1.9' (uid=1000 pid=501 comm="/usr/bin/pkttyagent >> --notify-fd 5 --fallback ") >> Aug 4 11:15:15 raspberrypi systemd[1]: Starting Authorization Manager... >> Aug 4 11:15:15 raspberrypi polkitd[504]: started daemon version 0.105 >> using authority implementation `local' version `0.105' >> Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Successfully >> activated service 'org.freedesktop.PolicyKit1' >> Aug 4 11:15:15 raspberrypi systemd[1]: Started Authorization Manager. >> Aug 4 11:17:01 raspberrypi CRON[517]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> Aug 4 11:19:37 raspberrypi systemd[1]: Starting Cleanup of Temporary >> Directories... >> Aug 4 11:19:37 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: >> Succeeded. >> >> >> Any ideas? >> >> >> >> _______________________________________________ >> Owfs-developers mailing list >> 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: Colin L. <cl...@gm...> - 2019-08-04 11:14:12
|
How are you connecting the devices to the pi? Have you run raspi-config and enabled/disabled the appropriate sections? You have to use sudo with systemctl. Colin On Sun, 4 Aug 2019 at 11:29, Mick Sulley <mi...@su...> wrote: > > I'm trying to install on Raspbian Buster and failing! > > I did the usual updates, then installed owserver owhttpd ow-shell, it > has installed 3.2p3 > > owdir worked, but that was with the fake devices in owfs.conf. Edited > that out and added dtparam=i2c1=on > > sudo i2cdetect -y 1 > > gives me > > Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or > directory > > Searching suggested adding dtparam=i2c1=on to /boot/config.txt > > I did that and rebooted > > I still get Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': > No such file or directory > > Thought I might need to restart the service but > > pi@raspberrypi:~ $ systemctl restart owserver.service > ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === > Authentication is required to restart 'owserver.service'. > Authenticating as: root > Password: > polkit-agent-helper-1: pam_authenticate failed: Authentication failure > ==== AUTHENTICATION FAILED === > Failed to restart owserver.service: Access denied > See system logs and 'systemctl status owserver.service' for details. > pi@raspberrypi:~ $ > > I think this is the section of the syslog file, but doesn't mean much to me > > Aug 4 11:14:06 raspberrypi OWFS[493]: DEFAULT: ow_arg.c:(127) Cannot > access device /dev/i2c-1 > Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Service > RestartSec=100ms expired, scheduling restart. > Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Scheduled > restart job, restart counter is at 5. > Aug 4 11:14:06 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Start request > repeated too quickly. > Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Activating via > systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' > requested by ':1.9' (uid=1000 pid=501 comm="/usr/bin/pkttyagent > --notify-fd 5 --fallback ") > Aug 4 11:15:15 raspberrypi systemd[1]: Starting Authorization Manager... > Aug 4 11:15:15 raspberrypi polkitd[504]: started daemon version 0.105 > using authority implementation `local' version `0.105' > Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Successfully > activated service 'org.freedesktop.PolicyKit1' > Aug 4 11:15:15 raspberrypi systemd[1]: Started Authorization Manager. > Aug 4 11:17:01 raspberrypi CRON[517]: (root) CMD ( cd / && run-parts > --report /etc/cron.hourly) > Aug 4 11:19:37 raspberrypi systemd[1]: Starting Cleanup of Temporary > Directories... > Aug 4 11:19:37 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: > Succeeded. > > > Any ideas? > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
From: Mick S. <mi...@su...> - 2019-08-04 10:29:01
|
I'm trying to install on Raspbian Buster and failing! I did the usual updates, then installed owserver owhttpd ow-shell, it has installed 3.2p3 owdir worked, but that was with the fake devices in owfs.conf. Edited that out and added dtparam=i2c1=on sudo i2cdetect -y 1 gives me Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory Searching suggested adding dtparam=i2c1=on to /boot/config.txt I did that and rebooted I still get Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directory Thought I might need to restart the service but pi@raspberrypi:~ $ systemctl restart owserver.service ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to restart 'owserver.service'. Authenticating as: root Password: polkit-agent-helper-1: pam_authenticate failed: Authentication failure ==== AUTHENTICATION FAILED === Failed to restart owserver.service: Access denied See system logs and 'systemctl status owserver.service' for details. pi@raspberrypi:~ $ I think this is the section of the syslog file, but doesn't mean much to me Aug 4 11:14:06 raspberrypi OWFS[493]: DEFAULT: ow_arg.c:(127) Cannot access device /dev/i2c-1 Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with result 'protocol'. Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server for 1-wire control. Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Service RestartSec=100ms expired, scheduling restart. Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5. Aug 4 11:14:06 raspberrypi systemd[1]: Stopped Backend server for 1-wire control. Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Start request repeated too quickly. Aug 4 11:14:06 raspberrypi systemd[1]: owserver.service: Failed with result 'protocol'. Aug 4 11:14:06 raspberrypi systemd[1]: Failed to start Backend server for 1-wire control. Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.9' (uid=1000 pid=501 comm="/usr/bin/pkttyagent --notify-fd 5 --fallback ") Aug 4 11:15:15 raspberrypi systemd[1]: Starting Authorization Manager... Aug 4 11:15:15 raspberrypi polkitd[504]: started daemon version 0.105 using authority implementation `local' version `0.105' Aug 4 11:15:15 raspberrypi dbus-daemon[276]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Aug 4 11:15:15 raspberrypi systemd[1]: Started Authorization Manager. Aug 4 11:17:01 raspberrypi CRON[517]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 4 11:19:37 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories... Aug 4 11:19:37 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Any ideas? |
|
From: Jan K. <jj...@gm...> - 2019-08-04 10:16:51
|
Am 04.08.19 um 10:02 schrieb Mick Sulley: > Yes it does. I also have a DS18S20 inside the test box that I use, that > shows as well. I have just tried a different DS2401 and get the same > results. > Please take a photo from the label side of the DS18B20, as well as the front and bottom side so we can check if it's obviously counterfeit. Kind regards Jan |
|
From: Martin P. <Mar...@GM...> - 2019-08-04 08:12:54
|
Mick, I made very good experience with https://www.fuchs-shop.com/ All sensors and other one wire components did work at arrival :-) Martin On 03.08.19 22:57, Mick Sulley wrote: > I recently bought 4 DS18B20 sensors from eBay. When I received them > they did not work, that is they did not show up on the bus when > connected to a DS9490 USB adapter. I reported it to the seller and > got a refund. I then ordered 10 from another seller on eBay, just > tested those and none of them work. I have tried testing a known good > sensor and that shows up as expected. > > Have I just been unlucky? Has anyone else bought sensors which do not > work? Can anyone recommend a supplier whose sensors do work? > > Thanks > > Mick > > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
From: Mick S. <mi...@su...> - 2019-08-04 08:02:32
|
Yes it does. I also have a DS18S20 inside the test box that I use, that shows as well. I have just tried a different DS2401 and get the same results. On 03/08/2019 23:41, Jan Kandziora wrote: > Am 03.08.19 um 22:57 schrieb Mick Sulley: >> I recently bought 4 DS18B20 sensors from eBay. When I received them >> they did not work, that is they did not show up on the bus when >> connected to a DS9490 USB adapter. I reported it to the seller and got >> a refund. I then ordered 10 from another seller on eBay, just tested >> those and none of them work. I have tried testing a known good sensor >> and that shows up as expected. >> >> Have I just been unlucky? Has anyone else bought sensors which do not >> work? Can anyone recommend a supplier whose sensors do work? >> > Does the DS2401 iButton inside the DS9490 adapter show up? Chances are > you blew up the DS9403 protection diode or the EMI choke in the GND line. > > Kind regards > > Jan > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
From: Jan K. <jj...@gm...> - 2019-08-03 22:41:44
|
Am 03.08.19 um 22:57 schrieb Mick Sulley: > I recently bought 4 DS18B20 sensors from eBay. When I received them > they did not work, that is they did not show up on the bus when > connected to a DS9490 USB adapter. I reported it to the seller and got > a refund. I then ordered 10 from another seller on eBay, just tested > those and none of them work. I have tried testing a known good sensor > and that shows up as expected. > > Have I just been unlucky? Has anyone else bought sensors which do not > work? Can anyone recommend a supplier whose sensors do work? > Does the DS2401 iButton inside the DS9490 adapter show up? Chances are you blew up the DS9403 protection diode or the EMI choke in the GND line. Kind regards Jan |
|
From: Mick S. <mi...@su...> - 2019-08-03 20:57:44
|
I recently bought 4 DS18B20 sensors from eBay. When I received them they did not work, that is they did not show up on the bus when connected to a DS9490 USB adapter. I reported it to the seller and got a refund. I then ordered 10 from another seller on eBay, just tested those and none of them work. I have tried testing a known good sensor and that shows up as expected. Have I just been unlucky? Has anyone else bought sensors which do not work? Can anyone recommend a supplier whose sensors do work? Thanks Mick |
|
From: Henrik Ö. <tr...@gm...> - 2019-07-24 05:19:13
|
I'm running everything within a Docker container on my Raspberry Pi, that way I need not to think about all the requirements and compiling compiling Owfs myself. And if something is not working right I just throw the container away and start a new one. https://github.com/smarthomerocks/owserver // Henrik Östman Den tors 18 juli 2019 kl 16:07 skrev Jaroslav Sobota <js...@kk...>: > Hi Colin, > thanks for your reply. There seems to be a problem with owserver start > job during installation. Although an error is shown, owserver is > running. Terminal output below. > > The most suspicious is this message: > owserver.service: Failed with result 'protocol'. > > If I run "dpkg --configure -a" after the failed installation, everything > seems fine. > > In Stretch and earlier releases, everything worked out of the box. The > /etc/owfs.conf file is the same as in Stretch. > > Tried restarting the owserver service few more times and it seems the > problem only appears a few times on a clean Raspbian image. After a > while (an hour or so), I am not able to reproduce the issue anymore. > > Any hints please? Thank you. > > With kind regards, > Jaroslav > > > pi@raspberrypi:~ $ systemctl status owserver.service > ● owserver.service - Backend server for 1-wire control > Loaded: loaded (/lib/systemd/system/owserver.service; disabled; > vendor preset: enabled) > Active: active (running) since Thu 2019-07-18 12:23:25 BST; 12min ago > Docs: man:owserver(1) > Main PID: 952 (owserver) > Tasks: 2 (limit: 2200) > Memory: 772.0K > CGroup: /system.slice/owserver.service > └─952 /usr/bin/owserver -c /etc/owfs.conf > > Jul 18 12:23:25 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 12:23:25 raspberrypi OWFS[952]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:25 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > > > > root@raspberrypi:~# journalctl -n 50 > -- Logs begin at Wed 2019-07-10 01:21:16 BST, end at Thu 2019-07-18 > 14:27:04 BST. -- > Jul 18 14:13:34 raspberrypi systemd[705]: Stopped target Timers. > Jul 18 14:13:34 raspberrypi systemd[705]: gpg-agent-ssh.socket: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Closed GnuPG cryptographic > agent (ssh-agent emulation). > Jul 18 14:13:34 raspberrypi systemd[705]: dirmngr.socket: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Closed GnuPG network > certificate management daemon. > Jul 18 14:13:34 raspberrypi systemd[705]: Stopped target Paths. > Jul 18 14:13:34 raspberrypi systemd[705]: Reached target Shutdown. > Jul 18 14:13:34 raspberrypi systemd[705]: systemd-exit.service: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Started Exit the Session. > Jul 18 14:13:34 raspberrypi systemd[705]: Reached target Exit the Session. > Jul 18 14:13:34 raspberrypi systemd[708]: > pam_unix(systemd-user:session): session closed for user pi > Jul 18 14:13:34 raspberrypi systemd[1]: us...@10...rvice: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopped User Manager for UID 1000. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopping User Runtime Directory > /run/user/1000... > Jul 18 14:13:34 raspberrypi systemd[757]: run-user-1000.mount: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: run-user-1000.mount: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: use...@10...rvice: > Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopped User Runtime Directory > /run/user/1000. > Jul 18 14:13:34 raspberrypi systemd[1]: Removed slice User Slice of UID > 1000. > Jul 18 14:14:00 raspberrypi groupadd[945]: group added to /etc/group: > name=Debian-ow, GID=114 > Jul 18 14:14:00 raspberrypi groupadd[945]: group added to /etc/gshadow: > name=Debian-ow > Jul 18 14:14:00 raspberrypi groupadd[945]: new group: name=Debian-ow, > GID=114 > Jul 18 14:14:00 raspberrypi useradd[950]: new user: name=Debian-ow, > UID=109, GID=114, home=/var/lib/owfs, shell=/usr/sbin/nologin > Jul 18 14:14:00 raspberrypi chage[957]: changed password expiry for > Debian-ow > Jul 18 14:14:00 raspberrypi chfn[961]: changed user 'Debian-ow' information > Jul 18 14:14:04 raspberrypi systemd[1]: Reloading. > Jul 18 14:14:04 raspberrypi systemd[1]: ge...@tt...rvice: Current > command vanished from the unit file, execution of the command list won't > be resumed. > Jul 18 14:14:04 raspberrypi systemd[1]: ser...@tt...rvice: > Current command vanished from the unit file, execution of the command > list won't be resumed. > Jul 18 14:14:04 raspberrypi systemd[1]: Reloading. > Jul 18 14:14:05 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 14:14:05 raspberrypi OWFS[1134]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > Jul 18 14:14:05 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Service > RestartSec=100ms expired, scheduling restart. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Scheduled > restart job, restart counter is at 1. > Jul 18 14:14:05 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > Jul 18 14:14:05 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 14:14:05 raspberrypi OWFS[1178]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:14:05 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > Jul 18 14:14:07 raspberrypi systemd[1]: Reloading. > Jul 18 14:17:01 raspberrypi CRON[1256]: pam_unix(cron:session): session > opened for user root by (uid=0) > Jul 18 14:17:01 raspberrypi CRON[1260]: (root) CMD ( cd / && run-parts > --report /etc/cron.hourly) > Jul 18 14:17:01 raspberrypi CRON[1256]: pam_unix(cron:session): session > closed for user root > Jul 18 14:17:34 raspberrypi systemd[1]: Stopping Backend server for > 1-wire control... > Jul 18 14:17:34 raspberrypi systemd[1]: owserver.service: Succeeded. > Jul 18 14:17:34 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > Jul 18 14:17:56 raspberrypi OWFS[1282]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:27:04 raspberrypi systemd[1]: Starting Cleanup of Temporary > Directories... > Jul 18 14:27:04 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: > Succeeded. > Jul 18 14:27:04 raspberrypi systemd[1]: Started Cleanup of Temporary > Directories. > > > > pi@raspberrypi:~ $ journalctl -xe > Jul 18 12:23:24 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > -- Subject: A start job for unit owserver.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has begun execution. > -- > -- The job identifier is 320. > Jul 18 12:23:24 raspberrypi OWFS[944]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:24 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The unit owserver.service has entered the 'failed' state with result > 'protocol'. > Jul 18 12:23:24 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > -- Subject: A start job for unit owserver.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has finished with a failure. > -- > -- The job identifier is 320 and the job result is failed. > Jul 18 12:23:24 raspberrypi systemd[1]: owserver.service: Service > RestartSec=100ms expired, scheduling restart. > Jul 18 12:23:25 raspberrypi systemd[1]: owserver.service: Scheduled > restart job, restart counter is at 1. > -- Subject: Automatic restarting of a unit has been scheduled > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Automatic restarting of the unit owserver.service has been scheduled, > as the result for > -- the configured Restart= setting for the unit. > Jul 18 12:23:25 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > -- Subject: A stop job for unit owserver.service has finished > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A stop job for unit owserver.service has finished. > -- > -- The job identifier is 377 and the job result is done. > Jul 18 12:23:25 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > -- Subject: A start job for unit owserver.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has begun execution. > -- > -- The job identifier is 377. > Jul 18 12:23:25 raspberrypi OWFS[952]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:25 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > -- Subject: A start job for unit owserver.service has finished successfully > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has finished successfully. > -- > -- The job identifier is 377. > Jul 18 12:23:26 raspberrypi systemd[1]: Reloading. > Jul 18 12:23:28 raspberrypi sudo[700]: pam_unix(sudo:session): session > closed for user root > > > > On 16.07.2019 22:43, Colin Law wrote: > > On Tue, 16 Jul 2019 at 19:08, Jaroslav Sobota <js...@kk...> > wrote: > >> > >> Creating config file /etc/owfs.conf with new version > >> Setting up libow-3.2-3:armhf (3.2p3+dfsg1-2) ... > >> Setting up owserver (3.2p3+dfsg1-2) ... > >> Job for owserver.service failed because the service did not take the > >> steps requi red by its unit > >> configuration. > >> See "systemctl status owserver.service" and "journalctl -xe" for > details. > > > > Not certain, but I think it installed ok, but failed to start. Did > > you run the commands suggested to see what it says? Perhaps you just > > need to setup the config properly. > > > > Colin > > > > > > _______________________________________________ > > Owfs-developers mailing list > > 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: Roland F. <fl...@fr...> - 2019-07-22 19:40:37
|
If you will need an I2C adapter including an 8-channel 1-wire controller, you may take an look at: https://www.axiris.eu/en/index.php/1-wire/1-wire-mini-host Here is an DS2482-800 installed inside regarding the wiring-diagram Best regards, Roland Franke -----Ursprüngliche Nachricht----- From: Mick Sulley Sent: Monday, July 22, 2019 8:36 PM To: owf...@li... Subject: Re: [Owfs-developers] 1-wire hubs Yes indeed, this was the message I have a Hobyboards 6 channel hub which has been in my drawer for many years. I did use it but changed over to a Sheepwalk RPi3 ages ago because that works directly with a Pi. I have been meaning to put it on eBay but never got around to it, do you want it? Cheers Mick On 22/07/2019 14:20, Jim Duda wrote: > Hi, > > Someone sent me a private email regards having an extra hobbyboards hub. > I just happened to notice it got into my spam folder. > I went to respond, but somehow lost the email. > > If you are listening, can you try again please? > I am indeed interested. > > Regards, > > Jim > > > On 7/20/19 10:52 AM, Jim Duda wrote: >> Hello, >> >> I have a 6 port 1-wire HUB that I purchased years ago from >> hobbyboards.com >> I think the device has finally stopped working. >> Hobbyboards hasn't come back online yet. >> >> Can anyone offer any advice on any available 1-wire hub devices for sale? >> >> The only one I can find is from unipi. >> https://www.unipi.technology/1-wire-8-port-hub-p31 >> >> Any advice appreciated. >> >> Regards, >> >> Jim >> > > > > _______________________________________________ > Owfs-developers mailing list > 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...> - 2019-07-22 18:36:37
|
Yes indeed, this was the message I have a Hobyboards 6 channel hub which has been in my drawer for many years. I did use it but changed over to a Sheepwalk RPi3 ages ago because that works directly with a Pi. I have been meaning to put it on eBay but never got around to it, do you want it? Cheers Mick On 22/07/2019 14:20, Jim Duda wrote: > Hi, > > Someone sent me a private email regards having an extra hobbyboards hub. > I just happened to notice it got into my spam folder. > I went to respond, but somehow lost the email. > > If you are listening, can you try again please? > I am indeed interested. > > Regards, > > Jim > > > On 7/20/19 10:52 AM, Jim Duda wrote: >> Hello, >> >> I have a 6 port 1-wire HUB that I purchased years ago from hobbyboards.com >> I think the device has finally stopped working. >> Hobbyboards hasn't come back online yet. >> >> Can anyone offer any advice on any available 1-wire hub devices for sale? >> >> The only one I can find is from unipi. >> https://www.unipi.technology/1-wire-8-port-hub-p31 >> >> Any advice appreciated. >> >> Regards, >> >> Jim >> > > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
From: Jim D. <ji...@du...> - 2019-07-22 13:20:23
|
Hi, Someone sent me a private email regards having an extra hobbyboards hub. I just happened to notice it got into my spam folder. I went to respond, but somehow lost the email. If you are listening, can you try again please? I am indeed interested. Regards, Jim On 7/20/19 10:52 AM, Jim Duda wrote: > Hello, > > I have a 6 port 1-wire HUB that I purchased years ago from hobbyboards.com > I think the device has finally stopped working. > Hobbyboards hasn't come back online yet. > > Can anyone offer any advice on any available 1-wire hub devices for sale? > > The only one I can find is from unipi. > https://www.unipi.technology/1-wire-8-port-hub-p31 > > Any advice appreciated. > > Regards, > > Jim > |
|
From: Gregg L. <gre...@gm...> - 2019-07-21 16:05:45
|
Hello! Thank you for confirming my thoughts on the VB stuff. As for the next release, I'll download that today, and add it to my collection. As for creating an GIT issue, I'm going to adopt a wait and see to this one. It's because Norton can be told to ignore stuff. ----- Gregg C Levine gre...@gm... "This signature fought the Time Wars, time and again." On Sun, Jul 21, 2019 at 6:07 AM Stefano Miccoli <mo...@ic...> wrote: > > The last official source release is v3.2p3 available at https://github.com/owfs/owfs/releases/tag/v3.2p3 > > There have been a number to commits since that release, but should not touch the very old visual basic files. > > BTW, I think that opening an issue could still be usefule for documenting this problem, including the exact Norton version and the exact file that the antivirus flags as a Trojan. > > SM > > On 18 Jul 2019, at 05:32, Gregg Levine <gre...@gm...> wrote: > > Hello! > I'd be delighted to do so, except all I have is what I stated above, > and perhaps the responses (as idiotic as they are) from Norton itself. > I also followed the same steps to download a new GIT blob onto a > folder on a Raspberry Pi to which I'd previously gotten OWFS to work > that way. I've since compressed it into a TAR file which was also > BZIP2 compressed. > > Depending on what your response is, I'll retrieve it and try again. > This time extracting that over what is already there. > > Can you tell me, also, if there where any commits to the directory recently? > ----- > Gregg C Levine gre...@gm... > "This signature fought the Time Wars, time and again." > > On Wed, Jul 17, 2019 at 1:22 PM Stefano Miccoli via Owfs-developers > <owf...@li...> wrote: > > > Can you please open an issue at https://github.com/owfs/owfs/issues with more details? > > SM > > > On 16 Jul 2019, at 01:34, Gregg Levine <gre...@gm...> wrote: > > Hello! > Okay I found and downloaded the OWS source code from the new GIT > location. But during the process of doing that, I found that Norton > insisted that there was a Trojan hiding in the VB example of one of > the OWFS programs. I am convinced that this is a rare false positive > for the Norton antivirus program. > > Incidentally this was downloaded onto a Linux on Windows instance > which is posing as SuSe SLES 12 server when running. I've built and > run the latest release on it and actually gotten it to work. > ----- > 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 > > > _______________________________________________ > Owfs-developers mailing list > Owf...@li... > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > |
101 messages has been excluded from this view by a project administrator.
