Professional Documents
Culture Documents
Revision: 5.1
Date: 11/13/2006
Number of pages: 37
File Name: Field_Trouble.doc
I: TABLE OF CONTENTS
TABLE OF FIGURES
Figure 2-1: Start-Up Screen .....................................................................................................................4
Figure 5-2: Screen Capture of Engine Load Test...................................................................................37
1 INTRODUCTION
This document will provide information required for field maintenance personnel to retrieve data from
the Sibas traction control unit (computer) in order to make informed decisions about what action to
take in the event of an outage. The procedures in this document are to be performed before contacting
any Siemens Energy & Automation personnel. This information is required in order to make any
decision regarding the status of the drive system.
REQUIREMENTS:
2 START-UP
To connect to the Sibas computer a 9-pin serial male to female cable is required. One end of the cable
must be hooked up to the serial port on the laptop computer, and the other end of the cable must be
hooked up to the 9-pin port on the dashboard of the truck. This cable can be purchased at any Radio
Shack or computer hardware store. After this connection is made, the key switch can be turned to the
“ON” or “START” position. After the truck is powered up, the monitor program can be started. This
is done by double clicking on the “Sibas Monitor” icon on the desktop of your computer. This will
result in a screen similar to the following if completed successfully. The monitor program is simply a
way to communicate with the SiBAS. The number following “Version” is the software version on that
particular truck and must be recorded on the outage data sheet at the end of this document. The
numbers following “Monitor 32” and “Operating System” are the Operating system’s software
versions.
Occasionally, there are problems connecting with the TCU, but these only occur when something is not
done correctly and are easy to fix.
If the “Check Serial Connection” message appears when you try to open the Monitor program, then
one of 2 things can be wrong. Either there is already a Monitor program window open or you are
trying to open a second one, or the connection is loose on the dashboard or the port on the laptop.
If this message appears, then either the Sibas computer is not on (key switch is not in the 24V
position), or your serial cable is not hooked up correctly.
The purpose of stringing a record file is so that all the information that scrolls across your screen can
be saved on your computer’s hard drive. This is helpful if you need to go back to an office and study
the files or if Siemen’s personnel need the files emailed to them. If this is not done correctly, then
once the information scrolls above the top of the screen, it is lost and cannot be seen once you
disconnect from the port on the dash. The information is not deleted; it just cannot be seen unless you
are on the truck. The procedure to string a record file is as follows:
Now you have started a record file and everything that scrolls across your screen will be saved in
010401.txt in your hard drive. This file can now be found in the SIBAS32 folder under the OS_MONI
subfolder.
Once you are finished downloading everything, simply do as follows to stop the file:
• Click on SET
• Click on RECORD
• Click on STOP in the pop up menu
• Press ENTER
3.2 What do I need to look at when there is a problem with the truck?
There are quite a few menus in the Monitor program, and most of them you will never have to worry
about. The following is a quick description of the procedure that a Siemen’s engineer goes through
when they are troubleshooting a problem with the drive system.
Once the monitor program is up and running, the first step that is required to troubleshoot a problem is
to determine the internal state of the drive system. Following these simple steps can do this:
• Click on the USER menu
• Click on STAT_INTERN
• Press ENTER
If the AC drive system is ready to run and there are no problems, the following screen will appear. If
this screen has information other than that shown below, specifically under drive status, this
information must be recorded and relayed on to the appropriate service personnel. This is the first step
in determining the source of the problem.
State intern
Vehicle number:
Powering system ... : "DIESEL ONLY"
TCU operation mode ... : NORMAL
DC-link contactor K104 : CLOSED
Field regulator status : ENABLED
Status gate unit power supply : ENABLED
Status auxiliary inverter : ENABLED
Drive status ... : IDLE
Inverter A ready for operation
Inverter B ready for operation
Figure 3-2: State Intern Screen Capture
To view the faults (also called Statistics) on the drive system, both active and non-active do the
following:
• Click on EVENTS
• Click on STATISTICS
• Press ENTER
You should now see a list of faults on the drive system like the one seen below.
Statistics
Diagnosis memory statistics:
The History of the system shows more detailed information about the last 20 faults that have occurred
on the drive system. To view the History use the following steps:
• Click on EVENT
• Click on HISTORY
• Press ENTER
After doing this, you should see a list like the one presented below.
History
! Diagnosis memory history!
Display: last event == older event
For the 4th fault, # 720, you can see that the fault appeared on the system on Dec. 12, 2000 (12.12.00)
at 17:38:26, which is 5:38 p.m. The next set of numbers is when the fault went away, Dec. 12, 2000
(12.12.00) at 17:38:33. This means that the fault lasted for 7 seconds. This particular fault is listed
below.
DC: 720: UWSB: GTO SWITCHING FAILURE A201-1
Time event occurred/disapp. 12.12.00 17:38:26 / 12.12.00 17:38:33
If the information that was just gathered, Statistics and History, is not enough for you to find and fix
the fault, then you probably need more information about the fault. You can look at the state of the
drive system at the exact moment the fault happened to see what was going on with the truck at that
time. To do this, do the following:
• Click on EVENTS
• Click on DAL:DC,ALL L
• Press ENTER
• Type in the fault code that you would like to look at, which would be 720
• Press ENTER
You should now see the following scroll across your screen. The monitor program will scroll too fast
for you to read it during this step, which is why we strung a record file at the beginning. If you did not
string a record file at the beginning, you can pause the screen from scrolling by hitting the CTRL key
and ‘S’ at the same time. To continue scrolling, hit CTRL ‘S’ again.
DAL:DC,All L
Select diagnosis code: 720
AC HAUL TRUCK
=============
[Headline]
Number of events... 1
[Number of events of this code occurred since last memory deletion]
Environment group 1:
Three phase motor B current transducer, 2400A to 2500A range, -2500A to –2400A, CPU
send out ref. Under this range, then compare hardware A/D reading with comparator
reading. . The input current should be zero, this can check out if the transducer output is
zero when there is no current.
Bit 15: fault of hardware comparator DC-link voltage GW5 UWSB]
DC-LINK voltage monitoring, 3520V to 36800VDC range, -3680V to –3520V, CPU sends
out a ref. Under this range, then compare hardware A/D reading with comparator reading.
Note: fault code 397, 697, 797 will be come out if one of the above bits is 1. First thing, it should check the
transducer.
Note: fault code 1330 will be come out if one of the above bits is 1. First thing, it should check the reason
why testing is stopped.
Note: fault code 51 will be come out if one of the above bits is 1.
Note: fault code 101 will be come out if one of the above bits is 1.
AC Haul Truck SiBAS 32 Customer Monitor User Guide Revision: 5.1
COPYRIGHT © Siemens Energy and Automation, Inc. All Rights Reserved. Page13 of 37
s SPECIAL DRIVES / SE&A
Bit 0: 0
Bit 1: Impulse release / BIMPFSP
Bit 2: Impulse release Test / BIMFTSP
Bit 3: Engine teeth number
Bit 4: Peak-current-operator-action
Bit 5: Voltage stability required
Bit 6: SPH-Controller release / BFSPHSP
Bit 7: Desired-direction forward
Bit 8: 0
Bit 9: du/dt acknowledgement
Bit 10: 0/1, DSP number, 0=DSPA, 1=DSPB
Bit 11: 0, Trolley application?
Bit 12: Motor configuration, 1=Small motor, 0=big motor
Bit 13: Chopper duty cycle control by ZR
Bit 14: 0
Bit 15: Vehicle status in Propel
Note: Either fault code 871 or 872 will be come out if one of the above bits is 1.
Please note: These bits cab be used to verify the setting for APRS.
Please note: These bits can be used to verify the setting for SHTS.
Environment group 2:
environment group 3:
Bit 0: reserved
Bit 1: reserved
Bit 2: reserved
Bit 3: total lock from power supply(G163)
Bit 4: FPGA block fault (G163)
Bit 5: +5V Power supply undervoltage fault
Bit 6: -15V Power supply undervoltage fault
Bit 7: +15V Power supply undervoltage fault
Bit 8: reserved
Bit 9: reserved
Bit 10: reserved
Bit 11: hardware fault from power supply (G163)
Bit 12: FPGA block fault (G163)
Bit 13: +24V Power supply undervoltage fault
Bit 14: -24V Power supply undervoltage fault
Bit 15: Power supply input undervoltage fault
Note: Either fault code from 30 to 37 should be come out if one of the above bits is 1.
Note: This is from HDWI package A/D error bit, which is from hardware on I/0 card. This information similar
to TCU self-test byte bit 0.
environment group 4:
Note: fault code 642 to 645, 742 to 745 will come out if either bit is 1.
Note: fault 620 to 626, 720 to 726 will come out if either bit is 1.
Note: switching fault 662 and 762 will come out if either bit of last 4 word is 1.
Bit 5: Free
Bit 6: Free
Bit 7: Free
Bit 8: SSE Phase 1
Bit 9: SSE Phase 2
Bit 10: SSE Phase 3
Bit 11: SSE Phase 4
Bit 12: Free
Bit 13: Free
Bit 14: Free
Bit 15: Free
Note: switching fault 669 and 769 will come out if either bit of last 3 word is 1.
environment group 5:
environment DSP A
fault status ............ : 0000 H |0000|0000|0000|0000|
[fault status word from DSP A]
Bit 0: Time Overflow in T1, fault code 57
Bit 1: Initialization error, fault code 56
Bit 2: Overcurrent, fault code 70
Bit 3: Parameter fault braking chopper frequency, fault 71
Bit 4: Voltage transducer U13 not OK, fault code 72
Bit 5: Voltage transducer U23 not OK, fault code 73
Bit 6: reserved
Bit 7: sum of three phase current not zero, fault code 76
Bit 8: communication with DSPB error, fault code 74,
Bit 9: reserved
Bit 10: Failure V/F card, L055, fault code 77
Bit 11: reserved
Bit 12: Unbalance current protection, >215A, fault code 85
Bit 13: Time Overflow in T4, fault code 60
Bit 14: Time Overflow in T3, fault code 59
Bit 15: Time Overflow in T2, fault code 58
It counts the address where the program is interrupted when there is Time slice overflow T1.
This can help to analyze the fault code 57
environment DSP B
environment group 7:
voltage/current/speed values:
trolley voltage/current : 0.0 V / 0.0 A
[trolley voltage (transducer U301) / trolley current (transducer U108)]
$UN / $IN
$NSD / $NIDSBG
$UDI_IO / $IDIGHW
$ISEXC
$UGG / $UDIGHW2
$IBTGZB / $IBTGZA
$FBLWSPT
$OSOLLSB / $OSOLLSA
$MS1B / $MS1A
$XMRFSSB / $XMRFSSA,
$VIB
$IL1PWRB / $IL1PWRA
$IL2PWRB / $IL2PWRA
$IL3PWRB / $IL3PWRA
environment group 8:
From the previously discussed menus, the problem with the drive system should be able to be solved.
Once the fault is found and solved, the fault history needs to be cleared. The statistics and fault history
can be very easily cleared in order to eliminate an overwhelming amount of data. This should also be
done periodically in order to keep the fault archive relatively clean so in the event of an outage the
cause of the problem can be easily found. The procedures below will allow you to clear all faults from
the archive except for faults that are still active.
• Click on EVENTS menu
• Click on CLEAR_NORM
• Press ENTER
Note: Before starting a load test verify that the system status is okay, Select User – State Intern. With
the engine running and start up sequence complete everything should be enabled and K104 closed. If
not, the reset button should be pressed and the status should be viewed again. Once the State intern
shows that everything is enabled and K104 is closed the load test can be started.
At this point, you can enter any of the following letters, “d”, “e”, to look at the diesel engine values or
electrical values, respectively. All entries must be followed by pressing enter. All scrolling of the
screen can be stopped by pressing CTRL 'C'. After pressing CTRL C you must select User _Engine
test and get the sub menu to do the other options. To increase the power select “p” and enter in a
increased value.
The following procedures must be completed to stop the test and take the computer out of self-load test
mode.
• Type “p”
• Press ENTER
• Type “500”
• Press ENTER **** allow the engine to ramp down a little if power was >1500Hp prior to this
• Type “f” *** stops the engine test
• Press ENTER
• Type “t” *** exits the self load test mode, allows use of the throttle pedal and movement
• Press ENTER
• Type “q” and press ENTER to exit the self load test menu
In this mode, the software will automatically regulate the chopper module duty-cycle to keep loading
the engine as much as possible while keeping engine speed at 1810rpm.
The most important information that can be gained by running this test is whether or not the diesel is
turning at full RPM when full power is needed. If the diesel is turning at less than 1810 RPM while
the load test is at 2550 hp, there is quite possibly a problem with the diesel engine. This is the most
common use for the load test when troubleshooting and can usually be used to eliminate one of the two
systems as the source of the problem at hand.