WO2014062700A1 - Système de gestion de dispositifs combinés (cdms) - Google Patents

Système de gestion de dispositifs combinés (cdms) Download PDF

Info

Publication number
WO2014062700A1
WO2014062700A1 PCT/US2013/065084 US2013065084W WO2014062700A1 WO 2014062700 A1 WO2014062700 A1 WO 2014062700A1 US 2013065084 W US2013065084 W US 2013065084W WO 2014062700 A1 WO2014062700 A1 WO 2014062700A1
Authority
WO
WIPO (PCT)
Prior art keywords
pins
signal
signals
management system
providing
Prior art date
Application number
PCT/US2013/065084
Other languages
English (en)
Inventor
Gregory Austin SMYTH
Original Assignee
Ultra Electronics, ProLogic
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ultra Electronics, ProLogic filed Critical Ultra Electronics, ProLogic
Publication of WO2014062700A1 publication Critical patent/WO2014062700A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/409—Mechanical coupling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/4068—Electrical coupling

Definitions

  • CDMS COMBINED DEVICE MANAGEMENT SYSTEM
  • the disclosed subject matter pertains to systems and methods for managing multiple devices, and more particularly, systems and methods that employ a single device to command and control multiple terminals and network devices.
  • a device management system includes a common bus configured to be communicatively coupled to a plurality of devices.
  • the device management system also includes a plurality of connectors.
  • Each of the connectors is configured to communicatively couple the common bus to a respective one of the devices and includes a plurality of conducting elements.
  • the plurality of conducting elements transmits signals between the common bus and the respective one of the devices.
  • the signals include: at least one power supply signal, at least one voice signal, at least one display signal, at least one serial communication signal, at least one request signal, at least one reset signal, at least one security signal, and at least one address signal.
  • a device management system includes a controller card.
  • the controller card includes at least one processor configured to manage communications between devices communicatively coupled to the device management system and at least one connector.
  • the at least one connector is configured to communicatively couple the controller to at least one input/output device and includes a plurality of conducting elements.
  • the plurality of conducting elements transmits signals between the controller card and the at least one input/output device.
  • the signals include: at least one power supply signal, at least one ground signal, at least one security signal, at least one display signal, and at least one voice signals.
  • a device management system includes a low volume terminal (LVT) card.
  • the LVT card includes at least one connector configured to communicatively couple the LVT card to at least one input/output device.
  • the at least one connector also includes a plurality of conducting elements transmitting signals between the LVT card and the at least one input/output device.
  • the signals include: at least one power supply signal, at least one standby signal, at least one ground signal, at least one zeroize signal, at least one long term transmit inhibit (LTTI) signal, at least one alarm signal, at least one voice signal, at least one push-to-talk signal, at least one voice signal, and at least one power control signal.
  • LTTI long term transmit inhibit
  • a device management system includes a small tactical terminal (STT) card.
  • the STT card includes at least one connector configured to communicatively couple the STT card to at least one input/output device.
  • the connector includes a plurality of conducting elements transmitting signals between the STT card and the at least one input/output device.
  • the signals include: at least one zeroize signal, at least one ground signal, at least one network selection signal, at least one voice signal, and at least one speaker output signal.
  • a device management system includes an STT card.
  • the STT card includes at least one connector configured to communicatively couple the STT card to at least one input/output device.
  • the connector includes a plurality of conducting elements transmitting signals between the STT card and the at least one input/output device.
  • the signals include: at least one power signal, at least one ground signal, at least one channel fail signal, at least one long term transmit inhibit (LTTI) signal, at least one emergency signal, at least one small tactical terminal-V (STT-V) fail signal, and at least one power control signal.
  • LTTI long term transmit inhibit
  • STT-V small tactical terminal-V
  • FIG. 1 illustrates an overview of the CDMS, according to aspects of the presently disclosed subject matter
  • FIG. 2 illustrates a CDMS interfacing with one or more remote physical devices via one or more equipment connections and with a web browser via a network connection according to aspects of the presently disclosed subject matter;
  • FIG. 3 illustrates an exemplary 48-pin common bus connector
  • FIG. 4 illustrates an exemplary controller card external connector layout
  • FIG. 5 illustrates an exemplary low volume terminal (LVT) card external connector layout
  • FIG. 6 illustrates an exemplary 4-pin connector operative to mate with a 4-pin connector on an LVT card
  • FIG. 7 illustrates an exemplary small tactical terminal (STT) card external connector layout
  • FIG. 8 illustrates a schematic of an exemplary CDMS card.
  • a Combined Device Management System as disclosed herein may be used to manage communications between different devices.
  • a controller card external devices may be added to and/or removed from the CDMS without the need for time- consuming programming and/or reconfiguration.
  • the remote devices and controller card may communicate via a common bus, allowing the CDMS to maintain a small footprint and allowing the controller card to efficiently manage communication and other requests from the external devices.
  • the chassis of the CDMS is configured to be easily stacked and to easily accommodate a number of external devices while maintaining a small footprint.
  • the CDMS may be configured to allow a user to remotely monitor and/or control CDMS operations via a network interface.
  • specific connector pin configurations are used, allowing for efficient and intelligent signal grouping.
  • a common pin configuration is used for devices connecting to the common bus, allowing a plurality of devices to easily communicate via the common bus.
  • systems and methods employ a CDMS.
  • the CDMS disclosed herein allows multiple devices to communicate with each other over a common bus, and allows new remote devices to be added or removed from the CDMS without requiring additional programming or configuration.
  • FIG. 1 illustrates an overview of an exemplary CDMS 100.
  • the CDMS 100 includes a single CDMS controller 10 that provides command and control capability for multiple remote devices (e.g., Tactical Data Link (TDL) terminals such as low volume terminals (LVTs) and or small tactical terminals (STTs), TDL support equipment, and network equipment).
  • TDL Tactical Data Link
  • the CDMS controller 10 may support multiple types of TDL terminals and network devices from a single device over a single web interface 30, (e.g., via a desktop web browser, a laptop web browser, a mobile web browser, etc.), allowing a user to control and/or monitor connected terminals and network devices locally or remotely.
  • the CDMS controller 10 may use a single IP address to communicate with multiple devices, and to allow a user to configure and/or customize the CDMS 100.
  • a user may configure the IP address of the CDMS controller 10 and install/add any required cards (e.g., LVTs and/or STTs) in any one of multiple, (e.g., six), on-board chassis slots.
  • the cards may communicate over a common bus using communication request lines so that each card can communicate without interfering with the others. Voice signals from all cards with voice technology and an optional front panel voice connector may also be transmitted over the common bus.
  • the CDMS controller 10 may communicate with other devices and/or be accessed via a plurality of IP addresses.
  • the CDMS controller 10 may include a single card used to control the operations of CDMS 100. Other cards that interface with the CDMS controller 10 may be optional. For example, in certain implementations, the CDMS controller 10 may communicate with one or more LVTs, while in other implementations, the CDMS controller 10 may only communicate with STTs. In certain implementations, the CDMS controller 10 may communicate with combinations of one or more LVTs and STTs.
  • the web interface 30 may automatically display information about each card installed in the CDMS 100 upon startup and initialization of the CDMS controller 10.
  • the web interface 30 may also optionally include a control panel.
  • the CDMS 100 is scalable, and in certain implementations, its chassis may be stacked to expand the number of devices 50 (e.g., TDL terminals, TDL support equipment, and network equipment) that can be controlled from a single CDMS controller 10 while still maintaining a small footprint. In certain implementations, up to 127 devices 50 may be controlled by a CDMS controller 10 inside the CDMS 100.
  • devices 50 e.g., TDL terminals, TDL support equipment, and network equipment
  • the CDMS 100 is expandable and adaptable to support the addition and/or removal of cards during operation and is configured to support new control needs as they are identified.
  • the CDMS 100 may be expanded using an expansion cable configured to allow additional devices 50 to be controlled by the CDMS controller 10.
  • the CDMS 100 may employ a low profile 1U chassis for a small form factor.
  • FIG. 2 illustrates a CDMS interfacing with one or more remote physical devices via one or more equipment connections and with a web browser via a network connection, according to aspects of the present disclosed subject matter.
  • the CDMS shown in FIG. 2 may, for example, be similar to CDMS 100 described above with respect to FIG. 1.
  • the CDMS Chassis 205 includes a controller card 210, one or more equipment cards 230, a liquid crystal display (LCD) interface 270, an RS-232 bus 280, and an RS-485 bus 240.
  • the buses 240 and 280 are configured to allow communications between CDMS components such as, for example, the controller card 210, the one or more equipment cards 230, and the LCD interface 270.
  • the controller card 210 is similar to CDMS controller 10 described above with respect to FIG. 1.
  • the equipment cards 230 may be similar to the devices 50 that are controlled by and communicate with the CDMS controller 10, as described above with respect to FIG. 1.
  • controller software resides on a small embedded computer (not shown) on the controller card 210. More specifically, the controller software may be stored on a non-transitory tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), or on other memory devices.
  • the controller software may communicate with hardware interfaces using General Purpose Input Outputs (GPIOs) exposed by the Linux based operating system.
  • GPIOs General Purpose Input Outputs
  • the controller software may also support a small web server for control, configuration and/or status information via external web-browsers, such as a web browser(s) 220. In certain implementations, the web browser(s) 220 may display the web interface 30 described above.
  • the controller card 210 communicates with the web browser(s) 220 via a network connection 225.
  • the network connection may be an Ethernet connection.
  • other types of connections e.g., WiFi, Bluetooth, DSL, USB, etc. may be used to connect the controller card 210 with the web browser(s) 220.
  • the controller card 210 may communicate with the equipment cards 230 (e.g., LVT cards and/or STT cards) via a common serial bus such as the bus 240.
  • a common bus allows the CDMS to maintain a small footprint and allows the controller card 210 to efficiently manage communication and other requests from the external devices.
  • all communications between the controller card 210 and the equipment cards 230 take place over the bus 240.
  • equipment cards 230 may communicate with external devices 250 such as, for example, monitoring sensors, communications terminals, cameras, etc., via equipment connections 260.
  • the controller card 210 may also be configured to communicate with an LCD interface 270 coupled to the CDMS via a serial bus such as RS- 232 Bus 280.
  • the LCD interface 270 may be coupled to the controller card and locally display information regarding the CDMS.
  • the LCD 270 is configured to display information about the status of the controller card 210 and/or other information about the equipment cards 230 coupled to the controller card 210. In certain implementations, this information may be different from the control and or monitoring information displayed on the web browser(s) 220, while in other implementations, the information displayed on the LCD 270 and the web browser(s) 220 may be similar.
  • Communications between CDMS cards may use a custom packet structure.
  • the packets may use the following structure, where '$' indicates the beginning of a new message, '*" indicates the beginning of a Cyclic Redundancy Check, and ' ⁇ ' represents the end of a message:
  • the sender address represents the address of the physical slot address of the message sender. This value is a two character, hex encoded value in the range: [01- FF], with address [00] reserved for broadcast messages.
  • the receiver address represents the address of the intended recipient of the message. This value is a two character, hex encoded value in the range: [01, FF], with address [00] reserved for broadcast messages.
  • the Message ID is a unique identification number generated by a controller card, such as, for example, controller card 210.
  • the valid range is that of an unsigned short [0,65535]. This is represented by a string in the actual message.
  • the Message ID is used to facilitate bi-directional checking of messages that require responses and therefore need to be matched with some request within the controller card.
  • the content of the message body varies according to the type of message.
  • the message body is a series of comma delineated values.
  • the first value is a verb, representing the type of action to perform or what action was performed.
  • the controller card 210 would like to request discrete values '5' and '6' from an equipment card 230 (e.g., an LVT or STT)
  • the message body would have the following format: GET,5,6
  • return values are key-value pairs delineated by the equals sign.
  • the message structure allows the controller card 210 to request or update many discrete values with the same message. Similar to the example above is the SET action.
  • a SET Message body for setting discretes '2' and '3 ' would have the following format:
  • FIG. 3 illustrates an exemplary 48-pin common bus connector.
  • Connector 300 may be used, for example, with the bus 240 described above to provide the controller card 210 and/or the equipment card(s) 230 a connection to power supply pins and/or to common bus pins.
  • These common bus pins may provide a variety of functionalities. For example, certain pins may be used for communication requests, allowing cards to communicate over the bus without interfering with other cards. For example, certain pins may allow communications between the controller card 210 and one or more of the equipment cards 230 (e.g., LVTs, and/or STTs).
  • certain pins may allow the controller card 210 to transmit or receive requests from new equipment cards that are added to a CDMS and/or allow the controller card to perform necessary operations when an equipment card is removed from the CDMS.
  • cards may be added or removed from a CDMS without the need for additional programming or configuration, and these processes may be handled using communications via the connector 300.
  • Other pins may allow a card to be reset.
  • Certain pins may also support voice input and/or output functionality.
  • An exemplary pinout for the connector 300 is listed below in Table 1.
  • FIG. 4 illustrates an exemplary controller card connector layout.
  • a connector 400 is coupled to a controller card such as, for example, the controller card 210 and may include a D-Subminiature connector 410, a connector 420, and Light Emitting Diodes (LEDs) 430-450.
  • PWR LED 430 may indicate when a controller card is powered on.
  • the TX LED 440 and RX LED 450 may indicate when the controller card is transmitting and receiving data, respectively.
  • the connectors 410 and 420 may be female-type connectors.
  • the connector 410 may be a 15 pin connector
  • connector 420 may be a standard network connector, such as, for example, an RJ45 connector.
  • the connector 410 may provide the controller card access to pins providing a variety of functionality and allow the connector card to connect to and communicate with a variety of external circuitry, including circuitry distinct from any attached LVTs and/or STTs.
  • a CDMS may incorporate a security system that may be used to control and monitor the security state of the device. If there is a legitimate security breach, the controller card may be configured to handle necessary security functions which are determined by the software modules for each card.
  • a security circuit coupled to the controller card may include a security relay that has 2 states, SECURE (energized) and NOT SECURE (not energized). The state of this relay is controlled by its Security Status, Security Bypass, and Security Output components.
  • the controller card may also be configured to communicate with an LCD panel (e.g., the LCD interface 270) on the CDMS.
  • the LCD panel may, for example, be configured to display information about the status of the CDMS and/or other information of interest to a user. Again, this information may be distinct from the information displayed on a web interface such web interface 30, and may be displayed locally on the CDMS.
  • the connector 410 may provide the controller card access to pins allowing the controller card to transmit and/or receive data from an incorporated LCD panel.
  • the connector 410 may also provide the controller card with access to pins carrying voice data signals.
  • a controller card (e.g., the controller card 210) may be monitored and/or controlled remotely over a network connection.
  • the network connection may be an Ethernet connection.
  • the controller card may also include a network connector such as the connector 420.
  • An exemplary pinout for the connector 420 is listed below in Table 4:
  • FIG. 5 illustrates an exemplary LVT card external connector layout.
  • the LVT card connector 500 is coupled to an LVT card, and like controller card connector 400 described above, the LVT card connector 500 may include LEDs that indicate power, data/signal transmission, data/signal reception, etc. More specifically, the PWR LED 530 may indicate when the LVT card is powered on. The TX LED 540 and The RX LED 550 may indicate when the LVT card is transmitting and receiving data, respectively. Additionally, Connector 500 may include D-Subminiature connector 510, and 4 Pin female connector 520.
  • Connector 510 provides the LVT card access to pins providing a variety of functionality. Exemplary LVT card functionality is described in further detail below. Further, the LVT card may operate in a variety of different power states including, for example, ON, OFF, and Standby States.
  • the LVT card may support zeroize functionality, allowing the card to retain or erase cryptographic data.
  • the LVT card may also be configured to incorporate Long Term Transmit Inhibit (LTTI) functionality.
  • LTTI functionality may include initiating the process of shutting down transmissions by the LVT card, including halting RF emission and taking necessary data processing actions so that normal functioning can be resumed as required.
  • the LVT card may include an air filter alarm and an air filter monitoring circuit. Voice and/or voice PTT circuitry may also be implemented, including both local and/or remote implementations.
  • An exemplary pinout for connector 510 is listed below in Table 5 :
  • Connector 520 may provide the LVT card with access to pins carrying analog voice signal data.
  • An exemplary pinout for connector 520 is listed below in Table 6:
  • FIG. 6 illustrates an exemplary 4-pin connector operative to mate with a 4-pin connector (e.g., the connector 520) on an LVT card.
  • Connector 600 may include sleeve 610, tip 620, Ring 630, and Ring 640.
  • Sleeve 610 may connect with pin 1 of connector 520 described above with respect to FIG. 5, tip 620 may connect with pin 2 of connector 520, Ring 630 may connect with Pin 3 of connector 520, and Ring 640 may connect with pin 4 of Connector 520.
  • FIG. 7 illustrates an exemplary small tactical terminal (STT) card external connector layout.
  • the STT card connector 700 is coupled to an STT card, and like controller card connector 400 and LVT card connector 500, the connector 700 may include LEDs that indicate power, data/signal transmission, data/signal reception, etc. More specifically, PWR LED 730 may indicate when the STT card is powered on. TX LED 740 and RX LED 750 may indicate when the STT card is transmitting and receiving data, respectively. Additionally, the connector 700 may include D-Subminiature connectors 710 and 720.
  • the connector 710 may provide the STT card incorporated access to pins providing a variety of functionality.
  • the STT card may support zeroize functionality, allowing the card to retain or erase cryptographic data.
  • Voice and/or voice PTT circuitry may also be implemented, including both local and/or remote implementations.
  • the STT card may additionally support speaker output capabilities.
  • An exemplary pinout for connector 710 is listed below in Table 7:
  • the connector 720 may provide the STT card additional access to pins providing further functionality.
  • the STT card may support LTTI functionality, initiating the process of shutting down transmissions by the STT, including halting RF emission and taking necessary data processing actions so that normal functioning can be resumed as required.
  • Emergency signaling functionality, along with status and power control functionality may also be supported.
  • An exemplary pinout for the connector 720 is listed below in Table 8:
  • FIG. 8 illustrates a schematic of an exemplary CDMS card.
  • the schematic represents the physical dimensions of an exemplary controller card, LVT, STT or any other appropriate card designed to operate with a CDMS.
  • the measurements shown in FIG. 8 are in inches.
  • the exemplary pinouts described above are arranged such that signals with common, similar, or related functionality are arranged in close proximity to each other. These arrangements allow the described connectors to efficiently handle communications between devices while allowing a CDMS to maintain a small footprint.
  • the connectors are configured such that the conducting elements are arranged in an array having one or more rows of consecutively numbered conducting elements (e.g., pins or pin receptacles). While specific connector pinouts are described herein, one of ordinary skill in the art would understand that in certain implementations, other pinouts may be used.
  • a CDMS may be used to manage communications between different devices.
  • external devices may be added to and/or removed from the CDMS without the need for time-consuming programming and/or reconfiguration.
  • the remote devices and controller card may communicate via a common bus, allowing the CDMS to maintain a small footprint and allowing the controller card to efficiently manage communication and other requests from the external devices.
  • the chassis of the CDMS may be configured to be easily stacked and to easily accommodate a number of external devices while maintaining a small footprint.
  • the CDMS may be configured to allow a user to remotely monitor and/or control CDMS operations via a network interface.
  • specific connector pin configurations are used, allowing for efficient and intelligent signal grouping.
  • a common pin configuration is used for devices connecting to the common bus, allowing a plurality of devices to easily communicate via the common bus.

