Subject:
|
documentation on bt / nxc
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Thu, 31 May 2007 06:27:57 GMT
|
Viewed:
|
22532 times
|
| |
|
|
I have two bots set up some meaningful ack and nack conversation. However,
when one bot/slave lost connection, e.g. terminated abruptly, the sender
(master) does not notice that it indeed lost it. The
ReceiveRemoteNumber(INBOX, true, ack) does not seem to update the ack, but
left the ack with the previous (good) value instead. Remedy?
Is there a more complete documentation, as far as the function specification
for all BT calls. Those in the guide and tutorial do not really provide
enough information in order for me to build a more robust conversation
between the bots. For example, if one bot terminates abruptly, what can I
check? I looked at val = BluetoothStatus(conn) but there is no detailed
spec for this
Suggestion?
--
MIME ATTACHMENTS DISCARDED:
1. Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Length: 3261
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in NXT programmable brick
|
|
|
|
|
|
