pibeacon selecting hci0 and not hci1

Posted on
Sat Jun 01, 2019 8:13 pm
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

you mean this?:

pi0:
Code: Select all
pi@broompi:~/pibeacon $ sudo python master.py20190601-19:10:01 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-19:10:01 master          L:-1= IP find:::: wifiIP >>10.0.1.124<<; eth0IP: >>10.0.124.1<<;   hostnameIP >>['10.0.124.1', '10.0.1.124']<<;   ipAddressRead >>10.0.1.124<<
20190601-19:10:01 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-19:10:01 installLibs     L:-1= ==== libraries install finished
20190601-19:10:02 receiveCommands L:-1= started, listening to port: 9999
20190601-19:10:12 master          L: 1= starting loop
20190601-19:10:13 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:E1:4E:57; devId:1
20190601-19:10:13 beaconloop      L:-1= hcitool -i hci1 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
20190601-19:10:13 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-19:10:13 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-19:10:13 beaconloop      L:-1= starting loop


pi1:
Code: Select all
pi@officepi:~/pibeacon $ sudo python master.py
Killed
pi@officepi:~/pibeacon $ 20190601-19:12:00 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-19:12:00 master          L:-1= IP find:::: wifiIP >>10.0.1.125<<; eth0IP: >>10.0.125.1<<;   hostnameIP >>['10.0.125.1', '10.0.1.125']<<;   ipAddressRead >>10.0.1.125<<
20190601-19:12:00 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-19:12:00 installLibs     L:-1= ==== libraries install finished
20190601-19:12:00 receiveCommands L:-1= started, listening to port: 9999
20190601-19:12:01 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:A2:03:A9; devId:1
20190601-19:12:01 beaconloop      L:-1= hcitool -i hci1 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
20190601-19:12:01 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-19:12:01 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-19:12:01 beaconloop      L:-1= starting loop


pi2:
Code: Select all
pi@lroomPi:~ $ cd pibeacon
pi@lroomPi:~/pibeacon $ sudo python master.py
Killed
pi@lroomPi:~/pibeacon $ 20190601-19:13:03 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-19:13:03 master          L:-1= IP find:::: wifiIP >>10.0.1.126<<; eth0IP: >><<;   hostnameIP >>['10.0.1.126']<<;   ipAddressRead >>10.0.1.126<<
20190601-19:13:03 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-19:13:03 installLibs     L:-1= ==== libraries install finished
20190601-19:13:03 receiveCommands L:-1= started, listening to port: 9999
20190601-19:13:04 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:55:B2:22; devId:1
20190601-19:13:04 beaconloop      L:-1= hcitool -i hci1 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 02 C5 00
20190601-19:13:04 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-19:13:04 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-19:13:05 beaconloop      L:-1= starting loop

Posted on
Sat Jun 01, 2019 8:14 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

Yes thx



Sent from my iPhone using Tapatalk

Posted on
Sat Jun 01, 2019 8:40 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

And could you also post
ssh pi...
cd pibeacon

tail -F temp/messageSend
For all 3 rpi

Need to see the mac number send by the rpi

If the mac numbers are correctly send the plugin has the problem if not it’s the program on the rpi.


Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 12:55 am
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

Interesting. That file doesn't exist on two of the three pi's. Output listed below.

pi0: seeing this error in the logs for this host (10.0.1.124):
23:52:51 TCPIP socket data receiving from ('10.0.1.125', 46888) not in accepted ip number list
23:52:51 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:52:51
23:52:51 pi TCPIP socket -IP name type first last #MSGs #bytes bytes/MSG maxBytes bytes/min MSGs/min
23:52:51 -10.0.1.125 pi_IN_0 ok 2019-06-01 11:00:15 2019-06-01 13:05:02 97 68484 706 947 34.2 0.05
23:52:51 -10.0.1.125 pi_IN_1 ok 2019-06-01 10:00:13 2019-06-01 13:05:18 63 42680 677 947 21.3 0.03
23:52:51 -10.0.1.125 pi_IN_Alive ok 2019-05-31 21:01:59 2019-06-01 12:51:27 18 5720 317 346 2.9 0.01
23:52:51 -10.0.1.125 unknown errIP 2019-06-01 13:06:18 2019-06-01 23:52:51 5749 0 0 0 0.0 2.87
23:53:04 TCPIP socket data receiving from ('10.0.1.124', 38086) not in accepted ip number list


no messageSenf file for p0, though rejects file updated within the last minute.
Code: Select all
pi@broompi:~/pibeacon/temp $ ls -l
total 28
-rw-rw-rw- 1 pi   pi     14 Jun  1 23:53 alive.beaconloop
-rw-rw-rw- 1 pi   pi   3983 Jun  1 23:40 beacon_parameters
-rw-r--r-- 1 root root    2 Jun  1 23:52 networkMODE
-rw-rw-rw- 1 pi   pi   1990 Jun  1 23:40 parameters
-rw-rw-rw- 1 pi   pi   3026 Jun  1 23:40 patterns
-rw-rw-rw- 1 pi   pi    630 Jun  1 23:52 rejects
-rw-r--r-- 1 root root    2 Jun  1 23:54 sending
-rw-rw-rw- 1 pi   pi      0 Jun  1 23:40 touchFile
pi@broompi:~/pibeacon/temp $ date
Sat Jun  1 23:54:07 PDT 2019
pi@broompi:~/pibeacon/temp $


pi1: No messageSend file, though the rejects file was updated within the last minute
Code: Select all
pi@officepi:~/pibeacon $ ls -l /home/pi/pibeacon/temp
total 32
-rw-rw-rw- 1 pi   pi     14 Jun  1 23:46 alive.beaconloop
-rw-rw-rw- 1 pi   pi   3983 Jun  1 19:13 beacon_parameters
-rw-r--r-- 1 pi   pi      2 Jun  1 23:36 networkMODE
-rw-rw-rw- 1 pi   pi   1990 Jun  1 19:13 parameters
-rw-rw-rw- 1 pi   pi   3026 Jun  1 19:13 patterns
-rw-rw-rw- 1 pi   pi   5610 Jun  1 23:47 rejects
-rw-r--r-- 1 root root    2 Jun  1 23:47 sending
-rw-rw-rw- 1 pi   pi      0 Jun  1 19:13 touchFile
pi@officepi:~/pibeacon $ date
Sat Jun  1 23:47:51 PDT 2019
pi@officepi:~/pibeacon $



pi2:
Code: Select all
pi@lroomPi:~/pibeacon $ tail -F temp/messageSend
beaconloop:  {"msgs":[["00:EA:24:46:CA:97",1,"08885dd0111b11e491910800200c9a66-9286-51863",-82.2,-49.0,16,"",30],["00:EA:24:46:CA:94",1,"08885dd0111b11e491910800200c9a66-9286-51860",-81.4,-60.0,13,"",30]],"reason":1,"secsCol":60,"mac":"B8:27:EB:55:B2:22","program":"beaconloop","ts":{"tz":"PDT","time":1559457802.17},"pi":"1","ipAddress":"10.0.1.126"}
tail: temp/messageSend: file truncated
beaconloop:  {"msgs":[["00:EA:24:46:CA:97",1,"x-x-x",-74.2,-49.0,11,"",30],["00:EA:24:46:CA:94",1,"x-x-x",-82.9,-60.0,11,"",30]],"reason":1,"secsCol":60,"mac":"B8:27:EB:55:B2:22","program":"beaconloop","ts":{"tz":"PDT","time":1559457862.4},"pi":"1","ipAddress":"10.0.1.126"}
tail: temp/messageSend: file truncated
beaconloop:  {"msgs":[["00:EA:24:46:CA:97",1,"x-x-x",-76.5,-49.0,13,"",30],["00:EA:24:46:CA:94",1,"x-x-x",-82.9,-60.0,11,"",30]],"reason":1,"secsCol":60,"mac":"B8:27:EB:55:B2:22","program":"beaconloop","ts":{"tz":"PDT","time":1559457922.55},"pi":"1","ipAddress":"10.0.1.126"}

Posted on
Sun Jun 02, 2019 1:23 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

I need to go through the logs. Will
Take me some time

But the outside value ip ... in the plugin log:
The ip number is not defined in initial setup of rpi
Hence it rejects it.


No
messageSend
File indicates that no messages are being send at all
==> Check out the /etc/log/pibeacon.log file
On the rpi. ( I believe it is /etc... on the phone can not check ).


Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 1:38 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

And I remember....
If the plugin does not accept the message no message send file is created


Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 3:49 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

steps I need to do:

1. add option to force using WIFI (wlan0/1) and ignore eth0/1 for pibeacon communication to indigo plugin
that should fix some things.
Currently only options are
a) random choice which ip number (wlan/eth) is used (if wan and eth are active)
b) force switch off wlan0/1 when eth0/1 is present

Will move that choice to RPI device edit from plugin-config so that you can set each different for each RPi.

