KISNET is the point-to-point communications network used by fast feedback to communicate between micros. A bad KISNET link will be signaled by messages like the following from a running feedback loop.
ConTroLler
to ACTuator micro) in which feedback loop has a problem. Your next
step is to use the stand-alone program KISTEST to verify that the link
is truly broken.
Before running KISTEST you must use the SCP to turn off the feedback loop(s) involved. A running loop will interfere with the test and the test will also interfere with the loop's operation.
To run KISTEST just use a terminal logged in to MCC and type KISTEST. You will be prompted as shown in the example immediately below for six things which specify the link to be tested. The proper responses for the links we have in our system are shown in the table below the example. You can get a current version of a similar table by typing HELP in response to the first prompt from KISTEST.
The following example shows a test of a working link from the controller to the actuator micro for the LI18 loop. The user's responses are in bold type.
MCC> kistest
Name of micro on this end of link: li18
Unit/Station id [0 or 8]: 0
Port/Socket number [0..6]: 1
Name of micro on the other end of link: li17
Unit/Station id [0 or 8]: 8
Port/Socket number [0..6]: 0
Do you want extended loop test [y/n]: n
Please TURN OFF FAST FEEDBACK LOOPS on these micros NOW!!
Warning: LI18 KISnet loopback test takes a minute!
LI18 Not allowed to overwrite existing MCOM map entry This is OK
Test passed; 5000 total packets; elapsed time is 00:00:22.23
Warning: LI17 KISnet loopback test takes a minute!
Test passed; 5000 total packets; elapsed time is 00:00:21.10
Read data = 'SLAVE->MASTER-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'SLAVE->MASTER-OK'
Read data = 'MASTER->SLAVE-OK'
Read data = 'SLAVE->MASTER-OK'
Cleaning up micro LI18.
Cleaning up micro LI17.
Exiting mcom diagnostics.
Please COLDSTART FAST FEEDBACK LOOPS on these micros
and restore them to their original state NOW!!
14-APR-1992 15:52:17 The following table shows the proper responses for each type of communications link for each feedback loop. Note that not all feedback loops use KISNET links, for example LI00FBCK has all its hardware in one micro and hence has no KISNET links.
Measurement to Controller KISNET links
Loop From Unit Port To Unit Port
Name Micro Number Micro Number
-------------------------------------------------------------------
NLTRSLTR DR01 0 0 LI01 8 2
NLTRSLTR DR11 0 0 LI01 8 1
NRTLFBCK LI02 0 0 DR13 8 0
SRTLFBCK LI02 0 1 DR03 8 0
LI06FBCK LI07 0 0 LI06 8 0
LI11FBCK LI12 0 0 LI11 8 0
LI18FBCK LI19 0 1 LI18 8 0
EP01SCAV LI19 0 0 EP01 8 0
LI23FBCK LI24 0 0 LI23 8 0
LI27FBCK LI28 0 0 LI27 8 0
Controller to Actuator KISNET links
Loop From Unit Port To Unit Port
Name Micro Number Micro Number
-------------------------------------------------------------------
NLTRSLTR LI01 0 0 LI00 8 0
LI06FBCK LI06 0 1 LI05 8 0
LI11FBCK LI11 0 1 LI10 8 0
LI18FBCK LI18 0 1 LI17 8 0
LI23FBCK LI23 0 1 LI22 8 0
LI27FBCK LI27 0 0 LI26 8 0
CASCADE KISNET links from named loop to next one downstream
Loop From Unit Port To Unit Port
Name Micro Number Micro Number
-------------------------------------------------------------------
SLTRFBCK DR03 0 1 LI03 8 1
NLTRFBCK DR13 0 1 LI03 8 2
LI03LOOP LI03 0 0 LI04 8 1
LI04LOOP LI04 0 0 LI06 8 3
LI06FBCK LI06 0 2 LI11 8 3
LI11FBCK LI11 0 2 LI18 8 3
LI18FBCK LI18 0 2 LI23 8 3
LI23FBCK LI23 0 2 LI27 8 3
LI27FBCK LI27 0 2 FF11 8 0
LI27FBCK LI27 0 2 FF01 9 0
Typically if the loopback test on a micro fails then that KISNET card is bad and needs to be replaced. If both loopback tests pass and the later communications tests all fail then there is probably a problem with the wire between the two micros.
At this point you should call in the micro hardware expert to repair the problem. The following information is for that expert or for an operator if for some reason the expert is not available.
Note the PORT NUMBER that you had to give KISTEST for the KISNET card which you have determined is bad.
Take a couple of spare KISNET cards (We have plenty of spares, but if you don't know where they are, there are always some installed in the LI31 development micro.) and drive out to the micro which has a bad card. Turn off the power to the multibus crate and open up the front door.
Port number 0 is on the main CPU board. Port numbers 1-6 are on a separate board made by Central Data. Ports 1-3 are on the part of the board closest to the front of the multibus crate with 1 on the bottom and 3 on the top. Ports 4-6 are on the back of the board with 4 on the bottom and 6 on the top.
Remove the appropriate multibus board and exchange the bad KISNET card with your spare. Be sure to set the dip-switches as they were on the original card. The proper setting is 0 or 8 as indicated by the UNIT you had to give KISTEST (Set switch 4 in socket 1, open=8, closed=0).
Re-insert the multibus card, close the door, apply power, IPL the micro, and run KISTEST again.
When you are done running KISTEST, coldstart the feedback loop(s) that used that link and turn them back on.