WO2020142200A1 - Dispositif de consignation de données de plusieurs véhicules - Google Patents

Dispositif de consignation de données de plusieurs véhicules Download PDF

Info

Publication number
WO2020142200A1
WO2020142200A1 PCT/US2019/066795 US2019066795W WO2020142200A1 WO 2020142200 A1 WO2020142200 A1 WO 2020142200A1 US 2019066795 W US2019066795 W US 2019066795W WO 2020142200 A1 WO2020142200 A1 WO 2020142200A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
network
data rate
rate
logging device
Prior art date
Application number
PCT/US2019/066795
Other languages
English (en)
Inventor
John A. SALVATORE
Original Assignee
Exxonmobil Research And Engineering Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Exxonmobil Research And Engineering Company filed Critical Exxonmobil Research And Engineering Company
Publication of WO2020142200A1 publication Critical patent/WO2020142200A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/407—Bus networks with decentralised control
    • H04L12/417—Bus networks with decentralised control with deterministic access, e.g. token passing
    • 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

Definitions

  • U.S. Patent Publication 2005/0094570 (‘570 Publication) describes a method for automatic detection of the network data rate and for configuration at the detected data rate by a device connected to the network. This method includes an initialization phase and an interactive processing phase. The invention is particularly but not exclusively applicable to Controlled Area Networks (CAN) bus type networks.
  • CAN Controlled Area Networks
  • CAN bus typically uses a protocol with the same name (CAN protocol) that is a serial communication protocol.
  • the CAN protocol covers two of the seven layers of the ISO's open systems interconnection (OSI) model, namely the physical layer (layer 1) and the data link layer (layer 2).
  • OSI open systems interconnection
  • layer 1 the physical layer
  • layer 2 the data link layer
  • the clock frequency of the CAN controller (for example, 12 MHz) can vary from network to network.
  • U.S. Patent Publication 2005/0251701 describes a system that automatically detects the baud rate of a CAN network.“Thus, for example, a well-known problem in CAN systems is that a module unit with incorrectly set bit speed can corrupt all communications. The solution to this has been to introduce a silent mode, that is, a node that is connected and just listens to the traffic and does not transmit any signals until it has received a correct message.”
  • aspects of the technology described herein describe a system for data logging that can receive data from CANs having different data transfer rates and protocols without prior knowledge of those features.
  • the data logging system can receive data from multiple CANs without knowing the type of data provided by an individual CAN.
  • Aspects of the technology described herein first determine the data transfer rate on each CAN and then determine the protocol. The system then follows the protocol to request data, if required by the protocol, and sets up the CAN interface to receive the data at the determined data transfer rate.
  • Some protocols require that requests for specific information be made of the CAN bus in order to receive data. Other system protocols simply broadcast data records. A challenge with protocols that require requests is to know what requests to make. For example, one CAN bus may connect the exhaust system and transmission, while another connects to the tire pressure, wiper fluid, and oil pressure. Different manufactures may combine systems in different ways on different vehicles. It is very challenging to know what systems are on what CAN in any given vehicle. Aspects of the technology described herein send all available requests for a vehicle to each CAN bus and then record whatever responses are received.
  • FIG. 1 is a diagram showing CANs in a vehicle, according to an aspect of the technology described herein;
  • FIG. 2 is a diagram showing a connector plug, according to an aspect of the technology described herein;
  • FIG. 3 is a diagram showing an operating environment for a data logger, according to an aspect of the technology described herein;
  • FIG. 4 is a flow chart showing a method of logging data from an unknown CAN, according to an aspect of the technology described herein;
  • FIG. 5 is a flow chart showing a method of logging data from an unknown CAN, according to an aspect of the technology described herein;
  • FIG. 6 is a flow chart showing a method of logging data from an unknown CAN, according to an aspect of the technology described herein;
  • FIG. 7 is a diagram showing a computing system environment suitable for use with aspects of the technology described herein.
  • aspects of the technology described herein describe a system for data logging that can receive data from CANs having different data transfer rates and protocols without prior knowledge of those features.
  • the data logging system can receive data from multiple CANs without knowing the type of data provided by an individual CAN.
  • Aspects of the technology described herein first determine the data transfer rate on each CAN bus and then the protocol. The system then follows the protocol to request data, if required by the protocol, and sets up the CAN interface to receive the data at the determined data transfer rate.
  • Some protocols require that requests for specific information be made of the CAN bus in order to receive data. Other system protocols simply broadcast data records. A challenge with protocols that require requests is to know what requests to make. For example, one CAN bus may connect the exhaust system and transmission, while another connects to the tire pressure, wiper fluid, and oil pressure. Different manufactures may combine systems in different ways on different vehicles. It is very challenging to know what systems are on what CAN in any given vehicle. Aspects of the technology described herein send all available requests for a vehicle to each CAN bus and then record whatever responses are received.
  • the vehicle 101 is depicted as a car, however, implementations of the technology described herein are not limited to cars.
  • the vehicle 101 could be a car, truck, van, farm equipment (e.g., tractor, combine), construction equipment (e.g., dump truck, excavator, bulldozer), bus, or train.
  • the vehicle 101 has a first CAN 110, a second CAN 112, and a third CAN 114.
  • Each CAN may connect different vehicle components, which can be described as nodes.
  • Each CAN may connect through a port 118 to a vehicle data logging device 120.
  • Each CAN may have different characteristics, such as data transfer and communication protocol.
  • the vehicle 101 may be a truck, car, bus, van, or the like. In one aspect, the vehicle 101 is a fleet vehicle, such as a delivery truck.
  • a CAN (Controller Area Network) Network is a connection of microcontrollers within a vehicle arranged per a CAN bus protocol.
  • the microcontrollers are often electronic control units (ECUs) for various vehicle subsystems.
  • ECUs electronice control units
  • the physical architecture of a CAN Network connects each node along two wires, known as a network bus.
  • the CAN bus protocol is a network protocol.
  • the CAN bus protocol is a robust vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer. It is a message-based protocol.
  • the CAN bus protocol can comprise an Application Layer, Object Layer, Transfer Layer, and Physical Layer. Different CAN bus protocols exist. Each of these layers may be governed by different protocols.
  • a data transfer rate of a CAN is the amount of data transferred per unit of time.
  • the data transfer rate may be measured and expressed as a bit rate or a baud rate.
  • FIG. 2 shows a vehicle connector port 200. Aspects of the technology are not limited to implementations on the vehicle connector port 200 shown.
  • the vehicle connector port 200 is consistent with the SAE J1962 OBD-2 standard, where OBD stands for on-board diagnostic.
  • the S AE J 1962 specification provides for two standardized hardware interfaces, called type A and type B. Both are female, 16-pin (2x8), D-shaped connectors, and both have a groove between the two rows of pins, but type B's groove is interrupted in the middle. This prevents the insertion of a type A male plug into a type B female socket while allowing a type B male plug to be inserted into a type A female socket.
  • the type A connector is used for vehicles that use 12V supply voltage, whereas type B is used for 24V.
  • the vehicle connector port 200 has 16 different pins.
  • the pins in the vehicle connector port 200 include a first pin 201, a second pin 202, a third pin 203, a fourth pin 204, a fifth pin 205, a sixth pin 206, a seventh pin 207, an eighth pin 208, a ninth pin 209, a tenth pin 210, an eleventh pin 211, a twelfth pin 212, a thirteenth pin 213, a fourteenth pin 214, a fifteenth pin 215, and a sixteenth pin 216.
  • the pins and pin combinations may serve different purposes in different vehicles.
  • the fourth pin 204 is a chassis ground
  • the fifth pin 205 is a signal ground.
  • the sixteenth pin 216 can connect to a battery and provide power to the logging device.
  • Pin combinations can form communication channels to a CAN bus.
  • the third pin 203 and the eleventh pin 211 may combine to form a communication channel for a first CAN bus
  • the twelfth pin 212 and thirteenth pin 213 may combine to form a communication channel for a second CAN bus
  • the sixth pin 206 and the fourteenth pin 214 may combine to form a communication channel to a third CAN bus.
  • the details of the given CAN are not known, but the pins and pin combinations available as channels to a CAN bus are known. Each possible combination may be investigated by the technology described herein.
  • vehicle data logging system 300 in which some embodiments of the present disclosure may be employed.
  • the components of vehicle data logging system 300 may be embodied as a set of compiled computer instructions or functions, program modules, computer software services, or an arrangement of processes carried out on one or more computer systems, such as computing device 700 described in connection to FIG. 7, for example.
  • the functions performed by components of vehicle data logging system 300 are associated with one or more applications, services, or routines. These components, functions performed by these components, or services carried out by these components may be implemented at appropriate abstraction layer(s) such as the operating system layer, application layer, hardware layer, etc., of the computing system(s). Alternatively, or in addition, the functionality of these components and/or the embodiments of the disclosure described herein can be performed, at least in part, by one or more hardware logic components.
  • illustrative types of hardware logic components include Field- programmable Gate Arrays (FPGAs), Application-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
  • FPGAs Field- programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • the vehicle data logging system 300 generally operates to retrieve and store information from vehicle CAN networks.
  • each component of the vehicle data logging system 300 may reside on a computing device (or devices).
  • the components of the data logging system 300 may reside on the exemplary computing device 700 described below and shown in FIG. 7, or similar devices.
  • each component of the vehicle data logging system 300 may be implemented using one or more of a memory, a processor or processors, presentation components, input/output (I/O) ports and/or components, radio(s) and a power supply (e.g., as represented by reference numerals 712-724, respectively, in FIG. 7).
  • the vehicle data logging system 300 comprises a data logger 320 coupled to a vehicle 310. More specifically, the data port 322 on the data logger 320 is coupled to the vehicle port 318 on the vehicle 310. The data port 322 and the vehicle port 318 may be connected through a connector with an arrangement similar to the vehicle connector port 200 described previously with reference to FIG. 2.
  • the vehicle 310 includes a first CAN 312, a second CAN 314, and a third CAN 316.
  • Each of the three CANs may connect different microcontrollers that run different systems within the vehicle 310.
  • Each CAN may have a different data transfer rate and/or communication protocol. Initially, both the data transfer rate and the communication protocol are unknown to the data logger 320.
  • the data port 322 connects each of the CANs in the vehicle to a CAN interface.
  • the first CAN interface 330 comprises a data rate detector 331, a protocol detector 332, and a request manager 333.
  • the data rate detector 331 determines the data rate for the first CAN 312.
  • the protocol detector 332 determines the protocol used by the first CAN 312. Once the data rate has been determined along with the communication protocol, then requests for information may be communicated when required.
  • the request manager 333 sends the first CAN 312 request messages formatted according to the required protocol. In one aspect, requests for every type of information possibly available on a CAN are communicated. Requests for information not available on the first CAN 312 may result in error messages. Requests for information that are available on the first CAN 312 will result in replies with the requested data.
  • the replies 335 can be stored in the CAN storage 334.
  • the data rate detector 331 can employ one of several different techniques to determine the data transfer rate for a given CAN.
  • messages are interactively sent at different rates until a confirmation message is received in response. If the wrong rate is used, then an error message or perhaps no message will be returned in response.
  • Standard data transfer rates are 125 kbit/s, 250 kbit/s, 500 kbit/s, and 1 Mbit/s. These and other common rates could be tried before attempting less common rates.
  • Each CAN in a car may have different data rates.
  • traffic on the CAN is retrieved, and one or more characteristics of the traffic is compared to a table of characteristics at different rates. The rate in the table that matches the characteristics of the observed traffic is selected.
  • the protocol detector 332 can detect a communication protocol a number of different ways. In general, communication protocols fall into two main categories. The first category requires information requests for data. The second category broadcasts data without requests. The second category can be detected by listening. If data is received, it can be compared to different protocols, or simply stored. Detecting messages can comprise determining a protocol. If no messages are received, then the protocol is likely in the first category. Protocols within the first category can be determined by outputting a series of requests within a category. When an affirmative response is received then the communication protocol has been determined.
  • the second CAN interface 340 comprises a data rate detector 341, a protocol detector 342, and a request manager 343.
  • the data rate detector 341 determines the data rate for the second CAN 314.
  • the protocol detector 342 determines the protocol used by the second CAN 314. Once the data rate has been determined along with the communication protocol, then requests for information may be communicated when required.
  • the request manager 343 sends the second CAN 314 request messages formatted according to the required protocol. In one aspect, requests for every type of information possibly available on a CAN are communicated. Requests for information not available on the second CAN 314 may result in error messages. Requests for information that are available on the second CAN 314 will result in replies with the requested data.
  • the replies 335 can be stored in the CAN storage 334.
  • the third CAN interface 350 comprises a data rate detector 351, a protocol detector 352, and a request manager 353.
  • the data rate detector 351 determines the data rate for the third CAN 316.
  • the protocol detector 352 determines the protocol used by the third CAN 316. Once the data rate has been determined along with the communication protocol, then requests for information may be communicated when required.
  • the request manager 353 sends the third CAN 316 request messages formatted according to the required protocol. In one aspect, requests for every type of information possibly available on a CAN are communicated. Requests for information not available on the third CAN 316 may result in error messages. Requests for information that are available on the third CAN 316 will result in replies with the requested data.
  • the replies 335 can be stored in the CAN storage 334.
  • a method 400 of logging vehicle data is provided.
  • the first, second, and third signal data may all be received simultaneously from the vehicle through a single port.
  • the port may be similar in format to the connector described with reference to FIG. 2.
  • a first data rate for the first CAN network is determined at the data logging device.
  • the data rate may be calculating according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the first CAN prior to receiving the first signal data.
  • a first CAN interface that processes the first signal data on the data logging device is reset to process data communicated at the first data rate.
  • the first signal data is recorded at the first data rate on the data logging device.
  • a second data rate for the second CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the second CAN prior to receiving the second signal data.
  • a second CAN interface that processes the second signal data on the data logging device is reset to process data communicated at the second data rate.
  • the second signal data is recorded on the data logging device at the second data rate.
  • a third data rate for the third CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the third CAN prior to receiving the third signal data.
  • the first data rate, the second data rate, and the third data rate can all be different. In other aspects, two of the three are the same or all three are the same.
  • a third CAN interface that processes the third signal data on the data logging device is reset to process data communicated at the third data rate.
  • the third signal data is recorded at the data logging device at the third data rate.
  • the first signal data is recorded in the same file as the first and second signal data.
  • a method 500 of logging vehicle data is provided.
  • the first, second, and third signal data may all be received simultaneously from the vehicle through a single port.
  • the port may be similar in format to the connector described with reference to FIG. 2.
  • a first data rate for the first CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the first CAN prior to receiving the first signal data.
  • a first CAN interface that processes the first signal data on the data logging device is reset to process data communicated at the first data rate.
  • the first signal data is recorded at the first data rate on the data logging device.
  • a second data rate for the second CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the second CAN prior to receiving the second signal data.
  • a second CAN interface that processes the second signal data on the data logging device is reset to process data communicated at the second data rate.
  • the second signal data is recorded on the data logging device at the second data rate.
  • a third data rate for the third CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the third CAN prior to receiving the third signal data.
  • the first data rate, the second data rate, and the third data rate can all be different. In other aspects, two of the three are the same or all three are the same.
  • a third CAN interface that processes the third signal data on the data logging device is reset to process data communicated at the third data rate.
  • the third signal data is recorded at the data logging device at the third data rate.
  • the first signal data is recorded in the same file as the first and second signal data.
  • a first communication protocol for the first CAN network is determined.
  • the first communication protocol provides logged vehicle data in response to a request. Without a request, the vehicle data will not be provided.
  • the request needs to conform to the first communication protocol.
  • the request also needs to request a specific item of information, such as coolant temperature.
  • Communication protocols may be determined for the second and third CAN networks. Each CAN network may have a different protocol.
  • all available requests for information known to be compatible with the first communication protocol are communicated to the first CAN network. The requests that do not match available data will be ignored or produce an error message. The requests that match available data will receive the requested data set in response, which will then be saved.
  • a method 600 of logging vehicle data is provided.
  • the first, second, and third signal data may all be received simultaneously from the vehicle through a single port.
  • the port may be similar in format to the connector described with reference to FIG. 2.
  • a first data rate for the first CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the first CAN prior to receiving the first signal data.
  • a first CAN interface that processes the first signal data on the data logging device is reset to process data communicated at the first data rate.
  • the first signal data is recorded at the first data rate on the data logging device in a single file.
  • a second data rate for the second CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the second CAN prior to receiving the second signal data.
  • a second CAN interface that processes the second signal data on the data logging device is reset to process data communicated at the second data rate.
  • the second signal data is recorded on the data logging device at the second data rate in the single file.
  • a third data rate for the third CAN network is determined at the data logging device.
  • the data rate may be calculated according to a method described previously with reference to FIG. 3.
  • the data logging device does not know the data rate of the third CAN prior to receiving the third signal data.
  • the first data rate, the second data rate, and the third data rate can all be different. In other aspects, two of the three are the same or all three are the same.
  • a third CAN interface that processes the third signal data on the data logging device is reset to process data communicated at the third data rate.
  • the third signal data is recorded at the data logging device at the third data rate in the single file.
  • a first communication protocol for the first CAN network is determined.
  • the first communication protocol provides logged vehicle data in response to a request. Without a request, the vehicle data will not be provided.
  • the request needs to conform to the first communication protocol.
  • the request also needs to request a specific item of information, such as coolant temperature.
  • Communication protocols may be determined for the second and third CAN networks. Each CAN network may have a different protocol.
  • step 695 all available requests for information known to be compatible with the first communication protocol are communicated to the first CAN network.
  • the requests that do not match available data will be ignored or produce an error message.
  • the requests that match available data will receive the requested data set in response, which will then be saved.
  • computing device 700 an exemplary operating environment for implementing aspects of the technology described herein is shown and designated generally as computing device 700.
  • Computing device 700 is but one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use of the technology described herein. Neither should the computing device 700 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated.
  • the technology described herein may be described in the general context of computer code or machine-useable instructions, including computer-executable instructions such as program components, being executed by a computer or other machine, such as a personal data assistant or other handheld device.
  • program components including routines, programs, objects, components, data structures, and the like, refer to code that performs particular tasks or implements particular abstract data types.
  • the technology described herein may be practiced in a variety of system configurations, including handheld devices, consumer electronics, general-purpose computers, specialty computing devices, etc. Aspects of the technology described herein may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • computing device 700 includes a bus 710 that directly or indirectly couples the following devices: memory 712, one or more processors 714, one or more presentation components 716, input/output (I/O) ports 718, EO components 720, and an illustrative power supply 722.
  • Bus 710 represents what may be one or more busses (such as an address bus, data bus, or a combination thereof).
  • I/O input/output
  • EO components 720 illustrative power supply 722.
  • Bus 710 represents what may be one or more busses (such as an address bus, data bus, or a combination thereof).
  • FIG. 7 is merely illustrative of an exemplary computing device that can be used in connection with one or more aspects of the technology described herein. Distinction is not made between such categories as“workstation,”“server,”“laptop,”“handheld device,” etc., as all are contemplated within the scope of FIG. 7 and refer to“computer” or“computing device.”
  • Computing device 700 typically includes a variety of computer-readable media.
  • Computer-readable media can be any available media that can be accessed by computing device 700 and includes both volatile and nonvolatile, removable and non-removable media.
  • Computer-readable media may comprise computer storage media and communication media.
  • Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
  • Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Computer storage media does not comprise a propagated data signal.
  • Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
  • modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.
  • Memory 712 includes computer storage media in the form of volatile and/or nonvolatile memory.
  • the memory 712 may be removable, non-removable, or a combination thereof.
  • Exemplary memory includes solid-state memory, hard drives, optical-disc drives, etc.
  • Computing device 700 includes one or more processors 714 that read data from various entities such as bus 710, memory 712, or EO components 720.
  • Presentation component(s) 716 present data indications to a user or other device.
  • Exemplary presentation components 716 include a display device, speaker, printing component, vibrating component, etc.
  • I/O ports 718 allow computing device 700 to be logically coupled to other devices, including I/O components 720, some of which may be built in.
  • Illustrative I/O components include a microphone, joystick, game pad, satellite dish, scanner, printer, display device, wireless device, a controller (such as a stylus, a keyboard, and a mouse), a natural user interface (NUI), and the like.
  • a pen digitizer (not shown) and accompanying input instrument (also not shown but which may include, by way of example only, a pen or a stylus) are provided in order to digitally capture freehand user input.
  • the connection between the pen digitizer and processor(s) 714 may be direct or via a coupling utilizing a serial port, parallel port, and/or other interface and/or system bus known in the art.
  • the digitizer input component may be a component separated from an output component such as a display device, or in some aspects, the useable input area of a digitizer may coexist with the display area of a display device, be integrated with the display device, or may exist as a separate device overlaying or otherwise appended to a display device. Any and all such variations, and any combination thereof, are contemplated to be within the scope of aspects of the technology described herein.
  • An NUI processes air gestures, voice, or other physiological inputs generated by a user. Appropriate NUI inputs may be interpreted as ink strokes for presentation in association with the computing device 700. These requests may be transmitted to the appropriate network element for further processing.
  • An NUI implements any combination of speech recognition, touch and stylus recognition, facial recognition, biometric recognition, gesture recognition both on screen and adjacent to the screen, air gestures, head and eye tracking, and touch recognition associated with displays on the computing device 700.
  • the computing device 700 may be equipped with camera systems 726.
  • the camera system 726 can include depth cameras, such as stereoscopic camera systems, infrared camera systems, RGB camera systems, structured light camera systems, TOF camera systems, and combinations of these, for generating depth images.
  • the depth images can be used in gesture detection and recognition, displayed to a user, or used to generate augmented reality, virtual reality, or other imagery.
  • the computing device 700 may be equipped with accelerometers or gyroscopes that enable detection of motion.
  • the output of the accelerometers or gyroscopes may be provided to the display of the computing device 700 to render immersive augmented reality or virtual reality.
  • a computing device may include a radio 724.
  • the radio 724 transmits and receives radio communications.
  • the computing device may be a wireless terminal adapted to receive communications and media over various wireless networks.
  • Computing device 700 may communicate via wireless protocols, such as code division multiple access (“CDMA”), global system for mobiles (“GSM”), or time division multiple access (“TDMA”), as well as others, to communicate with other devices.
  • CDMA code division multiple access
  • GSM global system for mobiles
  • TDMA time division multiple access
  • the radio communications may be a short-range connection, a long-range connection, or a combination of both a short-range and a long-range wireless telecommunications connection.
  • a short-range connection may include a Wi-Fi® connection to a device (e.g., mobile hotspot) that provides access to a wireless communications network, such as a WLAN connection using the 802.11 protocol.
  • a Bluetooth connection to another computing device is a second example of a short-range connection.
  • a long-range connection may include a connection using one or more of CDMA, GPRS, GSM, TDMA, and 802.16 protocols.
  • Embodiment 1 A method for logging vehicle data, the method comprising: receiving, at a data logging device, a first signal data from a first CAN network on a vehicle, a second signal data from a second CAN network on the vehicle, and a third signal data from a third CAN network on the vehicle; determining, at the data logging device, a first data rate for the first CAN network; resetting a first CAN interface that processes the first signal data on the data logging device to process data communicated at the first data rate; recording, at the data logging device, the first signal data at the first data rate; determining a second data rate for the second CAN network; resetting a second CAN interface that processes the second signal data on the data logging device to process data communicated at the second data rate; recording, at the data logging device, the second signal data at the second data rate; determining a third data rate for the third CAN network; resetting a third CAN interface that processes the third signal data on the data logging device
  • Embodiment 2 The method of embodiment 1, wherein the first signal data, the second signal data, and the third signal data are recorded in a single file.
  • Embodiment 3 The method as in any one of the above embodiments, wherein the first signal data, the second signal data, and the third signal data are received simultaneously.
  • Embodiment 4 The method as in any one of the above embodiments, wherein the first data rate and the second data rate are different.
  • Embodiment 5. The method as in any one of the above embodiments, wherein the data logging device did not know the first data rate for the first CAN network, the second data rate for the second CAN network, or the third data rate for the third CAN network before determining the first data rate, the second data rate, and the third data rate.
  • Embodiment 6 The method as in any one of the above embodiments, further comprising determining a first communication protocol for the first CAN network, wherein the first communication protocol only provides logged vehicle data in response to a request.
  • Embodiment 7 The method of embodiment 6, further comprising communicating all available requests for information known to be compatible with the first communication protocol to the first CAN network, wherein the data logging device does not know what information is available on the first CAN network.
  • Embodiment 8 A method for logging vehicle data, the method comprising: receiving, at a data logging device, a first signal data from a first CAN network on a vehicle, a second signal data from a second CAN network on the vehicle, and a third signal data from a third CAN network on the vehicle; determining, at the data logging device, a first data rate for the first CAN network; resetting a first CAN interface that processes the first signal data on the data logging device to process data communicated at the first data rate; recording, at the data logging device, the first signal data at the first data rate; determining a second data rate for the second CAN network; resetting a second CAN interface that processes the second signal data on the data logging device to process data communicated at the second data rate; recording, at the data logging device, the second signal data at the second data rate; determining a third data rate for the third CAN network; resetting a third CAN interface that processes the third signal data on the data logging device
  • Embodiment 9 The method of embodiment 8, wherein the data logging device does not know what information is available on the first CAN network.
  • Embodiment 10 The method as in any one of embodiments 8 and 9, wherein the first signal data, the second signal data, and the third signal data are recorded in a single file.
  • Embodiment 11 The method as in any one of embodiments 8, 9 and 10, wherein the first data rate, the second data rate, and the third data rate are different.
  • Embodiment 12 The method as in any one of embodiments 8, 9, 10 and 11, wherein the first signal data, the second signal data, and the third signal data are received simultaneously.
  • Embodiment 13 The method as in any one of embodiments 8, 9, 10, 11 and 12, wherein the data logging device did not know the first data rate for the first CAN network, the second data rate for the second CAN network, or the third data rate for the third CAN network before determining the first data rate, the second data rate, and the third data rate.
  • Embodiment 14 A method for logging vehicle data, the method comprising: simultaneously receiving, at a data logging device, a first signal data from a first CAN network on a vehicle, a second signal data from a second CAN network on the vehicle, and a third signal data from a third CAN network on the vehicle; determining, at the data logging device, a first data rate for the first CAN network; resetting a first CAN interface that processes the first signal data on the data logging device to process data communicated at the first data rate; recording, at the data logging device, the first signal data at the first data rate in a single file; determining a second data rate for the second CAN network; resetting a second CAN interface that processes the second signal data on the data logging device to process data communicated at the second data rate; recording, at the data logging device, the second signal data at the second data rate in the single file; determining a third data rate for the third CAN network; resetting a third CAN interface that processes
  • Embodiment 15 The method of embodiment 14, wherein the data logging device does not know what information is available on the first CAN network.
  • Embodiment 16 The method as in any one of embodiments 14 and 15, wherein the first data rate and the second data rate are different.
  • Embodiment 17 The method as in any one of embodiments 14, 15 and 16, wherein the data logging device did not know the first data rate for the first CAN network, the second data rate for the second CAN network, or the third data rate for the third CAN network before determining the first data rate, the second data rate, and the third data rate.
  • Embodiment 18 The method as in any one of embodiments 14, 15, 16 and 17, wherein the first signal data, the second signal data, and the third signal data are received from the same port.
  • Embodiment 19 The method as in any one of embodiments 14, 15, 16, 17 and 18, further comprising wirelessly transferring the single file to a different computing device.
  • Embodiment 20 The method as in any one of embodiments 14, 15, 16, 17, 18 and 19, wherein the vehicle is a commercial vehicle.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

