Subject:
|
Re: NQC 2.1 b2 in beta test
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 13 Jan 2000 02:42:34 GMT
|
Viewed:
|
1806 times
|
| |
|
|
In article <slrn87pa40.po6.mattdm@jadzia.bu.edu>, mattdm@mattdm.org wrote:
> Not that I'm complaining or anything :) but is the 'listen' feature I talked
> about a while ago in the plan for the future?
I remember discussing this briefly, but I don't think we ever came up with
a final "spec" for the feature. Here are the issues I forsee:
1) The IR tower times out. NQC should probably do something to keep it
alive - and that "something" should be as minimal as possible so as not to
clobber *too much* incoming data.
2) How should the receive data be formatted? Raw serial bytes? Raw
packet payload (strip out header, complements, and checksum)? Should it
actually walk into the packet and only show the RCX "messages"?
3) Does this really belong in NQC, or should it be a separate executable?
The NQC command line is getting a bit unwieldy due to everything I've
crammed into it.
Thoughts?
Dave
--
reply to: dbaum at enteract dot com
|
|
Message has 1 Reply:
 | | Re: NQC 2.1 b2 in beta test
|
| (...) Yes, this is why I'd like someone else to implement this. I just want to use it. *grin* (...) RCX messages is what I'm interested in. It might be reasonable to have several modes. (...) Good question. I don't think this feature is out of line (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | Re: NQC 2.1 b2 in beta test
|
| (...) Not that I'm complaining or anything :) but is the 'listen' feature I talked about a while ago in the plan for the future? I'll work on making Linux builds today if I have a chance. (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.nqc)
|
25 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
|
|
|
|
