Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time between update beacon varies. Filtering needs samples that are seperated by same time? #16

Open
kevindekemele opened this issue Mar 19, 2017 · 0 comments

Comments

@kevindekemele
Copy link

Hello,

When receiving beacons which have for instance, advertising period of 200ms; it seems that the beacon updates are received on random anywhere between 50ms up to 3000ms.

Here is my startScan() that shows this:

		evothings.eddystone.startScan(
			function(beacon)
			{
					if(beacon.address in beacons){
						var timediff = Date.now() - beacon.timeStamp;
						console.log(beacon.address + "updated with 
"+ beacon.rssi + " at " + timediff);
					}
					else{
						console.log(beacon.address + "discovered with "+ beacon.rssi + " at " + Date.now());
	
					}
					// Insert/update beacon table entry.
					beacon.timeStamp = Date.now();
					beacons[beacon.address] = beacon;			
				
			},
			function(error)
			{
				console.log('Eddystone Scan error: ' + JSON.stringify(error));
			});

I want to filter the erratic RSSI signal. I have a background in signal processing, and these discrete type signals can only be filtered if each update has the same time between them (uniform vs non-uniformally sampled signals).

So your lowPass filter doesn't really make much sense? You can not talk about a cutoff frequency if the time between each sample varies enormously.

Or do I have to assume that each update does correspond with 200 ms time difference (or is not every advertisement received??)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant