|
| Page 30 of 31 |
|
|
|
|
|
| Error Message | Explanation |
|
| Carrier:#15 Err. Alarm | The server does not support alarm functions. Polls beginning |
|
| commands not supported. |
| |
| AV or RA produce these errors. |
| |
| Carrier:#16 Err. Alarm |
| |
| request this information. § |
| |
| commands not supported. |
|
|
|
| On the line immediately following this error the driver reports |
|
| Carr:#17 Err. MD=<%s> | the response that generated the error. The driver will store a |
|
| discrete state word not | value that is the ASCII code for the first character of the |
|
| recognized. | unrecognized word. Add a new discrete state word to the .CSV |
|
|
| file as described in Appendix A.4. § |
|
|
| This message may be ignored if your communications are |
|
| CarrDL:#18 FYI. Timeout | operating reliably. Read Appendix A.5 for additional information |
|
| on timing considerations. The message is printed when the |
| |
| probably too short. Read |
| |
| driver detects that the configuration requires that a whole table |
| |
| Manual. |
| |
| be read and the timeout value is set below the recommended |
| |
|
|
| |
|
| minimum of 15s for this operation. |
|
|
| This error message should only be produced by FST’s QA |
|
| CarrDL:#19 Err. Diagnostic. | testing procedure. If you see this error, call Tech Support after |
|
| Call Support. | taking a log. Instructions for taking a log may be found in the |
|
|
| Trouble Shooting Guide. |
|
|
| The message is printed once and suppressed for subsequent |
|
|
| occurrences. The message is printed when writing a time to a |
|
| CarrDL:#20* FYI. Invalid | Carrier Device which is invalid as it is greater than 23:59. |
|
| Time(%02d:%02d) being | Check the value in the Data Array being used for the write. It’s |
|
| written. MD=%s | possible an upstream device sent an invalid value. The driver |
|
|
| sends the message with the invalid time and it’s up to the |
|
|
| Carrier device to reject the setting. |
|
|
| The message is printed once and suppressed for subsequent |
|
| CarrDL:#21* FYI. Invalid | occurrences. The message is printed when the Server is |
|
| Time(%02d:%02d) being | required to store an invalid time (>23.59). Check the value in |
|
| stored. MD=%s | the Data Array being used for the write. The data is stored |
|
|
| despite the warning. |
|
|
| These errors occur when communications are operating |
|
| CarrDL:#23* Err. CarrDL | correctly but the CarrDL device cannot respond to the poll. |
|
| The reason error is reported in the driver stats (See Appendix |
| |
| device reported errors. | C.1) Stat #9, reports the error number of the most recent error |
|
| Check exposed stats | reported. The message is printed once and then suppressed. |
|
|
| These errors are most commonly produced when a table |
|
|
| name/ variable name does not exist or is |
|
|
| DOW and times require that the Data_Type be specified when |
|
|
| writing to enable the Driver to convert the value extracted from |
|
| CarrDL:#22* FYI. Read | the Data Array for formatting in the write message. This error |
|
| is printed if the table name or the field name contain the sub- |
| |
| notes for #22 in Manual. |
| |
| string “OCC”, the function is a write, and a Data_Type has not |
| |
| MD=%s |
| |
| been specified. In most cases the write will be rejected by the |
| |
|
|
| |
|
| Carrier device or the value may not be what you expect. Refer |
|
|
| to Section 4.4.7 for more information. |
|
§Correct the error by editing the configuration CSV file, downloading the corrected file to the FieldServer and then resetting the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)