Subject:
|
Re: Brute Force Brick
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 11 Mar 2004 22:10:04 GMT
|
Viewed:
|
783 times
|
| |
|
|
In lugnet.robotics, Lamar wrote:
> IMHO, the serial I/O interface idea should be subplanted by a USB 1.0
> interface. As a programmer, I can see the oppurtunties that this would
> provide for additional controls above and beyound what is currently
> available.
A very well solution. I even think, it would be possible to interconnect
multiple BFBs in a communication line like that, the cable would
reduce UHF bandwith restrinctions. Such, that a cable connection
loads some of the communication load between BFBs interconnected by them.
+----------+ +---------------------+ +-------------+ +---------+
| BFB1 out +--->+ Expansion Unit BFB1 +--->+ in BFB2 out +--->+ EU BFB2 |
+----------+ +---------------------+ +-------------+ +---------+
The question is, how the Expansion Units could look like.
You can imagine fixed ports mounted on one expansion unit, assigned as
sensor input(s) or motor output(s). You can have two sensor inputs and one
motor output for instance, if you had three ports.
It would be more nice to have ports, that you can define from the software.
Simply assigning the function of a port, either sensor input or motor
output makes it a most flexible system. Regardless of the optimal number of
ports of an Expansion Unit.
Ever attached an oszilloscope to an RCX input? Then you know the 3 ms cycle
consisting of two phases: sensor read phase (approximatly 0.1 ms) and power
out phase (approximatly 2.9 ms).
Although it is imagined in the literture as bound to the port mode, this
3 ms cycle is independent of it. Meaning, it is allways there, after you
switch on the power of the RCX.
I suggest now, that the three inputs of the RCX are scanned in a 1 ms cycle.
Meaning every one millisecond another input is scanned. The Expansion Units
must go coincident with this.
(Nerver verified it)
Greetings
Ralph
|
|
Message has 2 Replies:
 | | Re: Brute Force Brick
|
| (...) I consider myself pretty well atuned to "what would be nice". In the process of actually designing and building prototypes which bear a resemblance to what might actually be reproducible as a product, there are certain limitations which apply. (...) (20 years ago, 12-Mar-04, to lugnet.robotics)
| | | Re: Brute Force Brick
|
| (...) Why? How many ports are needed? (either In or Out) What do you need to do that requires more than 10 inputs, or 5 outputs? I know in a perfect world, it would be really nice if John could fit a 1ghz processor with 80gb ram in a 4x4 brick. The (...) (20 years ago, 12-Mar-04, to lugnet.robotics)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
