Quote:
|
Originally Posted by whytheheckme
I think that a PBASIC controller might work without an operator interface because you are using the data from the dashboard port AS an operator interface. You can use the SERIN command to assign each byte to a variable. You could then have a simple IF/THEN statement to check which packet it is, and then send bytes to an encoder to send a 16 bit binary number out of the 16 I/O ports. From the I/O ports, you could hook a CPLD to transate the encoded nibble into 7seg displays and the likes. Do you see any major flaws in my plan?
Thank you,
Jacob Komar
|
Unfortunately the "I/O" ports on the pbasic rc are not actually IO. They are input only.
. The only outputs available are the serial port itself, relay outputs and PWM outputs. The relay and pwm outputs are proxied through the master processor and are only enabled if the RC is linked to a real OI. Also, just sending the data from the dashboard port to the serial port on the pbasic RC would not work
If you have one of the PIC based edu-RCs, they have general purpose IO, a serial port and don't require an OI at all. I think one of those would be a better option than a pbasic rc (although the pbasic RC would be alot easier to program).
Just to be clear, i am talking about this one:
http://www.ifirobotics.com/edu-rc.shtml