mlevings wrote:Just a quick pointer to keep in mind when sequencing for the ethernode....
1. Make sure you end every sequence with the pixels off on the last frame. The pixels will hold their last command when the sequence stops.
2. When building the show in Helix, place a 5 second pause between each sequence and after the last one. If you don't the ethernode won't have time to reset and will stop after the first sequence.
The Ether-Node firmware is still a little rough. These work arounds that mlevings provided are necessary to get around some of these rough spots. I have a couple of ideas for how to create an All Off method that will run when the sequence ends and turn all of the pixels off. This is how I handle the situation in the Helix Main Board firmware.
I also plan to optimize the firmware so that it resets faster. This should eliminate the need to add the pause between the sequences.
I updated the Helix Ether-Node Firmware to fix an issue that was brought to my attention. I also updated the new Helix Network Supervisor application to fix an issue with checking for updated firmware.
Please update the new Helix Network Supervisor application by opening it and accepting the update (again if you aren't using the new Helix Ether-Node board then you don't need the updated HNS yet). Then go to the Tools tab and press the Check for Update button in the Firmware Update panel.
blantrip, are you trying to use a sequence created in vixen 3? That looks like the error that I was getting when using Vixen 3 sequences.
Yes, I was giving it a try. Seeing if I had any better luck than you had. Looks like I may just have to bite the bullet and go back to Vixen 2.x unless Greg has an answer.
