Patent Application
20150350330
The embodiments disclosed herein relate generally a transport refrigeration system (TRS). More particularly, the embodiments relate to a system and method for transferring data and/or files between various components in a TRS or between a transport refrigeration unit (TRU) system and various consumer electronics such as personal computers (PCs, smart phones, tablet devices, and so forth).
A transport refrigeration system (TRS) is generally used to control an environmental condition (e.g., temperature, humidity, air quality, and the like) within a refrigerated transport unit (e.g., a container on a flat car, an intermodal container, etc.), a truck, a box car, or other similar transport units (TUs). A TRS may include a transport refrigeration unit (TRU) that is attached to the TU and provides refrigeration within a cargo space of the TU. The TRU may include, without limitation, a compressor, a condenser, a thermo expansion valve, an evaporator and fans and/or blowers to facilitate heat exchange between the cargo space of the TU and the environment surrounding the TU.
In a cooling cycle, a refrigerant is compressed by the compressor and subsequently flows into the condenser. In the condenser, the compressed refrigerant can release heat to the environment. Then the refrigerant can pass through the thermo expansion valve where it can subsequently flow into the evaporator to absorb heat from air in a space desired to be cooled. A fan and/or blower can be used to facilitate heat exchange between the refrigerant and the environment when the refrigerant is in the condenser and the evaporator by creating air flow through the condenser and the evaporator.
Known TRS and TRU system communication protocols are commonly used to transfer data and/or files between various components in a TRS or between a transport refrigeration unit (TRU) system and various consumer electronics such as personal computers (PCs, smart phones, tablet devices, and so forth).
Embodiments described herein are directed to a data communication protocol used to transfer data and/or files between various components in a TRS and/or used to transfer data and/or files between a TRU system and various consumer electronics that may include without limitation, PCs, smart phones and tablet devices.
The embodiments described herein can transfer data and/or files between various components in a TRS and/or between a TRU system and various consumer electronics using modern, high speed communication buses. Also, the embodiments described herein can provide quicker software upgrade times, quicker data logger download times, quicker data send and retrieval times, quicker system data point refresh rates, and allow for migrating from USB to other hardware layers such as Wi-Fi, Bluetooth, and so on, and provide sharing of entire files between system components. That is, the embodiments described herein provide a TRS and/or TRU system communication protocol that can be easily applied using modern, high speed communication buses and that can be readily implemented on many hardware layers using standard communication drivers which are available “off the shelf” to achieve higher data communication rates to improve system performance.
An exemplary embodiment comprises a method of transferring data and/or files between various components in a transport refrigeration system (TRS) and/or transferring data and/or files between a transport refrigeration unit (TRU) system and various consumer electronics. The method may comprise wrapping predetermined existing and/or new data transfer protocols within a common communication protocol (an “off the shelf” communication protocol) formatted to perform predetermined operations. The method may further comprise invoking a predetermined operation by performing a GET or a POST command to one or more predetermined services that are supported by the TRS and/or TRU system components. The method my further comprise formatting predetermined service data into an instruction set document within the body of a common communication protocol message. The instruction set document can use any format language known by the various components in the TRS and the various consumer electronics. In some embodiments, the common communication protocol is hypertext transfer protocol (HTTP). In some embodiments, the format language is extensible markup language (XML) and the instruction set document can be an XML document.
According to another embodiment, a method of transferring transport refrigeration system (TRS) data associated with a TRS comprises defining a single data structure common to a substantially non-exhaustive number of predetermined services that are supported by components associated with the TRS; and programming at least one TRS controller associated with the TRS to transfer predetermined TRS service data contained within an instruction set document (e.g., an XML document) via a common communication protocol (e.g., hypertext transfer protocol (HTTP)), wherein the predetermined TRS service data conforms to the defined single data structure.
According to yet another embodiment, a transport refrigeration system (TRS) comprises a programmable integral controller that may comprise a single integrated control unit or that may comprise a distributed network of control elements. The TRS may further comprise a high speed data communication link that may be wired or wireless. The TRS may further comprise one or more external controllers in communication via the high speed data communication link with the integral controller using a common communication protocol (e.g., HTTP) encapsulating predetermined data, commands, and/or files. The predetermined data, commands, and/or files are further encapsulated within instruction set documents (e.g., XML documents).
The foregoing and other features, aspects and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
While the above-identified drawing figures set forth alternative embodiments, other embodiments are also contemplated, as noted in the discussion. In all cases, this disclosure presents illustrated embodiments by way of representation and not limitation. Numerous other modifications and embodiments can be devised by those skilled in the art which fall within the scope and spirit of the principles of this disclosure.
With continued reference to
The primary fluid path 214 is completed via fluidic coupling of the evaporator 232 and the compressor 216.
Refrigerant in its various states flows through the primary fluid path 214 of the refrigerant circuit 212 as described herein. Vaporized refrigerant is delivered to the compressor 216 by the suction line 234. The compressor 216 compresses the vaporized refrigerant by increasing its temperature and pressure. The compressed, vaporized refrigerant is then delivered to the condenser 220 by the discharge line 218.
The condenser 220 receives compressed, vaporized refrigerant from the compressor 216. The condenser 220 is a heat exchanger apparatus used to remove heat from the refrigerant in order to condense the vaporized refrigerant into liquid refrigerant. In the condenser 220, the compressed, vaporized refrigerant releases heat to the air in communication with the condenser 220 in order to cool the vaporized refrigerant. The cooling action of the condenser 220 causes the state of the refrigerant to change from vapor to liquid.
While in the fluid path 214, the cool liquid refrigerant is then delivered to the EXV 228. The EXV 228 is a throttling device that restricts the flow of liquid refrigerant by forcing the liquid refrigerant through a small orifice causing the pressure of the liquid refrigerant to decrease, thereby lowering the boiling point of the refrigerant, making the refrigerant evaporate. As the liquid refrigerant passes through the small orifice of the EXV 228, the liquid refrigerant forms into liquid droplets.
The liquid refrigerant droplets are delivered to the evaporator 232 by evaporator input line 230. The liquid refrigerant droplets delivered to the evaporator 232 absorb heat from warm air flowing into the evaporator 232. The evaporator 232 is located within or in thermal communication with the space being conditioned by the transport refrigeration unit 200. Air is generally circulated between the conditioned space and the evaporator 232 by one or more evaporator fans (not shown). Generally, warmer air flows into the evaporator 232, the liquid refrigerant droplets absorb heat from the warmer air, and cooler air flows out of the evaporator 232. The cooler air flowing out of the evaporator 232 cools the masses in the conditioned space by absorbing heat from the masses within the conditioned space; the warmer air is circulated back to the evaporator 232 by the evaporator fans to be cooled again.
The liquid refrigerant droplets vaporize once they have absorbed sufficient heat, i.e. once the liquid refrigerant droplets reach their saturation or vaporization temperature at a given pressure. The refrigerant, which has changed from liquid refrigerant droplets back to vaporized refrigerant, is then delivered by suction line 234 back to the compressor 216. The delivery of the vaporized refrigerant back to the compressor 216 completes the flow of refrigerant through the fluid path 214.
The TRS controller 155 may be programmed to control various TRU 200 components such as, without limitation, the EXV 228, via communication link 250 in response to data provided by, for example, a plurality of sensors that may comprise an evaporator input temperature sensor 217, an evaporator output temperature sensor 222, a suction pressure sensor 210, a compressor discharge pressure sensor 206, a suction temperature sensor 211, a compressor discharge temperature sensor 208, and at least one sensor 221 coupled to the compressor 216. It will be appreciated that numerous additional sensors or fewer sensors may be employed according to the principles described herein based upon a particular application.
Programmable controller 160 may be connected to a local display device 330 according to one embodiment. Programmable controller 160 may further be connected to remote monitor devices, described herein, via a wired communication link 270 such as, for example, a USB communication link to a data logger 350, or a wireless communication link 272 such as a Wi-Fi data link, an IR data link, or a Bluetooth data link to a PC 262, smart phone 264, or a tablet 266, such as shown in
Exemplary remote communication nodes which may be connected to data bus 308 comprise, without limitation, a refrigerant compressor controller 312, a compressor prime mover engine controller 314, a refrigerant evaporator controller 316, a conditioned load humidity controller 318, a conditioned load atmosphere controller 320, a motor speed controller 322, such as a compressor prime mover motor, fan and blower motors, and the like, remote sensor modules 324, a display 326, and the data logger or data pack 350.
Exemplary embodiments of a communication protocol that may be used to transfer data and/or files between various components in a TRU or between various components in a TRS and various consumer electronics such as discussed herein with reference to
As shown in
A controller receiving the instruction set document(s) via the HTTP communication protocol then parses or decodes the data contained within the instruction set document into data that is recognized by the controller. The controller can then perform requested services in response to the parsed or decoded data and respond accordingly with the source transmitting the instruction set document.
Current transport refrigeration communication protocols and methods that employ serial data communication techniques can then be applied to implement desired services using modern, high speed communication busses when transmitting relevant data and/or files embedded within an instruction set document that is transported to one or more controllers using the HTTP communication protocol. It will be appreciated that the communication principles described herein allow the implementation of TRS and TRU services via a communication protocol that can be expanded to a theoretically infinite number of uses, simply and efficiently by defining each new service.
Looking now at
According to one aspect, the “About Service” request 406 is invoked by performing a GET request 408 to the desired TRS and/or TRU components about service. The TRS and/or TRU component receiving the request will then return an XML document 410 containing information about itself. The embodied communication protocol advantageously provides a higher level of efficiency with respect to current communication protocols that generally require a separate transaction for each piece of identified data through serial transmission of data and/or files, as stated herein.
According to one aspect, the “Datapac Service” request 506 allows predetermined TRS and/or TRU datapac commands to be sent in one message, thereby increasing system efficiency compared to the “one at a time” methods generally available in legacy TRSs and/or TRUs. The datapac commands are simply listed in an XML document 508 within the body of the HTTP message. The response to this request contains a list of the datapac responses in an XML document 510 within the body of the HTTP response.
According to one aspect, a “File Transfer—Send” service request 606 is used for operations such as data logger downloads, predetermined data retrieval, and predetermined master file updates. The communication protocol principles described herein are not so limited however, and it will be appreciated that the principles described herein may be expanded to any operation wherein one system component is required to get a file and/or data from another system component. Such feature rich capabilities are generally not present in legacy TRSs and TRU systems.
According to one aspect, the request portion of the handshake contains details about which file and/or data is being requested such as file size and the location to which the file and/or data will be sent. This location indicates to the receiver what should be done with the file and/or data.
According to another aspect, the response portion of the handshake contains details on how to send the file and/or data such as destination URL. Once the handshake is successfully completed, the sender performs a POST operation to the designated URL containing the file to be sent. According to one aspect, this process is used for operations such as, without limitation, software upgrades, that may be performed through use of, for example, flashloading. This process may further be used for programming desired operational features or even further expanded to any operation where one TRS and/or TRU system component is required to send a file and/or data to another component. As stated herein, such feature rich capabilities are generally not present in legacy TRSs and TRU systems.
In summary explanation, embodiments described herein are directed to a data communication protocol used to transfer data and/or files between various components in a TRS and/or used to transfer data and/or files between a TRU system and various consumer electronics that my include without limitation, PCs, smart phones and tablet devices. The embodied data communication protocol further allows placement of files and/or commands including, without limitation, predetermined proprietary files and commands within a commonly used common communication protocol wrapper to be easily implemented on many common, modern physical layers using standard communication drivers which are available “off the shelf”. According to one aspect, the relevant proprietary data is contained within the body of the common communication protocol (e.g., HTTP) message in an instruction set document (e.g., an XML document). The principles described herein allow the implementation of services via a communication protocol that can be expanded to a theoretically infinite number of uses simply by defining a new service.
The principles and embodiments described herein provide numerous advantages over legacy TRS and TRU systems. Some of these advantages include, improved software upgrade time, improved data logger download time, improved operational parameter data send and retrieve time, improved refresh rates for monitoring TRS and/or TRU system data points, ability to easily migrate from USB to other hardware layers such as Wi-Fi, Bluetooth, infrared, ZigBee among others, and use of high speed data transfer rates allowing sharing of entire files between TRS and TRU system components.
The embodiments described herein provide a communication scheme that enables proprietary TRS service data contained within an instruction set document to be transferred via a hypertext transfer protocol resulting in a generic data structure common to a substantially non-exhaustive number of predetermined services that are supported by components associated with the TRS. Although particular embodiments may employ other hardware layers such as stated herein, the embodiments described herein advantageously prevent third parties from transferring data/files between various components of a TRS or TRU and consumer electronics. Such consumer electronics may include, without limitation, PCs, smart phones, tablet devices, and so forth, as stated herein.
It is noted that any of aspects 1-9, 10-16 and 17-29 can be combined.
programming at least one TRS controller associated with the TRS to transfer predetermined TRS service data contained within an instruction set document via a common communication protocol; and
transferring the instruction set document via the common communication protocol to or from at least one TRS controller associated with the TRS to invoke one or more predetermined services that are supported by components associated with the TRS.
defining a generic data structure common to a substantially non-exhaustive number of predetermined services that are supported by components associated with the TRS; and
programming at least one TRS controller associated with the TRS to transfer predetermined TRS service data contained within an instruction set document via a common communication protocol, wherein the predetermined TRS service data contained within the instruction set document and transferred via a common communication protocol defines the generic data structure.
at least one TRS controller programmed to transfer predetermined TRS service data contained within an instruction set document using a common communication protocol; and
a medium for transferring the XML documents to and from at least one TRS controller using the common communication protocol, wherein the predetermined TRS service data contained within an instruction set document and transferred via the common communication protocol defines a generic data structure common to a substantially non-exhaustive number of predetermined services that are supported by components associated with the TRS.
Other distinctive features provided by the embodiments and principles described herein include the ability to send multiple datapac commands in one message, thus improving system efficiency. Further, the embodied “About Service” communication protocol allows vital system component information to be shared in a single transaction.
While only certain features of the embodiments have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the embodiments described herein.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US13/78436 | 12/31/2013 | WO | 00 |
| Number | Date | Country | |
|---|---|---|---|
| 61747439 | Dec 2012 | US |
