piBeacon: presence monitoring plugin discussions

Posted on
Mon Nov 20, 2017 9:18 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

ALL controleverything i2c sensors (i looked at) connect like this:

+5v = pin 2 or pin 4
gnd = pin 6 or 7
SDA = pin 3
SCL = pin 5


you could use 2,6,3,5, they are next to each other BUT !!! do not reverse them , You might connect +5v to and i2c pin that could kill the whole RPI

I use 1, 6 and 3,5 remove pins 1, 4 from the connector to make it asymmetrical, you could still connect 5V to i2c, but the direction of the connector is easier to id.

Karl

Posted on
Mon Nov 20, 2017 9:50 am
johnpolasek offline
Posts: 911
Joined: Aug 05, 2011
Location: Aggieland, Texas

Re: piBeacon: presence monitoring plugin discussions

You might want to correct that in the http://forums.indigodomo.com/viewtopic.php?f=187&t=15563 topic where you say to connect VCC to Pin1.

Posted on
Mon Nov 20, 2017 10:14 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

most other i2c sensors use 3.3V ONLY (*) controleverything.com uses +5V exclusively.

but I corrected PIN17 --> V+ to Pin1 V+ in some lines. Thanks for pointing it out .


Karl

(*) some use also +5V e.g. the microwave sensors, but they are not i2c sensors

Posted on
Fri Nov 24, 2017 9:16 pm
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Hi Karl

Still waiting for pressure sensors to arrive ....

But have expanded rpi family and currenty installing raspbian stretch image (done)

But cannot login with pi and raspberry to expand disk and set timezone.

?Is this the correct password for this image?
Edit:
See changed to pi:pibeacon --- in your instructions - sorry missed that!

G

Posted on
Fri Nov 24, 2017 10:02 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

I did that to NOT have raspberry as the default pass wd and to make you guys change it ..

initially thought about Karl-Is-The-Greatest but one Trump is enough. :cry:

Posted on
Fri Nov 24, 2017 10:56 pm
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Thanks Karl
Having issues with new rpis not being sent config files and not auto creating asDevices in Indigo.

They do exist, new ss, with the usual setup sets completed (expand disk, set timezone etc), I can SSH into them, and have within Indigo Menu - Run Basic IP setup, Send Files - but it appears nothing makes it to the rpi.

I am running in WebServer mode as did have some issues with Socket Mode (thought might be firewall/wifi setup) so went back to Webserver.

This continues to appear in log:
piBeacon printpiUpToDate list .. pi#:[actionLeft];.. ([]=ok): 0:[]; 1:[]; 2:[]; 3:[]; 4:[u'updateParams']; 5:[u'updateParams']; 6:[]; 7

Could this be relevant - is the default setup of the new rpi socket? or this shouldn't matter as files go via ssh?

(More than happy to TeamViewer if easier)

Glenn

Posted on
Sat Nov 25, 2017 12:06 am
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

this ":[u'updateParams']; 5:[u'updateParams'];" means it can not send to the RPI

are you trying from the same mac as the indigo server? if not go to the indigo server and try from there.

you can also switch on "debug send/update to RPI, it should give you more info

I often make the mistake to have the ROI not enabled / not on in initial setup.

COMING UP!!!!!!!!!!!!!!!
++new bosh sensor BME680 sensor for temp/press/hum and Gas composition.
have it running, just need to fine-tune the parameters, it is a little bit more complicated as it needs to heat, and become stable for ~ 10 minutes. then it goes through cycles fro temp vs Gas composition

++ MQx sensors to measure Co, CH4, benzine, CNG . They now work well.

++ some nice formatting

etc
COMING UP!!!!!!!!!!!!!!!

Karl


ps Glenn : let me know when you have time for teamviewer

Posted on
Sat Nov 25, 2017 12:09 am
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

TeamViewer - now fine with me.
Have PM/emailed you

Glenn

Posted on
Fri Dec 01, 2017 9:17 pm
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Hi Karl

Thanks for the Team Viewer session and sorting out those issues.

Some of the Network issue persist (well now isolated to some of the wifi RPIs) and appears to be isolated to wifi connected Stretch Rpis.

The only remaining jessie one is Ethernet connected. The Ethernet connected stretchs are fine and don't loose connection (and have moved some to Ethernet) - but the wifi ones eventually become uncontactable, unpingable, can ssh- but still occ seem to send data. The log then fills up with ping return 512. I can't ssh or ping until restart them

There seems a lot of wifi changes from Jessie to stretch with networks and wpa_supplicant.conf.

Code: Select all
wlan0     IEEE 802.11  ESSID:"GlennDesktop"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 24:A4:3C:11:DA:61
          Bit Rate=65 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=38/70  Signal level=-72 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3  Invalid misc:0   Missed beacon:0


I currently trying adding:
Code: Select all
sudo iwconfig wlan0 power off


To disable Power Management .

But wonder whether this is something up with the PI built in Wifi (which there shouldn't be) - will also try a usb dongle and see if better.

Glenn

Posted on
Fri Dec 01, 2017 10:21 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

can you start the RPi on wifi connected to a monitor and check if they change ip number, loose connection....

all but one of mine are on ethernet. the one on wifi is on jessie

Karl

Posted on
Fri Dec 01, 2017 10:29 pm
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

Sorry - can't do monitor - but on startup ping fine; and can ssh in. (just)
Changed power management to off and run dmsg (results below)
But unfortunately within a minute or two the same ping timeouts and failure to connect.
(have pibeacon disabled at the moment)


Code: Select all
Reply from 192.168.1.182: bytes=32 time=1013ms TTL=64
Reply from 192.168.1.182: bytes=32 time=1ms TTL=64
Reply from 192.168.1.182: bytes=32 time=6ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=7ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=68ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=6ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=11ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=2ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=8ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=2ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=8ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=6ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=3ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=2ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=9ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=6ms TTL=64
Reply from 192.168.1.182: bytes=32 time=1ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=3ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=1ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=22ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=6ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Reply from 192.168.1.182: bytes=32 time=30ms TTL=64
Reply from 192.168.1.182: bytes=32 time=24ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=17ms TTL=64
Reply from 192.168.1.182: bytes=32 time=4ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.182: bytes=32 time=443ms TTL=64
Reply from 192.168.1.182: bytes=32 time=5ms TTL=64
Reply from 192.168.1.182: bytes=32 time=94ms TTL=64
Reply from 192.168.1.182: bytes=32 time=149ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.182: bytes=32 time=186ms TTL=64
Request timed out.
Reply from 192.168.1.182: bytes=32 time=989ms TTL=64
Request timed out.



Code: Select all
dmsg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.41-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1023 SMP Tue Aug 8 16:00:15 BST 2017
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c6eec0, node_mem_map ba3a1000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] percpu: Embedded 14 pages/cpu @ba35b000 s25600 r8192 d23552 u57344
[    0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=ed6de3df-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940356K/970752K available (7168K kernel code, 484K rwdata, 2012K rodata, 1024K init, 778K bss, 22204K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c79094   ( 485 kB)
                      .bss : 0x80c7b000 - 0x80d3da64   ( 779 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000022] Switching to timer-based delay loop, resolution 52ns
[    0.000299] Console: colour dummy device 80x30
[    0.001183] console [tty1] enabled
[    0.001227] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001295] pid_max: default: 32768 minimum: 301
[    0.001628] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001670] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002563] Disabling cpuset control group subsystem
[    0.002720] CPU: Testing write buffer coherency: ok
[    0.002783] ftrace: allocating 22396 entries in 66 pages
[    0.049271] CPU0: update cpu_capacity 1024
[    0.049323] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.049383] Setting up static identity map for 0x100000 - 0x100034
[    0.051260] CPU1: update cpu_capacity 1024
[    0.051267] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.051951] CPU2: update cpu_capacity 1024
[    0.051957] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.052625] CPU3: update cpu_capacity 1024
[    0.052631] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.052719] Brought up 4 CPUs
[    0.052890] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.052919] CPU: All CPU(s) started in HYP mode.
[    0.052946] CPU: Virtualization extensions available.
[    0.053767] devtmpfs: initialized
[    0.064797] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.065116] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.065178] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.065741] pinctrl core: initialized pinctrl subsystem
[    0.066660] NET: Registered protocol family 16
[    0.068908] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.077666] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.077714] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.077884] Serial: AMBA PL011 UART driver
[    0.079787] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.080334] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.150081] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
[    0.151946] SCSI subsystem initialized
[    0.152122] usbcore: registered new interface driver usbfs
[    0.152224] usbcore: registered new interface driver hub
[    0.152337] usbcore: registered new device driver usb
[    0.159078] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-08-08 12:01
[    0.160474] clocksource: Switched to clocksource arch_sys_counter
[    0.207659] VFS: Disk quotas dquot_6.6.0
[    0.207770] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.207996] FS-Cache: Loaded
[    0.208261] CacheFiles: Loaded
[    0.220412] NET: Registered protocol family 2
[    0.221339] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.221476] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.221688] TCP: Hash tables configured (established 8192 bind 8192)
[    0.221801] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.221868] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.222101] NET: Registered protocol family 1
[    0.222537] RPC: Registered named UNIX socket transport module.
[    0.222569] RPC: Registered udp transport module.
[    0.222597] RPC: Registered tcp transport module.
[    0.222625] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.223556] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.225864] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.241939] FS-Cache: Netfs 'nfs' registered for caching
[    0.242934] NFS: Registering the id_resolver key type
[    0.242984] Key type id_resolver registered
[    0.243012] Key type id_legacy registered
[    0.245440] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.245582] io scheduler noop registered
[    0.245612] io scheduler deadline registered (default)
[    0.245920] io scheduler cfq registered
[    0.251601] BCM2708FB: allocated DMA memory fad10000
[    0.251654] BCM2708FB: allocated DMA channel 0 @ bb80f000
[    0.260333] Console: switching to colour frame buffer device 82x26
[    0.268777] bcm2835-rng 3f104000.rng: hwrng registered
[    0.271189] vc-cma: Videocore CMA driver
[    0.273409] vc-cma: vc_cma_base      = 0x00000000
[    0.275633] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.277893] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.280299] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.299888] brd: module loaded
[    0.310789] loop: module loaded
[    0.312831] Loading iSCSI transport class v2.0-870.
[    0.315396] usbcore: registered new interface driver smsc95xx
[    0.317493] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.547687] Core Release: 2.80a
[    0.549751] Setting default values for core params
[    0.551813] Finished setting default values for core params
[    0.754258] Using Buffer DMA mode
[    0.756311] Periodic Transfer Interrupt Enhancement - disabled
[    0.758466] Multiprocessor Interrupt Enhancement - disabled
[    0.760652] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.762858] Dedicated Tx FIFOs mode
[    0.765316] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
[    0.769769] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.781148] dwc_otg: Microframe scheduler enabled
[    0.781197] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058f7fc
[    0.783507] WARN::hcd_init_fiq:460: FIQ ASM at 0x8058fb6c length 36
[    0.785833] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
[    0.788187] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.790525] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.792890] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.795212] Init: Port Power? op_state=1
[    0.797469] Init: Power Port (0)
[    0.799847] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.802181] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.804487] usb usb1: Product: DWC OTG Controller
[    0.806738] usb usb1: Manufacturer: Linux 4.9.41-v7+ dwc_otg_hcd
[    0.809009] usb usb1: SerialNumber: 3f980000.usb
[    0.812106] hub 1-0:1.0: USB hub found
[    0.814312] hub 1-0:1.0: 1 port detected
[    0.817042] dwc_otg: FIQ enabled
[    0.817046] dwc_otg: NAK holdoff enabled
[    0.817051] dwc_otg: FIQ split-transaction FSM enabled
[    0.817064] Module dwc_common_port init
[    0.817297] usbcore: registered new interface driver usb-storage
[    0.819643] mousedev: PS/2 mouse device common for all mice
[    0.822806] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.825341] bcm2835-cpufreq: min=600000 max=1200000
[    0.827989] sdhci: Secure Digital Host Controller Interface driver
[    0.830308] sdhci: Copyright(c) Pierre Ossman
[    0.832860] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
[    0.837437] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.839985] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.845062] ledtrig-cpu: registered to indicate activity on CPUs
[    0.847715] hidraw: raw HID events driver (C) Jiri Kosina
[    0.850393] usbcore: registered new interface driver usbhid
[    0.852888] usbhid: USB HID core driver
[    0.856145] vchiq: vchiq_init_state: slot_zero = 0xbad80000, is_master = 0
[    0.860376] Initializing XFRM netlink socket
[    0.862945] NET: Registered protocol family 17
[    0.865538] Key type dns_resolver registered
[    0.868354] Registering SWP/SWPB emulation handler
[    0.871549] registered taskstats version 1
[    0.874334] vc-sm: Videocore shared memory driver
[    0.876849] [vc_sm_connected_init]: start
[    0.879766] [vc_sm_connected_init]: end - returning 0
[    0.888174] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.894707] sdhost: log_buf @ bad07000 (fad07000)
[    0.970500] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.975176] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.977622] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    1.030564] Indeed it is in host mode hprt0 = 00021501
[    1.093022] of_cfs_init
[    1.095457] of_cfs_init: OK
[    1.098090] Waiting for root device PARTUUID=ed6de3df-02...
[    1.112054] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.115505] random: fast init done
[    1.117983] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.121732] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.126632] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.161887] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.169057] mmc0: new high speed SDHC card at address aaaa
[    1.171933] mmcblk0: mmc0:aaaa SL32G 29.7 GiB
[    1.176845]  mmcblk0: p1 p2
[    1.215899] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    1.218216] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    1.230503] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.232927] Indeed it is in host mode hprt0 = 00001101
[    1.298287] mmc1: new high speed SDIO card at address 0001
[    1.328828] EXT4-fs (mmcblk0p2): recovery complete
[    1.332753] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.337350] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.340626] devtmpfs: mounted
[    1.344887] Freeing unused kernel memory: 1024K (80b00000 - 80c00000)
[    1.460808] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    1.463429] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.466832] hub 1-1:1.0: USB hub found
[    1.469538] hub 1-1:1.0: 5 ports detected
[    1.736696] systemd[1]: System time before build time, advancing clock.
[    1.790519] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.855493] NET: Registered protocol family 10
[    1.871079] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.906722] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.915667] systemd[1]: Detected architecture arm.
[    1.930836] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    1.930844] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.936920] smsc95xx v1.0.5
[    1.940645] systemd[1]: Set hostname to <raspberrypi>.
[    2.025467] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:ed:c6:2a
[    2.424415] systemd[1]: Created slice System Slice.
[    2.433570] systemd[1]: Mounting POSIX Message Queue File System...
[    2.440268] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    2.449956] systemd[1]: Mounting RPC Pipe File System...
[    2.457357] systemd[1]: Listening on Journal Socket (/dev/log).
[    2.464651] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    2.471746] systemd[1]: Created slice system-autologin.slice.
[    2.559085] i2c /dev entries driver
[    3.006165] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.377534] systemd-journald[111]: Received request to flush runtime journal from PID 1
[    3.509254] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    3.751044] usbcore: registered new interface driver brcmfmac
[    3.864689] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[    4.683657] uart-pl011 3f201000.serial: no DMA platform data
[    4.973365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    4.973392] brcmfmac: power management disabled
[    5.062704] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    5.063094] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.246263] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
[    5.975758] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[    9.285892] Bluetooth: Core ver 2.22
[    9.286024] NET: Registered protocol family 31
[    9.286034] Bluetooth: HCI device and connection manager initialized
[    9.287567] Bluetooth: HCI socket layer initialized
[    9.287583] Bluetooth: L2CAP socket layer initialized
[    9.287621] Bluetooth: SCO socket layer initialized
[    9.297251] Bluetooth: HCI UART driver ver 2.3
[    9.297264] Bluetooth: HCI UART protocol H4 registered
[    9.297270] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    9.297434] Bluetooth: HCI UART protocol Broadcom registered
[    9.495278] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.495284] Bluetooth: BNEP filters: protocol multicast
[    9.495295] Bluetooth: BNEP socket layer initialized
[   72.846343] random: crng init done
[  101.280032] brcmfmac: power management disabled


