Skip to content

Conversation

rotv
Copy link
Contributor

@rotv rotv commented Dec 10, 2015

No description provided.

@elliots
Copy link
Member

elliots commented Dec 10, 2015

Should I assume this works as expected and won't cause problems? (I have no idea how to run this)

:)

@rotv
Copy link
Contributor Author

rotv commented Dec 11, 2015

It works on my computer ;)

sudo ./RFSniffer is the normal way, I've added sudo ./RFSniffer <pulseLength>, e.g. sudo ./RFSniffer 150 (both ways are still supported)

@rotv
Copy link
Contributor Author

rotv commented Dec 19, 2015

I figured at would simplify quite a lot for users to easily be able to test/specify different pulse lengths without having to rewrite and recompile the code.

@rotv
Copy link
Contributor Author

rotv commented Jan 7, 2016

Any taker for merging this?

elliots pushed a commit that referenced this pull request Jan 7, 2016
Added optional pulse-length argument to RFSniffer and the executables to gitignore
@elliots elliots merged commit 9b75288 into ninjablocks:master Jan 7, 2016
@elliots
Copy link
Member

elliots commented Jan 7, 2016

Apologies, thought I already merged this.

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

Successfully merging this pull request may close these issues.

2 participants