Troubleshooting
About
This section contains troubleshooting information to help you identify, isolate, and resolve component and system issues.
Review the Introduction To Troubleshooting section below to learn about the troubleshooting process, troubleshooting best practices, and other pertinent information that will help you efficiently troubleshoot issues and return the equipment to service.
Information that will help you troubleshoot:
- Review the Introduction To Troubleshooting section below.
- Review the Error Log for active error codes, see the Error Log & CPA Event Log and Standard Error Codes topics.
- Refer to the Error Code Troubleshooting Guide for error code description and troubleshooting repair information.
- If the machine supports the Active Status Light feature, review the ASLActive Status Light: Service and maintenance status light. topic (see Active Status Light (ASL)).
- Review the System Troubleshooting Procedures topic for possible related issue fixes or repairs, see System Troubleshooting Procedures.
Introduction To Troubleshooting
Troubleshooting issues is an investigative process best implemented utilizing a systematic approach that efficiently targets the issue cause allowing correct equipment repairs and return to service. The following information will help you to systematically troubleshoot and resolve issues.
Basic Steps
Validate the customer reported issue:
The failure that is reported may differ from your observations as a trained technician. Many reported failure are not true failures and can be fixed without a customer visit.
- (powered units only) Always ask the customer if the unit power is connected and switched ON.
- Further interrogate the customer to determine if this is the real issue requiring an on-site visit or possibly a different issue that can be simply resolved over the phone.
Verify that the console is operating correctly
- On LED consoles (P10, P30, P30i and P31) make sure the console powers up and is working correctly, perform the following verification tests:
- If the console does not power up, make sure the Data COMM cable is properly connected at the console and LPCALower printed circuit assembly; generally this refers to the lower board. On treadmills, this is the motor controller unit (MCU), and on self-powered units, it is the main board in the lower section. and in good condition.
- Run the console Display, and Keypad diagnostic tests (see Hardware Validation Diagnostics Tests Menu (51765761)). Resolve any failures.
- On Touchscreen consoles (P62, P80, and P82) make sure the console powers up and is working correctly, perform the following verification tests:
- If the console does not power up, make sure the external ACAlternating Current: electric current which periodically reverses direction between positive and negative polarity./DCDirect Current: electrical current that only flows in one direction. power adapter is plugged in and connected to the console. Also make sure the AC/DC adapter brick is in good condition.
- Run the following console System Tests (see System Tests):
- Touchscreen Test
- Touchscreen Calibration
- Backlight Test
- RGB Test
- Numeric Backlight Test
- Numeric Display Test
|
Note: Keep in mind that if a key on the console keypad does not function, the LPCA will not receive a user initiated request for action. For failed console key problems, the machine failure is not caused by a problem with the LPCA or the machine base, In these types of console failures, no error codes will be triggered and logged. |
Review the Error Log or CPA Event Log for any active error codes
Always review the Error Log or CPA Event Log when troubleshooting an issue. The error logs will contain any triggered error code events and related information. You can then refer to Error Code Troubleshooting Guide to help resolve the issue. Also, when calling Precor customer service for assistance, refer to the Error Log or CPA Event Log for additional information to help the representative resolve the issue.
Refer to the Error Code Troubleshooting Guide for error code descriptions and repair information.
IMPORTANT: Error code descriptions and troubleshooting information can be found in the Error Code Troubleshooting Guide, see Error Code Guide.pdf. |
|
Note: Not all failures trigger an error event code. Many issues are purely mechanical in nature and therefore cannot trigger an error event code. |
Verify (reproduce) the issue.
Operate the unit in normal user mode and attempt to reproduce the reported failure Determine if the error is a repeatable or intermittent type failure Make note of any additional observations (noises, vibrations, etc.) that occur at the time of the failure which may then be used to help resolve the issue.
|
Note: It is important to keep in mind that some issues are weight (load) related. You may need to test the unit at minimum and maximum load Limits to reproduce the failure. |
Perform hardware validation diagnostic tests
Perform the equipment Hardware Validation Tests (LED consoles) or System Tests (Touchscreen consoles) to help isolate the cause of the issue. These tests will help identify failed system components. Resolve any resulting failures.
Verify Club Settings
Verify that one of the workout limit settings are not causing a failure, see Club Settings (LED consoles) or System Settings Workout Limits (Touchscreen consoles). If a failure is observed while using the machine but passes the hardware validation system tests, this could be an indication that one of the club parameters Limits settings is causing the issue.
Verify that there are no new error codes
After correcting the issue, reopen the Error Log and verify that there are no remaining active error codes. This will verify that the original error codes are not reoccurring and that there are no new error code issues. If the error code is reoccurring, the issue may be mileage related, review the error code odometer history to verify if the error event is related to mileage intervals.
On P10, P30, P30i and P31 consoles, clear the error log by pressing and holding the "Quick Start" key.
|
Note: If there is no logged error codes and the issue persists, you will need to use observable and audible indicators to identify the source of the failure. Also make sure that there are no related service bulletins that may resolve the issue. Browse the list of available Troubleshooting procedures for related Troubleshooting information. |
Verify service bulletins
Review the list of machine service bulletins and tech-tips and verify that there are no current bulletins that may fix the issue.