 |
| ||||||
| TimeClock Errors - Bad RX from Host | ||||||
| ||||||
| Question | |
| ||||
| I am getting a "Bad RX..." error message on the clock. What does this mean and how do I fix it? | ||||||
| Answer | ||||||
| BAD RX COMMUN (bad received communication) indicates that the terminal received multiple corrupted packets, or that the server has complained of multiple corrupted packets, and couldn't recover after several attempts. Note that these packets are sent over an analog telephone and can be "corrupted" simply by static, hums, or other line noise. These could mean a noisy line or a bad terminal if seen consistently. TROUBLESHOOTING: All of these messages can indicate problems with the telephone line. Before replacing a terminal that consistently shows these messages: 1. Have the customer make a regular call on the telephone line being used for the terminal. During periods of silence, is there any audible noise? Hum? Crackling or static? All of these could indicate a problem with the telephone line that only the telephone company can address. 2. Is the customer using any voice-over-IP (Vonage, Packet8, etc.) to connect their terminal? Avoid this. 3. Does the terminal work fine on another phone line? (The best way to test it is to have them take the terminal home and test it on a residential phone line. Residential phone lines offer the fewest surprises as they're just about always the right type of line for the TRANZ terminal.) Path: TimeClock (Main Page) > Time Clock Errors > TimeClock Errors - Bad RX from Host | ||||||
| Back to Search Results | ||||||