Error 50
Too Much Brake (Magnet) Current
Applies to
Consumer EFX, AMT, U/RBK
Issue Symptoms
This error is associated with eddy current EFX’s, AMT's, Climbers and Bikes. The resistance (brake) control system constantly monitors the amount of current being demanded by the eddy current magnet. Error 50 indicates that the amount of current being demanded by the eddy current magnet is excessive. The most common cause of this error is shorted or damaged wiring between the lower PCA and the eddy current magnet. While possible but lease likely, this can be caused when the eddy current magnet is bad or the lower PCA is bad.
Troubleshooting steps
1. Carefully check the eddy current wiring and connections, ensuring that the wires are not shorted together or shorted to the frame. Repair or replace the damaged wiring as appropriate.
2. Unplug the eddy current cable connection from the lower PCA. Pedal the unit and increase the resistance level, if the error is still displayed, replace the lower PCA. If the error is not displayed, replace the eddy
Too Much Brake (Magnet) Current
Applies to
Consumer EFX, AMT, U/RBK
Issue Symptoms
This error is associated with eddy current EFX’s, AMT's, Climbers and Bikes. The resistance (brake) control system constantly monitors the amount of current being demanded by the eddy current magnet. Error 50 indicates that the amount of current being demanded by the eddy current magnet is excessive. The most common cause of this error is shorted or damaged wiring between the lower PCA and the eddy current magnet. While possible but lease likely, this can be caused when the eddy current magnet is bad or the lower PCA is bad.
Troubleshooting steps
1. Carefully check the eddy current wiring and connections, ensuring that the wires are not shorted together or shorted to the frame. Repair or replace the damaged wiring as appropriate.
2. Unplug the eddy current cable connection from the lower PCA. Pedal the unit and increase the resistance level, if the error is still displayed, replace the lower PCA. If the error is not displayed, replace the eddy
Error 60, 61
Auto Stop Not Working/Present
Applies to
These errors are associated with the TRMv1 Treadmill
NOTE: These errors will not be present if the magnet on the deck is missing or misaligned. These errors will only indicate an electrical problem with the sensor. Failing to move or correctly align/gap the magnet when the deck is flipped, or moved to a new deck when a previously flipped deck is replaced, will cause the Auto Stop function to engage after 90 seconds of use, with a 10 second countdown following.
Issue Symptoms
Error 60 indicates the Auto Stop feature has stopped functioning during a workout. If the error is detected while a workout is in progress, the treadmill will operate normally until the workout has ended. At the end of theworkout, the error will lock out the next user, displaying "Temporarily Out of Order, Please Use another treadmill" on the P80 console and "PLEASE USE ANOTHER TREADMILL" on the P30 and P10 consoles. When this error occurs error 60 will be recorded in the error log of the console. The most likely cause of error 60 is a poor or missing connection between the Auto Stop sensor and the cable connecting the sensor to the console. A damaged or faulty Auto Stop sensor may also cause this problem. Least likely but possible is a failure in the upper PCA/Console.
Error 61 indicates the Auto Stop sensor is not detected. If the error is detected the user will be locked out, displaying "Temporarily Out of Order, Please Use another treadmill" on the P80 console and "PLEASE USE ANOTHER TREADMILL" on the P30 and P20 consoles. When this error occurs error 61 will be recorded in the error log of the console. The most likely cause of error 61 is a broken or disconnected cable between the sensor and the console. Less likely but possible is a missing or faulty sensor.
Auto Stop Not Working/Present
Applies to
These errors are associated with the TRMv1 Treadmill
NOTE: These errors will not be present if the magnet on the deck is missing or misaligned. These errors will only indicate an electrical problem with the sensor. Failing to move or correctly align/gap the magnet when the deck is flipped, or moved to a new deck when a previously flipped deck is replaced, will cause the Auto Stop function to engage after 90 seconds of use, with a 10 second countdown following.
Issue Symptoms
Error 60 indicates the Auto Stop feature has stopped functioning during a workout. If the error is detected while a workout is in progress, the treadmill will operate normally until the workout has ended. At the end of theworkout, the error will lock out the next user, displaying "Temporarily Out of Order, Please Use another treadmill" on the P80 console and "PLEASE USE ANOTHER TREADMILL" on the P30 and P10 consoles. When this error occurs error 60 will be recorded in the error log of the console. The most likely cause of error 60 is a poor or missing connection between the Auto Stop sensor and the cable connecting the sensor to the console. A damaged or faulty Auto Stop sensor may also cause this problem. Least likely but possible is a failure in the upper PCA/Console.
Error 61 indicates the Auto Stop sensor is not detected. If the error is detected the user will be locked out, displaying "Temporarily Out of Order, Please Use another treadmill" on the P80 console and "PLEASE USE ANOTHER TREADMILL" on the P30 and P20 consoles. When this error occurs error 61 will be recorded in the error log of the console. The most likely cause of error 61 is a broken or disconnected cable between the sensor and the console. Less likely but possible is a missing or faulty sensor.
Troubleshooting steps
1. Check that the Auto Stop cable connectors are secure at the sensor and console. Visually verify the Auto Stop hardware components are installed onto the treadmill frame. If the Auto Stop hardware is notpresent contact Precor Customer Support. Check that the Auto Stop cable connectors are secure at the sensor and console. Visually inspect the Auto Stop sensor for physical damage and correct installation. Replace if appropriate.
2. Access the diagnostic system tests, and select the Auto Stop test. If the feature is enabled the P80 Auto Stop sensor test will count the number of times the magnet crosses the sensor. The P30 and P20 consoleswill display "USER DETECTED" if motion is detected from the running deck or "NO USER DETECTED" if no motion is detected from the running deck. If the Auto Stop test in the P80 did not count steps or if the P30 and P20 consoles displayed "NO USER DETECTED", disconnect the Auto Stop cable from the Auto Stop sensor and check for 5 vdc between the red and black wire. If 5 vdc is present replace the Auto Stop sensor. If not present, continue with the next test.
1. Check that the Auto Stop cable connectors are secure at the sensor and console. Visually verify the Auto Stop hardware components are installed onto the treadmill frame. If the Auto Stop hardware is notpresent contact Precor Customer Support. Check that the Auto Stop cable connectors are secure at the sensor and console. Visually inspect the Auto Stop sensor for physical damage and correct installation. Replace if appropriate.
2. Access the diagnostic system tests, and select the Auto Stop test. If the feature is enabled the P80 Auto Stop sensor test will count the number of times the magnet crosses the sensor. The P30 and P20 consoleswill display "USER DETECTED" if motion is detected from the running deck or "NO USER DETECTED" if no motion is detected from the running deck. If the Auto Stop test in the P80 did not count steps or if the P30 and P20 consoles displayed "NO USER DETECTED", disconnect the Auto Stop cable from the Auto Stop sensor and check for 5 vdc between the red and black wire. If 5 vdc is present replace the Auto Stop sensor. If not present, continue with the next test.
3. Check for 5 vdc at the upper PCA or console. Disconnect the Auto Stop cable connector from the upper PCA or console and measure the voltage from the console. If 5 vdc is not present replace the upper PCA or console. If 5 vdc is present then replace the Auto Stop cable.
Error 62
Vertical Sensor Failure
Applies to
AMT 12
Issue Symptoms
Error 62 will occur when the vertical stride is not detected. The most likely cause of this will be a faulty, broken or poor cable connection at the lower PCA. A missing or reversed magnet on the crank arm is also a possibility, as is a defective sensor. Least likely but possible is a fault on the lower PCA.
Troubleshooting steps:
1. Check to ensure vertical sensor cable connector is secure on lower PCA, and that the cable is intact, that it has not been compromised.
2. Verify the magnet is present in the crank arm, and is correctly installed. The sensor is polarity sensitive, and an incorrectly installed magnet will cause this error. To test it, remove the magnet from the crankarm, and while in the Stride Sensor test move the magnet back and forth past the sensor, if the polarity is correct you will see counts recorded.
3. If the previous test does not show a count (regardless of polarity) eplace the vertical sensor with a known good vertical sensor. Retest.
Vertical Sensor Failure
Applies to
AMT 12
Issue Symptoms
Error 62 will occur when the vertical stride is not detected. The most likely cause of this will be a faulty, broken or poor cable connection at the lower PCA. A missing or reversed magnet on the crank arm is also a possibility, as is a defective sensor. Least likely but possible is a fault on the lower PCA.
Troubleshooting steps:
1. Check to ensure vertical sensor cable connector is secure on lower PCA, and that the cable is intact, that it has not been compromised.
2. Verify the magnet is present in the crank arm, and is correctly installed. The sensor is polarity sensitive, and an incorrectly installed magnet will cause this error. To test it, remove the magnet from the crankarm, and while in the Stride Sensor test move the magnet back and forth past the sensor, if the polarity is correct you will see counts recorded.
3. If the previous test does not show a count (regardless of polarity) eplace the vertical sensor with a known good vertical sensor. Retest.
4. Substitute the lower PCA with a known good lower PCA.
Error 70-79
Flat Belt Count Error Overview
Applies to
AMT12, all models
Issue Symptoms
These errors have to do with the flat belt count of the AMT12. The AMT12 utilizes a flat belt system to provide fluid movement and support to the stairarms. It is critical that the flat belts are replaced at a defined stride count.
To ensure the stride count is maintained throughout the life of the AMT12, the stride count is stored on both the lower PCA and the upper PCA.If either PCA is replaced, the stride count will be written to the new board, depending on certain criteria. Different conditions will cause an error to be logged. In most cases errors 70 to 77 will be for informational purposes, and will not affect the operation of the AMT. Errors 78 and 79 will indicate that belt replacement is imminent or necessary. The PCA’s will compare software versions and stride counts, and an appropriate error will be generated as an indicator of the condition. These error scan be used to determine if used or new PCA’s were installed.
Flat Belt Count Error Overview
Applies to
AMT12, all models
Issue Symptoms
These errors have to do with the flat belt count of the AMT12. The AMT12 utilizes a flat belt system to provide fluid movement and support to the stairarms. It is critical that the flat belts are replaced at a defined stride count.
To ensure the stride count is maintained throughout the life of the AMT12, the stride count is stored on both the lower PCA and the upper PCA.If either PCA is replaced, the stride count will be written to the new board, depending on certain criteria. Different conditions will cause an error to be logged. In most cases errors 70 to 77 will be for informational purposes, and will not affect the operation of the AMT. Errors 78 and 79 will indicate that belt replacement is imminent or necessary. The PCA’s will compare software versions and stride counts, and an appropriate error will be generated as an indicator of the condition. These error scan be used to determine if used or new PCA’s were installed.
Error 70, 71, 72, 73
Flat Belt Count/Software Mismatches
Applies to
AMT12, all models
Issues Symptoms
When power is applied to the upper PCA and lower PCA, the stride count written on each of the EEPOMs will be compared to each other and to a set of preset stride conditions. If the stride count written on the EEPOM's do not match or meet a preset stride count condition, a error will be written to the error log or displayed to the user at the end of the workout summary.
# Error 70: Lower PCA not read. The upper PCA EEPOM cannot detect the stride count written on the lower PCA. This error is only reported to the error log. This is usually caused by a lower PCA with no software installed.
# Error 71: Lower PCA. The upper PCA has detected a lower PCA that does not have a stride count written to the lower PCA EEPROM. This is not an error and is used for tracking only. For reference it will be reported to the error log.
# Error 72: Lower PCA version not known. A version mismatch is detected between the EEPROMs of the upper PCA and the lower PCA. When the upper PCA reads the data from the lower PCA’s EEPROM, andthe internal version isn’t correct, the upper PCA logs error 72. The upper PCA will then attempt to write the correct version number to the lower PCA. If the correct version can be successfully written to thelower PCA’s EEPROM, then this error probably won’t be seen again. If the upper PCA version number cannot be successfully written to the lower PCA, then numerous errors will be logged with different odometer values. The occurrence of this error would be rare and if it did occur, the normal operation of the AMT12 would not be effected.
# Error 73: Lower PCA record bad. A byte size error is detected between the EEPROMs of the upper PCA and the lower PCA. When the upper PCA reads the data from the lower PCA’s EEPROM, and the byte sizeisn’t correct, the upper PCA logs error 73. The upper PCA will then attempt to write the correct byte size to the lower PCA. If the correct byte size can be written to the lower PCA’s EEPROM, then this errorprobably won’t be seen again. If the upper PCA byte size cannot be successfully written to the lower PCA, then numerous errors will be logged with different odometer values. The occurrence of this error would be rare and if it did occur, the normal operation of the AMT12 would not be effected.
Troubleshooting steps
1. Error 70: Replace lower PCA with a known good lower PCA.
2. Error 71: None, this is for informational purposes only.
3. Errors 72 and 73: These errors will not affect the operation of the AMT12 and the error would only be recorded in the error log. Replacing the lower PCA would only resolve the repeated recordings of theerror in the error log.
Flat Belt Count/Software Mismatches
Applies to
AMT12, all models
Issues Symptoms
When power is applied to the upper PCA and lower PCA, the stride count written on each of the EEPOMs will be compared to each other and to a set of preset stride conditions. If the stride count written on the EEPOM's do not match or meet a preset stride count condition, a error will be written to the error log or displayed to the user at the end of the workout summary.
# Error 70: Lower PCA not read. The upper PCA EEPOM cannot detect the stride count written on the lower PCA. This error is only reported to the error log. This is usually caused by a lower PCA with no software installed.
# Error 71: Lower PCA. The upper PCA has detected a lower PCA that does not have a stride count written to the lower PCA EEPROM. This is not an error and is used for tracking only. For reference it will be reported to the error log.
# Error 72: Lower PCA version not known. A version mismatch is detected between the EEPROMs of the upper PCA and the lower PCA. When the upper PCA reads the data from the lower PCA’s EEPROM, andthe internal version isn’t correct, the upper PCA logs error 72. The upper PCA will then attempt to write the correct version number to the lower PCA. If the correct version can be successfully written to thelower PCA’s EEPROM, then this error probably won’t be seen again. If the upper PCA version number cannot be successfully written to the lower PCA, then numerous errors will be logged with different odometer values. The occurrence of this error would be rare and if it did occur, the normal operation of the AMT12 would not be effected.
# Error 73: Lower PCA record bad. A byte size error is detected between the EEPROMs of the upper PCA and the lower PCA. When the upper PCA reads the data from the lower PCA’s EEPROM, and the byte sizeisn’t correct, the upper PCA logs error 73. The upper PCA will then attempt to write the correct byte size to the lower PCA. If the correct byte size can be written to the lower PCA’s EEPROM, then this errorprobably won’t be seen again. If the upper PCA byte size cannot be successfully written to the lower PCA, then numerous errors will be logged with different odometer values. The occurrence of this error would be rare and if it did occur, the normal operation of the AMT12 would not be effected.
Troubleshooting steps
1. Error 70: Replace lower PCA with a known good lower PCA.
2. Error 71: None, this is for informational purposes only.
3. Errors 72 and 73: These errors will not affect the operation of the AMT12 and the error would only be recorded in the error log. Replacing the lower PCA would only resolve the repeated recordings of theerror in the error log.
Không có nhận xét nào:
Đăng nhận xét