I thought -1 was the default for maxing the servo speed. Thought for sure I read that somewhere. As soon as I get my dome back from the powdercoater I'll reinstall all the servos and play around some more.

I need to do a lot more tweaking.

Thanks DJ!

Hey DJ,

Any updates on the blaster? Can't wait to get my paws on it!

Thanks!

Doug

@DJ , Will the Pixel Blaster also be able to run the DotStar LED's? They seem to be slightly different than the Neos. Here is a link:

DotStar

You'd have to compare the data sheets to see if they have the same protocol

Quote:

However, unlike NeoPixels, these LEDs have 2 wires (input and output) for sending data - one clock pin and one data pin. That means you need two pins, not one, to control DotStars. Because the clock and data is seperated, you can use any processor speed or type to control these strips, and you don't have to worry about being careful with the timing. Hardware SPI support is handy but not required. This makes them excellent for use with any microcontroller or microprocessor, including Arduino, Raspberry Pi, BeagleBone, Propeller, SparkCore, and any 'raw'

from this, you might be able to run from the v4 directly without the blaster. It looks like the same protocols are still supported from what I read, but aren't optimal.

Ok thanks.

I'm trying to convert everything in ALAN over to dedicated EZ Products. I've managed so far to replace my specialty servo's with the very powerful EZ servos from the development kit by redesigning the neck mechanism. My next hurdle is the LED matrix. If I can get DotStars to work directly with the EZB then I can cut my LED Magician out of the equation. Obviously the Pixel Blaster will work with Neo Pixels and that would be fine, just not sure when that will be released.

I'm going to order both DotStars and Neos this week to play around.

Any availability updates?