Ok! - my value hasn't changed between Rpi,2b,3b&4b... Is there anything else I can do to troubleshoot this issue?
[image: Linkedin] <http://de.linkedin.com/in/rlagus> *Robert Lagus* +358 (0)40 662 44 99 rob...@lagus.net On Thu, 19 Sep 2019 at 13:09, Mick Sulley <m...@sulley.info> wrote: > The value and position in the grid depends, I think, on the actual adapter > it detects. > > e.g. on a system with a Sheepwalk RPi2 I see > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > on a system with a Sheepwalk RPi3 I see > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- 1c -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > Both work fine. > > > On 19/09/2019 10:56, Robert Lagus wrote: > > Resending, the last got stuck due to an attached image: > > robban@sniff:~$ *sudo i2cdetect -y 1* > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > *sudo i2cdetect -r 1* > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c-1 using receive byte commands. > I will probe address range 0x03-0x77. > Continue? [Y/n] > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > So it's the same value using -r & -y, I don't know if that's good or bad? > I have always only seen 1b, and nothing else when using -y as in guide I > was following previously (before Buster install). > > robban@sniff:~$ *sudo i2cdetect -r 2* > [sudo] password for robban: > Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or > directory > 1 robban@sniff:~$ *sudo i2cdetect -r 3* > Error: Could not open file `/dev/i2c-3' or `/dev/i2c/3': No such file or > directory > 1 robban@sniff:~$ *sudo i2cdetect -F 1* > Functionalities implemented by /dev/i2c-1: > I2C yes > SMBus Quick Command yes > SMBus Send Byte yes > SMBus Receive Byte yes > SMBus Write Byte yes > SMBus Read Byte yes > SMBus Write Word yes > SMBus Read Word yes > SMBus Process Call yes > SMBus Block Write yes > SMBus Block Read no > SMBus Block Process Call no > SMBus PEC yes > I2C Block Write yes > I2C Block Read yes > robban@sniff:~$ *sudo i2cdetect -l* > i2c-1 i2c bcm2835 I2C adapter I2C adapter > > > [image: Linkedin] <http://de.linkedin.com/in/rlagus> *Robert Lagus* > > +358 (0)40 662 44 99 > > rob...@lagus.net > > > > On Wed, 18 Sep 2019 at 19:51, Nico Bouthoorn via Owfs-developers < > owfs-developers@lists.sourceforge.net> wrote: > >> Can you see the ds2482 device on the i2c bus like?: >> >> i2cdetect -r 1 ( 2 or 3) >> WARNING! This program can confuse your I2C bus, cause data loss and worse! >> I will probe file /dev/i2c-1 using read byte commands. >> I will probe address range 0x03-0x77. >> Continue? [Y/n] >> 0 1 2 3 4 5 6 7 8 9 a b c d e f >> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- >> 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- >> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 70: -- -- -- -- -- -- -- -- >> >> >> You have to see the 18 for i2c device 0 etc >> >> >> Nico >> >> Mick Sulley wrote: >> > I am having trouble getting owfs to work on Raspbian Buster. I have >> posted on the Pi forum >> > >> > >> https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=251702&p=1536228#p1536228 >> > >> > Someone said they had the same problem but no suggestions to fix it, so >> I wonder if anyone here can give me a clue. >> > >> > I have just done a fresh install of Buster and updated. I ran >> raspi-config and enabled 1-wire and i2c. >> > I have installed owserver ow-shell >> > At first it worked, I could see devices with owdir, but it has stopped >> working, owdir returns nothing >> > I have run "sudo systemctl enable owserver.service" >> > but I see - >> > >> > |pi@pi-solar-old:~ $ sudo systemctl status owserver.service ● >> owserver.service - Backend server for 1-wire control Loaded: loaded >> (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled) >> Active: failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s >> ago Docs: man:owserver(1) Main PID: 493 (code=exited, status=0/SUCCESS) >> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Service >> RestartSec=100ms expired, scheduling Sep 13 21:47:16 pi-solar-old >> systemd[1]: owserver.service: Scheduled restart job, restart counter is at >> Sep 13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for 1-wire >> control. Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Start >> request repeated too quickly. Sep 13 21:47:16 pi-solar-old systemd[1]: >> owserver.service: Failed with result 'protocol'. Sep 13 21:47:16 >> pi-solar-old systemd[1]: Failed to start Backend server for 1-wire control. >> pi@pi-solar-old:~ $ ||| >> > >> > |I have tried disable, enable, restart for the service, I have removed >> and reinstalled owserver and ow-shell but nothing helps.| >> > >> > |Any ideas? >> > | >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Owfs-developers mailing list >> > Owfs-developers@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > >> >> -- >> 0623391101 >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> > > > _______________________________________________ > Owfs-developers mailing > listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers >
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
