Using the edu--erm, Robovation for more info?

[Billfred]

Alright, someone correct me if this has been proven to be incorrect or bunk or what have you.

The LED outputs on the OI are +5 volts.

The digital inputs on the Robovation (I'm forcing myself to say that) accept 0 to 5 volts.

So, all you people who know more than I do, would it be feasible to use the LED outputs as Robovation inputs, letting it do some more interesting things and display them? Worth the effort?

[seanwitte]

Originally Posted by Billfred

Alright, someone correct me if this has been proven to be incorrect or bunk or what have you.

The LED outputs on the OI are +5 volts.

The digital inputs on the Robovation (I'm forcing myself to say that) accept 0 to 5 volts.

So, all you people who know more than I do, would it be feasible to use the LED outputs as Robovation inputs, letting it do some more interesting things and display them? Worth the effort?

Yes, but a more robust solution would be to use the TTL or programming port on the mini controller to decode the dashboard output. Using the mini controller to decode the 8 LEDs won't buy you much because it would only give you 8 output lines to drive other LEDs. If you use the dashboard port you still have all 16, plus the PWM outputs which could drive a servo as an analog gauge.

[Astronouth7303]

Maybe, but why? it will only give you 8 bits of data.

The dashboard would be much better. You take a DCE-DCE Null-modem cable (M-M) and connect them. Set the jumper to RC and read the user bytes/user command.

I can give you a better idea of how to do this in code, if you want.

[Billfred]

DCE to DCE? Eh???

And I see the problem with the LED outs...and reading the IFI documentation on the TTL port left me with even more questions than answers. Can anyone give some more information on this?

[Astronouth7303]

DCE is short for Data Communication Equipment (a throw-back to the days when RS-232 was used for modems). Basically, anything with a female port is DCE. (Conversely, DTE is Data Terminal Equipment. It's anything with a male port). so a M-M null-modem cable would connect 2 DCEs. (it has a male port on each end).

(ps- I am not making this up. I am repeating terminology)

And skip the TTL port. You'd just have to make hardware for it.

[Billfred]

Tis true--but is there a way to listen on the programming port for stuff like this? I thought it was pretty well stuck with programming stuff, hence the TTL port. But feel free to prove me wrong.

[seanwitte]

Its actually pretty easy to read data from the programming port. When new data is received the flag PIR1bits.RC1IF will go high. The byte that was received will be in RCREG1.

if (PIR1bits.RC1IF == 1)
{
	//grab the data
	data = RCREG1;
}

The easiest way to hook it up to the OI would be to get a null modem adapter or cable from a computer store. I'm partial to the adapter since its harder to get it confused with a regular cable.

[Astronouth7303]

Originally Posted by seanwitte

The easiest way to hook it up to the OI would be to get a null modem adapter or cable from a computer store. I'm partial to the adapter since its harder to get it confused with a regular cable.

It's impossible to get them confused. a regular cable is Male to Female (M-F, F-M). A null-modem is M-M or F-F.

They're fairly easy to make, too. Try BeyondLogic.org for plans/details.

[seanwitte]

Originally Posted by Astronouth7303

It's impossible to get them confused. a regular cable is Male to Female (M-F, F-M). A null-modem is M-M or F-F.

They're fairly easy to make, too. Try BeyondLogic.org for plans/details.

I guess when you're on your way out the door and you grab the wrong beige cable out of the drawer on your way you only do it once. The amount of money you would spend on wire, connectors, and hoods is less than a null-modem gender changer. http://www.radioshack.com/product.as...uct%5Fid=26-26