Simovert Masterdrive Faults
Remember: If a fault message is not reset before the supply voltage is switched off, then the fault message will be present again when the electronic supply is switched on again. The unit cannot be operated without resetting the fault message.
- F001 Main contactor checkback - cause: The monitoring time of the main contactor checkback (P600) has expired - remedy/suggestion: Check main contactor checkback, Clear main contactor checkback (P591.B = 0), or Increase monitoring time (P600)
- F002 Precharging fault - cause: The monitoring time of pre-charging has expired, i.e. the DC link voltage has not reached the setpoint within 3 secs - remedy/suggestion: Check voltage connection (AC or DC), Unit-dependent: Check fuses, or Compare value in P070 and unit MLFB
- F006 DC link overvoltage - cause: Due to excessive DC link voltage, shutdown has occurred. The rated value of the shutdown DC link overvoltage threshold is 819 V. Due to component tolerances shutdown can take place in the range from 803 V to 835 V. - remedy/suggestion: Check the line voltage (AC-AC) or the input direct voltage (DC-AC). Compare value withP071 (Line Volts)
- F008 DC link undervoltage - cause: The lower limit value of 76% of the DC link voltage has been fallen short of. In the fault value the DC link voltage upon occurrence of the fault is indicated (normalization 0x7FFF corresponds to 1000V) - remedy/suggestion: Check the line voltage (AC-AC) or the input direct voltage (DC-AC). Compare value with P071 (Line Volts), Check input rectifier (AC-AC), or Check DC link
- F011 Overcurrent not Compact PLUS - cause: Overcurrent shutdown has occurred. The shutdown threshold has been exceeded. The phase in which an overcurrent has occurred is indicated in a bit-coded manner in the fault value (see P949). Phase U --> Bit 0 = 1--> fault value = 1 Phase V --> Bit 1 = 1--> fault value = 2 Phase W--> Bit 2 = 1--> fault value = 4 If an overcurrent occurs simultaneously in several phases, the total of the fault values of the phases concerned is the resulting fault value- remedy/suggestion: Check the converter output for short-circuit or earth fault, Check the load for an overload condition, Check whether motor and converter are correctly matched, or Check whether the dynamic requirements are too high
- F015 Motor Blocked - cause: Motor is blocked/overloaded (current control), or has stalled (v/f characteristic): Static load is too high, The fault is not generated until after the time entered in P805, Binector B0156 is set, in status word 2 r553 Bit 28, Whether the drive is blocked or not can be detected at P792 (Perm Deviation) and P794. P806 enables detection to be limited to "atstandstill" (P806 = 1, only for current control) or to be completely de-activated (P806 = 2). In the case of current control, the precondition for this fault is that the torque limits (B0234) have been reached. In the case of slave drive, detection is de-activated. In the case of v/f control, the I(max) controller must be active - remedy/suggestion: Reduce the load, Release the brake, Increase current limits, Increase P805 Blocking Time, Increase the response threshold for the permissible deviation P792, Increase torque limits or torque setpoint, Check connection of motor phases including correct phase assignment/sequence for v/f characteristic only: Reduce rate of acceleration or Check characteristic setting
- F017 SAFE STOP (Compact PLUS only) - cause: SAFE STOP operating or failure of the 24 V power supply during operation (only for Compact PLUS units) - remedy/suggestion: Jumper applied for SAFE STOP? SAFE STOP checkback connected? On Compact PLUS units: check 24 V supply
- F020 Excess temperature of motor - cause: The motor temperature limit value has been exceeded. r949 = 1 Motor temperature limit value exceeded, r949 = 2 Short-circuit in the motor temperature sensor cable or sensor defective, r949 = 4 Wire break of motor temperature sensor cable or sensor defective - remedy/suggestion: Temperature threshold adjustable in P381!, P131 = 0 -> fault de-activated, Check the motor (load, ventilation etc.), The current motor temperature can be read in r009 (Motor Temperat.), or Check the sensor for cable break, short-circuit
- F021 Motor I2t - cause: Parameterized limit value of the I2t monitoring for the motor (P384.002) has been exceeded - remedy/suggestion: Check: Thermal time constant of motor P383 Mot ThermT-Const or motor I2t load limitP384.002. The I2t monitoring for the motor is automatically activated if P383 >=100s(=factory setting) and P381 > 220°C is set.Monitoring can be switched off by setting a value <100s in P383.
- F023 Excess temperature of inverter - cause: The limit value of the inverter temperature has been exceeded - remedy/suggestion: Measure the air intake and ambient temperature (Observe minimum and maximum ambient temperature from 0°C to 45°C!), Observe the derating curves at theta > 45 °C (Compact PLUS) or 40 degrees C, Check whether the fan is running, Check that the air entry and discharge openings are not restricted, In the case of units >= 22 kW acknowledgement is only possible after 1 minute
- F025 UCE upper switch/UCE Phase L1 - cause: For Compact PLUS units: UCE upper switch, For chassis type units: UCE Phase L1- remedy/suggestion: Check the converter outputs for earth fault, Check the switch for "SAFE STOP" on Compact units
- F026 UCE lower switch/UCE Phase L2 - cause: For Compact PLUS units: UCE lower switch, For Compact and chassis type units: UCE Phase L2 - remedy/suggestion: Check the converter outputs for earth fault, Check the switch for "SAFE STOP" on Compact units
- F027 Pulse resistor fault /UCE Phase L3 - cause: For Compact PLUS AC/AC units: Pulse resistance fault, For chassis type units: UCE Phase L3 - remedy/suggestion: Check the converter outputs for earth fault, Check the switch for "SAFE STOP" on Compact DC/DC units and chassis units with the option "SAFE STOP"
- F029 Meas. value sensing (Compact PLUS only) - cause: A fault has occurred in the measured value sensing system: (r949 = 1) Offset adjustment in phase L1 not possible, (r949 = 2) Offset adjustment in phase L3 not possible, (r949 = 3) Offset adjustment in phases L1and L3 not possible, (r949=65) Autom. Adjustment of the analog inputs is not possible - remedy/suggestion: Fault in measured value sensing, Fault in power section (valve cannot block), Fault on CU
- F035 External fault 1 - cause: Parameterizable external fault input 1 has been activated - remedy/suggestion: Check whether there is an external fault, Check whether the cable to the corresponding digital output is interrupted, P575 (Src No ExtFault1)
- F036 External fault 2 - cause: Parameterizable external fault input 2 has been activated - remedy/suggestion: Check whether there is an external fault, Check whether the cable to the corresponding digital output is interrupted, P576 (Src No ExtFault2)
- F038 Voltage OFF during parameter storage- cause: A voltage failure has occurred during a parameter task - remedy/suggestion: Re-enter the parameter. The number of the parameter concerned is indicated in fault valuer949
- F040 Internal fault of sequence control - cause: Incorrect operating status - remedy/suggestion: Replace the control board (CUMC) or the unit(Compact PUS).
- F041 EEPROM fault - cause: A fault has occurred during the storage of values in the EEPROM - remedy/suggestion: Replace the control board (CUMC) or the unit(Compact PLUS)
- F042 Time slot overflow - cause: The available calculating time of the time slot has been exceeded., At least 10 failures of time slots T2, T3, T4 orT5 (see also parameter r829.2 to r829.5) - remedy/suggestion: Reduce pulse frequency, Calculate individual blocks in a slower sampling time, The technology functions Synchronization (U953.33) and Positioning (U953.32) must not be enabled at the same time
- F043 DSP link - cause: The link to the internal signal processor is interrupted - remedy/suggestion: Reduce pulse frequency (perhaps caused by calculating time overflow), If fault re-occurs, replace the board/unit
The pulse frequency P340 should not be adjusted to values larger than 7.5 kHz (for60MHz - DSP) or 6 kHz (for 40MHz - DSP). If higher values are set, indices 12 to 19 have to be checked on visualization parameter r829.The indicated free calculating time of the DSP time slots always have to be greater than zero. If the calculating time is exceeded, this is also displayed by fault F043 (DSP coupling). Remedy: Reduce pulse frequency (P340)
- F044 BICO manager fault - cause: A fault has occurred in the softwiring of binectors and connectors - remedy/suggestion: Fault value r949:>1000: Fault during connector softwiring>2000: Fault during binector softwiring, Voltage OFF and ON, Factory setting and new parameterization, Exchange the board1028: Link memory is full. The link area between the two processors is full. No further connectors can be transferred. Reduction of the linked connections between the two processors. Interface between the two processors is position control/setpoint conditioning i.e.softwires from and to the setpoint conditioning, position controller, speed controller, torque interface and current controller which are not necessary should be dissolved to reduce the link (value 0)
- F045 HW fault on optional boards - cause: A hardware fault has occurred during access to an optional board - remedy/suggestion: Replace CU board (Compact, chassis units), Replace the unit (Compact PLUS), Check the connection between the subrack and the optional boards, Replace optional boards
- F046 Parameter coupling fault - cause: A fault has occurred during the transfer of parameters to the DSP. - remedy/suggestion: If fault re-occurs, replace the board/unit
Note: This
Simovert fault list continues in subsequent posts...
This is the Simovert encoder fault, it's one of the more common Simovert faults:
- F051 Encoder fault - cause: Signal amplitude of resolver or encoder is below the tolerance threshold, Power supply faults in the case of encoders and multiturn encoders, In the case of multiturn encoders (SSI/Endat), connection fault of the serial protocol - remedy/suggestion: Fault value r949:10th and 1st position: 9 = Resolver signal missing (sin/cos track)
20 = Position error: Alarm A18 was generatedduring the change to the "operation" state.(For remedial action see 29)
21 = A/B track undervoltage:Root(A^2+B^2)<0.01V (For remedial actionsee 29)
22 = A/B track overvoltage:Root(A^2+B^2)>1.45V (For remedial actionsee 29)
25 = Encoder initial position not recognized(C/D track missing), Check encoder cable (faulty / interrupted)? Correct encoder type parameterized? Is the correct cable used for encoder ormultiturn encoder? Encoders and multiturn encoders need different cables!, Encoder faulty?
26 = Encoder zero pulse outside the permitted range
27 = No encoder zero pulse has occurred
28 = Encoder/multiturnVoltage supply Encoder fault, Short-circuit in encoder connection? Encoder faulty? Encoder incorrectly connected up?! Power off/on or in drive settings and back to new initialization of the starting position!
29 = A/B track undervoltage: In the zero passage of one track the amount of the other track was less than 0.025 V, Check encoder cable (faulty/torn off)? Is shield of encoder cable connected ? Encoder faulty? Replace SBR/SBM Replace unit or basic board, Is the correct cable being used in each case for the encoder/multiturn encoder? Encoders and multiturn encoders require different encoder cables! Power off/on or in drive settings and back to new initialization of the starting position!
Multiturn (SSI/EnDat):
30: Protocol fault CRC/Parity Check (EnDat)
31: Timeout Protocol (EnDat)
32: No-load level error, data line (SSI/EnDat)
33: Initialization of timeout, Check parameterization (P149), Check encoder cable (faulty / torn off? Encoder cable shield connected? Encoder faulty? Replace SBR/SBM, Replace unit or basic board
34: Address wrong (only EnDat)- Writing or reading of parameters not successful, check address and MRS code(P149)
35: The difference between the serial protocol and the pulse counter is greater than 0xFFFF(2^16). A possible fault may be a jump in the serial protocol. The fault can only be generated if an absolute encoder with incremental tracks (P149.01/.06 = X1XX) and multiturn portion is concerned. (EnDat)
40: Alarm, lighting, EnDat encoder
41: Alarm, signal amplitude, EnDat encoder
42: Alarm. position value, EnDat encoder
43: Alarm, overvoltage, EnDat encoder
44: Alarm, undervoltage, EnDat encoder
45: Alarm, overcurrent, EnDat encoder
46: Alarm, battery failure, EnDat encoder
49: Alarm, check sum error, EnDat encoder
60: SSI protocol faulty (see P143)
100th position:0xx: Motor encoder faulty1xx: External encoder faulty
1000th position: (from V1.50)
1xxx: Frequency exceeded, EnDat encoder
2xxx: Temperature, EnDat encoder
3xxx: Control reserve, light, EnDat encoder
4xxx: Battery charge, EnDat encoder5xxx: Home point not reached
Additional Simovert alarms follow in additional posts...
Continuation of the Simovert Masterdrive Errors...
- F054 Encoder board initialization fault - cause: A fault has occurred during initialization of the encoder board - remedy/suggestion: Fault value r949:
1: Board code is incorrect
2: TSY not compatible
3: SBP not compatible
4: SBR not compatible
5: SBM not compatible (from V2.0 only theSBM2 board is supported; see also r826 function diagram 517)
6: SBM initialization timeout
7: Board double
20: TSY board double
21: SBR board double
23: SBM board three-fold
24: SBP board three-fold
30: SBR board slot incorrect
31: SBM board slot incorrect
32: SBP board slot incorrect
40: SBR board not present
41: SBM board not present
42: SBP board not present
50: Three encoder boards or two encoder boards, none of them onSlot C
60: internal fault
- F056 SIMOLINK telegram failure - cause: Communication on the SIMOLINK ring is disturbed. - remedy/suggestion: Check the fiber-optic cable ring, Check whether an SLB in the ring is without voltage, Check whether an SLB in the ring is faulty, Check P741 (SLB TlgOFF)
- F058 Parameter fault Parameter task - cause: A fault has occurred during the processing of a parameter task - remedy/suggestion: No remedy for this
- F059 Parameter fault after factory setting/init - cause: A fault has occurred in the initialization phase during the calculation of a parameter - remedy/suggestion: The number of the inconsistent parameter isindicated in fault value r949. Correct this parameter (ALL indices) and switch voltage offand on again. Several parameters may be affected, i.e. repeat process
- F060 MLFB is missing during initial loading - cause: Is set if parameter P070 is at zero when INITIAL LOADING is exited - remedy/suggestion: Enter correct MLFB after acknowledging thefault (power section, initial loading
- F061 Incorrect parameterization - cause: A parameter which has been entered during drive setting is in the non-permissible range - remedy/suggestion: The number of the inconsistent parameter is indicated in fault value r949 (e.g. motor encoder = pulse encoder in the case of brushless DC motors) -> correct this parameter
- F063 PIN is missing- cause: The synchronization or positioning technology functions have been activated without an authorization being present (PIN) - remedy/suggestion: Deactivate synchronization or positioning, Enter the PIN (U2977)
If technology functions are inserted in the timeslots without enabling the technology function through the PIN, the message F063 is generated. This fault can only be cleared by putting in the correct PIN at U977.01 and U977.02 and switching the power off and on again, or by disabling the technology functions (put U953.32 = 20 and U053.33 = 20)
- F065 SCom telegram failure - cause: No telegram has been received at an SCom interface (SCom/USS protocol) within the telegram failure time - remedy/suggestion: Fault value r949:
1 = Interface 1 (SCom1)
2 = Interface 2 (SCom2)
Check the connection of PMU -X300 or X103 /27,28 (Compact, chassis unit)
Check the connection of X103 or X100 / 35,36(Compact PLUS unit)
Check "SCom/SCB TlgOff" P704.01 (SCom1)or P704.02 (SCom2)
- F070 SCB initialization fault - cause: A fault has occurred during initialization of the SCB board - remedy/suggestion: Fault value r949:
1: Board code incorrect
2: SCB board not compatible
5: Error in configuration data(Check parameterization)
6: Initialization timeout
7: SCB board double
10: Channel error
- F072 EB initialization fault - cause: A fault has occurred during initialization of the EB board. - remedy/suggestion: Fault value r949:
2: 1st EB1 not compatible
3: 2nd EB1 not compatible
4: 1st EB2 not compatible
5: 2nd EB2 not compatible
21: Three EB1 boards
22: Three EB2 boards
110: Fault on 1st EB1
120: Fault on 2nd EB1
210: Fault on 1st EB2
220: Fault on 2nd EB2
- F073 AnInp1SL1not Compact PLUS - cause: 4 mA at analog input 1, slave 1 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 1) -X428: 4, 5
This is Masterdrive Fault 74 to 82
- F074 AnInp2 SL1 (not Compact PLUS) - cause: 4 mA at analog input 2, slave 1 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 1) -X428: 7, 8
- F075 AnInp3 SL1 (not Compact PLUS) - cause: 4 mA at analog input 3, slave 1 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 1) -X428: 10, 11
- F076 AnInp1 SL2 (not Compact PLUS) - cause: 4 mA at analog input 1, slave 2 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 2) -X428: 4, 5
- F077 AnInp2 SL2 (not Compact PLUS) - cause: 4 mA at analog input 2, slave 2 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 2) -X428: 7, 8
- F078 AnInp3 SL2 (not Compact PLUS) - cause: 4 mA at analog input 3, slave 2 fallen short of - remedy/suggestion: Check the connection of the signal source to the SCI1 (slave 2) -X428: 10, 11
- F079 SCB telegram failure (not Compact PLUS) - cause: No telegram has been received by the SCB(USS, peer-to-peer, SCI) within the telegram failure time - remedy/suggestion: Check the connections of the SCB1(2), Check P704.03"SCom/SCB Tlg OFF", Replace SCB1(2), or Replace CU (-A10)
- F080 TB/CB initialization fault- cause: Fault during initialization of the board at the DPR interface - remedy/suggestion: Fault value r949:
1: Board code incorrect
2: TB/CB board not compatible
3: CB board not compatible
5: Error in configuration data
6: Initialization timeout
7: TB/CB board double
10: Channel error
Check the T300/CB board for correct contacting, check the PSU power supply, check the CU / CB / T boards and check the CB initialization parameters: P918.01 CB Bus Address, and P711.01 to P721.01 CB parameters 1 to 11
- F081 OptBrdHeartbeat-Counter - cause: Heartbeat-counter of the optional board is no longer being processed - remedy/suggestion: Fault value r949:
0: TB/CB heartbeat-counter
1: SCB heartbeat-counter
2: Additional CB heartbeat-counter
Acknowledge the fault (whereby automatic reset is carried out), If the fault re-occurs, replace the board concerned (see fault value), Replace ADB, Check the connection between the subrack and the optional boards (LBA) and replace, if necessary
- F082 TB/CB telegram failure - cause: No new process data have been received by the TB or the CB within the telegram failure time - remedy/suggestion: Fault value r949:
1 = TB/CB
2 = additional CB
Check the connection to TB/CB, Check P722 (CB/TB TlgOFF), Replace CB or TB
- F085 Add. CB initialization fault - cause: A fault has occurred during initialization of the CB board. - remedy/suggestion: Fault value r949:
1: Board code incorrect
2: TB/CB board not compatible
3: CB board not compatible
5: Error in configuration data
6: Initialization timeout
7: TB/CB board double
10: Channel error
Check the T300 / CB board for correct contacting and check the CB initialization parameters: P918.02 CB Bus Address, P711.02 to P721.02 CB Parameters 1 to 11
- F087 SIMOLINK initialization fault - cause: A fault has occurred during initialization of the SLB board - remedy/suggestion: Replace CU (-A10), or replace the unit(Compact PLUS type), or Replace SLB
- F099 Friction characteristic record - cause: Recording of the friction characteristic was interrupted or not done at all - remedy/suggestion:
- F109 Mld R(L) - cause: The rotor resistance determined during measurement of the direct current deviates too greatly - remedy/suggestion: Repeat measurement, Enter data manually
- F111 MId DSP - cause: A fault has occurred during the Mot Id.
r949=1 The current does not build up when voltage pulses are applied
r949=2 (only for P115=4) The difference between speed setpoint and actual value is too large during measurement
r949=3 (only for P115=4) The magnetizing current determined is too high.
r949=121 The stator resistance P121 is not determined correctly
r949=124 The rotor time constant P124 is parameterized with the value 0 ms
r949=347 The valve voltage drop P347 is not determined correctly - remedy/suggestion: Repeat measurement
When r949=1: Check motor cables, When r949=2: Avoid mechanical stressing of the motor during the measurement; if the fault occurs directly after the start of the motor identification check the encoder and motor cables, or When r949=3: Check the motor rating plate data stored (ratio Vrated / Irated does not correspond with the measured inductance
- F112 Mid X(L) - cause: A fault has occurred during measurement of the motor inductances or leakages - remedy/suggestion: Repeat measurement
- F114 MId OFF - cause: The converter has automatically stopped the automatic measurement due to the time limit up to power-up having been exceeded or due to an OFF command during the measurement, and has reset the function selection in P115 - remedy/suggestion: Re-start with P115 function selection = 2 "Motor identification at standstill". The ON command must be given within 20 sec. after the alarm message A078 = standstill measurement has appeared.
Cancel the OFF command and re-start measurement.
And so it continues, these are the technology board faults, not a lot of info with these here because as you can see from this part of the list, you'll need to look at the tech board manual...
- F116 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F117 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F118 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F119 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F120 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F121 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F122 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F123 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F124 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F125 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F126 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F127 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F128 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F129 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F130 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F131 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F132 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F133 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F134 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F135 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F136 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F137 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F138 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F139 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F140 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F141 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F142 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F143 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F144 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F145 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F146 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
- F147 Technology board fault (not Compact PLUS) - cause: See TB documentation - remedy/suggestion: See Technology Board documentation
[/li][/list]