|
|
| Page 20 of 24 |
| |||||
|
|
|
|
|
|
|
|
|
|
|
| Message |
|
| Description |
|
|
|
|
|
| FCI7100:#12a Err. No MD's to store message |
| A message arrived and the driver could |
| ||||
|
| data. |
|
| not find a place to store the data. |
| |||
|
| FCI7100:#12b Err. No MD's to store message |
| Perhaps you were not expecting this type |
| ||||
|
| data." |
|
| of event/this loop/sensor. | If you are not |
| ||
|
| FCI7100:#13 Err. Msg was ignored. MD Required |
| interested in the data then ignore the |
| ||||
|
|
| message. | Otherwise | update | the |
| ||
|
| for Storage. |
|
| configuration file. 3 |
|
|
| |
|
| FCI7100:#13a Err. Diagnostic 1); |
| Take a log. Try and repeat the event that |
| ||||
|
| FCI7100:#13b Err. Diagnostic 2); |
| caused the message to be printed. Then |
| ||||
|
| FCI7100:#13c Err. Diagnostic 3); |
| contact tech support. |
|
|
| ||
|
| FCI7100:#14 Err. <%s> file not found., md- |
|
|
|
|
|
| |
|
| >mapdesc_name ) ; |
| If this error is repeated often it is possible |
| ||||
|
| FCI7100:#15 Err. Event Type=<%s> Not |
|
| |||||
|
|
| that a FCI firmware update as made the |
| |||||
|
| recognized." , |
| driver unusable. Take a log and contact |
| ||||
|
| FCI7100:#16 Err. Point Type='%c'(%#x) Not |
|
| |||||
|
|
| tech support. |
|
|
|
| ||
|
| recognized. , |
|
|
|
|
|
| |
|
| >point_identifier[0] ) ; |
|
|
|
|
|
| |
|
|
|
|
| This message should only be printed if a |
| |||
|
| FCI7100:#17 Err. Loop=%d < 1. Rejected. , |
| byte in a message has been corrupted. If |
| ||||
|
|
|
| you notice it more than once then take a |
| ||||
|
|
|
|
| log and contact tech support. |
|
| ||
|
| FCI7100:#18 Err. Loop Type='%c'(%#x) Not |
| If this error is repeated often it is possible |
| ||||
|
|
| that a FCI firmware update as made the |
| |||||
|
| recognized. , |
| driver unusable. Take a log and contact |
| ||||
|
| >point_identifier[2] ) |
| tech support. |
|
|
| ||
|
|
|
|
|
|
|
| ||
|
| FCI7100:#19 Err. Relay=%d < 1. Rejected. , |
| This message should only be printed if a |
| ||||
|
|
|
| byte in a message has been corrupted. If |
| ||||
|
| FCI7100:#20 Err. Zone=%d < 1. Rejected. , |
| you notice it more than once then take a |
| ||||
|
|
|
| log and contact tech support. |
|
| |||
|
| FCI7100:#21 Err. Point Type not recognized |
| Valid Point Types are listed in section |
| ||||
|
| FCI7100:#22 Err. Undefined Point Type" | 4.4.23 |
|
|
|
| ||
|
| FCI7100:#23 Err. Event Type not recognized |
| Valid Event Types are listed in section |
| ||||
|
| FCI7100:#24 Err. Undefined Event Type | 4.4.23 |
|
|
|
| ||
|
| FCI7100:#25a | Err. Address+Length>99. Length |
| The maximum value for a sensor/module |
| |||
|
| Truncated |
|
| is 99. The combination of address and |
| |||
|
| FCI7100:#25b | Err. Address+Length>99. Length |
|
| ||||
|
|
| length specified produce a number > 993 |
| |||||
|
| Truncated |
|
|
|
|
|
|
|
|
| FCI7100:#26 | Err. Invalid Module number. |
|
|
|
|
|
|
|
| Expected 1..99 |
|
|
|
|
|
|
|
|
| FCI7100:#27a Err. Invalid Loop number. Expected |
|
|
|
|
|
| |
| 1..10 |
|
| Correct the configuration file3 |
|
| |||
|
|
|
|
| |||||
|
| FCI7100:#27b Err. Invalid Loop number. Expected |
|
|
|
|
|
| |
| 1..10 |
|
|
|
|
|
|
| |
|
| FCI7100:#27c Err. Invalid Loop number. Expected |
|
|
|
|
|
| |
| 1..10 |
|
|
|
|
|
|
| |
3Correct the configuration file, download to the FieldServer and restart the FieldServer for the changes to take effect.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)