Model train controller interface device

The model train controller interface device provides a user with the capability of operating model train engine, switch and accessories of one manufacturer with the handheld wireless device of a second manufacturer. Inserted between the command base units and controller devices of different model train manufacturers, the interface device allows the wireless remote of one train system to operate components of the other train system without loss of functionality by either model train system.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to control systems for model trains, and particularly to devices that interface between control systems of different model train manufacturers, allowing one vendor's control unit to operate components of a competing manufacturer.

2. Description of the Related Art

Model train control systems have, as basic building blocks, a set of interconnected sections of train track, electric switches between different sections of the train track, a variety of electrically controlled devices, and finally, at least one electric train engine.

Standard O-gauge electrical train operation is characterized by an AC track signal, wherein the AC signal is switchably offset by a DC signal used to enable various train accessories such as the horn/whistle function. The AC track signal energizes the electric motor of the train engine, with the DC offset enabling a train engine relay unit to activate the appropriate bell or whistle feature. In addition, certain standard O-gauge type transformers include fixed AC voltage supply terminals for operating lights and additional accessories.

In order to ensure compatibility of their products and accessories with those already in use, current manufacturers have adhered to the basic electrical standard, namely the AC track signal voltage and DC control offset popularized by the standard O-gauge transformer. The standardization of this power arrangement ensures the continued compatibility of vintage train engines with new engines and other model train technologies.

The vintage train engines utilize a transformer with a variable output voltage controls the speed of the engine by directly controlling the voltage applied to the track; the greater the voltage, the greater the speed.

In newer engines digital control systems are employed in which a set voltage is applied to the track and the train responds to command signals from a command unit that transmits signals to the train. There are several manufacturers of both the vintage and command signal model train methodologies, and within the command system category of model trains, different manufacturers employ different command signals for the control of their engines.

One example of the legacy control system includes U.S. Pat. No. 6,624,537, issued to Richard Westlake in September 2003. The '537 patent discloses a plural output control station having a data processor for monitoring and controlling the signals generated at a plurality of transformer-driven power output terminals. The variable-voltage outputs are controlled by a data processor, which responds to respective operator-controlled throttles for varying the AC output voltage and therefore the rate of movement and direction of electric train engines.

Digital model-railway control systems have been state-of-the-art for several years. In such control systems the full driving voltage, e.g. 16 volts AC, is continually applied to the track. The rails serve simultaneously to transmit digital data, forming a so-called data bus. For this purpose, appropriate digital control commands are superimposed on the driving voltage and include commands specifying direction, velocity and ancillary functions, such as activation of lights or automatic coupling. These digital control commands are encoded by a control system in a digital transmission format, e.g. NMRA/DCC, with address information designating a particular engine. Each engine has a decoder for picking out its commands. Such decoders can also be used in other functional articles such as cranes, switches or the like, for the remote triggering of control commands. Model train systems incorporating digital control systems include TrainMaster Command Control (TMCC) from Lionel Trains, Inc. and the DCS from Mike's Train House (MTH).

The Lionel TMCC, for instance, utilizes a wireless control unit (CAB), which transmits a signal to the TMCC base, which in turn, modulates a 455 KHz carrier signal. The FM modulated signal is then capacitor coupled to the common of the track system. An FM receiver in the engine detects the modulated signal and performs the required function. The TMCC also controls the operation of track switches and other devices by means of Accessory Switch Controllers (ACS). The TMCC transmits a digital signal to the ASC containing command information along with an address field. Each ASC has an unique address which responds to the address transmitted by the TMCC. Upon command from the Lionel wireless control unit (CAB), an ASC can operate eight accessories or four switches and ten train routes. In addition to receiving commands from the wireless digital controller, the TMCC has a port for receiving digital signals from a user provided digital device such as a computer.

An alternative control system for model trains is provided by Mike's Train House Inc. (MTH) DCS, which is based upon U.S. Pat. Nos. 6,457,681 and 6,655,640, issued to Wolf et al. in October 2002 and December 2003 respectively. The '681 patent discloses a handheld remote control unit through which various commands may be entered to control not only the train engine, but also track switches and ancillary electric devices. A Track Interface Unit (TIU), in RF communication with the handheld controller, converts the commands to a modulated signal and transmits control signals to the engine over the power rail of the track system. The control signal is not a wireless FM signal and requires electrical connectively between the train and the track. The train picks up the modulated signal, retrieves the entered command, and executes it through use of a processor and associated circuitry onboard the engine.

As with the TMCC, the MTH DCS permits remote control of track switches and accessories by the use of a TIU connected Accessory Interface Unit (AIU), which has a set of output relays that are coupled to various portions of the track layout through standard hard wiring.

The AIU is electrically connected to the TIU by a variety of electrical means and operates the various accessories in response to user commands initiated by the handheld unit. Because of their popularity most of the O-gauge world runs TMCC and DCS and many model train enthusiasts have both systems and may want to control their TMCC trains using their MTH handheld remote

