06.08.2013 Views

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

9.1.6. VBOX ColdStart Procedure<br />

NOTE: This procedure is to be used to reset the VBOX when it<br />

per<strong>for</strong>ms erratically. For example, this procedure is to be used when<br />

the VBOX is unable to maintain a satellite lock. In this situation, a<br />

graph of the satellite count may look similar to the image below.<br />

Figure 9.1.6-1: Example of Satellite In<strong>for</strong>mation Indicating the Need <strong>for</strong><br />

a Cold Start.<br />

NOTE: This procedure begins with the VBOX turned on and the<br />

support computer running. While the VBOX may remain connected to<br />

the eDAQ during this procedure, the eDAQ should not be in the middle<br />

of a run; if the eDAQ is on, only the solid green LED should be on.<br />

1) Connect the gray VBOX serial cable to socket 3 in the back of<br />

the VBOX.<br />

2) Connect the USB/Serial adapter to the support computer.<br />

3) Connect the gray VBOX cable to the serial adapter.<br />

4) Open the VBOXTools software.<br />

5) Per<strong>for</strong>m a Cold Start of the VBOX.<br />

a) Verify that the VBOX icon appears in the top left corner of the<br />

window. If not, press F11 to toggle from the file option.<br />

NOTE: The text beside this icon should read “Serial data okay.”<br />

If this is not the case, verify that the correct serial port is<br />

selected (Options > COM Port). It will be necessary to reopen<br />

the VBOXTools software after making any changes to the<br />

connections.<br />

b) Click the Tools icon and then click ColdStart.<br />

D-75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!