Additional Data Area 0; Pluto Stations 1 - ABB Pluto Series Integration Manual

7.1.2

Additional data area 0

Additional Data
When using additional data this example below show how additional data area 0 is mapped e.g.
the same as for the old Pluto node 0 (as above). The same mapping will for all other data areas 1 –
31 e.g. see corresponding Pluto node to get correct bit mapping!
Below is used "B0b0" to say Byte 0 and Bit 0. If data is global IO from Pluto e.g. IO-type is equal
111 for the additional area then the Pluto node mapping table is correct.
#
EIO_SIGNAL:
-Name "diAddData0_B0b0" -SignalType "DI" -Unit "ioPluto" -UnitMap "0"
-Name "diAddData0_B0b1" -SignalType "DI" -Unit "ioPluto" -UnitMap "1"
-Name "diAddData0_B0b2" -SignalType "DI" -Unit "ioPluto" -UnitMap "2"
-Name "diAddData0_B0b3" -SignalType "DI" -Unit "ioPluto" -UnitMap "3"
-Name "diAddData0_B0b4" -SignalType "DI" -Unit "ioPluto" -UnitMap "4"
-Name "diAddData0_B0b5" -SignalType "DI" -Unit "ioPluto" -UnitMap "5"
-Name "diAddData0_B0b6" -SignalType "DI" -Unit "ioPluto" -UnitMap "6"
-Name "diAddData0_B0b7" -SignalType "DI" -Unit "ioPluto" -UnitMap "7"
-Name "diAddData0_B1b0" -SignalType "DI" -Unit "ioPluto" -UnitMap "8"
-Name "diAddData0_B1b1" -SignalType "DI" -Unit "ioPluto" -UnitMap "9"
-Name "diAddData0_B1b2" -SignalType "DI" -Unit "ioPluto" -UnitMap "10"
-Name "diAddData0_B1b3" -SignalType "DI" -Unit "ioPluto" -UnitMap "11"
-Name "diAddData0_B1b4" -SignalType "DI" -Unit "ioPluto" -UnitMap "12"
-Name "diAddData0_B1b5" -SignalType "DI" -Unit "ioPluto" -UnitMap "13"
-Name "diAddData0_B1b6" -SignalType "DI" -Unit "ioPluto" -UnitMap "14"
-Name "diAddData0_B1b7" -SignalType "DI" -Unit "ioPluto" -UnitMap "15"
-Name "diAddData0_B2b0" -SignalType "DI" -Unit "ioPluto" -UnitMap "16"
-Name "diAddData0_B2b1" -SignalType "DI" -Unit "ioPluto" -UnitMap "17"
-Name "diAddData0_B2b2" -SignalType "DI" -Unit "ioPluto" -UnitMap "18"
-Name "diAddData0_B2b3" -SignalType "DI" -Unit "ioPluto" -UnitMap "19"
-Name "diAddData0_B2b4" -SignalType "DI" -Unit "ioPluto" -UnitMap "20"
-Name "diAddData0_B2b5" -SignalType "DI" -Unit "ioPluto" -UnitMap "21"
-Name "diAddData0_B2b6" -SignalType "DI" -Unit "ioPluto" -UnitMap "22"
-Name "diAddData0_B2b7" -SignalType "DI" -Unit "ioPluto" -UnitMap "23"
-Name "diAddData0_B3b0" -SignalType "DI" -Unit "ioPluto" -UnitMap "24"
-Name "diAddData0_B3b1" -SignalType "DI" -Unit "ioPluto" -UnitMap "25"
-Name "diAddData0_B3b2" -SignalType "DI" -Unit "ioPluto" -UnitMap "26"
-Name "diAddData0_B3b3" -SignalType "DI" -Unit "ioPluto" -UnitMap "27"
-Name "diAddData0_B3b4" -SignalType "DI" -Unit "ioPluto" -UnitMap "28"
-Name "diAddData0_B3b5" -SignalType "DI" -Unit "ioPluto" -UnitMap "29"
-Name "diAddData0_B3b6" -SignalType "DI" -Unit "ioPluto" -UnitMap "30"
-Name "diAddData0_B3b7" -SignalType "DI" -Unit "ioPluto" -UnitMap "31"
Example register handling when additional data have IO-type 100
-Name "diAddData_ErrorCode" -SignalType "GI" -Unit "ioPluto" -UnitMap "24-31"
7.1.3

Pluto stations 1

#
EIO_SIGNAL:
-Name "diPluto1_i0" -SignalType "DI" -Unit "ioPluto" -UnitMap "32"
-Name "diPluto1_i1" -SignalType "DI" -Unit "ioPluto" -UnitMap "33"
-Name "diPluto1_i2" -SignalType "DI" -Unit "ioPluto" -UnitMap "34"
-Name "diPluto1_i3" -SignalType "DI" -Unit "ioPluto" -UnitMap "35"
-Name "diPluto1_i4" -SignalType "DI" -Unit "ioPluto" -UnitMap "36"
-Name "diPluto1_i5" -SignalType "DI" -Unit "ioPluto" -UnitMap "37"
-Name "diPluto1_i6" -SignalType "DI" -Unit "ioPluto" -UnitMap "38"
-Name "diPluto1_i7" -SignalType "DI" -Unit "ioPluto" -UnitMap "39"
-Name "diPluto1_i8" -SignalType "DI" -Unit "ioPluto" -UnitMap "40"
27
2TLC172011M0205_B