Re: What happend to the sendMessageWithParm()-function?
This is my fault. Sorry. I didn't realize that anyone was using this capability in ROBOTC. It was originally added to provide Bluetooth messaging support for ROBOLAB which uses a subset of the ROBOTC firmware and could not be easily extended to the more powerful and robust messaging functionality found in ROBOTC.
The best "solution" is to revise your code to use the more robust "bluetooth functions mentioned below. I'm a little reluctant to re-add to ROBOTC because the implementation was less robust with the possibility of dropped messages through buffer overflows which is less likely than the solution described here.
The easiest way is to write a small function with sames parameters as "SendMessageWithParms" that simply fills a struct with your messages parms and then sends as a message on 'nQueuieID' 1. This is essentially what the missing message function did.
Similarly, on the read side, you cann "GetSize" to see if there is a message. If so, call "cCmdeMessageRead" to read the message into same struct declaration as for send. Wrap both of these in a new function that is called whenever you want to read.
If you want, I'll write a version of these and send to you. Please communicate directly via email to firstname.lastname@example.org
on this as it will get a faster response from me.
I'm surprised that you mentioned three NXTs. You must be doing the external connection management within your program? I assume single master and two slaves. And the slaves only need to talk to master. Is communication only master to slave. Or is there slave to master messages as well. [Did we already talk about this?]