Subject:
|
RE: AI, AI & AC (CM<->RCX)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Wed, 18 Oct 2000 09:14:31 GMT
|
Original-From:
|
Marco C. <MARCO@ihatespamSOPORCEL.PT>
|
Viewed:
|
728 times
|
| |
|
|
At 19:32 17-10-2000 +0200, Jon Kongsvold wrote:
> > Rama Hoetzlein wrote:
> I am also trying to make sort of a telegraph between the CyberMaster and the
> RCX, hoping to use the CM's radio connect to communicate even if the robot
> isn't pointed towards the IR tower. Any tips on making the green and yellow
> box talk, are appreciated. Should I use light sensors/lamps or a
> motor/touch sensor configuration? The light sensor/lamp idea might be
> faster, as the motor will need to use some "Morse signaling" to use a motor
> to press the other box' touch sensor and vice versa.
As Dean Husby said in a reply to your "Communication between the RCX and
the Cybermaster" thread, and as it has been discussed by me and others
already in older threads, it's pretty safe to connect directly the CM's OUT
to a RCX IN, and doing the reverse for bidirectional comms.
I don't own a RCX yet :( ...but, I tried to connect my CM's OUT to one of
it's IN, wrote a simple program and checked that it works ok, if you use
the OFF() and the FLOAT() commands it'll report back as a ON/OFF touch sensor.
I'm thinking of using the same technic one can use to read bar-codes mixed
with some feedback from the receiving machine to signal the "OK TO SEND /
BUSY" status. This is all theory for now. I'm hoping to buy a RCX (2.0?)
this Xmas, and then, try all this.
I'm also going to try and do something based on Jin Sato's VLL Library for
NQC. This way, I would work with a LEGO "standard" serial comms protocol,
and get some degree of compatibility with Scout, MicroScout and CodePilot.
Goto http://www.lugnet.com/robotics/ and try a search on the keywords "VLL"
or "CyberMaster".
One problem that I have to solve is the CyberMaster's lack of message support.
With the RCX you can always have a prog running and react to messages sent
through IR. But CyberMaster doesn't (AFAIK!). So, the only way I can do
PC->CM communication is by sending the actual p-codes, instead of 1 byte
message codes... and, I don't know how well it will work when sending
hard-wired VLL messages from CM to RCX that have to be composed at the PC
and not the CM :/
At least it's possible to have a program running in CM and the PC interfere
with CM's OUT/Motors but I don't know a way to interact with the program.
hmmm... maybe by setting variables... comm through a mem semaphore/flag
technic... must try this, dunno if I'm making any sense.
Please keep giving this list some feedback on your progress :) ...I'll do
the same, of course.
Marco C. (aka McViper)
_________________________________
Work mailto:mcviper@geocities.com
Home mailto:mcviper@clix.pt
|
|
Message is in Reply To:
 | | Re: AI, AI & AC
|
| (...) All very wonderful I'm sure - but isn't it just a *tad* off-topic? This has essentially nothing to do with either robotics or Lego. There is nowhere close to enough computing resources in anything people are likely to have in a Lego robot to (...) (24 years ago, 17-Oct-00, to lugnet.robotics)
|
10 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
