BAR-97 Software Specification
Pages 1 - 40
1 - 40
Section 3 specifies the software requirements for BAR-97 emission inspection systems (EIS). It includes inspection procedures, sequences, decisions, responses and prompts, as well as necessary information to be loaded, security issues, lockouts, file structures, etc. It also contains requirements for communication with the BAR's Vehicle Information Database (VID).
3.2 EIS SOFTWARE COMPONENTS
The program software used in the
EIS shall consist of a process control system as well as data look-up files. The software consists of inspection test procedures and criteria; necessary station, technician, and vehicle information; security measures, utilities and ancillary modules. Its features include vehicular emission measurements of HC, CO, CO2, NO and O2, engine RPM measurements, exhaust dilution determinations, bar code scanning, interface with a dynamometer, communication to and from the VID, etc.
The software shall ensure the EIS accurately operates within specified standards and records and transmits valid test data. The EIS shall identify inaccuracies and prohibit vehicle inspection until the inaccuracies are corrected.
The EIS shall allow performing official two-speed idle test (TSI) and related program functions such as, calibration, Manual Testing Mode, etc. without dynamometer and NOx measurement device being present.
Manufacturers shall permit BAR access and provide the necessary tools to view to all parameters that are used for 'self diagnostics' if the parameters are not 'hard coded' in the software. Parameters include items such as:
- Variables for calibration frequencies.
- Variables for allowable bench drift i.e. how much drift does the EIS allow prior to determining there is a problem.
- Variables for determining how often or severe a problem must be prior to locking the unit out.
- Variables for 'self correction' i.e. if an EIS was on a more frequent calibration schedule, but the problem that caused the more frequent calibration schedule was no longer present.
The variables shall be accessed through the QA/State menu.
When data is being stored or accessed, the computer shall display a message indicating that the disk is in operation and the EIS shall not be moved or disturbed. Following each disk read/write operation, the hard disk read/write head shall be moved to a safe position and parked.
3.2.2 Boot-up Configuration
On each POWER ON, the EIS shall automatically self-diagnose all computer systems, including memory checking, hard disk and loading of all necessary operating software without technician intervention. If any corruption is found on the hard disk during the hard disk check and if check files are saved (usually saved as *.chk files), then the check files must be deleted so that the hard disk will not contain an excessive number of these files. Upon satisfactory computer component checkout (including hard disk data structures), the application software shall present a menu of available EIS operations. All offered features shall be menu-driven. For smog check related features, context-sensitive, on-line help shall be provided which can be accessed preferably with a single keystroke.
3.2.3 Software Modifications and Software Update
Periodic software updates will be necessary. Software updates may be required by the BAR or the manufacturer. In either case, the manufacturer is responsible for installing the software in their respective EIS units throughout the state. The cost of the software update is the responsibility of the EIS owner if the software update is required by the BAR, and is the responsibility of the manufacturer if they require the update. (Software update costs are not required to be included as part of the EIS cost.)
Updates to the software specifications will be provided to the manufacturers by the BAR. The manufacturers shall provide the software code to the BAR upon each update. The software version number is to be indicated on the EIS status screen, on each vehicle test record and the VIR. The version number shall consist of a four digit numeric code to be made up of the last two digits of the year, followed by a two-digit version number.
All software updates shall cause the software version number to change. There will be a separate field in the test record indicating the software version currently in use and another field used to indicate the version number that the software will be updated to when its activation date is reached. This will permit the BAR to search the records prior to the update activation date to determine how many EIS units have been updated by looking at the update field. The update field in the test record shall go blank when the update is activated.
Areas in the software where changes or additions might be required include: preconditioning procedures and emission test sequences (as applicable for ASM and two-speed idle tests), various lookup tables, functional tests, diagnostic and repair procedures, data communication procedures, criteria affecting emission standards selection or referral of failing vehicles to the Referee/Test-Only Center, vehicle exemptions, capability to read on-board diagnostics fault codes and vehicle pass/fail criteria. Other areas not specifically mentioned may also be impacted at some point, but we do not expect to request changes in all these areas at once.
To maintain the integrity of California's I/M program, QA and BAR field personnel will be instructed to lock out EISs that have unauthorized modifications or are running unapproved software versions. The following criteria apply to software and hardware updates:
a) Only BAR-approved software shall be used in an EIS. BAR intends to accommodate software developed by third parties as long as system security and integrity are not compromised. In addition, the BAR may initiate the development of software updates by third parties for use in all EISs . If BAR initiates development of a software update, manufacturers shall cooperate with BAR and/or a BAR-approved third party. (This section does not prohibit manufacturers from charging reasonable fees for software updates or from requiring nondisclosure agreements when software updates are developed by third parties.)
b) All proposed software updates must be thoroughly tested by the manufacturer before being submitted to the BAR. Update disks as well as electronically transmitted updates shall be encrypted in a manner approved by the BAR. The EIS shall be capable of accepting software updates via CD, or floppy disk.
c) All proposed software updates generated by the manufacturer shall be submitted to the BAR with a written description of the reason for the update, such as the problem that the update corrects.
d) All submitted software updates, including manufacturer-generated updates, must be submitted to BAR for testing and approval as follows:
1. Software updates must be submitted on a mutually agreed upon medium.
2. Each new software version submitted to the BAR, including minor revisions, must have a new and unique software version number.
3. All proposed software updates must be accompanied by a cover letter with the following information:
i. A description of all of the changes contained in the proposed software update, including manufacturer-initiated modifications.
ii. A timeline of when the update is expected to be installed (start to finish) and how many units will be updated.
iii. If any hardware modifications or special procedures are needed to perform the software update, describe the procedures for performing the update.
4. All submitted software updates for the EIS must be accompanied by a data disk containing at least 74 total records for both ASM and Two-Speed Idle tests as shown in Table 1 below. BAR may require the completion of BAR supplied 'test scripts' instead of the tests listed below. BAR will determine if the 'test scripts' must be completed instead of the tests listed below prior to software submittal.
TABLE 1 - REQUIRED TEST RECORDS
# OF RECORDS
Fail (HC, CO, NO)
Fail (HC, CO)
Fail (HC, NO)
Fail (CO, NO)
Fail (ECS Visual)
Fail GP (HC, CO, NO)
Fail GP (HC)
Fail GP (CO)
Fail GP (NO)
Fail GP (HC, CO) W/ Repairs
Fail GP (HC, NO)
Fail GP ( CO, NO)
Tamper (ECS Visual)
i. The data disks shall also contain at least 20 complete calibration records - (10 complete three-day calibrations; 5 EIS gas calibration; 3 dynamometer calibration and 2 fuel cap tester calibration)
ii. The records must be generated by the EIS and should include all items required per Confidential Appendix C-2.
5. Depending on the type and number of changes contained in the proposed software update, the BAR may require testing at BAR-approved beta sites prior to release of the software. BAR will perform a preliminary review of the proposed software prior to releasing it for beta site testing.
e) Pursuant to Health and Safety Code §44036, manufacturers are allowed six months from the date the BAR issues its proposed specifications for periodic software updates, to obtain approval that the updates meet the proposed specifications and to install the updates in all EIS subject to the updates. During the first 30 days of the six-month period, the manufacturers shall be permitted to review and to comment upon the proposed specifications. However, a shorter period of time may be required by the BAR upon finding that a previously-installed update did not meet the specification. A manufacturer's failure to furnish or install software updates as so specified is cause for the BAR to decertify the manufacturer's EIS Certification or to issue a citation and civil penalty up to $1,000 per day that the manufacturer fails to furnish or install the software and hardware updates by the specified period. (The BAR may allow additional time to review and comment and/or submit software updates if they are more complex.)
f) Software updates must correct all previously identified software problems.
g) The software must be able to run on all certified BAR97 hardware configurations in the field for that manufacturer.
3.2.4 Running Changes and Other Software Modifications
Any changes to design characteristics, component specifications and any modifications to the software must be approved by BAR. It will be the manufacturer's responsibility to confirm that such changes have no detrimental effect on the performance of the EIS.
3.2.5 Virus Detection Software
Each EIS unit shall contain a virus detection program, subject to BAR approval, which shall verify the integrity (i.e. check for infection/corruption) of each update disk or decompressed file before it is applied to the EIS or allowed in memory. Infected/corrupted software shall be blocked from installation.
In lieu of this requirement, the EIS manufacturer may submit for BAR's consideration written procedures clearly illustrating how the EIS manufacturer intends to meet the intent of the VIRUS PROTECTION PROGRAM requirement. These procedures shall demonstrate how the integrity of the EIS software and update software or decompressed file shall be protected under all circumstances.
3.2.6 Directory and File Structure
(This information is confidential and may only be released with prior written consent from the BAR Engineering Section.)
3.2.7 Vehicle Look-Up Table (VLT)
a) The Vehicle Lookup Table is the BAR's version of the EPA/Sierra Lookup Table (ESLT). The VLT provides basic vehicle descriptions as well as ASM testing parameters, including single-axle dynamometer compatibility data. The VLT includes emission cutpoints exception information for some vehicles.
b) The table will be periodically revised on a "by-record" basis. The EIS shall send the version date and the number of records in its VLT file to the VID during any "Begin-Test" or "Data-Refresh" communications session.
c) When a "VLT Update" file is received from the VID, the EIS shall store the file to the hard drive until a period of relative inactivity (e.g. between Smog Check inspections). VLT.DAT file update strategies shall be proposed by each EIS manufacturer and be approved by BAR. Each VLT update record will be preceded by a single character and shall be processed as follows:
"C" = replace record (same row ID),
"A" = append record (new row ID),
"D" = delete record (same row ID).
d) The VLT Update file may appear to be corrupted if either of the following conditions exist:
1. The version date sent by the EIS does not match any dates stored in the "VLT Update History" table in the VID (second consecutive occurrence).
2. The number of records in the EIS's VLT.DAT does not match the appropriate number of records for that version date (determined at the VID).
If possible corruption is detected by the VID, the VID will send a lockout to the EIS. The EIS, upon receiving the response bit, shall display the following prompt:
THE VLT DATABASE IS CORRUPT. CALL SERVICE.
If the VLT is corrupt, a lockout shall be set. This lockout can only be cleared by the VID upon replacing the file and the VID has verified that the VLT data has been replaced.
e) The EIS shall be able to use an Extended Test Parameters Table in conjunction with the VLT. This table will contain additional parametric variables to be used during either the ASM test sequence or TSI test sequence. Having these values in an accessible and renewable table will allow for vehicle specific adjustments to the test cycle without the need to update the software. The table will use a reference ID number that will link the table rows to rows in the VLT and there will be a one-to-many relationship with the VLT. This table will be periodically revised by overwriting.
3.2.8 Repair Action Information
The EIS shall display a list of all repair categories and prompt the technician to select the category or categories of the system(s) which were repaired. The technician must be able to return to the list of major categories after each subcategory has been completed without having to hit more than two keys.
All repair actions shall be documented on the vehicle inspection report (VIR), and stored in the repair record. The technician shall be required to sign on the VIR to document the repairs that have been performed to reduce emissions. The tampered vehicle repair cost shall be printed on the VIR and recorded in the Tampered Repairs (Parts and Labor) Cost field of the repair record. If further repairs are needed, the estimated cost of the additional repairs shall be printed on the VIR and recorded in the Estimated Cost of Additional Repairs field of the repair record.
The display, when in the test mode, shall be readable at a minimum distance of eight feet in a building that meets OSHA lighting standards for a garage environment. Display contrast and brightness shall be adjustable.
b) BAR Messages
BAR messages shall be transmitted by the VID to the EIS during all communication sessions except during the network diagnostic routine (loopback). BAR messages will be in text file format. All new messages shall automatically display once immediately after the technician selects Smog CheckÖÖ from the main menu. The messages shall default to print and the technician must press a function key to continue. The EIS shall save the most recent 100 messages and provide an option for later recall and print.
c) Testing Messages
During the emissions test, the EIS shall display the word TESTING on the screen. The EIS shall also display messages, if applicable, test mode, vehicle speed, dynamometer load deviation, test time, excessive exhaust dilution, low flow, driver acceleration violations, and engine RPM violations.
d) Information Not Permitted During Testing
The EIS shall not display the emission readings during the inspection. (However, during manual mode testing, the readings shall be displayed.)
e) Print Screen Capability
The EIS shall have a PRINT feature, which prints any current text or graph displayed on the screen, by depressing no more than three keys. The print feature shall always be active; however, there shall be no print capability during emissions testing.
f) Engine RPM
The EIS shall have the capability to display the engine speed up to four digits during the emissions test.
3.2.10 Pretest/Training Mode
The EIS shall have a PRETEST/TRAINING MODE feature that will allow technicians and trainees, respectively, go through a Pretest and/or a Training Mode inspection.
The Pretest feature shall allow technicians (trainees are restricted) to pre-screen vehicles for gross polluter status by performing an inspection without officially labeling the vehicle as a gross polluter. The Pretest is not an official test and therefore the EIS shall not issue certificates for passing vehicles. The Pretest shall be performed in the same manner as a Smog Check inspection except as noted. During Pretest, the EIS shall display a message on the screen that the inspection is a "PRETEST INSPECTION" and shall print "PRETEST" on the VIR. For additional VIR information, refer to Appendix C, "Vehicle Inspection Report" for Pretest sample VIRs.
If the "Invalid Station Type" response bit (bit 53) is received from the VID, the EIS shall display the following prompt, and allow the Pretest to continue.
THE PRETEST MAY CONTINUE, BUT THIS VEHICLE MUST BE REFERRED TO A "REFEREE/TEST-ONLY CENTER" FOR CERTIFICATION.
During Pre-Test, the EIS shall not prompt for repair information in accordance with §3.6.20, 3.6.21 and 3.6.22 during Pre-Test.
The Training Mode capability will be used by the manufacturers for training purchasers of the EIS, by EIS owners to train new employees, or for schools to train students. The training mode shall not require the use of a technician's access code or allow access to secured areas of hardware or software and will not communicate to the VID. The display shall show a message throughout the inspection that this is a training exercise and not an official test (no certificates shall be issued). The EIS shall print TRAINING on the VIR.
The training mode test results shall be recorded and transmitted to the VID at the next required communication session (i.e. next Smog Check, data file refresh, etc.). Do not make an "end of test call" to the VID.
3.2.11 Inspection Cost Survey
Once a month, the EIS shall query during an inspection for the cost of a smog check inspection. The EIS shall display the following prompt:
ENTER INSPECTION FEE CHARGED FOR THIS TEST (EXCLUDING CERTIFICATE).
The EIS shall provide two five-character numeric fields (XX.XX) to enter the fees the station charges for the ASM and TSI inspections. The EIS shall store the inspection cost information in the inspection cost data file and transmit the file to the VID upon next VID communication transaction.
3.2.12 Configuration Information
The EIS shall receive configuration information from the VID. The following items will be in the configuration information file:
1) Drive configuration information (Y/N). See §3.6.9 b).
Note: The EIS shall record the current status (Y/N) of the Drive Configuration to the Drive Configuration routine activated field of the test record.
2) Collect second-by-second information (Y/N). If "Y," then the EIS shall collect and send the secxsec data as per §3.6.12 c). If "N," then the EIS shall discontinue collecting and sending the secxsec data.
3) ASM activation (Y/N/B). [B = Basic area configuration]
If "Y," then all vehicles shall receive either an ASM or TSI inspection as per this specification.
If "N," then the EIS shall allow the technician to select an ASM or TSI test. The EIS shall display the ASM/TSI test selection prompt prior to any prompts related to dynamometer compatibility. Note: the software shall be able to perform a TSI test without a dynamometer or NOx measuring device installed in the EIS.
If "B", then the EIS either perform a TSI inspection or abort the test.
When the configuration is set to "B" the EIS shall perform a TSI test under the following conditions:
1. VID returns anything other than "A" in the Required Test Type field of the test record.
2. Off-line test.
When the configuration is set to "B" the EIS shall abort the test under the following conditions:
1. VID returns an "A" in the Required Test Type field of the test record.
If an "A" is received in the Required Test Type field of the test record the EIS shall display the following prompt then abort the test:
THE VEHICLE UNDER TEST MUST BE TESTED AT AN "ENHANCED AREA STATION," THE SMOG CHECK WILL BE ABORTED.
Note: The EIS shall record the current status (Y/N/B) of the ASM activation to the ASM testing enabled field of the test record.
4) RPM limits (low/high, low/high). The EIS shall use the limits in the configuration file for all ASM tests, except when an extended parameters record is used. The order of the RPM limits shall be as follows. The first two numbers shall be the lower limit for engines less than or equal to 3.0L. The next two numbers shall be the upper limit for engines less than or equal to 3.0L. The next two numbers shall be the lower limit for engines greater than 3.0L. The last two numbers shall be the upper limit for engines greater than 3.0L. All limits shall be multiplied by 100 to determine the actual limit. The lower limit applies to manual transmissions only; automatic transmissions shall use 100 RPM for the lower limit. See §3.6.12.a.12, & Appendix C-4.
Example: if the engine size = 5.0L then use the appropriate lower limit in the configuration file times 100 as the lower RPM limit and the appropriate upper limit in the configuration file times 100 as the upper RPM limit.
5) Dynamometer scale lockout percentage thresholds (low/high). The EIS shall use these limits to determine if the dynamometer scale is out of calibration. See §3.6.12.a.7 & Appendix C-4.
6) Equivalent Test Weight percentage thresholds (low/high). See §3.6.12 a. 4.
7) Perform OBD II check (Y/N). If "N", then only perform the visual portion of the OBDII system check. If "Y", then perform the OBDII check as listed in section 220.127.116.11.3.
Note: The EIS shall record the current status (Y/N) of the Perform OBD II check to the Check OBD II field of the test record.
8) Fast Pass (Y/N). If 'Y', the EIS shall perform a 'fast pass' during the ASM test if all the 10-second average emission readings are simultaneously below the applicable standards. If 'N', the EIS shall use the final 10-second average emission readings for the overall emission results. The EIS shall default to 'N' if the fast pass field is not filled with 'Y' or 'N' in the configuration file. See §3.6.12.d & §3.6.12.e
Note: The EIS shall record the current status (Y/N) of the Fast Pass to the Fast Pass field of the test record.
3.2.13 VLT Exceptions
During the "begin test" communication to the VID, if there is a match with the VIN and license plate number, a Vehicle Specific VLT (which provides unique information for the vehicle under test) may be sent to the EIS from the VID. When sent, the information in the VSVLT shall be used instead of the information in the EIS resident VLT. The VSVLT will have the same layout as the VLT. The technician must enter vehicle information not received from the VSLT.
In most cases, exception vehicles are vehicles that have been identified by the State Referee as having special features, such as an engine change. These vehicles are also identified with a Referee Label Number.
3.3 SOFTWARE MODULES
3.3.1 Technician and Station License Numbers and Other Numbers
The technician's license number and access code shall reside in both the EIS and the VID. The EIS shall determine the validity of the technician's access code, and the VID shall confirm its validity at initial contact.
In addition, the EIS shall not be allowed to go into the inspection mode unless valid entries have been made for station number, PEF value, calibration gas values, certificate numbers, and at least one licensed technician.
The EIS shall have the capacity to store at least 99 technician access codes and 99 corresponding technician license numbers. Only the VID can add, change or delete the technician's access code and corresponding license number. Station and technician license numbers begin with two alpha characters which are followed by six numeric characters.
b) Technician Access Codes:
The EIS shall require the technician to enter a special access code before an inspection can begin. The access code shall neither be displayed nor printed on the VIR. This special access code number shall be linked to the technician's license number and is described in the Confidential Appendix C-2.
c) Technician License Numbers:
A technician's license number reflects the type of license the technician possesses. The EIS shall automatically abort the inspection and display a message indicating that the technician has not obtained the proper license number and/or endorsement from the BAR.
The two alpha characters in the technician license will be one of the following: EA, EO, EB, EI or GU . A description of these licenses can be found in the test record layout in Confidential Appendix C-2.
BAR may require update training prior to performing certain test or repair related activities. A special identifier, not shown on the technician's badge or as part of the license number, will be referred to as an endorsement. Specific endorsements will be developed by the BAR as the need arises. Currently, only the "A" (ASM), "G" (Gaseous Fuel), "B" (Both ASM and Gaseous Fuel) and "N" (None) endorsements exist. Records of these endorsements will reside in the VID and the EIS (refer to Confidential Appendix C-2).
d) Station License Number:
The station license number shall be entered into the EIS during initialization. Only valid station license prefixes may be entered into the EIS.
Station license prefixes beginning with an R and C indicate that the station is licensed to test and repair all classes of vehicles; therefore, the EIS must allow tests on light, medium- and heavy-duty vehicles.
Station license prefixes beginning with a T indicate that the station is licensed to test, but not repair, all classes of vehicles; therefore, the EIS must only allow tests on light, medium and heavy-duty vehicles.
Station license prefixes beginning with a D or F indicate that it is a fleet station and licensed to test and repair only those vehicles registered to their fleet.
Station license prefixes beginning with a G indicate that it is a government fleet station licensed to test and repair government fleet vehicles.
Station license numbers that begin with H or K are only licensed to test and repair vehicles over 8500 pounds.
Station license numbers that begin with P or V are only licensed to test vehicles over 8500 pounds.
Station license prefixes beginning with a S indicate that it is a training facility. Training facilities shall be blocked from performing official smog checks; however, training facilities are allowed to perform pretests, and training mode inspections.
Station license prefixes beginning with a Q, Y or Z shall be reserved for future expansion.
Valid entries for the second alpha character of the station license are A-N (A-Z for government fleet stations). The remaining 6 digits are numeric and unique to each station. The station license number shall be placed in the Station License Number field of the test record and on the VIR. This field must be populated in the test record for every valid test record sent to the VID.
Government fleet stations with license numbers that begin with the alpha character G, shall only be required to make one front-end call to the VID. If the VID has a match, the VID shall transfer the vehicle data to the EIS. However, if a match is not found as a result of the front-end call to the VID, the EIS shall not require the technician to initiate a second call to the VID. The EIS shall allow the inspection to proceed without making a second initial call. The test will default to government fleet vehicle and a certificate will not be issued. (Note: Provisions regarding certificate numbers and certificates purchased as well as lockouts associated with certificates do not apply to government fleet stations.)
Provisions regarding certificate numbers and certificates purchased as well as lockouts associated with certificates do not apply to training facilities.
e) Test Record Number
The EIS shall give each valid test a consecutive number. A valid test consists of a completed test with an overall pass or fail (including a tamper or gross polluter identification) test result that shall be transmitted to the VID. The record number shall be written to Test Record Number field of the test record. This field is numeric and has a length of 6 digits. When the number reaches 999999, the number shall be reset to 000001. This field must be populated in the test record for every valid test record sent to the VID.
f) EIS Number
The EIS number shall be unique for each EIS unit in the state of California. The first two characters of the EIS number are alpha. These two characters shall be assigned to each manufacturer upon certification of that manufacturer's EIS unit. The following 6 digits shall be unique to each EIS made by a manufacturer. The EIS number shall be written to the EIS Number field of the test record. This field must be populated in the test record for every valid emissions test record sent to the VID. Print the EIS number on the VIR.
g) Loaded Software Version Number
This field shall contain the version number of the software that is currently being used by the EIS. The loaded software version number shall be written to the Loaded Software Version Number field of the test record and printed on the VIR. This field must be populated in the test record for every valid test record sent to the VID.
h) Update Software Version Number
This field shall contain the version number of the update software that is currently loaded but not being used by the EIS. Update Software Version Number field of the test record must be populated if the EIS has update software loaded. At a predetermined date, the update software shall become the loaded software version, and the old version shall be discarded. After the update software version turns into the loaded software version, the Update Software Version Number field shall be blank.
i) VID Identification
The VID-ID is a record identifier generated by the VID. The VID shall assign an ID number to a test record which shall be transmitted to the EIS at the time of the begin test call. The ID will be written to the VID-ID field of the test record. The VID-ID shall not be modified by the EIS and shall be transmitted back to the VID during end-of-test contact.
j) DMV ID Number
When a certificate is issued, the DMV-ID number (described in Confidential Appendix C-3) shall be printed on the VIR, and written to the DMV-ID field of the test record for every passing inspection.
3.3.2 EIS Lockout Reasons
The EIS shall be prohibited from performing an inspection for any of the following reasons:
- Clock Lockout
- Warm-up in progress
- Warm-up failure
- Dynamometer warm-up in progress (See Note 3)
- Dynamometer calibration required (See Note 3)
- Dynamometer calibration failure (See Note 3)
- Dynamometer failure (See Note 3)
- Gas calibration required
- Gas calibration failure
- Gas analyzer failure
- Fuel cap tester failure
- Fuel cap tester out of calibration
- Oxygen sensor out of calibration
- Dyno lift failure
- Leak check required
- Leak check failure
- EIS tampering
- Out of certificates (see Note 2)
- Hard disk is full
- Floppy disk or disk mechanism failure
- Hard disk or disk mechanism failure
- QA/State EIS lockout
- EIS initialization (data missing, incorrect or incomplete)
- No communication with VID in XXX days and XXX tests (see Note 1)
- Station license suspended
- Station license revoked
- Station license expired
- Failure to pay for certificate numbers purchased
- Failure to pay for communications services
- Certificate sequencing error (see Note 2)
- Calibration Gas Cylinder Violation
- State disk drive tampering
- VLT Corrupt
- Dynamometer scale failure (See note 3)
- Excessive Number of Aborts
1. This lockout shall be set whenever (xxx inspection) fifty inspections (running total) have been performed by the EIS within five consecutive days without communicating to the VID. The VID sets the no contact limit and number of inspections allowed. The lockout can be cleared by QA/State personnel or by the VID HELP DESK in accordance with pre-established procedures. See Confidential Appendix C-2 for additional detail.
2. Not applicable for government fleet stations, or training facilities.
3. Dynamometer failures shall only prevent ASM inspections; two-speed idle inspections will be allowed to continue. See §3.9 a) for additional detail.
3.3.3 Fleet File Number
This field shall serve two purposes:
a) To record the file or identification number of fleet or military personnel vehicles.
b) When applicable, to identify a vehicle under test as a government fleet or military personnel vehicle, and as such, to prevent issuance of a certificate upon passage of the inspection.
This field shall contain the government fleet file number, PFR file number or military personnel identification number. The entry can be identified by the first character of the number. The data shall be recorded in the File Number Storage field of the test record.
3.3.4 Military Personnel Vehicle (Out-of-State)
Before transmitting the VIN/license plate number to the VID, if the vehicle has an out-of-state license plate, the EIS shall prompt the technician to ask if the consumer is seeking California DMV registration as follows:
IS THE CONSUMER SEEKING CALIFORNIA DMV REGISTRATION? (YES/NO)
1) If YES (consumer is seeking California DMV registration), continue the inspection.
2) If NO, determine if the consumer is in California on military assignment.
IS THE CONSUMER HERE ON MILITARY ASSIGNMENT? (YES/NO)
3) If YES, the inspection shall continue and the EIS shall build a military personnel identification number and print it on the VIR. The EIS shall store this number in the File Number Storage field of the test record. The EIS shall not issue a certificate.
1. Military Personnel Identification Number
Character Description 1 "M" 8 Last 7 characters of VIN
2. DISPLAY PROMPT:
NO CERTIFICATE SHALL BE ISSUED FOR THIS VEHICLE.
4) If NO, no inspection is required and the test shall be aborted.
3.3.5 Waiver and Hardship Extension
If a vehicle has a previous waiver or hardship extension on record, as indicated by the VID, then the technician shall be prompted to inform the consumer that no repair cost minimum applies if the vehicle fails the inspection. The EIS shall display the following message:
THIS VEHICLE HAS A PREVIOUS WAIVER OR HARDSHIP EXTENSION ON RECORD. THE VEHICLE IS NOT ELIGIBLE FOR ANOTHER WAIVER OR HARDSHIP EXTENSION. COST LIMITS DO NOT APPLY.
If the vehicle has a previous waiver or hardship extension on the record, the EIS shall print the following appropriate message on the VIR:
THIS VEHICLE HAS A PREVIOUS WAIVER ON RECORD.
THIS VEHICLE HAS A PREVIOUS HARDSHIP EXTENSION ON RECORD.
THE VEHICLE SHALL BE REFERRED TO THE REFEREE/TEST-ONLY STATION FOR ISSUANCE OF A CERTIFICATE OF COMPLIANCE.
In addition, the EIS shall write "W" for waiver or "H" for hardship to the Previous Waiver/Hardship Extension Issued field of the test record and the EIS shall also print the WAIVER/HARDSHIP EXTENSION ELIGIBILITY MESSAGE on the VIR. The EIS shall prohibit issuance of a certificate of compliance if the vehicle has a hardship extension even if the vehicle passes the inspection.
3.3.6 Emissions Recall Notice from DMV Records
The EIS receives emissions-related recall registration block from the VID. This information shall be stored in the Manufacturer Recall ID (DMV) and Manufacturer Date of Recall (DMV) fields of the vehicle test record. If a repair record exists for the vehicle under inspection, the information shall also be written to the Manufacturer Recall ID (DMV) and Manufacturer Date of Recall DMV) fields of the repair record.
If information from the VID indicates that a DMV-installed emissions-related recall registration block exists on the test record, and no evidence was provided during the inspection to indicate compliance, then the EIS shall print the following message on the VIR:
DMV HAS PLACED AN EMISSIONS-RELATED BLOCK ON YOUR VEHICLE REGISTRATION. THE EMISSIONS-RELATED RECALL NUMBER IS XXXXXXXX (MFR'S RECALL ID). PLEASE CONTACT YOUR DEALERSHIP TO COMPLY WITH THE EMISSIONS RECALL REQUIREMENT.
3.3.7 Applicable Model Years
1. The EIS shall not accept any vehicle model year older than 1966, or newer than the current calendar year plus two. Any attempt to make such an entry shall cause the EIS to display one of the following prompts:
DO NOT TEST VEHICLES OLDER THAN 1966.
DO NOT TEST VEHICLES NEWER THAN THE CURRENT YEAR PLUS TWO.
2. The EIS shall display the following prompt anytime the technician enters a model year that is less than five years old. Example: the current year is 1999, display the prompt for 2001, 2000, 1999, 1998, 1997, and 1996.
VEHICLES LESS THAN FIVE YEARS OLD ARE EXEMPT FROM BIENNIAL SMOG CHECKS. DO YOU WISH TO CONTINUE? (Yes/No)
1. If "YES", the EIS shall continue with the inspection. If "NO", the EIS shall abort the inspection.
3.3.8 Vehicle Information Entry
The full name of each vehicle make must be displayed and printed on the VIR, but only the first five characters of each make name shall be recorded on the test record. Based on the VIN, license plate number (and vehicle registration zip code), the VID (given a match) shall down-load the vehicle make, model name, model year, engine size, number of cylinders, transmission type, certification type, vehicle type, inspection reason, fuel type, vehicle test parameters and, if applicable, GVWR, fleet file number, referee label number, engine make and engine year. Since the VID does not always have complete information or the EIS to VID communication may have not been successful, the technician may have to enter some or all of this information manually. (See §3.6.6.g)
For each inspection the technician shall always enter the following information: odometer reading, and dual exhaust (if applicable).
3.3.9 Underhood Inspection
The technician shall be required to make an entry for each of the items on the list provided in §3.6.18 before proceeding to the next item. However, if the technician fails to make an entry for every item on the list, then a message shall be displayed indicating that an error was made. Edit capability shall be provided for all entries prior to continuing the inspection. A HELP screen shall also be provided to advise the technician to refer to the vehicle's underhood emissions control system label as the primary source of information to determine what emission control devices are required on a particular vehicle or else use a current emissions control application guide.
3.3.10 Emission Standards
The emissions standards category (ESC) tables (Appendix A) shall reside in the EIS and receive updates from the VID.
The EIS shall look into the VLT for emission cutpoints. If not available, the EIS shall use the ESC table.
The ESC tables shall also have a version number. Upon implementing the new ESC table, the old version shall be purged. Additional standards categories may be added at a future date.
Based on the vehicle information entered, the EIS shall determine the emissions test standards for the vehicle being tested. For all ASM tests that do not have emission standards in the VLT or VSVLT, the proper ESC category shall be determined as follows:
For vehicles that have a test weight (equivalent test weight, inertia weight class, measured test weight) less than or equal 3750 lbs. and the GVWR is less than 8501 pounds use the appropriate ESC record (based on model year, vehicle type, and GVWR) from TABLE1.DAT. If the vehicle test weight is greater than 3750 pounds, or the GVWR is greater than 8500 pounds use the appropriate ESC record from TABLE4.DAT. If the GVWR is not available select the appropriate table based on the vehicle test weight.
For each vehicle, the ESC will contain HC, CO, and NO Pass/Fail and Gross Polluter values and average emissions for non-polluting vehicles for ASM and two-speed idle tests. Print these emissions values on the VIR. The ESC tables also contain CO + CO2 dilution thresholds, GVWR and engine speed limits. Emission standard category values and the criteria for selecting categories shall be designed in a manner that allows for easy modification or addition.
Minimum dilution limits shall be determined before the Dilution Correction Factor (DCF) is applied to the emission measurements. Dilution measurements shall be based on the sum of CO and CO2. The EIS shall prevent testing if the uncorrected CO + CO2 value or the engine speed signal are outside the BAR specified thresholds. (Use the value on the ESC table for the minimum dilution limits, except that CNG- and LPG-powered vehicles shall use the table limits minus two. For example, if the minimum CO + CO2 was 7, the minimum for CNG-powered vehicles would be 5.)
The ESC for the vehicle under test shall be written to the Emission Standards Category field of the test record, and the ESC Version number for the vehicle under test shall be written to the ESC Version Number field of the test record.
3.3.11 NO Humidity Correction Factor
Nitric oxide (NO) readings shall be multiplied by the following factor to correct for ambient humidity effects on NO generation in engine combustion.
Kh = e[0.004977*(H-75)-0.004447*(T-75)]
where Kh = NO Humidity Correction Factor (Note cap HCF at 2.31; if greater than 2.31 use 2.31
H = Absolute humidity, grains of water per pound of dry air,
T = Temperature degrees Fahrenheit
Ra = Relative humidity (RH) of the ambient air, percent
Pd = Saturated vapor pressure, mm Hg, at the ambient dry bulb temperature. Pd vs. temperature data may be extracted from such sources as the Handbook of Chemistry & Physics (CRC Press).
PB = Barometric pressure, mm Hg
The following factors shall be written to the test record in the ATMOSPHERIC CONDITIONS section: Relative Humidity, Ambient Temperature, Barometric Pressure, Humidity Correction Factor.
3.3.12 Dilution Correction Factor
The EIS shall apply a DCF to the HC, CO, and NO inspection emissions results. The EIS shall look in the VLT for the minimum dilution threshold of CO + CO2. If the minimum dilution threshold does not exist in the VLT, the EIS shall default to 6%, except for vehicles running on CNG or LPG which shall default to 4%. This dilution correction accounts for any exhaust sample dilution, intentional or unintentional, occurring during inspection. The EIS shall calculate the DCF using the following procedure, and shall preselect the formula appropriate to the vehicle's fuel type. If the calculated DCF exceeds 3.0, a default value of 3.0 shall be used. If the DCF falls below 1.0, then a default value of 1.0 shall be used.
a) Calculate "x" using the EIS measurements of CO and CO2:
where [CO2]meas. and [CO]meas. are the final readings of each mode of the inspection (for example, ASM 5015, ASM 2525, 2500 RPM and idle).
b) Calculate the [CO2]adj. using the following formulas.
For Methanol or Ethanol:
For Compressed Natural Gas (CNG):
For Liquid Propane Gas (LPG):
c) Calculate the "Dilution Correction Factor" as follows:
Corrected HC = Observed HC x DCF
Corrected CO = Observed CO x DCF
Corrected NO = Humidity Corrected NO x DCF
The DCF shall NOT be applied to the CO2 reading.
The EIS shall apply the DCF to the final emission readings of the inspection to calculate the dilution-adjusted values. The EIS shall then compare the dilution-adjusted values against the vehicle's emission standards to determine the pass/fail or gross polluter status of the vehicle. The dilution-adjusted values shall be the final emission readings for the test vehicle. They shall be printed on the VIR as AMOUNT MEASURED and shall be stored in the test record. The EIS shall record the DCFs on the DCF - Dilution Correction Factor (ASM5015 or TSI-2500 RPM) and DCF - Dilution Correction Factor (ASM2525 or TSI-Idle RPM) fields on the test record. The values recorded shall be the calculated DCF values, not the default values.
3.3.13 Engine RPM Detection
Based on the vehicle identification information entered by the technician, the EIS may assist the technician in determining which vehicles require a primary pick up, which require that an alternate counting algorithm be used, and which require the use of an auxiliary piece of equipment. Prompts may be provided to assist the technician in locating an RPM signal on vehicles equipped with distributorless ignition systems (DIS).
The EIS shall record the engine RPM simultaneously with the emissions readings. If the EIS does not read engine RPM in the proper range, the EIS shall prohibit continuation of the inspection until proper RPM range has been achieved. (Manufacturers may propose an error tolerance factor to be used when testing vehicles with unstable RPM.)
For 1996 and newer vehicles, the OBD-II SAE standardized connector link shall be capable of providing the tachometer signal. See §3.6.11 for "RPM Signal."
3.4 EIS ACCESSORY RECOGNITION
3.4.1 Bar Code Scanner
The EIS shall detect the presence of the bar code scanner automatically at POWER ON. During the inspection, if the bar code scanner cannot successfully scan, the technician's badge license number (after each attempt), the VIN (after each attempt), the VIN and license plate numbers from the DMV registration document, or the bar code labels from the calibration gas cylinders, a message shall be displayed advising the technician that the bar code is not readable and the technician shall have the option of trying again or entering the necessary information manually. To help ensure the accuracy of manual entry, all bar-coded information (VIN, license plate, etc.) must be entered twice (dual entry method in which entry is not displayed). Dual entry method shall be two-in-a-row correctly entered and both entries must match before the data is accepted. The EIS shall provide prompts on how to manually enter all bar-coded information.
The modem shall be connected to a fully operational dial-up connection during all times of operation. The modem must be IBM-PC and MS-DOS compatible and show full ASCII file transmission compatibility. The manufacturer must provide all necessary software and protocol for the modem.
3.5 SMOG CHECK MENUS
The following menus are required. The BAR reserves the right to require modification of any menu if we feel it does not meet the minimum requirements.
3.5.1 Main Menu
The main menu shall display the following options:
1. SMOG CHECK
1. REPAIR-ONLY SOFTWARE FUNCTION
3. MANUAL TESTING MODE
4. EIS CALIBRATION MENU
5. STATUS PAGE
6. NETWORK COMMUNICATIONS DIAGNOSTICS
7. PRETEST or TRAINING MODE
8. RECALL PREVIOUS VEHICLE TESTS
9. QA FUNCTIONS
10. STATION MANAGER MENU
11. RECALL BAR MESSAGE
A detailed description of each menu item follows.
3.6 SMOG CHECK
The EIS shall initiate, run and terminate the I/M inspection sequence in accordance with the BAR-97 EIS specifications.
3.6.1 Technician License Number Entry
The license number shall be obtained by scanning the technician's badge. It must match a license number stored internally in the EIS. The EIS shall not allow license numbers from wall-mounted licenses. The technician's badge contains a bar-coded license expiration date. Whenever a technician scans the badge, the EIS shall verify the license expiration from the expiration date stored in the Technician Information Table. If the license has expired, the EIS shall prohibit the technician from performing an inspection. (If the expiration date in the Technician Information Table is blank, the EIS shall capture the expiration date from the technician's badge and write it to the appropriate location in the Technician Information Table.)
SCAN THE BAR CODE ON YOUR TECHNICIAN BADGE OR PRESS --- (function key) FOR MANUAL ENTRY.
1) If the expiration date from the bar code differs from the expiration date within the EIS, then the date within the EIS takes precedence. If a technician whose license number has expired initiates an inspection, the EIS shall not allow the inspection and shall display the following message:
THE TECHNICIAN LICENSE HAS EXPIRED. YOU CANNOT PERFORM AN INSPECTION OR REPAIR. CONTACT YOUR LOCAL BAR FIELD OFFICE.
2) The validity of a technician's license number and access code will be verified by the VID at the time of initial contact with the VID. If a technician scans a bar-coded technician license number that is not stored in the Technician Information Table, the EIS shall display the following message:
THE TECHNICIAN LICENSE NUMBER IS NOT IN THE EIS. CONTACT YOUR LOCAL BAR FIELD OFFICE.
3) The VID shall install a lockout for licenses that have expired, been suspended or revoked. If the technician's license expiration date information doesn't reside on the EIS, the VID shall send this information to the EIS upon initial contact. If a technician that has an expired license, been suspended or revoked initiates an inspection, the EIS shall display the following message:
TECHNICIAN LICENSE HAS BEEN EXPIRED, SUSPENDED OR REVOKED. YOU CANNOT PERFORM SMOG CHECK TESTS OR REPAIRS. CONTACT YOUR LOCAL BAR FIELD OFFICE.
4) In cases where the badge cannot be successfully scanned, the technician shall be given the option of manual entry via the following prompt:
ENTER YOUR TECHNICIAN LICENSE NUMBER.
5) The bar code scanner shall be used whenever possible. To help ensure the accuracy of manual entry, the license number must be entered correctly twice (dual entry method). Both entries must match before proceeding with an inspection.
BOTH ENTRIES ARE NOT THE SAME - TRY AGAIN.
6) After the technician's license number has been manually entered, the EIS shall display the following message:
YOU USED MANUAL ENTRY. IF YOUR BAR CODE SCANNER IS NOT WORKING, PLEASE GET IT REPAIRED. IF YOU DO NOT HAVE A TECHNICIAN BADGE LICENSE, PLEASE CONTACT YOUR LOCAL BAR FIELD OFFICE. BAR WILL INVESTIGATE FREQUENT USE OF MANUAL ENTRY.
7) Technician license numbers shall be two alpha characters followed by six numeric characters. The following technicians are authorized to perform enhanced ASM inspections if they have an ASM update training certification and license endorsement stored in the Technician Information Table. The initial two alpha characters are as follows (where nnnnnn represents the numeric portion):
EAnnnnnn Advanced Emission Specialist
EOnnnnnn Test-Only Technician
The EIS and VID shall also accept a license number that begins with a GU. This license number is only a placeholder for government fleet technicians. The government fleet technicians shall enter the number assigned to them by the BAR. Since bar code scanners are optional for government fleets, manual entry of GU license numbers must be allowed and the display prompt in Item 6) above should not be displayed. Government fleet technicians shall be allowed to perform tests only on government fleet vehicles. There will be no certificate issued to these vehicles. The format is as follows (where nnnnnn represents the technician's personal ID number):
GUnnnnnn Government Unlimited Technician (Government fleet only)
If accepted by the VID and/or EIS, the technician license number shall be written to the Test Technician License Number field of the test record.
If an ASM test is required and the technician does not have an ASM endorsement, the EIS shall display the following prompt:
TECHNICIAN IS NOT LICENSED TO PERFORM AN ASM INSPECTION. THE SMOG CHECK IS ABORTED.
8) Technician license numbers with the following two alpha characters shall not be allowed to perform enhanced inspections.
EBnnnnnn Basic Area Technician
EInnnnnn Intern Technician
9) A technician who is licensed to perform inspections only in the Basic Area shall not be allowed to perform tests on Enhanced Area vehicles. In this case, upon connecting to the VID, the VID shall determine, based on the technician's license number and endorsement status, whether or not a technician is licensed to inspect vehicles in an Enhanced Area. If a technician is not licensed to inspect vehicles in an Enhanced Area, the VID shall return the appropriate response to the EIS. The EIS shall display the following message:
TECHNICIAN IS NOT LICENSED TO PERFORM AN INSPECTION ON AN "ENHANCED AREA VEHICLE" AND THE SMOG CHECK IS ABORTED.
10) The VID shall transmit technician license numbers, expiration dates and endorsements to the EIS. The EIS, upon receiving this information from the VID, shall read and store this information in the appropriate locations within the Technician Information Table. Print the technician's name and license number on the VIR.
11) In the case of bar code entry, the EIS shall store a B (bar code scanner) in the Technician License Input Source field of the test record; otherwise an M shall be stored to indicate manual entry. This field must be populated for every valid test record sent to the VID.
12) The EIS shall block intern technicians from performing Smog checks, and pretests. Intern technicians shall be allowed to enter repair data in the repair only software menu.
3.6.2 Technician Access Code Entry
After entry of the technician's license number, the EIS shall require manual entry of the technician's access code.
ENTER YOUR TECHNICIAN ACCESS CODE.
1. Do not display actual entries on the screen, instead use X's.
2. The access code must match the code stored internally in the Technician Information Table. The EIS shall allow three attempts to enter a valid access code. Following each of the first two attempts, the following message shall be displayed.
YOUR ACCESS CODE IS NOT VALID - TRY AGAIN.
3. After the third unsuccessful attempt, the EIS shall display the following message:
THE ACCESS CODE ENTERED IS NOT VALID. CONTACT THE LOCAL BAR FIELD OFFICE. THE TEST IS ABORTED DUE TO ACCESS CODE FAILURE.
3.6.3 Vehicle Identification Number (VIN) and License Plate
The VIN and vehicle license plate number entry shall follow immediately after successfully entering technician access code (i.e., prior to any other data entry). The following display prompts can be displayed on one screen with the ability to scroll through the list and select the appropriate option.
SCAN THE BAR CODE ON THE DMV REGISTRATION DOCUMENT. PRESS (function key) IF NOT AVAILABLE.
a) If the technician scans the DMV bar-coded VIN and license plate (scanned entries cannot be edited), the EIS shall proceed to §3.6.3 g).
b) If the (function key) is pressed, the EIS shall prompt the technician:
SCAN THE BAR CODE ON THE VEHICLE FOR THE VIN. IF THE BAR CODE IS NOT AVAILABLE, ENTER THE VIN MANUALLY.
IF THE VIN EXCEEDS 17 CHARACTERS ENTER THE LAST 17 CHARACTERS ONLY.
If manual entry is used, the VIN must be entered using dual manual entry to ensure accuracy. Both VIN entries must match before moving on to the license plate entry. The EIS shall automatically convert letter "I" to number "1" and letter "O" to number "0" as entered by the technician.
BOTH ENTRIES ARE NOT THE SAME - - TRY AGAIN.
INVALID CHARACTER ENTERED - - TRY AGAIN.
If fewer than three characters are entered, the EIS shall display the following message:
AT LEAST THREE CHARACTERS MUST BE ENTERED - - TRY AGAIN.
c) After manual entry of the VIN, the EIS shall prompt the technician to manually enter (dual manual entry) the license plate number:
ENTER THE LICENSE PLATE NUMBER MANUALLY. DO NOT ENTER SYMBOLS OR SHAPES (I.E., DIAMONDS, HEXAGONS, ETC.)
d) If fewer than two (2) characters are entered, the EIS shall display the following message:
AT LEAST TWO CHARACTERS MUST BE ENTERED - - TRY AGAIN.
The license plate number must be entered using dual manual entry to ensure accuracy. Both entries must match before proceeding to the next screen. If both entries are not the same, the EIS shall display the following message:
BOTH ENTRIES ARE NOT THE SAME - - TRY AGAIN.
e) If the vehicle has no license plate, the EIS shall allow the technician to enter NONE. The EIS shall store N in the License Plate Number field and print NONE on the VIR. If a repair record exists for this vehicle, the license number shall also be stored in the License Plate Number field of the repair record. In addition the EIS shall store XX (unknown) in the License Plate Issuing State field of the test record.
IF THE VEHICLE HAS NO LICENSE PLATE, ENTER "NONE" FOR THE LICENSE PLATE NUMBER.
1. The bar code scanner shall be used whenever possible. To help ensure the accuracy of manual entry, the VIN and/or license plate number must be entered using dual manual entry.
2. If fewer than 17 characters are entered, the EIS shall display the following message:
THE VIN ENTERED HAS FEWER THAN 17 CHARACTERS. VERIFY THAT THE VIN ENTERED MATCHES THE VEHICLE'S ACTUAL VIN.
3. The license plate number shall not contain special characters; valid characters are 0-9 and A-Z and shall be limited to 7 characters.
4. The data shall be written to the VIN and License Plate Number fields of the test record. If a repair record exists for this vehicle, the data shall also be written to the VIN and License Plate Number fields of the repair record. Print the VIN and license plate number on the VIR.
5. The VIN and license plate number entries are mandatory for every test record. If there is no entry, the EIS shall display the following message:
NO VALUE HAS BEEN ENTERED - - TRY AGAIN.
6. The DMV bar-coded registration document (provided by the motorist) contains a bar code using either code 39 or 128 symbologies. The bar-code scanner must be able to automatically discriminate between the symbologies to ensure that the current information shall be automatically read.
The bar code format for the DMV registration document is defined in Appendix C-5.
f) The EIS shall automatically store the source of entry for both VIN and license plate number in the test record as follows:
1. For VIN Input Source field:
D = Bar code on DMV registration document
V = Bar code on vehicle
M = Manual entry
This field must be populated in the test record for every valid test record sent to the VID. The EIS shall write the input source in the VIN Input Source field of the test record.
2. For License Plate Input Source field:
D = Bar code on DMV registration document
M = Manual entry
This field must be populated for every valid test record sent to the VID. The EIS shall write the input source in the License Plate Input Source field of the test record.
g) The EIS shall prompt the technician for the vehicle issuing state license plate:
SELECT THE LICENSE PLATE ISSUING STATE.
1. The EIS shall display a list containing the names and abbreviations of the 50 states, District of Columbia, Puerto Rico, Guam, American Samoa, Mexico, Canada, Armed Forces Plate and various locations. (A complete listing of acceptable abbreviations for the issuing state is in the Confidential Appendix C-2.)
2. The cursor shall default to California. However, under no circumstances shall the "California" selection be entered into the test record automatically, it must be confirmed by the technician.
3. The technician shall be allowed (by scrolling through the list) to select the one that applies for the vehicle under test. The EIS shall display the following message:
SELECT AND ENTER THE "ISSUING STATE" OF THE LICENSE PLATE.
4. If the vehicle issuing state is unknown, the EIS shall display the following message (on the same screen as the above prompt):
IF THE ISSUING STATE IS UNKNOWN, SELECT "XX" FOR UNKNOWN FROM THE LIST OF ISSUING STATES.
Upon selecting XX, the EIS shall display the following message:
YOU HAVE SELECTED XX (UNKNOWN). IS THIS CORRECT? (YES/NO)
If Y is selected, continue the inspection. If N is selected, display the issuing state list and message:
SELECT AND ENTER THE "ISSUING STATE" OF THE LICENSE PLATE.
5. The EIS shall write the issuing state abbreviation in the License Plate "Issuing State" field of the test record. The issuing state field must be populated for every valid test record sent to the VID. The EIS shall print the full name of the issuing state on the VIR. If there is no license plate or the issuing state is unknown, then "Unknown" shall be entered on the VIR in place of the issuing state.
3.6.4 Network Communications
(This information is confidential and may only be released with prior written consent from the BAR Engineering Section.)
3.6.5 EIS Initiated Actions
After connecting to the VID, the EIS shall transmit the following data:
- Technician information
- VIN, license plate number, and issuing state
- Test records, if applicable
- Repair records, if applicable
- Calibration records, if applicable
- Certificate purchase request, if applicable
- QA/State inspection records, if applicable
- Request current lockout status
- Inspection cost survey data, if applicable
- VLT version date and number of records
a) Transmit VIN/License Plate
After the VIN, vehicle license plate number and issuing state has been entered, the EIS shall display the following message:
SEARCHING FOR VEHICLE INFORMATION, PLEASE WAIT.
1. If a vehicle match is found, the VID shall transmit to the EIS applicable information for the vehicle under test, in addition to any other pending transactions.
2. Once a match has been made and the vehicle data or previously failed test data has been transferred from the VID to the EIS unit, the EIS shall not allow changes or corrections to either the VIN or license plate number or issuing state. If changes or corrections must be made to VIN, license and/or issuing state, the test shall be aborted.
3. If NO MATCH is found on the first attempt (note: attempts are counted by the EIS unit) for a California-licensed (non-government fleet vehicle or non-government "G" station) vehicle, then the EIS shall prompt the technician as follows:
NO VEHICLE MATCH HAS BEEN FOUND. VERIFY THAT THE VIN AND LICENSE PLATE HAVE BEEN ENTERED CORRECTLY. RE-ENTER THE VIN AND LICENSE PLATE AND PRESS --------- (function key) TO PROCEED.
4. The EIS shall allow the technician to completely re-scan or re-enter the VIN and/or vehicle license plate number. The EIS shall prompt the technician to press a function key to initiate a second call to the VID.
5. If no changes to the VIN or vehicle license plate number are required, the EIS shall prompt the technician to press a function key to initiate a second call to the VID. However, if the station is a government "G" station, the EIS shall continue WITHOUT making a second begin-test call to the VID.
6. If NO MATCH is found on the second attempt for a California-licensed vehicle, or on the first attempt for a vehicle with an out-of-state license plate number, then the EIS shall proceed with the inspection by prompting the technician to enter required information manually (see Item # 8). For a California-licensed vehicle, the EIS must be able to differentiate between the first and the second NO MATCH message. (A Government Fleet Station is not required to make a second call for a no match condition.)
7. The EIS shall display a message alerting the technicians of their responsibility to advise the consumer that NO MATCH was found with the DMV record or test was performed off-line and that the consumer should retain the VIR for reference during the registration process. This message shall also be printed on the VIR.
NO MATCH HAS BEEN FOUND OR TEST HAS BEEN PERFORMED OFF-LINE. THE CONSUMER IS RESPONSIBLE FOR RETAINING THE VIR FOR REFERENCE THROUGHOUT THE VEHICLE REGISTRATION PROCESS.
8. If a NO MATCH message occurs, the EIS shall enable the technician to enter the test vehicle's description (year, make, model, engine size, etc.) according to §3.6.7.
b) Transmit Test and/or Repair Records
All records (inspection, hands-on, training, aborted) that the EIS has created in accordance with the test and/or repair record shall be transmitted to the VID.
TRANSMITTING DATA, PLEASE WAIT.
1. The first record transmitted will be the oldest. After successful transmission, each record shall be moved (see Appendix C-2). The EIS shall retain a minimum of one thousand (1,000) of the most recent records by overwriting the oldest record.
2. If successful communications cannot be achieved (the EIS has not communicated with the VID), then the EIS shall display the following message.
CANNOT ACCESS NETWORK. PROCEED WITH THE INSPECTION.
c) Transmit Calibration Records
All calibration records that the EIS has created pursuant to Calibration Test Data shall be transmitted to the VID.
TRANSMITTING DATA, PLEASE WAIT.
1. The EIS shall transmit all calibration records to the VID. The first record transmitted will be the oldest. After successful transmission, the EIS shall delete all of the calibration records from the calibration data file and each record shall append the historical calibration data file. The EIS shall retain a minimum of one hundred (100) of the most recent records by overwriting the oldest record.
d) Transmit Certificate Numbers Purchase Request
The EIS shall transmit certificate numbers purchase requests to the VID. The EIS shall allow the Station Manager or Owner through the Station Manager Menu to place a certificate numbers purchase order and transmit it to the VID.
3.6.6 Network Responses
As the low level communication interface protocol makes contact with the VID and establishes a session, the VID will respond with stored transactions and messages (appropriate response bits) which are waiting for transmission to the EIS. These messages are:
- SYSTEM DATE/TIME UPDATE
- LOCKOUT STATUS
- TECHNICIAN(S) TO BE ADDED/CHANGED/DELETED
- PURCHASED SMOG CERTIFICATE NUMBERS
- BAR MESSAGES
- COMMUNICATIONS TRANSACTIONS
- VEHICLE DATA
- PREVIOUS FAILED TEST DATA
- PREVIOUS REPAIR INFORMATION
- VLT ROW ID NUMBER
- VLT UPDATE
- EMISSIONS-RELATED RECALL INFORMATION
- EMISSIONS-RELATED RECALL BLOCK (DMV)
- EMISSIONS-RELATED TSB INFORMATION
- EMISSIONS STANDARDS CATEGORY (ESC) TABLES (1,3 and 4) UPDATE
- PREVIOUS ODOMETER READING
- INSPECTION REASON
- REQUIRED TEST TYPE
- VEHICLE SPECIFIC VLT (VSVLT)
- CONFIGURATION UPDATE
- MESSAGE UPDATE
- ADVISE UPDATE
- EXTENDED PARAMETERS UPDATE
The automatic transaction and message updates will occur on every session initiated by the EIS except during communications diagnostic transactions. The communications interface will provide the EIS application with the appropriate status information to determine which transactions have occurred following VID session initiation.
a) Receive SYSTEM DATE/TIME UPDATE
The communication software shall reset the current EIS date/time settings each time contact is made with the VID (except during network diagnostics or loopback). The VID shall pass, via the communication software, the current date/time settings to the EIS. Upon receiving the date and time settings, the date and time received shall serve as the date stamp (date of test) and time stamp (test start time) for the inspection in progress. The EIS shall use the received date and time settings to update the EIS clock. (If the EIS uses other clocks, the EIS shall be required to update the appropriate system clock.) The inspection start date and time stamp for an inspection shall be set in the test record following the receipt of the System Date/Time Update by the EIS just after the initial VID contact. If communication attempts fail for the initial VID contact, the date and time stamp shall be set using the EIS clock.
The date of the test, test start-time and test-end time shall be recorded in the test record in the following fields, as appropriate: Date of Test, Test Start Time and Test End Time. Each of these fields must be populated in the test record for every valid test record. Print the date of the test and test end time on the VIR.
b) Receive LOCKOUT/TAMPER STATUS
The status (on/off) of the lockouts and/or tampers shall be transmitted by the VID to the EIS. If a lockout(s)/tamper(s) is set, then subsequent inspections shall be prohibited until the applicable lockout(s)/tamper(s) has been cleared. The VID shall return the state of the following lockout/tamper conditions to the EIS:
- QA/State EIS Lockout
- Cabinet Tampering (see Note 1)
- State Disk Drive (see Note 1)
- Station License Expired
- Station License Suspended
- Station License Revoked
- Failure to Pay for Certificate Numbers Purchased
- Failure to Pay for Communication Services
- Certificate Sequencing Error
- Calibration Gas Cylinder Violation
- No communication with VID in XXX days and XXX tests
- Clock lockout
- VLT Corrupt (self-correcting - cleared upon VID verification of VLT data
- Excessive Number of Aborts
- Dynamometer scale failure
A tamper is set by the EIS and sent to the VID upon the next communication to the VID. Once the tamper condition has been received by the VID, it can only be cleared via the VID.
If a lockout/tamper has been set, the EIS shall display one or more of the messages shown below:
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A QA/STATE INSTALLED LOCKOUT BEING SET. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A CABINET TAMPER. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A STATE DISK DRIVE TAMPER. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED SINCE STATION LICENSE HAS EXPIRED. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED SINCE STATION LICENSE HAS BEEN REVOKED. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED SINCE STATION LICENSE HAS BEEN SUSPENDED. CONTACT LOCAL BAR OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A FAILURE TO PAY FOR CERTIFICATE NUMBERS PURCHASED. CONTACT BAR ACCOUNTING OFFICE FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A FAILURE TO PAY FOR COMMUNICATION SERVICES. CONTACT MCI HELP DESK FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A CERTIFICATE OUT OF SEQUENCE ERROR. CONTACT MCI HELP DESK FOR FURTHER INSTRUCTIONS.
THE SMOG CHECK CANNOT BE PERFORMED DUE TO A CALIBRATION GAS CYLINDER LOCKOUT. CONTACT LOCAL BAR FIELD OFFICE FOR FURTHER INSTRUCTIONS.
1 - 40