To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.trainsOpen lugnet.trains in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Trains / 21022
21021  |  21023
Subject: 
Re: Versions 2 and 3 of micromotorized crossing gates.
Newsgroups: 
lugnet.trains
Date: 
Sun, 7 Sep 2003 03:14:02 GMT
Viewed: 
1726 times
  
Ed McGlynn wrote:

You mean RCX w/light sensor as one option and DCC as another option?  How would
you tie in the logic for it, if not using manual controls via DCC?  Just
curious.
I've been thinking about this one. In the current state of LDCC, a fully
automated and LDCC-integrated (and pure LEGO) crossing gate could look something
like this (ASCII art follows):


Train presence
       sensor------+-------+
                   + RCX 1 |
               +---+-------+
               |
Gate motor----+
               |   +-------+
               |   | RCX 2 |
               +---+ LACC  +------LDCC Acknowledgement Sensor
                   +-------+                 |
                                          9v track
                   +-------+                 |
                   + RCX 3 +-----------------+
                   | LDCC  |
                   +-------+

In this instance, RCX 1 is running your favorite automated gate control software
(you would write this). RCX 2 running LACC is connected to the gate motor in
parallel with RCX 1. This allows manual control of the gate. In this situation,
neither RCX 1 nor RCX 2 will be, nor need be, aware of the other.

Okay, so it's fully automated, and LDDC integrated, but it's not LDDC automated.
For this to happen we need RCX software that can communicate directly with RCX 3
which is running LDCC. The emerging LDCC IR Protocol is a standard for this
communication.  There's not much on the software end yet for RCX 1. When it does
happen, the topology will look more like this:

Train presence
       sensor------+-------+
                   + RCX 1 |----------LDCC IRP link
Gate motor----+---+-------+                 |
                                             |
                   +-------+                 |
                   + RCX 3 +-----------------+
                   | LDCC  |
                   +-------+

You will still have to write your own program on RCX 1, and it will have to use a
replacement firmware such as BrickOS, leJOS or pbFORTH. You'll be able to re-use
code someone else wrote to "talk" LDCC.
I practically blog about this possibility in the thread
http://news.lugnet.com/org/us/indylug/?n=618&t=i&v=c so I won't go any further
into it here.



Message is in Reply To:
  Re: Versions 2 and 3 of micromotorized crossing gates.
 
(...) *snip* You mean RCX w/light sensor as one option and DCC as another option? How would you tie in the logic for it, if not using manual controls via DCC? Just curious. (...) Excellent point - take James' advice on this! Ed (21 years ago, 5-Sep-03, to lugnet.trains)

10 Messages in This Thread:



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

Custom Search

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