In SX Microcontrollers, SX/B Compiler and SX-Key Tool, PJMonty wrote:

Dan,

Glad you liked it.  As for increasing your framerate, it sounds like you only need to increase it enough to let you hit musical beats.  4 or 8 frames per second should be sufficient resolution to let you hit your beats.

In my system, the software on the PC streams 8 channels of servo data at 24 FPS and feeds the servo controller hardware.  I also double buffer so that I'm playing back one section on animation while pre-loading the next.  This is important in my system since multiple devices are sharing the same RS-485 serial network, and I can't afford to have the animation have glitches or hiccups if data doesn't arrive in time.  

On your system, it sounds like you're pre-storing your animation in the EEPROM.  It also sounds like you only have discrete events (fire the cannon, etc), so smooth animation isn't the issue as much as sync.  In that case, I would use a fixed framerate (4, 8, 10 FPS) and store the data as the number of frames at that rate.  Store the data as two sequential bytes.  The first byte is the number of frames to wait, and the second number is treated as a binary representation of the trigger outputs.  
[code]
4   %00000000
8   %00000100
20  %00000000
6   %00000001
67  %10000001
5   %00000000
[/code]

IN this case, the first number is shown in decimal and says how many frames to wait.  The second number if shown in binary so you can more easily see the bits turn on and off.   Note that in the 4th event, we turn on bit, but another event triggers 67 frames later so we make sure that bit 3 is still turned on there as well.  finally, on the last event, we turn both triggers off.  You can also wait zero frames and have something trigger right away.

Thanks,
PeterM

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=180020#m180049

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2007 (http://www.dotNetBB.com)