Welcome to Synthiam!

The easiest way to program the most powerful robots. Use technologies by leading industry experts. ARC is a free-to-use robot programming software that makes servo automation, computer vision, autonomous navigation, and artificial intelligence easy.

Get Started
Asked — Edited


I was wondering that it was possible to connect an neopixel ring(16) directly to the ez b4? If so, where do i connect the com port to ? tnx


Upgrade to ARC Pro

Unleash your creativity with the power of easy robot programming using Synthiam ARC Pro

AI Support Bot
Related Content
Ah, nice. Your using the Auto Position control for the freakout. Did you have to play with the delay and steps to get the wave right?
I increased the steps but left the delay alone. I also left the speed at -1 for the fastest travel. Beginner's luck, I guess. lol
-1 means "use last speed specified"

so if you use -1 everywhere, unless the speed will actually be 0 because -1 means don't change the speed.
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!


@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:

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


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.
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?
Good question - it should be in the store any day. I haven't heard much - i'll find out
Sorry to say there's still development delays in these bots. I was under the impression the components were completed a few months ago, but i received word today that they're still under development. This includes the neo pixel blaster, the new ultrasonic sensor, and the 8x8 display.

Due to this new information that they're not complete, I do not have an expected delivery date for you - apologies.
That's disappointing. Does this also reflect the /2 and the iotiny? Or just the items you listed above?
I understand. I don't have confidence in the timelines I've received at the moment, so I'm unable to answer that question.

I will get an answer for you soon
Dang. I hate waiting.
I understand and the feeling is mutual. I will get involved and get a better answer for you.