[OCCRA]: OCCRA OCT-NE 10/14/09 Basic VEX Workshop PDF

[apalrd]

I followed the directions, and have had no problems at all with VEXnet. It runs just fine. It is the job of the field controller to start autonomous, thus there is no need for a start switch. Even with the crystals, the code should not need a start switch. The whole latching switch thing is why there are tutorials on programming for VEX. At this point, I can pretty much only capable of running with VEXnet without major code modification. Actually, the biggest software problem that I have had so far is that my Vista laptop dosen't like the Prolific USB driver from VEX, so I am using an old laptop with IFI loader to upload the hex files. Why does the position of the power switch matter? The stop switch does make sense; our 2008 FRC robot took off down the hall and turned left because someone hit the autononmous switch (which is under a missile-switch style cover) We still have this problem where we ran out of switches (We had 2 bumper and 2 limit switches, we used both the bumpers on our bumpers and the limit to detect a ball in the robot, leaving one limit switch for a stop switch). Can I just use one of the bumpers to start, then remove its starting duty?

//wait out the non-starting period
while(rc_dig_in11)
       ;

If there are VEXnet problems and crystals are used, will we be required to use crystals or can we still use VEXnet? We can pretty much only run on VEXnet.

iwanttodunk: The lights blink alot when starting up. They will start to blink faster when they find another VEXnet controller, and will turn green when they are linked. Just wait a few seconds. Have you updated the master code and your software? I love all of the new features the VEXnet has to offer, and am glad that we are using it this year. I hope that VEXnet is extended to include computer driver support. that would make me very happy.