27::
1086:
Com. OK with RIO\n
Description\Reason:\n
- Contact established with RIO node\n
  connected at node address %d\n
\t\n
Check list:\n
1. Do nothing.
1090:
Invalid unit type.\n
Description\Reason:\n
- The vendor id read from\n
  unit %s doesn't match\n
  value in unit type configuration.\n
  Configuation: %d   Actual: %d\n
\t\n
Check list:\n
1. Change vendor id in configuration.\n
2. or check module.
1091:
Invalid unit type.\n
Description\Reason:\n
- The profile read from\n
  unit %s doesn't match\n
  value in unit type configuration.\n
  Configuration: %d   Actual: %d\n
\t\n
Check list:\n
1. Change profile in configuration.\n
2. Check that the type of board is\n
   correct.
1092:
Invalid unit type.\n
Description\Reason:\n
- The product code read from\n
  unit %s doesn't match\n
  value in unit type configuration.\n
  Configuration: %d   Actual: %d\n
\t\n
Check list:\n
1. Change product code in configuration\n
2. or check module.
1093:
Invalid unit type.\n
- The major revision read from\n
  unit %s doesn't match\n
  value in unit type configuration.\n
  Configuration: %d   Actual: %d\n
\t\n
Check list:\n
1. Change major revision.\n
2. or check module.
1096:
PLC in programming mode\n
Description\Reason:\n
- Can't access the board due to\n
  the PLC in programming mode\n
  or the RIO is configured\n
  incorrectly.\n
\t\n
Check list:\n
1. PLC in programming mode\n
2. Check RIO configuration
1100:
Bus table full.\n
Description\Reason:\n
- The number of buses\n
  must not exceed %d\n
\t\n
Check list:\n
1. Reduce the number of buses.\n
2. Increase the number of buses\n
   allowed.
1105:
Disable group failed\n
Description\Reason:\n
- Failed to disable unit %s\n
  at address %d.%d\n
\t\n
Check list:\n
1. Check I/O system parameters\n
2. Check unit
1106:
IBS board failure\n
Description\Reason:\n
- Faulty IBS board\n
  Board internal error code: %X\n
  Warm start required.\n
\t\n
Check list:\n
1. Check above error, see IBS manual:\n
   Firmware Service and Error Messages\n
2. Update board firmware\n
3. Replace IBS board
1107:
IBS bus failure\n
Description\Reason:\n
- BUS ERROR reported\n
  Lost contact at address\n
  %d.%d\n
\t\n
Check list:\n
1. Check the unit at\n
   the above address\n
2. Check cables at\n
   the above address
1108:
IBS module failure\n
Description\Reason:\n
- Unit %s at address %s\n
  reported peripheral fault.\n
  IBS error code: %X\n
\t\n
Check list:\n
1. Check the unit at\n
   the above address\n
2. Check above error, see IBS manual:\n
   Firmware Service and Error Messages
1109:
IBS bus failure\n
Description\Reason:\n
- Lost contact with IBS network\n
  No error message from IBS board.\n
\t\n
Check list:\n
1. Check the IBS network.
1110:
IBS bus failure\n
Description\Reason:\n
- Lost contact at address %d.%d\n
  IBS error code: %X\n
\t\n
Check list:\n
1. Check IBS bus\n
   at the above address\n
2. Check above error, see IBS manual:\n
   Firmware Service and Error Messages
1111:
Wrong product code.\n
Description\Reason:\n
- The product code of unit %s\n
  doesn't compare to actual.\n
  Product code is %d, expected %d\n
\t\n
Check list:\n
1. Change product code in configuration\n
2. Replace module or\n
3. Use predefined unit types,\n
   ibsGeneric and ibsSlave.
1112:
Unequal # of units.\n
Description\Reason:\n
- Definied number of units is different\n
  to the one binded to the board.\n
\t\n
Check list:\n
1. Change unit definition in\n
   the configuration.\n
