USPatent applicationPatented

Implementing a coded time domain transmission distance meter

Granted 9 Aug 2011 · no office action yet

Life of the application

6 dated events
⤢ drag to zoom20102012201420162018202020222024202620282030ProsecutionOwnershipTerm & fees
ProsecutionOwnershipTerm & feeshover for detail · click to open

Abstract

A method and circuit for implementing a coded time domain transmission distance meter, and a design structure on which the subject circuit resides are provided. A first transmitter module connected to a cable at a first point or power outlet, generates and sends a testing coded pulse onto the power cable. A second receiver module connected to the cable at a second point, receives the testing coded pulse, and returns a receiver response coded pulse to the transmitter module. The first transmitter module determines the round-trip elapsed time, subtracts a receiver latency time, and calculates a distance to the second receiver module. Encoded in the testing coded pulse are data representing the last calculated distance. Both the first transmitter module and the second receiver module include a display for displaying the calculated distance.

Description

6 parts
›FIELD OF THE INVENTION

The present invention relates generally to the data processing field, and more particularly, relates to a method and circuit for implementing a coded time domain transmission distance meter, and a design structure on which the subject circuit resides.

›DESCRIPTION OF THE RELATED ART

A problem exists to determine whether two nearby power outlets are on the same branch circuit. The problem with present methods exists to determine whether two nearby power outlets are on the same branch circuit is that electrically when two branch circuits are connected together at a circuit breaker panel at low frequencies it always appears that the two branch circuits are connected.

Known time domain reflectometry arrangements can determine distances but with many drops and stubs off the low frequency power, the data is not conclusive.

A need exists for an effective mechanism to define a start of a connection to a first power outlet and to determine a distance to a second power outlet that is a tightly defined receive point.

›SUMMARY OF THE INVENTION

Principal aspects of the present invention are to provide a method and circuit for implementing a coded time domain transmission distance meter, and a design structure on which the subject circuit resides. Other important aspects of the present invention are to provide such method, circuit and design structure substantially without negative effect and that overcome many of the disadvantages of prior art arrangements.

In brief, a method and circuit for implementing a coded time domain transmission distance meter, and a design structure on which the subject circuit resides are provided. The coded time domain transmission distance meter circuit includes a first transmitter module and a second receiver module. The first transmitter module is connected to a cable at a first point or power outlet. The first transmitter module includes a code generator, and generates and sends a testing coded pulse onto the power cable. The second receiver module is connected to the cable at a second point or power outlet, receives the testing coded pulse, and returns a receiver response coded pulse to the transmitter module. The first transmitter module determines the round-trip elapsed time, subtracts a receiver latency time, and calculates a distance to the second receiver module.

In accordance with features of the invention, by using coded pulses rather than analog pulses the reflections and multiple reflections are ignored. Encoded in the testing coded pulse is information representing the last calculated distance data corresponding to the identified time interval from the last reading. The test sequence loops continuously.

In accordance with features of the invention, both the first transmitter module and the second receiver module include a display. The first transmitter module sends distance data with the testing coded pulse so that the second receiver module can display the distance.

In accordance with features of the invention, a clock in the transmitter continuously runs at a predefined frequency, such as used to calibrate with a velocity factor of the cable. The first transmitter module includes a timer, which is started when a testing coded pulse is sent onto the power cable. The second receiver module receives and checks the testing coded pulse, and if the testing coded pulse is correct, the second receiver module sends a receiver response coded pulse to the first transmitter module. When the first transmitter module receives the receiver response coded pulse, from the second receiver module, the timer is stopped. The first transmitter module checks the receiver coded pulse, and if the receiver coded pulse is correct, uses the elapsed time from the timer to determine the distance. The calculated distance is coded back into the code generator and transmitted in the next testing coded pulse to the receiver module.

In accordance with features of the invention, the testing coded pulse contains the information from the last test and is displayed on both the transmitter and receiver modules. The second receiver module checks the testing coded pulse and when the testing coded pulse is correct, the second receiver module decodes the testing coded pulse and displays the distance.

›BRIEF DESCRIPTION OF THE DRAWINGS

The present invention together with the above and other objects and advantages may best be understood from the following detailed description of the preferred embodiments of the invention illustrated in the drawings, wherein:

FIG. 1 is a schematic diagram of an exemplary circuit for implementing a coded time domain transmission distance meter in accordance with the preferred embodiment;

