The ZomB has automatic instance protection
Renaming the DefaultDash.exe to Dashboard.exe and putting it in the C:\Program files\FRC Dashboard\ folder did the trick for us, you might want to move the first dashboard out, and then put the ZomB in.
As for the slowness, was it slow with updating the graphs/controls? (ie. push a button, wait a second, shows up) or just with mouse/keyboard feedback (ie. move mouse over button, wait one second, ui cues show up)
I have noticed the mouse/keyboard feedback lag increases in driver mode for both the ZomB and the DS by about 1 second every 3 hours, which needs a full reboot to cure. (I don't think it took you 3 hours, but you still might have this problem)
for the delay (on the robot side) if you are just testing, use Thread.Sleep(20) to get maximum throughput
Code:
while(istelop())//?
{
//calculate
zomB.Add("spk1",0);
//etc...
zomB.Send();
Thread.sleep(20);
}
otherwise, use a timer (pseudo code)
Code:
Timer t
t.start()
while telop
{
...
if t.Get()>=0.02
{
t.reset()
zomB.add(...)
zomB.send()
}
...
}
As for the camera, click the "reset camera" button and wait 2-5 seconds. If it does not show up after 10 seconds, click it again (make sure the camera the camera is initialized, ~10 seconds after the camera ring turns green)
(also make sure you have a camera instance in your code)
You say it worked with the dash.commit() line?
EDIT: BTW, have you seen the awesomeness of the taco yet? (its a -1 to 1 float value) (full documentation on its awesomeness:
http://firstforge.wpi.edu/sf/wiki/do...wiki/TacoMeter)