Moving a mater/slave group from one port to another in system configurator

 This post describes a procedure for moving a master or slave protocol group from one comms port to another.  The comms port can be on the same or different cards in the RTU File.

Note:  This procedure is not (to my knowledge) an approved or recognised procedure (by Foxboro) for accomplishing this task! Proceed at your own peril and backup first.

 

  1. It is assumed that the port that the protocol group is to be moved to has already created in System Configurator.  System Configurator may or may not be running whilst making changes to the database, depending on your installation.  If errors are encountered connecting to the database withpsql then close System Configurator.
  2. In this example the DNP3 Master group will be moved to the second port on the 8 Channel Serial Card on slot 5.
  3. Open Bash

    • Bash can be started by start->run and type bash
    • If not, run C:\Program Files\Foxboro\cygwin\cygwin.bat or C:\Program Files\Foxboro\cygwin\bin\bash.exe (change path to suit your installation)
  4. Start psql
    • At the bash prompt open the SYSCFG database by typing psql SYSCFG
    • NOTE: At this point it is good to increase the screen buffer size so that all the tables will format nicely.
  1. There should now be a psql prompt like the image above which reads SYSCFG=#
  2. Locate the comms ports the protocol group is to be moved from and to.
    • For all the comms ports, type select * from comms_port;
    • For serial ports only, select * from comms_port_serial;
    • For Ethernet ports only, select * from comms_port_ethernet;
    • For optonet ports only, select * from comms_port_optonet;
    • The more specific tables will contain additional information that might help identify the correct port.  Specifically, they will identify the card to which they are attached.
    • To view the cards in the file, type select * from card;
    • When the correct comms ports have been located, record their oids (first column in the table).
    • In the example above, the correct ports can be identified from the port number in the card, ie port 2 in the V28_DCB card and port 2 in the Multi_Chn_Serial card.  Adding descriptions in System Configurator may make this much easier, as the description will appear in the table.  ‘From’ port/card oids are in the red boxes, ‘to’ port/card oids are in the blue boxes in image above.
  3. Locate the protocol group that is to be moved.
    • For slave groups, type select * from protocol_slave_grp;
    • For master groups, type select * from protocol_master_grp;
    • The correct group should be able to be identified from the oid of the comms port and other information in the table.  Optionally, type select * from protocol_master_grp where comms_port_oid=201201240949535730; to go straight to the correct group (replace the number with the correct oid that was recorded earlier.  Record the oid of this protocol group.
  4. Move the protocol group.
    • For master groups:  update protocol_master_grp set comms_port_oid=xxxxx where oid=yyyyyy;
    • For slave groups:  update protocol_slave_grp set comms_port_oid=xxxxx where oid=yyyyyy;
    • Where xxxxx is the comms port oid recorded in step 6g (port to move protocol group to) and yyyyyy is the oid of the protocol group recorded in step 7c.
  5. Refresh (or start) System Configurator by right clicking the RTU or file and select refresh.  The protocol group should have moved to the new serial port.

| April 29th, 2012 | Posted in Foxboro, SCADA |

Leave a Reply