Quote:
|
Originally Posted by Mike Copioli
The O/I has 4 analog channels/port. We use the extra two analog channels as digital when they are not used for analog.
BTW
Congrats on your recent TV appearance.
|
Yes, you are correct. I have really been out of things too long.
As to Mode2, where you send the 12 buttons. Do you send them via the analog channels, where different ranges imply different button combinations for example
0-15: 0000 0000 0000
16-31: 0000 0000 0001
32-47: 0000 0000 0010
48-63: 0000 0000 0011
etc.
If this is true then you don't use the switch inputs or the LED outputs.
If this is correct, can I propose 2 more modes?
mode 3:
LED outputs used by the RC to multiplex between mode1 and mode2
mode 4:
every other data packet switch between mode1 data & mode2 data with the switch inputs used to tell the RC which type of data to expect*
Finally, you don't discuss the POV data. The POV button is a very nice way to drive robots in many cases. From a Windows application, the data is returned as 0, 45, 90, 135, 180, 225, 270, 315 but as a practical matter, the POV data is really just 4 more switch inputs that are mapped to these 8 pionts of the compass. Any chance you can map these 4 switches to give access to that data too**?
Think about it.
Joe J.
*This may run into problems with aliasing since you can't sync with the IO packet sending. perhaps it would be better to send 2 packets in mode1 and 2 in mode2 or maybe even randomly switching, within limits. Also, there is another possible problem with this if the OI does not synchronize the reading of the OI switches with the reading of the analog ports, but the ability to have all the switches and both X-Y data on the thumb would be great.
**note that if you can use 16 bits per range on the analog inputs, then you have room for 16 swithches with a 255 bit resolution on the ADC on the OI -- I am not sure but I think that the ADC on the OI is still just 8 bits. It seems feasible.