Using an FRC with the RCX?

[Ryan M.]

That'd probably work. It would be interesting, you could say, have the RCX in charge of controlling drive motors, leaving the RC free to determine where you want to go, etc. I have a Mindstorms set (plus all of the expansions (a few of them twice )), so I might find this and interesting thing to look into.

--EDIT--
Oh, yeah. NQC is good, but BrickOS (former LegOS) is better. BrickOS is also C/C++ programming, but everything is precompiled, not interpruted like with NQC and the default LEGo firmware.

[Astronouth7303]

Plus, if you have an RCX v1, there is a 9-volt AC adaptor plug in the back (made for the train adaptors). So, connect the 12v Exide to a 12vdc-9vdc transformer, hook that up to the RCX, and you don't need to use 6 AAs!

Anyway, The connecting cable won't be standard: the tower is a Male with just enough space for the cable that came with the kit (No screws). The FRC prog is female. Both the FRC prog and the LEGO IR Tower (LIRT) are made to connect to a computer, so there are going to be problems if you just connect them directly. (Some good info on RS-232 can be found here.)
Using the jargon, we are trying to connect 2 DCE devices. Unfortunately, I only have pins for DTEs which is (DB9):

DTE
Pin   Purpose
 0  - Gnd (Shell)
 1  < DCD (Data Carrier Detect)
 2  < Rx
 3  > Tx
 4  > DTR (Data Terminal Ready)
 5  - Gnd (signal Ground)
 6  < DSR (Data Send Ready)
 7  > RTS (Request To Send)
 8  < CTS (Clear To Send)
 9  < RI (Ring Indicator)
    ^Direction (< = DCE to DTE, > = DTE to DCE, - = None)

So, to connect DCE to DCE (think of the FRC as the DTE):

FRC LIRT
Gnd Gnd
 Tx Rx
 Rx Tx
DSR DTR
DTR DSR

I'm not sure about the rest of it (RI, DCD, RTS, CTS). The problem is that there are 3 lines for DTE>DCE but there are 5 for DCE>DTE. And I don't want to fry my FRC or LIRT. Don't forget, the labels are relative to the DTE. If someone figures it out, tell us!
(The standard is RS-232.)

[Ryan M.]

Originally Posted by Astronouth7303

Plus, if you have an RCX v1, there is a 9-volt AC adaptor plug in the back (made for the train adaptors).

I want to know why they got rid of it on v1.5 and v2.0.

I'm going to look up some info on the RC to computer protocol.

[Astronouth7303]

Got it!
Thank you B&B Electronics!

FRC   LIRT
Gnd - Gnd
 Tx < Rx
 Rx > Tx
DTR < DSR
DSR > DTR
RTS < CTS
CTS > RTS
DCD X DCD
 RI X RI

Don't connect DCD or RI to anything.
The pins are as follows (DB9):

Shell Shell (optional)
    5 5
    3 2
    2 3
    4 6
    6 4
    7 8
    8 7

1 and 9 don't connect to anything.

So if anyone fries something doing this, please tell us before we fry something!

[Ryan M.]

Originally Posted by Astronouth7303

So if anyone fries something doing this, please tell us before we fry something!

LOL!

You'll have to wait until tomorrow for the info. Sorry.

[Grommit]

Two questions:

1) What kind of hardware would I need on the receiving end to make this work?

2) Has anyone tried to accomplish this successfully?

Thanks, I would have never thought of trying something like this!

[Ryan M.]

Originally Posted by Grommit

Two questions:

1) What kind of hardware would I need on the receiving end to make this work?

For the RC, you need a cable to attach to the LEGO IR tower. For the RCX, nothing. It has it's own built in IR.

Originally Posted by Grommit

2) Has anyone tried to accomplish this successfully?

I don't know of anyone.

[Ryan M.]

Here are a few links:

Packet description: (includes example of sending IR message)
http://graphics.stanford.edu/~kekoa/rcx/protocol.html
From this website, I think that sending:
55 ff 00 f7 08 M ~M C ~C
Where C is the checksum. Sends the messageM. One thing I'm confused on is the checksum. It doesn't seem to work the way I read it in his description. Even trying to figure the checksum using his example I didn't come up with the same thing he did. It may be I just don't understand it. If you kow, tell me how to compute it.

