Field of the Invention
The present invention relates to enabling communication between devices and more particularly to enabling communication between the devices using splitter cables.
Brief Description of Related Art
In a typical imaging system (e.g., a soldier imaging system), multiple accessory devices are connected to a host device (e.g., handheld device). In existing methods, the host device may require different interfaces and communications protocols (e.g., RS232, RS422, universal serial bus (USB), and so on) for connecting to different accessory devices. This may lead to an increased number of pins and dedicated hardware on the host device to handle communications with the accessory devices. Further, e pins nay require a large number of connectors to allow the accessory devices to be connected at the same time. This may lead to placing of breakout boxes at ends of the connectors or octopus ends to the connectors thereby increasing the complexity in managing the accessory devices in the field.
A system and method for enabling communication between devices using splitter cables are disclosed. According to one aspect of the present subject matter, the system includes a first device and a second device. Further, the system includes a first splitter cable having a first interface connected to the first device, a second interface connected to the second device and a third interface. Furthermore, the first splitter cable includes an embedded communications interface unit to enable communication between the first device and second device.
According to another aspect of the subject matter, communication is enabled between a first device and a second device by an embedded communications interface unit of a splitter cable having three interfaces. The first device is connected to a first interface of the splitter cable and the second device is connected to a second interface of the splitter cable.
The advantages and features of the present disclosure will become better understood with reference to the following detailed description and claims taken in conjunction with the accompanying drawings, wherein like elements are identified with like symbols, and in which:
The exemplary embodiments described herein in detail for illustrative purposes are subject to many variations in structure and design. The present technique includes a handheld device that features a 7 pin, universal serial bus (USB) power and data interface. The USB power and data interface connects to a first interface of a splitter cable and communicates with a communications interface unit embedded in a segment of the splitter cable. Further, the splitter cable includes a second interface for connecting to an accessory device and a third interface for connecting to another splitter cable. The splatter cables can then be daisy chained together to form a physical connection chain back to the handheld device while providing connections to multiple accessory devices.
In an example implementation, data from the accessory devices go to the communications interface unit in each splitter cable and get translated or converted in associated communications interface unit into a common protocol (e.g., RS232, RS422, universal serial bus (USB), and so on) that can be read on the handheld device. In another example implementation, data from the handheld device go to the communications interface unit in the associated splitter cable and get translated or converted in the communications interface unit into a protocol that can be read on the associated accessory device. Each communications interface unit can be operated as both a USB client and host, and when daisy chained together, messaging is aggregated and passed up to the handheld device such that the splitter cables can be attached and removed in a hot swap, plug and play type of operation.
Furthermore, the splitter cables 104A-C include interfaces 108A1-A3 to 108C1-C3 and communications interface units 110A-C, respectively. The communications interface units 110A-C are embedded in splitter cables 104A-C, for example, in segments between the associated interfaces 108A1-A3 to 108C1-C3. One can envision that a communications interface unit can include logical circuitry or a processor and a memory including instructions run by the processor.
In the example illustrated in
Furthermore, the interface 108A3 is connected to the interface 108B1 of the splitter cable 104B, the interface 108B2 of the splitter cable 104B is connected to the interface 106C of the device 102C via any sized cable and the interface 108B3 of the splitter cable 10413 is connected to the interface 108C1 of the splitter cable 104C. In addition, the interface 108C2 of the splitter cable 104C is connected to the interface 106D of the device 102D via any sized cable. Thus forming daisy chained splitter cables 104A-C and connecting the devices 102B-C to the device 102A via the splitter cables 104A-C. In an example, a GPS, a DRIOD mission computer, a laser designator, a RF Radio and the like can connect to a HTLM. In another example, cameras (serial USB, camera link, etc.), smart sensors (pressure, accelerometers, and temperature) motor controllers, and the like can connect to a laptop, or a tablet. In an example implementation, the devices 102A-C can connect to the device 104D for power or to use remote applications on the device 102D. Each of the communications interface units 110A-C may include protocols supported by associated connected devices 102A-D.
In some embodiments, the splitter cables 104A-C may he different due to connectors on the interfaces (108A2, 108B2 and 108C2) that connect to the devices 102B-D. As such a communications interface unit of a splitter cable knows what type of cable it is and when accessory devices, such as a GPS, a laser marker, a DROID mission computer, and the like plugged in, it may identify itself as a plug and play feature.
In an example implementation, when the splitter cables, 104A-C receive data from devices 102B-D, respectively, the associated communications interface unit 110A-C converts the data into a protocol (e.g., RS232, RS422, USB, and so on) understandable by the device 102A and send the converted data to the device 102A. For example, when the device 102D sends data to the device 102A, the communication interface unit 110C converts the data into the protocol understandable by the device 102A and sends the converted data to the device 102A via the splitter cables 104B and 104A. In another example implementation, when the device 102A sends data to the device 102B, then the communications interface unit 110A converts the data into the protocol understandable by the device 102B and sends the converted data to the device 102B. In yet another example implementation, when the device 102A sends data to the device 102C, then the communications interface unit 110A may send unconverted data to the splitter cable 104B. The communications interface unit 110B then converts the data to the protocol that can be read on the device 102C and sends the converted data to the device 102C. In one example, the protocols that can be understandable by the devices 102A-D can be same or different.
In some embodiments, the splitter cables 104-C can be unique to the connected devices 102A-D. For example, some devices need discrete controls (transistor-transistor logic (TTL) high) to arm a laser or to execute a function like fire a laser. In this example, a handheld device may send a message o data via USB to a communications interface unit to arm and fire the laser. When the communications interface unit receives the message, the communications interface unit may decode the message and generate an aim and fire discrete TTL signal (or interface needs) to fire the laser.
The memory 304 may store instructions 306. In an example, the instructions 306 may be executed by processor 302 to enable communication between a first device and a second device. The first device is connected to a first interface of a splitter cable having three interfaces and the second device is connected to a second interface of the splitter cable.
In various embodiments shown in
The foregoing descriptions of specific embodiments of the present disclosure have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the present disclosure and its practical application, to thereby enable others skilled in the art to best utilize the present disclosure and various embodiments with various modifications as are suited to the particular use contemplated. It is understood that various omission and substitutions of equivalents are: contemplated as circumstance may suggest or render expedient, but such are intended to cover the application or implementation without departing from the spirit or scope of the claims of the present:disclosure.
This Application claims rights under 35 USC §119(e) from U.S. Application 61/963,287 filed Nov. 30, 2013, the contents of which are incorporated herein by reference.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US14/67801 | 11/28/2014 | WO | 00 |