Abstract

Un système de gestion de dispositifs combinés (CDMS) peut être utilisé pour gérer les communications entre différents dispositifs. Des dispositifs à distance peuvent être ajoutés au CDMS et/ou retirés de celui-ci sans le besoin d'une programmation et/ou d'une reconfiguration prenant du temps. Les dispositifs à distance et une carte de contrôleur peuvent communiquer par l'intermédiaire d'un bus commun, permettant au CDMS de maintenir une petite empreinte et permettant à la carte de contrôleur de gérer efficacement la communication et d'autres demandes des dispositifs externes. Des configurations de broches de connecteur spécifiques sont utilisées, permettant un groupement efficace et intelligent des signaux. En outre, une configuration de broches commune est utilisée pour les dispositifs se connectant au bus commun, ce qui permet à une pluralité de dispositifs de communiquer facilement par l'intermédiaire du bus commun.
PCT/US2013/065084 2012-10-15 2013-10-15 Système de gestion de dispositifs combinés (cdms) WO2014062700A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201261713968P 2012-10-15 2012-10-15
US61/713,968 2012-10-15

Publications (1)

Publication Number Publication Date
WO2014062700A1 true WO2014062700A1 (fr) 2014-04-24

Family

ID=50488704

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/065084 WO2014062700A1 (fr) 2012-10-15 2013-10-15 Système de gestion de dispositifs combinés (cdms)