Both the Lionel TMCC and the MTH TIU have serial data ports that once connected allow for limited interoperability between the two competing systems. In order to do this, a serial data cable must be connected between the MTH TIU and the Lionel TMCC, and the MTH TIU must then be programmed to transmit Lionel train commands over the serial interface to the TMCC. However, as noted, the interface is limited. DCS can control TMCC but TMCC cannot control DCS. Furthermore, the TMCC command base port to which the TMCC-TIU cable is connected is the same port used to connect to the TMCC ASCs. Therefore, the use of the TMCC-TIU cable precludes the use of the TMCC ASC devices, and for all intents and purposes, renders the CAB-1 hand held remote ineffective to control TMCC accessories through TMCC ASC devices.

MTH DCS and TMCC are not the only model train control systems that have been developed. Other systems have been disclosed in U.S. Pat. No. 6,065,406, issued to M. Katzer in May 2000, and U.S. Pat. No. 6,441,570, issued to Grubba et al. in August 2002.

None of the above inventions and patents, taken either singly or in combination, is seen to describe the instant invention as claimed. Thus, a model train controller interface capable of interfacing disparate model train systems is desired.

SUMMARY OF THE INVENTION

The model train interface device provides a user with the capability of operating model train engines, switches and accessories of one manufacturer with the handheld wireless device of a second manufacturer. Inserted between the Track Interface Unit (TIU) supplied by Mike's Train House (MTH) and the TrainMaster Command Control (TMCC) command base station manufactured by Lionel, Inc., the interface allows the MTH hand held remote to control TMCC devices without limiting the functionality of the TMCC wireless controller. The interface converts the signals from the TIU to the TMCC protocol and transmits them to the TMCC base station. The TMCC base station then transmits engine commands to the locomotives or echoes switch and accessory commands to Accessory Switch Controllers through the interface.

Unlike simple serial cable interfaces which permits a DCS handheld control device to operate TMCC equipped trains at the price of rendering useless TMCC switch and accessory control components, embodiments of the present invention do not limit functionality of the TMCC components.

The model train interface device comprises three embodiments. The first embodiment comprises a housing, which includes a printed circuit board, a plurality of connectors in electrical communication with a first train controller device, a second train controller device, and at least one train accessory controller device. The device receives AC power from a transformer or the train track and produces an operative voltage to the electronic circuitry contained within the housing.

The printed circuit board contains electronic circuitry that controls the flow of data between the interconnected devices. The circuitry includes a microcontroller with memory, interface logic and program instruction code stored within the memory. The microcontroller controls the flow of commands from the MTH TIU to the TMCC command base. Furthermore, the microcontroller accepts commands received from any other source of TMCC commands, such as the action Recorder Controller (ARC) and multiplexes these commands over the data link to the TMCC command base.

The second embodiment is an interface cable having two connectors disposed on either cable end, and includes a pigtail having at least two leads extends from one of the cable connectors and is adapted for attachment to terminal leads disposed on the switch and accessory device controllers. Designed to operate in combination with the commercially available TIU/TMCC serial cable, the present invention allows MTH DCS wireless controls to command TMCC equipped engines, while retaining the ability of the TMCC remote handheld to command TMCC equipped switch and accessory controller devices.

A third embodiment, similar to the interface cable of the second embodiment, connects directly to the TIU and is designed to eliminate the need of the prior art TIU/TMCC serial cable.

These and other features of the present invention will be apparent upon consideration of the following specification and drawings.

Similar reference characters denote corresponding features consistent throughout the attached drawings.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention is a model train controller interface device, designated generally as100in the drawings, that allows communication between components of Mikes Train House (MTH) DCS model train system and model train systems incorporating TrainMaster Command Control (TMCC) developed by Lionel, Inc.

FIG. 1represents a block diagram of a first embodiment of the present invention100incorporated in a model train layout having both TMCC and Mike's Train House (MTH) model train components.FIG. 2Arepresents prior art and illustrates a train layout in which the MTH model train components provide no commands to TMCC equipped components. In other words, the MTH handheld wireless device102can control only MTH engines and devices connected to the Accessory Interface unit (AIU)112. Likewise, the CAB-1 remote110can control only TMCC engines and TMCC controllers, such as Accessory Switch Controllers (ASC)116–120and the Action Recorder Controller (ARC)114.

Still illustrating the prior art,FIG. 2Brepresents an alternate track layout in which the MTH TIU104and the TMCC command base108are interconnected by a TIU/TMCC serial cable206having female and male 9-pin connectors202,204connected between TIU104port130and TMCC base command unit108port132respectively. Implementing the TIU/TMCC cable206allows a DCS handheld wireless device102to command TMCC equipped engines and precludes the use of the TMCC controller devices114–120which must be connected to the same port, that is TMCC base command unit108port132.

Referring back toFIG. 2A, a model train layout utilizing the TMCC system requires, at a minimum, a CAB-1 remote control110, which is used by the operator to control all model train functions, and a TMCC command base108. The command base108receives signals from the CAB-1110and relays them to TMCC controllers114–120. The command base108relays signals to the layout in two ways. The first way uses radio waves, so that signals to engines are carried along the outside rail122of the layout. This requires a single wire connecting the command base108to an outside rail122of the track128or a transformer's common or U terminal. Engines, placed on the track, pick up the signals independent of their location on the track128. The second means by which the TMCC command base108communicates is via an asynchronous data link that uses 2 wires connected to a serial port132integrated in the command base. Port132of the command base108echoes on its transmit lead all commands received from the CAB-1110. In addition to echoing signals received from the CAB-1110, the transmit lead on port132echoes back all commands received on the receive lead of port132after being processed by the command base108. The wires carrying the command signals can be daisy-chained from one TMCC device to another, so a layout that uses multiple TMCC equipped controllers only needs to have one pair of wires connected to the command base108. One such controller for controlling up to 4 switches or up to 8 accessories is the Accessory Switch Controller (ASC)116–120. An Action Recorder Controller (ARC)114is also available, which records whatever commands are generated by the CAB-1 remote110, storing them for future playback.

The data link between port132and the TMCC controllers114–120transmits and receives signals utilizing a 9600-baud, one stop bit, and no parity protocol. The data is transmitted in a three-byte format, the first eight-bit byte being hexadecimal “FE”. The remaining two bytes, as shown in Table 1, consists of address and data bits, whereby the CAB-1 handheld remote110can transmit switch commands, route commands, engine commands, train commands, accessory commands and group commands.

Table 2 represents the command set the command base108uses to communicate with the ASCs for controlling routes. Table 3 represents the command set that the TMCC108sends to the ASCs116–120for controlling track switches, and Table 4 represents the commands sent by the command base108to the ASCs for controlling accessories.

Still referring to the prior art ofFIG. 2A, the MTH DCS features two required components, the DCS Remote Control102and the Track Interface Unit (TIU)104. An additional component, the Accessory Interface Unit (AIU)112, can be added to provide control over the accessories and switches. The DCS operates by transmitting an electrical “digital” signal superimposed upon the power from the transformer106into the center rail126of the railroads track128.

The MTH DCS controls switches and accessories by means of one or more AIUs112. The AIU112receives its commands from the TIU104and supplies relay contact closure outputs to accessories and switches. One interface protocol between the TIU104and the AIU112is defined in U.S. Pat. No. 6,457,681, issued to Wolf et al. in October 2002 and incorporated herein by reference in its entirety. The disclosed interface consists of a three-wire serial interface port134, wherein one wire is a data line that is set to the value of the most significant bit of the data byte being sent. A clock line is then pulsed high then low to clock in the signal into an 8-bit shift register in the AIU. After 8 bits have been clocked in, the entire byte is clocked out by pulsing the third line, which is a latch. The data in the byte is therefore essentially 7 bits of address to select the particular relay in the AIU that the user wishes to open or close and 1 bit to either open or close the relay.

As previously discussed, MTH DCS has the capability, by means of the TIU/TMCC serial cable206, to permit a MTH DCS wireless remote to command TMCC equipped engines.

Now referring toFIG. 1, the first embodiment of the Model Train Controller Interface100acts as a bridge between MTH and TMCC components. As shown inFIG. 1, the interface100includes a plurality of digital ports connected to circuitry136. Port J1, is connected to port130on the TIU104by means of a standard 9-pin serial null model cable and receives therefrom a first digital data stream141formatted in the TMCC protocol. A second port J2connects to port134on the TIU104and receives therefrom a second digital signal142in a second protocol that would normally be received by an AIU. A third port J3may be connected to command generating devices such as the ARC114from which the interface100receives a third digital signal143. A fourth port J4connects to port132on the TMCC command base108by means of a standard 9-pin male-to-male null modem cable. Port J4is bidirectional, transmitting a fourth digital signal144in TMCC protocol on pin2to the TMCC command base108and receiving back a fifth digital signal145from the command base108on pin3. This fifth signal145is transmitted as signal146on port J3, to device controllers114–120. Power is supplied to the device by means of a pair of wires148wired to the transformer106. Signal ground150is received from the TMCC command base108on pin5of J4and is passed along on lead152to device controllers114–120.

FIG. 3is a representative schematic of the circuit136mounted within the housing of the interface100. The electronic circuit controls the flow of digital data between the TIU104, the TMCC command base108, and TMCC devices114–120. The circuitry includes a microcontroller U1with built in memory, discrete electronic devices, and program instruction code stored within the memory. The firmware stored in the memory controls the multiplexing of the various data streams and is of a level of complexity known to those skilled in the art of programming.