La présente invention concerne, selon certains aspects, un système de consignation de données qui peut recevoir des données de CAN de véhicules ayant différents débits et protocoles de transfert de données sans connaissance préalable de ces caractéristiques. Le système de consignation de données peut recevoir des données issues de multiples CAN sans connaître le type de données fournies par un CAN individuel. Des aspects de la présente invention déterminent le débit de transfert de données sur le CAN et ensuite le protocole. Le système suit ensuite le protocole pour demander des données, si elles sont requises par le protocole, et configure l'interface CAN pour recevoir les données au débit de transfert de données déterminé. Il est très difficile de savoir quels systèmes se trouvent sur quel CAN dans un véhicule donné. Des aspects de la présente invention consistent à envoyer toutes les requêtes disponibles concernant un véhicule à chaque bus CAN, puis à enregistrer les réponses qui sont reçues.
PCT/US2019/066795 2019-01-02 2019-12-17 Dispositif de consignation de données de plusieurs véhicules WO2020142200A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962787567P 2019-01-02 2019-01-02
US62/787,567 2019-01-02

Publications (1)

Publication Number Publication Date
WO2020142200A1 true WO2020142200A1 (fr) 2020-07-09

Family

ID=69173445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/066795 WO2020142200A1 (fr) 2019-01-02 2019-12-17 Dispositif de consignation de données de plusieurs véhicules