Country Status (1)

Country Link
WO (1) WO2014062700A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016023000A1 (fr) * 2014-08-07 2016-02-11 Mitra Nasserbakht Mécanisme de connexion intelligent

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5096139A (en) * 1990-08-16 1992-03-17 Hughes Aircraft Company Missile interface unit
US6651175B1 (en) * 1999-04-28 2003-11-18 Dvi Acquisition Corp. Device and method for providing security for a computer software program
US20060154530A1 (en) * 2005-01-07 2006-07-13 Novotney Donald J Connector system
US20100008512A1 (en) * 2004-12-26 2010-01-14 Neil Thomas Packer Paging System
US20110167187A1 (en) * 2010-01-06 2011-07-07 Apple Inc. Connectors in a portable device
US20120196640A1 (en) * 2010-08-04 2012-08-02 Bae Systems Information And Electronic Systems Integration Inc. System, voice cable assembly, and method for voice communication

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5096139A (en) * 1990-08-16 1992-03-17 Hughes Aircraft Company Missile interface unit
US6651175B1 (en) * 1999-04-28 2003-11-18 Dvi Acquisition Corp. Device and method for providing security for a computer software program
US20100008512A1 (en) * 2004-12-26 2010-01-14 Neil Thomas Packer Paging System
US20060154530A1 (en) * 2005-01-07 2006-07-13 Novotney Donald J Connector system
US20110167187A1 (en) * 2010-01-06 2011-07-07 Apple Inc. Connectors in a portable device
US20120196640A1 (en) * 2010-08-04 2012-08-02 Bae Systems Information And Electronic Systems Integration Inc. System, voice cable assembly, and method for voice communication

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016023000A1 (fr) * 2014-08-07 2016-02-11 Mitra Nasserbakht Mécanisme de connexion intelligent
US10055597B2 (en) 2014-08-07 2018-08-21 ENORCOM Corporation Intelligent connection method
EP3486793A1 (fr) * 2014-08-07 2019-05-22 Enorcom Corporation Mécanisme de connexion intelligent
EP3896577A1 (fr) * 2014-08-07 2021-10-20 Enorcom Corporation Mécanisme de connexion de sécurité intelligent
US11238171B1 (en) 2014-08-07 2022-02-01 ENORCOM Corporation Intelligent connection mechanism
US11822678B1 (en) 2014-08-07 2023-11-21 ENORCOM Corporation Autonomous and self-aware connection mechanism