& after 5 minutes or so got this back

Code: Select all
wlan0     IEEE 802.11  ESSID:"GlennDesktop"
          Mode:Managed  Frequency:2.462 GHz  Access Point: 24:A4:3C:11:DA:61
          Bit Rate=5.5 Mb/s   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=51/70  Signal level=-59 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:52  Invalid misc:0   Missed beacon:0


Pretty bad wifi signal - despite being under the wifi Unifi AP literally.

I'll get some usb dongles and try them.


Mmmm - managed to run netstat on rpi before connection dies - and found this.
192,168.1.6 - is the IndigoServer - but this is with PiBeacon Disabled..

This is obviously rpi 182 talking to Indigo. But the timeouts and slow-downs appear at the same time it starts on the netstat result.
Other wired rpi - only have one open connection - whether this is result of poor connection.

Will try socket connection again and see whether any better...

?
..

Code: Select all
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 192.168.1.182:44346     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44348     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44352     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44356     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44354     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44350     192.168.1.6:8176        TIME_WAIT
tcp        0    164 192.168.1.182:22        192.168.1.209:7879      ESTABLISHED
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 192.168.1.182:44346     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44348     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44352     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44356     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44354     192.168.1.6:8176        TIME_WAIT
tcp        0      0 192.168.1.182:44350     192.168.1.6:8176        TIME_WAIT
tcp        0    164 192.168.1.182:22        192.168.1.209:7879      ESTABLISHED



G

Posted on
Fri Dec 01, 2017 11:14 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

If ping does not work nothing will be working.


Sent from my iPhone using Tapatalk

Posted on
Fri Dec 01, 2017 11:16 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

Will switch my pi0 to stretch. And try tomorrow.


Sent from my iPhone using Tapatalk

Posted on
Fri Dec 01, 2017 11:23 pm
GlennNZ offline
User avatar
Posts: 1562
Joined: Dec 07, 2014
Location: Central Coast, Australia

Re: piBeacon: presence monitoring plugin discussions

kw123 wrote:
Will switch my pi0 to stretch. And try tomorrow.


Sent from my iPhone using Tapatalk


Thanks.

I have switched to socket - and on indigo get multiple incoming socket connections from same dodgy reception rpi
Code: Select all
tcp4       0      0  192.168.1.6.12087      192.168.1.182.35942    ESTABLISHED
tcp4       0      0  192.168.1.6.12087      192.168.1.182.35938    ESTABLISHED
tcp4       0      0  192.168.1.6.12087      192.168.1.182.35918    ESTABLISHED
tcp4       0      0  192.168.1.6.12087      192.168.1.182.35914    ESTABLISHED
tcp4       0      0  192.168.1.6.12087      192.168.1.182.35902    ESTABLISHED


I actually wonder whether it is dodgy reception based
eg. the python/rpi based timeout for the connection attempts back to server - the timeout, repeats etc??

Hence only obvious when reception not brilliant.

In piBeaconUtils.py
? use UDP rather than TCP.
Won't know that it has got there - but less of issue I suspect.
Code: Select all
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)

or the time.sleep (0.5) going up to the timeout?

Just my two cents!
Good luck. :roll:


Glenn

Posted on
Fri Dec 01, 2017 11:31 pm
kw123 offline
User avatar
Posts: 8363
Joined: May 12, 2013
Location: Dallas, TX

Re: piBeacon: presence monitoring plugin discussions

Connections:
1. Rpi to indigo. Either curl or socket with new data
2. Ssh sftp indigo to rpi to send config and py files
3. Socket indigo to rpi as backup and for specific quick messages

In between pings to each other to check if connection ok.



Sent from my iPhone using Tapatalk

Page 60 of 78 1 ... 57, 58, 59, 60, 61, 62, 63 ... 78

Who is online

Users browsing this forum: No registered users and 7 guests