FIG. 2 is a timing diagram illustrating operation of the coded time domain transmission distance meter circuit of FIG. 1 in accordance with the preferred embodiment; and

FIG. 3 is a flow diagram of a design process used in semiconductor design, manufacturing, and/or test.

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 1 of 2

In accordance with features of the invention, a method and circuit for implementing a coded time domain transmission distance meter, and a design structure on which the subject circuit resides are provided. The coded time domain transmission distance meter circuit includes a first transmitter module and a second receiver module, each using coded pulses so that problems and errors typically resulting with conventional arrangements using analog pulses are eliminated.

Having reference now to the drawings, in FIG. 1 , there is shown an exemplary coded time domain transmission distance meter circuit generally designated by the reference character 100 in accordance with the preferred embodiment. Coded time domain transmission distance meter circuit 100 includes a first transmitter module 102 and a second receiver module 104 .

The first transmitter module transmitter 106 and is connected to a cable or branch circuit labeled CABLE at a first point or power outlet indicated at a node TR 1 . The first transmitter module 102 includes a code generator 108 connected to the transmitter 106 for generating and sending a testing coded pulse onto the power cable.

The first transmitter module 102 includes a timer 110 receiving a start input from the transmitter 106 indicated at a line START and receiving a clock input from a clock 112 . The timer 110 is connected to a calculate distance function 114 and a display 116 for displaying a calculated distance is connected to the calculate distance function 114 .

The first transmitter module 102 includes a receiver 118 connected to the cable at node TR 1 receiving a receiver response coded pulse from the second receiver module 104 and applying a stop signal to the timer 110 indicated at a line STOP. The first transmitter module 102 includes a code checking function 120 represented by a decision block labeled CORRECT? The code checking function 120 is connected between the receiver 118 and the calculate distance function 114 .

The second receiver module 104 is connected to the cable at a second point or power outlet indicated at a node RC 2 . The second receiver module 104 includes a receiver 122 receives the testing coded pulse sent by the first transmitter module 102 , and selectively returns a receiver response coded pulse to the transmitter module 102 .

The second receiver module 104 includes a code checking function 124 represented by a decision block labeled CORRECT? The code checking function 124 is connected a code generator 126 . The code generator 126 generates a receiver response coded pulse responsive to an identified valid testing coded pulse by the code checking function 124 .

The second receiver module 104 includes a transmitter 128 connected to the code generator 126 and connected to the cable at node RC 2 for transmitting the receiver response coded pulse to the transmitter module 102 .

The second receiver module 104 includes a decoder 130 connected to the code checking function 124 and connected to a distance display 132 . The decoder 130 decodes the identified valid testing coded pulse applied by the code checking function 124 . The decoder 130 applies a distance display signal to the distance display 132 responsive to the particular identified valid testing coded pulse applied to the decoder 130 by the code checking function 124 .

Referring also to FIG. 2 , there is shown a timing diagram generally designated by the reference character 100 illustrating operation of the coded time domain transmission distance meter circuit 100 in accordance with the preferred embodiment. The upper waveform labeled RECEIVER PULSE BACK TO TRANSMITTER illustrates the receiver response coded pulse sent to the first transmitter module 102 by the second receiver module 104 . The lower waveform labeled TRANSMITTED CODED PULSE illustrates the testing coded pulse sent by the first transmitter module 102 to the second receiver module 104 . An example coded elapsed time information and valid transmit code are shown in the waveform TRANSMITTED CODED PULSE. An example receiver response coded pulse sent to the transmitter module 102 is shown in the waveform RECEIVER PULSE BACK TO TRANSMITTER.

In operation, the clock 112 in the first transmitter module 102 continuously runs at a predefined frequency used to calibrate with a velocity factor of the tested cable. The timer 110 is started when the transmitter 106 sends a testing coded pulse onto the power cable. The second receiver module 104 receives and checks the testing coded pulse, and if the testing coded pulse is correct, the second receiver module 104 sends a receiver response coded pulse to the first transmitter module 102 . When the first transmitter module 102 receives the receiver response coded pulse from the second receiver module, the timer is stopped. The first transmitter module 102 checks the receiver coded pulse, and if the receiver coded pulse is correct, the calculate distance function 114 uses the elapsed time from the timer 110 to determine the distance.

The calculate distance function 114 of the first transmitter module 102 identifies or determines the round-trip elapsed time from the timer 110 , subtracts a predefine receiver latency time, and calculates a distance to the second receiver module 104 . The calculated distance is displayed on the distance display 116 and applied to the code generator 108 of the first transmitter module 102 .

The first transmitter module 102 provides and sends distance data with a next testing coded pulse so that the second receiver module 104 can display the identified distance between the modules 102 , and 104 . The calculated distance is coded back into the code generator 108 and transmitted within the next testing coded pulse transmitted by the first transmitter module 102 . The testing coded pulse contains the calculated distance information from the last test and is displayed on respective displays 116 and 132 of the transmitter and receiver modules 102 , 104 .

FIG. 3 shows a block diagram of an example design flow 300 . Design flow 300 may vary depending on the type of IC being designed. For example, a design flow 300 for building an application specific IC (ASIC) may differ from a design flow 300 for designing a standard component. Design structure 302 is preferably an input to a design process 304 and may come from an IP provider, a core developer, or other design company or may be generated by the operator of the design flow, or from other sources. Design structure 302 comprises circuit 100 in the form of schematics or HDL, a hardware-description language, for example, Verilog, VHDL, C, and the like. Design structure 302 may be contained on one or more machine readable medium. For example, design structure 302 may be a text file or a graphical representation of circuit 100 . Design process 304 preferably synthesizes, or translates, circuit 100 into a netlist 306 , where netlist 306 is, for example, a list of wires, transistors, logic gates, control circuits, I/O, models, etc. that describes the connections to other elements and circuits in an integrated circuit design and recorded on at least one of machine readable medium. This may be an iterative process in which netlist 306 is resynthesized one or more times depending on design specifications and parameters for the circuits.

›DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS · 2 of 2

Design process 304 may include using a variety of inputs; for example, inputs from library elements 308 which may house a set of commonly used elements, circuits, and devices, including models, layouts, and symbolic representations, for a given manufacturing technology, such as different technology nodes, 32 nm, 45 nm, 90 nm, and the like, design specifications 310 , characterization data 312 , verification data 314 , design rules 316 , and test data files 318 , which may include test patterns and other testing information. Design process 304 may further include, for example, standard circuit design processes such as timing analysis, verification, design rule checking, place and route operations, and the like. One of ordinary skill in the art of integrated circuit design can appreciate the extent of possible electronic design automation tools and applications used in design process 304 without deviating from the scope and spirit of the invention. The design structure of the invention is not limited to any specific design flow.

Design process 304 preferably translates an embodiment of the invention as shown in FIG. 1 along with any additional integrated circuit design or data (if applicable), into a second design structure 320 . Design structure 320 resides on a storage medium in a data format used for the exchange of layout data of integrated circuits, for example, information stored in a GDSII (GDS2), GL1, OASIS, or any other suitable format for storing such design structures. Design structure 320 may comprise information such as, for example, test data files, design content files, manufacturing data, layout parameters, wires, levels of metal, vias, shapes, data for routing through the manufacturing line, and any other data required by a semiconductor manufacturer to produce an embodiment of the invention as shown in FIG. 1 . Design structure 320 may then proceed to a stage 322 where, for example, design structure 320 proceeds to tape-out, is released to manufacturing, is released to a mask house, is sent to another design house, is sent back to the customer, and the like.

While the present invention has been described with reference to the details of the embodiments of the invention shown in the drawing, these details are not intended to limit the scope of the invention as claimed in the appended claims.

Claims as granted

20 claims

Log in to read the claims of this application.

Log in to unlock

Classifications

5 codes
IPC · International Patent Classification
Section G — Physics
  • G01R31/02
  • G01R31/11
USPC · US Patent Classification
324/533324/534324/543

Claim changes

Soon
Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoomApr 2009Jul 2009Oct 2009Jan 2010Apr 2010Jul 2010Oct 2010Jan 2011Apr 2011Jul 2011Oct 2011USPTOApplicantNotice of allowance
USPTOApplicanthover for detail · click to open
Pendency
2.3 y
832 days filing → grant
Office actions
0
none on record
Examiner
Hoai-An D Nguyen
art unit 2858 · TC 2800
Citations: 8 back · 0 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Log in to unlock

Chain of title

⤢ drag to zoom20102012201420162018202020222024202620282030Owner 1
Titlehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.

Log in to unlock