Not sure what you meant your slave controller not reading sensors though . As far as reading sensors, it works identically the same way no matter it is a master controller or slave. I guess you meant bi-directional transfer? i.e. transferring data from the slave controller back to master ? It should work, I have a sample too, but it was written way back in 2009 or so. With the new implementation, I'll have to test that out again. However, is it what you need ?

]]>2014-10-08T12:35:32-04:002014-10-08T12:35:32-04:00http://robotc.net/forums/viewtopic.php?t=9510&p=31650#p31650I am looking for instructions on connecting a XBEE PRO radio to a VEX PIC Microcontroller (old model). This is to enable communication between an arduino mega and vex.ThanksRam

]]>2014-01-15T17:43:37-04:002014-01-15T17:43:37-04:00http://robotc.net/forums/viewtopic.php?t=7627&p=28267#p28267I just wanted to do it just via rs485 (S4-S4) or preferably via BT as one won't waste another precious NXT sensor port - or both all at once, connecting 1 master to 1 BT slave and to 1 other rs485 slave.

I actually thought that after 7 years of NXT life there should be easy and powerful communication APIs providing message control protocols like. e.g.,

An underlying (already implemented and integrated) RobotC network protocoll should make it MT-safe and should protect from data collision, data loss, and data corruption. It could be something like the bitbus protocoll which is implemented by Java/LeJos, but this of course requires RobotC firmware changes.

for using BT instead of rs485, just the data transmission mode and the slaveID will have to be exchanged in the function call:

]]>2014-01-15T16:57:05-04:002014-01-15T16:57:05-04:00http://robotc.net/forums/viewtopic.php?t=7627&p=28265#p28265ROBOTC supports the RS-485 method of communicating. This is what we use for our XBee Projects (http://www.robotc.net/firewiki). That method uses two wireless Xbee Radio's using Dexter Industries's "NXTBee Adapter" (cool sidebar: John at Dexter Industries actually designed the NXTBee for us originally for a project we were doing!)

One of the cool thing you can do though is replace your Xbee radios and just throw a normal NXT sensor cable between Sensor Port 4 on a pair of NXTs and do the same serial communication between those. Using that and your own custom serial protocol, you can easily make a program that will read/control sensors and motors on another brick. We have some examples on how to get started and an easy to use Xbee/RS485 library included with ROBOTC (just add #include "XbeeTools.h" to your program) to access the commands covered in the "firewiki".

It's no fun if we give you guys all of the code needed for your projects - plus we have other important things to do... like finish working on EV3

]]>2014-01-15T08:32:24-04:002014-01-15T08:32:24-04:00http://robotc.net/forums/viewtopic.php?t=7627&p=28262#p28262Statistics: Posted by Ford Prefect — Wed Jan 15, 2014 8:32 am
]]>2014-01-09T13:12:08-04:002014-01-09T13:12:08-04:00http://robotc.net/forums/viewtopic.php?t=7627&p=28168#p28168it would be really great if you could provide us with a sample program for a quick-as-possible-polling of all the slave's sensors (perpetually or on demand, including slave encoder readings) and commanding all the slave's motors (intermediately, on demand) by the master NXT... (via rs485 or via BT)

It should make all slave I/Os accessable just as if they were local on the master, sort of mimic "daisy chaining" which is currently provided by the EV3 Lego software for up to 4 EV3s