2. or check the modules.
1116:
Disable & Trust Level = 0\n
Description\Reason:\n
Unit '%s' has been configured\n
disabled with Trust Level set to 0.\n
This is NOT allowed.\n
\t\n
Check list:\n
1. Change the configuration.
1134:
Parameter value not found\n
Description\Reason:\n
Unit %s refers to values(%s)\n
that don't exists.\n
\t\n
Check list:\n
1. Check unit configuration.
1135:
Parameter defs. not found\n
Description\Reason:\n
Unit type %s refers to\n
parameter definitions (%s)\n
that don't exists.\n
\t\n
Check list:\n
1. Check unit type configuration.
1136:
Parameter Error\n
Description\Reason:\n
Parameter %s could not be\n
downloaded to unit %s\n
\t\n
Check list:\n
1. Check unit configuration.\n
2. Check precceding error messages
1138:
Unknown Parameter\n
Description\Reason:\n
%s is not a valid parameter\n
for unit %s\n
\t\n
Check list:\n
1. Check unit parameter configuration.
1144:
Enable group failed\n
Description\Reason:\n
- Failed to enable unit %s\n
  at address %d.%d\n
\t\n
Check list:\n
1. Check I/O system parameters\n
2. Check unit
1145:
IBS bus deactivated\n
Description\Reason:\n
- IBS bus changed into a none\n
  running mode.\n
\t\n
Check list:\n
1. Restart the system\n
2. Check that correct IBS boot project\n
   is selected.
1147:
No response IBS\n
Description\Reason:\n
- Access to the IBS is denied\n
\t\n
Check list:\n
1. Check the IBS board\n
2. Check IBS internal configuration\n
3. Reduce cycle time on the slave unit
1148:
No access to IBS\n
Description\Reason:\n
- Access to the IBS service interface\n
  is denied during %s,\n
  error code is 0x%x\n
\t\n
Check list:\n
1. Check IBS internal confiuration\n
2. The IBS is faulty. Replace board
1149:
IBS command failure\n
Description\Reason:\n
- Incompatible definition\n
  due to %d!\n
\t\n
Check list:\n
1. Check the I/O system parameters\n
2. Restart the system
1150:
The IBS is busy\n
Description\Reason:\n
- The response service capability\n
  is limited due to IBS configuration\n
\t\n
Check list:\n
1. Check IBS internal configuration\n
2. Change cycle time on the slave unit
1152:
IBS bus failure\n
Description\Reason:\n
- %s bus failure.\n
  Lost contact at\n
  address %d.%d\n
\t\n
Check list:\n
1. Check IBS bus\n
   at the above address\n
2. Restart the system
1154:
The unit has no power\n
Description\Reason:\n
- Unit %s has\n
  no power connected\n
\t\n
Check list:\n
1. Attach power to the unit
1155:
The unit is faulty\n
Description\Reason:\n
- Unit %s has\n
  not been correctly connected\n
\t\n
Check list:\n
1. Diagnose with CMD application\n
2. Modify the IBS local start-up\n
   procedure\n
3. Replace the IBS firmware
1158:
Address out of range\n
Description\Reason:\n
- The address of unit %s is out of\n
  range.\n
\t\n
Check list:\n
1.Change the address\n
2.Check the address syntax
1170:
Delay table full\n
Description\Reason:\n
- The number of delays in a queue is\n
  greater than %d.\n
\t\n
Check list:\n
1.Make another call
1172:
Illegal watchdog time\n
Description\Reason:\n
- The watchdog time for unit %s\n
  must be larger than the largest\n
  min_slave_interval = %d.\n
\t\n
Check list:\n
1. Increase the watchdog time
1173:
Illegal MaxTsdr\n
Description\Reason:\n
- The MaxTsdr for unit %s is larger\n
  than the MaxTsdr for the bus = %d.\n
\t\n
Check list:\n
1. Increase MaxTsdr for the bus\n
2. or set the bus MaxTsdr to -1\n
3. Check the unit type configuration
1174:
Illegal MinSlaveInt\n
Description\Reason:\n
- The MinSlaveInt for unit %s is larger\n
  than MinSlaveInt for bus = %d.\n
\t\n
Check list:\n
1. Increase MinSlaveInt for the bus\n
2. or set the bus MinSlaveInt to -1\n
3. Check the unit type configuration
1175:
Illegal Data_Ctrl_Time\n
Description\Reason:\n
- The Data_Ctrl_Time must be larger\n
  than %d (6 * T_WatchDog for\n
  unit %s)\n
\t\n
Check list:\n
1. Increase Data_Ctrl_Time for the bus\n
   or set the bus Data_Ctrl_Time to -1\n
   or decrease T_WatchDog for the\n
   I/O Unit.
1176:
Illegal T_TargetRot\n
Description\Reason:\n
- The T_TargetRot must be smaller\n
  than %d (T_WatchDog (%d)\n
  for unit %s)\n
\t\n
Check list:\n
1. Decrease T_TargetRot for the bus\n
   or set the bus T_TargetRot to -1\n
   or increase T_WatchDog for the\n
   I/O Unit
1177:
No contact with I/O unit\n
Description\Reason:\n
- I/O Unit %s is already locked by\n
  another master.\n
\t\n
Check list:\n
1. Remove the I/O Unit from the other\n
   masters configuration.\n
2. Restart the system.
1178:
Incorrect User Prm Data\n
Description\Reason:\n
- I/O Unit %s reports incorrect\n
  parameter data.\n
\t\n
Check list:\n
1. Modify the User Prm Data according\n
   to the DP-slaves manual.\n
2. Restart the system.
1179:
Service not supported\n
Description\Reason:\n
- I/O Unit %s reports that an\n
  unsupported functionality\n
  was requested.\n
\t\n
Check list:\n
1. Check the Sync_Req parameter\n
2. Check the Freeze_Req parameter\n
3. Restart the system.
1180:
Incorrect configuration\n
Description\Reason:\n
- I/O Unit %s reports incorrect\n
  configuration data.\n
\t\n
Check list:\n
1. Check all Module parameters\n
   for the I/O Unit.\n
2. Restart the system.
1181:
Dsqc368 board missing.\n
Description\Reason:\n
- ProfiBus DP-master and DP-slave\n
  board is not connected or is.\n
  not working properly.\n
  (internal info: %d).\n
\t\n
Check list:\n
1. Connect board.\n
2. Run board diagnostics.\n
3. Replace board.
1182:
Missing signal name\n
Description\Reason:\n
- A signal name was expected at\n
  position %d in cross-connection\n
  actor %s.\n
\t\n
Check list:\n
1. Correct the cross-connection syntax\n
   in the EIO-configuration file.\n
2. Restart the system.
1183:
Missing logical operator\n
Description\Reason:\n
- A logical operator was expected\n
  before %s in cross-connection\n
  actor %s.\n
\t\n
Check list:\n
1. Correct the cross-connection syntax\n
   in the EIO-configuration file.\n
2. Restart the system.
1184:
Illegal logical operator\n
Description\Reason:\n
- A unexpected logical operator in\n
  %s at cross-connection\n
  actor %s.\n
\t\n
Check list:\n
1. Correct the cross-connection syntax\n
   in the EIO-configuration file.\n
2. Restart the system.
1185:
Duplicated name\n
Description\Reason:\n
- The name %s has already been\n
  used. It has either been used as a\n
  BUS, TYPE, UNIT, or SIGNAL.\n
\t\n
Check list:\n
1. Remove one of the names\n
   in the EIO-configuration file.\n
2. Restart the system.
1186:
Illegal serial channel\n
Description\Reason:\n
- The serial channel %s\n
  was not possible to create.\n
\t\n
Check list:\n
1. Remove the option from configuration.
1187:
Abnormal rate of errors\n
Description\Reason:\n
- An abnormal rate of errors\n
  on ProfiBus DP-master bus.\n
  Service IND: %s. Reason: %d\n
\t\n
Check list:\n
1. Check bus connections\n
2. Check terminators.
1188:
PBUS disconnected\n
Description\Reason:\n
- A major error on bus has been\n
  detected on ProfiBus DP-master\n
  bus.\n
\t\n
Check list:\n
1. Check previous message for reason\n
2. A restart is required.
1189:
Profibus bus param error\n
Description\Reason:\n
- Faulty bus parameters has been\n
  downloaded into the Profibus system\n
  Parameter: %s. Value %d.\n
\t\n
Check list:\n
1. Change bus parameter
1190:
Illegal module definition\n
Description\Reason:\n
- Unit %s has zero bytes input and\n
  output according to the module\n
  definitions.\n
\t\n
Check list:\n
1. Check all Module parameters\n
   for the I/O Unit.
1191:
No receiver sync\n
Description\Reason:\n
- Profibus master synchronization error\n
\t\n
Check list:\n
1. Check for short circuits\n
2. Check cable connections\n
3. Check termination\n
4. Bad shielding
1192:
Physical IO mapping error\n
Description\Reason:\n
- IO Mapping error on unit %s.\n
  Physical signal %s-%d\n
  overrides %s-%d\n
\t\n
Check list:\n
1. Check configuration for physical\n
   signal mapping
1193:
Phys. IO mapping error\n
Description\Reason:\n
- IO Mapping error on unit %s.\n
\t\n
Check list:\n
1. Check configuration for physical\n
   signal mapping
1194:
Illegal physical signal\n
Description\Reason:\n
- Physical signal %d on unit %s.\n
  is of type %s,\n
  it should be of type AI, AO, DI or DO.\n
\t\n
Check list:\n
1. Check configuration for physical\n
   signal type
1195:
Illegal I/O Unit\n
Description\Reason:\n
- The unit %s is not\n
  a configured unit\n
\t\n
Check list:\n
1. Change the name to an existing unit\n
2. Add a new unit to the configuration
1196:
Invalid encoding type\n
Description\Reason:\n
- The encoding type: %s for\n
  physical signal %s-%d on\n
  unit %s is invalid.\n
\t\n
Check list:\n
1. Change the encoding type in the\n
   configuration
1197:
Signal bitswap error\n
Description\Reason:\n
- The NoOfBits and StartBit is not\n
  valid for bitswap on signal\n
  %s-%d at unit %s.\n
\t\n
Check list:\n
1. Check that NoOfBits and StartBit\n
   is valid for signal bitswap.\n
    NoOfBits = 16 or 32\n
    StartBit = even multiple of NoOfBits
1198:
Address out of range\n
Description\Reason:\n
- The address of bus %s is out of\n
  range.\n
\t\n
Check list:\n
1.Change the address\n
2.Check the address syntax
1199:
Baudrate out of range\n
Description\Reason:\n
- The baudrate of bus %s is out of\n
  range.\n
\t\n
Check list:\n
1.Change the baudrate\n
2.Check the baudrate syntax
1200:
Invalid slave response\n
Description\Reason:\n
- I/O Unit %s sends\n
  invalid slave responses\n
\t\n
Check list:\n
1. Check User_Prm_Data\n
2. Restart the system.
1201:
Unknown bus\n
Description\Reason:\n
- %s can not be found in the system\n
\t\n
Check list:\n
1. Check the bus configuration\n
2. Check the installed options.
1202:
Phys. value out of range\n
Description\Reason:\n
- Signal %s-%d at unit %s:\n
  Physical Max is less or equal to\n
  Physical Min\n
\t\n
Check list:\n
1. Correct the values to be max\n
   greater than min
1203:
Phys. value out of range\n
Description\Reason:\n
- Signal %s-%d at unit %s:\n
  HighAnalog is less or equal to\n
  LowAnalog\n
\t\n
Check list:\n
1. Correct the values to be max\n
   greater than min
1204:
Phys. value out of range\n
Description\Reason:\n
- Signal %s-%d at unit %s:\n
  HighDigital is less or equal to\n
  LowDigital\n
\t\n
Check list:\n
1. Correct the values to be max\n
   greater than min
1206:
Different bus driver\n
Description\Reason:\n
- The driver given for '%s'\n
  '%s' differs\n
  from the default driver '%s'\n
  The default driver will be used.\n
\t\n
Check list:\n
1. Check configuration for the\n
   bus in EIO-configuration file
1207:
Errors in bus config.\n
Description\Reason:\n
- Errors detected in configuration\n
  for bus '%s'\n
  The default values will be used.\n
\t\n
Check list:\n
1. Check configuration for the\n
   bus in EIO-configuration file
1208:
Unable to configure bus\n
Description\Reason:\n
- Unable configure bus '%s'\n
  according to user settings\n
  The default values will be used.\n
  Internal error code: %d\n
\t\n
Check list:\n
1. Check configuration for the\n
   bus in EIO-configuration file
1209:
Bus not internally loaded\n
Description\Reason:\n
- Bus %s is not internally loaded\n
  and will therefore not be\n
  configured\n
\t\n
Check list:\n
1. Remove the bus from your\n
   EIO-configuration file\n
   and reload it.
1220:
Option not found\n
Description\Reason:\n
- A DSQC510 board was found but the\n
  Profibus option is not installed.\n
\t\n
Check list:\n
1. Install option.\n
2. Change board.
1221:
DSQC510 file not found\n
DSQC510 %s firmware file not\n
found or not readable. The board\n
firmware may be out of date.\t
1222:
Profibus file not found\n
Description\Reason:\n
- The binary Profibus configuration was\n
  not found.\n
  file: %s\n
  path: %s\n
\t\n
Check list:\n
1. Make sure the file exist.\n
2. Change the path in the\n
   EIO-configuration.
1223:
Profibus file parse error\n
Description\Reason:\n
- The binary Profibus configuration file\n
  is corrupt. (Internal error: %s)\n
  file: %s\n
  path: %s\n
\t\n
Check list:\n
1. Recreate and download the binary\n
   configuration file using the external\n
   Profibus configuration tool.
1224:
Profibus channel flashed\n
Description\Reason:\n
- The %s channel firmware of the\n
  Profibus board has been updated\n
  from %s\n
  to %s.
1225:
Profibus cfg error\n
Description\Reason:\n
- The local slave channel has\n
  more DI/DO than the configuration\n
  in its master.\n
\t\n
Check list:\n
1. Make the number of DI/DO of the\n
   external Profibus master more\n
   or equal than the local slave.
1226:
Profibus cfg ok\n
Description\Reason:\n
- The number of DI/DO of the external\n
  Profibus master is now more or equal\n
  than for the unit of DP_SLAVE type.
1227:
Profibus init failed\n
Description\Reason:\n
- The initialization of the local\n
  Profibus slave failed.\n
\t\n
Check list:\n
1. Restart the system\n
2. Change board
1228:
Profibus binary cfg fault\n
Description\Reason:\n
- The configuration data in the binary\n
  file is not accepted by the slave at\n
  address %i.\n
\t\n
Check list:\n
1. Make the configuration data in the\n
   binary file match the configuration\n
   for the slave and reboot the system
1229:
Profibus binary prm fault\n
Description\Reason:\n
- The parameter data in the binary file\n
  is not accepted by the slave at\n
  address %i.\n
\t\n
Check list:\n
1. Make the parameter data in the\n
   binary file match the parameters for\n
   the slave and reboot the system
1230:
Unit configuration error\n
Description\Reason:\n
- Unit %s is configured\n
  in system parameters but is missing\n
  or incorrect in profibus binary file.\n
\t\n
Check list:\n
1. Check/change system parameters\n
2. Check/change profibus binary file.
1240:
Unit on wrong bus\n
Description\Reason:\n
- The unit %s cannot reside\n
  on bus %s.\n
\t\n
Check list:\n
1. Move the unit to the SIM bus\n
   and reboot the system
1241:
Too many boards on bus\n
Description\Reason:\n
- The number of boards on bus %s\n
  must not exceed %d.\n
\t\n
Check list:\n
1. Reduce the number of defined boards\n
   and reboot the system
1242:
Wrong number of signals\n
Description\Reason:\n
- Unit %s at address %s consists\n
  of a not supported number of\n
  io-signals, namely %d.\n
  4,8,16,32, etc are supported values\n
\t\n
Check list:\n
1. Exchange the unit.\n
2. Make sure the EIO.cfg is correct\n
3. Reconfigure the IBS network.
1243:
Wrong bus start up state\n
Description\Reason:\n
- IBS must be in RUN state\n
  when robot controller is started.\n
\t\n
Check list:\n
1. Check IBS parameteriztion memory.\n
2. Check that correct IBS boot project\n
   is selected.
1244:
Incorrect IBS unit type\n
Description\Reason:\n
- Unit %s at address %s\n
  has a unit type not supported by\n
  the system.\n
\t\n
Check list:\n
1. Exchange the unit.\n
2. Make sure the EIO.cfg is correct\n
3. Reconfigure the IBS network.
1245:
Unit not defined in IBS\n
Description\Reason:\n
- Unit %d.%d has no address space in\n
  the IBS-system.\n
\t\n
Check list:\n
1. Modify IBS-config. with CMD-tool,\n
   use process data menu.\n
   Add address for the unit.
1246:
No access to IBS data\n
Description\Reason:\n
- Access to the data interface of the\n
  IBS-board is denied. %s not\n
  performed, error code %d.\n
\t\n
Check list:\n
1. The IBS is faulty. Replace board\n
2. Check IBS internal configuration.
1247:
No internal slave conf.\n
Description\Reason:\n
- The internal slave on the IBS\n
  board has not been configured.\n
\t\n
Check list:\n
1. Configure the internal slave with\n
   CMD-tool\n
2. Reboot the system.
1248:
Unit not conf. on IBS-bus\n
Description\Reason:\n
- The unit with address %s has not\n
  been configured on the IBS network\n
\t\n
Check list:\n
1. Make sure the EIO.cfg is correct\n
2. Reconfigure the IBS network.
1249:
Unit not configured\n
Description\Reason:\n
- The unit with address %d.%d is\n
  configured on the IBS network but\n
  not as an I/O parameter\n
\t\n
Check list:\n
1. Make sure the EIO.cfg is correct\n
2. Reconfigure the IBS network.
1250:
Cannot conf. ibs board\n
Description\Reason:\n
- Error downloading configuration files\n
  to IBS board.\n
  IBS error code: %X\n
\t\n
Check list:\n
1. Check path to configuration files.\n
2. Check validity of config. files.\n
3. Check above error, see IBS manual:\n
   Firmware Service and Error Messages
1251:
Signal swap bytes error\n
Description\Reason:\n
- The NoOfBits, StartBit and Phsig\n
  combination is not valid for\n
  SwapBytes on signal %s-%d\n
  at unit %s.\n
\t\n
Check list:\n
1. Check that NoOfBits, StartBit and\n
   Phsig are valid for signal SwapBytes\n
   All shall consist of whole bytes. 
1252:
Signal swap bits error\n
Description\Reason:\n
- The NoOfBits, StartBit and Phsig\n
  combination is not valid for SwapBits\n
  on signal %s-%d at unit\n
  %s.\n
\t\n
Check list:\n
1. Check that NoOfBits, StartBit and\n
   Phsig are valid for signal SwapBits.\n
   All shall consist of whole bytes. 
1253:
Dig. signal bitswap error\n
Description\Reason:\n
- The BitSwap and ByteSwap input switch\n
  is intended only for analog signals\n
  and is not valid for signal %s-%d\n
   at unit %s.\n
\t\n
Check list:\n
1. Use SwapBits and/or SwapBytes instead
1254:
NoOfBits value invalid\n
Description\Reason:\n
- The NoOfBits input value is invalid\n
  for signal %s-%d at unit\n
  %s.\n
\t\n
Check list:\n
1. Check that the value is between 4\n
   and 32.    
1255:
No physical object\n
Description\Reason:\n
- A a physical object for %s-%d\n
  at unit %s could\n
  not be found.\n
\t\n
Check list:\n
1. Check that NoOfBits, StartBit and\n
   Phsig are valid
1256:
Persistent data\n
Description\Reason:\n
- Previous shutdown did not\n
  include persistent data\n
  storage.\n
\t\n
Check list:\n
1. Check power supply\n
2. File system lockup
1257:
IBS slave wrong dev type\n
Description\Reason:\n
- The given device type '2' for unit\n
  with address %s does not match.\n
\t\n
Check list:\n
1. Check EIO cfg-file
1258:
IBS file not found\n
Description\Reason:\n
- Configuration file for the\n
  IBS board was not found.\n
  file: %s\n
\t\n
Check list:\n
1. Make sure the file exist.\n
2. Change the path in the\n
   EIO-configuration.
1259:
Couldn't read IBS file\n
Description\Reason:\n
- Error when reading configuration\n
  file for IBS board.\n
  file: %s\n
\t\n
Check list:\n
1. Download the file ones more\n
   to the robot controller.\n
2. Reboot the system.
1260:
IBS bus failure\n
Description\Reason:\n
- Lost contact on bus.\n
  IBS error code: %X\n
\t\n
Check list:\n
1. Check IBS bus\n
2. Check above error, see IBS manual:\n
   Firmware Service and Error Messages
1261:
Transport layer failure\n
Description\Reason:\n
- The physical channel for transport\n
  layer %s is invalid.\n
\t\n
Check list:\n
1. Verify that the physical channel\n
   is valid, see manual.
1270:
RIO parameter mismatch\n
Description\Reason:\n
- RIO node at address %d will be\n
  restarted automatically, for new\n
  parameters to be valid.\n
\t\n
Check list:\n
1. Do nothing.
1271:
Parameter value error\n
Description\Reason:\n
- DeviceNet parameter on unit %s\n
  Value type or value length incorrect\n
  Path = %s,\n
  status = %d\n
\t\n
Check list:\n
1. Check parameter configuration.
1272:
Parameter syntax error\n
Description\Reason:\n
- DeviceNet parameter path syntax error\n
  on unit %s,\n
  Path = %s,\n
  status = %d\n
\t\n
Check list:\n
1. Check parameter configuration.
1273:
Unit configuration error\n
Description\Reason:\n
- Unit %s not configured in cfg\n
  or binary configuration file.\n
\t\n
Check list:\n
1. Check cfg file\n
2. Check binary file (profibus).
1274:
IBS bus failure\n
Description\Reason:\n
- Unable to determine the bus operating\n
  mode of the IBS board.\n
\t\n
Check list:\n
1. Restart the system
1275:
Couldn't write IBS file\n
Description\Reason:\n
- The flash card is full and needs to\n
  be formatted\n
\t\n
Check list:\n
1. Restart the system.\n
2. or Format the flash card or remove\n
   "NOFORMAT" from the cfg file and\n
   restart the system.
1276:
Regained cont with unit\n
Description\Reason:\n
- Regained contact with\n
  unit '%s'\n
\t\n

1277:
Unable to create bus\n
Description\Reason:\n
- Unable to open/configure bus '%s'\n
  according to user settings.\n
\t\n
Check list:\n
1. Check configuration for the\n
   bus in EIO-configuration file.\n
2. Check bus hardware. 
1279:
IBS bus failure\n
Description\Reason:\n
- Wrong operating mode on the IBS board.\n
\t\n
Check list:\n
1. Use CMD-tool and set Bus Operating\n
   mode to "Asynch mit pulse" and\n
2. Restart the system
1280:
Ana. signal swapbits err\n
Description\Reason:\n
- The SwapBits input switch\n
  is intended only for digital signals\n
  and is not valid for signal %s-%d\n
   at unit %s.\n
\t\n
Check list:\n
1. Use BitSwap instead
1281:
An. signal SwapBytes err\n
Description\Reason:\n
- The SwapBytes input switch\n
  is intended only for digital signals\n
  and is not valid for signal %s-%d\n
   at unit %s.\n
\t\n
Check list:\n
1. Use ByteSwap instead
1282:
Digital input mismatch\n
Description\Reason:\n
- The unit at address %s has no\n
  digital input channels\n
\t\n
Check list:\n
1. Compare the configuration file\n
   with the physical configuration
1283:
Digital output mismatch\n
Description\Reason:\n
- The unit at address %s has no\n
  digital output channels\n
\t\n
Check list:\n
1. Compare the configuration file\n
   with the physical configuration
1284:
Analog input mismatch\n
Description\Reason:\n
- The unit at address %s has no\n
  analog inputs\n
\t\n
Check list:\n
1. Compare the configuration file\n
   with the physical configuration
1285:
Analog output mismatch\n
Description\Reason:\n
- The unit at address %s has no\n
  analog outputs\n
\t\n
Check list:\n
1. Compare the configuration file\n
   with the physical configuration
1286:
Remapping non def. signal\n
Description\Reason:\n
- The remapped signal no %d\n
  on unit %s\n
  has no signal definition\n
\t\n
Check list:\n
1. Check the configuration file for\n
   remapping units and signals.\n
   For each remapped signal there\n
   must exist a signal definition.
1287:
TPU restarted\n
Description\Reason:\n
- Communication was lost between TPU\n
  and IOC.\n
  The TPU has been restarted.\n
\t\n
1. Check external cabling for bad\n
   shielding/electromagnetic\n
   disturbance.\n
2. Check that power and signal\n
   cabling is separated.
1292:
Slave units overflow\n
Description\Reason:\n
- Number of slave units on bus:\n
  %s\n
  exceeds %d\n
\t\n
1. Reduce number of units
1369:
Error on I/O Bus\n
Description\Reason:\n
- An abnormal rate of errors on the\n
  %.8s Bus has been detected.\n
\t\n
Check list:\n
1. Check bus terminators.\n
2. Check I/O bus for short-circuit.\n
3. Restart system.
1370:
Error on I/O Bus\n
Description\Reason:\n
- The DeviceNet channel %.8s\n
  has gone bus off.\n
\t\n
Check list:\n
1. Check bus terminators.\n
2. Check I/O bus for short-circuit.\n
3. Restart system.
1371:
Recieve buffer overrun\n
Description\Reason:\n
- The DeviceNet channel %.8s\n
  recieve buffer overrun.\n
- You have lost one or more\n
  input signals.\n
\t\n
Check list:\n
1. Reduce the load on the DeviceNet.
1372:
Send buffer overrun\n
Description\Reason:\n
- The DeviceNet channel %.8s\n
  send buffer overrun.\n
- You have lost one or more\n
  output signals.\n
\t\n
Check list:\n
1. Reduce the load on the DeviceNet.
1373:
Invalid ModBus Config.\n
Description\Reason:\n
The PLC connecting to the Robot\n
has a faulty configuration.\n
\t\n
Check list:\n
1. First In-register: %d\n
2. Inputs in Bytes: %d\n
3. First Out-register: %d\n
4. Outputs in Bytes: %d.
1374:
ModBus Error\n
Description\Reason:\n
Unit '%s' reported\n
the following error:\n
%s\n
\t\n
Check list:\n
1. Check Device.\n
2. Check Configuration.
1375:
Read buffer overflow\n
Description\Reason:\n
The read buffer for DeviceNet is full\n
and you have lost a signal value.\n
\t\n
Check list:\n
1. Reduce the load on DeviceNet.
1376:
Recovery Time Ignored\n
Description\Reason:\n
The recovery time for "BASE" is zero in\n
the config file. Since it's not allowed\n
to have recovery time zero for "BASE",\n
the default value is used (5s).\n
\t\n
Check list:\n
It is recommended to use the default\n
value for RecoveryTime for "BASE".\n
Check the EIO config file and change\n
RecoveryTime for "BASE".
1377:
Dengensha board failure\n
No contact with Dengensha PCI board.\n
Possible cause: Dengensha board not\n
present.\n
\t\n
Check the Dengensha PCI board.
1378:
Dengensha board failure\n
Failed to access the\n
Dengensha PCI board.\n
\t\n
Check the Dengensha PCI board.
1384:
CAN2 power down\n
No external power connected to CAN2\n
\t\n
Check the external power to CAN2
