FieldServer Kernel Error Messages and Descriptions

Kernel Version: 5.22

Document Revision: 4

 

Error Description Action
10003 A write to a Data Array exceeds the available space. Check Map Descriptor Offset, length.
10004 A write to a Byte/FloatData Array exceeds the available space. Check Map Descriptor Offset, length.
10005 A range of data exceeds the length of a BYTE Data Array. Check Map Descriptor Offset, length, count
10009 Protocol not detected. Check Node_Name in csv file.
10010 No connection defined for an existing Physical Node Descriptor. Confirm that Active Map Descriptors are not added to a Server Node.
Define the Client Node Descriptor connection in the CSV file.
10011 Unable to create a Client Node Descriptor, since no valid channel adapter or port has been specified. Specify a valid channel adapter or port.
10014 Attempting to read a range past the end of BYTE Data Array. Check Map Descriptor Offset, length, count.
10016 Could not find or create Node Check Node_Name, Node_ID and protocol in CSV file.
10019 Check CSV file spelling.
10023 Protocol or Node_Name for Map_Descriptor not detected Check CSV file.
10025 Modbus/TCP – Client goes offline before receiving a response to a poll. Increase the timeout on the Modbus/TCP Client.
10026 There is no connection to one side of a virtual wire Ensure that a Client and a Server is configured for each virtual wire
10027 Connection mode of Hot_Standby_Data only supported in Hot Standby Mode1
10028 Could not find nor create a Node. Refer to 10010
10031 The data_points limit on the FieldServer has been
reached
Contact FST.
10032 A Server Node has been assigned to a Client Map
Descriptor OR a Client Node does not have a connection/Server_Name
Check CSV file.
10033 Invalid length specified for Cable_Status_Bits See specification inSection 10.3.8.2
10034 An attempt to generate a write cache block failed
because the Node did not have a connection.
10034 A protocol was specified in the configuration file, but the required driver is not loaded in the firmware (CB8MENU). Correct the protocol in the configuration file Obtain the correct DCC
10038 The FieldServer did not respond due to a Data Array Age time exceeding the Cache Age time limit. Increase Cache Age setting in the configuration file.
10039 There was a message overrun on Modbus TCP slave driver. The Client is polling too often for the FieldServer to respond and there is more than one message in the in-buffer. There should be overrun statistics on the Server Connection in question. Increase the timeout on the Client device.
10040 Same as 10039, except the overrun is more than two messages. Increase the timeout on the Client device.
10041 Invalid move function specified in configuration file, or move not defined. Fix the configuration error
10042 High and Low Scaling values are equal
10045 Move overruns Data Array. This usually means that the offset PLUS the length of the Move command is larger than the length of the Data Array. Actions:
Check Data_Array Length: Check Move settings,
Target_Offset, Source_Offset, Client_Offset, Server_Offset,
Feedback_Offset, Mode_Offset, Length
10046 Move Offset lies outside the Data Array. This usually means that the offset of the Move command is larger than the length of the Data Array. Actions:
Check Data_Array Length: Check Move settings,
Target_Offset, Source_Offset, Client_Offset, Server_Offset,
Feedback_Offset, Mode_Offset, Length
10047 Could not find Source Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10048 Could not find Target Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10049 Could not find Client Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10050 Could not find Server Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10051 Could not find Feedback Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10052 Could not find Mode Data Array for Move. Make sure that the specified Data Array exists before specifying move.
10053 Data Array already has a responsible move
10054 Setpoint Moves are only allowed to be 1 item in length
10055 A move was defined, and a write occurred to the target Data Array, but cannot transfer to the Source Data Array because no Responsible Active Map Descriptor is defined.
10056 A move was defined, and a write occurred to the target Data Array, but cannot transfer to the Source Data Array because the Node associated with the Responsible Active Map Descriptor is offline.
10058 8051bp03 or CB8MENU found SMCTCP.INI and FS_TCP.INI files, so it will delete FS_TCP.INI and use SMCTCP.INI in future.
10059 Old version of RUIBOOT.EXE being used. Obtain latest RUIBOOT or use manual method of setting IP address – see Utilities manual.
10070 Illegal Node_ID.
10071 Map Descriptor length of 0 is not allowed.
10072 Map Descriptor length too large.
10073 Illegal Data Type for J-Bus. Legal values = AI AR DI DR.
10074 An attempt to generate a write cache block failed because the Node did not have a connection.
10075 Illegal Map Descriptor address.
10076 This section of Data Array already has a responsible Map Descriptor.
10077 Unable to add parameters from this line. Ensure Map Descriptor headings are included in the .CSV file.
10079 Map Descriptor length greater than Data Array length
10082 Failed attempt to do a Modbus read from Node_ID 0. Only writes can be broadcast.
10083 Illegal Modbus Map Descriptor length
10084 Illegal Modbus Map Descriptor address
10085 Check backup station number settings…
10085 PLC_Port_Count set to 1, but Hot Standby not configured for Mode2. Set FieldServer parameter hs_mode to mode2
10087 Protocol specified in config file, but no such driver is loaded.
10089 Illegal Modbus Node ID Must be in range 1 to 255.
10102 An attempt to generate a write cache block failed because the Node did not have a connection Typically a Node has a Server_Name specified, and a write to this Node occurred before the Server_Name mechanism discovered a valid connection.
10103 The maximum number of concurrent cache blocks has been exceeded. A write cache_block poll did not occur
10104 Connection mode of Hot_Standby_Data is only supported in Hot Standby Mode1
10105 PLC_Port_Count = 1 only supported in hot_standby mode2. Set FieldServer parameter hs_mode to mode2
10106 An invalid hot_standby_mode has been specified as part of the FieldServer parameters, check hsb_p(s).ini files
10107 Could not create cache block – possibly because the maximum number of data_points has been exceeded Contact FST.
10108 A BACNet alarm event was generated but the required Alarm Limits has not been set
10110 Hot_Standby “partner_discover” found a PRIMARY SECONDARY mismatch
10111 Hot_Standby “partner_discover” found an API Version mismatch
10112 Hot_Standby “partner_discover” found a DCC version mismatch
10113 Hot_Standby “partner_discover” found a config file mismatch
10114 A Node_ID > 255 was used in the Hot_Standby commbit configuration.
10116 A port other than P1/R1 was specified on an X20. The port handle has been changed to point to the only UART on X20.
10117 The Gateway Address for adapter N1 has not been specified. This  FieldServer will only be accessible on the local TCP/IP subnet.
10118 The NETMASK for adapter N1 or N2 has not been specified. This FieldServer will not be accessible on the TCP/IP network through one or both of these adapters.
10119 The IP_ADDRESS for adapter N1 or N2 has not been specified. This FieldServer will not be accessible on the TCP/IP network through one or both of these adapters.
10120 An unrecognized rui_command was received. Check that the Ruinet and Kernel versions match.
10125 In the BACNet driver, the OPTION_LIST specified caused the packet buffer to be exceeded. As a result the packet buffer was truncated.
10126 The BACNet driver received a request for a read_property_multiple with multiple objects. This is not reported in the current release of the BACNet driver.
10127 An UDP socket buffer overflowed and UDP data was lost. style=”border: 1px solid rgb(0, 0, 0);”
10128 The keyword MY_IP has been used in the FS_TCP.INI file. Only use KW_N1 and KW_N2
10129 The keyword N1_IP has been used in the SMCTCP.INI file. Use the FS_TCP.INI file.
10130 UDP broadcast panics has been disabled until a hardwired send is added
10133 The ARP resolve queue has been overrun. This is typically the result of a mis-configuration on the FieldServer. Check all IP_addresses, in particular the gateway address.
10134 A cache block was not created The Client side plc_channel has not yet been discovered, or an attempt to write to an Analog_Input Data_Type
10136 A temporary write block has been removed because an identical one existed. Write data might have been lost.
10209 Warning: the Server is responding with data from an explicit Map Descriptor that is not reading continuously
10210 Info: the inet Server received a write to input command that is not supported.
10214 Warning: A Server side driver tried to read from a Data_Object that has a WRBX as a responsible Map Descriptor. The data being read from the Server side might not be the same as on the Client side.
10216 A Server node is associated with more than one Client Node.
10302 An IP Fragmented packet was received while IP Defragmentation was disabled. Display “RX IP fragments” stat in the Ethernet api stat screen. If this occurs frequently enable IP Defragmentation
10401 The I/Net Server ignored a write to an Input
10402 The Baud Rate on a Connections Port has not been defined. A default value will be used.
10403 The MSTP driver must run at a cycle time shorter that 10ms or proper operation cannot be guaranteed
10404 The Write Queue is full and data has been overwritten. This could be caused by using moves to do multiple write-thru’s on a RDBC Map Descriptor. Solve by increasing the Write_Queue_Size or slowing write-thru’s.
10999 Up to and including
11001 Lutron driver: Data Array length for Area names too small Increase Data_Array_Length in .CSV file.
11002 Lutron driver: Data Array length for Scene names too small Increase Data_Array_Length in .CSV file.
11003 Lutron driver: Data Array length for Zone names too small Increase Data_Array_Length in .CSV file.
11004 Envirotronics SystemsPlus driver: The name entered in the SysPlus_Cmd mapdesc field is not recognized or was not entered at all. This field must be filled in with a valid SysPlus_Cmd.
11005 Envirotronics SystemsPlus driver: The name entered in the SysPlus_Data_Type mapdesc field is not recognized or was not entered at  all. This field must be filled in with a valid SysPlus_Data_Type.
11006 Envirotronics SystemsPlus driver: The name entered in the  Store_Data_Array_Name mapdesc field is not valid or was not entered at all. This field must be filled in with a valid Data Array name.
11007 Envirotronics SystemsPlus driver: The name entered in the  Par_Data_Array_Name mapdesc field is not valid or was not entered at all. This field must be filled in with a valid Data Array name.
11008 Envirotronics SystemsPlus driver: The name entered in the SysPlus_Alarm_Name mapdesc field is not valid or was not entered at all. This field must be filled in with a valid Data Array name.
11009 Envirotronics SystemsPlus driver: The requested number of events or auxs to set is more than set up in the parameter Data Array.. Reduce number of events or auxs or increase parameter Data Array length
11010 Siemens Cerberus driver: The counts Data Array has less than 14 data elements per panel and event countds could not be stored. Increase the number of data elements in the counts Data Array to 14 elements per panel.
11011 Siemens Cerberus driver: The Client driver could not find a suitable Map Descriptor to store the incoming event. The error message reported the event’s panel, module and device numbers. Use the event’s panel, module and device numbers to define a Map Descriptor with Node_Name = panel.
e.g For message: DRIVER-> CER : No mapdesc for panel 2, module 15, device 4, Create a mapdesc that will map to an address of15*256 + 4 = 3844, since there are always 256 devices per module for Cerberus.
The mapdesc field block_number represents the Cerberus module number. A Cerberus mapdesc maps to addresses from module*256 + 0 to module*256 + (length-1), e.g. the following addresses are defined for a mapdesc of module 15 and length 4: (15*256 +0) ; (15*256 +1) ; (15*256 +2) ; (15*256 +3).Our example event will cause this error message since the greatest address is (15*256 +3) = 3843 and we need an address of 3844. A mapdesc with module 15 and length 5 will store the event ok, since (15*256 + (5-1)) = (15*256 +4) = 3844.
11012 Envirotronics SystemsPlus driver: The SystemsPlus panel replied with “Not Monitored” when the driver tried to edit read scan alarm or tried to read alarm status. The driver message screen records the specific alarm’s name Refer to the SystemsPlus user manual to set up the alarm for monitoring in the panel. This message can only be solved in the panel and is not a driver problem.
11013 A BACnet Ethernet packet was received on a network adapter that is not configured in the CSV file. Message will be ignored. If BACnet comms fail, check the configuration and network connection.
11014 An 802.3 (Hot Standby) packet was received on an incorrectly configured network adapter. Packet will be discarded.
11015 GE SRTP – SD016 message indicates NAK error.
If you liked this post;
  • Please consider subscribing to our RSS feed