Skip to main content

BlueTooth: playing with blocks

So you’ve gotten two NXTs connected via BT, and sent a couple of files across for no apparent reason (although I’ll bet such filesharing becomes a fun pastime at FLL events this year; everybody bring your favorite sound file to share ;-). How do you use this within NXT-G? Once connected, NXTs can send BT messages to each other using the Send Message and Receive Message blocks. And unlike IR messages with the RCX, limited to a single number, these can numbers, Boolean values, even text strings (yes, you can turn your NXT into a really bulky instant messaging system ;-).

The tricky part is those connections – remember how the master and slave NXTs showed that they labeled the connection with different numbers? Those are the “addresses” of the NXTs. But each address can have multiple mailboxes as well, making for yet another way of sorting out all the BT mail that ends up flying around. It’s similar to how mail gets to an apartment building: all of it gets sent to the same building (which NXT, identified by a connection number), but you can also tag each message as headed for a particular apartment (the mailbox number).

If you take a close look at the Send Message block, you’ll see you can tell it where you’d like the message to go: what connection to send it out on, and what mailbox in the receiving NXT to pop it into. But where is that information on the Receive Message block? Here there is no connection to select, so how do I tell the Receive Message block where to get messages from? The answer is you don’t: all messages sent to a single NXT are accessed through the Receive Message block, just like all your mail is sent to your address (even if some of it started in Austin, TX, while another was sent from Billund in Denmark). In short, NXT-G BT messages have no return address built into them (although there are ways around this… those mailboxes again).

Confused yet? Here’s a simple set of programs for the two connected NXTs. One (“DiceMaster”), running on the “master” NXT just generates a random number to send to the other one, and then waits for a return message from the second NXT telling it if the sum of all the numbers has exceeded some preset limit. The other program (“DiceSlave”) listens for a number to be sent to it, and then adds it to the total and checks to see if the limit has been exceeded, sending a message back to the master to let it know the result. Simple, but it does show how messages are sent both from the master to the slave, as well as from the slave back to the master. Note that a slave NXT can only send a message back to the master, so for a slave there is really only one outgoing connection: connection #0. And of course all the messages coming into the slave come only from the master as well, which is listed in the slave’s Connection menu as on connection #0. So I tend to think of this in the terms I used in the program comments: slaves both send and receive all messages over connection #0, while from the master’s point of view, it can send messages out to any one of three addresses (#1, #2, or #3), but again receives all incoming messages along a single “line”, which I still think of as a “connection #0”.


Now, for any of you with two or more NXTs, experiment! And let us know what new quirks or features you uncover.

--
Brian Davis

Popular posts from this blog

Celebrating MINDSTORMS with a Remix - Part 2

The ROBOTMAK3RS continued their celebration of the 25th Anniversary of MINDSTORMS through these summer and fall remix projects. Each ROBOTMAK3R was tasked with selecting one LEGO set of their choice and combining it with a MINDSTORMS set. Below are the five amazing models they came up with. Remote controlled material handle r by Jozua van Ravenhorst (aka Mr Jo) This remix combines the LEGO Technic Material Handler (42144) with MINDSTORMS EV3 (31313) It uses the power of pneumatic cylinders to move objects around. By using a bluetooth remote control, very precise movements can be made with this model. Touch sensors in the base chassis prevent the turret twisting the cables that go through the turntable to much. The program has several protections to prevent over pressurizing the system for each of the 3 individual pumps and valves that control the 2 booms and claws. The real version of this machine is mostly used in waste material sites to bring the material to machines that sort and

MINDSTORMS Retires!

2023 is the 25th Anniversary of the MINDSTORMS brand. For 25 years, MINDSTORMS has educated and inspired a generation of robot builders, both children and adults. Unfortunately, the LEGO Group decided to end the line on December 2022. Many ROBOTMAK3RS have been passionately involved with the development of MINDSTORMS through the MUP and MCP programs. Even with the newest Robot Inventor line, several ROBOTMAK3RS were invited to submit additional bonus models that were included in the official app. Regardless of the retirement of a major LEGO robotics product line, ROBOTMAK3RS continue to MAKE-SHARE-INSPIRE using all LEGO robotics platforms available to us. Here is the official statement from LEGO. Since its launch in September 1998, LEGO MINDSTORMS has been one of the core ‘Build & Code’ experiences in the company’s portfolio, carrying with it significant brand equity and becoming a stand-out experience for the early days of consumer robotics and leading to current Build & Code

Celebrating 25 Years of MINDSTORMS

In celebration of the 25th Anniversary of MINDSTORMS, we take a trip through history. Please also visit ROBOTMAK3RS Community every week as we highlight different projects all through 2023 in celebration of the anniversary. Some of the early history is based on the content shared by  Coder Shah  in our  MINDSTORMS EV3 Community Group . Some of the text and links may have been edited from his original posts for consistency and clarity.  1984 - Kjeld Kirk Kristiansen watched a TV program called "Talking Turtle," where MIT professor Seymour Papert demonstrated how children could control robot "turtles" using LOGO, a programming language he developed. 1988 - The collaboration between MIT and LEGO resulted in LEGO TC Logo in 1988, which allowed students to control LEGO models using computer commands. The video shows Papert demonstrating TC Logo. 1990 - LEGO TC Logo was hampered since the robots you built had to be tethered to a personal computer. LEGO and MIT