Actron 9640A manual Playback, Datack

Global OBD II Diagnostics

Most of the functions displayed on the Review Data screen are self explana- tory. Only one function, Playback, needs detailed instructions. Follow the prompts and instructions provided by the scan tool.

If data does not exist for the function
you selected to review (for example	Datack	]
Vehicle Info), a message informs you
to run the function first.	INFOBefore
cate data recorded before the trigger
Playback	Reviewta
The Playback function is used to play
back a recording. This function is very	`7)Playb9ModulesPresent	~
similar to View Data. The only differ-	8VehicleInfo
ence is that View Data is a real time
viewing of PIDs, while Playback is a
viewing of previously recorded PIDs.

To play back your vehicle’s recorded PIDs, select Pl yb		m the Review
Data list. Press the	key to continue.

The scan tool displays a NO RECORDING PRESENT m ssage if a recording 4

does not exist. Otherwise, press			to play		ck the r co ding. The scan
tool plays back the Entire Data List or the Cust m						List, dep		di g on
how the data was recorded.				No		StoredIn
The Playback is composed of three
lines of data and one line for the frame
number and timestamp (in seconds).
Negative frames and timestamps indi-				Tool.		VEHICLE			~
event. Positive frames and timestamps					ReviwingUse		.
indicate data recorded after the trigger event.
Use the		arrow keys to view the r		corded		ID data of each frame.
RIGHTLEFT/RIGHTUP/DOWNBACK				]	LEFT
The end of the list is reached when only the				(up) con is visible.
Use the		arrow keys to scroll back and forth through the frames.
The	arrow key advances to the next fram				, “wrapping arou d” to the
earliest frame when the final frame is reached. The						arrow key goes back
to the previous frame, again “wrapping around” to the final f ame.
✓ Different vehicles communicate at different speeds and support a different
number of PIDs. Therefore, the maximum number of frames that can be
recorded will vary.
✓ Some vehicles waitENTERa long period of time to store a trouble code after the
driveability problem occurs. If you selected “Trigger On Codes” when you
made your recording, you might not see any drastic change in data param-
eters before and after the triggerENTERpoint. In cases like this, the user can
manually trigger the recording when the symptom is observed.
When done, press		to return to Review Data or to the OBDII Function
List.			MILSTATUS(ABSLTFRAME:TM:4TPS(%)($1$A.410)					ON35[~

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 4 – 11