Advertising and Scanning parameters, Cracking Contraptions

I read (no, I ‘scanned’ har, har) “Precise Energy Modeling for the Bluetooth LowEnergy Protocol” and set up advertising and scanning parameters based on it’s teachings.

I concluded:

Advertising interval 1-2.5 seconds
Scan interval 2.56s
Scan window 11.25 ms

I made two new test programs for David to measure.

Advertise250mNoLeds.hex

Performs an advertising cycle every 250ms – no led activity under test! N.B. There will be some random additional housekeeping activity every 5th advertising cycle, which should be ignored.

Scan256m12msNoLeds.hex

Performs a 12ms scanning cycle every 255ms – no led activity under test! I think it should run for about an hour before it performs disruptive housekeeping.

———-
David writes

My attempt at shielding has failed miserably. It turns out that the best results comes from not using the uCurrent but rather a larger resistor. these photos used the 10 ohm resistor in the uCurrent but the uCurrent is turned off and the scope connected directly to the wires from the TS06.

What does it mean when all of the LEDs flash on and off 4 times per second when running Scan256m12msNoLeds.hex? It starts what I think is normally and after a couple of minutes the flashing starts.

It’s a bug! I set a timer-based pause, and sometimes it’s value is zero seconds. This causes the soft-machine to crash. Seems like pasue(0) ought to make sense. Fixed in the next version.