| Page 24 of 28 |
| |||||||||
|
|
|
|
|
|
|
|
|
|
| |
|
| Message |
|
|
|
|
| Notes and Corrective Action∼ |
|
| |
|
|
|
|
|
|
|
|
| The driver has found a malfunction but could not match it |
| |
|
|
|
|
|
|
|
|
| exactly to a malfunction in the Malfunction Table. The |
| |
|
| TGM: | #21 | FYI. |
| Malfunction. |
| driver used a soundex function which looks for matches |
| ||
|
|
|
| based on a ‘sounds like’ evaluation. As the match is not |
| ||||||
|
| Don’t | recognize |
| <%s> | But |
| exact the driver provides the alert. |
|
| |
|
| sounds like <%s>. |
|
|
|
|
|
| |||
|
|
|
|
|
| To suppress this message in the future, note the message |
| ||||
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| and add it to the Malfunction Table. Notes in Appendix B.5 |
| |
|
|
|
|
|
|
|
|
| provide information on how to do this. |
|
|
|
|
|
|
|
|
|
|
| The driver has found an event description that is being |
| |
|
|
|
|
|
|
|
|
| evaluated as a potential ‘Return to Normal’ message, but |
| |
|
|
|
|
|
|
|
|
| could not match it exactly to a ‘Return to Normal’ in the |
| |
|
| TGM: | #22 | FYI. |
| Return | to |
| Malfunction Table. The driver used a soundex function |
| |
|
| Normal. | Don’t |
| recognize |
| which looks fro matches based on a ‘sounds like’ |
| |||
|
|
|
| evaluation. As the match is not exact the driver provides the |
| ||||||
|
| <%s>But sounds like <%s>. |
|
| alert. |
|
| ||||
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| To suppress this message in the future, note the message |
| |
|
|
|
|
|
|
|
|
| and add it to the ‘Return to Normal' Table. Notes in |
| |
|
|
|
|
|
|
|
|
| Appendix B.6 provide information on how to do this. |
| |
|
| TGM: | #23 | FYI. | Duplicate |
|
|
|
| ||
|
| Malfunction Number=<%d>.Text |
|
|
|
| |||||
|
| has been updated from=<%s> |
|
|
|
| |||||
|
| to=<%s> |
|
|
|
|
| If these messages are produced then the driver processes |
| ||
|
| TGM: #24 Err. No space. Reject |
|
| |||||||
|
|
| the TGM config file. Read Appendix B.7 for more |
| |||||||
|
| Malfunction=<%s> |
| Index |
| information. |
|
| |||
|
| Val=%d |
|
|
|
|
|
|
|
| |
|
| TGM: | #25 | FYI. | User added |
|
|
|
| ||
|
| Malfunction=<%s> |
| Index |
|
|
|
| |||
|
| Val=%d |
|
|
|
|
|
|
|
| |
|
| TGM: #26a Err. Malfunction=%s |
| The maximum malfunction index value | is 99. Use the |
| |||||
|
| Index value=%d > 99. |
|
| procedure in Appendix B.5 to modify the malfunction index |
| |||||
|
|
|
| value.4 |
|
| |||||
|
|
|
|
|
|
|
|
| It is almost impossible for the driver to distinguish between |
| |
|
|
|
|
|
|
|
|
| ‘Return to Normal’ events and those events not associated |
| |
|
|
|
|
|
|
|
|
| with a malfunction. When a |
| |
|
|
|
|
|
|
|
|
| that doesn’t match the entries in the Return to Normal Table |
| |
|
| TGM: | #27 | Err. | Event=%s | is |
| then this message is printed. It is printed 20 times and then |
| ||
|
| Unknown. Read manual. |
|
| suppressed. |
|
| ||||
|
|
|
| Ignore the messages if they clearly are not ‘Return to |
| ||||||
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| Normal’ events that correspond to Malfunctions. If, however, |
| |
|
|
|
|
|
|
|
|
| they are obviously associated with Malfunctions then add |
| |
|
|
|
|
|
|
|
|
| the description to the ‘Return to Normal’ Table. Notes in |
| |
|
|
|
|
|
|
|
|
| Appendix B.6 provide information on how to do this. |
| |
|
| TGM: |
| #28 |
| Err |
| This message is printed during Map Descriptor Validation. |
| ||
|
| TGM_Function=%s invalid. |
|
| The function is not recognized. Correct the configuration |
| |||||
|
|
|
| using information found in section 4.4.24 |
|
| |||||
4 Modify the configuration CSV file. Download the modified file to the FieldServer and Reset the FieldServer for the changes to take effect.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)
