Resolved the issue of user-defined start and stop angles not actually be...

...ing reflected in data output. This was done by adding two new functions to LMS1xx.h, setScanRange and getScanRange. In addition, ensured that an LMS5xx could also be used by specifically telling the laser to run in ofxSick class's connect function with startDevice().

Got a 5xx to run the basic example, hooray! I'm hoping this doesn't break the 1xx ability to function, but I only have a 5xx so I can't test this. Blob detection is broken but I'll open up an issue to explain that.

I was examining the message spec for the 5xx and 1xx models and noticed that mLMPsetscancfg actually ignores whatever angle values you give it. Mechanically, the laser never actually modifies the area it scans but it does modify its frequency and resolution so I suppose it makes sense. The spec I found is here: https://dl.dropboxusercontent.com/u/60273224/im0045927.pdf

I assumed this was an oversight and modified the code so that now whatever angle values you provide in the ofxSick constructor are reflected in the laser's data output.