safety
This commit is contained in:
parent
2e3fedc6ce
commit
9074217edc
2 changed files with 103 additions and 1 deletions
|
|
@ -22,4 +22,103 @@ It repeatedly reports BleakScanner callbacks not invoked.
|
|||
zerodev1 shows no scanner callback errors in the shown log.
|
||||
So the immediate code point to instrument is LinuxBluetoothDriver._perform_scan(), around BleakScanner(... detection_callback=...), scanner.start(), scanner.stop(), and callback_count[0] == 0.
|
||||
```
|
||||
So I'll try a run with no change on zerodev1, but force "cpp" for zerdev2, I'll keep the logs in run14.
|
||||
So I'll try a run with no change on zerodev1, but force "cpp" for zerdev2, I'll keep the logs in run14.
|
||||
May 17, 2026 4:45 AM Did a lot of forensics for run 14, finally concluded a reboot of both was last resort. Also, created symlinks under ~/.reticulum/interfaces to this project's files. Previous runs may not have been using the "shim" given static file under ~/.reticulum/interfaces. For example:
|
||||
|
||||
```bash
|
||||
So this discrepancy may invalidate all prior testing? Should I try using soft links under ~/.reticulum/interfaces pointing to the git controlled project files?
|
||||
jlpoole@zerodev1:/usr/local/src/ble-reticulum $ ls src/ble_reticulum/ -la
|
||||
total 312
|
||||
drwxrwxr-x 3 jlpoole jlpoole 4096 May 16 20:28 .
|
||||
drwxrwxr-x 3 jlpoole jlpoole 4096 May 15 11:25 ..
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 9891 May 16 08:11 BLEAgent.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 20471 May 15 11:25 BLEFragmentation.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 2433 May 16 19:36 BLEFragmentationBackend.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 27232 May 16 08:11 BLEGATTServer.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 120620 May 16 20:28 BLEInterface.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 0 May 15 11:25 __init__.py
|
||||
drwxrwxr-x 2 jlpoole jlpoole 4096 May 16 19:37 __pycache__
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 7340 May 15 11:25 bluetooth_driver.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 107923 May 16 08:11 linux_bluetooth_driver.py
|
||||
jlpoole@zerodev1:/usr/local/src/ble-reticulum $ ls ~/.reticulum/interfaces/ -la
|
||||
total 308
|
||||
drwxrwxr-x 3 jlpoole jlpoole 4096 May 15 16:35 .
|
||||
drwxrwxr-x 4 jlpoole jlpoole 4096 May 16 07:43 ..
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 9751 May 15 12:19 BLEAgent.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 20471 May 15 12:19 BLEFragmentation.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 27092 May 15 12:19 BLEGATTServer.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 119128 May 15 12:19 BLEInterface.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 0 May 15 12:19 __init__.py
|
||||
drwxrwxr-x 2 jlpoole jlpoole 4096 May 15 16:35 __pycache__
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 7340 May 15 12:19 bluetooth_driver.py
|
||||
-rw-rw-r-- 1 jlpoole jlpoole 107783 May 15 12:19 linux_bluetooth_driver.py
|
||||
jlpoole@zerodev1:/usr/local/src/ble-reticulum
|
||||
```
|
||||
I tried CPP versions and I extended the timeout from 60 seconds to 90, the previous 60 was cutting it too close, though at the very early tests, the Constitution could be transferred in 36 seconds, so note should be made that something was introduced that slowed the transfer down.
|
||||
```bash
|
||||
(rnsenv) jlpoole@jp /usr/local/src/ble-reticulum/scripts $ date; ./analyze_reticulum_file_transfer_20260516_1130.pl ../tmp/run15/20260517_0439_zerodev1_Constitution_CPP.txt ../tmp/run15/20260517_0439_zerodev2_Constitution_CPP.txt
|
||||
Sun May 17 04:52:33 PDT 2026
|
||||
Reticulum BLE file transfer analysis
|
||||
Generated: 2026-05-17 04:52:33 PDT
|
||||
Input files:
|
||||
../tmp/run15/20260517_0439_zerodev1_Constitution_CPP.txt
|
||||
../tmp/run15/20260517_0439_zerodev2_Constitution_CPP.txt
|
||||
|
||||
Log provenance summary:
|
||||
20260517_0439_zerodev1_Constitution_CPP.txt receiver=zerodev1 date='Sun May 17 04:44:06 PDT 2026' command_lines=21 post_marker_lines=591
|
||||
20260517_0439_zerodev2_Constitution_CPP.txt receiver=zerodev2 date='Sun May 17 04:44:08 AM PDT 2026' command_lines=20 post_marker_lines=587
|
||||
|
||||
Chrony clock notes from logs:
|
||||
20260517_0439_zerodev1_Constitution_CPP.txt
|
||||
System time : 0.000602999 seconds fast of NTP time
|
||||
System time : 0.000000797 seconds slow of NTP time
|
||||
20260517_0439_zerodev2_Constitution_CPP.txt
|
||||
System time : 0.000199690 seconds slow of NTP time
|
||||
System time : 0.000000200 seconds fast of NTP time
|
||||
|
||||
Declared outbound sends observed in logs:
|
||||
sender=zerodev1 file=US_Constitution.txt chunks= 140 bytes= 44225 chunk_data_bytes=316
|
||||
sender=zerodev2 file=US_Constitution.txt chunks= 148 bytes= 44225 chunk_data_bytes=n/a
|
||||
|
||||
Direction: zerodev1->zerodev2
|
||||
file : US_Constitution.txt
|
||||
chunks received : 140 of 140
|
||||
completeness : 100.00%
|
||||
missing chunks : none
|
||||
duplicate chunks : none
|
||||
payload bytes RX : 44225
|
||||
first chunk RX : 04:44:33.283
|
||||
last chunk RX : 04:45:09.259
|
||||
receiver span : 35.976 s
|
||||
sender span : 14.299 s
|
||||
payload rate RX span : 1229.3 B/s 9834.3 bit/s
|
||||
payload rate TX span : 3092.8 B/s 24742.6 bit/s
|
||||
one-way latency min/median/mean/p95/max/stddev: 246.163 / 11275.384 / 11238.875 / 21147.058 / 21922.931 / 6402.281 ms
|
||||
receiver inter-chunk gap min/median/mean/p95/max/stddev: 191.000 / 244.000 / 258.820 / 297.300 / 341.000 / 36.970 ms
|
||||
sender inter-chunk gap min/median/mean/p95/max/stddev: 101.924 / 102.945 / 102.872 / 104.299 / 109.563 / 0.917 ms
|
||||
|
||||
Direction: zerodev2->zerodev1
|
||||
file : US_Constitution.txt
|
||||
chunks received : 148 of 148
|
||||
completeness : 100.00%
|
||||
missing chunks : none
|
||||
duplicate chunks : none
|
||||
payload bytes RX : 44225
|
||||
first chunk RX : 04:44:33.284
|
||||
last chunk RX : 04:45:07.703
|
||||
receiver span : 34.419 s
|
||||
sender span : 15.470 s
|
||||
payload rate RX span : 1284.9 B/s 10279.2 bit/s
|
||||
payload rate TX span : 2858.7 B/s 22869.8 bit/s
|
||||
one-way latency min/median/mean/p95/max/stddev: 254.424 / 9806.025 / 9750.358 / 18371.803 / 19203.224 / 5533.436 ms
|
||||
receiver inter-chunk gap min/median/mean/p95/max/stddev: 145.000 / 243.000 / 234.143 / 246.700 / 292.000 / 24.080 ms
|
||||
sender inter-chunk gap min/median/mean/p95/max/stddev: 103.738 / 104.216 / 105.239 / 108.147 / 122.931 / 2.539 ms
|
||||
|
||||
Hello/handshake RX records:
|
||||
zerodev2 -> zerodev1 recv=04:44:32.951 latency= 118.171 ms message='hello'
|
||||
zerodev1 -> zerodev2 recv=04:44:32.963 latency= 113.954 ms message='hello back'
|
||||
|
||||
Caution: one-way latency assumes sender and receiver clocks are synchronized.
|
||||
Your chronyc tracking output helps bound this error, but it is not a substitute for ACK/round-trip timing.
|
||||
(rnsenv) jlpoole@jp /usr/local/src/ble-reticulum/scripts $
|
||||
```
|
||||
|
|
|
|||
|
|
@ -18,6 +18,7 @@ timeout 240 python3 examples/ble_dual_node_echo.py \
|
|||
|
||||
# zerodev1 Command clump START
|
||||
date
|
||||
cd /usr/local/src/ble-reticulum/
|
||||
chronyc tracking
|
||||
chronyc sources -v
|
||||
echo .
|
||||
|
|
@ -41,6 +42,7 @@ chronyc sources -v
|
|||
|
||||
# zerodev2 Command clump START
|
||||
date
|
||||
cd /usr/local/src/ble-reticulum/
|
||||
chronyc tracking
|
||||
chronyc sources -v
|
||||
echo .
|
||||
|
|
@ -61,6 +63,7 @@ chronyc sources -v
|
|||
|
||||
# zerodev2 CPP Command clump START
|
||||
date
|
||||
cd /usr/local/src/ble-reticulum/
|
||||
chronyc tracking
|
||||
chronyc sources -v
|
||||
echo .
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue