US20220043135A1 - Automatic device ordering - Google Patents
Automatic device ordering Download PDFInfo
- Publication number
- US20220043135A1 US20220043135A1 US16/985,423 US202016985423A US2022043135A1 US 20220043135 A1 US20220043135 A1 US 20220043135A1 US 202016985423 A US202016985423 A US 202016985423A US 2022043135 A1 US2022043135 A1 US 2022043135A1
- Authority
- US
- United States
- Prior art keywords
- node
- node device
- pulse
- order
- data lines
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S13/00—Systems using the reflection or reradiation of radio waves, e.g. radar systems; Analogous systems using reflection or reradiation of waves whose nature or wavelength is irrelevant or unspecified
- G01S13/02—Systems using reflection of radio waves, e.g. primary radar systems; Analogous systems
- G01S13/06—Systems determining position data of a target
- G01S13/08—Systems for measuring distance only
- G01S13/10—Systems for measuring distance only using transmission of interrupted, pulse modulated waves
- G01S13/26—Systems for measuring distance only using transmission of interrupted, pulse modulated waves wherein the transmitted pulses use a frequency- or phase-modulated carrier wave
- G01S13/28—Systems for measuring distance only using transmission of interrupted, pulse modulated waves wherein the transmitted pulses use a frequency- or phase-modulated carrier wave with time compression of received pulses
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S13/00—Systems using the reflection or reradiation of radio waves, e.g. radar systems; Analogous systems using reflection or reradiation of waves whose nature or wavelength is irrelevant or unspecified
- G01S13/02—Systems using reflection of radio waves, e.g. primary radar systems; Analogous systems
- G01S13/06—Systems determining position data of a target
- G01S13/08—Systems for measuring distance only
- G01S13/10—Systems for measuring distance only using transmission of interrupted, pulse modulated waves
- G01S13/12—Systems for measuring distance only using transmission of interrupted, pulse modulated waves wherein the pulse-recurrence frequency is varied to provide a desired time relationship between the transmission of a pulse and the receipt of the echo of a preceding pulse
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40097—Interconnection with other networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40123—Interconnection of computers and peripherals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
Definitions
- the apparatus includes a processor and a memory storing code executable by the processor.
- the processor configures each node device on a serial network for an order measurement.
- the processor further measures an order parameter for each of the node devices.
- the processor determines an order number of each of the node devices based on the order parameter for the node device.
- a method for automatic device ordering is also disclosed.
- the method configures, by use of a processor, each node device on a serial network for an order measurement.
- the method measures an order parameter for each of the node devices.
- the method determines an order number of each of the node devices based on the order parameter for the node device.
- a computer program product for automatic device ordering comprises a non-transitory computer readable storage medium having code embodied therein.
- the code is readable/executable by a processor.
- the processor configures each node device on a serial network for an order measurement.
- the processor further measures an order parameter for each of the node devices.
- the processor determines an order number of each of the node devices based on the order parameter for the node device.
- FIG. 1A is a schematic block diagram of serial network according to an embodiment
- FIG. 1B is a schematic drawing of a network cable according to an embodiment
- FIG. 3A is a schematic drawing of a master device and a node device on the serial network according to an embodiment
- FIG. 3B is a schematic drawing of a current source according to an embodiment
- FIG. 3C is a schematic drawing of a voltage circuit according to an embodiment
- FIG. 3D is a schematic drawing of a master device and a node device on the serial network according to an alternate embodiment
- FIG. 3E is a schematic drawing of a pulse circuit according to an embodiment
- FIG. 3F is a schematic drawing of a low impedance circuit according to an embodiment
- FIG. 3G is a schematic drawing of a master device and a node device on the serial network according to an alternate embodiment
- FIG. 3H is a schematic drawing of pulses according to an embodiment
- FIG. 4 is a schematic block diagram of a controller according to an embodiment
- FIG. 5A is a schematic flow chart diagram of a device addressing method according to an embodiment
- FIG. 5B is a schematic flow chart diagram of a time-of-flight order determination method according to an embodiment.
- FIG. 5C is a schematic flow chart diagram of a node voltage order determination method according to an embodiment.
- aspects of the present invention may be embodied as a system, method, and/or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having program code embodied thereon.
- modules may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
- a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
- Modules may also be implemented in software for execution by various types of processors.
- An identified module of program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
- a module of program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
- operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
- the program code may be stored and/or propagated on in one or more computer readable medium(s).
- the computer readable medium may be a tangible computer readable storage medium storing the program code.
- the computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
- the computer readable storage medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing.
- a computer readable storage medium may be any tangible medium that can contain, and/or store program code for use by and/or in connection with an instruction execution system, apparatus, or device.
- the computer readable medium may also be a computer readable signal medium.
- a computer readable signal medium may include a propagated data signal with program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electrical, electro-magnetic, magnetic, optical, or any suitable combination thereof.
- a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport program code for use by or in connection with an instruction execution system, apparatus, or device.
- Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireline, optical fiber, Radio Frequency (RF), or the like, or any suitable combination of the foregoing
- the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums.
- program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.
- Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, C sharp, Lisp, Clojure, PHP or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages.
- the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- LAN local area network
- WAN wide area network
- the computer program product may be shared, simultaneously serving multiple customers in a flexible, automated fashion.
- the computer program product may be integrated into a client, server and network environment by providing for the computer program product to coexist with applications, operating systems and network operating systems software and then installing the computer program product on the clients and servers in the environment where the computer program product will function.
- software is identified on the clients and servers including the network operating system where the computer program product will be deployed that are required by the computer program product or that work in conjunction with the computer program product. This includes the network operating system that is software that enhances a basic operating system by adding networking features.
- the embodiments may transmit data between electronic devices.
- the embodiments may further convert the data from a first format to a second format, including converting the data from a non-standard format to a standard format and/or converting the data from the standard format to a non-standard format.
- the embodiments may modify, update, and/or process the data.
- the embodiments may store the received, converted, modified, updated, and/or processed data.
- the embodiments may provide remote access to the data including the updated data.
- the embodiments may make the data and/or updated data available in real time.
- the embodiments may generate and transmit a message based on the data and/or updated data in real time.
- the program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- the program code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the program code which executed on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code for implementing the specified logical function(s).
- FIG. 1A is a schematic block diagram of a serial network 100 .
- the serial network 100 provides communications between the plurality of devices.
- the serial network 100 includes a master device 101 , a plurality of node devices 103 , and a network cable 105 .
- the master device 101 may communicate with and/or control the plurality of node devices 103 .
- the master device 101 may communicate with networks and/or devices outside of the serial network 100 .
- the master device 101 may communicate with the local area network.
- the node devices 103 may communicate with networks and/or devices through the master device 101 .
- the network cable 105 functions as a multi-drop bus.
- Node devices 103 may be added to the network cable 105 as needed.
- a switch node device 103 may be added to an automation system by physically installing the switch node device 103 the automation system and connecting the switch node device 103 to the network cable 105 .
- the master device 101 may discover the switch node device 103 and communicate with the switch node device 103 .
- inputs to the switch node device 103 are communicated to the master device 101 and/or upstream networks and/or devices outside of the serial network 100 .
- the serial network 100 supports the convenient addition of node devices 103 .
- the master device 101 and node devices 103 may each have a node device identifier.
- the node device identifier is a Media Access Control (MAC) address.
- the node device identifier is used to logically identify and address a corresponding node device 103 .
- a user may need to physically identify a node device 103 as a third node device 103 on the network cable 105 in order to service the node device 103 .
- the place of the node device 103 on the network cable 105 may be indicated using a device address.
- a serial network unique but non-sequential device address is assigned for each location.
- FIG. 1B is a schematic drawing of the network cable 105 .
- the network cable 105 is a ribbon cable.
- the network cable includes switched power lines 111 , network power lines 113 , and data lines 115 .
- the switched power lines 111 may provide unregulated power suitable for use with components such as contactors.
- the network power lines 113 may provide regulated power for communications.
- the data lines 115 may carry communications and/or data between the node devices 103 and the master device 101 . In one embodiment, the data lines 115 are single pair Ethernet wires.
- network cables 105 for serial networks 100 included a select line.
- the select line supported the identification of node devices 103 on network cables 105 .
- the select line was used to determine an order of the node devices 103 on the network cable 105 .
- the addition of select lines increased the cost of the serial network 100 .
- the embodiments described herein determine the order of node devices 103 on the network cable 105 without a select line.
- the order of the node devices 103 may be used to assign serial network unique and/or sequential device addresses to the node devices 103 as will be described hereafter. As a result, the order of the node devices 103 may be determined and serial network unique and/or sequential device addresses may be assigned without a select line in the network cable 105 .
- the cost of the serial network 100 is reduced.
- FIG. 2 is a schematic block diagram of network data 200 .
- the network data 200 may be used to determine the order of node devices 103 on the network cable 105 and to assign device addresses 205 to the node devices 103 .
- the network data 200 may be organized as a data structure in a memory.
- the network data 200 includes an entry 202 for each node device 103 .
- Each entry 202 may include the node device identifier 201 , an order parameter 203 , the device address 205 , and an order number 207 .
- the node device identifier 201 may be a MAC address, a serial number, a custom identifier, and the like. Each node device identifier 201 may be unique. The node device identifier 201 may be used to address the corresponding node device 103 .
- the order parameter 203 may be measured by the master device 101 in order to determine the order of the corresponding node device 103 on the network cable 105 .
- the order parameter 203 is a node voltage that is measured at the node device 103 .
- the order parameter 203 may be a node voltage of a data line 115 measured at the node device 103 .
- the order parameter 203 may be a time-of-flight for a pulse that is transmitted on the data line 115 by the master device 101 , returned as an answering pulse that is reflected by one and only one node device 103 or generated by one and only one node device 103 , and received back at the master device 101 .
- the order number 207 may indicate the place of the node device 103 on the network cable 105 .
- Table 1 illustrates one embodiment of order numbers 207 .
- the device address 205 may indicate the physical place of the node device 103 on the network cable 105 .
- the device address 205 is an Internet Protocol (IP) address.
- IP Internet Protocol
- the IP address may be serial network unique.
- the IP address may be assigned sequentially beginning with the master device 101 .
- Table 2 illustrates one embodiment of sequential IP address assignment.
- FIG. 3A is a schematic drawing of a master device 101 and a node device 103 on the serial network 100 .
- the data lines 115 are shown.
- the master device 101 and one representative node device 103 are connected to the data lines 115 .
- the master device 101 and the node device 103 each comprise a physical device 301 and/or a controller 303 .
- the physical device 301 may be a switch, a control, a display, an indicator, an actuator, and the like.
- the physical device 301 may be connected to the data lines 115 via capacitors 315 .
- the controller 303 may manage the corresponding master device 101 or node device 103 .
- the physical device 301 and controller 303 may be configured based on the functions performed by the corresponding master device 101 and/or node device 103 .
- the master device 101 includes a current source 305 .
- the current source 305 may apply a current to the data lines 115 via current connections 321 .
- the current source 305 applies the current at a specified voltage.
- the current source 305 may apply the current in response to a current command 323 from the controller 303 .
- the current command 323 may be an analog signal or a digital command.
- At least node device 103 may include a voltage circuit 313 as shown.
- the voltage circuit 313 may measure voltage between the data lines 115 at data line connections 325 .
- the voltage circuit 313 may communicate the voltage to the controller 303 via a voltage signal 327 .
- the voltage signal 327 may be a digital value.
- the voltage signal 327 may be an analog value that is converted to a digital value by an analog to digital converter at the controller 303 .
- the controller 303 may communicate the digital value of the voltage as the order parameter 203 from the node device 103 to the master device 101 .
- the controller 303 may communicate the node device identifier 201 with the order parameter 203 to the master device 101 .
- the data lines 115 between the master device 101 and/or each node device 103 comprise at least one node component 307 .
- Each node component 307 may present a constant Direct Current (DC) resistance in series with the data lines 115 of the serial network 100 .
- the node component 307 is an inductor.
- the node component 307 may also be a resistor and/or a resistor/inductor combination.
- the node component 307 may have an inductance in the range of 20 to 80 nanohenries (nH).
- the node component 307 may be disposed inside a connector of the network cable 105 .
- each node device 103 has a distinct voltage that is measured by the voltage circuit 313 .
- each node device 103 reports a distinct, unique voltage to the master device 101 , enabling the node voltage to identify the order of node devices 103 on the network cable 105 .
- the current return path is not depicted, but may be through an end of line termination.
- FIG. 3B is a schematic drawing of one embodiment of the current source 305 of FIG. 3A .
- the current command 323 turns a current generator 319 on and off.
- the current generator 319 applies the current to the data lines 115 via the current connections 321 .
- one or more current inductors 317 are in series with the current generator 319 .
- the current inductors 317 may have a constant DC resistance.
- the current source 305 may supply a voltage between the current connections 321 .
- FIG. 3C is a schematic drawing of one embodiment of the voltage circuit 313 of FIG. 3A .
- the data line connections 325 are buffered by a protection circuit 331 .
- An operational amplifier (op amp) 333 may measure the voltage at the data lines 115 and communicate the voltage signal 327 to the controller 303 of the node device 103 .
- An analog to digital converter at the controller 303 may convert the voltage signal 327 to a digital node voltage.
- FIG. 3D is a schematic drawing of the master device 101 and the node device 103 on the serial network 100 .
- the master device 101 and the node device 103 are shown connected to the data lines 115 of the network cable 105 .
- the physical device 301 is connected to the data lines 115 via capacitors 315 .
- the node device 103 includes a low impedance circuit 311 .
- the low impedance circuit 311 is connected to the data lines 115 via impedance connections 345 a - b .
- the low impedance circuit 311 may generate a low impedance such as the short across the data lines 115 .
- the master device 101 includes a pulse circuit 309 that is connected to the data lines 115 via a pulse connection 341 .
- the pulse circuit 309 may generate a pulse in response to a pulse command 353 .
- the pulse circuit 309 may further detect an answering pulse that is a reflection of the pulse at the pulse connection 341 using a voltage threshold 343 as will be described hereafter.
- the pulse circuit 309 may measure a time-of-flight 363 of the pulse as a time interval from the generation of the pulse to the detection of the answering pulse.
- the pulse circuit 309 may communicate the time-of-flight 363 as the order parameter 203 to the controller 303 .
- the data lines 115 between the master device 101 and/or each node device 103 comprise at least one node component 307 .
- Each node component 307 may present a constant DC resistance in series with the data lines 115 of the serial network 100 .
- the node component 307 is an inductor.
- the node component 307 may also be a resistor and/or a resistor/inductor combination.
- the node component 307 may have an inductance in the range of 20 to 80 nanohenries (nH).
- the node component 307 may increase the time-of-flight 363 measured between the node devices 103 , increasing the differences between the order parameters 203 .
- FIG. 3E is a schematic drawing of the pulse circuit 309 .
- the pulse circuit 309 includes a pulse generator 361 that generates the pulse on a data line 115 via the pulse connection 341 .
- the pulse command 353 initiates generation of the pulse and starts a timer 362 .
- An op amp 335 compares the voltage of the data line 115 to the voltage threshold 343 . If the voltage of the data line 115 exceeds the voltage threshold 343 a stop command 365 is generated by the op amp 335 that stops the timer 362 .
- the voltage threshold 343 may be in the range of 0.5 to 1.5 volts.
- the time interval from the start of the timer 362 to stopping the timer 362 is the time-of-flight 363 of the pulse.
- FIG. 3F is a schematic drawing of the low impedance circuit 311 of FIG. 3D .
- the low impedance command 349 closes a switch 350 that shorts the impedance connections 345 a - b .
- a low impedance component 352 is in series with the switch 350 .
- the low impedance component 352 may have a resistance of less than 50 ohms.
- FIG. 3G is a schematic drawing of a master device 101 and a node device 103 on the serial network according 100 .
- the node device 103 includes the pulse circuit 309 .
- the pulse circuit 309 of the node device 103 detects the pulse 361 a generated by the pulse circuit 309 of the master device 101 .
- the controller 303 of the node device 103 directs the pulse circuit 309 of the node device 103 to generate a response pulse as the answering pulse 361 b .
- the pulse circuit 309 of the master device 101 receives the answering pulse 361 b.
- FIG. 3H is a schematic drawing of the pulses 361 of FIGS. 3D and 3G .
- the pulse circuit 309 of the master device 101 generates a pulse 361 a that travels over the data line 115 .
- an answering pulse 361 b that is a reflection of the pulse 361 b is generated that returns to the pulse circuit 309 of the master device 101 .
- the pulse 361 a reaches the pulse circuit 309 of the node device 103 of FIG.
- an answering pulse 361 b that is a response pulse generated by the pulse circuit 309 of the node device 103 is communicated to the pulse circuit 309 of the master device 101 .
- the time interval between generating the pulse 361 a at the pulse circuit 309 and receiving the answering pulse 361 b at the pulse circuit 309 of the master device 101 is the time-of-flight 363 .
- FIG. 4 is a schematic block diagram of the controller 303 .
- the controller 303 includes a processor 405 , a memory 410 , and communication hardware 415 .
- the memory 410 may be a semiconductor storage device, a hard disk drive, or combinations thereof.
- the memory 410 stores code.
- the processor 405 executes the code.
- the communication hardware 415 may communicate with other devices.
- the communication hardware 415 may communicate with the physical device 301 .
- the communication hardware 415 may communicate with the data lines 115 .
- the communication hardware 415 communicates with a network such as an Ethernet network.
- the controller 303 includes the timer 362 .
- the controller 303 may include an analog to digital converter 420 and/or a digital to analog converter 430 .
- the analog-to-digital converter 420 may convert the voltage signal 327 to a digital value.
- the digital to analog converter 430 may generate the voltage threshold 343 .
- FIG. 5A is a schematic flow chart diagram of a device addressing method 500 .
- the method 500 may generate the order parameter 203 and the order number 207 for each node device 103 .
- the method 500 may generate the device address 205 for each node device 103 .
- the method 500 may be performed by the controller 303 and/or processor 405 of the master device 101 and/or node devices 103 .
- the method 500 starts, and in one embodiment, the processor 405 configures 501 each node device 103 on the serial network 100 for an order measurement.
- Configuring 501 each of the node devices 103 may comprise applying a specified current to the data lines 115 with the current source 305 and directing each node device 103 to report the node voltage as the order parameter 203 and a node device identifier 201 . Determining the order number 207 using the node voltage is described in more detail in FIG. 5C .
- configuring 501 each of node devices 103 comprises iteratively directing one of the node devices 103 to create a low impedance across data lines 115 of the serial network 100 with the low impedance circuit 311 and directing all other of the node devices 103 to create a high impedance across the data lines 115 with the low impedance circuit 311 . Determining the order number 207 using the time-of-flight 363 is described in more detail in FIG. 5B .
- the processor 405 further measures 503 the order parameter 203 .
- Measuring the order parameter 203 may include receiving the node voltage as the order parameter 203 and receiving the node device identifier 201 .
- measuring the order parameter 203 includes transmitting the pulse 361 a over the data lines 115 from the pulse circuit 309 , receiving an answering pulse 361 b at the pulse circuit 309 , and measuring the order parameter 203 as a time of flight 363 for the answering pulse 361 b over the data lines 115 from transmitting the pulse to receiving the answering pulse 361 b.
- the processor 405 may determine 505 the order number 207 of each of the node devices 103 based on the order parameter 203 for the node device 103 .
- the order parameter 203 is the node voltage.
- the processor 405 may determine 505 the order number 207 by ranking the node voltages from highest to lowest node voltage. Table 3 illustrates one embodiment of determining 505 the order number 207 based on node voltages.
- the processor 405 determines 505 the order number 207 by ranking the time-of-flight 363 for each node device 103 from shortest to longest time-of-flight 363 .
- Table 4 illustrates one embodiment of determining 505 the order number 207 based on the time-of-flight 363 as measured in microseconds ( ⁇ s).
- the processor 405 assigns 507 a serial network unique and/or sequential device address 205 to each of the plurality of node devices 103 based on the order number 207 of the node device 103 .
- the master device 101 may be assigned a first device address 205 and each subsequent node device 103 the assigned a serial network unique and/or sequential device address 205 based on the first device address 205 .
- Table 5 illustrates one embodiment of assigning 507 serial network unique and/or sequential device addresses 205 .
- a node device 103 is configured based on the order number 207 .
- the node device 103 may be configured based on the node device identifier 201 .
- the node device 103 is configured based on a function of the node device.
- the processor 405 may verify 508 at least one node device 103 based on the order number 207 for the node device 103 . For example, the processor 405 may verify 508 that a correct node device 103 is at a location in the network cable 105 as indicated by the order number 207 . In addition, the processor 405 may verify 508 a firmware version and/or manufacturer for at least one node device 103 .
- the processor 405 further communicates 509 with one or more node devices 103 based on the device addresses 205 and the method 500 ends. For example, continuing the example of Table 5, the processor 405 may communicate 509 with the node device 103 at IP address 192.168.1.2.
- FIG. 5B is a schematic flow chart diagram of a time-of-flight order determination method 550 .
- the method 550 may generate the order parameter 203 and the order number 207 for each node device 103 .
- the method 550 may be performed by the controller 303 and/or processor 405 of the master device 101 and/or node devices 103 .
- the method 550 starts, and in one embodiment, the processor 405 selects 551 one and only one node device 103 of the plurality of node devices 103 .
- the processor 405 may iteratively select 551 each node device 103 in turn.
- the node devices 103 are selected based on the node device identifier 201 .
- the processor 405 further directs 553 the selected node device 103 to communicate the answering pulse 361 b .
- the processor 405 may direct 553 the selected node device 103 of FIG. 3D to create a low impedance across data lines 115 to communicate the answering pulse 361 b .
- the processor 405 asserts the low impedance command 349 at the selected node device 103 . Asserting the low impedance command 349 may direct the low impedance circuit 311 to short the data lines 115 . Alternatively, asserting the low impedance command 349 may direct the low impedance circuit 311 to lower the impedance between the data lines 115 .
- the processor 405 directs 553 the selected node device 103 to generate a response pulse to communicate the answering pulse 361 b .
- the processor 405 of the selected node device 103 of FIG. 3G may receive the time-of-flight 363 from the timer 362 indicating that the pulse 361 a was received.
- the processor 405 of the selected node device 103 may assert the pulse command 353 to generate the response pulse answering pulse 361 b.
- the processor 405 further directs 555 all other of the node devices 103 not communicate the answering pulse 361 b .
- the processor 405 may direct 555 the all other of the node devices 103 of FIG. 3D to create a high impedance across the data lines 115 .
- the processors 405 of the all other node devices 103 de-assert the low impedance command 349 . De-asserting the low impedance command 349 may direct the low impedance circuit 311 to maintain the impedance between the data lines 115 .
- the processor 405 may direct 555 all other node devices of FIG. 3G to not generate the answering pulse 361 b.
- the processor 405 further transmits 557 the pulse 361 a over the data lines 115 .
- the processor 405 issues the pulse command 353 .
- the pulse circuit 309 may generate the pulse 361 a .
- the pulse 361 a is slowed by at least one node component 307 .
- the pulse 361 a is reflected by the low impedance circuit 311 of the selected node device 103 as the answering pulse 361 b .
- the answering pulse 361 b is generated by the pulse circuit 309 of the selected node device 103 as a response pulse.
- the pulse circuit 309 receives 559 the answering pulse 361 b and measures 561 the time-of-flight 363 for the answering pulse 361 b .
- the pulse circuit 309 may communicate the time-of-flight 363 to the processor 405 of the master device 101 as the order parameter 203 .
- the time-of-flight 363 may be communicated in a standard format.
- the processor 405 determines 563 if the time-of-flight 363 for each node device 103 is measured. If all time-of-flights 363 are not measured, the processor 405 selects 551 a new device node 103 . If all time-of-flights 363 are measured, the processor 405 determines 565 the order number 207 based on the order parameter 203 and the method 550 ends. For example, the order number 207 may be determined 565 as shown in Table 4.
- FIG. 5C is a schematic flow chart diagram of a node voltage order determination method 600 .
- the method 600 may generate the order parameter 203 and the order number 207 for each node device 103 .
- the method 600 may be performed by the controller 303 and/or processor 405 of the master device 101 and/or node devices 103 .
- the method 600 starts, and in one embodiment, the processor 405 applies 601 a specified current to the data lines 115 .
- the processor 405 may assert the voltage command 323 . Asserting the voltage command 323 may activate the current generator 319 .
- the processor 405 may further direct 603 each node device 103 to report a node voltage and a node device identifier 201 . In one embodiment, the processor 405 directs 603 each node device 103 to go silent and not communicate with the data lines 115 . The processor 405 may use the node device identifier 201 to direct 603 a specified node device 103 to measure the node voltage with the voltage circuit 313 . The processor 405 may further direct 603 each node device 103 to measure the node voltage after a specified quiet time interval.
- the voltage circuit 313 may communicate the voltage signal 327 to the processor 405 of the node device 103 .
- the controller 303 of the node device 103 may convert the voltage signal 327 to the node voltage and communicate the node voltage to the processor 405 of the master device 101 as the order parameter 203 .
- the processor 405 iteratively directs 603 each node device 103 to report the node voltage.
- the processor 405 directs 603 all node devices 103 to report the node voltage.
- the node devices 103 may report the node voltage along with the node device identifier 201 for each node device 103 .
- the processor 405 receives 605 the node voltage as the order parameter 203 .
- the processor 405 may receive 605 the node device identifier 201 .
- the order parameter 203 and/or node device identifier 201 may be received in a standard format.
- the processor 405 determines 607 the order number 207 based on the order parameter 203 and the method 600 ends.
- the order number 207 may be determined 607 as shown in Table 3.
- Node devices 103 are added to the network cable 105 of the serial network 100 to provide communications to the node devices 103 . While each node device 103 may be logically identified and addressed based on the node device identifier 201 , the physical order of node devices 103 on the network cable 105 may be unknown.
- the embodiments configure each node device 103 on the serial network 100 for an order measurement.
- the embodiments further measure the order parameter 203 for each of the node devices 103 .
- the embodiments determine the order number 207 for each of the node devices 103 based on the order parameter 203 for the node device 103 .
- the embodiments assign a serial network unique and/or sequential device address 205 to each of the node devices 103 based on the order number 207 of the node device 103 .
- the physical order of the node devices 103 may be identified based on the device address 205 .
- a node device 103 may be physical identified and/or located on the network cable 105 .
Abstract
Description
- An apparatus for automatic device ordering is disclosed. The apparatus includes a processor and a memory storing code executable by the processor. The processor configures each node device on a serial network for an order measurement. The processor further measures an order parameter for each of the node devices. The processor determines an order number of each of the node devices based on the order parameter for the node device.
- A method for automatic device ordering is also disclosed. The method configures, by use of a processor, each node device on a serial network for an order measurement. The method measures an order parameter for each of the node devices. The method determines an order number of each of the node devices based on the order parameter for the node device.
- A computer program product for automatic device ordering is also disclosed. The computer program product comprises a non-transitory computer readable storage medium having code embodied therein. The code is readable/executable by a processor. The processor configures each node device on a serial network for an order measurement. The processor further measures an order parameter for each of the node devices. The processor determines an order number of each of the node devices based on the order parameter for the node device.
- In order that the advantages of the embodiments of the invention will be readily understood, a more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
-
FIG. 1A is a schematic block diagram of serial network according to an embodiment; -
FIG. 1B is a schematic drawing of a network cable according to an embodiment; -
FIG. 2 is a schematic block diagram of network data according to an embodiment; -
FIG. 3A is a schematic drawing of a master device and a node device on the serial network according to an embodiment; -
FIG. 3B is a schematic drawing of a current source according to an embodiment; -
FIG. 3C is a schematic drawing of a voltage circuit according to an embodiment; -
FIG. 3D is a schematic drawing of a master device and a node device on the serial network according to an alternate embodiment; -
FIG. 3E is a schematic drawing of a pulse circuit according to an embodiment; -
FIG. 3F is a schematic drawing of a low impedance circuit according to an embodiment; -
FIG. 3G is a schematic drawing of a master device and a node device on the serial network according to an alternate embodiment; -
FIG. 3H is a schematic drawing of pulses according to an embodiment; -
FIG. 4 is a schematic block diagram of a controller according to an embodiment; -
FIG. 5A is a schematic flow chart diagram of a device addressing method according to an embodiment; -
FIG. 5B is a schematic flow chart diagram of a time-of-flight order determination method according to an embodiment; and -
FIG. 5C is a schematic flow chart diagram of a node voltage order determination method according to an embodiment. - Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise. The term “and/or” indicates embodiments of one or more of the listed elements, with “A and/or B” indicating embodiments of element A alone, element B alone, or elements A and B taken together.
- Furthermore, the described features, advantages, and characteristics of the embodiments may be combined in any suitable manner. One skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.
- These features and advantages of the embodiments will become more fully apparent from the following description and appended claims or may be learned by the practice of embodiments as set forth hereinafter. As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, and/or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having program code embodied thereon.
- Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
- Modules may also be implemented in software for execution by various types of processors. An identified module of program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
- Indeed, a module of program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the program code may be stored and/or propagated on in one or more computer readable medium(s).
- The computer readable medium may be a tangible computer readable storage medium storing the program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
- More specific examples of the computer readable storage medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, and/or store program code for use by and/or in connection with an instruction execution system, apparatus, or device.
- The computer readable medium may also be a computer readable signal medium. A computer readable signal medium may include a propagated data signal with program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electrical, electro-magnetic, magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport program code for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireline, optical fiber, Radio Frequency (RF), or the like, or any suitable combination of the foregoing
- In one embodiment, the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums. For example, program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.
- Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, C sharp, Lisp, Clojure, PHP or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). The computer program product may be shared, simultaneously serving multiple customers in a flexible, automated fashion.
- The computer program product may be integrated into a client, server and network environment by providing for the computer program product to coexist with applications, operating systems and network operating systems software and then installing the computer program product on the clients and servers in the environment where the computer program product will function. In one embodiment software is identified on the clients and servers including the network operating system where the computer program product will be deployed that are required by the computer program product or that work in conjunction with the computer program product. This includes the network operating system that is software that enhances a basic operating system by adding networking features.
- Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
- The embodiments may transmit data between electronic devices. The embodiments may further convert the data from a first format to a second format, including converting the data from a non-standard format to a standard format and/or converting the data from the standard format to a non-standard format. The embodiments may modify, update, and/or process the data. The embodiments may store the received, converted, modified, updated, and/or processed data. The embodiments may provide remote access to the data including the updated data. The embodiments may make the data and/or updated data available in real time. The embodiments may generate and transmit a message based on the data and/or updated data in real time.
- Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the invention. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by program code. The program code may be provided to a processor of a general purpose computer, special purpose computer, sequencer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- The program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
- The program code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the program code which executed on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code for implementing the specified logical function(s).
- It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
- Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and program code.
- The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
-
FIG. 1A is a schematic block diagram of aserial network 100. Theserial network 100 provides communications between the plurality of devices. In the depicted embodiment, theserial network 100 includes amaster device 101, a plurality ofnode devices 103, and anetwork cable 105. Themaster device 101 may communicate with and/or control the plurality ofnode devices 103. In addition, themaster device 101 may communicate with networks and/or devices outside of theserial network 100. For example, themaster device 101 may communicate with the local area network. Thenode devices 103 may communicate with networks and/or devices through themaster device 101. - The
network cable 105 functions as a multi-drop bus.Node devices 103 may be added to thenetwork cable 105 as needed. For example, aswitch node device 103 may be added to an automation system by physically installing theswitch node device 103 the automation system and connecting theswitch node device 103 to thenetwork cable 105. Themaster device 101 may discover theswitch node device 103 and communicate with theswitch node device 103. As a result, inputs to theswitch node device 103 are communicated to themaster device 101 and/or upstream networks and/or devices outside of theserial network 100. Thus, theserial network 100 supports the convenient addition ofnode devices 103. - The
master device 101 andnode devices 103 may each have a node device identifier. In one embodiment, the node device identifier is a Media Access Control (MAC) address. The node device identifier is used to logically identify and address acorresponding node device 103. In addition, it is often desirable to physically identify the place of anode device 103 on thenetwork cable 105. For example, a user may need to physically identify anode device 103 as athird node device 103 on thenetwork cable 105 in order to service thenode device 103. The place of thenode device 103 on thenetwork cable 105 may be indicated using a device address. In one embodiment, a serial network unique but non-sequential device address is assigned for each location. -
FIG. 1B is a schematic drawing of thenetwork cable 105. In the depicted embodiment, thenetwork cable 105 is a ribbon cable. The network cable includes switched power lines 111, network power lines 113, and data lines 115. The switched power lines 111 may provide unregulated power suitable for use with components such as contactors. The network power lines 113 may provide regulated power for communications. The data lines 115 may carry communications and/or data between thenode devices 103 and themaster device 101. In one embodiment, the data lines 115 are single pair Ethernet wires. - In the past,
network cables 105 forserial networks 100 included a select line. The select line supported the identification ofnode devices 103 onnetwork cables 105. The select line was used to determine an order of thenode devices 103 on thenetwork cable 105. Unfortunately, the addition of select lines increased the cost of theserial network 100. The embodiments described herein determine the order ofnode devices 103 on thenetwork cable 105 without a select line. The order of thenode devices 103 may be used to assign serial network unique and/or sequential device addresses to thenode devices 103 as will be described hereafter. As a result, the order of thenode devices 103 may be determined and serial network unique and/or sequential device addresses may be assigned without a select line in thenetwork cable 105. Thus, the cost of theserial network 100 is reduced. -
FIG. 2 is a schematic block diagram ofnetwork data 200. Thenetwork data 200 may be used to determine the order ofnode devices 103 on thenetwork cable 105 and to assign device addresses 205 to thenode devices 103. Thenetwork data 200 may be organized as a data structure in a memory. In the depicted embodiment, thenetwork data 200 includes anentry 202 for eachnode device 103. Eachentry 202 may include the node device identifier 201, an order parameter 203, the device address 205, and an order number 207. - The node device identifier 201 may be a MAC address, a serial number, a custom identifier, and the like. Each node device identifier 201 may be unique. The node device identifier 201 may be used to address the
corresponding node device 103. - The order parameter 203 may be measured by the
master device 101 in order to determine the order of thecorresponding node device 103 on thenetwork cable 105. In one embodiment, the order parameter 203 is a node voltage that is measured at thenode device 103. For example, the order parameter 203 may be a node voltage of a data line 115 measured at thenode device 103. In an alternative embodiment, the order parameter 203 may be a time-of-flight for a pulse that is transmitted on the data line 115 by themaster device 101, returned as an answering pulse that is reflected by one and only onenode device 103 or generated by one and only onenode device 103, and received back at themaster device 101. - The order number 207 may indicate the place of the
node device 103 on thenetwork cable 105. Table 1 illustrates one embodiment of order numbers 207. -
TABLE 1 Device 101/103Order Number 207 Master Device 1010 First Node Device 1031 Second Node Device 1032 Third Node Device 1033 Fourth Node Device 1034 - The device address 205 may indicate the physical place of the
node device 103 on thenetwork cable 105. In one embodiment, the device address 205 is an Internet Protocol (IP) address. The IP address may be serial network unique. The IP address may be assigned sequentially beginning with themaster device 101. Table 2 illustrates one embodiment of sequential IP address assignment. -
TABLE 2 Device 101/103Device Address 205 Master Device 101192.168.1.0 First Node Device 103192.168.1.1 Second Node Device 103192.168.1.2 Third Node Device 103192.168.1.3 Fourth Node Device 103192.168.1.4 -
FIG. 3A is a schematic drawing of amaster device 101 and anode device 103 on theserial network 100. In the depicted embodiment, the data lines 115 are shown. Themaster device 101 and onerepresentative node device 103 are connected to the data lines 115. In one embodiment, themaster device 101 and thenode device 103 each comprise aphysical device 301 and/or acontroller 303. Thephysical device 301 may be a switch, a control, a display, an indicator, an actuator, and the like. Thephysical device 301 may be connected to the data lines 115 viacapacitors 315. Thecontroller 303 may manage the correspondingmaster device 101 ornode device 103. Thephysical device 301 andcontroller 303 may be configured based on the functions performed by the correspondingmaster device 101 and/ornode device 103. - In the depicted embodiment, the
master device 101 includes acurrent source 305. Thecurrent source 305 may apply a current to the data lines 115 viacurrent connections 321. In a certain embodiment, thecurrent source 305 applies the current at a specified voltage. Thecurrent source 305 may apply the current in response to acurrent command 323 from thecontroller 303. Thecurrent command 323 may be an analog signal or a digital command. - In addition, at
least node device 103 may include avoltage circuit 313 as shown. Thevoltage circuit 313 may measure voltage between the data lines 115 atdata line connections 325. Thevoltage circuit 313 may communicate the voltage to thecontroller 303 via avoltage signal 327. Thevoltage signal 327 may be a digital value. Alternatively, thevoltage signal 327 may be an analog value that is converted to a digital value by an analog to digital converter at thecontroller 303. Thecontroller 303 may communicate the digital value of the voltage as the order parameter 203 from thenode device 103 to themaster device 101. In addition, thecontroller 303 may communicate the node device identifier 201 with the order parameter 203 to themaster device 101. - In one embodiment, the data lines 115 between the
master device 101 and/or eachnode device 103 comprise at least onenode component 307. Eachnode component 307 may present a constant Direct Current (DC) resistance in series with the data lines 115 of theserial network 100. In the depicted embodiment, thenode component 307 is an inductor. Thenode component 307 may also be a resistor and/or a resistor/inductor combination. Thenode component 307 may have an inductance in the range of 20 to 80 nanohenries (nH). - The
node component 307 may be disposed inside a connector of thenetwork cable 105. As a result, as thecurrent source 305 applies the current to the data lines 115, eachnode device 103 has a distinct voltage that is measured by thevoltage circuit 313. Thus, eachnode device 103 reports a distinct, unique voltage to themaster device 101, enabling the node voltage to identify the order ofnode devices 103 on thenetwork cable 105. The current return path is not depicted, but may be through an end of line termination. -
FIG. 3B is a schematic drawing of one embodiment of thecurrent source 305 ofFIG. 3A . In the depicted embodiment, thecurrent command 323 turns acurrent generator 319 on and off. Thecurrent generator 319 applies the current to the data lines 115 via thecurrent connections 321. In one embodiment, one or morecurrent inductors 317 are in series with thecurrent generator 319. Thecurrent inductors 317 may have a constant DC resistance. As a result, thecurrent source 305 may supply a voltage between thecurrent connections 321. -
FIG. 3C is a schematic drawing of one embodiment of thevoltage circuit 313 ofFIG. 3A . In the depicted embodiment, thedata line connections 325 are buffered by aprotection circuit 331. An operational amplifier (op amp) 333 may measure the voltage at the data lines 115 and communicate thevoltage signal 327 to thecontroller 303 of thenode device 103. An analog to digital converter at thecontroller 303 may convert thevoltage signal 327 to a digital node voltage. -
FIG. 3D is a schematic drawing of themaster device 101 and thenode device 103 on theserial network 100. Themaster device 101 and thenode device 103 are shown connected to the data lines 115 of thenetwork cable 105. Thephysical device 301 is connected to the data lines 115 viacapacitors 315. - In the depicted embodiment, the
node device 103 includes alow impedance circuit 311. Thelow impedance circuit 311 is connected to the data lines 115 via impedance connections 345 a-b. In response to alow impedance command 349 from thecontroller 303, thelow impedance circuit 311 may generate a low impedance such as the short across the data lines 115. - In the depicted embodiment, the
master device 101 includes apulse circuit 309 that is connected to the data lines 115 via apulse connection 341. Thepulse circuit 309 may generate a pulse in response to apulse command 353. Thepulse circuit 309 may further detect an answering pulse that is a reflection of the pulse at thepulse connection 341 using avoltage threshold 343 as will be described hereafter. Thepulse circuit 309 may measure a time-of-flight 363 of the pulse as a time interval from the generation of the pulse to the detection of the answering pulse. Thepulse circuit 309 may communicate the time-of-flight 363 as the order parameter 203 to thecontroller 303. - In one embodiment, the data lines 115 between the
master device 101 and/or eachnode device 103 comprise at least onenode component 307. Eachnode component 307 may present a constant DC resistance in series with the data lines 115 of theserial network 100. In the depicted embodiment, thenode component 307 is an inductor. Thenode component 307 may also be a resistor and/or a resistor/inductor combination. Thenode component 307 may have an inductance in the range of 20 to 80 nanohenries (nH). Thenode component 307 may increase the time-of-flight 363 measured between thenode devices 103, increasing the differences between the order parameters 203. -
FIG. 3E is a schematic drawing of thepulse circuit 309. Thepulse circuit 309 includes apulse generator 361 that generates the pulse on a data line 115 via thepulse connection 341. Thepulse command 353 initiates generation of the pulse and starts atimer 362. Anop amp 335 compares the voltage of the data line 115 to thevoltage threshold 343. If the voltage of the data line 115 exceeds the voltage threshold 343 astop command 365 is generated by theop amp 335 that stops thetimer 362. Thevoltage threshold 343 may be in the range of 0.5 to 1.5 volts. The time interval from the start of thetimer 362 to stopping thetimer 362 is the time-of-flight 363 of the pulse. -
FIG. 3F is a schematic drawing of thelow impedance circuit 311 ofFIG. 3D . In the depicted embodiment, thelow impedance command 349 closes aswitch 350 that shorts the impedance connections 345 a-b. In one embodiment, alow impedance component 352 is in series with theswitch 350. Thelow impedance component 352 may have a resistance of less than 50 ohms. -
FIG. 3G is a schematic drawing of amaster device 101 and anode device 103 on the serial network according 100. Thenode device 103 includes thepulse circuit 309. In the depicted embodiment, thepulse circuit 309 of thenode device 103 detects thepulse 361 a generated by thepulse circuit 309 of themaster device 101. In response to thenode device 103 detecting thepulse 361 a, thecontroller 303 of thenode device 103 directs thepulse circuit 309 of thenode device 103 to generate a response pulse as the answeringpulse 361 b. Thepulse circuit 309 of themaster device 101 receives the answeringpulse 361 b. -
FIG. 3H is a schematic drawing of thepulses 361 ofFIGS. 3D and 3G . In the depicted embodiment, thepulse circuit 309 of themaster device 101 generates apulse 361 a that travels over the data line 115. When thepulse 361 a reaches thelow impedance circuit 311 ofFIG. 3D , an answeringpulse 361 b that is a reflection of thepulse 361 b is generated that returns to thepulse circuit 309 of themaster device 101. Alternatively, when thepulse 361 a reaches thepulse circuit 309 of thenode device 103 ofFIG. 3G , an answeringpulse 361 b that is a response pulse generated by thepulse circuit 309 of thenode device 103 is communicated to thepulse circuit 309 of themaster device 101. The time interval between generating thepulse 361 a at thepulse circuit 309 and receiving the answeringpulse 361 b at thepulse circuit 309 of themaster device 101 is the time-of-flight 363. -
FIG. 4 is a schematic block diagram of thecontroller 303. In the depicted embodiment, thecontroller 303 includes aprocessor 405, amemory 410, andcommunication hardware 415. Thememory 410 may be a semiconductor storage device, a hard disk drive, or combinations thereof. Thememory 410 stores code. Theprocessor 405 executes the code. Thecommunication hardware 415 may communicate with other devices. For example, thecommunication hardware 415 may communicate with thephysical device 301. In addition, thecommunication hardware 415 may communicate with the data lines 115. In a certain embodiment, thecommunication hardware 415 communicates with a network such as an Ethernet network. - In one embodiment, the
controller 303 includes thetimer 362. In addition, thecontroller 303 may include an analog todigital converter 420 and/or a digital toanalog converter 430. The analog-to-digital converter 420 may convert thevoltage signal 327 to a digital value. The digital toanalog converter 430 may generate thevoltage threshold 343. -
FIG. 5A is a schematic flow chart diagram of adevice addressing method 500. Themethod 500 may generate the order parameter 203 and the order number 207 for eachnode device 103. In addition, themethod 500 may generate the device address 205 for eachnode device 103. Themethod 500 may be performed by thecontroller 303 and/orprocessor 405 of themaster device 101 and/ornode devices 103. - The
method 500 starts, and in one embodiment, theprocessor 405 configures 501 eachnode device 103 on theserial network 100 for an order measurement. Configuring 501 each of thenode devices 103 may comprise applying a specified current to the data lines 115 with thecurrent source 305 and directing eachnode device 103 to report the node voltage as the order parameter 203 and a node device identifier 201. Determining the order number 207 using the node voltage is described in more detail inFIG. 5C . - Alternatively, configuring 501 each of
node devices 103 comprises iteratively directing one of thenode devices 103 to create a low impedance across data lines 115 of theserial network 100 with thelow impedance circuit 311 and directing all other of thenode devices 103 to create a high impedance across the data lines 115 with thelow impedance circuit 311. Determining the order number 207 using the time-of-flight 363 is described in more detail inFIG. 5B . - The
processor 405further measures 503 the order parameter 203. Measuring the order parameter 203 may include receiving the node voltage as the order parameter 203 and receiving the node device identifier 201. Alternatively, measuring the order parameter 203 includes transmitting thepulse 361 a over the data lines 115 from thepulse circuit 309, receiving an answeringpulse 361 b at thepulse circuit 309, and measuring the order parameter 203 as a time offlight 363 for the answeringpulse 361 b over the data lines 115 from transmitting the pulse to receiving the answeringpulse 361 b. - The
processor 405 may determine 505 the order number 207 of each of thenode devices 103 based on the order parameter 203 for thenode device 103. In one embodiment, the order parameter 203 is the node voltage. Theprocessor 405 may determine 505 the order number 207 by ranking the node voltages from highest to lowest node voltage. Table 3 illustrates one embodiment of determining 505 the order number 207 based on node voltages. -
TABLE 3 Node Voltage Order Number 207 4.5 V 1 3.5 V 2 2.5 V 3 1.5 V 4 - In an alternative embodiment, the
processor 405 determines 505 the order number 207 by ranking the time-of-flight 363 for eachnode device 103 from shortest to longest time-of-flight 363. Table 4 illustrates one embodiment of determining 505 the order number 207 based on the time-of-flight 363 as measured in microseconds (μs). -
TABLE 4 Time-of- Flight 363Order Number 207 0.4 μs 1 0.7 μs 2 1.1 μs 3 1.4 μs 4 - In one embodiment, the
processor 405 assigns 507 a serial network unique and/or sequential device address 205 to each of the plurality ofnode devices 103 based on the order number 207 of thenode device 103. For example, themaster device 101 may be assigned a first device address 205 and eachsubsequent node device 103 the assigned a serial network unique and/or sequential device address 205 based on the first device address 205. Table 5 illustrates one embodiment of assigning 507 serial network unique and/or sequential device addresses 205. -
TABLE 5 Order Number 207 Device Address 205 Master Device 101192.168.1.0 1 192.168.1.1 2 192.168.1.2 3 192.168.1.3 4 192.168.1.4 - In one embodiment, a
node device 103 is configured based on the order number 207. In addition, thenode device 103 may be configured based on the node device identifier 201. In a certain embodiment, thenode device 103 is configured based on a function of the node device. - The
processor 405 may verify 508 at least onenode device 103 based on the order number 207 for thenode device 103. For example, theprocessor 405 may verify 508 that acorrect node device 103 is at a location in thenetwork cable 105 as indicated by the order number 207. In addition, theprocessor 405 may verify 508 a firmware version and/or manufacturer for at least onenode device 103. - In one embodiment, the
processor 405 further communicates 509 with one ormore node devices 103 based on the device addresses 205 and themethod 500 ends. For example, continuing the example of Table 5, theprocessor 405 may communicate 509 with thenode device 103 at IP address 192.168.1.2. -
FIG. 5B is a schematic flow chart diagram of a time-of-flightorder determination method 550. Themethod 550 may generate the order parameter 203 and the order number 207 for eachnode device 103. Themethod 550 may be performed by thecontroller 303 and/orprocessor 405 of themaster device 101 and/ornode devices 103. - The
method 550 starts, and in one embodiment, theprocessor 405 selects 551 one and only onenode device 103 of the plurality ofnode devices 103. Theprocessor 405 may iteratively select 551 eachnode device 103 in turn. In one embodiment, thenode devices 103 are selected based on the node device identifier 201. - The
processor 405 further directs 553 the selectednode device 103 to communicate the answeringpulse 361 b. Theprocessor 405 may direct 553 the selectednode device 103 ofFIG. 3D to create a low impedance across data lines 115 to communicate the answeringpulse 361 b. In one embodiment, theprocessor 405 asserts thelow impedance command 349 at the selectednode device 103. Asserting thelow impedance command 349 may direct thelow impedance circuit 311 to short the data lines 115. Alternatively, asserting thelow impedance command 349 may direct thelow impedance circuit 311 to lower the impedance between the data lines 115. - In one embodiment, the
processor 405 directs 553 the selectednode device 103 to generate a response pulse to communicate the answeringpulse 361 b. For example, in response to the selection, theprocessor 405 of the selectednode device 103 ofFIG. 3G may receive the time-of-flight 363 from thetimer 362 indicating that thepulse 361 a was received. Theprocessor 405 of the selectednode device 103 may assert thepulse command 353 to generate the responsepulse answering pulse 361 b. - The
processor 405 further directs 555 all other of thenode devices 103 not communicate the answeringpulse 361 b. Theprocessor 405 may direct 555 the all other of thenode devices 103 ofFIG. 3D to create a high impedance across the data lines 115. In one embodiment, theprocessors 405 of the allother node devices 103 de-assert thelow impedance command 349. De-asserting thelow impedance command 349 may direct thelow impedance circuit 311 to maintain the impedance between the data lines 115. - Alternatively, the
processor 405 may direct 555 all other node devices ofFIG. 3G to not generate the answeringpulse 361 b. - The
processor 405further transmits 557 thepulse 361 a over the data lines 115. In one embodiment, theprocessor 405 issues thepulse command 353. In response to thepulse command 353, thepulse circuit 309 may generate thepulse 361 a. In one embodiment, thepulse 361 a is slowed by at least onenode component 307. Thepulse 361 a is reflected by thelow impedance circuit 311 of the selectednode device 103 as the answeringpulse 361 b. Alternatively, the answeringpulse 361 b is generated by thepulse circuit 309 of the selectednode device 103 as a response pulse. Thepulse circuit 309 receives 559 the answeringpulse 361 b and measures 561 the time-of-flight 363 for the answeringpulse 361 b. Thepulse circuit 309 may communicate the time-of-flight 363 to theprocessor 405 of themaster device 101 as the order parameter 203. The time-of-flight 363 may be communicated in a standard format. - The
processor 405 determines 563 if the time-of-flight 363 for eachnode device 103 is measured. If all time-of-flights 363 are not measured, theprocessor 405 selects 551 anew device node 103. If all time-of-flights 363 are measured, theprocessor 405 determines 565 the order number 207 based on the order parameter 203 and themethod 550 ends. For example, the order number 207 may be determined 565 as shown in Table 4. -
FIG. 5C is a schematic flow chart diagram of a node voltageorder determination method 600. Themethod 600 may generate the order parameter 203 and the order number 207 for eachnode device 103. Themethod 600 may be performed by thecontroller 303 and/orprocessor 405 of themaster device 101 and/ornode devices 103. - The
method 600 starts, and in one embodiment, theprocessor 405 applies 601 a specified current to the data lines 115. Theprocessor 405 may assert thevoltage command 323. Asserting thevoltage command 323 may activate thecurrent generator 319. - The
processor 405 may further direct 603 eachnode device 103 to report a node voltage and a node device identifier 201. In one embodiment, theprocessor 405 directs 603 eachnode device 103 to go silent and not communicate with the data lines 115. Theprocessor 405 may use the node device identifier 201 to direct 603 a specifiednode device 103 to measure the node voltage with thevoltage circuit 313. Theprocessor 405 may further direct 603 eachnode device 103 to measure the node voltage after a specified quiet time interval. - The
voltage circuit 313 may communicate thevoltage signal 327 to theprocessor 405 of thenode device 103. Thecontroller 303 of thenode device 103 may convert thevoltage signal 327 to the node voltage and communicate the node voltage to theprocessor 405 of themaster device 101 as the order parameter 203. - In one embodiment, the
processor 405 iteratively directs 603 eachnode device 103 to report the node voltage. Alternatively, theprocessor 405 directs 603 allnode devices 103 to report the node voltage. Thenode devices 103 may report the node voltage along with the node device identifier 201 for eachnode device 103. - The
processor 405 receives 605 the node voltage as the order parameter 203. In addition, theprocessor 405 may receive 605 the node device identifier 201. The order parameter 203 and/or node device identifier 201 may be received in a standard format. - The
processor 405 determines 607 the order number 207 based on the order parameter 203 and themethod 600 ends. The order number 207 may be determined 607 as shown in Table 3. - Problem/Solution
-
Node devices 103 are added to thenetwork cable 105 of theserial network 100 to provide communications to thenode devices 103. While eachnode device 103 may be logically identified and addressed based on the node device identifier 201, the physical order ofnode devices 103 on thenetwork cable 105 may be unknown. The embodiments configure eachnode device 103 on theserial network 100 for an order measurement. The embodiments further measure the order parameter 203 for each of thenode devices 103. The embodiments determine the order number 207 for each of thenode devices 103 based on the order parameter 203 for thenode device 103. The embodiments assign a serial network unique and/or sequential device address 205 to each of thenode devices 103 based on the order number 207 of thenode device 103. As a result, the physical order of thenode devices 103 may be identified based on the device address 205. Thus, anode device 103 may be physical identified and/or located on thenetwork cable 105. - This description uses examples to disclose the invention and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/985,423 US20220043135A1 (en) | 2020-08-05 | 2020-08-05 | Automatic device ordering |
EP21185483.1A EP3961998A1 (en) | 2020-08-05 | 2021-07-14 | Automatic device ordering |
US18/160,517 US20230168357A1 (en) | 2020-08-05 | 2023-01-27 | Automatic device ordering |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/985,423 US20220043135A1 (en) | 2020-08-05 | 2020-08-05 | Automatic device ordering |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/160,517 Continuation US20230168357A1 (en) | 2020-08-05 | 2023-01-27 | Automatic device ordering |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220043135A1 true US20220043135A1 (en) | 2022-02-10 |
Family
ID=77249664
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/985,423 Abandoned US20220043135A1 (en) | 2020-08-05 | 2020-08-05 | Automatic device ordering |
US18/160,517 Pending US20230168357A1 (en) | 2020-08-05 | 2023-01-27 | Automatic device ordering |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/160,517 Pending US20230168357A1 (en) | 2020-08-05 | 2023-01-27 | Automatic device ordering |
Country Status (2)
Country | Link |
---|---|
US (2) | US20220043135A1 (en) |
EP (1) | EP3961998A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6542946B1 (en) * | 2000-01-28 | 2003-04-01 | Compaq Information Technologies Group, L.P. | Dual mode differential transceiver for a universal serial bus |
US7486104B2 (en) * | 2006-06-02 | 2009-02-03 | Rambus Inc. | Integrated circuit with graduated on-die termination |
US20150244370A1 (en) * | 2011-02-02 | 2015-08-27 | Rambus Inc. | On-Die Termination |
US20210320683A1 (en) * | 2020-04-13 | 2021-10-14 | Samsung Electro-Mechanics Co., Ltd. | Front-end module |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9934191B2 (en) * | 2014-07-31 | 2018-04-03 | Neofocal Systems, Inc. | Systems and methods for assigning addresses to serially arranged circuit nodes |
EP3419225B1 (en) * | 2017-06-21 | 2020-03-18 | Nxp B.V. | System and method allowing for determining relative positions of slave units along a stub bus |
DE102018104489A1 (en) * | 2018-02-27 | 2019-08-29 | Elmos Semiconductor Aktiengesellschaft | Self-testable bus system and use of this self-test capability for the assignment of bus node addresses with possibility of mixing |
-
2020
- 2020-08-05 US US16/985,423 patent/US20220043135A1/en not_active Abandoned
-
2021
- 2021-07-14 EP EP21185483.1A patent/EP3961998A1/en active Pending
-
2023
- 2023-01-27 US US18/160,517 patent/US20230168357A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6542946B1 (en) * | 2000-01-28 | 2003-04-01 | Compaq Information Technologies Group, L.P. | Dual mode differential transceiver for a universal serial bus |
US7486104B2 (en) * | 2006-06-02 | 2009-02-03 | Rambus Inc. | Integrated circuit with graduated on-die termination |
US20150244370A1 (en) * | 2011-02-02 | 2015-08-27 | Rambus Inc. | On-Die Termination |
US20210320683A1 (en) * | 2020-04-13 | 2021-10-14 | Samsung Electro-Mechanics Co., Ltd. | Front-end module |
Also Published As
Publication number | Publication date |
---|---|
US20230168357A1 (en) | 2023-06-01 |
EP3961998A1 (en) | 2022-03-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108153670A (en) | A kind of interface test method, device and electronic equipment | |
US10387282B2 (en) | Test unit and test method for efficient testing during long idle periods | |
US7346814B2 (en) | System and method for controlling power sources of motherboards under test through networks | |
US20220043135A1 (en) | Automatic device ordering | |
CN113765733A (en) | Bus network testing method and device | |
CN105338129B (en) | Automatically divide location method, display terminal and modular terminal | |
EP3016351B1 (en) | Method for operating a sensor arrangement with multiple sensor devices, sensor device, sensor arrangement and sensor system | |
US8805566B2 (en) | Product line management system and method thereof | |
EP3819728A1 (en) | Automatic device naming for fast device replacement | |
KR20000047471A (en) | Dynamic burn rack monitor listener server | |
US20170273096A1 (en) | Wireless communication device, wireless communication system, and wireless communication method | |
CN104869580A (en) | Radio frequency automation test system and method | |
CN106294146B (en) | Parameter replacement test method and device | |
CA3112110A1 (en) | Method of assigning addresses to bus participants | |
CN109491852A (en) | A kind of automotive electronics detection device positioning system and method | |
CN112956160B (en) | System for providing a sequence of nodes in a network | |
CN106712990A (en) | Method and system for deploying service | |
CN110866986A (en) | Inspection method | |
TW202024915A (en) | Lighting controlling system based on testing status and method thereof | |
KR102085731B1 (en) | Interconnection Evaluation System for Switchboard | |
KR20190101141A (en) | Programmable logic controller system | |
US20220083489A1 (en) | Bi-directional bus topology | |
CN116866236B (en) | Router reliability batch test method, system, terminal and storage medium | |
US11575409B2 (en) | Time-domain reflectometer distance measurement for devices sharing a common bus | |
US11956316B2 (en) | Vehicle-mounted apparatus, vehicle-mounted communication system, and communication management method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ROCKWELL AUTOMATION TECHNOLOGIES, INC., OHIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRIFFITHS, SCOTT T.;KOCZWARA, WOJCIECH;BRANDT, DAVID D.;AND OTHERS;SIGNING DATES FROM 20200803 TO 20200805;REEL/FRAME:053405/0389 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |