Astronouth7303
07-07-2004, 15:47
Several times I have proposed using the OI/RC as the control input. Here's my write up on it.
There are 2 ways to do this: use the dashboard port or write a program for the RC.
Dashboard
Use the OI (with or w/o RC) as 4 game ports. you hook up the original controls & the dashboard and you're all set!
PROS:
Lots of game ports.
original controls work
CONS:
May not work w/o RC
Not everyone has an OI
Not everyone has an RS-232 port
RC
You load a program to the RC and hook up the prog port to your PC. You turn it on and it should work fine!
PROS:
Wireless!
almost garenteed to work
Can be made to work with previous years
CONS:
May require the big batt (see below)
Not everyone has an OI/RC
Not everyone has an RS-232 port
POWER
There are a couple of things we could do for power of the RC/OI:
Use the original equipment (safest, heaviest?)
Make an AC adaptor for the RC (most cords)
Make custom battery backs (need to replace batteries)
I guess that is more of an user problem, not our problem.
I've attached a version of the code for the RC. (79.5 KB)
There are 2 ways to do this: use the dashboard port or write a program for the RC.
Dashboard
Use the OI (with or w/o RC) as 4 game ports. you hook up the original controls & the dashboard and you're all set!
PROS:
Lots of game ports.
original controls work
CONS:
May not work w/o RC
Not everyone has an OI
Not everyone has an RS-232 port
RC
You load a program to the RC and hook up the prog port to your PC. You turn it on and it should work fine!
PROS:
Wireless!
almost garenteed to work
Can be made to work with previous years
CONS:
May require the big batt (see below)
Not everyone has an OI/RC
Not everyone has an RS-232 port
POWER
There are a couple of things we could do for power of the RC/OI:
Use the original equipment (safest, heaviest?)
Make an AC adaptor for the RC (most cords)
Make custom battery backs (need to replace batteries)
I guess that is more of an user problem, not our problem.
I've attached a version of the code for the RC. (79.5 KB)