I have to admit, I am a novice with C-like programs. I have been studying the Bluetooth sample programs looking for a way to communicate with more than one other NXT, but I am not having much luck.

Does anyone have any pointers or better yet, some sample code that I can use to help me along?

ROBOTC currently only supports two forms of BT communication.

PC via BT to the NXT.
NXT via BT to another NXT.

If you explain exactly what you would like to do, I could help you out with some sample programs/code.

There are currently some samples in the ROBOTC for Mindstorms 1.10 build that illustrate the bluetooth communication. There's an entire folders of samples that should get you started

I am doing pretty simple stuff. As with with NXT-G, I was going to use one NXT as a master and the rest as slaves. I want to send simple values back and forth and store them in a variable on the master.

My project is a series of Gantry robots that all ride on the same track. I want section out the length of track into 10 or so sections. The master would maintain a log of which sectors are occupied and which are open. The master would stop the slaves from hitting each other.

If ROBOTC is restricted right now to one on one communication, I am going to have to come up with an inovative way to communicate with all NXTs

I have looked thoroughly at the BT sample code, but some of the undocumented stuff keeps throwing me. I have sent that code to two NXTs but I have had no success as of yet.

Any help would be appreciated.

Setup:
- one master has connections to all 3 slaves, named s1, s2, s3 at slot id 1, 2, and 3 respectively.

What works:
- the master sends a single byte ONLY to s1 via id 1. It works.

What does not work:
- the master sends a message ONLY to s2 via id 2. But, s2 did not get any message.
- then, I manually disconnect s1 from master. Run the same program, s2 immediately is able to get messages from master.
- note that s3 is still connected thru the manual setup.
- This tells me that only the slave at the 1st queue can get message. Is this an expected behavior?

Does anyone have suggestion how to resolve this issue?

That's not a good way, but if time is not a problem, you could do this:

1- Connect S1.
2- SEND
3- Disconnect S1.

4- Connect S2.
5- SEND
6- Disconnect S2.

7- Connect S3.
8- SEND
9- Disconnect S3.

10 - Go back to 1...

hmmm.... that's what I'm afraid of ... .must disconnect before you send.

btConnect (port, name) has to work first. (assuming the port = queue id)

I tested it. It kept returning FILENOTFOUND...

btConnect works fine here...

I am doing some work with BT, so when i finnish it, i could post it here.

work ok now after I removed 1.1 and downloaded the 1.40 RC instead.

Still...this bluetooth communication works quite kludge! Once in a while, it will go into this funny state that the only way to get it to work again is to manually resetting everyone!