Some more stuff on the packets: (not as good)
http://graphics.stanford.edu/~kekoa/rcx/#Protocol

Do you need to know how to send that out, or do you already have that figured out?

--EDIT--
Here is a site with examples of using it in C++. http://www.generation5.org/content/2001/rob08.asp.
Reading that, it's a great site.

[Astronouth7303]

Originally Posted by Texan

Here are a few links:

Packet description: (includes example of sending IR message)
http://graphics.stanford.edu/~kekoa/rcx/protocol.html
From this website, I think that sending:
55 ff 00 f7 08 M ~M C ~C
Where C is the checksum. Sends the messageM. One thing I'm confused on is the checksum. It doesn't seem to work the way I read it in his description. Even trying to figure the checksum using his example I didn't come up with the same thing he did. It may be I just don't understand it. If you kow, tell me how to compute it.

Some more stuff on the packets: (not as good)
http://graphics.stanford.edu/~kekoa/rcx/#Protocol

Do you need to know how to send that out, or do you already have that figured out?

--EDIT--
Here is a site with examples of using it in C++. http://www.generation5.org/content/2001/rob08.asp.
Reading that, it's a great site.

The example from LUGNET was made for MSCOMM and VB. I just took the array and wrote the functions for the controller.

A message packet is only one additional info section.
Header (3 bytes)
OpCode (2)
Message (Info, 2)
Checksum (2)

The OpCode for Message is 0xF7. It has one argument: the message value. Every data byte is followed by it's not. So you get:
Header = 55FF00
OpCode = F708
Message = M ~M
CheckSum = (F7+M) & FF

I think we're finally getting it!

The second link is extremely helpful. And I'm glad to know about the Null-modem cable thing: The LIRT is CTE, not a CSE (it is a male, like your computer), so maybe a standard cable works!

[Ryan M.]

You said the prog port earlier, but how do we access that? Or, rather, can we get enough control to do what we want? You can send text, but I haven't studied the printf() access of the port. Maybe that port will work or maybe something else is necessary. Correct me if you know the way.

[Astronouth7303]

Originally Posted by Texan

You said the prog port earlier, but how do we access that? Or, rather, can we get enough control to do what we want? You can send text, but I haven't studied the printf() access of the port. Maybe that port will work or maybe something else is necessary. Correct me if you know the way.

Ok. The text is transmitted as bytes (I assumed ASCII, but I'm not sure). So basically, you replace the text with bytes. A string is an array of bytes terminated by a null characcter (0x00).

I looked in printf_lib.c I traced the flow of execution from printf(), and ended up at Write_Byte_To_Uart(). Which is:

/*********************************************************
* SUBROUTINE NAME: Write_Byte_To_Uart
* PURPOSE:       Writes a byte to the UART.
*     Argument       Type           IO   Description
*     --------       -----------    --   -----------
*         data       int            I    data to transmit to the UART
* RETURNS:       void
*********************************************************/

static void Write_Byte_To_Uart(int data)
{
  TXREG = data;  /* a carriage return */
  Wait4TXEmpty();
}

I simplified it to the macro:

#define SendByte(Byte) {TXREG = Byte; Wait4TXEmpty();}

(And I don't actually know how to write macros!)

You call this repeatedly to write the whole packet.

Of course, You can't recieve: the LIRT only remains active for 3 seconds after you transmit something.
Also: this whole setup is unusual, so if it doesn't work, don't worry. We just may end up buying a pair of UART DTEs and making a double box!

[Ryan M.]

Originally Posted by Astronouth7303

I simplified it to the macro:

#define SendByte(Byte) {TXREG = Byte; Wait4TXEmpty();}

(And I don't actually know how to write macros!)

You call this repeatedly to write the whole packet.

That's what I figured would work, but I wasn't sure. Don't do a lot of COMM port work.

And the macro looks fine.

[Astronouth7303]

Originally Posted by Grommit

Two questions:

1) What kind of hardware would I need on the receiving end to make this work?

LEGO's RCX. That's all (You may need the official firmware to get the message packets to work). At transmission, however, you need an old COM tower, not a new USB.

Originally Posted by Grommit

2) Has anyone tried to accomplish this successfully?

I don't think so. But it hasn't been very long. The hardest part would be the cable

Originally Posted by Grommit

Thanks, I would have never thought of trying something like this!

Neither would I until yesterday!