To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcxOpen lugnet.robotics.rcx in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / 2734
2733  |  2735
Subject: 
Re: RCX to RCX NQC
Newsgroups: 
lugnet.robotics.rcx
Date: 
Wed, 14 Sep 2005 21:07:23 GMT
Viewed: 
4215 times
  
On Wed, September 14, 2005 3:15 pm, Brian Davis wrote:
   How does the remote get around this? Or does it? It seems to imply that
commanding a pBrick with the computer IR link or a remote at the same time would

I'm pretty sure, both the remote, and the send message commands only have one
op-code, and are done differently from the rest.

Steve



Message has 1 Reply:
  RE: RCX to RCX NQC
 
The message "toggle" bit was a good concept that has very limited value in practical use. I guess the intent was to prevent unexpected behavior when a PC program attempts retransmission after a message failure. Suppose the failure condition was that (...) (19 years ago, 15-Sep-05, to lugnet.robotics.rcx)

Message is in Reply To:
  Re: RCX to RCX NQC
 
(...) Ahh, now I understand why it is called a "toggle bit" - I somehow misinterpreted this to mean a new command had the toggle bit set (to 1), and if the sending unit doesn't recieve a reply it should re-transmit the command with the toggle bit (...) (19 years ago, 14-Sep-05, to lugnet.robotics.rcx)

8 Messages in This Thread:



Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR