With a standard valve setup, the high velocity can't really be blamed on the T-board. There's really nothing the board or its programming can do to increase the velocity unless you timed your old board wrong and caused some form of blowback or such that lowered your velocity. I posted early on some things you can check and do in another one of your threads regarding the SON and CDEL times that you really should try before you go any further.
There is this thread here that has a lot of information about our testing of the T-board. We're awaiting new firmware before we will continue our testing. The issues with the eyes that you mentioned are covered there. Pretty much the only mode of fire that works "correctly" is semi.
http://www.halfcocker.com/modules.php?name=Forums&file=viewtopic&t=338I can't really remember exactly what my settings were, but they were basically along these lines. I use a MQ-based delrin turtle body.
3.0ms SON
9ms CDEL
25ms CON (minimum - problem with the board is that unlike the eBlade boards, the T-board uses the CON time even when eye functionality is enabled)
for CTO - this is really personal preference, I think I set it to something over 100
20ms COFF
I'm pretty sure I set my eye delay to 2 or 3ms and the ball detection to 5ms.
Good luck and read a good guide on timing the eBlade if you aren't 100% familiar with the process.