In operation, the interface100transmits commands received on ports J1–J3to the TMCC command base108. For instance, engine commands in data stream141, originating from the MTH DCS handheld remote102, are received by the TIU104and are transmitted on port130through a standard commercially available serial cable to port J1. Switch and accessory commands generated from the MTH DCS handheld remote102, are relayed through port134on the TIU104, and are received in data stream142on port J2. The signal is read by shift register U2and after 8 bits have been clocked in, the entire byte is clocked into U1. Finally, pin3on port J3receives digital data stream143, a third source of command data from any ARC114or other automated device that generates TMCC commands intended for TMCC controlled components.

Still referring toFIG. 3, engine and accessory commands received in data streams141–143on ports J1–J3respectively are processed by circuitry shown inFIG. 3and are read by microcontroller U1. The microcontroller U1reads the data stream presented by the three digital input streams, converting the data received to the TMCC protocol disclosed in Tables 1–4 as necessary. The microcontroller multiplexes the data and outputs a data stream which is processed by R5, R6and Q2into a digital data stream144on pin2of port J4to port132of the TMCC command base108. Upon receipt of the data stream transmitted from port J4pin2, the TMCC command base108transmits engine commands to a model train engine (not shown) via Frequency Modulation (FM).

Without the present invention100, switch and accessory commands from the TMCC command base108, would normally, as shown inFIG. 2A, be contained in transmit signal145wired directly to controllers114–120through port132. Use of the present invention100, however, requires that port132be wired to J4of the interface100. Therefore, since the TMCC command base108has only one port132, the transmit lead of the command base108must route the data stream145back to J4pin3of interface100. Data stream145is then transmitted on pin2of J3to the receive port of the daisy-chained device controllers114-120via data stream146as shown inFIG. 1.

A rectifier circuit140, known to those skilled in the art converts the AC signal from the transformer106to the DC voltage required by the present invention100.

The microcontroller U1is a commonly available commercial device, such as the PIC17C42A or the newer PIC18F4220, and is typically found with an oscillator circuit formed by C1, C2and crystal Y1. Similarly, a power on reset function is provided by R1, C3and D1.

Table 5 provides representative values for components disclosed inFIG. 3and is based upon known interfaces for the various model train components and the design preferences of those skilled in the art of electronic design.

FIG. 4illustrates a second embodiment of the present invention in which a specially designed interface cable400retains the ability of the CAB-1110remote to command TMCC equipped switch and accessory device controllers116–120while permitting the MTH DCS remote102to command TMCC equipped engines.

Interface cable400comprises a cable402having at least two electrical conductors connected between two commercially available 9-pin “D” shell connectors404,406, one connector406is a 9-pin male connector and the other a 9-pin female connector404. The interface cable400is similar to a commercially available “null modem” cable in that pin2of one connector is wired to pin3of the connector at the other end. Signal ground is transmitted though pin5on both connectors. Although the TMCC does not presently send commands to the TIU and therefore would not require a transmit lead from the TMCC to the TIU, this lead is made available for future use.

FIG. 5illustrates the interconnection of interface cable400within the model train layout. Male connector406is adapted for mounting to port132of the TMCC command base108, and female connector404is connected to the male connector204of the MTH/TIU serial cable206. Unlike standard “null modem” cables, the cable converter400includes a pigtail414comprising three conductors408–412extending from a connector, the three conductors408–412being in electrical contact with pins2,3, and5of connector406respectively. Although the pigtail414may extend from connector404, in the present design, pigtail414extends from connector406and conductors408–120are soldered or crimped to pins2,3and5of connector406respectively. The end of wire408is connected by a tightening screw connector to the receive terminal of the first device controller114and is the means by which commands are transmitted from the TMCC command base108to device controllers114–120. The end of wire410is screwed on to the transmit terminal of any transmitting device controller114and transmits commands back to the TMCC command base108. Wire412carries signal ground from the command base108to device controllers114–120.

A third embodiment600, similar to the cable converter disclosed inFIGS. 4–5, is illustrated inFIG. 6. Similar to the embodiment400, interface cable600is designed to replace the need of the MTH TIU/TMCC serial cable206shown inFIG. 5. As best illustrated inFIG. 7, connector604engages port130of the TIU104, and connector606engages port132of TMCC command base108. The interface cable600differs from embodiment400shown inFIG. 4, in that interface cable600has male connectors404,406on both ends of cable602and pin3of connector406is wired to pin9of connector404, for unlike standard practice, the TIU transmits on pin9instead of pin2.

Still referring toFIGS. 6–7, interface cable600is similar to the cable interface disclosed as embodiment400, in that pigtail414and conductors408–412extend from pins2,3and5of connector606and are connected to device controllers114–120.