Time to address this issue if we want to keep our lovely Neo pixels. Who does not love our Neos. (don't raise your hand).

The problem

"The single-wire control protocol used by NeoPixels requires a very steady data stream at 800 kilobits per second. There’s a tiny margin for error, but not very much. Bits must be issued at a precisely controlled rate…the Adafruit_NeoPixel library handles all this behind the scenes, carefully counting the time of each machine code instruction. For every pixel, there’s 24 of these:"

"Meanwhile, the Arduino is normally using small fractions of time here and there... (More)

1. Using Processing

Give new users an easy interface to work with. One that is not as scary as the serial monitor.

We have a video that shows the process

Follow this link to the full guide and all details

2. Using desktop App by @Jason Snow

Try this desktop App it will ask you to install .NET Framework 3.5

It is like the mobile App but on your PC using USB to send all commands

3. Using Otto Blockly with the calibration block

The most simple way so far but annoyingly need to reupload the code until by iteration... (More)

When writing a new angle to a servo remember that a servo pulse is updated every 20ms - so for a slow move / sweep a wait state (delay) before writing a servo pos should be a multiple of 20ms.

When incrementing the angle by 1 and writing the new position every 50ms, the arm would move after 60ms then after 40ms, again after 60ms then 40ms and so on.

When incrementing the angle by 1 and writing the new position every 10ms, the arm would move after 20ms but in the meantime the angle is incremented by 2; when... (More)