Country Status (1)

Country Link
WO (1) WO2020142200A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4102778A1 (fr) * 2021-06-07 2022-12-14 Robert Bosch GmbH Dispositif émetteur-récepteur pour une station d'abonnés d'un système de bus série et procédé de communication dans un système de bus série

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050094570A1 (en) 2003-09-17 2005-05-05 Atmel Nantes Sa Method for automatic detection of the data rate in a network, particularly a CAN bus type network, and for configuration to the detected data rate, corresponding device
US20050251701A1 (en) 2002-01-07 2005-11-10 Lars-Berno Fredriksson Distributed control and monitoring system
WO2008127243A1 (fr) * 2007-04-16 2008-10-23 Robert Bosch Gmbh Enregistrement chronologique de données diagnostiques mises en réseau par plusieurs sources
US20120233341A1 (en) * 2011-03-07 2012-09-13 Microchip Technology Incorporated Microcontroller with can bus module and auto speed detect
WO2013084205A1 (fr) * 2011-12-07 2013-06-13 Texa S.P.A. Enregistreur de données automobiles à auto-apprentissage identifiant des messages automobiles transmis sur un bus can reliant des unités de commande électronique automobiles

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050251701A1 (en) 2002-01-07 2005-11-10 Lars-Berno Fredriksson Distributed control and monitoring system
US20050094570A1 (en) 2003-09-17 2005-05-05 Atmel Nantes Sa Method for automatic detection of the data rate in a network, particularly a CAN bus type network, and for configuration to the detected data rate, corresponding device
WO2008127243A1 (fr) * 2007-04-16 2008-10-23 Robert Bosch Gmbh Enregistrement chronologique de données diagnostiques mises en réseau par plusieurs sources
US20120233341A1 (en) * 2011-03-07 2012-09-13 Microchip Technology Incorporated Microcontroller with can bus module and auto speed detect
WO2013084205A1 (fr) * 2011-12-07 2013-06-13 Texa S.P.A. Enregistreur de données automobiles à auto-apprentissage identifiant des messages automobiles transmis sur un bus can reliant des unités de commande électronique automobiles

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4102778A1 (fr) * 2021-06-07 2022-12-14 Robert Bosch GmbH Dispositif émetteur-récepteur pour une station d'abonnés d'un système de bus série et procédé de communication dans un système de bus série

