WO2012158888A2 - Système et procédé permettant une collecte de données d'enquête dans le domaine des pneus - Google Patents

Système et procédé permettant une collecte de données d'enquête dans le domaine des pneus Download PDF

Info

Publication number
WO2012158888A2
WO2012158888A2 PCT/US2012/038306 US2012038306W WO2012158888A2 WO 2012158888 A2 WO2012158888 A2 WO 2012158888A2 US 2012038306 W US2012038306 W US 2012038306W WO 2012158888 A2 WO2012158888 A2 WO 2012158888A2
Authority
WO
WIPO (PCT)
Prior art keywords
tire
data
program instructions
computer
tires
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.)
Ceased
Application number
PCT/US2012/038306
Other languages
English (en)
Other versions
WO2012158888A3 (fr
Inventor
Joseph Gomez
Daisuke Tamura
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bridgestone Americas Tire Operations LLC
Original Assignee
Bridgestone Americas Tire Operations LLC
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 Bridgestone Americas Tire Operations LLC filed Critical Bridgestone Americas Tire Operations LLC
Publication of WO2012158888A2 publication Critical patent/WO2012158888A2/fr
Publication of WO2012158888A3 publication Critical patent/WO2012158888A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60C—VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES
    • B60C11/00—Tyre tread bands; Tread patterns; Anti-skid inserts
    • B60C11/24—Wear-indicating arrangements
    • B60C11/246—Tread wear monitoring systems

Definitions

  • the present disclosure relates to the field of data collection. More particularly, the present disclosure relates to the field of tire field survey data collection.
  • Tires of a vehicle may be an important factor in the performance and reliability of the vehicle.
  • improving the design of the tires may be desirable in order to improve the performance and reliability of the tires, and in turn the performance and reliability of the vehicle.
  • real world field conditions of the tires may be an important factor in the tire development and improvement process.
  • Field testing of the tires, including data collection, is one aspect of the tire development and improvement process that takes into account real world field conditions.
  • a computer receives data representative of a selected tire test template.
  • the tire test template includes data representative of at least one test field.
  • the computer receives data representative of a selected vehicle, including data representative of a plurality of tires on the selected vehicle.
  • the computer displays, on a graphical display, data representative of the plurality of tires on the selected vehicle, including data representative of the physical location of the plurality of tires on the selected vehicle.
  • the computer displays, on a graphical display, a data entry form corresponding to a selected tire of the plurality of tires.
  • the data entry form includes at least one data entry field corresponding to the at least one test field of the selected tire test template.
  • the computer receives tire inspection data corresponding to at least one tire of the plurality of tires, wherein the tire inspection data corresponds to the at least one data entry field.
  • a system for collecting tire field survey data includes at least one processor, at least one computer-readable tangible storage device, and program instructions stored on the at least one storage device for execution by the at least one processor.
  • the program instructions include first program instructions configured to receive data representative of a selected tire test template, the tire test template including data representative of at least one test field.
  • the program instructions further include second program instructions configured to receive data representative of a selected vehicle, including data representative of a plurality of tires on the selected vehicle.
  • the program instructions further include third program instructions configured to display, on a graphical display, data representative of the plurality of tires on the selected vehicle, including data representative of the physical location of the plurality of tires on the selected vehicle.
  • the program instructions further include fourth program instructions configured to display, on a graphical display, a data entry form corresponding to a selected tire of the plurality of tires, the data entry form including at least one data entry field corresponding to the at least one test field of the selected tire test template.
  • the program instructions further include fifth program instructions configured to receive tire inspection data corresponding to at least one tire of the plurality of tires, wherein the tire inspection data corresponds to the at least one data entry field.
  • a computer program product collecting tire field survey data includes at least one computer-readable tangible storage device and program instructions stored on the at least one storage device.
  • the program instructions include first program instructions configured to receive data representative of a selected tire test template, the tire test template including data representative of at least one test field.
  • the program instructions further include second program instructions configured to receive data representative of a selected vehicle, including data representative of a plurality of tires on the selected vehicle.
  • the program instructions further include third program instructions configured to display, on a graphical display, data representative of the plurality of tires on the selected vehicle, including data representative of the physical location of the plurality of tires on the selected vehicle.
  • the program instructions further include fourth program instructions configured to display, on a graphical display, a data entry form corresponding to a selected tire of the plurality of tires, the data entry form including at least one data entry field corresponding to the at least one test field of the selected tire test template.
  • the program instructions further include fifth program instructions configured to receive tire inspection data corresponding to at least one tire of the plurality of tires, wherein the tire inspection data corresponds to the at least one data entry field.
  • Fig. 1 illustrates an example system for collecting tire field survey data.
  • Fig. 2 illustrates a block diagram of an example tire field survey data collection system.
  • FIG. 3 illustrates a flow chart of an example method for collecting tire field survey data.
  • FIG. 4 is a schematic diagram illustrating an example computer for implementing the system and method of Figs. 2 and 3.
  • a computer component refers to a computer- related entity, either hardware, firmware, software, a combination thereof, or software in execution.
  • a computer component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer.
  • an application running on a server and the server can be computer components.
  • One or more computer components can reside within a process or thread of execution and a computer component can be localized on one computer or distributed between two or more computers.
  • Computer communication refers to a communication between two or more computing devices (e.g., computer, personal digital assistant, cellular telephone) and can be, for example, a network transfer, a file transfer, an applet transfer, an email, a hypertext transfer protocol (HTTP) transfer, and so on.
  • a computer communication can occur across, for example, a wireless system (e.g., IEEE 802.11, IEEE 802.15), an Ethernet system (e.g., IEEE 802.3), a token ring system (e.g., IEEE 802.5), a local area network (LAN), a wide area network (WAN), a point-to-point system, a circuit switching system, a packet switching system, combinations thereof, and so on.
  • a wireless system e.g., IEEE 802.11, IEEE 802.15
  • Ethernet system e.g., IEEE 802.3
  • a token ring system e.g., IEEE 802.5
  • LAN local area network
  • WAN wide area network
  • point-to-point system e.g., IEEE
  • Computer-readable medium refers to a medium that participates in directly or indirectly providing signals, instructions or data.
  • a computer-readable medium may take forms, including, but not limited to, nonvolatile media, volatile media, and transmission media.
  • Non-volatile media may include, for example, optical or magnetic disks, and so on.
  • Volatile media may include, for example, optical or magnetic disks, dynamic memory and the like.
  • Transmission media may include coaxial cables, copper wire, fiber optic cables, and the like. Transmission media can also take the form of electromagnetic radiation, like that generated during radio-wave and infra-red data communications, or take the form of one or more groups of signals.
  • a computer-readable medium include, but are not limited to, a floppy disk, a flexible disk, a hard disk, a magnetic tape, other magnetic media, a CDROM, other optical media, punch cards, paper tape, other physical media with patterns of holes, a RAM, a ROM, an EPROM, a FLASH-EPROM, or other memory chip or card, a memory stick, a carrier wave/pulse, and other media from which a computer, a processor or other electronic device can read.
  • Signals used to propagate instructions or other software over a network like the Internet, can be considered a "computer-readable medium.”
  • Data store refers to a physical or logical entity that can store data.
  • a data store may be, for example, a database, a table, a file, a list, a queue, a heap, a memory, a register, and so on.
  • a data store may reside in one logical or physical entity or may be distributed between two or more logical or physical entities.
  • logic includes but is not limited to hardware, firmware, software or combinations of each to perform a function(s) or an action(s), or to cause a function or action from another logic, method, or system.
  • logic may include a software controlled microprocessor, discrete logic like an application specific integrated circuit (ASIC), a programmed logic device, a memory device containing instructions, or the like.
  • ASIC application specific integrated circuit
  • Logic may include one or more gates, combinations of gates, or other circuit components.
  • Logic may also be fully embodied as software. Where multiple logical logics are described, it may be possible to incorporate the multiple logical logics into one physical logic. Similarly, where a single logical logic is described, it may be possible to distribute that single logical logic between multiple physical logics.
  • an "operable connection,” or a connection by which entities are “operably connected,” is one in which signals, physical communications, or logical communications may be sent or received.
  • an operable connection includes a physical interface, an electrical interface, or a data interface, but it is to be noted that an operable connection may include differing combinations of these or other types of connections sufficient to allow operable control.
  • two entities can be operably connected by being able to communicate signals to each other directly or through one or more intermediate entities like a processor, operating system, a logic, software, or other entity.
  • Logical or physical communication channels can be used to create an operable connection.
  • Query refers to a semantic construction that facilitates gathering and processing information.
  • a query might be formulated in a database query language like structured query language (SQL) or object query language (OQL).
  • a query might be implemented in computer code (e.g., C#, C++, Javascript) that can be employed to gather information from various data stores or information sources.
  • Signal includes but is not limited to one or more electrical or optical signals, analog or digital signals, data, one or more computer or processor instructions, messages, a bit or bit stream, or other means that can be received, transmitted or detected.
  • Software includes but is not limited to, one or more computer or processor instructions that can be read, interpreted, compiled, or executed and that cause a computer, processor, or other electronic device to perform functions, actions or behave in a desired manner.
  • the instructions may be embodied in various forms like routines, algorithms, modules, methods, threads, or programs including separate applications or code from dynamically or statically linked libraries.
  • Software may also be implemented in a variety of executable or loadable forms including, but not limited to, a stand-alone program, a function call (local or remote), a servelet, an applet, instructions stored in a memory, part of an operating system or other types of executable instructions.
  • Suitable software for implementing the various components of the example systems and methods described herein may be produced using programming languages and tools like Java, Java Script, Java.NET, ASP.NET, VB.NET, Cocoa, Pascal, C#, C++, C, CGI, Perl, SQL, APIs, SDKs, assembly, firmware, microcode, or other languages and tools.
  • Software whether an entire system or a component of a system, may be embodied as an article of manufacture and maintained or provided as part of a computer-readable medium as defined previously.
  • Another form of the software may include signals that transmit program code of the software to a recipient over a network or other communication medium.
  • a computer- readable medium has a form of signals that represent the software/firmware as it is downloaded from a web server to a user.
  • the computer-readable medium has a form of the software/firmware as it is maintained on the web server. Other forms may also be used.
  • User includes but is not limited to one or more persons, software, computers or other devices, or combinations of these.
  • Fig. 1 illustrates an example system 100 for collecting tire field survey data.
  • Collecting tire field survey data includes collecting information regarding tire pattern, tire brand and serial number, tire position in the vehicle, tire option code, air pressure, DOT information in or out, outside tire diameter (OTD), tire size, tire specifications, tire edge OTD, mounting date, and so on. Additionally, collecting tire field survey data includes collecting irregular tire wear information such as the depth, width, and length of irregular thread wear. Collecting tire field survey data also includes collecting remaining thread depth measurement information at various measurement locations within tire grooves.
  • One or more computers 102a-c (hereinafter referred to as computer 102) are operably connected to one or more corresponding thread gages 104a-c (hereinafter referred to as thread gage 104).
  • thread gage 104 is illustrated as being coupled to computer 102 by a wire, thread gage 104 may also be coupled to computer 102 wirelessly.
  • thread gage 104 may be a Mitutoyo wireless digital thread gage.
  • Thread gage 104 is configured to collect tire thread measurement data from one or more tires 106a-c (hereinafter referred to as tire 106). Tire thread measurement data is useful to in estimating the estimated life of a tire. By measuring the depth of the remaining tire thread, a tester may estimate how many more miles a tire may safely drive. Thread gage 104 is configured to automatically transmit the tire thread measurement data to computer 102 without requiring manual data entry.
  • computer 102 is configured to receive tire data via alternative user input devices.
  • computer 102 may be configured to receive tire data via a keyboard, a mouse, a touch screen, or other similar input device.
  • the system 100 further includes a server 108 to which data can be uploaded and from which data can be downloaded.
  • server 108 serves as a central data repository so that various users may upload and download data. In this arrangement, the integrity of the data is improved over a decentralized system because all users work from the same data.
  • a distributed model is used instead of a central server. In the distributed model, the data is uploaded and downloaded from multiple locations (instead of a single location) that work in concert to maintain data integrity.
  • Computer 102 is in communication with server 108 and is configured to upload tire thread measurement data to server 108. Computer 102 is also configured to download, from server 108, data necessary to perform tire field survey data collection.
  • Server 108 and computer 102 include one or more data tables (not shown) for storing data.
  • server 108 and computer 102 include a tire mounting data table for storing data about tires and how they are mounted on specific vehicles.
  • Tire mounting tables may also include a tire test template (not shown).
  • a tire test template includes data fields for entering tire survey data.
  • a tire test template may also include data fields representative of customers for whose tires the survey data is being collected, and so on.
  • the mounting data table may further include fleet data including data representative of a plurality of vehicles in a fleet.
  • Server 108 and computer 102 also include an inspection table in which the tire inspection data is stored. Data may be downloaded or uploaded between computer 102 and main server 108.
  • Computer 102 has a tire field survey data collection program (not shown).
  • tire field survey data collection program is responsible for the graphical display of tire information including, for example, tire location information, tire pattern information, tire brand and model information, tire manufacturing date information, tire mileage information, tire air pressure information, and so on.
  • Tire location information refers to information regarding the physical location of the tires in a particular vehicle in the fleet (e.g. driver side front, passenger side rear, left front, right rear, and so on).
  • Tire field survey data collection program is further responsible for receiving tire inspection data corresponding to the tire 106 being inspected.
  • the tire inspection data corresponds to at least one test field from the test fields in the tire test template.
  • Fig. 2 illustrates a block diagram of an example tire field survey data collection program 200.
  • Tire field survey data collection program 200 includes a tire test template program 202 for receiving data representative of a tire test template, or a survey form, including data representative of at least one test field for collecting tire survey data.
  • Tire test template program enables a user to choose a test template, from a drop down menu, corresponding to the type of test, or field survey, the user wants to perform. The user may choose to obtain historical tire inspection data corresponding to the chosen test template as well. Once a user selects a test template, the user may proceed to select a vehicle from a fleet of vehicles for which the user wishes to perform the field survey.
  • Tire field survey data collection program 200 further includes a vehicle data program 204 for receiving data representative of at least one selected vehicle. Before a user may proceed to collect survey data, the user may select a specific test, or survey type, as well as the vehicle. In one example, Tire field survey data collection program 200 may customize a data entry form based on the selected test type and the vehicle. A user may first choose a test from a drop down menu and decide whether to obtain mounting data corresponding to the chosen test. The user then chooses a fleet from a drop down menu and a particular vehicle from that fleet from a second drop down menu which populates after a fleet is selected. The user may then include additional information, using vehicle data program 204, before proceeding with a field survey. For example, a user may choose mounting mileage corresponding to the chosen vehicle, and input odometer current mileage information.
  • Tire field survey data collection program 200 further includes a tire location program 206 for displaying, on a graphical display, tire location data, based on the test type and the vehicle selected.
  • Tire location data refers to the physical location of the tires on a particular vehicle (e.g. driver side front, passenger side rear, left front, right rear, and so on).
  • Tire location program 206 displays tire information including tire location relative to the axles of the vehicle and relative to the other tires in the vehicle.
  • a vehicle may include three axles, for example. The tires corresponding to a front axle may have be removed from a vehicle and therefore data corresponding to those tires may not be displayed by tire location program 206.
  • a middle axle may include four tires that may be labeled G17, G18, G19, and G20, for example, by tire location program 206.
  • a rear axle may include four tires that may be labeled G21, G22, G23, and G24.
  • Tire location program 206 may display additional tire information for each tire.
  • tire location program 206 may display the tire pattern.
  • tire location program 206 may display other relevant tire information for each tire such as tire brand and model information, tire manufacturing date information, tire mileage information, tire air pressure information, and so on.
  • Tire location program 206 may employ a plurality of indicators to distinguish tires that have been inspected, tires yet to be inspected, and tires that will not be inspected because they have been removed from the vehicle. For example, a blue rectangle on a graphical display of a tire may indicate that the tire is yet to be inspected. Other indicators may indicate that the tire has been removed, has already been inspected, or will not be inspected or inspected at a later time. [00037] In one example, tire location program 206 allows a user to (1) enter inflation pressure information for each tire, (2) enter any comments regarding the vehicle whose tires are being inspected, and (3) click on a particular tire to begin the collection of tire field survey data or test data for each of the tires.
  • Tire survey data collection program 200 further includes a tire inspection program 208 for receiving tire inspection data corresponding to at least one tire of the plurality of tires.
  • the tire inspection data includes data representing tire test data corresponding to the at least one test field.
  • Tire inspection program 208 may display information relating to a chosen tire. Displayed information may include tire pattern, tire brand and serial number, tire position in the vehicle, tire option code, air pressure, DOT information in or out, outside tire diameter (OTD), tire size, tire specifications, tire edge OTD, mounting date, and so on.
  • OTD outside tire diameter
  • the tire inspection data includes data representing tire test data corresponding to at least one test field from a set of test fields.
  • Test fields include, but are not limited to, remaining tread depth (RTD) and irregular wear (IW).
  • RTD remaining tread depth
  • IW irregular wear
  • the system may receive or provide calculated fields such as average RTD (Avg RTD), worn thread depth [original thread depth - RTD] (WTD), miles [new miles - old miles], miles per millimeters [miles / WTD] (MPM), total IW volume [IW1 + IW2 + IWn] (TIWV), and so on.
  • tire inspection program 208 may provide data fields for receiving RTD measurement information at various measurement locations within the various tire grooves, according to a selected tire pattern.
  • a tire of pattern may have four grooves. Accordingly, tire inspection program 208 may provide for three RTD measurement positions within each groove for a total of twelve RTD measurements.
  • tire inspection program 208 may provide fields for receiving IW data including, but not limited to, the depth, width, and length of irregular thread wear.
  • Tire inspection program 208 includes a "Save Record” function or button for saving data. Saved data may be stored on computer 102 or uploaded to server 108.
  • tire field survey data collection program 200 may be configured to display a list of vehicles. Tire field survey data collection program 200 may employ a plurality of indicators to distinguish vehicles that have been inspected, vehicles yet to be inspected, and vehicles that will not be inspected because the tires of interest have been removed from the vehicle. For example, a vehicle which has been inspected may be displayed with a background of a different color than vehicles that have not been inspected.
  • tire field survey data collection program 200 may display an overview of the tires that have been inspected.
  • An overview may include, but is not limited to, test information, date of the measurement, vehicle identification, tire pattern, tire brand number, tire position, tire mileage, miles per millimeter, and so on.
  • Example methods may be better appreciated with reference to the flow diagram of Figures 3. While for purposes of simplicity of explanation, the illustrated methodologies are shown and described as a series of blocks, it is to be appreciated that the methodologies are not limited by the order of the blocks, as some blocks can occur in different orders or concurrently with other blocks from that shown or described. Moreover, less than all the illustrated blocks may be required to implement an example methodology. Furthermore, additional or alternative methodologies can employ additional, not illustrated blocks.
  • blocks denote “processing blocks” that may be implemented with logic.
  • the processing blocks may represent a method step or an apparatus element for performing the method step.
  • a flow diagram does not depict syntax for any particular programming language, methodology, or style (e.g., procedural, object-oriented). Rather, a flow diagram illustrates functional information one skilled in the art may employ to develop logic to perform the illustrated processing. It will be appreciated that in some examples, program elements like temporary variables, routine loops, and so on, are not shown. It will be further appreciated that electronic and software applications may involve dynamic and flexible processes so that the illustrated blocks can be performed in other sequences that are different from those shown or that blocks may be combined or separated into multiple components.
  • methodologies are implemented as processor executable instructions or operations provided on a computer-readable medium. While the above method is described being provided on a computer-readable medium, it is to be appreciated that other example methods described herein can also be provided on a computer-readable medium.
  • Figure 3 illustrates various actions occurring in serial, it is to be appreciated that various actions illustrated in Figure 3 could occur substantially in parallel. While five processes are described, it is to be appreciated that a greater or lesser number of processes could be employed and that lightweight processes, regular processes, threads, and other approaches could be employed. It is to be appreciated that other example methods may, in some cases, also include actions that occur substantially in parallel.
  • Figure 3 illustrates a flow chart of an example method for collecting tire field survey data.
  • computer 102 receives data representative of a selected tire test template.
  • the tire test template includes data representative of at least one test field.
  • computer 102 receives data representative of a selected vehicle, including data representative of a plurality of tires on the selected vehicle.
  • computer 102 displays, on a graphical display, data representative of the plurality of tires on the selected vehicle, including data representative of the physical location of the plurality of tires on the selected vehicle.
  • computer 102 displays, on a graphical display, a data entry form corresponding to a selected tire of the plurality of tires.
  • the data entry form includes at least one data entry field corresponding to the at least one test field of the selected tire test template.
  • computer 102 receives tire inspection data corresponding to at least one tire of the plurality of tires, wherein the tire inspection data corresponds to the at least one data entry field.
  • Figure 4 is a schematic drawing illustrating an example computer for implementing the example system and method of Figs. 2 and 3.
  • Figure 4 illustrates a computer 400 that includes a processor 402, a memory 404, and I/O Ports 410 operably connected by a bus 408.
  • the computer 400 may include an inspection logic 430 configured to receive tire test template data including data representing a set of test fields.
  • Inspection logic 430 may also be configured to receive fleet data including data representing a plurality of vehicles in a fleet.
  • Inspection logic 430 may also be configured to graphically display or cause the graphical display of tire location information including information regarding the physical location of a plurality of tires in a particular vehicle in the fleet.
  • Inspection logic 430 may also be configured to receive tire inspection data corresponding to at least one tire from the plurality of tires, wherein the tire inspection data includes data representing tire test data corresponding to at least one test field from the set of test fields.
  • the inspection logic 430 whether implemented in computer 400 as hardware, firmware, software, or a combination thereof may provide means for receiving tire inspection data and means for displaying tire location information.
  • the inspection logic 430 may be permanently or removably attached to the computer 400.
  • the processor 402 can be a variety of various processors including dual microprocessor and other multi-processor architectures.
  • the memory 404 can include volatile memory or non-volatile memory.
  • the non-volatile memory can include, but is not limited to, ROM, PROM, EPROM, EEPROM, and the like.
  • Volatile memory can include, for example, RAM, synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).
  • a disk 406 may be operably connected to the computer 400 via, for example, an I/O Interfaces (e.g., card, device) 418 and an I/O Ports 410.
  • the disk 406 can include, but is not limited to, devices like a magnetic disk drive, a solid state disk drive, a floppy disk drive, a tape drive, a Zip drive, a flash memory card, or a memory stick.
  • the disk 406 can include optical drives like a CD-ROM, a CD recordable drive (CD-R drive), a CD rewriteable drive (CD-RW drive), or a digital video ROM drive (DVD ROM).
  • the memory 404 can store processes 414 or data 416, for example.
  • the disk 406 or memory 404 can store an operating system that controls and allocates resources of the computer 400.
  • the bus 408 can be a single internal bus interconnect architecture or other bus or mesh architectures. While a single bus is illustrated, it is to be appreciated that computer 400 may communicate with various devices, logics, and peripherals using other busses that are not illustrated (e.g., PCIE, SATA, Infiniband, 1394, USB, Ethernet).
  • the bus 408 can be of a variety of types including, but not limited to, a memory bus or memory controller, a peripheral bus or external bus, a crossbar switch, or a local bus.
  • the local bus can be of varieties including, but not limited to, an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an extended ISA (EISA) bus, a peripheral component interconnect (PCI) bus, a universal serial (USB) bus, and a small computer systems interface (SCSI) bus.
  • ISA industrial standard architecture
  • MCA microchannel architecture
  • EISA extended ISA
  • PCI peripheral component interconnect
  • USB universal serial
  • SCSI small computer systems interface
  • the computer 400 may interact with input/output devices via I/O Interfaces 418 and I/O Ports 410.
  • Input/output devices can include, but are not limited to, a keyboard, a microphone, a pointing and selection device, cameras, video cards, displays, disk 406, network devices 420, depth gage 425 and the like.
  • the I O Ports 410 can include but are not limited to, serial ports, parallel ports, and USB ports.
  • the computer 400 can operate in a network environment and thus may be connected to network devices 420 via the I/O Interfaces 418, or the I/O Ports 410. Through the network devices 420, the computer 400 may interact with a network. Through the network, the computer 400 may be logically connected to remote computers.
  • the networks with which the computer 400 may interact include, but are not limited to, a local area network (LAN), a wide area network (WAN), and other networks.
  • the network devices 420 can connect to LAN technologies including, but not limited to, fiber distributed data interface (FDDI), copper distributed data interface (CDDI), Ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (IEEE 802.15.1), Zigbee (IEEE 802.15.4) and the like.
  • the network devices 420 can connect to WAN technologies including, but not limited to, point to point links, circuit switching networks like integrated services digital networks (ISDN), packet switching networks, and digital subscriber lines (DSL). While individual network types are described, it is to be appreciated that communications via, over, or through a network may include combinations and mixtures of communications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Tires In General (AREA)

Abstract

Dans un procédé permettant de collecter des données d'enquête dans le domaine des pneus, un ordinateur reçoit des données représentant un modèle de test de pneus sélectionné. Le modèle de test de pneus comprend des données représentant au moins un domaine de test. L'ordinateur reçoit des données représentant un véhicule sélectionné, comportant des données représentant une pluralité de pneus sur le véhicule sélectionné. L'ordinateur affiche, sur un écran graphique, des données représentant la pluralité de pneus sur le véhicule sélectionné, contenant des données représentant l'emplacement physique de la pluralité de pneus sur le véhicule sélectionné. L'ordinateur affiche, sur un écran graphique, une forme d'entrée de données correspondant à un pneu sélectionné parmi la pluralité de pneus. La forme d'entrée de données comprend au moins un champ d'entrée de données correspondant au dit champ de test du modèle de test de pneus sélectionné.
PCT/US2012/038306 2011-05-18 2012-05-17 Système et procédé permettant une collecte de données d'enquête dans le domaine des pneus Ceased WO2012158888A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161487568P 2011-05-18 2011-05-18
US61/487,568 2011-05-18

Publications (2)

Publication Number Publication Date
WO2012158888A2 true WO2012158888A2 (fr) 2012-11-22
WO2012158888A3 WO2012158888A3 (fr) 2013-01-10

Family

ID=47177625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/038306 Ceased WO2012158888A2 (fr) 2011-05-18 2012-05-17 Système et procédé permettant une collecte de données d'enquête dans le domaine des pneus

Country Status (1)

Country Link
WO (1) WO2012158888A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2876413A1 (fr) 2013-11-21 2015-05-27 Volvo Car Corporation Procédé permettant d'estimer la performance de friction relative de pneu
CN112710478A (zh) * 2020-12-04 2021-04-27 深圳市道通科技股份有限公司 用于汽车部件检测的客户端及汽车部件检测系统
CN113866167A (zh) * 2021-09-13 2021-12-31 北京逸驰科技有限公司 一种轮胎检测结果的生成方法、计算机设备及存储介质
CN116331263A (zh) * 2023-03-29 2023-06-27 奇瑞新能源汽车股份有限公司 一种轮胎检查模式控制方法及系统
CN116691236A (zh) * 2022-02-24 2023-09-05 博泰车联网(南京)有限公司 一种车辆、车辆控制方法、装置及计算机存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6034676A (en) * 1995-04-11 2000-03-07 Data View, Inc. System and method for measuring and processing tire depth data
US6791695B2 (en) * 1999-06-16 2004-09-14 Bandag Licensing Corporation Shearographic imaging machine with archive memory for animation data and air handling system
GB2386951A (en) * 2002-03-27 2003-10-01 Mitutoyo Corp Wheel data measuring and processing system and method
US20090293603A1 (en) * 2008-05-29 2009-12-03 Michael Wayne Douglas Method and system for determining wheel parameter consistency

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2876413A1 (fr) 2013-11-21 2015-05-27 Volvo Car Corporation Procédé permettant d'estimer la performance de friction relative de pneu
US9944132B2 (en) 2013-11-21 2018-04-17 Volvo Car Corporation Method for estimating a relative tire friction performance
CN112710478A (zh) * 2020-12-04 2021-04-27 深圳市道通科技股份有限公司 用于汽车部件检测的客户端及汽车部件检测系统
WO2022116925A1 (fr) * 2020-12-04 2022-06-09 深圳市道通科技股份有限公司 Client pour test de pièce automobile et système de test de pièce automobile
CN113866167A (zh) * 2021-09-13 2021-12-31 北京逸驰科技有限公司 一种轮胎检测结果的生成方法、计算机设备及存储介质
CN116691236A (zh) * 2022-02-24 2023-09-05 博泰车联网(南京)有限公司 一种车辆、车辆控制方法、装置及计算机存储介质
CN116331263A (zh) * 2023-03-29 2023-06-27 奇瑞新能源汽车股份有限公司 一种轮胎检查模式控制方法及系统

Also Published As

Publication number Publication date
WO2012158888A3 (fr) 2013-01-10

Similar Documents

Publication Publication Date Title
EP2613212B1 (fr) Optimisation des paramètres d'un algorithme de diagnostic
WO2012158888A2 (fr) Système et procédé permettant une collecte de données d'enquête dans le domaine des pneus
US9607375B2 (en) Biological data annotation and visualization
French et al. Identifying biological landmarks using a novel cell measuring image analysis tool: Cell-o-Tape
RU2010137352A (ru) Способ, компьютерный программный продукт и система обеспечения поддержки принятия клинического решения
Grotzinger et al. Multivariate genomic architecture of cortical thickness and surface area at multiple levels of analysis
JP6315528B1 (ja) 異常検知モデル構築装置、異常検知モデル構築方法及びプログラム
RU2009101194A (ru) Направляемая клинистом компьютерная диагностика на базе примеров
CN114492764A (zh) 人工智能模型测试方法、装置、电子设备和存储介质
CN112541510A (zh) 基于多通道时间序列数据的智能故障诊断方法
CN106906295A (zh) 数字pcr检测基因点突变方法及装置
CN113673827A (zh) 一种区域水资源脆弱性预警系统及方法
Rao et al. Investigating the intra-driver heterogeneity in car following behaviour based on large-scale naturalistic driving study
CN109977923B (zh) 基于脑电信号的驾驶员性别检测方法及系统
Dede et al. Lack of univariate, clinically-relevant biomarkers of autism in resting state EEG: a study of 776 participants
CN106776742A (zh) 一种纯电动车vcu数据处理和分析方法
US20160357906A1 (en) Biological data annotation and visualization
CN119152501B (zh) 基于深度学习的细胞应力分析方法及其应用
CN111833080A (zh) 信息推送的方法、装置、电子设备和计算机可读存储介质
CN114138668A (zh) 一种利用gui工具进行自动泊车测试的方法
CN111611353A (zh) 筛选方法、装置、电子设备及计算机可读存储介质
JP2021033353A (ja) ユーザ属性推定装置、ユーザ属性推定方法およびプログラム
CN117113800A (zh) 一种行车运行状态异常检测可视分析方法及系统
CN117605627A (zh) 一种风电齿轮箱冷却器芯体漏油检测系统及方法
CN110533093A (zh) 一种汽车前脸品牌家族化分析方法

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12785435

Country of ref document: EP

Kind code of ref document: A2