2. I still need to understand the logic why it would have 3 times the same Mac number - which is not in hci config
(btw: it uses the BLE -MAC number NOT the ethernet MAC number to id RPI 0-9 )

3.will add some more logic to better diagnose when switching ip / Mac numbers

.. but that needs to wait until I am back.

Karl

Posted on
Sun Jun 02, 2019 10:46 am
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

Thanks again, Karl. Also, I've currently set the pi's to "let piBeacon decide" regarding the use of the usb or internal BLE. Let me know if I should change that now, or after we get things up and running. Don't want to add to complexity by making unrequested changes on you now. lol

So, I did purchase the USB dongle that you recommended for all of them, and noticed that hci0 is identical for all three pi's (which is where the post started, before I sat down and started giving you hard data..doh). I'm not familiar enough with BLE to know why those ID's would be the same, or if I can change them like a network card.

pi0:
Code: Select all
pi@broompi:/var/log $ hcitool dev
Devices:
   hci1   B8:27:EB:E1:4E:57
   hci0   00:1A:7D:DA:71:13
pi@broompi:/var/log $


pi1:
Code: Select all
pi@officepi:~ $ hcitool dev
Devices:
   hci1   B8:27:EB:A2:03:A9
   hci0   00:1A:7D:DA:71:13
pi@officepi:~ $


pi2:
Code: Select all
pi@lroomPi:~ $ hcitool dev
Devices:
   hci1   B8:27:EB:55:B2:22
   hci0   00:1A:7D:DA:71:13
pi@lroomPi:~ $


some interesting entries in those logs, though. The /var/log/piBeaacon.log entries look pretty clean, but the piBeacon.log files do show some errors. All of the clients do appear to identify the unique BLE MAC from hci1 in the logs, however.

pi0:
Code: Select all
pi@broompi:/var/log $ more /var/log/piBeacon.log
20190601-23:40:20 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-23:40:20 master          L:-1= IP find:::: wifiIP >>10.0.1.124<<; eth0IP: >>10.0.124.1<<;   hostnameIP >>['10.0.124.1', '10.0.1.124']<<;   ipAddressRead >>10.0.1.124<<
20190601-23:40:21 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-23:40:22 installLibs     L:-1=  installLibs starting
20190601-23:40:22 installLibs     L:-1=  installLibs no opsys upgrade requested
20190601-23:40:22 installLibs     L:-1= ==== libraries seem to be setup, no need for action
20190601-23:40:22 installLibs     L:-1= ==== libraries install finished
20190601-23:40:22 receiveCommands L:-1= proceding with normal on no ad-hoc network
20190601-23:40:22 receiveCommands L:-1= started, listening to port: 9999
20190601-23:40:22 beaconloop      L: 1= trying to kill ps -ef | grep 'beaconloop.py' | grep -v grep
20190601-23:40:22 beaconloop      L:-1= (re)starting bluetooth
20190601-23:40:23 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:E1:4E:57; devId:1
20190601-23:40:23 beaconloop      L:-1= hcitool -i hci1 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
20190601-23:40:23 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-23:40:23 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-23:40:23 beaconloop      L:-1= BLE start returned :  ('hci1:\tType: Primary  Bus: UART\n\tBD Address: B8:27:EB:E1:4E:57  ACL MTU: 1021:8  SCO MTU: 64:1\n\tUP RUNNING \n\tRX bytes:1553 acl:0 sco:0 events:101 errors:0\n\tTX bytes:5061 acl:0 sco:0 commands:101 errors:0\
n\nhci0:\tType: Primary  Bus: USB\n\tBD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8\n\tUP RUNNING \n\tRX bytes:1866 acl:0 sco:0 events:114 errors:0\n\tTX bytes:4480 acl:0 sco:0 commands:114 errors:0\n\n', '')
20190601-23:40:23 beaconloop      L:-1= my BLE mac# is : B8:27:EB:E1:4E:57
20190601-23:40:23 beaconloop      L:-1= ble thread started
20190601-23:40:23 beaconloop      L:-1= starting loop
20190601-23:40:28 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-23:40:31 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-23:40:36 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'

