CN103630375B - A kind of method for diagnosing faults of board units, board units and system - Google Patents
A kind of method for diagnosing faults of board units, board units and system Download PDFInfo
- Publication number
- CN103630375B CN103630375B CN201210307643.1A CN201210307643A CN103630375B CN 103630375 B CN103630375 B CN 103630375B CN 201210307643 A CN201210307643 A CN 201210307643A CN 103630375 B CN103630375 B CN 103630375B
- Authority
- CN
- China
- Prior art keywords
- situation
- obu
- instruction
- information
- failure
- 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.)
- Active
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
This application discloses a kind of method for diagnosing faults of board units, board units and system, wherein, method is comprised the following steps：Perform failure information storing step：Board units are during flow is specified in operation, if instruction performs failure, by storage region of the corresponding execution failure information record in the board units；Perform failure information and step is provided：The execution failure information is supplied to outside reading equipment by board units.The application is easy to technical staff accurately and rapidly to be diagnosed to the failure of OBU in rework process, OBU can not only be improved reprocesses speed, ensure to reprocess quality, and it is easy to the technical staff of OBU manufacturers to pass through to analyze and assess the execution failure information recorded in OBU, the links such as the design of product/test/use are improved, the repair rate of product is reduced to greatest extent.
Description
Technical field
The application is related to a kind of intelligent transportation（ITS：Intelligent Transportation System）Field, especially
It is related to a kind of board units（OBU：On-board Units）Method for diagnosing faults, OBU and system.
Background technology
DSRC（DSRC：Dedicated Short Range Communications）Technology is used for road
Roadside device（RSU：Road Side Unit）With the short range communication between the OBU on vehicle, to realize deducting fees vehicle
Or monitoring, such as in electric non-stop toll（Electronic Toll Collection：ETC）In system, on RSU and vehicle
OBU carry out the interaction of microwave signal, make vehicle automatic fee in the case of not parking.
With developing rapidly and extensive use for DSRC technology, and OBU customer group scales go from strength to strength, people couple
The maintenance of OBU proposes requirements at the higher level.Once OBU is damaged, it is necessary first to accurately find out the reason for failure occurs and specific
Link, i.e., carry out fault diagnosis to OBU, it is generally the case that the reason for causing OBU to reprocess mainly includes that improper use, technique are asked
Topic, normal damage etc..A part of reprocessed products are tested by some and are easy to confirm failure cause；However, because some failures are
Occur under specific use environment, the practical application scene that it occurs cannot be reduced or simulated by technical staff, therefore be had
Some reprocessed products are just less susceptible to confirm failure cause（What such as improper use was caused reprocesses）, it is unfavorable for reprocessing for OBU.
The content of the invention
The application technical problem underlying to be solved be to provide a kind of method for diagnosing faults for being easy to safeguard OBU,
Board units and system.
In order to solve the above technical problems, according to the application's in a first aspect, the application provides a kind of failure of board units
Diagnostic method, comprises the following steps：
Perform failure information storing step：Board units are during flow is specified in operation, if instruction performs failure,
Corresponding execution failure information is then recorded into the storage region in the board units；
Perform failure information and step is provided：The execution failure information is supplied to outside reading equipment by board units.
In a kind of embodiment, the concrete mode for recording the execution failure information includes：The execution failure information includes
Fault type, failure command, unsuccessfully reply at least one.
In a kind of embodiment, the record form for performing failure information is failure record structure, array, function, change
Amount or pointer.
In a kind of embodiment, the execution failure information also includes call number, after the execution failure information is recorded every time,
The call number of the execution failure information for recording next time Jia 1 automatically.
In a kind of embodiment, during the execution failure information is recorded every time, also the execution failure information is entered
Row data check, and generate and record after check code in the execution failure information.
In a kind of embodiment, during the execution failure information is recorded every time, also the execution failure information is entered
Row backup.
In a kind of embodiment, the specified flow include once distribution flow, secondary offering flow, activation testing process,
At least one in transaction flow.
In a kind of embodiment, the execution failure information storing step also includes：If instruction runs succeeded, will correspondence
The information that runs succeeded also record the storage region in board units.
According to the second aspect of the application, this application provides a kind of board units, including：
Perform judge module：Perform failure information memory module：During specifying flow in board units operation,
If instruction performs failure, by storage region of the corresponding execution failure information record in board units；
Perform failure information and module is provided：For the execution failure information to be supplied into outside reading equipment.
In a kind of embodiment, the execution failure information memory module includes structure generation unit, for failed regeneration
Interrecord structure body, information in the failure record structure includes fault type, failure command, unsuccessfully reply at least one
Kind.
According to the third aspect of the application, this application provides a kind of fault diagnosis system of board units, including the above
Described board units, and the outside reading equipment.
The beneficial effect of the application is：The application is carried out to the specifying information that OBU breaks down in actual application
Record, is easy to technical staff accurately and rapidly to be diagnosed to the failure of OBU according to these information in rework process, not only
OBU can be improved reprocesses speed, it is ensured that reprocesses quality, and is easy to the technical staff of OBU manufacturers by analysis and assesses
The execution failure information recorded in OBU, improves the links such as the design of product/test/use, and product is reduced to greatest extent
Repair rate, so as to meet the use demand of user, also allow for user and be based on these information, the quality of OBU is made a distinction and
Selection, so as to select preferable OBU manufacturers.
Brief description of the drawings
Fig. 1 is a kind of method for diagnosing faults flow chart of the OBU of embodiment of the application；
Fig. 2 is the flow chart that a kind of OBU of embodiment of the application is once issued；
Fig. 3 is a kind of flow chart of the OBU secondary offerings of embodiment of the application；
Fig. 4 is a kind of flow chart of the OBU activation detections of embodiment of the application；
Fig. 5 is a kind of flow chart of the OBU arm's length dealings of embodiment of the application；
Fig. 6 is the flow chart that a kind of OBU of embodiment of the application carries out fault diagnosis during arm's length dealing；
Fig. 7 is the flow chart of the read failure information from a kind of OBU of embodiment of the application；
Fig. 8 is a kind of structured flowchart of the OBU of embodiment of the application.
Specific embodiment
The application is described in further detail below by specific embodiment combination accompanying drawing.
In the embodiment of the present application, OBU is remembered in the execution failure information performed appeared in all kinds of instruction process
Record, is easy in OBU rework process carry out fault diagnosis accurately and quickly.
Embodiment one：
Fig. 1 is refer to, the method for diagnosing faults of the present embodiment OBU is mainly included the following steps that：
Step S101：Perform failure information storing step, OBU during all kinds of specified flows are run, decision instruction
Whether failure is performed, if instruction performs failure, by storage region of the corresponding execution failure information record in OBU.
Used as one of crucial DSRC equipment, in order to meet technical standard and use demand, OBU is from producing to actually making
The flow of various instructions can be experienced during, it is main to include once distribution, secondary offering, activation and test and reality
Transaction flow.In every kind of flow, OBU can perform multiple instruction according to according to certain order again, in most cases, these instructions
Capital successful execution, under fortuitous event, also due to the reason such as OBU improper uses, technological problemses, signal intensity, normal damage
Instruction is caused to perform failure, in this case, corresponding execution failure information is recorded and internally specifically deposited by OBU by software
Storage area domain.For example memory space can carry out information Store using the less EEPROM or Flash that takes up room, it is assumed that EEPROM holds
Amount size is 2Kbyte, and every performs the memory space that failure information only takes up 106 bytes, and maximum can support 19 records, when
So can also according to actual needs increase the capacity of EEPROM.
The content of the execution failure information of record may include call number, fault type, failure command, unsuccessfully reply every time
One or more of information, the property for recording failure facilitates technical staff's rapid understanding failure during reprocessing to produce
The reason for raw and how to solve failure.Call number is used to carry out order differentiation and statistics to the instruction that failure is performed a plurality of times, often
After secondary record performs failure information, the call number in the execution failure information for recording next time Jia 1 automatically.Record performs mistake every time
During losing information, also data check can be carried out to performing failure information, and to generate record after check code and unsuccessfully believe performing
In breath, it is to avoid information is tampered in memory period, data check is carried out in order to improve processing speed and outside reading equipment
Speed, the mechanism of data check uses CRC check.Further, during record performs failure information every time, can also be to holding
Row failure information is backed up, and further improves the reliability of data processing.
The recording mode for performing failure information has various, such as in the present embodiment, the software in OBU can generate a note
Directory structures body err_record is used to record specific execution failure information, when structure definition includes call number, failure occurs
Instruction（Abbreviation failure command）, occur failure when response or information（Referred to as unsuccessfully reply）, structure crc check codes
Deng.Or in other embodiment, the record form for performing failure information can also be array, function, variable or pointer etc..
In addition, in each flow, in addition to record performs failure information, according to real needs, if instruction runs succeeded, also
The corresponding information that runs succeeded can also be recorded the storage region in OBU, to be set by outside reading in case of need
It is standby to read these data.The recording mode of the information that runs succeeded can also refer to perform failure information, be carried out in the form of structure
Record.
Step S102：Perform failure information and step is provided, according to specific needs, OBU will perform failure information and be supplied to outward
Portion reads equipment, for example reprocess in equipment, periodic detection, during maintenances etc., the executable step.Specifically, it is outside to read
Equipment can be emulator, hand-held set etc., and it has the data-interface compatible with OBU phases, can be sent to OBU by data-interface
Information reading step, and the execution failure information stored in OBU is read one by one, certainly, can also one by one read therein execution into
Work(information.For the sake of security, when outside reading equipment reads information, also need to carry out data check one by one to it, only
Information is just read in the case of data check is successful, it is invalid to be otherwise set to this information.
Once distribution flow below to OBU, secondary offering flow, activation testing process, transaction flow are situated between respectively
Continue.
As shown in Fig. 2 the acquiescence that the once distribution flow of OBU is mainly used in being loaded in ESAM when replacement OBU dispatches from the factory is close
Key, publishing system carries out key dispersion (specific dispersion process refers to the relevant content in GB) according to the individual information of OBU,
Due to each OBU individual information have uniqueness, therefore therefore each OBU be replaced after key also just have uniqueness, should
Flow is mainly carried out when equipment is dispatched from the factory.Idiographic flow is：
Distributed software obtains OBU individual informations --- issuing equipment sends BST broadcasting instructions to OBU --- by OBU from not
Dormancy state wakes up, and --- OBU provides VST responses --- issuing equipment extracts the individual information of OBU --- to issuing equipment, and distribution is soft
Issuing equipment sends key to individual information distributed key of the part according to OBU --- distributed software replaces master control key --- to OBU
Replacement instruction Transfer channel.rq --- OBU is to embedded safe control module（ESAM：Embedded Secure
Access Module）Transmission is instructed and obtains key replaces result --- and key is replaced result Transfer by OBU
Channel.rs is sent to issuing equipment --- issuing equipment replaces result to distributed software " return " key" ---, and distributed software is sentenced
Whether disconnected key replacement succeeds, and once distribution terminates if success（Returned to if unsuccessful and replace key again）--- it is logical
Knowing OBU release links SetMMT.rq+Evenreport --- OBU is given after issuing successfully prompting to issuing equipment and is transferred to dormancy
Pattern.
As shown in figure 3, the once distribution flow of OBU is mainly used in writing the individual information of car owner, these individual informations example
Such as car plate, engine mumber, the number-plate number, vehicle（Lorry, minibus）, start and end date etc., generally done business at each
Site is carried out.Operating personnel will be confirmed by observing the information of distributed software finally display after distribution is finished, to ensure
The information for being write is all correct.Idiographic flow is：
Distributed software obtains OBU individual informations --- issuing equipment sends BST broadcasting instructions to OBU --- by OBU from not
Dormancy state wakes up, and --- OBU provides VST responses --- issuing equipment extracts the individual information of OBU --- to issuing equipment, and distribution is soft
Part shows that OBU information --- distributed software sets the guarantee period of OBU --- issuing equipment sends change system information and instructs to OBU
OBU will change result to Transfer channel.rq --- OBU sends to ESAM and instructs and obtain change result ---
Transfer channel.rs are sent to issuing equipment --- issuing equipment returns to change result to distributed software ---, and distribution is soft
Part judges whether change succeeds, and information of vehicles, such as license plate number, tonnage vehicle etc. are set if success（If unsuccessful
Reset the guarantee period）--- issuing equipment sends change information of vehicles instruction Transfer channel.rq to OBU ---
OBU sends to ESAM and instructs and obtain change result --- and OBU sends information of vehicles change response Transfer to issuing equipment
Distributed software judges whether to change successfully channel.rs --- issuing equipment returns to change result to distributed software ---, is then
Read some information of vehicles such as（Otherwise reset information of vehicles）--- distributed software sends GetSecure.rq and refers to OBU
OBU provides response message to issuing equipment for order --- OBU sends instruction and reads information of vehicles to ESAM ---
GetSecure.rs --- due to information of vehicles be ciphertext, issuing equipment it is decrypted after output result --- distributed software shows
And information of vehicles is read, and judging whether it is wrong --- secondary offering terminates, and distributed software notifies OBU release links and be given to carry
Show that OBU provides hair to information --- issuing equipment notifies OBU release links SetMMT.rq+Evenreport --- to issuing equipment
Go and successfully point out and be transferred to park mode.
As shown in figure 4, activation testing process be mainly remove ESAM in dismounting position and detect that can OBU just on vehicle
Normal open is interrogated, and indivedual provinces can also do a mock trading, such as zero consumption checking（Detain 0 yuan）, in OBU formally using preceding doing most
Afterwards check to ensure that OBU can be used normally on vehicle.Idiographic flow is：
Handheld device sends broadcasting instructions search OBU-OBU and is waken up from resting state --- and OBU is provided to handheld device
VST responses --- handheld device shows OBU individual informations --- handheld device prepares to remove dismounting position Transfer
Channel.rq --- OBU send to ESAM instruct and obtain implementing result --- OBU is by implementing result Transfer
Channel.rs returns to handheld device --- and handheld device judges whether to remove successfully, is then to read information of vehicles Get
Secure.rq --- OBU sends to ESAM and instructs and obtain implementing result --- OBU are to the vehicle after handheld device loopback encryption
Information Get Secure.rs --- handheld device is decrypted and shows information of vehicles --- handheld device notifies OBU release links
SetMMT.rq+Evenreport --- OBU provides prompt message and is transferred to park mode to handheld device.
As shown in figure 5, transaction flow is most crucial link in OBU applications, it is also the ring for being easiest to failure problem
Section, the RSU and OBU for being primarily referred to as ETC tracks entrance or outlet carries out the process that vehicle toll is realized in data interaction.Although track
Pattern is divided into entrance, outlet and open three kinds but different for OBU, the instruction that antenna is issued under different track patterns
It is otherwise varied, but protocol level has no substantial difference.Idiographic flow is：
Lane system last time notifies that the antenna in RSU terminates transaction --- antennae polling sends BST broadcast and refers to OBU
--- OBU is into being waken up after antenna coverage areas --- OBU provides the VST signals for having been enter into communications zone to antenna --- for order
Its line drawing OBU information --- lane system judges whether OBU is legal, is then to read information of vehicles Get by antenna
Secure.rq（Otherwise notify that antenna terminates transaction）--- OBU sends the information of vehicles after encryption is read in instruction to ESAM ---
OBU is to antenna loopback information of vehicles Get Secure.rs --- antenna decrypts information of vehicles ---, and lane system registration of vehicle is believed
Antenna reads the IC card information Transfer of OBU to breath --- lane system notifies antenna continuous business ---
OBU is to antenna return response information Transfer for channel.rq --- OBU sends to IC-card and instructs ---
Channel.rs --- antenna judges whether to run succeeded, and is, carries out consumption Transfer channel.rq（Otherwise track system
System termination is concluded the business and provides alarm and no through traffic）--- OBU sends to IC-card and instructs --- OBU is to antenna return response
Information Transfer channel.rs --- antenna judges whether to conclude the business successfully, is, discharges link（Otherwise lane system terminates
Conclude the business and provide alarm and no through traffic）SetMMT.rq+Evenreport --- OBU provides prompt message simultaneously to antenna
Park mode is transferred to, while lane system notifies that track is let pass after concluding the business successfully --- lane system judges whether vehicle has rolled away from
Track, is then to continue to send broadcasting instructions（Otherwise continue to judge）.
Embodiment two：
As shown in fig. 6, a kind of idiographic flow that OBU realizes fault diagnosis in transaction flow is present embodiments provided, it is main
Comprise the following steps：
Step S601：OBU is into being waken up after the antenna coverage areas of RSU.
Step S602：System and outside reading equipment are initialized.
Step S603：OBU judges whether to conclude the business successfully, is, goes to step S606, otherwise goes to step S604.
Step S604：OBU generates corresponding failure record structure rr_record, and each structure is used as a carrying
This performs the record of failure information, including fault type failure command, unsuccessfully replys, also including call number and verification
Code, often records a call number and Jia 1 automatically.
Step S605：In the value of the storage region memory storage rr_record of OBU, while carry out crc data checks to avoid depositing
Data are tampered during storage, and also record can be backed up as needed.
Step S606：Record the information that runs succeeded.
Step S607：Run succeeded information in the storage region memory storage of OBU.
Step S608：After information Store is finished, OBU is transferred to park mode.
Certainly, it is similar with above step in other flows, once performing occurs during performing a certain instruction in OBU
The situation of failure, OBU just will perform failure information to the form by failure record structure and be recorded and stored, so as to event
As diagnosis basis during barrier diagnosis.
Embodiment three：
As shown in fig. 7, during present embodiments providing and carrying out fault diagnosis, detection etc. to OBU, being set using outside reading
The step of execution failure information of standby reading OBU storages, mainly including below scheme：
Step S 701：OBU after the modes such as wireless communication interface, serial ports, emulator are connected with outside reading equipment,
It is firstly received information read requests.
Step S702：Outside reading equipment reads the total number of record first, i.e., instruction perform failure from number of times, and take
The failure record structure of call number N=1 starts to read its specifying information.
Step S703：Read the specifying information in n-th structure.
Step S704：CRC data verification is carried out, and judges whether verification succeeds, be then to enter step S705, otherwise entered
Step S708.
Step S705：The prompting of information is read to OBU loopbacks.
Step S706：Take call number N+1.
Step S707：Judge whether record has run through, be then to enter step S711, otherwise return to step S703 readings next
Bar is recorded.
Step S708：Read the record of backup.
Step S709：CRC data verification is carried out, and judges whether verification succeeds, be then to enter step S705, otherwise entered
Step S710.
Step S710：Set this record information void in whole, will data be set to full 0.
Step S711：OBU is transferred to other logical process steps, for example, can be transferred to resting state.
Outside reading equipment obtain these record after, you can according to specifying information therein the failure of OBU is carried out accurately,
Quickly diagnosis, can also coordinate the log information of auxiliary software certainly, it is determined that the reason for causing failure, and provide valuable to reprocess
The clue of value, not only contribute to raising OBU reprocesses speed, it is ensured that reprocesses quality, and is easy to the technical staff of OBU manufacturers
By analyzing and assessing the execution failure information recorded in OBU, improve the quality of OBU, held from now on so as to avoid or reduce OBU
Occur the failure of correlation when row dependent instruction again, effectively reduce fault rate.
Such as OBU is likely to occur failure when the dependent instruction of following link in performing each flow, and each instruction causes
Failure situation may have it is following several, but only a kind of situation caused by can unsuccessfully occur first, software is only recorded at first
The situation of appearance.
Instruction one：【OBU wakes up from resting state】
Situation one：OBU is waken up rear clock handoff failure：
Situation two：OBU can not receive instruction after waking up
Instruction two：【OBU provides VST responses】
Situation one：BST parsing failures
Situation two：Loopback VST fails
Instruction three：【Read information of vehicles Get Secure.rs】
Situation one：Instruction parsing failure
Situation two：ESAM answer faileds
Instruction four：【The Transfer channel.rs such as key is replaced, change system information, clear dismounting position】
Situation one：Instruction parsing failure
Situation two：ESAM answer faileds
Situation three：IC-card answer failed
Instruction five：【The information set up after communication connection is received】
Situation one：Information receives time-out
Situation two：CRC check fails
Situation three：Signal intensity is low
Instruction six：【Link discharges】From from the point of view of OBU ends it is every do not go to this link all think Fail Transaction.
Situation one：SetMMI is not received
Situation two：EvenReport is not received
The execution failure information of all kinds of situation records, the failure that technical staff can be according to following table to being likely to occur for more than
Type, analyzing failure cause, and propose to solve the method for failure：
Example IV：
As shown in figure 8, present embodiments providing a kind of OBU for realizing various embodiments above, and read with outside by the OBU
The OBU fault diagnosis systems of write device composition, OBU mainly includes performing failure information memory module 10 and performing failure information carrying
For module 20：
Wherein, performing failure information memory module 10 is used for during flow is specified in OBU operations, if instruction is performed
During failure, then the storage region by corresponding execution failure information record in OBU, for example, perform failure information memory module 10
May include structure generation unit, for utilize Software Create failure record structure, perform failure information include fault type,
Failure command, unsuccessfully reply at least one, call number and check code etc. are may also include certainly.
Perform failure information and provide module 20 for according to specific needs, being supplied to outside reading to set execution failure information
It is standby.
It will be understood by those skilled in the art that all or part of step of various methods can pass through in above-mentioned implementation method
Program instructs related hardware to complete, and the program can be stored in a computer-readable recording medium, storage medium can be wrapped
Include：Read-only storage, random access memory, disk or CD etc..
Above content is to combine the further description that specific embodiment is made to the application, it is impossible to assert this Shen
Specific implementation please is confined to these explanations.For the application person of an ordinary skill in the technical field, do not taking off
On the premise of conceiving from the application, some simple deduction or replace can also be made, should all be considered as belonging to the protection of the application
Scope.
Claims (9)
1. a kind of method for diagnosing faults of board units, it is characterised in that comprise the following steps：
Perform failure information storing step：Board units are during flow is specified in operation, if instruction performs failure, will
The corresponding storage region for performing failure information record in the board units；
Perform failure information and step is provided：The execution failure information is supplied to outside reading equipment by board units；
The specified flow includes at least in once distribution flow, secondary offering flow, activation testing process, transaction flow
Kind；
In transaction flow, board units judge whether to conclude the business successfully, and otherwise board units generation performs the record of failure information；
The specified flow includes following dependent instruction, and the corresponding failure scenarios of the dependent instruction include situations below, if having
Failure occurs first caused by a kind of situation, then only record situation about occurring at first：
Instruction one：【OBU wakes up from resting state】；
Situation one：OBU is waken up rear clock handoff failure：
Situation two：OBU can not receive instruction after waking up；
Instruction two：【OBU provides VST responses】；
Situation one：BST parsing failures；
Situation two：Loopback VST fails；
Instruction three：【Read information of vehicles】；
Situation one：Instruction parsing failure；
Situation two：ESAM answer faileds；
Instruction four：【Key is replaced, changes system information, clearly dismantles position】；
Situation one：Instruction parsing failure；
Situation two：ESAM answer faileds；
Situation three：IC-card answer failed；
Instruction five：【The information set up after communication connection is received】；
Situation one：Information receives time-out；
Situation two：CRC check fails；
Situation three：Signal intensity is low；
Instruction six：【Link discharges】；
Situation one：SetMMI is not received；
Situation two：EvenReport is not received.
2. the method for claim 1, it is characterised in that the concrete mode for recording the execution failure information includes：Institute
State perform failure information include fault type, failure command, unsuccessfully reply at least one.
3. method as claimed in claim 2, it is characterised in that the record form of the execution failure information is failure record knot
Structure body, array, function, variable or pointer.
4. method as claimed in claim 2, it is characterised in that the execution failure information also includes call number, every time record
After the execution failure information, the call number of the execution failure information for recording next time Jia 1 automatically.
5. method as claimed in claim 2, it is characterised in that also right during recording the execution failure information every time
The execution failure information carries out data check, and records in the execution failure information after generating check code.
6. method as claimed in claim 2, it is characterised in that also right during recording the execution failure information every time
The execution failure information is backed up.
7. the method as any one of claim 1-6, it is characterised in that the execution failure information storing step is also wrapped
Include：If instruction runs succeeded, the corresponding information that runs succeeded also is recorded into the storage region in board units.
8. a kind of board units, it is characterised in that including：
Perform failure information memory module：During specifying flow in board units operation, if instruction performs failure
When, then corresponding execution failure information is recorded into the storage region in board units；
Perform failure information and module is provided：For the execution failure information to be supplied into outside reading equipment；
The specified flow includes at least in once distribution flow, secondary offering flow, activation testing process, transaction flow
Kind；
In transaction flow, board units judge whether to conclude the business successfully, and otherwise board units generation performs the record of failure information；
The specified flow includes following dependent instruction, and the corresponding failure scenarios of the dependent instruction include situations below, if having
Failure occurs first caused by a kind of situation, then only record situation about occurring at first：
Instruction one：【OBU wakes up from resting state】；
Situation one：OBU is waken up rear clock handoff failure：
Situation two：OBU can not receive instruction after waking up；
Instruction two：【OBU provides VST responses】；
Situation one：BST parsing failures；
Situation two：Loopback VST fails；
Instruction three：【Read information of vehicles】；
Situation one：Instruction parsing failure；
Situation two：ESAM answer faileds；
Instruction four：【Key is replaced, changes system information, clearly dismantles position】；
Situation one：Instruction parsing failure；
Situation two：ESAM answer faileds；
Situation three：IC-card answer failed；
Instruction five：【The information set up after communication connection is received】；
Situation one：Information receives time-out；
Situation two：CRC check fails；
Situation three：Signal intensity is low；
Instruction six：【Link discharges】；
Situation one：SetMMI is not received；
Situation two：EvenReport is not received.
9. a kind of fault diagnosis system of board units, it is characterised in that including the board units described in claim 8, and
The outside reading equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210307643.1A CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210307643.1A CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103630375A CN103630375A (en) | 2014-03-12 |
| CN103630375B true CN103630375B (en) | 2017-06-23 |
Family
ID=50211655
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210307643.1A Active CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103630375B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102016224351A1 (en) * | 2016-12-07 | 2018-06-07 | Robert Bosch Gmbh | Concept for testing a sensor system for detecting an occupancy state of a parking space for errors |
| CN109920073A (en) * | 2019-02-20 | 2019-06-21 | 深圳成谷科技有限公司 | A kind of ETC method of commerce and the roadside unit antenna for ETC transaction |
| CN110427010A (en) * | 2019-05-27 | 2019-11-08 | 苏州思卡信息系统有限公司 | A kind of vehicle-mounted OBU unusual condition warning system and method |
| CN111158943B (en) * | 2019-12-20 | 2024-03-22 | 航天信息股份有限公司 | Fault diagnosis method and device, storage medium and electronic equipment |
| CN111741489B (en) * | 2020-06-09 | 2022-11-08 | 福耀玻璃工业集团股份有限公司 | OBU fault detection method, OBU device and OBU fault detection system |
| CN117914347B (en) * | 2024-03-19 | 2024-05-31 | 广州铭创通讯科技有限公司 | DSRC switch on-off control method and device based on abnormal optimization of control signals |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1304487A (en) * | 1999-05-11 | 2001-07-18 | 罗伯特·博施有限公司 | Diagnostic test device for motor vehicles which comprises portable testing apparatus |
| CN101031455A (en) * | 2004-08-24 | 2007-09-05 | 夏普株式会社 | Display system |
| CN101136069A (en) * | 2007-09-18 | 2008-03-05 | 深圳市金溢科技有限公司 | Issuing method of ETC electronic label |
| CN102184576A (en) * | 2011-03-09 | 2011-09-14 | 东南大学 | Vehicle-mounted unit of 5.8 GHz electronic toll collection system |
| CN202049350U (en) * | 2011-03-09 | 2011-11-23 | 东南大学 | Vehicle-mounted unit of 5.8GHz ETC system |
-
2012
- 2012-08-27 CN CN201210307643.1A patent/CN103630375B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1304487A (en) * | 1999-05-11 | 2001-07-18 | 罗伯特·博施有限公司 | Diagnostic test device for motor vehicles which comprises portable testing apparatus |
| CN101031455A (en) * | 2004-08-24 | 2007-09-05 | 夏普株式会社 | Display system |
| CN101136069A (en) * | 2007-09-18 | 2008-03-05 | 深圳市金溢科技有限公司 | Issuing method of ETC electronic label |
| CN102184576A (en) * | 2011-03-09 | 2011-09-14 | 东南大学 | Vehicle-mounted unit of 5.8 GHz electronic toll collection system |
| CN202049350U (en) * | 2011-03-09 | 2011-11-23 | 东南大学 | Vehicle-mounted unit of 5.8GHz ETC system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103630375A (en) | 2014-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103630375B (en) | A kind of method for diagnosing faults of board units, board units and system | |
| CN203386245U (en) | Electronic toll collection (ETC) on board unit on-line issuing system combining mobile terminal | |
| EP0425961A2 (en) | Automatic toll exaction system for urban and extraurban highways, for bridge and tunnel crossings and for accesses to urban areas and car parks | |
| CN112152673B (en) | CPC card transaction testing method and device under antenna interference | |
| HUE028808T2 (en) | Inherently fail safe processing or control apparatus | |
| CN101136069A (en) | Issuing method of ETC electronic label | |
| CN1971656A (en) | Electronic testing system capable of managing motor vehicles and driver reliably | |
| CN102486884B (en) | Point-of-sale (POS) machine with use region limitation function and method thereof | |
| US20020002443A1 (en) | Multi-level architecture for monitoring and controlling a functional system | |
| CN112016520B (en) | Traffic violation credential generation method and device based on AI, terminal and storage medium | |
| CN113313849B (en) | Electronic transaction method, device, computer equipment and storage medium | |
| CN104424664A (en) | Vehicle payment-information processing method and system in parking lot | |
| CN108038763A (en) | The shared control loop and method of a kind of private car | |
| CN103679823B (en) | OBU and its implementation, ETC system and the OBU of compatible multiple application initialize | |
| CN111667596A (en) | Vehicle integration system | |
| CN106354127A (en) | Onboard equipment information brushing and writing control method and system based on CAN | |
| CN106296839A (en) | The safety certifying method of a kind of anti-pintle hook lock and ETC system | |
| CN203386246U (en) | Electronic toll collection (ETC) vehicle-mounted electronic label on-line issuing system | |
| CN100433071C (en) | System and method for automatically collecting vehicle information | |
| JP5295716B2 (en) | Automatic ticket gate and automatic ticket gate system with safe mode | |
| CN110827427A (en) | Expressway portal system protection method based on multi-service fault tolerance | |
| CN112235015B (en) | CPC card pre-reading mechanism test method and device | |
| JP2001067504A (en) | Toll collection system, portable terminal, and method for maintenance test of toll collection system | |
| CN109543868A (en) | A kind of about vehicle approaches to IM and relevant apparatus | |
| CN108945007A (en) | A kind of on-site verification system of CTCS-4 grades of train control system ground installation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB02 | Change of applicant information |
Address after: Nanshan District Keyuan Road Shenzhen city Guangdong province 518057 Tsinghua building A building 12 layer Applicant after: SHENZHEN GENVICT TECHNOLOGY CO., LTD. Address before: Nanshan District Keyuan Road Shenzhen city Guangdong province 518057 Tsinghua building A building 12 layer Applicant before: Shenzhen Jinyi Technologies Co., Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: SHENZHEN JINYI TECHNOLOGIES CO., LTD. TO: SHENZHEN GENVICT TECHNOLOGY CO., LTD. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |