View Single Post
  #6   Spotlight this post!  
Unread 22-08-2005, 17:05
Rickertsen2 Rickertsen2 is offline
Umm Errr...
None #1139 (Chamblee Gear Grinders)
Team Role: Alumni
 
Join Date: Dec 2002
Rookie Year: 2002
Location: ATL
Posts: 1,421
Rickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant futureRickertsen2 has a brilliant future
Send a message via AIM to Rickertsen2 Send a message via Yahoo to Rickertsen2
Re: FRC hardware design

Quote:
Originally Posted by Gdeaver
The other thing is the I2c and SPi port are not available for our use.
Would you rather both serial ports or the I2C/SPi? Personally i find 2 serial ports alot more useful.

Quote:
Originally Posted by Gdeaver
Wouldn't the hardware software model be easier if the FRC had one main processor and a buss (rs485,can,rs232, etc.) There are 2 async. ports on the current processor. One port could be used for the programming and tether. The other would be for the coproc buss. why.
Well, technically speaking it wouldn't be that hard to do all of the PWMs from one processor. The main reason for having two procs is that the user processor is designed as a "sandbox" so that no matter how hard you try, there is no way to prevent the E-stop functionality from working, the team color lights from behaving oddly etc. With two procs, all the safety critical tasks are managed by the master processor and out of the programmer's control.
__________________
1139 Alumni