Similar Documents

Publication Publication Date Title
US10997091B2 (en) Intelligent Bluetooth® beacon I/O expansion system
US9122621B2 (en) Configurable intelligent I/O expander system
JP7025276B2 (ja) 路面標示を用いた都市環境における位置特定
CN209842367U (zh) 一种基于自动驾驶系统的网络架构的集散式域控制器系统
CN104994601A (zh) 一种4g车载智慧终端系统
CN202939460U (zh) 车载数据采集终端及车辆信息采集系统
JP6549579B2 (ja) 大容量記憶装置ベースのインタフェースを通じてｍ−ｐｈｙベースの通信を運用すること、ならびに関連するコネクタ、システム、および方法
CN111124443A (zh) 车辆、车机设备及车载仪表升级方法
WO2020142200A1 (fr) Dispositif de consignation de données de plusieurs véhicules
CN211656247U (zh) 多传感器数据同步系统
US11817968B1 (en) Methods and devices for routing controller area network traffic over a universal serial bus connection
CN114511945B (zh) 单机行车记录仪行车轨迹生成方法、装置、设备及介质
EP4297305A1 (fr) Procédé, appareil, et système de transmission de données
WO2024026592A1 (fr) Procédé de stockage de données et appareil associé
CN105704660A (zh) 一种车联网终端
CN114637275A (zh) 车辆远程诊断方法、装置、电子设备及存储介质
CN118042108A (zh) 控制器测试方法、装置、存储介质及电子装置
Jung et al. Implementation of Automotive Platform for Real-Time Diagnosis

Legal Events

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

Ref document number: 19839045

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19839045

Country of ref document: EP

Kind code of ref document: A1