US20190268675A1 - Telematics Road Ready System including a Bridge Integrator Unit - Google Patents
Telematics Road Ready System including a Bridge Integrator Unit Download PDFInfo
- Publication number
- US20190268675A1 US20190268675A1 US16/293,578 US201916293578A US2019268675A1 US 20190268675 A1 US20190268675 A1 US 20190268675A1 US 201916293578 A US201916293578 A US 201916293578A US 2019268675 A1 US2019268675 A1 US 2019268675A1
- Authority
- US
- United States
- Prior art keywords
- data
- integrator unit
- trailer
- bridge integrator
- bridge
- 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
- 230000006854 communication Effects 0.000 claims abstract description 64
- 238000004891 communication Methods 0.000 claims abstract description 64
- 238000001514 detection method Methods 0.000 claims description 25
- 238000012544 monitoring process Methods 0.000 claims description 15
- 230000001413 cellular effect Effects 0.000 claims description 9
- 230000005540 biological transmission Effects 0.000 abstract description 15
- 230000001953 sensory effect Effects 0.000 description 26
- 238000010586 diagram Methods 0.000 description 11
- 238000000034 method Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- HBBGRARXTFLTSG-UHFFFAOYSA-N Lithium ion Chemical compound [Li+] HBBGRARXTFLTSG-UHFFFAOYSA-N 0.000 description 7
- 229910001416 lithium ion Inorganic materials 0.000 description 7
- 230000002093 peripheral effect Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000000446 fuel Substances 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000010926 purge Methods 0.000 description 3
- 238000005070 sampling Methods 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 241000218691 Cupressaceae Species 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000013078 crystal Substances 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- JLVVSXFLKOJNIY-UHFFFAOYSA-N Magnesium ion Chemical compound [Mg+2] JLVVSXFLKOJNIY-UHFFFAOYSA-N 0.000 description 1
- 208000034809 Product contamination Diseases 0.000 description 1
- ZRXYMHTYEQQBLN-UHFFFAOYSA-N [Br].[Zn] Chemical compound [Br].[Zn] ZRXYMHTYEQQBLN-UHFFFAOYSA-N 0.000 description 1
- UFNRFBFHJJPDNF-UHFFFAOYSA-N [Zn].[Ce] Chemical compound [Zn].[Ce] UFNRFBFHJJPDNF-UHFFFAOYSA-N 0.000 description 1
- 239000002253 acid Substances 0.000 description 1
- 235000015241 bacon Nutrition 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- OJIJEKBXJYRIBZ-UHFFFAOYSA-N cadmium nickel Chemical compound [Ni].[Cd] OJIJEKBXJYRIBZ-UHFFFAOYSA-N 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000003467 diminishing effect Effects 0.000 description 1
- 238000006073 displacement reaction Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000010408 film Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 229910001425 magnesium ion Inorganic materials 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000059 patterning Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 150000003839 salts Chemical class 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000010409 thin film Substances 0.000 description 1
- 229910052720 vanadium Inorganic materials 0.000 description 1
- LEONUFNNVUYDNQ-UHFFFAOYSA-N vanadium atom Chemical compound [V] LEONUFNNVUYDNQ-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60D—VEHICLE CONNECTIONS
- B60D1/00—Traction couplings; Hitches; Draw-gear; Towing devices
- B60D1/24—Traction couplings; Hitches; Draw-gear; Towing devices characterised by arrangements for particular functions
- B60D1/248—Traction couplings; Hitches; Draw-gear; Towing devices characterised by arrangements for particular functions for measuring, indicating or displaying the weight
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60Y—INDEXING SCHEME RELATING TO ASPECTS CROSS-CUTTING VEHICLE TECHNOLOGY
- B60Y2200/00—Type of vehicle
- B60Y2200/10—Road Vehicles
- B60Y2200/14—Trucks; Load vehicles, Busses
- B60Y2200/148—Semi-trailers, articulated vehicles
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
- B62D—MOTOR VEHICLES; TRAILERS
- B62D53/00—Tractor-trailer combinations; Road trains
- B62D53/04—Tractor-trailer combinations; Road trains comprising a vehicle carrying an essential part of the other vehicle's load by having supporting means for the front or rear part of the other vehicle
- B62D53/06—Semi-trailers
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
- B62D—MOTOR VEHICLES; TRAILERS
- B62D63/00—Motor vehicles or trailers not otherwise provided for
- B62D63/06—Trailers
- B62D63/08—Component parts or accessories
-
- 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
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
- H04L2012/40215—Controller Area Network CAN
-
- 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
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2209/00—Arrangements in telecontrol or telemetry systems
- H04Q2209/40—Arrangements in telecontrol or telemetry systems using a wireless architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2209/00—Arrangements in telecontrol or telemetry systems
- H04Q2209/40—Arrangements in telecontrol or telemetry systems using a wireless architecture
- H04Q2209/43—Arrangements in telecontrol or telemetry systems using a wireless architecture using wireless personal area networks [WPAN], e.g. 802.15, 802.15.1, 802.15.4, Bluetooth or ZigBee
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2209/00—Arrangements in telecontrol or telemetry systems
- H04Q2209/70—Arrangements in the main station, i.e. central controller
- H04Q2209/75—Arrangements in the main station, i.e. central controller by polling or interrogating the sub-stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2209/00—Arrangements in telecontrol or telemetry systems
- H04Q2209/80—Arrangements in the sub-station, i.e. sensing device
- H04Q2209/88—Providing power supply at the sub-station
- H04Q2209/886—Providing power supply at the sub-station using energy harvesting, e.g. solar, wind or mechanical
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
Definitions
- the present application is directed to a telematics system including a bridge integrator unit for receiving and translating data transmissions from more than one type of data transmissions from sensory devices and transmitting the translated messages to a master control unit.
- Embodiments disclosed herein disclose a bridge integrator unit with ability to receive data transmissions from more than one type of data transmission from a sensory device or plurality of sensors or sensory devices.
- the bridge integrator unit is a hub for various forms of data coming from sensory devices manufactured across the industry of transportation.
- the bridge integrator unit can communicate at least via radio frequency, an RS232 UART connection, and by a CAN bus connection to a CAN bus data system that is an industry standard North American data bus for trailers.
- Different embodiments of the bridge integrator unit encompass the different transmissions modes, among others configured as desired, that can come into the bridge integrator unit from different manufactures of sensory devices.
- the data can be translated to a master control unit (MCU).
- MCU master control unit
- the data coming into the bridge integrator unit will work from messaging data, i.e. in a comma delimited format, that will be translated from the sensory devices protocol to a proprietary firmware language and then broadcast to the MCU using a radio frequency band of IEEE 802.15.4.
- the different means of communication from several devices can come in to the bridge integrator unit simultaneously. From this data that is transmitted into the bridge integrator unit, messages that are sent to the MCU are configured to be transmitted if and when a condition arises to notify a user of the equipment (e.g., a trailer).
- the bridge integrator unit may be powered from a trailer blue line power on the trailer when connected to a tractor, and may also resource its battery backup if not connected to the blue line power. For that reason, the bridge integrator unit can work independently from the tractor power, untethered from the tractor, and still broadcast data being received from the sensory devices.
- the bridge integrator unit can be queried as to status and real-time data updates whether tethered with a tractor, or untethered, such as in a parking lot.
- This feature provides the end user the ability to access the trailer network (telematically) through the MCU and request status updates from the sensory devices remotely or with assistance from onsite human interaction.
- FIG. 1 illustrates a telematics system including multiple sensing devices.
- FIG. 2 illustrates a master control unit and a wireless network around a trailer.
- FIGS. 3A and 3B are side open and top open views of a bridge integrator unit, respectively.
- FIGS. 4A-4D illustrate example circuit diagrams for use in a bridge integrator unit.
- FIG. 5A illustrates a three-dimensional representation of one embodiment of a bridge integrator unit.
- FIG. 5B illustrates an end view of the bridge integrator unit of FIG. 5A .
- FIG. 5C is a cross-sectional view of the bridge integrator unit of FIG. 5A .
- FIG. 5D illustrates a detailed three-dimensional representation of another embodiment of a bridge integrator unit.
- FIG. 5E is a cross-sectional view of the bridge integrator unit of FIG. 5D
- FIG. 5F represents a layout of a printed circuit board (PCB) in one embodiment.
- PCB printed circuit board
- FIG. 6 illustrates a detailed representation of various modules of a bridge integrator unit.
- FIG. 7 illustrates a schematic as to operation of an embodiment of a bridge integrator unit.
- FIG. 8 represents a schematic as to levels of the framework architecture integrated in an embodiment of firmware utilized for an embodiment of a bridge integrator unit.
- FIG. 9 represents a schematic as to an operational embodiment of a bridge integrator unit.
- FIGS. 10-12 illustrate a bridge integrator unit interconnected with various components of a system for communication in a trailer network.
- FIG. 13A is one embodiment of circuitry as utilized in a bridge integrator unit.
- FIG. 13B illustrates another embodiment of circuitry as utilized in a bridge integrator unit.
- FIGS. 14-28 illustrate examples of user interface screen shots of the telematics system with a widget displayed as to communication from a bridge integrator unit.
- a telematics system 500 (such as Road ReadyTM) sends, receives and stores data acquired from sensors attached to various systems and components of a trailer 512 and communicates the data to external display devices through radio frequency power line carrier or light communication, such as fiber optics. Sensors are configured to communicate with a master control unit (MCU) 525 of the telematics system, or other such external device.
- MCU master control unit
- the telematics system 500 sends, receives and stores data acquired from a light failure detection system, as indicated at 540 .
- Light failure detection system 540 is capable of multi-volt operation, such as 12V/24V, 10-30V, and 10-42V. Further, light failure detection system 540 includes LED and Incandescent Lamp capabilities (capable of determining current between LED/Incandescent), monitoring of anti-lock brake system (ABS) (On/Off), battery power for untethered operation to facilitate: asset location determination and/or asset remote diagnostic check.
- the light failure detection system 540 may be used in conjunction with multiple trailer configurations, including trailers of various sizes, dimensions, flat-beds, enclosed trailers, specifically pup trailers as defined by standards in transportation, or otherwise; and additional sensors including wireless (radio frequency (RF) or optical) or hardwired sensors may be included as well.
- RF radio frequency
- a nose box assembly 541 of the trailer communication system includes components of the light failure detection system 540 includes a wireless transmitting device with a communication protocol such as Zigbee (i.e., an IEEE 802.15.4-based specification for a suite of high-level communication protocols used to create personal area networks with small, low-power digital radios) or Bluetooth (i.e., a wireless technology standard for exchanging data over short distances from fixed and mobile devices, and building personal area networks) that will transmit signals to the master control unit (MCU) 525 or other remote device such as a laptop, tablet, or cell phone.
- MCU master control unit
- the transmitted data is acquired from the various sensors installed on the trailer 520 or asset.
- light failure detection system 540 is integrated with the nosebox assembly 541 .
- the telematics system 500 uses a cellular based trailer intelligence system to provide transportation companies with real-time updates of a trailer's roadside status.
- Telematics system 500 includes interior and exterior sensors.
- the exterior sensors include at least light failure detection system 540 , a warning sensor 532 , such as an anti-lock braking system (ABS) monitoring sensor 532 , and tire pressure/inflation sensor.
- the interior sensors include at least a temperature sensor 528 , cargo load detection sensor 530 , and a door position detection sensor 529 .
- a dispatcher evaluates the trailer's condition remotely, by utilizing an online dashboard, or via a remote user interface, prior to dispatching a driver. If a failure occurs, the dashboard will instantly notify the dispatcher.
- a wireless network is provided around the trailer using a solar-powered master control unit (MCU) 525 placed on the roof of the trailer. Wireless sensors are then placed inside and outside of the trailer. If a failure occurs, the telematics system will instantly detect it and report the failure to an alert dashboard at a remote or local user interface.
- MCU master control unit
- the ABS monitoring sensor 532 detects if the ABS light illuminates. When tethered to a tractor, the sensor reports the information to the system 500 , and indicates the failure to the alert dashboard. Multiple tire pressure monitoring sensors detects if a specific tire pressure is too low or if the inflation system has been running too long. The information reported back to the alert dashboard depends on the type of tire system installed on the trailer.
- Real-time updates from the temperature sensor provides the customer with time and location stamped temperature history during transit.
- Real-time updates from the cargo load detection sensor 530 allow the customer to know exactly when a trailer is loaded or unloaded.
- the cargo detection zone is located directly under the sensor's location. Real-time updates are also provided from the door sensor to provide the customer with time and location stamped door positions. Custom alerts can be setup for unauthorized door openings or improper closing, to help detect theft and product contamination.
- FIG. 1 shows the telematics system 500 for use with a truck trailer 512 having top 514 , bottom 516 , front 518 , and side surfaces 522 and 523 .
- Doors 519 are positioned at a back end of truck trailer 512 .
- Truck trailer 512 may be a dry-van semi-trailer shipping container or a refrigerated shipping container.
- Master control unit (MCU) 525 attached to top 514 of truck trailer 512 .
- Wireless sensors such as a temperature sensor 528 , three-axis accelerometer door sensor or door position detection sensor 529 , an ultrasonic load sensor or cargo load detection sensor 530 are positioned within trailer 512 and are in wireless communication with a local wireless network master transceiver module of the MCU 525 .
- Warning ABS sensor 532 , bridge integrator unit 600 , and light failure detection system 540 are all located external to the trailer 512 .
- MCU 525 includes solar cells 550 and an electronics module 552 , which are integrated into a one-piece unit as described below.
- MCU 525 is comprised of at least about six main parts: a cellular module, a GPS, an RF wireless xBee module, a microcontroller, a rechargeable lithium-ion battery and a military grade flexible solar film.
- Charging circuitry allows MCU 525 to use on average 3% of the battery while charging as much as 15% per hour. In the absence of sunlight, MCU 525 continues to report for 60 days due to specialized back-off controls. The solar panel continues to charge even in low sunlight conditions and heavy cloud coverage.
- the solar cells 550 converts light energy, such as from the sun, into power for operation of the electronics module 552 .
- the local wireless network master transceiver module of MCU 525 comprises the master node in a local wireless network with the wireless sensors.
- An exemplary wireless network uses the hardware specified by IEEE standard 802.15.4 coupled with a proprietary communication protocol.
- the local wireless network allows sensor data from wireless sensors in the network to be gathered by MCU 525 and transmitted using the cellular data transceiver module of MCU 525 .
- Examples of the MCU 525 are :005-197-502—Verizon (CDMA) with internal Zigbee—allows use of additional sensors, such as temp, cargo, door, and fuel sensors; 005-197-501—AT&T (GSM) with internal Zigbee—allows use of additional sensors, such as temp, cargo, door, and fuel sensors; 005-198-502—Verizon (CDMA) without internal Zigbee—tracking only, no additional sensors; 005-198-501—AT&T (GSM) without internal Zigbee—tracking only, no additional sensors.
- Bridge integrator unit 600 is shown in side open and top open views, respectively.
- Bridge integrator unit 600 includes a plastic enclosure 553 , with a cover 554 and sealing interface 555 for internal power and ground wires.
- the bridge integrator unit uses a direct sequence spread spectrum (DSSS) radio module to gather RF signal data from products installed on trailer 512 .
- DSSS direct sequence spread spectrum
- the radio communications are used with STEMCO RF signal data, for exemplary purposes and not limitation, from STEMCO products, such as an automatic tire inflation system, a mileage sensor, or a single or dual tire pressure monitoring sensor.
- Bridge integrator unit 600 may be referred to as a “smart bridge”, or hub, due to its functionality of bridging (and/or translating) communications of customer products, (e.g., here, STEMCO products) with communications to the MCU 525 .
- the bridge integrator unit connects directly to the customer device communications, for example, RS232 or CAN bus, or through a WiFi connection via RF communications, and serves as a hub to translate the communications to a remote server.
- the bridge integrator unit comprises hardware, software, and firmware.
- Bridge integrator unit 600 includes circuitry, as shown on circuit board 551 , that translates a signal from one communication signal into another messaging format. For example, an RF signal from the sensors may be translated into a secondary messaging format. Once the signal is converted to the secondary format, the messages are delivered to MCU 525 through a ZigBee network.
- the low power communication protocol ZigBee is power efficient and has additional capability to extend the network.
- Bridge integrator unit 600 may be powered by a blue circuit wire and/or a rechargeable lithium-ion battery.
- FIGS. 4A-4D are examples of detailed circuitry for bridge integrator unit 600 .
- FIG. 4A shows U 2 , which is one diode circuit to reduce losses. The remainder of the circuit provides battery charge current.
- FIG. 4B shows U 1 , which is an OP AMP used to buffer/measure the voltage at the battery as it is charging. U 4 provides regulated 3V power for the system.
- FIG. 4C includes main controller (U 6 ), and IEEE 802.15.4 transceiver (U 5 ) for connection to the Zigbee network and communication with MCU.
- 4D includes a temperature sensor to monitor ambient temperature (U 10 ), an extra memory for controller (U 8 ), a 2.4 GHz wireless modem for non-Zigbee communication (U 11 ), and an accelerometer (U 9 ) to detect when the vehicle is in motion.
- FIG. 5A illustrates a three dimensional perspective view of a bridge integrator unit 600 .
- Bridge integrator unit 600 is configured to be coupled to a surface of a trailer or other mounting structure and may have various shapes and structures depending upon the surface of the trailer.
- the embodiments detailed herein represent, but are not limited to, bridge integrator unit 600 having a stepped mount sealed housing ( FIGS. 5A-5C ) and a flat mount sealed housing ( 5 D- 5 E).
- FIGS. 5A-5C stepped mount sealed housing
- 5 D- 5 E flat mount sealed housing
- FIG. 5A, 5B, and 5C illustrate three-dimensional, side and cross-section views of bridge integrator unit 600 having a stepped mount sealed housing 602 configured to be coupled to a stepped or un-stepped surface of a trailer.
- Housing 602 includes a top surface 605 , a bottom surface 606 , first and second ends, 607 and 608 , and first and second sides, 610 and 611 . Each of first and second sides, 610 and 611 , and a laterally extending stepped flange 613 , 614 extending therefrom.
- FIG. 5B is an end view of bridge integrator unit 600 .
- First end 607 includes openings (not shown) through which overmolded connectors 617 , 618 extend for coupling to power and ground wires.
- ends 607 , 608 of housing 602 may be end plates fastened to housing 602 with a plurality of fasteners, such as screws 620 .
- Other configurations of housings may be permitted to serve similar design and functionality.
- Bridge integrator unit 600 may either receive power from an external source, such as a blue line power of a trailer, or a backup battery 623 , such as a rechargeable lithium-ion battery, as shown in FIG. 5C . Further, the lithium-ion battery may be used to deliver constant power to the bridge integrator unit 600 via a blue circuit wire.
- the embodiments described herein are not limited to lithium-ion battery for delivering power to bridge integrator unit 600 .
- Other types of batteries for example, aluminum-ion battery, vanadium redox battery, zinc-bromine battery zinc-cerium battery, lead-acid battery, thin film lithium-ion battery, magnesium-ion battery molten salt battery, nickel-cadmium battery, etc. may also be used to deliver power to bridge integrator unit 600 .
- a light emitting diode indicator light 622 is provided to indicate the status of bridge integrator unit 600 .
- an LED typically ranging from 520 nm ⁇ 550 nm may be used to indicate status of bridge integrator unit 600 .
- indicator light 622 may emit green light when bridge integrator unit 600 is in an active state and no light when bridge integrator unit 600 is turned off.
- FIG. 5C further illustrates housing 602 having support ribs 625 to reinforce the strength of housing 602 and a support element 627 for securing battery 623 .
- a slot 630 is also provided for supporting the circuit board 650 (See FIG. 5F ) within housing 602 .
- FIGS. 5D and 5E illustrate detailed three-dimensional and cross-sectional views of bridge integrator unit 600 with a flat mount sealed housing 602 ′ which may be coupled to flat surface of a trailer.
- Housing 602 ′ includes a top surface 605 , a bottom surface 606 , first and second ends, 607 and 608 , and first and second sides, 610 and 611 .
- Each of first and second sides. 610 and 611 has a laterally extending flat flange extending therefrom at 613 ′ and 614 ′.
- a plurality of apertures, each indicated at 615 are formed in first and second laterally extending flat flanges, 613 ′ and 614 ′, for receiving fasteners for mounting bridge integrator unit 600 to a flat surface of a trailer or mounting structure.
- Each of the remaining components of bridge integrator unit 600 shown in FIGS. 5D-5E correspond to those discussed for FIGS. 5A-5C .
- FIG. 5F is a detailed view of an exemplary circuit board 650 for use with bridge integrator unit 600 .
- bridge integrator unit 600 may comprise various modules.
- FIG. 6 illustrates a detailed representation of bridge integrator unit 600 comprising various modules.
- Bridge integrator unit 600 comprises a power/battery module 806 , a wired interface 802 , a microcontroller 814 , wireless modules 804 , and auxiliary connections 808 .
- the bridge integrator unit 600 also comprises various interfaces such as serial peripheral interface (SPI), universal asynchronous receiver-transmitter (UART) and analog-digital conversion (ADC) interfaces.
- SPI serial peripheral interface
- UART universal asynchronous receiver-transmitter
- ADC analog-digital conversion
- Bridge integrator unit 600 may utilize the modules for receiving data from one or more sensory devices or a plurality of sensors, and further send the data to a remote user interface.
- the sensory devices installed on the trailer 512 may comprise various types of sensors which are used to sense and/or record values of multiple parameters.
- the sensors may be wired or wireless sensors; as depicted, for representation and not limitation, the sensors are wireless.
- Such sensors may include: a temperature sensor 528 , three-axis accelerometer door sensor or door position detection sensor 529 , an ultrasonic load sensor or cargo load detection sensor 530 etc.
- the sensors may be positioned on surface of the trailer 512 and may communicate either via wireless interface or via wired interface.
- the sensors may further send or receive data from a local wireless network master transceiver module of the MCU 525 .
- the MCU 525 may also integrate additional sensors to include customer requested sensory data, as desired, and not limited to, including temperature, tire pressure, trailer weight, cargo, door and fuel sensors, among others for monitoring various parameters of the trailer 512 .
- the MCU 525 may also transmit a plurality of signals to the trailer 512 regarding certain conditions or alerts sensed by the warning sensor 532 .
- the sensor 532 generates a plurality of messages such as, P-power up, E-alert, S-Status, R-resolved and Y-acknowledgment which may be transmitted to the trailer 512 from the MCU 525 .
- sensory data may be transmitted to a bridge integrator unit, otherwise disclosed as a bridge integrator unit 600 that is capable of intake of a multitude of network communications, specifically radiofrequency identification (RFID), a controller area network (CAN bus), universal (synchronous) asynchronous receiver/transmitter (UART), or as specifically designed; the input can then be integrated with the communication architecture to provide an output for communications to a user.
- RFID radiofrequency identification
- CAN bus controller area network
- UART universal (synchronous) asynchronous receiver/transmitter
- the CAN bus standard design allows microcontrollers and devices to communicate with each other in applications without a host computer.
- the UART is responsible for sending and receiving a sequence of bits, the output of these UART bits usually represented by logic level voltages. These bits can be RS-232, RS-422. RS-485, or perhaps some proprietary specification.
- RS-232 is referenced, as integrated in the bridge integrator unit 600 , though the system remains open to the potential for a variety of communications and protocols to be input and integrated at the bridge integrator unit.
- Messages are sent to the MCU if and when a condition change arises at one of the monitoring sensors on the trailer 512 , or when data declines below or exceeds a defined threshold value.
- An update may also be sent to an operator of the trailer 512 , or to a remote interface.
- the directionality of messaging can be uni-directional, sending to the MCU; or the directionality may be bi-directional whereby the bridge integrator unit can be queried by a remote device, input with data from an external source, or otherwise automatically queried for data at intervals or set timepoints.
- the sensory devices may communicate with the bridge integrator unit 600 through a wired interface 802 , which may include a CAN interface 810 , a RS232 interface 812 , or as selected for directing wiring.
- CAN interface 810 is a small-footprint external CAN flexible data-rate (CAN FD) controller that communicates with microprocessor 814 via a serial peripheral interface bus (SPI) 815 .
- SPI serial peripheral interface
- the serial peripheral interface (SPI) is a synchronous serial communication interface specifically used for short distance communication, typically embedded in the system(s).
- CAN interface 810 typically supports two types of formats for transmission and reception of CAN frames, classical format (CAN 2.0B) or CAN flexible data Rate (CAN FD) format as specified in ISO11898-1:2015. Further, CAN interface 810 has an arbitration bit rate up to 1 Mbps and a data bitrate of up to 8 Mbps. Bidirectional communication with bridge integrator unit 600 is achieved by configuration of 31 FIFOs of CAN interface 810 . Typically, CAN interface 810 employs a VDD power supply of 2.7V-5.5V for its operation.
- a plurality of sensors may communicate with bridge integrator unit 600 via the RS232 interface 812 .
- Data related to the trailer 512 may then be sent to microprocessor 814 via a UART (universal asynchronous receiver-transmitter) 816 .
- the UART may accept data in byte format and may transmit the data in bit format in a sequential fashion, or as desired depending on communication protocols.
- the RS232 interface 812 may be used to convert logic level signals of the UART to and from the external signaling levels, which may be standardized voltage levels, current levels, or other signals.
- the received sensor data may be sent by RS232 interface 812 as a time-series of bits. Further, the interface may operate in a duplex manner, supporting concurrent data flow in both directions from the bridge integrator unit 600 and may support both synchronous and asynchronous data transmission.
- serial peripheral interface bus is a synchronous serial communication interface specifically used for short distance communication, typically embedded in the system(s).
- SPI devices communicate using master-slave architecture with a single master device or with one or more slave devices. Multiple slave devices are supported through selection with individual slave select (SS) lines.
- SS slave select
- bridge integrator unit 600 includes a microprocessor 814 , which is a 24-bit processor, e.g. PIC24FJ microcontroller with integrated peripherals for segmented or graphical displays, USB-OTG, motor control and capacitive touch implementation.
- Microprocessor 814 may also have intelligent analog integration, and include 10, 12, 16, 20 bit processors, -bit analog-to-digital converters (ADCs), digital-to-analog converters (DACs), and operational amplifiers in the smallest form factors available.
- ADCs analog-to-digital converters
- DACs digital-to-analog converters
- Microprocessor 814 receives data from one or more of wired interface 802 , wireless modules 804 , and auxiliary connections 808 . Data may then be sent to MCU 525 .
- the bridge integrator unit 600 may be referred to as a hub to intake data coming from sensory devices that belong to different manufacturers and translate that data to a uniform language for communication with a master control unit that updates an operator or user at a user interface.
- Sensory devices having multiple communication channels, such as RS232, CAN, and UART may transmit and receive messages in a comma delimited format, or as otherwise designed, to and from bridge integrator unit 600 .
- wireless modules 804 are adapted to transmit and receive data between bridge integrator unit 600 and MCU 525 .
- Wireless modules 804 comprise, for example, a Bluetooth module 818 , a radiofrequency module 820 and internal wireless protocol module 834 .
- Bluetooth module 818 transmits data received wirelessly from the sensory devices to microcontroller 814 via UART transmitter 819 .
- Radiofrequency module 820 and internal wireless protocol module 834 transmit data received from the wireless sensory devices to microcontroller 814 via one or more SPIs 821 and 822 , respectively.
- Internal wireless module 834 also can transmit data directly to MCU 525 . Sensory data from multiple communication protocols is translated at the internal wireless module 834 to a firmware language that communicates directly with the MCU 525 , and using a radio frequency band of IEEE 802.15.4 or other wireless communication.
- the module 834 may be a 2.4 GHz IEEE Std. 802.15.4 compliant, surface mount module with integrated crystal, internal voltage regulator, matching circuitry, power amplifier (PA), low noise amplifier (LNA) with PCB trace antenna (MRF24J40MD) or 50 ⁇ external antenna connector (MRF24J40ME), or other compatible device comparable in the state of the art.
- the module 834 is configured to operate in a non-licensed 2.4 GHz frequency band and may minimize use of extensive RF and antenna design.
- the module 834 is based on microchip technology of MRF24J40 2.4 GHz IEEE 802.15.4 RF transceiver IC. After the sensory data is converted into a common protocol, the data is transmitted to MCU 525 .
- the MCU controls a local wireless network master transceiver module to periodically obtain sensor data from one or more wireless sensors directly, or through a bridge integrator unit that translates the message to a readable form, and further controls access to the data via a cellular data transceiver module to transmit location and sensor data of trailer 512 to a remote user interface.
- the processor 6 utilizes wired interfaces 810 , 812 , alone or in combination with wireless RF module 820 to pull information from wireless sensors on a trailer (or other external tracked asset) into the processor that is part of microcontroller 814 .
- the processor translates the message received from those communication avenues into a secondary communication protocol to provide messaging and communication feedback to an operator or user at a user interface.
- the secondary communication protocol can be queried directly from the user interface, or may be displayed at the user interface via the messaging through the MCU of the trailer. Either way, direct or indirect access through the MCU, the data conveyed via the bridge integrator unit is consistent with ongoing user communications and displayed in real-time.
- the bridge integrator unit may be accessed remotely via the user interface, or through the MCU, in real-time.
- Bluetooth LE module 818 is a low-energy Bluetooth module, which supports UART, I2C, and SPI interfaces.
- Bluetooth module 818 works on an ISM Band from 2.402 GHz to 2.480 GHz over 0-39 channels and typically has a reception sensitivity of ⁇ 90 dBm.
- Bluetooth module 818 may provide operate in low energy conditions for embedded applications. It conforms to Bluetooth core specification version 4.2 to enhance the throughput and security for IoT applications.
- Bluetooth module 818 may also support bacon technology to enhance user experience for the IoT applications and enables users to control data in the cloud and receive data without opening the application through a smart phone.
- Bluetooth stack is integrated and is available in different form factor to optimize the space, cost, and RF performance. For portable and wearable applications, it provides power-optimized design to minimize the current consumption to extend the battery life.
- RF module 820 may be a AW24MCHL-H2 transceiver in wireless modules 804 which has a 2.4-GHz direct sequence spread spectrum (DSSS) complete radio module and includes Cypress radio integrated circuit CyFiTM CYRF7936, integrated antenna, and various external components.
- DSSS direct sequence spread spectrum
- the wireless RF module offers a radio module solution for integration into existing or new 2.4-GHz products.
- Data from the RF module 820 , and associated sensing units, is sent to the bridge integrator unit 600 via the SPI bus for data transmission/reception to MCU 525 .
- Bridge integrator unit 600 also includes auxiliary connection module 808 with a flash memory 823 and a debug port 824 .
- Embodiments herein may incorporate various auxiliary connections as needed for storage and retrieval of information, security systems, or otherwise.
- flash memory 822 may utilize lower voltages for programming. Memory 822 may operate from a single 1.7V to 3.6V power supply for the erase and program and read operations. Flash memory 822 is enabled through the chip select pin (CS) and accessed via a 3-wire interface consisting of the serial input (SI), serial output (SO), and the serial clock (SCK). It is compatible with SPI 825 for communication with microcontroller 814 .
- Debug port 824 is used to simplify development and debugging, but its functions are not limited and can be used for multiple functions by a person skilled in the art. Data to/from microprocessor 814 is transmitted from/to the debug port 824 via an SPI interface 826 .
- Debug port 824 is compatible with low end communication protocols such as I 2 C (e.g., for ‘Inter-Integrated Circuit’, protocol) and SPI (e.g., for ‘Serial Peripheral Interface’), among others. Both protocols are well-suited for communications between integrated circuits, and for slow communication with on-board peripherals.
- Bridge integrator unit 600 further includes a power and battery sub-system 806 , which includes a disconnectable input voltage sense sub-system 827 , a disconnectable battery voltage sense sub-system 828 , a power management sub-system 830 and a boost regulator 832 .
- Power supplies are often designed to operate in 120 VAC and 220 VAC input voltage range.
- An automatic disconnectable input voltage-sensing switch 827 as shown in FIG. 6 , the input voltage can be sensed so that the power supply can automatically switch between two or more input ranges.
- An analog-to-digital converter (ADC_ 1 ) 834 converts an analog signal from the power supply into a digital signal to be sent to microcontroller 814 .
- ADC_ 1 analog-to-digital converter
- power and battery sub-system 806 also includes a disconnectable battery voltage sense unit 828 for sensing a battery's voltage.
- the sensed voltage may be translated and sent to microcontroller 814 via an analog-to-digital converter (ADC_ 2 ) 836 , which converts an analog signal from the power supply into a digital signal to be sent to microcontroller 814 .
- ADC_ 2 analog-to-digital converter
- the battery back-up system described here allows for a trailer to be monitored via the bridge integrator unit when tethered with direct battery connection, and for communication with the bridge integrator unit when the trailer is untethered from a tractor. Power and battery sub-system 806 , as shown in FIG.
- power management sub-system 830 for regulating the trailer's input power supply, which may be from input trailer voltage 835 , voltage from a battery 836 , or system voltage 838 . Under normal operation, the trailer's input voltage is about 12 volts, but may be modified as appropriate or desired to provide power efficiency and maintenance.
- Power and battery sub-system 806 also includes reverse connection protection and a lithium ion battery, which may have an input voltage of 3.6 volts under normal operation.
- a boost regulator 832 is provided which may receive power from a CAN transceiver (e.g., active receiver antennae) 840 , or any suitable DC sources, such as batteries, solar panels, rectifiers and DC generators. In the present embodiment, the boost regulator 832 is a DC to DC converter providing 5 volts greater than the source voltage. Boost regulator 832 may also be referred as a step-up converter since it “steps up” the source voltage.
- the system 1200 illustrates a process at 1200 (A) to start-up 1202 , bootload initialize 1204 , and upgrade 1206 prior to any launch of interrupt service routines (ISRs) 1218 for communications through the application initialization 1214 , and/or execution of associated tasks 1222 via the process at 1200 (B).
- ISRs interrupt service routines
- a power up or reset signal 1202 is generated when power is applied to bridge integrator unit 600 .
- the boot loader present in the framework 1408 (See FIG. 8 ) is initialized and loads system software for the bridge integrator unit, or bridge integrator unit 600 .
- the logic proceeds to inquire at 1206 as to any firmware or upgrades for the system. If additional or revised firmware is available, a copy of the firmware is copied to a microchip controller at 1208 .
- the controller is represented as a PIC controller ROM. This is comparable to a software update followed by an upload and/or restart of the system. If not updated firmware is available, the integration application proceeds to start at 1212 .
- the application is initialized at 1214 , followed by a step of turning off any unused interfaces 1216 .
- the ISRs are launched 1218 , generating a dispatch message at step 1220 , through a protocol 1404 , as encoded at the dictionary or hexadecimal coding level, protocol of which relates to information as to the message designated by the plurality of sensing devices.
- the messaging protocol here, as encoded by the hexadecimal (or other coding) library, designates the specific tasks 1222 to be monitored.
- the firmware as described, indicates when an issue arises as to the specific sensing device parameters, and data that falls outside a range or threshold values so as to indicate the issue.
- the system may handle various types of interrupt service routines (ISRs) such as Jiffy Tick 1224 (i.e., updating time variations 1226 ) or RTC 1228 (i.e., real-time clock given 1 minute periods 1230 , though any designated timing may be utilized) embedded in the framework 1408 .
- ISRs interrupt service routines
- An interface handler 1232 of the hardware abstraction layer 1402 has various communication channels 1234 including, but not limited to, RF (802.15.4), BTLE, CAN bus, CyFi, RS232, among others.
- the blue line 1236 is used to choose an interrupt from a plurality of interrupts and querying as to state changes 1238 having 30 second debounce periods. Here, the status is queried every 30 seconds.
- the system continues to query here unless there is no state change.
- the logic queries as to whether the trailer is tethered 1240 . If yes, then the blue line is tethered 1242 , and the battery connection to the bridge integrator unit is directly connected to the power supplied by the tractor to which the trailer is tethered. If not tethered, the blue line is untethered 1244 , and thus the bridge integrator unit proceeds to utilize its battery backup.
- an interface handler 1232 enables communication between sensors and bridge integrator unit 600 via wired RS232 interface 812 and CAN interface 810 , as also previously shown in FIG. 6 .
- the interface handler operates in the hardware abstraction layer (HAL) 1402 of FIG. 8 .
- the interface handler 1232 enables communication between bridge integrator unit 600 and MCU 525 via a secondary language protocol, (e.g., TRiPST Module 834 , Bluetooth LE module 818 and RF module 820 as also previously shown in FIG. 6 .
- the interface handler 1232 also monitors the tethered/un-tethered state of the blue power line.
- the interface handler 1232 also allows a choice of an interface from a plurality of available interfaces.
- the system may choose a service from 802.15.4, BTLE, CAN Bus, CyFi or RS232 interfaces.
- Flow level chart 1222 (A) illustrates third party protocols at step 1246 , communicating with the remote user interface 255 .
- parameters are customized according to customer demand and sensing units utilized, capturing real-time data from the sensors when queried, such as light failure detection system 540 , warning sensor 532 , anti-lock braking system (ABS) monitoring sensor 532 , tire pressure/inflation sensor, temperature sensor 528 , cargo load detection sensor 530 , and a door position detection sensor 529 .
- light failure detection system 540 warning sensor 532 , anti-lock braking system (ABS) monitoring sensor 532 , tire pressure/inflation sensor, temperature sensor 528 , cargo load detection sensor 530 , and a door position detection sensor 529 .
- ABS anti-lock braking system
- the bridge integrator unit queries sensors every 2.5 seconds, or as coded in the system.
- the data is translated at the bridge integrator unit, and if changed from a previous state or outside a range or threshold, pushes the data to the MCU.
- the remaining data static data of which remains unchanged or unused for a certain time period, is removed and conserves storage space.
- FIG. 1222 (B) illustrates a process to determine if the blue power line of a tractor-trailer is connected to a bridge integrator unit 600 . If bridge integrator unit 600 is in power saving mode as shown in step 1250 , the blue power line is monitored at step 1252 as to whether the firmware is connected to the blue line. The system 1200 checks to see if tasks are in process at 1254 ; if no task in process, then bridge integrator unit goes into sleep mode 1256 for a time designated, here at least about 2 minutes.
- logic level flow diagram 1222 (F) illustrates the downloading of updated firmware at step 1292 .
- a message is received by the bridge integrator unit at step 1294 . If the message is not received, the query returns to the firmware receive message 1294 . If the message is appropriately received 1296 , the check sum of the received data is calculated to determine any erroneous data 1298 . If the check sum is okay, the system prepares for bootload 1300 , and the system resets 1304 . If the check sum is not okay, the firmware update is discarded 1302 .
- the tasks 1222 of the bridge integrator unit firmware logic simultaneously monitors data queried by the MCU.
- the PAD inquires whether additional interface data is present 1260 , whether a data request has been sent 1262 , and whether data has expired 1264 . If affirmative for any of steps 1260 , 1262 , 1264 , the system intakes various forms of data to store 1266 , retrieve 1268 , or purge 1270 the data. Note that after the date has been retrieved, it is purged. Following storage 1260 and purging 1270 , the dictionary is updated.
- the manage dictionary functionality of the protocol agnostic database intakes the messaging from RF, CAN bus, and RS232 transmissions and information corresponding to specified sensors within the assigned monitored parameters.
- one customer may request tire pressure monitoring.
- the smart bridge integrator can interconnect with a device control unit of the particular customer to pull raw data into a user-based system to monitor and access that data via a common interface.
- the bridge integrator unit facilitates this communication, and rather has the capability to pull all streams of data to translate into secondary messaging to the user, customer, or fleet operations.
- the bridge integrator unit intakes the data via a CAN bus communication line, pinging the sensors at regular intervals, such as every 2.5 seconds.
- the messages are translated, at the bridge integrator unit, for example, encoded into hexadecimal format at the dictionary. If the data is consistent with specifications provided, the system purges the data. If the data changes, to indicate an issue, the bridge integrator unit relays the information in a uniform proprietary language, or secondary language, at a particular RF frequency to a master control unit (MCU). The MCU transmits the information to a designated user interface.
- MCU master control unit
- logic level flow diagram 1222 illustrates the process of TripsNet secondary messaging 1306 initializing followed by queries to send a message 1308 , acknowledge a sent message 1310 , and query whether a message was received 1312 .
- step 1308 if a message is generated, a communication to the MCU 525 is transmitted via TripsNet at step 1314 . If the sent message is not acknowledged by the TripsNet protocol in the framework of the MCU 525 , the message shall be sent again at step 1316 . If the message is received by MCU 525 at step 1312 , the message is stored 1318 .
- logic flow chart 1222 (D) illustrates a process of transmitting a dispatch message to the third parties.
- the scheduler monitors the operation of the dispatch message. Once the scheduler detects that time has exceeded a specified time 1276 , here 24 hours, the dispatch message is sent 1278 .
- logic level flow chart 1222 (E) monitors the tethered and un-tethered state of the blue power line with the bridge integrator unit.
- the blue power line is associated with the tractor; and the firmware associated with the bridge integrator unit is in connection with the trailer unit.
- the sensor sample time is being monitored at step 1280 .
- the blue power line status is monitored. If the blue power line is tethered to the bridge integrator unit, the sensor data is sampled after every 60 seconds at 1284 .
- the system queries whether the bridge integrator unit was untethered for a duration of time at 1286 ; here, for example, the query asks if the bridge integrator unit was untethered for more than a week. If untethered more than the specified duration of time, sampling of the bridge integrator unit is queried in increments 1290 . Here, for example, sampling would then occur every 1 minute. If the blue line is not untethered for more than a week, sampling occurs for another specified period of time 1288 , here selected at about every 5 minutes.
- the tethering of the bridge integrator unit references whether a trailer is connected to the tractor; when untethered, the trailer (and thus, associated bridge integrator unit) is detached, or untethered from the trailer. This allows a user or operator to determine how long a trailer has sat at a delivery, in a parking lot, or at another designated or unknown location.
- logic level flow diagram 1222 (H) illustrates the process of determining the connection state of the blue power line (BL).
- the bridge integrator unit monitors the tethered or untethered state 1320 of the blue power line.
- a connection/disconnection message 1322 is sent in order to check whether the status of the blue power line has changed 1324 . If the state has changed at 1324 , the system queries whether the blue power line is tethered/connected 1326 . If the blue power line is tethered at step 1326 , a connection message 1328 is sent. If the blue power line is untethered at step 1326 , a disconnect message 1330 is sent.
- a bridge integrator unit system 1400 illustrates a broad view of firmware logic levels of framework 1408 which provide controls for a bridge integrator unit 600 , including specific hardware and software/firmware.
- Framework 1408 may store sensor data.
- the sensor data may come from light failure detection system 540 , warning sensor 532 , anti-lock braking system (ABS) monitoring sensor, tire pressure/inflation sensor, temperature sensor 528 , cargo load detection sensor 530 , a door position detection sensor 529 , among other parameter sensing devices and sensors.
- the system 1400 an operating environment and architecture for bridge integrator unit and also provides additional levels of programming and integrated hardware and/or software to perform control, monitoring and manipulation of data functions.
- the system 1400 may be held in a non-volatile memory device which may be flash memory 822 as previously shown in FIG. 6 , or storage within the bridge integrator unit.
- the hardware abstraction layer 1402 and protocol agnostic database 1404 , along with third party protocols 1406 are built on top of framework 1408 .
- the manage dictionary 1272 allows communication and translation of data that is received from either RF. CAN bus, and/or RS232. Various other communications may be identified and integrated at the bridge integrator unit also.
- FIG. 9 represents an example of flowchart logic as to a bridge integrator unit 1500 for a tire pressure sensing system.
- the system 1500 is capable of setting up communications 1500 (A) with a third party device and third party communications network.
- the system further integrates the third party communications 1500 (B) for further translation and status update communications to a user interface.
- the flow diagram 1500 (A) establishes whether bridge integrator unit 600 is configured for pressure check (CPC) or not. Once bridge integrator unit 600 is configured for pressure check (CPC), the logic flow level diagram 1500 (B) initiates CPC protocol.
- CPC pressure check
- Step 1504 where a device control unit 1604 (will be detailed in the below embodiments) generates a request to obtain CAN driver information. Further, the flow level diagram proceeds to Step 1506 , which is a conditional statement to check whether bridge integrator unit 600 is configured for pressure check (CPC) or not. In the case where the bridge integrator unit 600 is configured for pressure check (CPC), the logic level flow proceeds to step 1508 . When bridge integrator unit 600 is not configured for pressure check (CPC), the logic level flow waits to configure bridge integrator unit 600 for pressure check (CPC).
- CPC pressure check
- the system then sets up the CAN interface for PGN 1508 which is a deeper level firmware for data storage.
- the logic flow level proceeds to store 1510 the incoming PGN data in the database.
- the step 1510 works in a loop because the PGN data is not stored in the database for a long duration of time.
- the data stored in the database is discarded once the vehicle shuts off, or once the signal or issue is resolved.
- the system is designed to save memory and storage space. As mentioned prior, the data is stored in the database library in hexadecimal format, or coding as desired.
- the logic flow level diagram 1500 proceeds via the CPC protocol handler 1512 .
- the system protocol checks to see as to whether the CPC data is stored 1514 in the database or not. If the CPC data is not stored in the database, the logic flow level waits until the CPC data is stored 1514 in database. Once the CPC data is stored in the database, the logic flow level diagram proceeds to step 1516 .
- the step 1516 is a conditional statement which checks whether the pressure recorded by tire pressure monitoring system (TPMS) is out-of-bounds or not. If the recorded pressure is out-of-bounds, the logic flow level proceeds to check whether or not an alert has been sent 1518 ; otherwise the logic flow level proceeds to step 1524 . If the alert has not been sent at 1518 , then a secondary messaging alert 1522 via a TripsNet protocol is sent to the MCU. If the alert is already sent at step 1518 , the logic proceeds to check whether the alert timer has expired at step 1520 . If yes, then a secondary messaging alert 1522 via a TripsNet protocol is sent to the MCU. If the alert has not expired, the logic proceeds to check the next condition, here temperature at 1528 .
- TPMS tire pressure monitoring system
- a condition is checked whether the system was previously in alert or not. If the system was previously in the alert state, the logic proceeds to resolve the secondary messaging command at step 1526 , here, the TripsNet resolve. Otherwise, the logic flow proceeds to step 1528 . Note that the TripsNet resolve command returns the system back to normal after correcting the pressure monitored by the TPMS.
- a temperature check is performed for the measured tire conditions.
- the step 1528 checks whether temperature of the TPMS is out-of-bounds or not. If the recorded pressure is out-of-bounds, the logic flow level proceeds to step 1530 where an already sent alert is monitored, otherwise the logic flow level proceeds to step 1536 .
- the step 1536 checks whether the system is previously in alert or not. In case the system is in the alert state, the logic flow level proceeds to step 1538 where a TripsNet resolve command is issued, otherwise the flow proceeds to step 1540 .
- Tripsnet resolve command returns the system back to normal after correcting the pressure monitored by the TPMS.
- the logic flow level checks if the system has already sent an alert or not. If the alert is already sent, the logic proceeds to step 1532 ; otherwise, if the alert is not sent, the logic flow proceeds to step 1600 , where the system generates a TripsNet alert.
- step 1532 is the system checks if the alert timer has expired or not. If the alert timer has expired, the logic proceeds to step 1600 , where the system generates a TripsNet alert; otherwise the logic flow level proceeds to step 1540 .
- step 1540 of the logic various other parameters related to the monitored TPMS are checked, as designated and designed by user, operator, and/or customer.
- the parameters may be low battery, wrong orientation, loose connections, or other monitoring parameters or controls.
- the logic proceeds to step 1542 as to whether or not a message was sent. If the checked parameters are within required limits, the logic flow level proceeds to inquire whether the status period is over at step 1546 .
- step 1542 the system checks if message had already been sent or not regarding parameters within or exceeding ranges and thresholds. In case the message had not been sent, the logic flow level proceeds to step 1544 where a TripsNet message is sent; otherwise, the logic flow level proceeds to step 1546 to inquire whether the status period is over.
- the issued TripsNet message at step 1544 is sent in order to return the trailer to the authorized dealer, as may be appropriate where sensor controls are not within a control or modification protocol via interfaces such as the bridge integrator unit or MCU.
- the system checks if the status period is over or not by noticing a time out period. In case the status period is over, the logic proceeds to send a TripsNet status message 1548 as to that terminated status period. Otherwise, the logic returns to step 1514 to check if the CPC data is stored in database or not.
- This CPC data protocol is one embodiment that is demonstrated for exemplary purposes and not limitation. Similar protocols may be designed and implemented to adapt to customized management and monitoring of various systems capable of communicating with the bridge integrator unit.
- FIG. 10 illustrates bridge integrator unit 600 and its communication with various components of the telematics system, such as a device control unit 1604 and a trailer ECU 1602 .
- the ECU is the electronic control that bridge integrator unit 600 receives a 12V power via power line 1605 from a power line carrier (PLC) 1610 .
- PLC power line carrier
- bridge integrator unit 600 also comprises a battery 620 for delivering power to microprocessor 1606 .
- Bridge integrator unit 600 also includes SPI or UART interface 1614 for connecting CANBUS in order to transfer sensory data between microprocessor 1606 and device control unit 1604 via a wired interface SPI or UART.
- the device control unit 1604 may receive sensory data from a plurality of sensors installed on the trailer 512 .
- the bridge integrator unit 600 also comprises a CAN interface 1616 for communicating trailer 512 data received by a plurality of sensors to PCB-A 1606 .
- Power Line 1620 provides a voltage of 12V to the device control unit 1604 which receives data from a plurality of sensors and transmits the received data to microprocessor 1606 of bridge integrator unit 600 .
- Bridge integrator unit 600 further transfers the data received from a plurality of sensor devices to the master control unit (MCU) 525 via wireless radio frequency (RF) interface.
- MCU master control unit
- RF wireless radio frequency
- FIG. 11 illustrates a detailed view of communication between various components of the network.
- Bridge integrator unit 600 receives data from a plurality of sensors installed on the trailer 512 via wired or wireless interfaces.
- Bridge integrator unit 600 may receive sensory data through various wired communication modes such as RS232, CAN, etc.
- Bridge integrator unit 600 may also receive data related to the tires 1622 of the trailer 512 through various sensors installed on the tires 1622 of the trailer 512 .
- the data received from the sensors installed on the tires 1622 may represent various tire conditions such as tire pressure, tire inflation etc.
- Bridge integrator unit 600 transmits the received sensory data to the master control unit (MCU) 525 via radio frequency interface 1624 , as also shown in FIG. 11 .
- MCU 525 transfers the data received from bridge integrator unit 600 to a third party interface via wireless transmission mode or MCU 525 may store the received data on a cloud server.
- the wireless transmission mode in accordance with the embodiment may be but not limited to cellular transmission mode.
- MCU 525 may transfer the received data to a remote location via cellular transmission, where a remote user may control the trailer 512 .
- the remote user may read and modify the data received by MCU 525 via a telematics user interface 1620 .
- the user interface may be alerts dashboard, which gives a complete fleet overview of any trailer failures. A map of each trailer's location is displayed. Further, a trailer dashboard gives a complete digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position.
- the remote user may also enter commands for the trailer 512 via the telematics user interface 1620 .
- FIG. 11 also shows a nose box assembly 1618 of the trailer communication system.
- the nose box assembly may include a wireless transmitting device with a communication protocol such as Zigbee or Bluetooth that will transmit signals to the master control unit 525 or other remote device such as a laptop, tablet, or cell phone.
- the Light failure detection system 540 may also act as the nosebox assembly 1618 .
- the nosebox assembly 1618 may receive power from tractor and may transmit the power to bridge integrator unit 600 , device control unit 1604 , trailer ECU 1602 via power line carrier 1610 .
- FIG. 12 represents a typical heavy duty trailer view detailing a driver side, curb side and rear side of the trailer 512 .
- the trailer nose box assembly 1618 may transmit the power to bridge integrator unit 600 , device control unit 1604 ; trailer ECU 1602 via power line carrier 1610 .
- bridge integrator unit 600 may receive data from a plurality of sensors installed on the tires 1622 of the trailer 512 via a radio frequency (RF) interface 1626 .
- the sensory data may indicate tire's conditions such as pressure, inflation etc.
- FIG. 13A schematically discloses various components of bridge integrator unit 600 .
- bridge integrator unit 600 comprises a microcontroller 814 schematically shown herein as U 1 , which has analog features for supporting extreme low-power devices.
- module 820 is an AW24MCHL-H2 transceiver among wireless modules 804 which has a 2.4-GHz Direct Sequence Spread Spectrum (DSSS) complete radio module which includes a Cypress radio integrated circuit CyFiTM CYRF7936, integrated antenna, and external components.
- DSSS Direct Sequence Spread Spectrum
- a module BM70BLES1FC2 818 offers Bluetooth Low Energy solution for embedded applications. It conforms to Bluetooth core specifications to enhance the throughput and security for the IoT applications.
- IEEE 802.15.4 is a technical standard which defines the operation of low-rate wireless personal area networks (LR-WPANs).
- U 12 shown in the FIG. 13A schematically refers to the BTLE module BM70BLES1FC2 818 .
- the Auxiliary connection module 808 comprises a Flash memory AT45DB081E 822 which is a 1.7V minimum, serial-interface sequential access suitable for a wide variety of digital voice, image, program code, and data storage applications. Flash—dual footprint comprising U 8 and U 15 shown in FIG. 13A are referred to herein as the Flash memory modules.
- U 5 shown in the FIG. 13A refers to TRIPSNET Module 834 which may be a MRF24J40MD/ME which is a 2.4 GHz IEEE Std. 802.15.4TM compliant, surface mount module with integrated crystal, internal voltage regulator, matching circuitry, Power Amplifier (PA), Low Noise Amplifier (LNA) with PCB Trace Antenna (MRF24J40MD) or 50 ⁇ external antenna connector (MRF24J40ME).
- U 13 refers to RS232 Transceiver 812 which may be used to convert logic level signals of the UART to and from the external signaling levels, which may be standardized voltage levels, current levels, or other signals.
- FIG. 13B schematically discloses various components of bridge integrator unit 600 in continuation to FIG. 13A .
- the power and battery sub-system 806 as shown in FIG. 6 , comprises a dis-connectable Input voltage sense sub-system 826 , a dis-connectable battery voltage sense sub-system 828 , a power management sub-system 830 and a voltage regulator 832 .
- U 2 refers to the dis-connectable Input voltage sense sub-system 826 .
- U 3 refers to the power management sub-system 830 and
- U 4 refers to a voltage regulator which may be used to output a 3V constant voltage.
- ICs 34 and 36 represent Debug port 824 which is used to simplify development and debugging operations.
- U 14 represents CAN interface 810 used to communicate sensory data from STEMCOM sensors to the microcontroller 814 .
- U 9 refers to 5V boost regulator 832 which is a DC to DC converter providing 5 volts greater than the source voltage.
- U 10 refers to CAN interface 810 which is used to communicate sensory data from STEMCOM sensors to the microcontroller 814 .
- U 16 with reference to FIG. 13B represents Micro-electromechanical systems (MEMS) accelerometer sensors used to measure displacement of the trailer 512 with a position-measuring interface circuit. The measured data is then converted into a digital electrical signal through an analog-to-digital converter (ADC) for digital processing.
- MEMS Micro-electromechanical systems
- the remote user interface may be modified overall, or widgets embedded in the user interface may be customized by customer and user preference.
- the user may read and modify the data received by MCU 525 via a telematics user interface 1620 .
- the user interface may be alerts at a dashboard, which gives a complete fleet overview of any trailer failures (See FIGS. 14-28 ).
- a map of each trailer's location may be displayed.
- a trailer dashboard gives an overall digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position, among other parameters.
- the remote user may also enter commands for the trailer 512 via the telematics user interface 1620 .
- Telematics system 500 also includes a user interface or alerts dashboard, which gives an overall fleet overview of any trailer failures.
- a map of each trailer's location is displayed with written details as to the condition.
- a trailer dashboard provides a digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position.
- FIGS. 14-28 illustrate examples of user interface screen shots of the telematics road ready system with a bridge integrator unit, and customized widgets dependent on the monitored parameter(s).
Abstract
Description
- The present application is directed to a telematics system including a bridge integrator unit for receiving and translating data transmissions from more than one type of data transmissions from sensory devices and transmitting the translated messages to a master control unit.
- Embodiments disclosed herein disclose a bridge integrator unit with ability to receive data transmissions from more than one type of data transmission from a sensory device or plurality of sensors or sensory devices. As referred to herein, the bridge integrator unit is a hub for various forms of data coming from sensory devices manufactured across the industry of transportation. The bridge integrator unit can communicate at least via radio frequency, an RS232 UART connection, and by a CAN bus connection to a CAN bus data system that is an industry standard North American data bus for trailers. Different embodiments of the bridge integrator unit encompass the different transmissions modes, among others configured as desired, that can come into the bridge integrator unit from different manufactures of sensory devices. Thus, the data can be translated to a master control unit (MCU). In particular, the data coming into the bridge integrator unit will work from messaging data, i.e. in a comma delimited format, that will be translated from the sensory devices protocol to a proprietary firmware language and then broadcast to the MCU using a radio frequency band of IEEE 802.15.4.
- The different means of communication from several devices can come in to the bridge integrator unit simultaneously. From this data that is transmitted into the bridge integrator unit, messages that are sent to the MCU are configured to be transmitted if and when a condition arises to notify a user of the equipment (e.g., a trailer). The bridge integrator unit may be powered from a trailer blue line power on the trailer when connected to a tractor, and may also resource its battery backup if not connected to the blue line power. For that reason, the bridge integrator unit can work independently from the tractor power, untethered from the tractor, and still broadcast data being received from the sensory devices. As such, the bridge integrator unit can be queried as to status and real-time data updates whether tethered with a tractor, or untethered, such as in a parking lot. This feature provides the end user the ability to access the trailer network (telematically) through the MCU and request status updates from the sensory devices remotely or with assistance from onsite human interaction.
-
FIG. 1 illustrates a telematics system including multiple sensing devices. -
FIG. 2 illustrates a master control unit and a wireless network around a trailer. -
FIGS. 3A and 3B are side open and top open views of a bridge integrator unit, respectively. -
FIGS. 4A-4D illustrate example circuit diagrams for use in a bridge integrator unit. -
FIG. 5A illustrates a three-dimensional representation of one embodiment of a bridge integrator unit. -
FIG. 5B illustrates an end view of the bridge integrator unit ofFIG. 5A . -
FIG. 5C is a cross-sectional view of the bridge integrator unit ofFIG. 5A . -
FIG. 5D illustrates a detailed three-dimensional representation of another embodiment of a bridge integrator unit. -
FIG. 5E is a cross-sectional view of the bridge integrator unit ofFIG. 5D FIG. 5F represents a layout of a printed circuit board (PCB) in one embodiment. -
FIG. 6 illustrates a detailed representation of various modules of a bridge integrator unit. -
FIG. 7 illustrates a schematic as to operation of an embodiment of a bridge integrator unit. -
FIG. 8 represents a schematic as to levels of the framework architecture integrated in an embodiment of firmware utilized for an embodiment of a bridge integrator unit. -
FIG. 9 represents a schematic as to an operational embodiment of a bridge integrator unit. -
FIGS. 10-12 illustrate a bridge integrator unit interconnected with various components of a system for communication in a trailer network. -
FIG. 13A is one embodiment of circuitry as utilized in a bridge integrator unit. -
FIG. 13B illustrates another embodiment of circuitry as utilized in a bridge integrator unit. -
FIGS. 14-28 illustrate examples of user interface screen shots of the telematics system with a widget displayed as to communication from a bridge integrator unit. - As shown in
FIG. 1 , a telematics system 500 (such as Road Ready™) sends, receives and stores data acquired from sensors attached to various systems and components of atrailer 512 and communicates the data to external display devices through radio frequency power line carrier or light communication, such as fiber optics. Sensors are configured to communicate with a master control unit (MCU) 525 of the telematics system, or other such external device. - The
telematics system 500 sends, receives and stores data acquired from a light failure detection system, as indicated at 540. Lightfailure detection system 540 is capable of multi-volt operation, such as 12V/24V, 10-30V, and 10-42V. Further, lightfailure detection system 540 includes LED and Incandescent Lamp capabilities (capable of determining current between LED/Incandescent), monitoring of anti-lock brake system (ABS) (On/Off), battery power for untethered operation to facilitate: asset location determination and/or asset remote diagnostic check. The lightfailure detection system 540 may be used in conjunction with multiple trailer configurations, including trailers of various sizes, dimensions, flat-beds, enclosed trailers, specifically pup trailers as defined by standards in transportation, or otherwise; and additional sensors including wireless (radio frequency (RF) or optical) or hardwired sensors may be included as well. - A nose box assembly 541 of the trailer communication system includes components of the light
failure detection system 540 includes a wireless transmitting device with a communication protocol such as Zigbee (i.e., an IEEE 802.15.4-based specification for a suite of high-level communication protocols used to create personal area networks with small, low-power digital radios) or Bluetooth (i.e., a wireless technology standard for exchanging data over short distances from fixed and mobile devices, and building personal area networks) that will transmit signals to the master control unit (MCU) 525 or other remote device such as a laptop, tablet, or cell phone. The transmitted data is acquired from the various sensors installed on thetrailer 520 or asset. In the embodiment shown, lightfailure detection system 540 is integrated with the nosebox assembly 541. - The
telematics system 500 uses a cellular based trailer intelligence system to provide transportation companies with real-time updates of a trailer's roadside status. Telematicssystem 500 includes interior and exterior sensors. The exterior sensors include at least lightfailure detection system 540, awarning sensor 532, such as an anti-lock braking system (ABS)monitoring sensor 532, and tire pressure/inflation sensor. The interior sensors include at least atemperature sensor 528, cargoload detection sensor 530, and a doorposition detection sensor 529. A dispatcher evaluates the trailer's condition remotely, by utilizing an online dashboard, or via a remote user interface, prior to dispatching a driver. If a failure occurs, the dashboard will instantly notify the dispatcher. If thetrailer 520 is experiencing a failure, it will highlight the failure in red (or any other indication of color or patterning) with a fault code. A wireless network is provided around the trailer using a solar-powered master control unit (MCU) 525 placed on the roof of the trailer. Wireless sensors are then placed inside and outside of the trailer. If a failure occurs, the telematics system will instantly detect it and report the failure to an alert dashboard at a remote or local user interface. - In one embodiment, the
ABS monitoring sensor 532 detects if the ABS light illuminates. When tethered to a tractor, the sensor reports the information to thesystem 500, and indicates the failure to the alert dashboard. Multiple tire pressure monitoring sensors detects if a specific tire pressure is too low or if the inflation system has been running too long. The information reported back to the alert dashboard depends on the type of tire system installed on the trailer. Real-time updates from the temperature sensor provides the customer with time and location stamped temperature history during transit. Real-time updates from the cargoload detection sensor 530, allow the customer to know exactly when a trailer is loaded or unloaded. The cargo detection zone is located directly under the sensor's location. Real-time updates are also provided from the door sensor to provide the customer with time and location stamped door positions. Custom alerts can be setup for unauthorized door openings or improper closing, to help detect theft and product contamination. -
FIG. 1 shows thetelematics system 500 for use with atruck trailer 512 having top 514, bottom 516,front 518, andside surfaces truck trailer 512.Truck trailer 512 may be a dry-van semi-trailer shipping container or a refrigerated shipping container. Master control unit (MCU) 525 attached to top 514 oftruck trailer 512. Wireless sensors, such as atemperature sensor 528, three-axis accelerometer door sensor or doorposition detection sensor 529, an ultrasonic load sensor or cargoload detection sensor 530 are positioned withintrailer 512 and are in wireless communication with a local wireless network master transceiver module of theMCU 525.Warning ABS sensor 532,bridge integrator unit 600, and lightfailure detection system 540 are all located external to thetrailer 512. - As shown in
FIG. 2 ,MCU 525 includessolar cells 550 and anelectronics module 552, which are integrated into a one-piece unit as described below.MCU 525 is comprised of at least about six main parts: a cellular module, a GPS, an RF wireless xBee module, a microcontroller, a rechargeable lithium-ion battery and a military grade flexible solar film. Charging circuitry allowsMCU 525 to use on average 3% of the battery while charging as much as 15% per hour. In the absence of sunlight,MCU 525 continues to report for 60 days due to specialized back-off controls. The solar panel continues to charge even in low sunlight conditions and heavy cloud coverage. Thesolar cells 550 converts light energy, such as from the sun, into power for operation of theelectronics module 552. The local wireless network master transceiver module ofMCU 525 comprises the master node in a local wireless network with the wireless sensors. An exemplary wireless network uses the hardware specified by IEEE standard 802.15.4 coupled with a proprietary communication protocol. The local wireless network allows sensor data from wireless sensors in the network to be gathered byMCU 525 and transmitted using the cellular data transceiver module ofMCU 525. - Examples of the
MCU 525 are :005-197-502—Verizon (CDMA) with internal Zigbee—allows use of additional sensors, such as temp, cargo, door, and fuel sensors; 005-197-501—AT&T (GSM) with internal Zigbee—allows use of additional sensors, such as temp, cargo, door, and fuel sensors; 005-198-502—Verizon (CDMA) without internal Zigbee—tracking only, no additional sensors; 005-198-501—AT&T (GSM) without internal Zigbee—tracking only, no additional sensors. - As illustrated in
FIGS. 3A and 3B , abridge integrator unit 600 is shown in side open and top open views, respectively.Bridge integrator unit 600 includes aplastic enclosure 553, with acover 554 and sealinginterface 555 for internal power and ground wires. The bridge integrator unit uses a direct sequence spread spectrum (DSSS) radio module to gather RF signal data from products installed ontrailer 512. - In one embodiment, the radio communications are used with STEMCO RF signal data, for exemplary purposes and not limitation, from STEMCO products, such as an automatic tire inflation system, a mileage sensor, or a single or dual tire pressure monitoring sensor.
Bridge integrator unit 600 may be referred to as a “smart bridge”, or hub, due to its functionality of bridging (and/or translating) communications of customer products, (e.g., here, STEMCO products) with communications to theMCU 525. The bridge integrator unit connects directly to the customer device communications, for example, RS232 or CAN bus, or through a WiFi connection via RF communications, and serves as a hub to translate the communications to a remote server. To that extent, the bridge integrator unit comprises hardware, software, and firmware. -
Bridge integrator unit 600 includes circuitry, as shown oncircuit board 551, that translates a signal from one communication signal into another messaging format. For example, an RF signal from the sensors may be translated into a secondary messaging format. Once the signal is converted to the secondary format, the messages are delivered to MCU 525 through a ZigBee network. The low power communication protocol ZigBee is power efficient and has additional capability to extend the network.Bridge integrator unit 600 may be powered by a blue circuit wire and/or a rechargeable lithium-ion battery. -
FIGS. 4A-4D are examples of detailed circuitry forbridge integrator unit 600.FIG. 4A shows U2, which is one diode circuit to reduce losses. The remainder of the circuit provides battery charge current.FIG. 4B shows U1, which is an OP AMP used to buffer/measure the voltage at the battery as it is charging. U4 provides regulated 3V power for the system.FIG. 4C includes main controller (U6), and IEEE 802.15.4 transceiver (U5) for connection to the Zigbee network and communication with MCU.FIG. 4D includes a temperature sensor to monitor ambient temperature (U10), an extra memory for controller (U8), a 2.4 GHz wireless modem for non-Zigbee communication (U11), and an accelerometer (U9) to detect when the vehicle is in motion. - Embodiments of a bridge integrator unit, or bridge integrator unit, are described as follows in
FIGS. 5A-5F .FIG. 5A illustrates a three dimensional perspective view of abridge integrator unit 600.Bridge integrator unit 600 is configured to be coupled to a surface of a trailer or other mounting structure and may have various shapes and structures depending upon the surface of the trailer. The embodiments detailed herein represent, but are not limited to,bridge integrator unit 600 having a stepped mount sealed housing (FIGS. 5A-5C ) and a flat mount sealed housing (5D-5E).FIGS. 5A, 5B, and 5C illustrate three-dimensional, side and cross-section views ofbridge integrator unit 600 having a stepped mount sealedhousing 602 configured to be coupled to a stepped or un-stepped surface of a trailer.Housing 602 includes atop surface 605, a bottom surface 606, first and second ends, 607 and 608, and first and second sides, 610 and 611. Each of first and second sides, 610 and 611, and a laterally extending steppedflange bridge integrator unit 600 to a surface of a trailer or to a mounting structure.FIG. 5B is an end view ofbridge integrator unit 600.First end 607 includes openings (not shown) through which overmoldedconnectors housing 602 may be end plates fastened tohousing 602 with a plurality of fasteners, such as screws 620. Other configurations of housings, however, may be permitted to serve similar design and functionality. -
Bridge integrator unit 600 may either receive power from an external source, such as a blue line power of a trailer, or abackup battery 623, such as a rechargeable lithium-ion battery, as shown inFIG. 5C . Further, the lithium-ion battery may be used to deliver constant power to thebridge integrator unit 600 via a blue circuit wire. The embodiments described herein are not limited to lithium-ion battery for delivering power to bridgeintegrator unit 600. Other types of batteries for example, aluminum-ion battery, vanadium redox battery, zinc-bromine battery zinc-cerium battery, lead-acid battery, thin film lithium-ion battery, magnesium-ion battery molten salt battery, nickel-cadmium battery, etc. may also be used to deliver power to bridgeintegrator unit 600. - In addition, a light emitting
diode indicator light 622 is provided to indicate the status ofbridge integrator unit 600. In one embodiment, an LED typically ranging from 520 nm<λ<550 nm may be used to indicate status ofbridge integrator unit 600. For example,indicator light 622 may emit green light whenbridge integrator unit 600 is in an active state and no light whenbridge integrator unit 600 is turned off. -
FIG. 5C further illustrateshousing 602 havingsupport ribs 625 to reinforce the strength ofhousing 602 and asupport element 627 for securingbattery 623. Aslot 630 is also provided for supporting the circuit board 650 (SeeFIG. 5F ) withinhousing 602. -
FIGS. 5D and 5E illustrate detailed three-dimensional and cross-sectional views ofbridge integrator unit 600 with a flat mount sealedhousing 602′ which may be coupled to flat surface of a trailer.Housing 602′ includes atop surface 605, a bottom surface 606, first and second ends, 607 and 608, and first and second sides, 610 and 611. Each of first and second sides. 610 and 611, has a laterally extending flat flange extending therefrom at 613′ and 614′. A plurality of apertures, each indicated at 615, are formed in first and second laterally extending flat flanges, 613′ and 614′, for receiving fasteners for mountingbridge integrator unit 600 to a flat surface of a trailer or mounting structure. Each of the remaining components ofbridge integrator unit 600 shown inFIGS. 5D-5E correspond to those discussed forFIGS. 5A-5C .FIG. 5F is a detailed view of anexemplary circuit board 650 for use withbridge integrator unit 600. - In accordance with above embodiments,
bridge integrator unit 600 may comprise various modules.FIG. 6 illustrates a detailed representation ofbridge integrator unit 600 comprising various modules.Bridge integrator unit 600 comprises a power/battery module 806, awired interface 802, a microcontroller 814,wireless modules 804, andauxiliary connections 808. In addition, thebridge integrator unit 600 also comprises various interfaces such as serial peripheral interface (SPI), universal asynchronous receiver-transmitter (UART) and analog-digital conversion (ADC) interfaces. -
Bridge integrator unit 600 may utilize the modules for receiving data from one or more sensory devices or a plurality of sensors, and further send the data to a remote user interface. In an exemplary embodiment, the sensory devices installed on thetrailer 512 may comprise various types of sensors which are used to sense and/or record values of multiple parameters. The sensors may be wired or wireless sensors; as depicted, for representation and not limitation, the sensors are wireless. Such sensors may include: atemperature sensor 528, three-axis accelerometer door sensor or doorposition detection sensor 529, an ultrasonic load sensor or cargoload detection sensor 530 etc. The sensors may be positioned on surface of thetrailer 512 and may communicate either via wireless interface or via wired interface. The sensors may further send or receive data from a local wireless network master transceiver module of theMCU 525. TheMCU 525 may also integrate additional sensors to include customer requested sensory data, as desired, and not limited to, including temperature, tire pressure, trailer weight, cargo, door and fuel sensors, among others for monitoring various parameters of thetrailer 512. - In addition, the
MCU 525 may also transmit a plurality of signals to thetrailer 512 regarding certain conditions or alerts sensed by thewarning sensor 532. Thesensor 532 generates a plurality of messages such as, P-power up, E-alert, S-Status, R-resolved and Y-acknowledgment which may be transmitted to thetrailer 512 from theMCU 525. - In one embodiment, sensory data may be transmitted to a bridge integrator unit, otherwise disclosed as a
bridge integrator unit 600 that is capable of intake of a multitude of network communications, specifically radiofrequency identification (RFID), a controller area network (CAN bus), universal (synchronous) asynchronous receiver/transmitter (UART), or as specifically designed; the input can then be integrated with the communication architecture to provide an output for communications to a user. The CAN bus standard design allows microcontrollers and devices to communicate with each other in applications without a host computer. Also, the UART is responsible for sending and receiving a sequence of bits, the output of these UART bits usually represented by logic level voltages. These bits can be RS-232, RS-422. RS-485, or perhaps some proprietary specification. Here, the use of RS-232 is referenced, as integrated in thebridge integrator unit 600, though the system remains open to the potential for a variety of communications and protocols to be input and integrated at the bridge integrator unit. Messages are sent to the MCU if and when a condition change arises at one of the monitoring sensors on thetrailer 512, or when data declines below or exceeds a defined threshold value. An update may also be sent to an operator of thetrailer 512, or to a remote interface. In addition, the directionality of messaging can be uni-directional, sending to the MCU; or the directionality may be bi-directional whereby the bridge integrator unit can be queried by a remote device, input with data from an external source, or otherwise automatically queried for data at intervals or set timepoints. - With further reference to
FIG. 6 , the sensory devices may communicate with thebridge integrator unit 600 through awired interface 802, which may include aCAN interface 810, aRS232 interface 812, or as selected for directing wiring. In one embodiment, CAN interface 810 is a small-footprint external CAN flexible data-rate (CAN FD) controller that communicates with microprocessor 814 via a serial peripheral interface bus (SPI) 815. The serial peripheral interface (SPI) is a synchronous serial communication interface specifically used for short distance communication, typically embedded in the system(s). CAN interface 810 typically supports two types of formats for transmission and reception of CAN frames, classical format (CAN 2.0B) or CAN flexible data Rate (CAN FD) format as specified in ISO11898-1:2015. Further, CAN interface 810 has an arbitration bit rate up to 1 Mbps and a data bitrate of up to 8 Mbps. Bidirectional communication withbridge integrator unit 600 is achieved by configuration of 31 FIFOs ofCAN interface 810. Typically, CAN interface 810 employs a VDD power supply of 2.7V-5.5V for its operation. - A plurality of sensors may communicate with
bridge integrator unit 600 via theRS232 interface 812. Data related to thetrailer 512 may then be sent to microprocessor 814 via a UART (universal asynchronous receiver-transmitter) 816. The UART may accept data in byte format and may transmit the data in bit format in a sequential fashion, or as desired depending on communication protocols. TheRS232 interface 812 may be used to convert logic level signals of the UART to and from the external signaling levels, which may be standardized voltage levels, current levels, or other signals. The received sensor data may be sent byRS232 interface 812 as a time-series of bits. Further, the interface may operate in a duplex manner, supporting concurrent data flow in both directions from thebridge integrator unit 600 and may support both synchronous and asynchronous data transmission. - In addition, the serial peripheral interface bus (SPI) is a synchronous serial communication interface specifically used for short distance communication, typically embedded in the system(s). SPI devices communicate using master-slave architecture with a single master device or with one or more slave devices. Multiple slave devices are supported through selection with individual slave select (SS) lines.
- As also shown in
FIG. 6 ,bridge integrator unit 600 includes a microprocessor 814, which is a 24-bit processor, e.g. PIC24FJ microcontroller with integrated peripherals for segmented or graphical displays, USB-OTG, motor control and capacitive touch implementation. Microprocessor 814 may also have intelligent analog integration, and include 10, 12, 16, 20 bit processors, -bit analog-to-digital converters (ADCs), digital-to-analog converters (DACs), and operational amplifiers in the smallest form factors available. Microprocessor 814 receives data from one or more ofwired interface 802,wireless modules 804, andauxiliary connections 808. Data may then be sent toMCU 525. Thus, thebridge integrator unit 600 may be referred to as a hub to intake data coming from sensory devices that belong to different manufacturers and translate that data to a uniform language for communication with a master control unit that updates an operator or user at a user interface. Sensory devices having multiple communication channels, such as RS232, CAN, and UART may transmit and receive messages in a comma delimited format, or as otherwise designed, to and frombridge integrator unit 600. - In the embodiment shown in
FIG. 6 ,wireless modules 804 are adapted to transmit and receive data betweenbridge integrator unit 600 andMCU 525.Wireless modules 804 comprise, for example, aBluetooth module 818, aradiofrequency module 820 and internalwireless protocol module 834.Bluetooth module 818 transmits data received wirelessly from the sensory devices to microcontroller 814 viaUART transmitter 819.Radiofrequency module 820 and internalwireless protocol module 834 transmit data received from the wireless sensory devices to microcontroller 814 via one or more SPIs 821 and 822, respectively. -
Internal wireless module 834 also can transmit data directly toMCU 525. Sensory data from multiple communication protocols is translated at theinternal wireless module 834 to a firmware language that communicates directly with theMCU 525, and using a radio frequency band of IEEE 802.15.4 or other wireless communication. Themodule 834 may be a 2.4 GHz IEEE Std. 802.15.4 compliant, surface mount module with integrated crystal, internal voltage regulator, matching circuitry, power amplifier (PA), low noise amplifier (LNA) with PCB trace antenna (MRF24J40MD) or 50Ω external antenna connector (MRF24J40ME), or other compatible device comparable in the state of the art. Themodule 834 is configured to operate in a non-licensed 2.4 GHz frequency band and may minimize use of extensive RF and antenna design. In one embodiment, themodule 834 is based on microchip technology of MRF24J40 2.4 GHz IEEE 802.15.4 RF transceiver IC. After the sensory data is converted into a common protocol, the data is transmitted toMCU 525. The MCU controls a local wireless network master transceiver module to periodically obtain sensor data from one or more wireless sensors directly, or through a bridge integrator unit that translates the message to a readable form, and further controls access to the data via a cellular data transceiver module to transmit location and sensor data oftrailer 512 to a remote user interface. The bridge integrator unit system ofFIG. 6 utilizes wiredinterfaces wireless RF module 820 to pull information from wireless sensors on a trailer (or other external tracked asset) into the processor that is part of microcontroller 814. The processor translates the message received from those communication avenues into a secondary communication protocol to provide messaging and communication feedback to an operator or user at a user interface. The secondary communication protocol can be queried directly from the user interface, or may be displayed at the user interface via the messaging through the MCU of the trailer. Either way, direct or indirect access through the MCU, the data conveyed via the bridge integrator unit is consistent with ongoing user communications and displayed in real-time. The bridge integrator unit may be accessed remotely via the user interface, or through the MCU, in real-time. -
Bluetooth LE module 818, as shown inFIG. 6 , is a low-energy Bluetooth module, which supports UART, I2C, and SPI interfaces.Bluetooth module 818 works on an ISM Band from 2.402 GHz to 2.480 GHz over 0-39 channels and typically has a reception sensitivity of −90 dBm. In addition,Bluetooth module 818 may provide operate in low energy conditions for embedded applications. It conforms to Bluetooth core specification version 4.2 to enhance the throughput and security for IoT applications.Bluetooth module 818 may also support bacon technology to enhance user experience for the IoT applications and enables users to control data in the cloud and receive data without opening the application through a smart phone. Bluetooth stack is integrated and is available in different form factor to optimize the space, cost, and RF performance. For portable and wearable applications, it provides power-optimized design to minimize the current consumption to extend the battery life. - As further shown in
FIG. 6 .RF module 820 may be a AW24MCHL-H2 transceiver inwireless modules 804 which has a 2.4-GHz direct sequence spread spectrum (DSSS) complete radio module and includes Cypress radio integrated circuit CyFi™ CYRF7936, integrated antenna, and various external components. The wireless RF module offers a radio module solution for integration into existing or new 2.4-GHz products. Data from theRF module 820, and associated sensing units, is sent to thebridge integrator unit 600 via the SPI bus for data transmission/reception toMCU 525. -
Bridge integrator unit 600 also includesauxiliary connection module 808 with aflash memory 823 and adebug port 824. Embodiments herein may incorporate various auxiliary connections as needed for storage and retrieval of information, security systems, or otherwise. To allow for simple in-system re-programming,flash memory 822 may utilize lower voltages for programming.Memory 822 may operate from a single 1.7V to 3.6V power supply for the erase and program and read operations.Flash memory 822 is enabled through the chip select pin (CS) and accessed via a 3-wire interface consisting of the serial input (SI), serial output (SO), and the serial clock (SCK). It is compatible withSPI 825 for communication with microcontroller 814.Debug port 824 is used to simplify development and debugging, but its functions are not limited and can be used for multiple functions by a person skilled in the art. Data to/from microprocessor 814 is transmitted from/to thedebug port 824 via anSPI interface 826.Debug port 824 is compatible with low end communication protocols such as I2C (e.g., for ‘Inter-Integrated Circuit’, protocol) and SPI (e.g., for ‘Serial Peripheral Interface’), among others. Both protocols are well-suited for communications between integrated circuits, and for slow communication with on-board peripherals. -
Bridge integrator unit 600 further includes a power andbattery sub-system 806, which includes a disconnectable inputvoltage sense sub-system 827, a disconnectable batteryvoltage sense sub-system 828, apower management sub-system 830 and aboost regulator 832. Power supplies are often designed to operate in 120 VAC and 220 VAC input voltage range. By using an automatic disconnectable input voltage-sensing switch 827, as shown inFIG. 6 , the input voltage can be sensed so that the power supply can automatically switch between two or more input ranges. An analog-to-digital converter (ADC_1) 834 converts an analog signal from the power supply into a digital signal to be sent to microcontroller 814. In addition, power andbattery sub-system 806 also includes a disconnectable batteryvoltage sense unit 828 for sensing a battery's voltage. The sensed voltage may be translated and sent to microcontroller 814 via an analog-to-digital converter (ADC_2) 836, which converts an analog signal from the power supply into a digital signal to be sent to microcontroller 814. Further, the battery back-up system described here allows for a trailer to be monitored via the bridge integrator unit when tethered with direct battery connection, and for communication with the bridge integrator unit when the trailer is untethered from a tractor. Power andbattery sub-system 806, as shown inFIG. 6 , also includespower management sub-system 830 for regulating the trailer's input power supply, which may be frominput trailer voltage 835, voltage from abattery 836, orsystem voltage 838. Under normal operation, the trailer's input voltage is about 12 volts, but may be modified as appropriate or desired to provide power efficiency and maintenance. Power andbattery sub-system 806 also includes reverse connection protection and a lithium ion battery, which may have an input voltage of 3.6 volts under normal operation. Additionally, aboost regulator 832 is provided which may receive power from a CAN transceiver (e.g., active receiver antennae) 840, or any suitable DC sources, such as batteries, solar panels, rectifiers and DC generators. In the present embodiment, theboost regulator 832 is a DC to DC converter providing 5 volts greater than the source voltage.Boost regulator 832 may also be referred as a step-up converter since it “steps up” the source voltage. - With reference to
FIG. 7 , thesystem 1200 illustrates a process at 1200(A) to start-up 1202, bootload initialize 1204, and upgrade 1206 prior to any launch of interrupt service routines (ISRs) 1218 for communications through theapplication initialization 1214, and/or execution of associatedtasks 1222 via the process at 1200(B). - In
FIG. 7 , a power up or reset signal 1202 is generated when power is applied to bridgeintegrator unit 600. At step 1204, the boot loader present in the framework 1408 (SeeFIG. 8 ) is initialized and loads system software for the bridge integrator unit, orbridge integrator unit 600. The logic proceeds to inquire at 1206 as to any firmware or upgrades for the system. If additional or revised firmware is available, a copy of the firmware is copied to a microchip controller at 1208. Here, the controller is represented as a PIC controller ROM. This is comparable to a software update followed by an upload and/or restart of the system. If not updated firmware is available, the integration application proceeds to start at 1212. The application is initialized at 1214, followed by a step of turning off anyunused interfaces 1216. For exemplary purposes, and not limitation, if not using a UART connection, and a CAN bus instead, then the UART can be switched off. The ISRs are launched 1218, generating a dispatch message atstep 1220, through aprotocol 1404, as encoded at the dictionary or hexadecimal coding level, protocol of which relates to information as to the message designated by the plurality of sensing devices. The messaging protocol here, as encoded by the hexadecimal (or other coding) library, designates thespecific tasks 1222 to be monitored. The firmware, as described, indicates when an issue arises as to the specific sensing device parameters, and data that falls outside a range or threshold values so as to indicate the issue. - In reference to the launching of interrupt
service routines 1218, the system may handle various types of interrupt service routines (ISRs) such as Jiffy Tick 1224 (i.e., updating time variations 1226) or RTC 1228 (i.e., real-time clock given 1minute periods 1230, though any designated timing may be utilized) embedded in theframework 1408. Aninterface handler 1232 of thehardware abstraction layer 1402 has various communication channels 1234 including, but not limited to, RF (802.15.4), BTLE, CAN bus, CyFi, RS232, among others. Theblue line 1236 is used to choose an interrupt from a plurality of interrupts and querying as to state changes 1238 having 30 second debounce periods. Here, the status is queried every 30 seconds. The system continues to query here unless there is no state change. The logic queries as to whether the trailer is tethered 1240. If yes, then the blue line is tethered 1242, and the battery connection to the bridge integrator unit is directly connected to the power supplied by the tractor to which the trailer is tethered. If not tethered, the blue line is untethered 1244, and thus the bridge integrator unit proceeds to utilize its battery backup. - Moreover, in logic flow level 1218(C), an
interface handler 1232 enables communication between sensors andbridge integrator unit 600 viawired RS232 interface 812 and CAN interface 810, as also previously shown inFIG. 6 . The interface handler operates in the hardware abstraction layer (HAL) 1402 ofFIG. 8 . In addition, theinterface handler 1232 enables communication betweenbridge integrator unit 600 andMCU 525 via a secondary language protocol, (e.g.,TRiPST Module 834,Bluetooth LE module 818 andRF module 820 as also previously shown inFIG. 6 . - Still with reference to logic flow level 1218(C) in
FIG. 7 , theinterface handler 1232 also monitors the tethered/un-tethered state of the blue power line. Theinterface handler 1232 also allows a choice of an interface from a plurality of available interfaces. The system may choose a service from 802.15.4, BTLE, CAN Bus, CyFi or RS232 interfaces. - Again referring to flow diagram 1200(B) of
FIG. 7 , after a dispatch message is generated, a plurality oftasks 1222 may be performed by plurality offirmware logic levels 1400. Flow level chart 1222(A) illustrates third party protocols atstep 1246, communicating with the remote user interface 255. At step 1248, parameters are customized according to customer demand and sensing units utilized, capturing real-time data from the sensors when queried, such as lightfailure detection system 540, warningsensor 532, anti-lock braking system (ABS)monitoring sensor 532, tire pressure/inflation sensor,temperature sensor 528, cargoload detection sensor 530, and a doorposition detection sensor 529. As designated here, the bridge integrator unit queries sensors every 2.5 seconds, or as coded in the system. The data is translated at the bridge integrator unit, and if changed from a previous state or outside a range or threshold, pushes the data to the MCU. The remaining data, static data of which remains unchanged or unused for a certain time period, is removed and conserves storage space. - Further flow diagram 1222(B) illustrates a process to determine if the blue power line of a tractor-trailer is connected to a
bridge integrator unit 600. Ifbridge integrator unit 600 is in power saving mode as shown instep 1250, the blue power line is monitored atstep 1252 as to whether the firmware is connected to the blue line. Thesystem 1200 checks to see if tasks are in process at 1254; if no task in process, then bridge integrator unit goes intosleep mode 1256 for a time designated, here at least about 2 minutes. - Further, logic level flow diagram 1222(F) illustrates the downloading of updated firmware at
step 1292. A message is received by the bridge integrator unit atstep 1294. If the message is not received, the query returns to the firmware receivemessage 1294. If the message is appropriately received 1296, the check sum of the received data is calculated to determine anyerroneous data 1298. If the check sum is okay, the system prepares forbootload 1300, and the system resets 1304. If the check sum is not okay, the firmware update is discarded 1302. - Within a protocol agnostic database (PAD) 1404 of
FIG. 8 , thetasks 1222 of the bridge integrator unit firmware logic simultaneously monitors data queried by the MCU. Here, the PAD inquires whether additional interface data is present 1260, whether a data request has been sent 1262, and whether data has expired 1264. If affirmative for any ofsteps purge 1270 the data. Note that after the date has been retrieved, it is purged. Followingstorage 1260 and purging 1270, the dictionary is updated. The manage dictionary functionality of the protocol agnostic database intakes the messaging from RF, CAN bus, and RS232 transmissions and information corresponding to specified sensors within the assigned monitored parameters. - For exemplary purposes, and not limitation, one customer may request tire pressure monitoring. While not having direct access to proprietary protocol implemented in a customer tire pressure sensor or other sensor communications, the smart bridge integrator can interconnect with a device control unit of the particular customer to pull raw data into a user-based system to monitor and access that data via a common interface. The bridge integrator unit facilitates this communication, and rather has the capability to pull all streams of data to translate into secondary messaging to the user, customer, or fleet operations. For exemplary purposes, and not limitation, by integrating with the customer's particular sensors that monitor tire pressure within each tire, the bridge integrator unit intakes the data via a CAN bus communication line, pinging the sensors at regular intervals, such as every 2.5 seconds. The messages are translated, at the bridge integrator unit, for example, encoded into hexadecimal format at the dictionary. If the data is consistent with specifications provided, the system purges the data. If the data changes, to indicate an issue, the bridge integrator unit relays the information in a uniform proprietary language, or secondary language, at a particular RF frequency to a master control unit (MCU). The MCU transmits the information to a designated user interface.
- As shown in the embodiment of
FIG. 7 , logic level flow diagram 1222(G) illustrates the process of TripsNetsecondary messaging 1306 initializing followed by queries to send amessage 1308, acknowledge a sentmessage 1310, and query whether a message was received 1312. Atstep 1308, if a message is generated, a communication to theMCU 525 is transmitted via TripsNet atstep 1314. If the sent message is not acknowledged by the TripsNet protocol in the framework of theMCU 525, the message shall be sent again atstep 1316. If the message is received byMCU 525 atstep 1312, the message is stored 1318. - Continuing with reference to
FIG. 7 , logic flow chart 1222(D) illustrates a process of transmitting a dispatch message to the third parties. At step 1274, the scheduler monitors the operation of the dispatch message. Once the scheduler detects that time has exceeded a specifiedtime 1276, here 24 hours, the dispatch message is sent 1278. - Further, logic level flow chart 1222(E) monitors the tethered and un-tethered state of the blue power line with the bridge integrator unit. Here, the blue power line is associated with the tractor; and the firmware associated with the bridge integrator unit is in connection with the trailer unit. The sensor sample time is being monitored at
step 1280. Atstep 1282, the blue power line status is monitored. If the blue power line is tethered to the bridge integrator unit, the sensor data is sampled after every 60 seconds at 1284. If the blue power line is untethered from the bridge integrator unit, the system queries whether the bridge integrator unit was untethered for a duration of time at 1286; here, for example, the query asks if the bridge integrator unit was untethered for more than a week. If untethered more than the specified duration of time, sampling of the bridge integrator unit is queried inincrements 1290. Here, for example, sampling would then occur every 1 minute. If the blue line is not untethered for more than a week, sampling occurs for another specified period oftime 1288, here selected at about every 5 minutes. Note that the tethering of the bridge integrator unit references whether a trailer is connected to the tractor; when untethered, the trailer (and thus, associated bridge integrator unit) is detached, or untethered from the trailer. This allows a user or operator to determine how long a trailer has sat at a delivery, in a parking lot, or at another designated or unknown location. - Further, logic level flow diagram 1222(H) illustrates the process of determining the connection state of the blue power line (BL). The bridge integrator unit monitors the tethered or
untethered state 1320 of the blue power line. In the next step, a connection/disconnection message 1322 is sent in order to check whether the status of the blue power line has changed 1324. If the state has changed at 1324, the system queries whether the blue power line is tethered/connected 1326. If the blue power line is tethered atstep 1326, aconnection message 1328 is sent. If the blue power line is untethered atstep 1326, adisconnect message 1330 is sent. - With reference to
FIG. 8 , a bridgeintegrator unit system 1400 illustrates a broad view of firmware logic levels offramework 1408 which provide controls for abridge integrator unit 600, including specific hardware and software/firmware.Framework 1408 may store sensor data. The sensor data may come from lightfailure detection system 540, warningsensor 532, anti-lock braking system (ABS) monitoring sensor, tire pressure/inflation sensor,temperature sensor 528, cargoload detection sensor 530, a doorposition detection sensor 529, among other parameter sensing devices and sensors. In an embodiment, thesystem 1400 an operating environment and architecture for bridge integrator unit and also provides additional levels of programming and integrated hardware and/or software to perform control, monitoring and manipulation of data functions. Thesystem 1400 may be held in a non-volatile memory device which may beflash memory 822 as previously shown inFIG. 6 , or storage within the bridge integrator unit. - Here, as shown in the
system 1400 as integrated with the bridge integrator unit, thehardware abstraction layer 1402 and protocolagnostic database 1404, along withthird party protocols 1406 are built on top offramework 1408. As described prior, the managedictionary 1272 allows communication and translation of data that is received from either RF. CAN bus, and/or RS232. Various other communications may be identified and integrated at the bridge integrator unit also. -
FIG. 9 represents an example of flowchart logic as to abridge integrator unit 1500 for a tire pressure sensing system. Whether queried by the MCU of the trailer system at regular intervals or voluntarily and instantaneously from a remote interface, thesystem 1500 is capable of setting up communications 1500(A) with a third party device and third party communications network. The system further integrates the third party communications 1500(B) for further translation and status update communications to a user interface. The flow diagram 1500(A) establishes whetherbridge integrator unit 600 is configured for pressure check (CPC) or not. Oncebridge integrator unit 600 is configured for pressure check (CPC), the logic flow level diagram 1500(B) initiates CPC protocol. - At
Step 1504, where a device control unit 1604 (will be detailed in the below embodiments) generates a request to obtain CAN driver information. Further, the flow level diagram proceeds to Step 1506, which is a conditional statement to check whetherbridge integrator unit 600 is configured for pressure check (CPC) or not. In the case where thebridge integrator unit 600 is configured for pressure check (CPC), the logic level flow proceeds to step 1508. Whenbridge integrator unit 600 is not configured for pressure check (CPC), the logic level flow waits to configurebridge integrator unit 600 for pressure check (CPC). - The system then sets up the CAN interface for
PGN 1508 which is a deeper level firmware for data storage. After setting up the CAN interface for PGN, the logic flow level proceeds to store 1510 the incoming PGN data in the database. Thestep 1510 works in a loop because the PGN data is not stored in the database for a long duration of time. The data stored in the database is discarded once the vehicle shuts off, or once the signal or issue is resolved. The system is designed to save memory and storage space. As mentioned prior, the data is stored in the database library in hexadecimal format, or coding as desired. - Once
bridge integrator unit 600 is configured for pressure check (CPC), the logic flow level diagram 1500(B) proceeds via theCPC protocol handler 1512. The system protocol checks to see as to whether the CPC data is stored 1514 in the database or not. If the CPC data is not stored in the database, the logic flow level waits until the CPC data is stored 1514 in database. Once the CPC data is stored in the database, the logic flow level diagram proceeds to step 1516. - The
step 1516 is a conditional statement which checks whether the pressure recorded by tire pressure monitoring system (TPMS) is out-of-bounds or not. If the recorded pressure is out-of-bounds, the logic flow level proceeds to check whether or not an alert has been sent 1518; otherwise the logic flow level proceeds to step 1524. If the alert has not been sent at 1518, then asecondary messaging alert 1522 via a TripsNet protocol is sent to the MCU. If the alert is already sent atstep 1518, the logic proceeds to check whether the alert timer has expired atstep 1520. If yes, then asecondary messaging alert 1522 via a TripsNet protocol is sent to the MCU. If the alert has not expired, the logic proceeds to check the next condition, here temperature at 1528. - At
step 1524, a condition is checked whether the system was previously in alert or not. If the system was previously in the alert state, the logic proceeds to resolve the secondary messaging command atstep 1526, here, the TripsNet resolve. Otherwise, the logic flow proceeds to step 1528. Note that the TripsNet resolve command returns the system back to normal after correcting the pressure monitored by the TPMS. - At
step 1528, a temperature check is performed for the measured tire conditions. Thestep 1528 checks whether temperature of the TPMS is out-of-bounds or not. If the recorded pressure is out-of-bounds, the logic flow level proceeds to step 1530 where an already sent alert is monitored, otherwise the logic flow level proceeds to step 1536. Thestep 1536 checks whether the system is previously in alert or not. In case the system is in the alert state, the logic flow level proceeds to step 1538 where a TripsNet resolve command is issued, otherwise the flow proceeds to step 1540. Tripsnet resolve command returns the system back to normal after correcting the pressure monitored by the TPMS. - At
step 1530, the logic flow level checks if the system has already sent an alert or not. If the alert is already sent, the logic proceeds to step 1532; otherwise, if the alert is not sent, the logic flow proceeds to step 1600, where the system generates a TripsNet alert. Atstep 1532, is the system checks if the alert timer has expired or not. If the alert timer has expired, the logic proceeds to step 1600, where the system generates a TripsNet alert; otherwise the logic flow level proceeds to step 1540. - At
step 1540 of the logic), various other parameters related to the monitored TPMS are checked, as designated and designed by user, operator, and/or customer. The parameters may be low battery, wrong orientation, loose connections, or other monitoring parameters or controls. Where it is determined that something is wrong with the checked parameters, the logic proceeds to step 1542 as to whether or not a message was sent. If the checked parameters are within required limits, the logic flow level proceeds to inquire whether the status period is over at step 1546. - At
step 1542, the system checks if message had already been sent or not regarding parameters within or exceeding ranges and thresholds. In case the message had not been sent, the logic flow level proceeds to step 1544 where a TripsNet message is sent; otherwise, the logic flow level proceeds to step 1546 to inquire whether the status period is over. - The issued TripsNet message at
step 1544 is sent in order to return the trailer to the authorized dealer, as may be appropriate where sensor controls are not within a control or modification protocol via interfaces such as the bridge integrator unit or MCU. At step 1546, the system checks if the status period is over or not by noticing a time out period. In case the status period is over, the logic proceeds to send aTripsNet status message 1548 as to that terminated status period. Otherwise, the logic returns to step 1514 to check if the CPC data is stored in database or not. This CPC data protocol is one embodiment that is demonstrated for exemplary purposes and not limitation. Similar protocols may be designed and implemented to adapt to customized management and monitoring of various systems capable of communicating with the bridge integrator unit. -
FIG. 10 illustratesbridge integrator unit 600 and its communication with various components of the telematics system, such as adevice control unit 1604 and atrailer ECU 1602. The ECU is the electronic control thatbridge integrator unit 600 receives a 12V power viapower line 1605 from a power line carrier (PLC) 1610. Along with thePLC 1610,bridge integrator unit 600 also comprises abattery 620 for delivering power tomicroprocessor 1606.Bridge integrator unit 600 also includes SPI orUART interface 1614 for connecting CANBUS in order to transfer sensory data betweenmicroprocessor 1606 anddevice control unit 1604 via a wired interface SPI or UART. - The
device control unit 1604 may receive sensory data from a plurality of sensors installed on thetrailer 512. In addition, thebridge integrator unit 600 also comprises a CAN interface 1616 for communicatingtrailer 512 data received by a plurality of sensors to PCB-A 1606. - Further,
Power Line 1620 provides a voltage of 12V to thedevice control unit 1604 which receives data from a plurality of sensors and transmits the received data tomicroprocessor 1606 ofbridge integrator unit 600.Bridge integrator unit 600 further transfers the data received from a plurality of sensor devices to the master control unit (MCU) 525 via wireless radio frequency (RF) interface. - Further,
FIG. 11 illustrates a detailed view of communication between various components of the network.Bridge integrator unit 600 receives data from a plurality of sensors installed on thetrailer 512 via wired or wireless interfaces.Bridge integrator unit 600 may receive sensory data through various wired communication modes such as RS232, CAN, etc.Bridge integrator unit 600 may also receive data related to thetires 1622 of thetrailer 512 through various sensors installed on thetires 1622 of thetrailer 512. The data received from the sensors installed on thetires 1622 may represent various tire conditions such as tire pressure, tire inflation etc. -
Bridge integrator unit 600 transmits the received sensory data to the master control unit (MCU) 525 viaradio frequency interface 1624, as also shown inFIG. 11 .MCU 525 transfers the data received frombridge integrator unit 600 to a third party interface via wireless transmission mode orMCU 525 may store the received data on a cloud server. The wireless transmission mode in accordance with the embodiment may be but not limited to cellular transmission mode. - Thus,
MCU 525 may transfer the received data to a remote location via cellular transmission, where a remote user may control thetrailer 512. The remote user may read and modify the data received byMCU 525 via atelematics user interface 1620. The user interface may be alerts dashboard, which gives a complete fleet overview of any trailer failures. A map of each trailer's location is displayed. Further, a trailer dashboard gives a complete digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position. The remote user may also enter commands for thetrailer 512 via thetelematics user interface 1620. - In addition, the
FIG. 11 also shows anose box assembly 1618 of the trailer communication system. The nose box assembly may include a wireless transmitting device with a communication protocol such as Zigbee or Bluetooth that will transmit signals to themaster control unit 525 or other remote device such as a laptop, tablet, or cell phone. The Lightfailure detection system 540 may also act as thenosebox assembly 1618. Thenosebox assembly 1618 may receive power from tractor and may transmit the power to bridgeintegrator unit 600,device control unit 1604,trailer ECU 1602 viapower line carrier 1610. - Further,
FIG. 12 represents a typical heavy duty trailer view detailing a driver side, curb side and rear side of thetrailer 512. The trailernose box assembly 1618 may transmit the power to bridgeintegrator unit 600,device control unit 1604;trailer ECU 1602 viapower line carrier 1610. In addition,bridge integrator unit 600 may receive data from a plurality of sensors installed on thetires 1622 of thetrailer 512 via a radio frequency (RF) interface 1626. The sensory data may indicate tire's conditions such as pressure, inflation etc. -
FIG. 13A schematically discloses various components ofbridge integrator unit 600. In the embodiment shown,bridge integrator unit 600 comprises a microcontroller 814 schematically shown herein as U1, which has analog features for supporting extreme low-power devices. Further,module 820 is an AW24MCHL-H2 transceiver amongwireless modules 804 which has a 2.4-GHz Direct Sequence Spread Spectrum (DSSS) complete radio module which includes a Cypress radio integrated circuit CyFi™ CYRF7936, integrated antenna, and external components. U7 and U11 shown in theFIG. 13A refer tomodule 820. - In addition, a
module BM70BLES1FC2 818 offers Bluetooth Low Energy solution for embedded applications. It conforms to Bluetooth core specifications to enhance the throughput and security for the IoT applications. IEEE 802.15.4 is a technical standard which defines the operation of low-rate wireless personal area networks (LR-WPANs). U12 shown in theFIG. 13A schematically refers to theBTLE module BM70BLES1FC2 818. Moreover, theAuxiliary connection module 808 comprises aFlash memory AT45DB081E 822 which is a 1.7V minimum, serial-interface sequential access suitable for a wide variety of digital voice, image, program code, and data storage applications. Flash—dual footprint comprising U8 and U15 shown inFIG. 13A are referred to herein as the Flash memory modules. - U5 shown in the
FIG. 13A refers toTRIPSNET Module 834 which may be a MRF24J40MD/ME which is a 2.4 GHz IEEE Std. 802.15.4™ compliant, surface mount module with integrated crystal, internal voltage regulator, matching circuitry, Power Amplifier (PA), Low Noise Amplifier (LNA) with PCB Trace Antenna (MRF24J40MD) or 50Ω external antenna connector (MRF24J40ME). U13 refers toRS232 Transceiver 812 which may be used to convert logic level signals of the UART to and from the external signaling levels, which may be standardized voltage levels, current levels, or other signals. -
FIG. 13B schematically discloses various components ofbridge integrator unit 600 in continuation toFIG. 13A . The power andbattery sub-system 806, as shown inFIG. 6 , comprises a dis-connectable Inputvoltage sense sub-system 826, a dis-connectable batteryvoltage sense sub-system 828, apower management sub-system 830 and avoltage regulator 832. With reference toFIG. 13B . U2 refers to the dis-connectable Inputvoltage sense sub-system 826. U3 refers to thepower management sub-system 830 and U4 refers to a voltage regulator which may be used to output a 3V constant voltage. - Additionally, with reference to
FIG. 13B , ICs 34 and 36 representDebug port 824 which is used to simplify development and debugging operations. U14 represents CAN interface 810 used to communicate sensory data from STEMCOM sensors to the microcontroller 814. U9 refers to5V boost regulator 832 which is a DC to DC converter providing 5 volts greater than the source voltage. U10 refers to CAN interface 810 which is used to communicate sensory data from STEMCOM sensors to the microcontroller 814. U16 with reference toFIG. 13B represents Micro-electromechanical systems (MEMS) accelerometer sensors used to measure displacement of thetrailer 512 with a position-measuring interface circuit. The measured data is then converted into a digital electrical signal through an analog-to-digital converter (ADC) for digital processing. - Further, in adapting the user interface to the monitored parameters and customized systems integrated with the
bridge integrator unit 600, the remote user interface may be modified overall, or widgets embedded in the user interface may be customized by customer and user preference. In addition the user may read and modify the data received byMCU 525 via atelematics user interface 1620. The user interface may be alerts at a dashboard, which gives a complete fleet overview of any trailer failures (SeeFIGS. 14-28 ). A map of each trailer's location may be displayed. A trailer dashboard gives an overall digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position, among other parameters. The remote user may also enter commands for thetrailer 512 via thetelematics user interface 1620. -
Telematics system 500 also includes a user interface or alerts dashboard, which gives an overall fleet overview of any trailer failures. A map of each trailer's location is displayed with written details as to the condition. A trailer dashboard provides a digital view of the trailer's current status including tethered/untethered, tractor voltage, lighting status, ABS status, tire conditions, temperature of the trailer, cargo status and door position.FIGS. 14-28 illustrate examples of user interface screen shots of the telematics road ready system with a bridge integrator unit, and customized widgets dependent on the monitored parameter(s). - It should be understood that various changes and modifications to the embodiments described herein will be apparent to those skilled in the art. Such changes and modifications can be made without departing from the spirit and scope of the present subject matter and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claims.
Claims (1)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/293,578 US20190268675A1 (en) | 2017-03-15 | 2019-03-05 | Telematics Road Ready System including a Bridge Integrator Unit |
CA3074847A CA3074847A1 (en) | 2019-03-05 | 2020-03-05 | Telematics road ready system including a bridge integrator unit |
MX2020002561A MX2020002561A (en) | 2019-03-05 | 2020-03-05 | Telematics road ready system including a bridge integrator unit. |
US17/107,012 US11496816B2 (en) | 2017-03-15 | 2020-11-30 | Telematics road ready system including a bridge integrator unit |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/460,166 US10093232B2 (en) | 2015-09-16 | 2017-03-15 | Telematics road ready system |
US15/904,422 US10388161B2 (en) | 2015-09-16 | 2018-02-25 | Telematics road ready system with user interface |
US201862638947P | 2018-03-05 | 2018-03-05 | |
US16/293,578 US20190268675A1 (en) | 2017-03-15 | 2019-03-05 | Telematics Road Ready System including a Bridge Integrator Unit |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/904,422 Continuation-In-Part US10388161B2 (en) | 2015-09-16 | 2018-02-25 | Telematics road ready system with user interface |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/107,012 Continuation US11496816B2 (en) | 2017-03-15 | 2020-11-30 | Telematics road ready system including a bridge integrator unit |
Publications (1)
Publication Number | Publication Date |
---|---|
US20190268675A1 true US20190268675A1 (en) | 2019-08-29 |
Family
ID=67685244
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/293,578 Abandoned US20190268675A1 (en) | 2017-03-15 | 2019-03-05 | Telematics Road Ready System including a Bridge Integrator Unit |
US17/107,012 Active US11496816B2 (en) | 2017-03-15 | 2020-11-30 | Telematics road ready system including a bridge integrator unit |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/107,012 Active US11496816B2 (en) | 2017-03-15 | 2020-11-30 | Telematics road ready system including a bridge integrator unit |
Country Status (1)
Country | Link |
---|---|
US (2) | US20190268675A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10688839B1 (en) * | 2019-05-15 | 2020-06-23 | Grote Industries, Inc. | Nose box insert for monitoring and fault detection in a truck trailer |
US11496816B2 (en) * | 2017-03-15 | 2022-11-08 | Truck-Lite Co., Llc | Telematics road ready system including a bridge integrator unit |
US20230171525A1 (en) * | 2019-09-17 | 2023-06-01 | Freightlucid, Llc | Railcar Sensor Communication System |
US20230192105A1 (en) * | 2020-09-15 | 2023-06-22 | Tusimple, Inc. | Digital inspection of health of autonomous vehicles |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024019926A1 (en) * | 2022-07-20 | 2024-01-25 | G3 Enterprises, Inc. | Gondola monitoring system and method |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5157376A (en) * | 1990-04-04 | 1992-10-20 | Mercedes-Benz Ag | Method and device for monitoring direction indicator lights of a vehicle trailer |
US6127939A (en) * | 1996-10-14 | 2000-10-03 | Vehicle Enhancement Systems, Inc. | Systems and methods for monitoring and controlling tractor/trailer vehicle systems |
US6218952B1 (en) * | 1998-09-30 | 2001-04-17 | Leslie R. Borland | Trailer light monitor |
US20030080856A1 (en) * | 2001-10-23 | 2003-05-01 | Spx Corporation | Apparatus and method for testing an antilock brake system |
US6788195B1 (en) * | 2002-08-09 | 2004-09-07 | Osborne Coinage Company | Light monitor |
US20050187675A1 (en) * | 2003-10-14 | 2005-08-25 | Kenneth Schofield | Vehicle communication system |
US20060238332A1 (en) * | 2005-02-02 | 2006-10-26 | Carle Patrick F | Wireless integrated condition monitoring system |
US20070063832A1 (en) * | 2005-09-16 | 2007-03-22 | Ollis Jeffrey D | Method and apparatus for using a wireless controller in a wired security system |
US7250872B2 (en) * | 2004-04-30 | 2007-07-31 | Siemens Aktiengesellschaft | Method and device for testing at least one LED strip |
US20090219148A1 (en) * | 2007-10-29 | 2009-09-03 | Donald Thomas, Llc | Wireless vehicle trailer monitoring and control system |
US20120161633A1 (en) * | 2010-12-27 | 2012-06-28 | Denso Corporation | Lighting apparatus and lighting fitting |
US8599260B1 (en) * | 2012-06-13 | 2013-12-03 | Zen-Tinel, Inc. | School bus traffic arm camera system |
US9489778B2 (en) * | 2010-07-27 | 2016-11-08 | General Motors Llc | Method and system for alerting a driver to a condition of a vehicle |
US9499109B2 (en) * | 2015-01-27 | 2016-11-22 | Peterson Manufacturing Company | Trailer communication system |
US20170072854A1 (en) * | 2015-09-16 | 2017-03-16 | Truck-Lite Co., Llc | Light Emitting Diode Failure Detection System for a Vehicle |
US20170171952A1 (en) * | 2015-09-16 | 2017-06-15 | Truck-Lite Co., Llc | Light Emitting Diode Failure Detection System for a Vehicle with Pre-trip Inspection |
US20180009377A1 (en) * | 2015-09-16 | 2018-01-11 | Truck-Lite Co., Llc | Telematics Road Ready System |
US20180099712A1 (en) * | 2016-10-07 | 2018-04-12 | Phillips Connect Technologies Llc | Smart trailer system |
US20180229786A1 (en) * | 2016-10-07 | 2018-08-16 | Phillips Connect Technologies Llc | Modular harness system |
US20180293891A1 (en) * | 2015-09-16 | 2018-10-11 | Scott Troutman | Telematics Road Ready System with User Interface |
Family Cites Families (186)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0629116Y2 (en) | 1985-04-12 | 1994-08-10 | 株式会社東海理化電機製作所 | Lamp burnout detection device |
US5142278A (en) | 1989-04-18 | 1992-08-25 | Qualcomm Incorporated | Current carrier tractor-trailer data link |
US6295449B1 (en) | 1992-01-27 | 2001-09-25 | @Track Communications, Inc. | Data messaging in a communications network using a feature request |
US6278936B1 (en) | 1993-05-18 | 2001-08-21 | Global Research Systems, Inc. | System and method for an advance notification system for monitoring and reporting proximity of a vehicle |
US6198390B1 (en) | 1994-10-27 | 2001-03-06 | Dan Schlager | Self-locating remote monitoring systems |
US6744352B2 (en) | 1995-11-09 | 2004-06-01 | Vehicle Enhancement Systems, Inc. | System, apparatus and methods for data communication between vehicle and remote data communication terminal, between portions of vehicle and other portions of vehicle, between two or more vehicles, and between vehicle and communications network |
US6111524A (en) * | 1995-11-09 | 2000-08-29 | Vehicle Enhancement Systems, Inc. | Systems and methods for identifying tractor/trailers and components thereof |
US6084870A (en) | 1996-07-22 | 2000-07-04 | Qualcomm Incorporated | Method and apparatus for the remote monitoring and configuration of electronic control systems |
US6346876B1 (en) | 1996-08-22 | 2002-02-12 | Kenneth E. Flick | Multi-vehicle compatible control system generating command signals on a data bus and associated methods |
US7394363B1 (en) | 1998-05-12 | 2008-07-01 | Bahador Ghahramani | Intelligent multi purpose early warning system for shipping containers, components therefor and methods of making the same |
US6317029B1 (en) | 1998-08-07 | 2001-11-13 | Aeroastro, Llc | In situ remote sensing |
DE19852351A1 (en) | 1998-11-13 | 2000-05-18 | Hella Kg Hueck & Co | Diagnostic system for an LED light in a motor vehicle |
AU2355200A (en) | 1998-12-07 | 2000-06-26 | Global Trak, Inc. | Apparatus and method for triggerable location reporting |
US6611686B1 (en) | 1999-02-09 | 2003-08-26 | Elite Logistics Services, Inc. | Tracking control and logistics system and method |
US6130487A (en) | 1999-02-19 | 2000-10-10 | Paccar Inc | Electronic interface and method for connecting the electrical systems of a truck and trailer |
US6175301B1 (en) * | 1999-03-19 | 2001-01-16 | Gregory H. Piesinger | Low tire pressure warning system |
US6266617B1 (en) | 1999-06-10 | 2001-07-24 | Wayne W. Evans | Method and apparatus for an automatic vehicle location, collision notification and synthetic voice |
US6392364B1 (en) | 1999-06-21 | 2002-05-21 | Denso Corporation | High voltage discharge lamp apparatus for vehicles |
US6292724B1 (en) | 1999-10-12 | 2001-09-18 | Micrologic, Inc. | Method of and system and apparatus for remotely monitoring the location, status, utilization and condition of widely geographically dispresed fleets of vehicular construction equipment and the like and providing and displaying such information |
MXPA02004971A (en) | 1999-11-17 | 2002-09-18 | Vehicle Enhancement Sys Inc | Method for data communication between a vehicle and a remote terminal. |
US6509867B1 (en) | 2000-05-08 | 2003-01-21 | Securatrak, Inc. | Article tracking device |
US8032278B2 (en) | 2000-05-17 | 2011-10-04 | Omega Patents, L.L.C. | Vehicle tracking unit with downloadable codes and associated methods |
US9015071B2 (en) | 2000-09-08 | 2015-04-21 | Intelligent Technologies International, Inc. | Asset monitoring using the internet |
US6907253B2 (en) | 2001-03-08 | 2005-06-14 | Qualcomm, Incorporated | Method and apparatus for high density message coding |
EP1246094A1 (en) | 2001-03-27 | 2002-10-02 | TELEFONAKTIEBOLAGET L M ERICSSON (publ) | Container surveillance system and related method |
AU2002310023A1 (en) | 2001-05-22 | 2002-12-03 | Geospatial Technologies, Inc. | A durable global asset-tracking device and a method of using the same |
US6674288B2 (en) | 2001-09-21 | 2004-01-06 | International Truck Intellectual Property Company, Llc | Vehicle lamp inspection system |
DE10160750A1 (en) | 2001-12-11 | 2003-06-12 | Wabco Gmbh & Co Ohg | Process for the exchange of data between a towing vehicle and a connected trailer vehicle |
US6651001B2 (en) | 2002-03-18 | 2003-11-18 | Micrologics, Inc. | Method of and system and apparatus for integrating maintenance vehicle and service personnel tracking information with the remote monitoring of the location, status, utilization and condition of widely geographically dispersed fleets of vehicular construction equipment and the like to be maintained, and providing and displaying together both construction and maintenance vehicle information |
US6735150B2 (en) | 2002-03-28 | 2004-05-11 | Micrologic, Inc. | Method of and apparatus for distinguishing engine idling and working hours |
US6804602B2 (en) | 2002-04-02 | 2004-10-12 | Lockheed Martin Corporation | Incident-aware vehicular sensors for intelligent transportation systems |
US20030204407A1 (en) | 2002-04-26 | 2003-10-30 | John Nabors | System and apparatus for tracking, monitoring, and reporting parameter of a mobile unit |
JP2005527920A (en) * | 2002-05-07 | 2005-09-15 | アーゴ−テック・コーポレーション | Tracking system and related methods |
GB0211644D0 (en) | 2002-05-21 | 2002-07-03 | Wesby Philip B | System and method for remote asset management |
US6687609B2 (en) | 2002-06-13 | 2004-02-03 | Navcom Technology, Inc. | Mobile-trailer tracking system and method |
CA2500996C (en) | 2002-10-01 | 2010-11-09 | Truck-Lite Co., Inc. | Light emitting diode headlamp and headlamp assembly |
US6832153B2 (en) | 2002-11-27 | 2004-12-14 | Mobilearia | Method and apparatus for providing information pertaining to vehicles located along a predetermined travel route |
US7064658B2 (en) | 2003-03-10 | 2006-06-20 | Daimlerchrysler Corporation | Integrated vehicle power distribution and gateway system |
US6858986B2 (en) | 2003-03-19 | 2005-02-22 | Mite (Milks Industries Towing Equipment, Inc.) | Programmable LED vehicle marker light assembly |
DE10313467A1 (en) | 2003-03-26 | 2004-10-07 | Daimlerchrysler Ag | Fault diagnosis and/or control information re-programming method for traffic network control device, using radio link between hand-held diagnosis device and control device |
WO2005002125A2 (en) | 2003-06-24 | 2005-01-06 | Startrak, L.L.C. | Wireless control for creation of, and command response to, standard freight shipment messages |
CA2775736C (en) | 2003-08-27 | 2014-09-30 | Osram Sylvania Inc. | Driver circuit for led vehicle lamp |
US7098784B2 (en) | 2003-09-03 | 2006-08-29 | System Planning Corporation | System and method for providing container security |
US7046132B2 (en) | 2003-11-12 | 2006-05-16 | Emergency Technology, Inc. | Lamp monitor and method for operating a lamp monitor |
US7126464B2 (en) | 2003-11-19 | 2006-10-24 | Qualcomm Incorporated | Method and apparatus for controlling a valve during a hazard event |
US7265668B1 (en) | 2003-12-12 | 2007-09-04 | Skybitz, Inc. | System and method for asset tracking and monitoring |
US20050137983A1 (en) | 2003-12-18 | 2005-06-23 | Matthew Bells | System and method for digital rights management |
US20050273277A1 (en) * | 2004-01-14 | 2005-12-08 | University Of Tennessee Research Foundation, Inc. | Vehicle fatigue life and durability monitoring system and methodology |
US7460871B2 (en) | 2004-01-16 | 2008-12-02 | Skyguard, Llc | Method and system for tracking mobile telemetry devices |
WO2006047538A2 (en) | 2004-10-25 | 2006-05-04 | Payment Protection Systems, Inc. | Method and system for monitoring a vehicle |
DE102004056123A1 (en) | 2004-11-20 | 2006-06-08 | Daimlerchrysler Ag | commercial vehicle |
US9601015B2 (en) * | 2005-02-25 | 2017-03-21 | Concaten, Inc. | Maintenance decision support system and method for vehicular and roadside applications |
US7339460B2 (en) | 2005-03-02 | 2008-03-04 | Qualcomm Incorporated | Method and apparatus for detecting cargo state in a delivery vehicle |
US7430464B2 (en) | 2005-03-15 | 2008-09-30 | International Truck Intellectual Property Company, Llc | Dynamic vehicle electrical system test |
US8559937B2 (en) | 2005-06-07 | 2013-10-15 | Qualcomm Incorporated | Wireless system for providing critical sensor alerts for equipment |
US8461958B2 (en) | 2005-08-17 | 2013-06-11 | Wireless Data Solutions, Llc | System for monitoring and control of transport containers |
US7382239B2 (en) * | 2005-08-23 | 2008-06-03 | Gm Global Technology Operations, Inc. | System and method for improving received signal strength for an in-vehicle wireless communication system |
US7498925B2 (en) | 2005-09-12 | 2009-03-03 | Skybitz, Inc. | System and method for reporting a status of an asset |
US7877208B1 (en) | 2005-09-29 | 2011-01-25 | Skybitz, Inc. | Sensor interface with mobile terminal satellite modem and global location system |
US7339465B1 (en) | 2005-10-06 | 2008-03-04 | Cheng John C | Vehicle-to-trailer light connection verification tester |
CN101461271B (en) | 2005-10-14 | 2012-05-30 | 开利网络有限责任公司 | System and method for real-time management of mobile resources |
US7853210B2 (en) | 2005-11-14 | 2010-12-14 | System Planning Corporation | Intelligent sensor open architecture for a container security system |
US7702358B2 (en) | 2005-11-14 | 2010-04-20 | System Planning Corporation | System and method for communications of cargo containers in a container security system using wireless ad-hoc networking techniques |
US7973717B2 (en) | 2005-11-14 | 2011-07-05 | System Planning Corporation | System and method for an integrated antenna in a cargo container monitoring and security system |
US8620623B2 (en) | 2005-11-14 | 2013-12-31 | Globaltrak, Llc | Hierarchical and distributed information processing architecture for a container security system |
US7710050B2 (en) | 2005-11-17 | 2010-05-04 | Magna International Inc | Series connected power supply for semiconductor-based vehicle lighting systems |
JP2007200610A (en) | 2006-01-24 | 2007-08-09 | Koito Mfg Co Ltd | Lighting control device of vehicular lamp |
US7429917B2 (en) | 2006-02-27 | 2008-09-30 | Whelen Engineering Company, Inc. | LED aviation warning light with fault detection |
ATE478542T1 (en) | 2006-03-03 | 2010-09-15 | Actia Uk Ltd | LIGHTING AND LIGHTING CONTROL SYSTEMS |
US7813870B2 (en) * | 2006-03-03 | 2010-10-12 | Inrix, Inc. | Dynamic time series prediction of future traffic conditions |
US20070239346A1 (en) | 2006-04-05 | 2007-10-11 | Pegasus Transtech Corporation | System and Method of Receiving Data from a Plurality of Trucking Companies and Disseminating Data to a Plurality of Parties |
US8223009B2 (en) | 2006-05-15 | 2012-07-17 | TRACK America | Mobile asset tracking system and method |
US7784707B2 (en) | 2006-05-18 | 2010-08-31 | Xata Corporation | Environmental condition monitoring of a container |
US7714719B2 (en) | 2006-06-27 | 2010-05-11 | Qualcomm Incorporated | Field disturbance sensor utilizing leaky or radiating coaxial cable for a conformable antenna pattern |
US7535375B2 (en) | 2006-07-21 | 2009-05-19 | Mcdermott Sr Vernon C | Lamp or LED failure monitoring system |
US8633813B2 (en) | 2006-08-25 | 2014-01-21 | Uusi, Llc | Vehicle light system |
US8803683B2 (en) | 2006-09-13 | 2014-08-12 | Trackpoint Systems, Llc | System, method, and device for measuring and reporting changing levels of liquids in storage tanks |
US7978065B2 (en) | 2006-09-13 | 2011-07-12 | Trackpoint Systems, Llc | Device, system and method for tracking mobile assets |
US7725216B2 (en) | 2006-09-14 | 2010-05-25 | Qualcomm Incorporated | Critical event reporting |
US7589471B2 (en) | 2006-10-20 | 2009-09-15 | International Truck Intellectual Property Company, Llc | System for pre-indication of motor vehicle HID lamp feature |
DE102006057643A1 (en) | 2006-12-05 | 2008-06-12 | Deutsche Post Ag | Method and system for monitoring a container |
US8010127B2 (en) | 2007-02-22 | 2011-08-30 | Skybitz, Inc. | Satellite aided location tracking and data services using geosynchronous and low earth orbit satellites with global locating system |
EP1965609A3 (en) | 2007-02-27 | 2011-06-15 | Lumination, LLC | LED chain failure detection |
US7904260B2 (en) | 2007-02-28 | 2011-03-08 | Stmicroelectronics, Inc. | Integrated circuit and method for classification of electrical devices and short circuit protection |
US20080229289A1 (en) * | 2007-03-13 | 2008-09-18 | First Data Corporation | Bitmapped Data String Conversions |
US7843335B2 (en) | 2007-03-13 | 2010-11-30 | Blackbird Technologies, Inc. | Mobile asset tracking unit, system and method |
US7932815B2 (en) | 2007-03-16 | 2011-04-26 | Intermec Ip Corp. | Wireless tractor-trailer communications |
US7504783B2 (en) | 2007-03-23 | 2009-03-17 | National Semiconductor Corporation | Circuit for driving and monitoring an LED |
ES2324001B1 (en) | 2007-05-04 | 2010-05-13 | Oscar Ruben Moreno Cano | SYSTEM FOR THE LOCATION, MONITORING, CONTROL AND MANAGEMENT OF MOBILE OR TRANSPORTABLE ELEMENTS. |
US7646295B1 (en) | 2007-06-04 | 2010-01-12 | Skybitz, Inc. | System and method for asset tracking and monitoring using antenna diversity |
US8179238B2 (en) | 2007-07-23 | 2012-05-15 | R&L Carriers, Inc. | Information transmission and processing systems and methods for freight carriers |
US8362886B2 (en) | 2007-09-26 | 2013-01-29 | Omega Patents, L.L.C. | Multi-controller data bus adaptor and associated methods |
US8390464B1 (en) | 2007-10-11 | 2013-03-05 | Startrak Information Technologies, Llc | Integrating refrigerated transport operations and logistics by creating operational states via wireless communications |
US20090160646A1 (en) | 2007-12-20 | 2009-06-25 | General Electric Company | System and method for monitoring and tracking inventories |
US8751098B2 (en) | 2008-01-25 | 2014-06-10 | Omnitracs, Llc | Method of monitoring CANbus information |
US8374824B2 (en) | 2008-02-27 | 2013-02-12 | Identec Solutions Ag | Wireless data transmission of a refrigerated container unit |
US8022843B2 (en) * | 2008-03-31 | 2011-09-20 | The Boeing Company | Wireless aircraft sensor network |
US8307667B2 (en) | 2008-04-30 | 2012-11-13 | Carrier Corporation | Method and system for remote acquisition of refrigerated vehicle data via telematics |
US8416067B2 (en) | 2008-09-09 | 2013-04-09 | United Parcel Service Of America, Inc. | Systems and methods for utilizing telematics data to improve fleet management operations |
WO2010035168A1 (en) | 2008-09-23 | 2010-04-01 | Koninklijke Philips Electronics, N.V. | Current limiting controlling for power supply, e.g. led driver, having automatic reset |
US8700255B2 (en) * | 2008-10-08 | 2014-04-15 | Trimble Navigation Limited | Devices, systems, and methods for monitoring driver and vehicle behavior |
DE102008054366A1 (en) | 2008-11-03 | 2010-05-06 | Wabco Gmbh | Control arrangement for a trailer vehicle |
US9415759B2 (en) | 2008-11-26 | 2016-08-16 | Haldex Brake Corporation | Vehicle monitoring system with multiple inputs for a tractor-trailer |
US8947096B1 (en) | 2009-04-10 | 2015-02-03 | Paul Wolf | Trailer light tester |
JP2010287601A (en) | 2009-06-09 | 2010-12-24 | Panasonic Corp | Light emitting element drive unit |
EP2269870B1 (en) | 2009-06-24 | 2012-06-20 | Nxp B.V. | Exterior vehicle lights |
WO2011030381A1 (en) | 2009-09-10 | 2011-03-17 | 三菱電機株式会社 | Led lighting apparatus for head lamp, and head lamp lighting system for vehicle |
US8334662B2 (en) | 2009-09-11 | 2012-12-18 | Iwatt Inc. | Adaptive switch mode LED driver |
JP5389182B2 (en) | 2009-09-30 | 2014-01-15 | 東芝三菱電機産業システム株式会社 | Power conversion system |
US8558690B2 (en) | 2009-10-01 | 2013-10-15 | Ford Global Technologies, Llc | Vehicle system passive notification using remote device |
US8461973B2 (en) * | 2009-10-02 | 2013-06-11 | Orion Innovations | Integrated vehicle cellular telephone detection system |
US8489271B2 (en) | 2009-10-31 | 2013-07-16 | Calamp Corp. | Systems and methods for virtual ignition detection |
US8378843B2 (en) | 2009-12-22 | 2013-02-19 | General Electric Company | System and method to provide value added services in an asset network |
US8653539B2 (en) | 2010-01-04 | 2014-02-18 | Cooledge Lighting, Inc. | Failure mitigation in arrays of light-emitting devices |
US20110169447A1 (en) | 2010-01-11 | 2011-07-14 | Leviton Manufacturing Co., Inc. | Electric vehicle supply equipment |
US8853965B2 (en) | 2010-02-01 | 2014-10-07 | Twisthink, L.L.C. | Luminary control systems |
US8503145B2 (en) | 2010-04-14 | 2013-08-06 | Vektrek Electronic Systems, Inc. | Fault protected current source for lighting element testing |
CA2797486A1 (en) | 2010-05-04 | 2011-11-10 | Xicato, Inc. | Flexible electrical connection of an led-based illumination device to a light fixture |
WO2011142852A1 (en) | 2010-05-14 | 2011-11-17 | Raymond Suda | Tractor trailer data communication apparatus and method |
US8494447B2 (en) * | 2010-07-29 | 2013-07-23 | General Motors Llc | Aftermarket telematics unit for use with a vehicle |
US8412406B2 (en) | 2010-08-13 | 2013-04-02 | Deere & Company | Method and system for performing diagnostics or software maintenance for a vehicle |
EP2616278B8 (en) | 2010-09-14 | 2018-08-15 | Lumileds Holding B.V. | Lighting system |
US9189661B1 (en) | 2010-12-06 | 2015-11-17 | Globaltrak, Llc | Apparatus for establishing a mesh network for reefer sensor architecture |
WO2012077013A2 (en) | 2010-12-08 | 2012-06-14 | Koninklijke Philips Electronics N.V. | Control circuit for led lamps in automobile applications |
JP5828103B2 (en) | 2010-12-20 | 2015-12-02 | パナソニックIpマネジメント株式会社 | LED lighting device and lighting apparatus using the same |
US8812173B2 (en) | 2010-12-21 | 2014-08-19 | Calamp Corp. | Systems and methods for collecting information from vehicle devices via a vehicle data bus |
US8635035B2 (en) | 2011-03-15 | 2014-01-21 | Honeywell International Inc. | Systems and methods for monitoring operation of an LED string |
US9208626B2 (en) | 2011-03-31 | 2015-12-08 | United Parcel Service Of America, Inc. | Systems and methods for segmenting operational data |
US8760274B2 (en) | 2011-12-07 | 2014-06-24 | Spireon, Inc. | System for communicating between a trailer tracking device, a truck tracking device, and a central monitoring station |
US9147335B2 (en) | 2011-12-22 | 2015-09-29 | Omnitracs, Llc | System and method for generating real-time alert notifications in an asset tracking system |
US8902590B2 (en) | 2012-02-13 | 2014-12-02 | Omnitracs, Llc | Solar powered apparatus having a thermally decoupled solar panel for tracking a portable asset |
US8816697B2 (en) | 2012-02-29 | 2014-08-26 | Nissan North America, Inc. | Trailer connection checking device and method |
US20160086391A1 (en) | 2012-03-14 | 2016-03-24 | Autoconnect Holdings Llc | Fleetwide vehicle telematics systems and methods |
WO2013142698A1 (en) | 2012-03-21 | 2013-09-26 | Thermo King Corporation | Systems and methods for handling discrete sensor information in a transport refrigeration system |
JP6055540B2 (en) * | 2012-03-21 | 2016-12-27 | パワーキャスト コーポレイションPowercast Corporation | Wireless sensor system, method and apparatus with switch and outlet control |
US9457666B2 (en) * | 2012-03-30 | 2016-10-04 | Elwha Llc | Method and apparatus for supplying auxiliary electrical power to an electric or hybrid vehicle |
US9127945B2 (en) | 2012-04-04 | 2015-09-08 | Trimble Navigation Limited | Systems and methods for managing a cargo transaction |
US20150306928A1 (en) * | 2012-04-09 | 2015-10-29 | John McCollum | Trailer Lighting and Braking System with Pressure Failure Alarm |
EP2717653B1 (en) | 2012-10-04 | 2016-09-14 | Nxp B.V. | A method of detecting a LED failure, a controller therefor, a lighting unit and lighting system |
US9119270B2 (en) | 2012-10-04 | 2015-08-25 | Osram Sylvania Inc. | Solid state lighting device and driver configured for failure detection and recovery |
US9406222B2 (en) | 2012-10-18 | 2016-08-02 | Calamp Corp. | Systems and methods for location reporting of detected events in vehicle operation |
US9185768B2 (en) | 2012-11-16 | 2015-11-10 | Apple Inc. | Short circuit protection |
DE102012023968A1 (en) | 2012-12-07 | 2014-06-12 | Wabco Gmbh | Method and apparatus for transmitting telematics data from a truck to a telematics portal |
AU2013360014B2 (en) | 2012-12-10 | 2017-10-19 | Axiflux Holdings Pty Ltd | Electric motor/generator with integrated differential |
GB2511095A (en) | 2013-02-22 | 2014-08-27 | Scorpion Automotive Ltd | Trailer and bulb failure detection |
FR3003510B1 (en) | 2013-03-21 | 2015-03-27 | Inteva Products France Sas | PIVOTING SHEATH STOP FOR SHEATH, SUPPORT, GUIDE RAIL, ASSEMBLY, WINDOW LIFTER, CORRESPONDING MOUNTING METHOD |
US9139130B2 (en) | 2013-06-06 | 2015-09-22 | Douglas J. Wolfe | Light component coordination |
JP6160955B2 (en) | 2013-07-10 | 2017-07-12 | パナソニックIpマネジメント株式会社 | LIGHT EMITTING DIODE DRIVING DEVICE, VEHICLE LIGHTING DEVICE HAVING THE SAME, AND VEHICLE |
DE102013015370A1 (en) | 2013-09-13 | 2015-03-19 | Wabco Gmbh | Method for providing and transmitting data, in particular in connection with a vehicle |
JP6234154B2 (en) | 2013-10-15 | 2017-11-22 | 三菱電機株式会社 | Light source control device and light source control method |
CN105766067B (en) * | 2013-10-23 | 2019-06-18 | 鲍尔卡斯特公司 | Automatic system for Lighting control |
US9434308B2 (en) | 2013-11-15 | 2016-09-06 | R.A. Phillips Industries, Inc. | System for detecting the integrity of a lighting circuit |
US9358921B2 (en) | 2013-11-15 | 2016-06-07 | Virginia Electronic & Lighting, LLC | LED signal lamp |
KR101710317B1 (en) | 2013-11-22 | 2017-02-24 | 퀄컴 인코포레이티드 | System and method for configuring an interior of a vehicle based on preferences provided with multiple mobile computing devices within the vehicle |
WO2015171825A1 (en) * | 2014-05-06 | 2015-11-12 | Carvajal Hernan Ramiro | Switch network of containers and trailers for transportation, storage, and distribution of physical items |
GB2529141A (en) * | 2014-07-09 | 2016-02-17 | Paresh Jogia | Body heat powered wireless transmitter |
US9628565B2 (en) | 2014-07-23 | 2017-04-18 | Here Global B.V. | Highly assisted driving platform |
US20160027224A1 (en) | 2014-07-28 | 2016-01-28 | Ford Global Technologies, Llc | Method and Apparatus for Vehicle Data Monitoring |
CA2958633C (en) | 2014-08-18 | 2019-06-11 | Trimble Navigation Limited | Tractor-trailer connections for image capture data |
US10003926B2 (en) | 2014-09-16 | 2018-06-19 | DataSpark, Pte., Ltd. | Predicting human movement behaviors using location services model |
JP2016071981A (en) | 2014-09-29 | 2016-05-09 | 三菱電機株式会社 | Light source control device and light source control method |
KR102250052B1 (en) | 2014-11-03 | 2021-05-11 | 삼성디스플레이 주식회사 | Display apparatus |
US20160121792A1 (en) | 2014-11-03 | 2016-05-05 | Js Products, Inc. | Trailer light diagnostic device |
US20160128168A1 (en) | 2014-11-04 | 2016-05-05 | Thermo King Corporation | Network light device for a transport unit |
KR101592784B1 (en) | 2014-11-06 | 2016-02-15 | 현대자동차주식회사 | Apparatus and Method for Disconnecting Detection of Lamps |
EP3281493A1 (en) * | 2015-04-10 | 2018-02-14 | Danmarks Tekniske Universitet | Medical preparation container comprising microwave powered sensor assembly |
TWI634024B (en) * | 2015-04-17 | 2018-09-01 | 矽力杰股份有限公司 | Tire pressure detecting device group with Bluetooth signal conversion |
US10150339B2 (en) | 2015-04-24 | 2018-12-11 | Advantage Enterprises, Inc. | Systems and methods for monitoring tire pressure |
FR3035767B1 (en) | 2015-04-29 | 2017-05-19 | Valeo Vision | DEVICE AND METHOD FOR DETECTING A SHORT-CIRCULATED ELECTROLUMINESCENT DIODE IN A LUMINOUS DEVICE OF A MOTOR VEHICLE |
US10149370B2 (en) * | 2015-05-04 | 2018-12-04 | Powercast Corporation | Automated system for lighting control |
US10284387B2 (en) * | 2015-05-29 | 2019-05-07 | GM Global Technology Operations LLC | Hybrid intra-vehicle communication network |
US9740892B2 (en) | 2015-08-26 | 2017-08-22 | Blackberry Limited | Method and system for asset tracking in an enterprise environment |
US20180279429A1 (en) | 2015-09-17 | 2018-09-27 | Innosys, Inc. | Solid State Lighting Systems |
US9776847B2 (en) * | 2015-10-14 | 2017-10-03 | Recon Dynamics, Llc | Comprehensive worksite and transportation safety system |
TWI613623B (en) * | 2015-11-06 | 2018-02-01 | 財團法人資訊工業策進會 | Smart remote controller, electronic device control system and electronic device control method |
US10694461B2 (en) | 2016-01-04 | 2020-06-23 | Blackberry Limited | Method and mobile transceiver for asset tracking |
US9916559B2 (en) | 2016-01-04 | 2018-03-13 | Blackberry Limited | Mobile transceiver having selectable travel modes and a method of operation |
JP6767189B2 (en) | 2016-07-26 | 2020-10-14 | セイコーインスツル株式会社 | Thermal printers and portable terminals |
TWI650975B (en) * | 2016-08-25 | 2019-02-11 | 凌華科技股份有限公司 | LoRa mobile device providing mobile device direct access to LoRa information packet and data transmission method thereof |
CN109891937B (en) * | 2016-10-07 | 2023-07-18 | 鲍尔卡斯特公司 | Lighting control automation system |
US20190268675A1 (en) * | 2017-03-15 | 2019-08-29 | Scott Troutman | Telematics Road Ready System including a Bridge Integrator Unit |
WO2018203911A1 (en) | 2017-05-05 | 2018-11-08 | Ford Global Technologies, Llc | Adaptive diagnostic parametrization |
US11723489B2 (en) * | 2017-06-01 | 2023-08-15 | Apption Labs Limited | Temperature sensing devices and wireless communication improvements for cooking appliances |
CA3067545C (en) * | 2017-06-30 | 2023-01-24 | HawkEye 360, Inc. | Detecting radio signal emitter locations |
US11445348B2 (en) * | 2020-01-23 | 2022-09-13 | Ademco Inc. | Bluetooth perimeter extension |
US11385906B2 (en) * | 2020-04-13 | 2022-07-12 | Silicon Motion, Inc. | Computer program product and method and apparatus for controlling access to flash storage |
-
2019
- 2019-03-05 US US16/293,578 patent/US20190268675A1/en not_active Abandoned
-
2020
- 2020-11-30 US US17/107,012 patent/US11496816B2/en active Active
Patent Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5157376A (en) * | 1990-04-04 | 1992-10-20 | Mercedes-Benz Ag | Method and device for monitoring direction indicator lights of a vehicle trailer |
US6127939A (en) * | 1996-10-14 | 2000-10-03 | Vehicle Enhancement Systems, Inc. | Systems and methods for monitoring and controlling tractor/trailer vehicle systems |
US6218952B1 (en) * | 1998-09-30 | 2001-04-17 | Leslie R. Borland | Trailer light monitor |
US20030080856A1 (en) * | 2001-10-23 | 2003-05-01 | Spx Corporation | Apparatus and method for testing an antilock brake system |
US6788195B1 (en) * | 2002-08-09 | 2004-09-07 | Osborne Coinage Company | Light monitor |
US20050187675A1 (en) * | 2003-10-14 | 2005-08-25 | Kenneth Schofield | Vehicle communication system |
US7250872B2 (en) * | 2004-04-30 | 2007-07-31 | Siemens Aktiengesellschaft | Method and device for testing at least one LED strip |
US20060238332A1 (en) * | 2005-02-02 | 2006-10-26 | Carle Patrick F | Wireless integrated condition monitoring system |
US20070063832A1 (en) * | 2005-09-16 | 2007-03-22 | Ollis Jeffrey D | Method and apparatus for using a wireless controller in a wired security system |
US20090219148A1 (en) * | 2007-10-29 | 2009-09-03 | Donald Thomas, Llc | Wireless vehicle trailer monitoring and control system |
US9489778B2 (en) * | 2010-07-27 | 2016-11-08 | General Motors Llc | Method and system for alerting a driver to a condition of a vehicle |
US20120161633A1 (en) * | 2010-12-27 | 2012-06-28 | Denso Corporation | Lighting apparatus and lighting fitting |
US8599260B1 (en) * | 2012-06-13 | 2013-12-03 | Zen-Tinel, Inc. | School bus traffic arm camera system |
US9499109B2 (en) * | 2015-01-27 | 2016-11-22 | Peterson Manufacturing Company | Trailer communication system |
US10093232B2 (en) * | 2015-09-16 | 2018-10-09 | Truck-Lite Co., Llc | Telematics road ready system |
US20170171952A1 (en) * | 2015-09-16 | 2017-06-15 | Truck-Lite Co., Llc | Light Emitting Diode Failure Detection System for a Vehicle with Pre-trip Inspection |
US20180009377A1 (en) * | 2015-09-16 | 2018-01-11 | Truck-Lite Co., Llc | Telematics Road Ready System |
US10065563B2 (en) * | 2015-09-16 | 2018-09-04 | Truck-Lite Co. Llc | Light emitting diode failure detection system for a vehicle |
US20170072854A1 (en) * | 2015-09-16 | 2017-03-16 | Truck-Lite Co., Llc | Light Emitting Diode Failure Detection System for a Vehicle |
US20180293891A1 (en) * | 2015-09-16 | 2018-10-11 | Scott Troutman | Telematics Road Ready System with User Interface |
US10271411B2 (en) * | 2015-09-16 | 2019-04-23 | Truck-Lite Co., Llc | Light emitting diode failure detection system for a vehicle with pre-trip inspection |
US10388161B2 (en) * | 2015-09-16 | 2019-08-20 | Truck-Lite Co., Llc | Telematics road ready system with user interface |
US20180099712A1 (en) * | 2016-10-07 | 2018-04-12 | Phillips Connect Technologies Llc | Smart trailer system |
US20180229786A1 (en) * | 2016-10-07 | 2018-08-16 | Phillips Connect Technologies Llc | Modular harness system |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11496816B2 (en) * | 2017-03-15 | 2022-11-08 | Truck-Lite Co., Llc | Telematics road ready system including a bridge integrator unit |
US10688839B1 (en) * | 2019-05-15 | 2020-06-23 | Grote Industries, Inc. | Nose box insert for monitoring and fault detection in a truck trailer |
US11220146B2 (en) | 2019-05-15 | 2022-01-11 | Grote Industries, Inc. | Nose box insert for monitoring and fault detection in a truck trailer |
US20230171525A1 (en) * | 2019-09-17 | 2023-06-01 | Freightlucid, Llc | Railcar Sensor Communication System |
US11849266B2 (en) * | 2019-09-17 | 2023-12-19 | Freightlucid, Llc | Railcar sensor communication system |
US20230192105A1 (en) * | 2020-09-15 | 2023-06-22 | Tusimple, Inc. | Digital inspection of health of autonomous vehicles |
Also Published As
Publication number | Publication date |
---|---|
US20210112318A1 (en) | 2021-04-15 |
US11496816B2 (en) | 2022-11-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11496816B2 (en) | Telematics road ready system including a bridge integrator unit | |
US10093232B2 (en) | Telematics road ready system | |
US10388161B2 (en) | Telematics road ready system with user interface | |
WO2008033981A2 (en) | Device, system and method for tracking mobile assets | |
US9110897B2 (en) | Sensor tag and method of providing service using the same | |
US20030167345A1 (en) | Communications bridge between a vehicle information network and a remote system | |
US8918148B2 (en) | Systems and methods for controlling sensor devices in mobile devices | |
CN103419577B (en) | A kind of scalable universal tire pressure sensing apparatus, system and network system realization | |
CN102482909A (en) | Liftgate controller | |
WO2009080097A1 (en) | Device for receiving signals from sensors associated with vehicle's components, particularly tires, and system comprising the same | |
CN103069786A (en) | Sensor module | |
US10040324B2 (en) | Tire-monitoring system and method therefor | |
KR100726053B1 (en) | A tire pressure monitoring system and a control method thereof | |
CN101911131B (en) | Method for displaying information | |
KR20110085679A (en) | The apparatus of self-diagnosi with zigbee communication and can communication in car | |
US20120198120A1 (en) | Expanded protocol adapter for in-vehicle networks | |
CA3074847A1 (en) | Telematics road ready system including a bridge integrator unit | |
US20180246831A1 (en) | Device and system for aggregating networks and serving data from those networks to computers | |
CN113687711B (en) | Terminal wake-up circuit and wake-up method | |
CA3054668A1 (en) | Telematics road ready system | |
CN114633589A (en) | Tire monitoring device, tire monitoring system and method of operating the same | |
US11758392B1 (en) | Electronic tag device | |
CN206075017U (en) | Intelligent watch | |
CN219811186U (en) | Electronic component, device capable of adapting to multiple electronic components and electronic product | |
CN114780162B (en) | Device capable of adapting to multiple electronic components and electronic product capable of replacing electronic components |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |
|
AS | Assignment |
Owner name: MIDCAP FINANCIAL TRUST, MARYLAND Free format text: SECURITY INTEREST;ASSIGNORS:TRUCK-LITE CO., LLC;DAVCO TECHNOLOGY, LLC;JST PERFORMANCE, LLC;AND OTHERS;REEL/FRAME:051396/0540 Effective date: 20191213 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
AS | Assignment |
Owner name: TRUCK-LITE CO., LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ELMER, ROGER;TROUTMAN, SCOTT;KING, ANDREW;SIGNING DATES FROM 20130520 TO 20200908;REEL/FRAME:054036/0727 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: LUMITEC, LLC, FLORIDA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MIDCAP FINANCIAL TRUST;REEL/FRAME:066582/0385 Effective date: 20240213 Owner name: JST PERFORMANCE, LLC, ARIZONA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MIDCAP FINANCIAL TRUST;REEL/FRAME:066582/0385 Effective date: 20240213 Owner name: DAVCO TECHNOLOGY, LLC, MICHIGAN Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MIDCAP FINANCIAL TRUST;REEL/FRAME:066582/0385 Effective date: 20240213 Owner name: TRUCK-LITE CO., LLC, PENNSYLVANIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MIDCAP FINANCIAL TRUST;REEL/FRAME:066582/0385 Effective date: 20240213 |