[apalrd]

1.
How could code cause problems for the VEXnet? If the code encounters an error, and does not update the master by the time the master receives the next data packet (18.5ms), then the PGM STATUS light will turn red and the master will kill the user. As far as I can see, this does not cause any problems (I actually use this as a stop switch). It the VEXnet system can be killed by student programming error, then the system is not designed correctly.

2.
If the battery is low, the only reason for a problem is if the battery is low enough to cause the processor to reset. This *shouldnt* cause a problem for the VEXnet since you would only need a new battery and to reload the code. As far as I know, the VEXnet dosen't actually store any data except possibly to buffer it in RAM while transfering. Once again, if it can't handle a normal situation, then it is not designed well.

3. Hardware problems are reasonable. I understand that these are early models and may have a few bugs.

New VEX transmitter? I can't seem to find that on the VEX site... Seems like they still sell the 75mhz system and VEXnet upgrades, no new transmitters yet (although they have hinted on one to be released next year). Unless you mean they released a firmware upgrade on the VEXnet upgrades for the transmitter, I can see no difference... Although they did hint to the release of a new VEXnet transmitter that is more like a ps2 joystick, which will have VEXnet only operation. That will come after the Cortex microcontroller, which has not yet been released.



Could you possibly be thinking of the RC and not the RC Upgrade? I am talking about the RC Upgrade, not the RC itself. The RC works fine.