This is very disappointing, I have tried to use LSP for several years with little or no success and paid for all the upgrades. I'm really sorry I wasted my money. In my humble opinion LSP is going to be DOA and LSP should stop selling licenses until and unless they have a proven product!
Don't know if something like this is available to you in NZ, Not directly DMX controllable but it can be triggered via a relay and the speed is adjustable. Also the prop motors they sell have pretty good torque.
http://www.frightprops.com/electric-motors-1/controllers/picovolt-0975.html
Glad I could help, looks like you were getting two strings of conflicting DMX signals sent to your strips . I also noticed in your video that one strip of lights acted correctly during the test pattern. You might want to check that you have that stings' Universe set correctly in LOR, It may be...
The only reason I asked was that I have seen this exact same behavior when running the test pattern while a sequence was running. With the controllers test pattern running, does anything change if you unplug the network cable form the controller? Also, how are you running the Test Pattern, via...
Do you have a sequence running while you are using the test pattern? The first flash in the video makes me think so, you can only have one running at at time (sequence or test pattern).
Current is 2.9 which includes strobe functionality. Look 5 Posts below yours in the Forum.
http://auschristmaslighting.com/forums/index.php/topic,4972.0.html
I'm running Technicolor Pixels on P2 and P12S controllers at 3200 Kbps and I'm not having any problems at all. I got that number form the UBL Procedures Document included with the 3.2 Firmware Update.
Glad you got it worked out. Seems you're not the only one who received mislabeled power supplies.
http://auschristmaslighting.com/forums/index.php/topic,4982.15.html
Which firmware version are you using? According to the UBL Procedures document distributed with firmware version 3.2 "As of v3.2 the keep-alives are not activated. We will fix that in v3.3 after v3.2 has been wrung out in the field". Did I miss a firmware update?