pi@broompi:/var/log $ cat /var/log/piBeaacon.log
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
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
    337408 bytes per FAT (= 659 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 691200 (sector 1350)
     84261 data clusters (43141632 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
     85611 sectors total
Checking file /
Checking file /boot
Checking file /overlays (OVERLAYS)
Checking file /bcm2708-rpi-0-w.dtb (BCM270~1.DTB)
Checking file /COPYING.linux (COPYIN~1.LIN)
Checking file /LICENCE.broadcom (LICENC~1.BRO)
Checking file /issue.txt (ISSUE.TXT)
Checking file /bcm2708-rpi-b-plus.dtb (BCM270~2.DTB)
Checking file /bcm2708-rpi-b.dtb (BCM270~3.DTB)
Checking file /bcm2708-rpi-cm.dtb (BCM270~4.DTB)
Checking file /bcm2709-rpi-2-b.dtb (BCM270~5.DTB)
Checking file /bcm2710-rpi-3-b-plus.dtb (BCM271~1.DTB)
Checking file /bcm2710-rpi-3-b.dtb (BCM271~2.DTB)
Checking file /bcm2710-rpi-cm3.dtb (BCM271~3.DTB)
Checking file /bootcode.bin (BOOTCODE.BIN)
Checking file /cmdline.txt (CMDLINE.TXT)
Checking file /config.txt (CONFIG.TXT)
Checking file /fixup.dat (FIXUP.DAT)
Checking file /fixup_cd.dat (FIXUP_CD.DAT)
Checking file /fixup_db.dat (FIXUP_DB.DAT)
Checking file /fixup_x.dat (FIXUP_X.DAT)
Checking file /kernel.img (KERNEL.IMG)
Checking file /kernel7.img (KERNEL7.IMG)
Checking file /start.elf (START.ELF)
Checking file /start_cd.elf (START_CD.ELF)
Checking file /start_db.elf (START_DB.ELF)
Checking file /start_x.elf (START_X.ELF)
Checking file /LICENSE.oracle (LICENS~1.ORA)
Checking file /overlays/.
Checking file /overlays/..
Checking file /overlays/adau7002-simple.dtbo (ADAU70~1.DTB)
Checking file /overlays/README
Checking file /overlays/adau1977-adc.dtbo (ADAU19~1.DTB)
Checking file /overlays/akkordion-iqdacplus.dtbo (AKKORD~1.DTB)
Checking file /overlays/ads1015.dtbo (ADS101~1.DTB)
Checking file /overlays/ads1115.dtbo (ADS111~1.DTB)
Checking file /overlays/ads7846.dtbo (ADS784~1.DTB)
Checking file /overlays/bmp085_i2c-sensor.dtbo (BMP085~1.DTB)
Checking file /overlays/audremap.dtbo (AUDREM~1.DTB)
Checking file /overlays/allo-boss-dac-pcm512x-audio.dtbo (ALLO-B~1.DTB)
Checking file /overlays/allo-digione.dtbo (ALLO-D~1.DTB)
Checking file /overlays/allo-piano-dac-pcm512x-audio.dtbo (ALLO-P~1.DTB)
Checking file /overlays/allo-piano-dac-plus-pcm512x-audio.dtbo (ALLO-P~2.DTB)
Checking file /overlays/applepi-dac.dtbo (APPLEP~1.DTB)
Checking file /overlays/at86rf233.dtbo (AT86RF~1.DTB)
Checking file /overlays/audioinjector-addons.dtbo (AUDIOI~1.DTB)
Checking file /overlays/audioinjector-wm8731-audio.dtbo (AUDIOI~2.DTB)
Checking file /overlays/dwc-otg.dtbo (DWC-OT~1.DTB)
Checking file /overlays/dpi18.dtbo (DPI18~1.DTB)
Checking file /overlays/dht11.dtbo (DHT11~1.DTB)
Checking file /overlays/dionaudio-loco.dtbo (DIONAU~2.DTB)
Checking file /overlays/dpi24.dtbo (DPI24~1.DTB)
Checking file /overlays/enc28j60-spi2.dtbo (ENC28J~1.DTB)
Checking file /overlays/dwc2.dtbo (DWC2~1.DTB)
Checking file /overlays/googlevoicehat-soundcard.dtbo (GOOGLE~1.DTB)
Checking file /overlays/enc28j60.dtbo (ENC28J~2.DTB)
Checking file /overlays/exc3000.dtbo (EXC300~1.DTB)
Checking file /overlays/fe-pi-audio.dtbo (FE-PI-~1.DTB)
Checking file /overlays/goodix.dtbo (GOODIX~1.DTB)
Checking file /overlays/iqaudio-digi-wm8804-audio.dtbo (IQAUDI~3.DTB)
Checking file /overlays/gpio-ir.dtbo (GPIO-I~1.DTB)
Checking file /overlays/gpio-key.dtbo (GPIO-K~1.DTB)
Checking file /overlays/gpio-poweroff.dtbo (GPIO-P~1.DTB)
Checking file /overlays/gpio-shutdown.dtbo (GPIO-S~1.DTB)
Checking file /overlays/hifiberry-amp.dtbo (HIFIBE~1.DTB)
Checking file /overlays/hifiberry-dac.dtbo (HIFIBE~2.DTB)
Checking file /overlays/hifiberry-dacplus.dtbo (HIFIBE~3.DTB)
Checking file /overlays/hifiberry-digi-pro.dtbo (HIFIBE~4.DTB)
Checking file /overlays/hifiberry-digi.dtbo (HIFIBE~5.DTB)
Checking file /overlays/hy28a.dtbo (HY28A~1.DTB)
Checking file /overlays/hy28b.dtbo (HY28B~1.DTB)
Checking file /overlays/i2c-bcm2708.dtbo (I2C-BC~1.DTB)
Checking file /overlays/i2c-gpio.dtbo (I2C-GP~1.DTB)
Checking file /overlays/i2c-mux.dtbo (I2C-MU~1.DTB)
Checking file /overlays/i2c-pwm-pca9685a.dtbo (I2C-PW~1.DTB)
Checking file /overlays/i2c-rtc-gpio.dtbo (I2C-RT~1.DTB)
Checking file /overlays/i2c-rtc.dtbo (I2C-RT~2.DTB)
Checking file /overlays/i2c-sensor.dtbo (I2C-SE~1.DTB)
Checking file /overlays/i2c0-bcm2708.dtbo (I2C0-B~1.DTB)
Checking file /overlays/i2c1-bcm2708.dtbo (I2C1-B~1.DTB)
Checking file /overlays/i2s-gpio28-31.dtbo (I2S-GP~1.DTB)
Checking file /overlays/iqaudio-dac.dtbo (IQAUDI~1.DTB)
Checking file /overlays/iqaudio-dacplus.dtbo (IQAUDI~2.DTB)
Checking file /overlays/rra-digidac1-wm8741-audio.dtbo (RRA-DI~1.DTB)
Checking file /overlays/justboom-dac.dtbo (JUSTBO~1.DTB)
Checking file /overlays/justboom-digi.dtbo (JUSTBO~2.DTB)
Checking file /overlays/lirc-rpi.dtbo (LIRC-R~1.DTB)
Checking file /overlays/mbed-dac.dtbo (MBED-D~1.DTB)
Checking file /overlays/mcp23017.dtbo (MCP230~1.DTB)
Checking file /overlays/mcp23s17.dtbo (MCP23S~1.DTB)
Checking file /overlays/mcp2515-can0.dtbo (MCP251~1.DTB)
Checking file /overlays/mcp2515-can1.dtbo (MCP251~2.DTB)
Checking file /overlays/mcp3008.dtbo (MCP300~1.DTB)
Checking file /overlays/mcp3202.dtbo (MCP320~1.DTB)
Checking file /overlays/media-center.dtbo (MEDIA-~1.DTB)
Checking file /overlays/midi-uart0.dtbo (MIDI-U~1.DTB)
Checking file /overlays/midi-uart1.dtbo (MIDI-U~2.DTB)
Checking file /overlays/mmc.dtbo (MMC~1.DTB)
Checking file /overlays/mpu6050.dtbo (MPU605~1.DTB)
Checking file /overlays/mz61581.dtbo (MZ6158~1.DTB)
Checking file /overlays/papirus.dtbo (PAPIRU~1.DTB)
Checking file /overlays/pi3-act-led.dtbo (PI3-AC~1.DTB)
Checking file /overlays/pi3-disable-bt.dtbo (PI3-DI~1.DTB)
Checking file /overlays/pi3-disable-wifi.dtbo (PI3-DI~2.DTB)
Checking file /overlays/pi3-miniuart-bt.dtbo (PI3-MI~1.DTB)
Checking file /overlays/piscreen.dtbo (PISCRE~1.DTB)
Checking file /overlays/piscreen2r.dtbo (PISCRE~2.DTB)
Checking file /overlays/pisound.dtbo (PISOUN~1.DTB)
Checking file /overlays/pitft22.dtbo (PITFT2~1.DTB)
Checking file /overlays/pitft28-capacitive.dtbo (PITFT2~2.DTB)
Checking file /overlays/pitft28-resistive.dtbo (PITFT2~3.DTB)
Checking file /overlays/pitft35-resistive.dtbo (PITFT3~1.DTB)
Checking file /overlays/pps-gpio.dtbo (PPS-GP~1.DTB)
Checking file /overlays/pwm-2chan.dtbo (PWM-2C~1.DTB)
Checking file /overlays/pwm.dtbo (PWM~1.DTB)
Checking file /overlays/qca7000.dtbo (QCA700~1.DTB)
Checking file /overlays/dionaudio-loco-v2.dtbo (DIONAU~1.DTB)
Checking file /overlays/rotary-encoder.dtbo (ROTARY~1.DTB)
Checking file /overlays/rpi-backlight.dtbo (RPI-BA~1.DTB)
Checking file /overlays/rpi-cirrus-wm5102.dtbo (RPI-CI~1.DTB)
Checking file /overlays/rpi-dac.dtbo (RPI-DA~1.DTB)
Checking file /overlays/rpi-display.dtbo (RPI-DI~1.DTB)
Checking file /overlays/rpi-ft5406.dtbo (RPI-FT~1.DTB)
Checking file /overlays/rpi-proto.dtbo (RPI-PR~1.DTB)
Checking file /overlays/rpi-sense.dtbo (RPI-SE~1.DTB)
Checking file /overlays/rpi-tv.dtbo (RPI-TV~1.DTB)
Checking file /overlays/upstream-aux-interrupt.dtbo (UPSTRE~1.DTB)
Checking file /overlays/sc16is750-i2c.dtbo (SC16IS~1.DTB)
Checking file /overlays/sc16is752-spi1.dtbo (SC16IS~2.DTB)
Checking file /overlays/sdhost.dtbo (SDHOST~1.DTB)
Checking file /overlays/sdio-1bit.dtbo (SDIO-1~1.DTB)
Checking file /overlays/sdio.dtbo (SDIO~1.DTB)
Checking file /overlays/sdtweak.dtbo (SDTWEA~1.DTB)
Checking file /overlays/smi-dev.dtbo (SMI-DE~1.DTB)
Checking file /overlays/smi-nand.dtbo (SMI-NA~1.DTB)
Checking file /overlays/smi.dtbo (SMI~1.DTB)
Checking file /overlays/spi-gpio35-39.dtbo (SPI-GP~1.DTB)
Checking file /overlays/spi-rtc.dtbo (SPI-RT~1.DTB)
Checking file /overlays/spi0-cs.dtbo (SPI0-C~1.DTB)
Checking file /overlays/spi0-hw-cs.dtbo (SPI0-H~1.DTB)
Checking file /overlays/spi1-1cs.dtbo (SPI1-1~1.DTB)
Checking file /overlays/spi1-2cs.dtbo (SPI1-2~1.DTB)
Checking file /overlays/spi1-3cs.dtbo (SPI1-3~1.DTB)
Checking file /overlays/spi2-1cs.dtbo (SPI2-1~1.DTB)
Checking file /overlays/spi2-2cs.dtbo (SPI2-2~1.DTB)
Checking file /overlays/spi2-3cs.dtbo (SPI2-3~1.DTB)
Checking file /overlays/tinylcd35.dtbo (TINYLC~1.DTB)
Checking file /overlays/uart0.dtbo (UART0~1.DTB)
Checking file /overlays/uart1.dtbo (UART1~1.DTB)
Checking file /overlays/vc4-fkms-v3d.dtbo (VC4-FK~1.DTB)
Checking file /overlays/vc4-kms-v3d.dtbo (VC4-KM~1.DTB)
Checking file /overlays/vga666.dtbo (VGA666~1.DTB)
Checking file /overlays/w1-gpio-pullup.dtbo (W1-GPI~1.DTB)
Checking file /overlays/w1-gpio.dtbo (W1-GPI~2.DTB)
Checking file /overlays/wittypi.dtbo (WITTYP~1.DTB)
Checking file /overlays/gpio-ir-tx.dtbo (GPIO-I~2.DTB)
Checking file /overlays/pibell.dtbo (PIBELL~1.DTB)
Checking file /overlays/pwm-ir-tx.dtbo (PWM-IR~1.DTB)
Checking file /overlays/sc16is752-i2c.dtbo (SC16IS~3.DTB)
Checking file /overlays/superaudioboard.dtbo (SUPERA~1.DTB)
Checking file /overlays/sx150x.dtbo (SX150X~1.DTB)
Checking file /overlays/upstream.dtbo (UPSTRE~2.DTB)
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/mmcblk0p1: 159 files, 44039/84261 clusters



pi1:
Code: Select all
more /var/log/piBeacon.log
20190601-19:13:07 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-19:13:07 master          L:-1= IP find:::: wifiIP >>10.0.1.125<<; eth0IP: >>10.0.125.1<<;   hostnameIP >>['10.0.125.1', '10.0.1.125']<<;   ipAddressRead >>10.0.1.125<<
20190601-19:13:08 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-19:13:09 installLibs     L:-1=  installLibs starting
20190601-19:13:09 installLibs     L:-1=  installLibs no opsys upgrade requested
20190601-19:13:09 installLibs     L:-1= ==== libraries seem to be setup, no need for action
20190601-19:13:09 installLibs     L:-1= ==== libraries install finished
20190601-19:13:09 receiveCommands L:-1= proceding with normal on no ad-hoc network
20190601-19:13:09 receiveCommands L:-1= started, listening to port: 9999
20190601-19:13:09 beaconloop      L: 1= trying to kill ps -ef | grep 'beaconloop.py' | grep -v grep
20190601-19:13:09 beaconloop      L:-1= (re)starting bluetooth
20190601-19:13:10 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:A2:03:A9; devId:1
20190601-19:13:10 beaconloop      L:-1= hcitool -i hci1 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
20190601-19:13:10 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-19:13:10 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-19:13:10 beaconloop      L:-1= BLE start returned :  ('hci1:\tType: Primary  Bus: UART\n\tBD Address: B8:27:EB:A2:03:A9  ACL MTU: 1021:8  SCO MTU: 64:1\n\tUP RUNNING \n\tRX bytes:1553 acl:0 sco:0 events:101 errors:0\n\tTX bytes:5061 acl:0 sco:0 commands:101 errors:0\
n\nhci0:\tType: Primary  Bus: USB\n\tBD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8\n\tUP RUNNING \n\tRX bytes:1866 acl:0 sco:0 events:114 errors:0\n\tTX bytes:4480 acl:0 sco:0 commands:114 errors:0\n\n', '')
20190601-19:13:10 beaconloop      L:-1= my BLE mac# is : B8:27:EB:A2:03:A9
20190601-19:13:10 beaconloop      L:-1= ble thread started
20190601-19:13:10 beaconloop      L:-1= starting loop
20190601-19:13:12 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-19:13:15 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-19:13:18 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-19:13:24 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'
20190601-19:13:28 master          L:-1= sendURL in Line '1211' has error='[Errno 104] Connection reset by peer'

pi@officepi:~ $ cat /var/log/piBeaacon.log
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
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
    337408 bytes per FAT (= 659 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 691200 (sector 1350)
     84261 data clusters (43141632 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
     85611 sectors total
Checking file /
Checking file /boot
Checking file /overlays (OVERLAYS)
Checking file /bcm2708-rpi-0-w.dtb (BCM270~1.DTB)
Checking file /COPYING.linux (COPYIN~1.LIN)
Checking file /LICENCE.broadcom (LICENC~1.BRO)
Checking file /issue.txt (ISSUE.TXT)
Checking file /.fseventsd (FSEVEN~1)
Checking file /bcm2708-rpi-b-plus.dtb (BCM270~2.DTB)
Checking file /bcm2708-rpi-b.dtb (BCM270~3.DTB)
Checking file /bcm2708-rpi-cm.dtb (BCM270~4.DTB)
Checking file /bcm2709-rpi-2-b.dtb (BCM270~5.DTB)
Checking file /bcm2710-rpi-3-b-plus.dtb (BCM271~1.DTB)
Checking file /bcm2710-rpi-3-b.dtb (BCM271~2.DTB)
Checking file /bcm2710-rpi-cm3.dtb (BCM271~3.DTB)
Checking file /bootcode.bin (BOOTCODE.BIN)
Checking file /cmdline.txt (CMDLINE.TXT)
Checking file /config.txt (CONFIG.TXT)
Checking file /fixup.dat (FIXUP.DAT)
Checking file /fixup_cd.dat (FIXUP_CD.DAT)
Checking file /fixup_db.dat (FIXUP_DB.DAT)
Checking file /fixup_x.dat (FIXUP_X.DAT)
Checking file /kernel.img (KERNEL.IMG)
Checking file /kernel7.img (KERNEL7.IMG)
Checking file /start.elf (START.ELF)
Checking file /start_cd.elf (START_CD.ELF)
Checking file /start_db.elf (START_DB.ELF)
Checking file /start_x.elf (START_X.ELF)
Checking file /LICENSE.oracle (LICENS~1.ORA)
Checking file /overlays/.
Checking file /overlays/..
Checking file /overlays/adau7002-simple.dtbo (ADAU70~1.DTB)
Checking file /overlays/README
Checking file /overlays/adau1977-adc.dtbo (ADAU19~1.DTB)
Checking file /overlays/akkordion-iqdacplus.dtbo (AKKORD~1.DTB)
Checking file /overlays/ads1015.dtbo (ADS101~1.DTB)
Checking file /overlays/ads1115.dtbo (ADS111~1.DTB)
Checking file /overlays/ads7846.dtbo (ADS784~1.DTB)
Checking file /overlays/bmp085_i2c-sensor.dtbo (BMP085~1.DTB)
Checking file /overlays/audremap.dtbo (AUDREM~1.DTB)
Checking file /overlays/allo-boss-dac-pcm512x-audio.dtbo (ALLO-B~1.DTB)
Checking file /overlays/allo-digione.dtbo (ALLO-D~1.DTB)
Checking file /overlays/allo-piano-dac-pcm512x-audio.dtbo (ALLO-P~1.DTB)
Checking file /overlays/allo-piano-dac-plus-pcm512x-audio.dtbo (ALLO-P~2.DTB)
Checking file /overlays/applepi-dac.dtbo (APPLEP~1.DTB)
Checking file /overlays/at86rf233.dtbo (AT86RF~1.DTB)
Checking file /overlays/audioinjector-addons.dtbo (AUDIOI~1.DTB)
Checking file /overlays/audioinjector-wm8731-audio.dtbo (AUDIOI~2.DTB)
Checking file /overlays/dwc-otg.dtbo (DWC-OT~1.DTB)
Checking file /overlays/dpi18.dtbo (DPI18~1.DTB)
Checking file /overlays/dht11.dtbo (DHT11~1.DTB)
Checking file /overlays/dionaudio-loco.dtbo (DIONAU~2.DTB)
Checking file /overlays/dpi24.dtbo (DPI24~1.DTB)
Checking file /overlays/enc28j60-spi2.dtbo (ENC28J~1.DTB)
Checking file /overlays/dwc2.dtbo (DWC2~1.DTB)
Checking file /overlays/googlevoicehat-soundcard.dtbo (GOOGLE~1.DTB)
Checking file /overlays/enc28j60.dtbo (ENC28J~2.DTB)
Checking file /overlays/exc3000.dtbo (EXC300~1.DTB)
Checking file /overlays/fe-pi-audio.dtbo (FE-PI-~1.DTB)
Checking file /overlays/goodix.dtbo (GOODIX~1.DTB)
Checking file /overlays/iqaudio-digi-wm8804-audio.dtbo (IQAUDI~3.DTB)
Checking file /overlays/gpio-ir.dtbo (GPIO-I~1.DTB)
Checking file /overlays/gpio-key.dtbo (GPIO-K~1.DTB)
Checking file /overlays/gpio-poweroff.dtbo (GPIO-P~1.DTB)
Checking file /overlays/gpio-shutdown.dtbo (GPIO-S~1.DTB)
Checking file /overlays/hifiberry-amp.dtbo (HIFIBE~1.DTB)
Checking file /overlays/hifiberry-dac.dtbo (HIFIBE~2.DTB)
Checking file /overlays/hifiberry-dacplus.dtbo (HIFIBE~3.DTB)
Checking file /overlays/hifiberry-digi-pro.dtbo (HIFIBE~4.DTB)
Checking file /overlays/hifiberry-digi.dtbo (HIFIBE~5.DTB)
Checking file /overlays/hy28a.dtbo (HY28A~1.DTB)
Checking file /overlays/hy28b.dtbo (HY28B~1.DTB)
Checking file /overlays/i2c-bcm2708.dtbo (I2C-BC~1.DTB)
Checking file /overlays/i2c-gpio.dtbo (I2C-GP~1.DTB)
Checking file /overlays/i2c-mux.dtbo (I2C-MU~1.DTB)
Checking file /overlays/i2c-pwm-pca9685a.dtbo (I2C-PW~1.DTB)
Checking file /overlays/i2c-rtc-gpio.dtbo (I2C-RT~1.DTB)
Checking file /overlays/i2c-rtc.dtbo (I2C-RT~2.DTB)
Checking file /overlays/i2c-sensor.dtbo (I2C-SE~1.DTB)
Checking file /overlays/i2c0-bcm2708.dtbo (I2C0-B~1.DTB)
Checking file /overlays/i2c1-bcm2708.dtbo (I2C1-B~1.DTB)
Checking file /overlays/i2s-gpio28-31.dtbo (I2S-GP~1.DTB)
Checking file /overlays/iqaudio-dac.dtbo (IQAUDI~1.DTB)
Checking file /overlays/iqaudio-dacplus.dtbo (IQAUDI~2.DTB)
Checking file /overlays/rra-digidac1-wm8741-audio.dtbo (RRA-DI~1.DTB)
Checking file /overlays/justboom-dac.dtbo (JUSTBO~1.DTB)
Checking file /overlays/justboom-digi.dtbo (JUSTBO~2.DTB)
Checking file /overlays/lirc-rpi.dtbo (LIRC-R~1.DTB)
Checking file /overlays/mbed-dac.dtbo (MBED-D~1.DTB)
Checking file /overlays/mcp23017.dtbo (MCP230~1.DTB)
Checking file /overlays/mcp23s17.dtbo (MCP23S~1.DTB)
Checking file /overlays/mcp2515-can0.dtbo (MCP251~1.DTB)
Checking file /overlays/mcp2515-can1.dtbo (MCP251~2.DTB)
Checking file /overlays/mcp3008.dtbo (MCP300~1.DTB)
Checking file /overlays/mcp3202.dtbo (MCP320~1.DTB)
Checking file /overlays/media-center.dtbo (MEDIA-~1.DTB)
Checking file /overlays/midi-uart0.dtbo (MIDI-U~1.DTB)
Checking file /overlays/midi-uart1.dtbo (MIDI-U~2.DTB)
Checking file /overlays/mmc.dtbo (MMC~1.DTB)
Checking file /overlays/mpu6050.dtbo (MPU605~1.DTB)
Checking file /overlays/mz61581.dtbo (MZ6158~1.DTB)
Checking file /overlays/papirus.dtbo (PAPIRU~1.DTB)
Checking file /overlays/pi3-act-led.dtbo (PI3-AC~1.DTB)
Checking file /overlays/pi3-disable-bt.dtbo (PI3-DI~1.DTB)
Checking file /overlays/pi3-disable-wifi.dtbo (PI3-DI~2.DTB)
Checking file /overlays/pi3-miniuart-bt.dtbo (PI3-MI~1.DTB)
Checking file /overlays/piscreen.dtbo (PISCRE~1.DTB)
Checking file /overlays/piscreen2r.dtbo (PISCRE~2.DTB)
Checking file /overlays/pisound.dtbo (PISOUN~1.DTB)
Checking file /overlays/pitft22.dtbo (PITFT2~1.DTB)
Checking file /overlays/pitft28-capacitive.dtbo (PITFT2~2.DTB)
Checking file /overlays/pitft28-resistive.dtbo (PITFT2~3.DTB)
Checking file /overlays/pitft35-resistive.dtbo (PITFT3~1.DTB)
Checking file /overlays/pps-gpio.dtbo (PPS-GP~1.DTB)
Checking file /overlays/pwm-2chan.dtbo (PWM-2C~1.DTB)
Checking file /overlays/pwm.dtbo (PWM~1.DTB)
Checking file /overlays/qca7000.dtbo (QCA700~1.DTB)
Checking file /overlays/dionaudio-loco-v2.dtbo (DIONAU~1.DTB)
Checking file /overlays/rotary-encoder.dtbo (ROTARY~1.DTB)
Checking file /overlays/rpi-backlight.dtbo (RPI-BA~1.DTB)
Checking file /overlays/rpi-cirrus-wm5102.dtbo (RPI-CI~1.DTB)
Checking file /overlays/rpi-dac.dtbo (RPI-DA~1.DTB)
Checking file /overlays/rpi-display.dtbo (RPI-DI~1.DTB)
Checking file /overlays/rpi-ft5406.dtbo (RPI-FT~1.DTB)
Checking file /overlays/rpi-proto.dtbo (RPI-PR~1.DTB)
Checking file /overlays/rpi-sense.dtbo (RPI-SE~1.DTB)
Checking file /overlays/rpi-tv.dtbo (RPI-TV~1.DTB)
Checking file /overlays/upstream-aux-interrupt.dtbo (UPSTRE~1.DTB)
Checking file /overlays/sc16is750-i2c.dtbo (SC16IS~1.DTB)
Checking file /overlays/sc16is752-spi1.dtbo (SC16IS~2.DTB)
Checking file /overlays/sdhost.dtbo (SDHOST~1.DTB)
Checking file /overlays/sdio-1bit.dtbo (SDIO-1~1.DTB)
Checking file /overlays/sdio.dtbo (SDIO~1.DTB)
Checking file /overlays/sdtweak.dtbo (SDTWEA~1.DTB)
Checking file /overlays/smi-dev.dtbo (SMI-DE~1.DTB)
Checking file /overlays/smi-nand.dtbo (SMI-NA~1.DTB)
Checking file /overlays/smi.dtbo (SMI~1.DTB)
Checking file /overlays/spi-gpio35-39.dtbo (SPI-GP~1.DTB)
Checking file /overlays/spi-rtc.dtbo (SPI-RT~1.DTB)
Checking file /overlays/spi0-cs.dtbo (SPI0-C~1.DTB)
Checking file /overlays/spi0-hw-cs.dtbo (SPI0-H~1.DTB)
Checking file /overlays/spi1-1cs.dtbo (SPI1-1~1.DTB)
Checking file /overlays/spi1-2cs.dtbo (SPI1-2~1.DTB)
Checking file /overlays/spi1-3cs.dtbo (SPI1-3~1.DTB)
Checking file /overlays/spi2-1cs.dtbo (SPI2-1~1.DTB)
Checking file /overlays/spi2-2cs.dtbo (SPI2-2~1.DTB)
Checking file /overlays/spi2-3cs.dtbo (SPI2-3~1.DTB)
Checking file /overlays/tinylcd35.dtbo (TINYLC~1.DTB)
Checking file /overlays/uart0.dtbo (UART0~1.DTB)
Checking file /overlays/uart1.dtbo (UART1~1.DTB)
Checking file /overlays/vc4-fkms-v3d.dtbo (VC4-FK~1.DTB)
Checking file /overlays/vc4-kms-v3d.dtbo (VC4-KM~1.DTB)
Checking file /overlays/vga666.dtbo (VGA666~1.DTB)
Checking file /overlays/w1-gpio-pullup.dtbo (W1-GPI~1.DTB)
Checking file /overlays/w1-gpio.dtbo (W1-GPI~2.DTB)
Checking file /overlays/wittypi.dtbo (WITTYP~1.DTB)
Checking file /overlays/gpio-ir-tx.dtbo (GPIO-I~2.DTB)
Checking file /overlays/pibell.dtbo (PIBELL~1.DTB)
Checking file /overlays/pwm-ir-tx.dtbo (PWM-IR~1.DTB)
Checking file /overlays/sc16is752-i2c.dtbo (SC16IS~3.DTB)
Checking file /overlays/superaudioboard.dtbo (SUPERA~1.DTB)
Checking file /overlays/sx150x.dtbo (SX150X~1.DTB)
Checking file /overlays/upstream.dtbo (UPSTRE~2.DTB)
Checking file /.fseventsd/.
Checking file /.fseventsd/..
Checking file /.fseventsd/fseventsd-uuid (FSEVEN~1)
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/mmcblk0p1: 161 files, 44041/84261 clusters


pi2:
Code: Select all
pi@lroomPi:~ $ cat /var/log/piBeacon.log
20190601-19:14:11 master          L:-1= Master adhocWifi is: -1 ;  G.wifiType is: normal
20190601-19:14:11 master          L:-1= IP find:::: wifiIP >>10.0.1.126<<; eth0IP: >><<;   hostnameIP >>['10.0.1.126']<<;   ipAddressRead >>10.0.1.126<<
20190601-19:14:12 master          L:-1= can ping indigo server at ip:>>10.0.1.78<<
20190601-19:14:12 installLibs     L:-1=  installLibs starting
20190601-19:14:12 installLibs     L:-1=  installLibs no opsys upgrade requested
20190601-19:14:12 installLibs     L:-1= ==== libraries seem to be setup, no need for action
20190601-19:14:12 installLibs     L:-1= ==== libraries install finished
20190601-19:14:13 receiveCommands L:-1= proceding with normal on no ad-hoc network
20190601-19:14:13 receiveCommands L:-1= started, listening to port: 9999
20190601-19:14:13 beaconloop      L: 1= trying to kill ps -ef | grep 'beaconloop.py' | grep -v grep
20190601-19:14:13 beaconloop      L:-1= (re)starting bluetooth
20190601-19:14:14 beaconloop      L:-1= Beacon Use HCINo -1;  useHCI:hci1;  myBLEmac:B8:27:EB:55:B2:22; devId:1
20190601-19:14:14 beaconloop      L:-1= hcitool -i hci1 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 02 C5 00
20190601-19:14:14 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x0006 00 10 00 20 03 00 00 00 00 00 00 00 00 07 00
20190601-19:14:14 beaconloop      L:-1= hcitool -i hci1 cmd 0x08 0x000a 01
20190601-19:14:14 beaconloop      L:-1= BLE start returned :  ('hci1:\tType: Primary  Bus: UART\n\tBD Address: B8:27:EB:55:B2:22  ACL MTU: 1021:8  SCO MTU: 64:1\n\tUP RUNNING \n\tRX bytes:1581 acl:0 sco:0 events:103 errors:0\n\tTX bytes:5069 acl:0 sco:0 commands:103 errors:0\n\nhci0:\tType: Primary  Bus: USB\n\tBD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8\n\tUP RUNNING \n\tRX bytes:1866 acl:0 sco:0 events:114 errors:0\n\tTX bytes:4480 acl:0 sco:0 commands:114 errors:0\n\n', '')
20190601-19:14:14 beaconloop      L:-1= my BLE mac# is : B8:27:EB:55:B2:22
20190601-19:14:14 beaconloop      L:-1= ble thread started
20190601-19:14:14 beaconloop      L:-1= starting loop
20190601-19:25:52 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-19:25:59 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-19:26:03 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-19:42:15 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-19:42:22 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-19:42:25 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-19:44:34 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-20:13:36 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-20:17:47 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-20:42:16 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-20:44:28 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-20:44:35 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-20:44:38 beaconloop      L:-1= sendURL in Line '1208' has error='[Errno 113] No route to host'
20190601-21:59:55 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-22:05:54 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("cd /home/pi/pibeacon; /usr/bin/python /home/pi/pibeacon/master.py & ")
20190601-22:08:52 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-22:32:21 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-22:45:36 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-22:45:44 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-22:45:52 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190601-23:05:55 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("sleep 10; cd /home/pi/pibeacon; python /home/pi/pibeacon/master.py &")
20190601-23:16:01 beaconloop      L:-1= sendURL in Line '1208' has error='timed out'
20190602-00:00:24 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("cd /home/pi/pibeacon; /usr/bin/python /home/pi/pibeacon/master.py & ")
20190602-01:00:16 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("sleep 10; cd /home/pi/pibeacon; python /home/pi/pibeacon/master.py &")
20190602-02:00:24 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("cd /home/pi/pibeacon; /usr/bin/python /home/pi/pibeacon/master.py & ")
20190602-03:00:32 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("sleep 10; cd /home/pi/pibeacon; python /home/pi/pibeacon/master.py &")
20190602-04:00:39 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("cd /home/pi/pibeacon; /usr/bin/python /home/pi/pibeacon/master.py & ")
20190602-05:00:47 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("sleep 10; cd /home/pi/pibeacon; python /home/pi/pibeacon/master.py &")
20190602-09:01:08 master          L:-1= writing new callbeacon.py file  with new line:
 os.system("cd /home/pi/pibeacon; /usr/bin/python /home/pi/pibeacon/master.py & ")

pi@lroomPi:~ $ cat /var/log/piBeaacon.log
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
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
    337408 bytes per FAT (= 659 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 691200 (sector 1350)
     84261 data clusters (43141632 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
     85611 sectors total
Checking file /
Checking file /boot
Checking file /overlays (OVERLAYS)
Checking file /bcm2708-rpi-0-w.dtb (BCM270~1.DTB)
Checking file /COPYING.linux (COPYIN~1.LIN)
Checking file /LICENCE.broadcom (LICENC~1.BRO)
Checking file /issue.txt (ISSUE.TXT)
Checking file /.fseventsd (FSEVEN~1)
Checking file /bcm2708-rpi-b-plus.dtb (BCM270~2.DTB)
Checking file /bcm2708-rpi-b.dtb (BCM270~3.DTB)
Checking file /bcm2708-rpi-cm.dtb (BCM270~4.DTB)
Checking file /bcm2709-rpi-2-b.dtb (BCM270~5.DTB)
Checking file /bcm2710-rpi-3-b-plus.dtb (BCM271~1.DTB)
Checking file /bcm2710-rpi-3-b.dtb (BCM271~2.DTB)
Checking file /bcm2710-rpi-cm3.dtb (BCM271~3.DTB)
Checking file /bootcode.bin (BOOTCODE.BIN)
Checking file /cmdline.txt (CMDLINE.TXT)
Checking file /config.txt (CONFIG.TXT)
Checking file /fixup.dat (FIXUP.DAT)
Checking file /fixup_cd.dat (FIXUP_CD.DAT)
Checking file /fixup_db.dat (FIXUP_DB.DAT)
Checking file /fixup_x.dat (FIXUP_X.DAT)
Checking file /kernel.img (KERNEL.IMG)
Checking file /kernel7.img (KERNEL7.IMG)
Checking file /start.elf (START.ELF)
Checking file /start_cd.elf (START_CD.ELF)
Checking file /start_db.elf (START_DB.ELF)
Checking file /start_x.elf (START_X.ELF)
Checking file /LICENSE.oracle (LICENS~1.ORA)
Checking file /overlays/.
Checking file /overlays/..
Checking file /overlays/adau7002-simple.dtbo (ADAU70~1.DTB)
Checking file /overlays/README
Checking file /overlays/adau1977-adc.dtbo (ADAU19~1.DTB)
Checking file /overlays/akkordion-iqdacplus.dtbo (AKKORD~1.DTB)
Checking file /overlays/ads1015.dtbo (ADS101~1.DTB)
Checking file /overlays/ads1115.dtbo (ADS111~1.DTB)
Checking file /overlays/ads7846.dtbo (ADS784~1.DTB)
Checking file /overlays/bmp085_i2c-sensor.dtbo (BMP085~1.DTB)
Checking file /overlays/audremap.dtbo (AUDREM~1.DTB)
Checking file /overlays/allo-boss-dac-pcm512x-audio.dtbo (ALLO-B~1.DTB)
Checking file /overlays/allo-digione.dtbo (ALLO-D~1.DTB)
Checking file /overlays/allo-piano-dac-pcm512x-audio.dtbo (ALLO-P~1.DTB)
Checking file /overlays/allo-piano-dac-plus-pcm512x-audio.dtbo (ALLO-P~2.DTB)
Checking file /overlays/applepi-dac.dtbo (APPLEP~1.DTB)
Checking file /overlays/at86rf233.dtbo (AT86RF~1.DTB)
Checking file /overlays/audioinjector-addons.dtbo (AUDIOI~1.DTB)
Checking file /overlays/audioinjector-wm8731-audio.dtbo (AUDIOI~2.DTB)
Checking file /overlays/dwc-otg.dtbo (DWC-OT~1.DTB)
Checking file /overlays/dpi18.dtbo (DPI18~1.DTB)
Checking file /overlays/dht11.dtbo (DHT11~1.DTB)
Checking file /overlays/dionaudio-loco.dtbo (DIONAU~2.DTB)
Checking file /overlays/dpi24.dtbo (DPI24~1.DTB)
Checking file /overlays/enc28j60-spi2.dtbo (ENC28J~1.DTB)
Checking file /overlays/dwc2.dtbo (DWC2~1.DTB)
Checking file /overlays/googlevoicehat-soundcard.dtbo (GOOGLE~1.DTB)
Checking file /overlays/enc28j60.dtbo (ENC28J~2.DTB)
Checking file /overlays/exc3000.dtbo (EXC300~1.DTB)
Checking file /overlays/fe-pi-audio.dtbo (FE-PI-~1.DTB)
Checking file /overlays/goodix.dtbo (GOODIX~1.DTB)
Checking file /overlays/iqaudio-digi-wm8804-audio.dtbo (IQAUDI~3.DTB)
Checking file /overlays/gpio-ir.dtbo (GPIO-I~1.DTB)
Checking file /overlays/gpio-key.dtbo (GPIO-K~1.DTB)
Checking file /overlays/gpio-poweroff.dtbo (GPIO-P~1.DTB)
Checking file /overlays/gpio-shutdown.dtbo (GPIO-S~1.DTB)
Checking file /overlays/hifiberry-amp.dtbo (HIFIBE~1.DTB)
Checking file /overlays/hifiberry-dac.dtbo (HIFIBE~2.DTB)
Checking file /overlays/hifiberry-dacplus.dtbo (HIFIBE~3.DTB)
Checking file /overlays/hifiberry-digi-pro.dtbo (HIFIBE~4.DTB)
Checking file /overlays/hifiberry-digi.dtbo (HIFIBE~5.DTB)
Checking file /overlays/hy28a.dtbo (HY28A~1.DTB)
Checking file /overlays/hy28b.dtbo (HY28B~1.DTB)
Checking file /overlays/i2c-bcm2708.dtbo (I2C-BC~1.DTB)
Checking file /overlays/i2c-gpio.dtbo (I2C-GP~1.DTB)
Checking file /overlays/i2c-mux.dtbo (I2C-MU~1.DTB)
Checking file /overlays/i2c-pwm-pca9685a.dtbo (I2C-PW~1.DTB)
Checking file /overlays/i2c-rtc-gpio.dtbo (I2C-RT~1.DTB)
Checking file /overlays/i2c-rtc.dtbo (I2C-RT~2.DTB)
Checking file /overlays/i2c-sensor.dtbo (I2C-SE~1.DTB)
Checking file /overlays/i2c0-bcm2708.dtbo (I2C0-B~1.DTB)
Checking file /overlays/i2c1-bcm2708.dtbo (I2C1-B~1.DTB)
Checking file /overlays/i2s-gpio28-31.dtbo (I2S-GP~1.DTB)
Checking file /overlays/iqaudio-dac.dtbo (IQAUDI~1.DTB)
Checking file /overlays/iqaudio-dacplus.dtbo (IQAUDI~2.DTB)
Checking file /overlays/rra-digidac1-wm8741-audio.dtbo (RRA-DI~1.DTB)
Checking file /overlays/justboom-dac.dtbo (JUSTBO~1.DTB)
Checking file /overlays/justboom-digi.dtbo (JUSTBO~2.DTB)
Checking file /overlays/lirc-rpi.dtbo (LIRC-R~1.DTB)
Checking file /overlays/mbed-dac.dtbo (MBED-D~1.DTB)
Checking file /overlays/mcp23017.dtbo (MCP230~1.DTB)
Checking file /overlays/mcp23s17.dtbo (MCP23S~1.DTB)
Checking file /overlays/mcp2515-can0.dtbo (MCP251~1.DTB)
Checking file /overlays/mcp2515-can1.dtbo (MCP251~2.DTB)
Checking file /overlays/mcp3008.dtbo (MCP300~1.DTB)
Checking file /overlays/mcp3202.dtbo (MCP320~1.DTB)
Checking file /overlays/media-center.dtbo (MEDIA-~1.DTB)
Checking file /overlays/midi-uart0.dtbo (MIDI-U~1.DTB)
Checking file /overlays/midi-uart1.dtbo (MIDI-U~2.DTB)
Checking file /overlays/mmc.dtbo (MMC~1.DTB)
Checking file /overlays/mpu6050.dtbo (MPU605~1.DTB)
Checking file /overlays/mz61581.dtbo (MZ6158~1.DTB)
Checking file /overlays/papirus.dtbo (PAPIRU~1.DTB)
Checking file /overlays/pi3-act-led.dtbo (PI3-AC~1.DTB)
Checking file /overlays/pi3-disable-bt.dtbo (PI3-DI~1.DTB)
Checking file /overlays/pi3-disable-wifi.dtbo (PI3-DI~2.DTB)
Checking file /overlays/pi3-miniuart-bt.dtbo (PI3-MI~1.DTB)
Checking file /overlays/piscreen.dtbo (PISCRE~1.DTB)
Checking file /overlays/piscreen2r.dtbo (PISCRE~2.DTB)
Checking file /overlays/pisound.dtbo (PISOUN~1.DTB)
Checking file /overlays/pitft22.dtbo (PITFT2~1.DTB)
Checking file /overlays/pitft28-capacitive.dtbo (PITFT2~2.DTB)
Checking file /overlays/pitft28-resistive.dtbo (PITFT2~3.DTB)
Checking file /overlays/pitft35-resistive.dtbo (PITFT3~1.DTB)
Checking file /overlays/pps-gpio.dtbo (PPS-GP~1.DTB)
Checking file /overlays/pwm-2chan.dtbo (PWM-2C~1.DTB)
Checking file /overlays/pwm.dtbo (PWM~1.DTB)
Checking file /overlays/qca7000.dtbo (QCA700~1.DTB)
Checking file /overlays/dionaudio-loco-v2.dtbo (DIONAU~1.DTB)
Checking file /overlays/rotary-encoder.dtbo (ROTARY~1.DTB)
Checking file /overlays/rpi-backlight.dtbo (RPI-BA~1.DTB)
Checking file /overlays/rpi-cirrus-wm5102.dtbo (RPI-CI~1.DTB)
Checking file /overlays/rpi-dac.dtbo (RPI-DA~1.DTB)
Checking file /overlays/rpi-display.dtbo (RPI-DI~1.DTB)
Checking file /overlays/rpi-ft5406.dtbo (RPI-FT~1.DTB)
Checking file /overlays/rpi-proto.dtbo (RPI-PR~1.DTB)
Checking file /overlays/rpi-sense.dtbo (RPI-SE~1.DTB)
Checking file /overlays/rpi-tv.dtbo (RPI-TV~1.DTB)
Checking file /overlays/upstream-aux-interrupt.dtbo (UPSTRE~1.DTB)
Checking file /overlays/sc16is750-i2c.dtbo (SC16IS~1.DTB)
Checking file /overlays/sc16is752-spi1.dtbo (SC16IS~2.DTB)
Checking file /overlays/sdhost.dtbo (SDHOST~1.DTB)
Checking file /overlays/sdio-1bit.dtbo (SDIO-1~1.DTB)
Checking file /overlays/sdio.dtbo (SDIO~1.DTB)
Checking file /overlays/sdtweak.dtbo (SDTWEA~1.DTB)
Checking file /overlays/smi-dev.dtbo (SMI-DE~1.DTB)
Checking file /overlays/smi-nand.dtbo (SMI-NA~1.DTB)
Checking file /overlays/smi.dtbo (SMI~1.DTB)
Checking file /overlays/spi-gpio35-39.dtbo (SPI-GP~1.DTB)
Checking file /overlays/spi-rtc.dtbo (SPI-RT~1.DTB)
Checking file /overlays/spi0-cs.dtbo (SPI0-C~1.DTB)
Checking file /overlays/spi0-hw-cs.dtbo (SPI0-H~1.DTB)
Checking file /overlays/spi1-1cs.dtbo (SPI1-1~1.DTB)
Checking file /overlays/spi1-2cs.dtbo (SPI1-2~1.DTB)
Checking file /overlays/spi1-3cs.dtbo (SPI1-3~1.DTB)
Checking file /overlays/spi2-1cs.dtbo (SPI2-1~1.DTB)
Checking file /overlays/spi2-2cs.dtbo (SPI2-2~1.DTB)
Checking file /overlays/spi2-3cs.dtbo (SPI2-3~1.DTB)
Checking file /overlays/tinylcd35.dtbo (TINYLC~1.DTB)
Checking file /overlays/uart0.dtbo (UART0~1.DTB)
Checking file /overlays/uart1.dtbo (UART1~1.DTB)
Checking file /overlays/vc4-fkms-v3d.dtbo (VC4-FK~1.DTB)
Checking file /overlays/vc4-kms-v3d.dtbo (VC4-KM~1.DTB)
Checking file /overlays/vga666.dtbo (VGA666~1.DTB)
Checking file /overlays/w1-gpio-pullup.dtbo (W1-GPI~1.DTB)
Checking file /overlays/w1-gpio.dtbo (W1-GPI~2.DTB)
Checking file /overlays/wittypi.dtbo (WITTYP~1.DTB)
Checking file /overlays/gpio-ir-tx.dtbo (GPIO-I~2.DTB)
Checking file /overlays/pibell.dtbo (PIBELL~1.DTB)
Checking file /overlays/pwm-ir-tx.dtbo (PWM-IR~1.DTB)
Checking file /overlays/sc16is752-i2c.dtbo (SC16IS~3.DTB)
Checking file /overlays/superaudioboard.dtbo (SUPERA~1.DTB)
Checking file /overlays/sx150x.dtbo (SX150X~1.DTB)
Checking file /overlays/upstream.dtbo (UPSTRE~2.DTB)
Checking file /.fseventsd/.
Checking file /.fseventsd/..
Checking file /.fseventsd/fseventsd-uuid (FSEVEN~1)
Checking file /.fseventsd/000000001730101b (000000~1)
Checking file /.fseventsd/000000001730101c (000000~2)
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/mmcblk0p1: 163 files, 44043/84261 clusters

Posted on
Sun Jun 02, 2019 11:00 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

pibeacon selecting hci0 and not hci1

It’s completely unclear to me how all 3 rpi can have the same ble mac number on the internal bus.

They don’t know of each other ..!!


The error in send message are from the fact that the plugin ignores the messages because of the ip number screw up


Karl.



Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 11:09 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

I believe the sequence was:

After initial start the rpi uses hci0 (default)
registers at the plugin with the hci0 mac and then gets told use hci1

That is true for all 3 rpi

And all hci0 ble mac numbers are identical
Then it also uses the wrong ip number.

Then things are screwed up


I first have to understand why all the rpi3 use the same ble-mac

Then fix the ip number (WiFi/eth) selection

Then allow to switch the mac & up number in a graceful way.


Karl


Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 11:24 am
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

It is definitely weird, and has felt like a MAC address confusion since I started, for sure.. Should we try removing the external dongles and see if they return unique ID's then, or should I wait and have you try your fix in code?

Posted on
Sun Jun 02, 2019 11:25 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

Yes you can try that


Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 12:56 pm
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

So, I removed the dongle from pi0 and pi1, and left the one in pi2 as a test. Not sure when this happened, but the MAC address in the drop down changed to: BB:27:EB:55:B2:22, which maps to hic1 on pi2. Also noticed that the pi0 device has since been deleted, though it shows up as a configured device in the menus. I can delete and re-add, etc, but again figured only controlled changes for now, so I've left it alone. I think, once we get this MAC address issue resolved, I should be fully back in business so will be able to add/remove devices at will by then.

And, looking through plugin.log, it seems the ip address that it's been complaining about has shifted to 10.0.1.125, which is pi1's wlan0 ip:

Code: Select all
23:59:29                          - sending ok to pi_IN_1      data: {"msgs":[["00:EA:24:46:CA:97",1,"x-x-x",-81.0,-49...dress":"10.0.1.126"}
23:59:30 TCPIP socket data receiving from ('10.0.1.124', 38198) not in accepted ip number list
23:59:30 TCPIP socket error rate high for 10.0.1.124/unknown ; previous:2019-06-01 23:59:30
23:59:30 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:30                          -10.0.1.124      pi_IN_0      ok         2019-05-31 16:05:03 2019-06-01 15:05:34      1275       899835       705      1474     447.6      0.63
23:59:30                          -10.0.1.124      pi_IN_Alive  ok         2019-05-31 16:04:35 2019-06-01 14:55:49        62        21176       341       346      10.5      0.03
23:59:30                          -10.0.1.124      unknown      errIP      2019-06-01 10:03:06 2019-06-01 23:59:30      2780            0         0         0       0.0      1.38
23:59:32 TCPIP socket data receiving from ('10.0.1.124', 38200) not in accepted ip number list
23:59:32 TCPIP socket error rate high for 10.0.1.124/unknown ; previous:2019-06-01 23:59:32
23:59:32 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:32                          -10.0.1.124      pi_IN_0      ok         2019-05-31 16:05:03 2019-06-01 15:05:34      1275       899835       705      1474     447.6      0.63
23:59:32                          -10.0.1.124      pi_IN_Alive  ok         2019-05-31 16:04:35 2019-06-01 14:55:49        62        21176       341       346      10.5      0.03
23:59:32                          -10.0.1.124      unknown      errIP      2019-06-01 10:03:06 2019-06-01 23:59:32      2781            0         0         0       0.0      1.38
23:59:34 TCPIP socket data receiving from ('10.0.1.124', 38202) not in accepted ip number list
23:59:34 TCPIP socket error rate high for 10.0.1.124/unknown ; previous:2019-06-01 23:59:34
23:59:34 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:34                          -10.0.1.124      pi_IN_0      ok         2019-05-31 16:05:03 2019-06-01 15:05:34      1275       899835       705      1474     447.6      0.63
23:59:34                          -10.0.1.124      pi_IN_Alive  ok         2019-05-31 16:04:35 2019-06-01 14:55:49        62        21176       341       346      10.5      0.03
23:59:34                          -10.0.1.124      unknown      errIP      2019-06-01 10:03:06 2019-06-01 23:59:34      2782            0         0         0       0.0      1.38
23:59:37 TCPIP socket data receiving from ('10.0.1.124', 38204) not in accepted ip number list
23:59:37 TCPIP socket error rate high for 10.0.1.124/unknown ; previous:2019-06-01 23:59:37
23:59:37 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:37                          -10.0.1.124      pi_IN_0      ok         2019-05-31 16:05:03 2019-06-01 15:05:34      1275       899835       705      1474     447.6      0.63
23:59:37                          -10.0.1.124      pi_IN_Alive  ok         2019-05-31 16:04:35 2019-06-01 14:55:49        62        21176       341       346      10.5      0.03
23:59:37                          -10.0.1.124      unknown      errIP      2019-06-01 10:03:06 2019-06-01 23:59:37      2783            0         0         0       0.0      1.38
23:59:42 TCPIP socket data receiving from ('10.0.1.125', 47004) not in accepted ip number list
23:59:42 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:59:42
23:59:42 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:42                          -10.0.1.125      pi_IN_0      ok         2019-06-01 11:00:15 2019-06-01 13:05:02        97        68484       706       947      34.1      0.05
23:59:42                          -10.0.1.125      pi_IN_1      ok         2019-06-01 10:00:13 2019-06-01 13:05:18        63        42680       677       947      21.2      0.03
23:59:42                          -10.0.1.125      pi_IN_Alive  ok         2019-05-31 21:01:59 2019-06-01 12:51:27        18         5720       317       346       2.8      0.01
23:59:42                          -10.0.1.125      unknown      errIP      2019-06-01 13:06:18 2019-06-01 23:59:42      5807            0         0         0       0.0      2.89
23:59:45 TCPIP socket data receiving from ('10.0.1.125', 47006) not in accepted ip number list
23:59:45 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:59:45
23:59:45 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:45                          -10.0.1.125      pi_IN_0      ok         2019-06-01 11:00:15 2019-06-01 13:05:02        97        68484       706       947      34.1      0.05
23:59:45                          -10.0.1.125      pi_IN_1      ok         2019-06-01 10:00:13 2019-06-01 13:05:18        63        42680       677       947      21.2      0.03
23:59:45                          -10.0.1.125      pi_IN_Alive  ok         2019-05-31 21:01:59 2019-06-01 12:51:27        18         5720       317       346       2.8      0.01
23:59:45                          -10.0.1.125      unknown      errIP      2019-06-01 13:06:18 2019-06-01 23:59:45      5808            0         0         0       0.0      2.89
23:59:48 TCPIP socket data receiving from ('10.0.1.125', 47008) not in accepted ip number list
23:59:48 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:59:48
23:59:48 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:48                          -10.0.1.125      pi_IN_0      ok         2019-06-01 11:00:15 2019-06-01 13:05:02        97        68484       706       947      34.1      0.05
23:59:48                          -10.0.1.125      pi_IN_1      ok         2019-06-01 10:00:13 2019-06-01 13:05:18        63        42680       677       947      21.2      0.03
23:59:48                          -10.0.1.125      pi_IN_Alive  ok         2019-05-31 21:01:59 2019-06-01 12:51:27        18         5720       317       346       2.8      0.01
23:59:48                          -10.0.1.125      unknown      errIP      2019-06-01 13:06:18 2019-06-01 23:59:48      5809            0         0         0       0.0      2.89
23:59:54 TCPIP socket data receiving from ('10.0.1.125', 47010) not in accepted ip number list
23:59:54 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:59:54
23:59:54 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:54                          -10.0.1.125      pi_IN_0      ok         2019-06-01 11:00:15 2019-06-01 13:05:02        97        68484       706       947      34.1      0.05
23:59:54                          -10.0.1.125      pi_IN_1      ok         2019-06-01 10:00:13 2019-06-01 13:05:18        63        42680       677       947      21.2      0.03
23:59:54                          -10.0.1.125      pi_IN_Alive  ok         2019-05-31 21:01:59 2019-06-01 12:51:27        18         5720       317       346       2.8      0.01
23:59:54                          -10.0.1.125      unknown      errIP      2019-06-01 13:06:18 2019-06-01 23:59:54      5810            0         0         0       0.0      2.89
23:59:58 TCPIP socket data receiving from ('10.0.1.125', 47012) not in accepted ip number list
23:59:58 TCPIP socket error rate high for 10.0.1.125/unknown ; previous:2019-06-01 23:59:58
23:59:58 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
23:59:58                          -10.0.1.125      pi_IN_0      ok         2019-06-01 11:00:15 2019-06-01 13:05:02        97        68484       706       947      34.1      0.05
23:59:58                          -10.0.1.125      pi_IN_1      ok         2019-06-01 10:00:13 2019-06-01 13:05:18        63        42680       677       947      21.2      0.03
23:59:58                          -10.0.1.125      pi_IN_Alive  ok         2019-05-31 21:01:59 2019-06-01 12:51:27        18         5720       317       346       2.8      0.01
23:59:58                          -10.0.1.125      unknown      errIP      2019-06-01 13:06:18 2019-06-01 23:59:58      5811            0         0         0       0.0      2.89

Posted on
Sun Jun 02, 2019 1:01 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: pibeacon selecting hci0 and not hci1

I guess the setup is messed up.


Could you edit the rpi device and set the mac# at the bottom to the proper one
It’s in the experts only section

Then save.


But I think I should first fix some things with the ip numbers before we continue.
Otherwise we chase our tails.

Karl




Sent from my iPhone using Tapatalk

Posted on
Sun Jun 02, 2019 1:26 pm
shrxman offline
Posts: 83
Joined: Apr 22, 2015

Re: pibeacon selecting hci0 and not hci1

Sure, I can wait. I can also make that MAC change if you'd like. To which pi, and to what MAC value? hci1 on each pi?

Who is online

Users browsing this forum: No registered users and 6 guests

cron