Similar Documents

Publication Publication Date Title
CN109791528B (zh) 配置坞
AU2014228186B2 (en) Modular pool/spa control system
US9231331B2 (en) Connector identification through proximity sensing
EP2961197B1 (fr) Appareil et procédé pour empêcher les défaillances dans un dispositif électronique
US11703910B2 (en) Docking station, electrical device, and method for configuring basic input output system
US20150363344A1 (en) Selectively Connecting a Port of an Electrical Device to Components in the Electrical Device
US8886859B2 (en) USB storage device
KR20170001475A (ko) 모드에 따라 신호 세기를 제어하는 전자 장치 및 방법
US20130166896A1 (en) Management system for network card
US10484519B2 (en) Auto-negotiation over extended backplane
US20150006700A1 (en) Establishing connectivity of modular nodes in a pre-boot environment
CN204155267U (zh) 一种otg usb接口电路
US9478855B2 (en) Space vehicle field unit and ground station system
WO2014062700A1 (fr) Système de gestion de dispositifs combinés (cdms)
US20140365699A1 (en) Adapter card for thin computing devices
US9525608B2 (en) Out-of band network port status detection
US10251293B2 (en) Smart USB modules and method of making
CN102801903A (zh) 一种具有射频网关功能的网络摄像机
US20130128438A1 (en) Heat dissipating system
US9432566B2 (en) Camera system capable of expanding functions and an amount of video stream
TWI650038B (zh) Ｚ－Ｗａｖｅ閘道器
US9836037B2 (en) Managing power emission to electrical appliances
US20160335212A1 (en) Device for switching between communication modes
US9960811B1 (en) DC bias signals isolatable from transmission protocols
US20160076951A1 (en) Calibration device and sensor calibration system using the same

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13846500

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13846500

Country of ref document: EP

Kind code of ref document: A1