Precision, Performance, Confidence. ™

PPCx Pressure Controller - Log control diagnostics to COM 2

Capture diagnostics data to COM2 of a PPC4 (or PPC3, PPCH, PPCH-G) controller

If your PPCx Pressure Controller (PPC2+, PPC3, PPC4, PPC4E, PPC4EX, PPCH, PPCH-G) is having control problems we might ask that you capture diagnostics logs and send them to us.

Diagnostics can be captured from the RS232 COM1 port of these controllers when connected to a computer running logging software like HyperTerminal or putty.org. These instructions refer to HyperTerminal software.

Instructions to Log Diagnostics

  1. Connect to COM1 of the device with a serial (RS-232) connection.
  2. Establish a communications channel with the controller with a terminal program like HyperTerminal (or putty.org). High baud rates are suggested for diagnostics. Suggested COM settings for both HyperTerminal and the controller are 19200, N, 8, 1. Typical path for PPC controllers is [Special], <Remote>, <RS232>, <COM1>.
  3. To confirm that there is a connection, send the command VER. When typing commands in HyperTerminal they are not shown on the screemn.
  4. The response should be a version string similar to “Fluke Calibration, model name and software version”. Old model equipment may show “DHI”
  5. Send command(s) !diag=8192 to output any diagnostics to COM2 of the controller. A response containing 8192 should be returned.
  6. Send command !diaggen=1 to capture pressure control diagnostics for PPC valve control. A response containing 1 should be returned.
  7. Connect a serial (RS-232) cable to COM2 of the controller and establish a communications channel with the controller with a terminal program like HyperTerminal. High baud rates are suggested for diagnostics. Suggested COM settings for both HyperTerminal and test equipment are 19200, N, 8, 1. Typical path for PPC controllers is [Special], <Remote>, <RS232>, <COM2>.
  8. Use the HyperTerminal menu selection of <Transfer>,<Capture Text> to start capturing and saving data that will be generated. Choose a directory and file name or make one.
  9. When running diagnostics it is preferable to not push any buttons on the device. Use remote commands from HyperTerminal to COM1 to set pressures, etc. (e.g. PS=100 sets a pressure of 100 in the current units. ABORT stops pressure control, VENT=1 vents the controller, VENT=0 closes the vent valve)
  10. The diagnostics can run during any test or command
  11. Send command !diag=0 to stop capturing diagnostics. Cycling power on the controller also stops diagnostics.
  12. When you are done, use the <Transfer>,<Capture Text>,<Stop> menu selections to stop capturing data.
  13. Cycle power after doing diagnostics to prevent any communications problems.
  14. Send the file to pressuresupport@flukecal.com along with a description of what was happening.

 

Have more questions? Submit a request

Comments

Please sign in to leave a comment.