12meter manual debugging pages

• I've extracted some pages used for debugging.. (see users guide for complete manual)
  
• unidrive_menu10.pdf:  Menu 10 has the registers for the status and trips
• page 201 of the SP userguide
• unidrive diagnostices chapter (.pdf)
• starts page 275 of SP userguide.
• has the trip codes.

Controller addresses and pages

    We have 3 motor controllers.
 Each controller has up to 3 slots for add on cards mounted from the front side below the menu buttons:

• top: slot 1 (menu page 15)
• middle: slot 2 (menu page 16)
• bottom: slot3 (menu page 17)
• The add on card pages 15,16,17 can also be references as page 81.
• user guide pages for the various module types
• sm-i/o plus  users guide page 229
• sm-encoder plus:users guide page 225
  

  looking at the huffman box through the open door:(see electrical schematic page 4)

• U1:left          - elevation controller (elec schematic page 5)
• slot 1 : universal encoder plus  (15.01)=102 sm universal encoder +)
  
• slot 2 : sm applications plus      (16.01)=304  (this must be a new number not in the manual)
  
• slot 3 : sm I/O plus                    (17.01)=201 sm i/o plus)
  
• U3:middle     - azimuth master  (schematic page 6)
  
• slot 1 : universal encoder plus  (15.01)=102 sm universal encoder
  
• slot 2 : sm applications plus      (16.01)=304
  
• slot 3 : sm I/O plus                     (17.01)=201
  
• U4:right most-   azimuth slave (schematic page 7)
• slot 1 : sm applications plus       (15.01) = 304
  
• slot 2 : sm applications plus       (16.01) = 304
  
• slot 3 : sm ethernet                    (17.01) - 410 ethernet
  

220511: slave controller tripping with sl1.err

220526 update:

•     tripped at 00:12:03.979   ast.. seems to trip around midnight (clock related?)
• 15.50 = 50 math error
• 15.48  =1357    line number in program with error.

•  tripped at 00:12:09 ast
• 15:50 = 50
• 15:48  - 1357

220531: 

• tripped: 00:12:16 ast
• didn't get a chance to read the menu's before reset.

220601:

• tripped 00:12:19
  

    This has happened a few times now.

• sl1.err means an error in the slot 1 device of the controller.
• slot1 of azimuth slave is an  sm applications plus module
• Since it is in slot 1, menu 15 should hold the info.
• menu 15.50 should have the detailed  error code

When the trip occurred: What i tried to do:

• remote control can no longer close the contactor
• No error appears in the 12meter status window (other than contactor open)
• the system time (monp12m) no longer updates. It freezes at  the trip time
• going to the 12meter and pushing the reset button undoes the trip
• I tried running /share/megs/phil/svn/aosoft/p12m/Test/p12m_nodedata.sc
  
• this will download all of the registers from each controller (using dump_node.c)
• for some reason it hung up during the error. After resetting i was able to run it.
• I did run  p12m_diagdata.sc  which uses some of mark's code to read some  of the diagnostics:
• link to output
• see operation and maintenance manual part 1 page 127.
• the az slave values were:
• 74.41_UpdateAzimuthSlaveDiagnostic       23824 val:        0 0x00000000
  74.42_AzimuthSlaveTrip0                  23825 val:        6 0x00000006
  74.43_AzimuthSlaveTrip1                  23826 val:        6 0x00000006
  74.44_AzimuthSlaveTrip2                  23827 val:        6 0x00000006
  74.45_AzimuthSlaveDriveOverload          23828 val:        0 0x00000000
  74.46_AzimuthSlaveDriveOvertemp          23829 val:        0 0x00000000
  74.47_AzimuthSlaveDriveSummary           23830 val:    12335 0x0000302f
  74.49_AzimuthSlaveAppsErrorCode          23832 val:        0 0x00000000
  74.50_AzimuthSlaveAppsTaskInError        23833 val:        0 0x00000000
  74.51_AzimuthSlaveDPLProgStatus          23834 val:        2 0x00000002
  74.52_AzimuthSlaveDPLLineNumberInError   23835 val:        0 0x00000000
  74.53_AzimuthSlaveCTNetDiagnostics       23836 val:     1000 0x000003e8
• 74.42,43,44 are the last 3 tripcodes.. (10.20,10.21,10.220 6 is under voltage.
• 74.50 is the AppsErrorCode coming from15.50 .. and had 0=noerror
  

What i think is happening.

• The failure occurred in the az slave drive. This is node 4 (el-1,azM-3,azSl=4)
• page 10 of the controller has the status and trips
• 10.20 to 10.29 are the trip codes for the last 10 trips (10.20 is the most recent)
• After resetting the controller I was able to read all of the pages of each drive.
• link to azSlave menu dump after reset done
  
• 10.20 to 10.29 now look like
•   4    10.20          202
    4    10.21          212
    4    10.22          212
    4    10.23            6
    4    10.24            6
    4    10.25            6
    4    10.26            6
    4    10.27          212
    4    10.28            6
    4    10.29            6
• So the last 3 trips are now:
• 202,212, and 212.
• the 6,6,6 seen in the 74.42-44 look like previous trips.
• When i dumped the diag data it looks like the new trips had not been updated yet.
• Page 285 of the users manual shows the error codes for automation (applications) module category .. )(supposedly our applications +  module)
• 10.20 of 202 or 212   could have error codes of 32-89 .. in 15.50 
  

It looks like the problem is the trip codes 10.20 are archived in 10.20 -> 10.29  but the detailed code 15.50 is only the current value

If this happens again:

•  Go to the 12meter az slave controller
• if slN.err
• N=1  read 15.50
• N=2  read 16.50
• N=3  read 17.50
• push M button to switch from status to parameter  mode (or try down on the joy stick)
• The flashing cursor should be on the top line (parameter address...) if not use up arrow
• move the cursor to the left
• push up arrow til  nn.mm where nn is 15
• push arrow to the right to move to mm
• push up,down arrow till you have 50..
• record the value in the bottom line
• hit m button until you are back in status mode.

12meter page
home_phil