AMG8833 sensor i2c address

Posted on
Sun Jun 30, 2019 6:57 am
ostr offline
Posts: 7
Joined: Jul 27, 2015

AMG8833 sensor i2c address

I've started having a look at the AMG8833 sensor, as a presence detector where a person is stationary - looks like this could work quite well.

A single sensor would work for most rooms, however for larger rooms 2 sensors may be required.

My understanding for these sensors (I'm trying out the Sparkfun Qwiic board) is that the alternative i2c address is 0x68 (the default being 0x69) - however the plugin has the options of 0x69 and 0x6B. Can this be amended to add 0x68?
Attachments
Screenshot 2019-06-30 at 13.38.22.png
Screenshot 2019-06-30 at 13.38.22.png (389.7 KiB) Viewed 4028 times

Posted on
Sun Jun 30, 2019 7:35 am
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

Sure .. later today

When you plugin the sensor do on the rpi
i2cdetect -y 1
It will show you the actual address the sensor uses.




Sent from my iPhone using Tapatalk

Posted on
Sun Jun 30, 2019 8:24 am
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

posted v .294 with added i2c address.

Karl
Attachments
Screen Shot 2019-06-30 at 09.23.51.png
Screen Shot 2019-06-30 at 09.23.51.png (51.87 KiB) Viewed 4000 times

Posted on
Sun Jun 30, 2019 9:25 am
ostr offline
Posts: 7
Joined: Jul 27, 2015

Re: AMG8833 sensor i2c address

Awesome - thanks!

Sensors up and running - now to find a suitable case or mounting...

Posted on
Sun Jun 30, 2019 2:08 pm
ostr offline
Posts: 7
Joined: Jul 27, 2015

Re: AMG8833 sensor i2c address

Updating to v.294 I'm now getting an error in the event log every couple of minutes:

Code: Select all
30 Jun 2019 at 20:51:02
   piBeacon Warning                RPI# 0 check , too many empty messages in a row: 2
   piBeacon Warning                sending reboot command to RPI


However, this also happens on downgrade to v.293 - but not on v.291

Posted on
Sun Jun 30, 2019 3:16 pm
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

need a little more info:

could you ssh to the RPi and do
Code: Select all
tail -f /var/log/piBeacon.log
also in config set set debug beacon data ON

Karl

Posted on
Sun Jun 30, 2019 4:20 pm
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

AND please set ETH and WLAN parameters in config (and in RPI edit). those are new in these versions

Karl

Posted on
Mon Jul 01, 2019 3:29 pm
ostr offline
Posts: 7
Joined: Jul 27, 2015

Re: AMG8833 sensor i2c address

Hi - thanks for coming back on this

Beacon data debug set to on..

Code: Select all
pi@raspberrypi:~ $ tail -f /var/log/piBeacon.log
   UP RUNNING
   RX bytes:1581 acl:0 sco:0 events:103 errors:0
   TX bytes:5069 acl:0 sco:0 commands:103 errors:0

 
20190701-21:32:22 beaconloop      L:-1= my BLE mac# is : B8:27:EB:B2:3E:A2
20190701-21:32:22 beaconloop      L:-1= ble thread started
20190701-21:32:22 beaconloop      L:-1= starting loop
20190701-21:32:23 master          L:-1= IP find:: IPs#: Indigo>192.168.2.2<; wlan0>192.168.2.40<; eth0><; hostname>['192.168.2.40']<; AddressFile>192.168.2.40<; PKTS(eth0>0,0<; wlan0>73,55<, dTime:4.2)
20190701-21:32:23 master          L:-1=           Requested Config:{u'wlan0': {u'on': u'on', u'useIP': u'use'}, u'eth0': {u'on': u'off', u'useIP': u'doNotUse'}}
20190701-22:06:22 master          L:-1= dosfsck has error (was fixed after boot): fsck.fat 4.1 (2017-01-24)/--/Checking we can access the last sector of the filesystem/--/0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt./--/ Automatically removing dirty bit./--/Boot sector contents:/--/System ID "mkfs.fat"/--/Media byte 0xf8 (hard disk)/--/       512 bytes per logical sector/--/       512 bytes per cluster/--/        32 reserved sectors


and it hangs here

ETH and WLAN parameters are as shown in attachment for both config and rPI edit
Attachments
Screenshot 2019-07-01 at 22.07.39.png
Screenshot 2019-07-01 at 22.07.39.png (69.44 KiB) Viewed 3871 times

Posted on
Mon Jul 01, 2019 4:01 pm
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

this:
""dosfsck has error (was fixed after boot): fsck.fat 4.1 (2017-01-24)/--/Checking we can access the last sector of the filesystem/--/0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt./--/ Automatically removing dirty bit./--/Boot sector contents:/--/System ID "mkfs.fat"/--/Media byte 0xf8 (hard disk)/--/ 512 bytes per logical sector/--/ 512 bytes per cluster/--/ 32 reserved sectors""

means your ssd has a problem. it was fixed after reboot, but .. ==> so if you have time: make a new SSD

and
ssh to api
cd pibeacon
sudo python master.py

post what's happening

Karl

Posted on
Mon Jul 01, 2019 4:19 pm
ostr offline
Posts: 7
Joined: Jul 27, 2015

Re: AMG8833 sensor i2c address

Thanks - just tried to format and create the SSD, still showing the error so will try a new SSD...

Code: Select all
pi@raspberrypi:~ $ cd pibeacon
pi@raspberrypi:~/pibeacon $ sudo python master.py
Killed
pi@raspberrypi:~/pibeacon $ 20190701-21:32:42 master          L:-1= writing new callbeacon.py file
20190701-21:32:44 master          L:-1= START.. indigoServer IP:>>192.168.2.2<<
20190701-21:32:45 master          L:-1= Master adhocWifi is:-1 ;  G.wifiType is:normal
20190701-21:32:45 master          L:-1= IP find:: IPs#: Indigo>192.168.2.2<; wlan0>192.168.2.40<; eth0><; hostname>['192.168.2.40']<; AddressFile>192.168.2.40<; PKTS(eth0>0,<; wlan0>206,<, dTime:99.9)
20190701-21:32:45 master          L:-1=           Requested Config:{u'wlan0': {u'on': u'on', u'useIP': u'use'}, u'eth0': {u'on': u'off', u'useIP': u'doNotUse'}}
20190701-21:32:46 master          L:-1= can ping indigo server at ip:>>192.168.2.2<<
20190701-21:32:46 installLibs     L:-1= ==== libraries install finished
20190701-21:32:47 receiveCommands L:-1= started, listening to port: 9999
20190701-21:32:48 master          L:-1= IP find:: IPs#: Indigo>192.168.2.2<; wlan0>192.168.2.40<; eth0><; hostname>['192.168.2.40']<; AddressFile>192.168.2.40<; PKTS(eth0>0,0<; wlan0>228,206<, dTime:3.2)
20190701-21:32:48 master          L:-1=           Requested Config:{u'wlan0': {u'on': u'on', u'useIP': u'use'}, u'eth0': {u'on': u'off', u'useIP': u'doNotUse'}}
20190701-21:32:48 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci0;  myBLEmac:B8:27:EB:B2:3E:A2; devId:0
20190701-21:32:48 beaconloop      L:-1= hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 2f 23 44 54 cf 6d 4a 0f ad f2 f4 91 1b a9 ff a6 00 09 00 00 C5 00
20190701-21:32:48 beaconloop      L:-1= hcitool -i hci0 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190701-21:32:48 beaconloop      L:-1= hcitool -i hci0 cmd 0x08 0x000a 01
20190701-21:32:48 beaconloop      L:-1= BLE start returned:
hci0:   Type: Primary  Bus: UART
   BD Address: B8:27:EB:B2:3E:A2  ACL MTU: 1021:8  SCO MTU: 64:1
   UP RUNNING
   RX bytes:115142 acl:0 sco:0 events:3523 errors:0
   TX bytes:5920 acl:0 sco:0 commands:150 errors:0


20190701-21:32:48 beaconloop      L:-1= starting loop
20190701-21:32:48 master          L: 1= starting loop


hangs at this point...

Posted on
Mon Jul 01, 2019 4:47 pm
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

this looks correct..

next step:

after 10 secs or more after sudo python master.py do :

show which python processes are running:
ps -ef | grep .py

show which messages are send to plugin .. let it run for 2 minutes
tail -F temp/messageSend

(with capital -F not -f)

Karl

Posted on
Mon Jul 01, 2019 5:04 pm
kw123 offline
User avatar
Posts: 8333
Joined: May 12, 2013
Location: Dallas, TX

Re: AMG8833 sensor i2c address

could we do a chat, instead of 30 min ping pong ..?

eg teamviewer ..?

Karl

Posted on
Tue Jul 02, 2019 2:24 am
ostr offline
Posts: 7
Joined: Jul 27, 2015

Re: AMG8833 sensor i2c address

Thanks - PM’d

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 6 guests