To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 1039
1038  |  1040
Subject: 
Re: Electrical Data Link between 2 RCXs
Newsgroups: 
lugnet.robotics.rcx.nqc, lugnet.robotics
Date: 
Wed, 28 Mar 2001 12:40:39 GMT
Viewed: 
2475 times
  
Hi Marco,

it is always interesting how many other people in the world do have the same
problems or are dealing with the same subject. Sometimes I had the feeling that
I dealt with "exotic" problems but then I realized that other "Mindstormers"
had similiar questions. But that is what this forum is for - right?

You wrote

...
After this, I'll try to do standard VLL input with RCX2 firmware using
FastTimer(). Because Standard VLL needs 10ms resolution, I think it'll work.


When you use "fast" timers, giving a resolution of 10 ms per tick, in most
cases you will not be able to create a certain time period exactly. E.g., if
you want to create a time period of 50 ms, you will get 50 ms + e, with
0 <= e < 10 ms. The reason for this is that you have to use a condition with
"FastTimer(n) >=" instead "FastTimer(n) ==".

Even when having a very simple loop like:

ClearTimer(0);
until (FastTimer(0) == 5) statement;

you will miss the exact condition very often. So you must use a ">=" instead of
a "==", producing the above tolerance "e".

When I say VLL, I include the direct electrical connection, using the
Off()/Float() technique, along with the other light emission through OUT
ports or through active IN ports (example: using the LightSensor LED)


I wrote a VLL interface for the Microscout, adapting some technique of a
Japanese guy, that worked brilliant (besides the fact that the Microscout is a
really "stupid" unit). What I found out is that the transmission could not be
speeded up. The reason - as far asI think - is that the toggling of the light
sensor could not be made faster. Somewhere in Lugnet I read that the LED in the
light sensor is too slow but I don't believe this.

I will continue with tuning the interface. Currently - if I have the time - I
am experimenting with a bi-directional IR link between 2 RCXs with 3
requirements: asynchroneous, fast and totally reliable. Sounds simple - in fact
it is not, due to the fact that the IR unit in the RCX can either send or
receive.

Best regards
Bernd



Message has 1 Reply:
  RE: Electrical Data Link between 2 RCXs
 
(...) Hi :) (...) Heheh, my feelings exactly before "bumping" into LUGnet community almost a year and a half ago ;) Ok, now, about the way I use Timer() and will try to use FastTimer() or counter loop if proven more effective. I have no need to get (...) (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.nqc, lugnet.robotics)

Message is in Reply To:
  RE: Electrical Data Link between 2 RCXs
 
Hi Bernd :) I see we're working in the same subject here :) *great* If you care to browse lugnet.robotics old thread "VLL *input* for RCX/CyberMaster (in NQC) ?" or the newer one, starting with "CM-RCX" (the subject had some variations) Your (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.nqc, lugnet.robotics)

11 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