Christian Tsoi-A-Sue  Jansen-Whealey, Lana 

  1.  NETCONFIG:
    1. Purpose: A netconfig entry autocreates/auto-associates an IP address to a device through its MAC address.
    2. Command(s):    netconfig search
                               netconfig add

                        Example: 'netconfig search power-cxi*'

    1. Need: 
      1. MAC Adress
      2. Description
      3. Contact Info
  2. Local programming/configuration:
    1. Purpose: Need to have the device recognizing itself with the newly auto-generated IP address from netconfig entry
    2. How?: Depends on devices
      1. PDUs: Need to locally connect with ethernet cable, and access its page. (Reference:  PDUs
      2. SETRAS/OTHERS: Need to go to their connection screen and ensure the devices IP address is updated and has correct configuration inputs (baud rate)
  3. Attempt to access over network
    1. PING the device
      1. Command Ex: ping 172.21.69.23
      2. If it pings, YAY, good job, the device is now communicating!
      3. If not, need to troubleshoot
  4. IOC
    1. Purpose: To get devices on EPICS/LUCID. To align netconfig entry with chosen PV name. PV names have to follow a format
    2. How?: Create IOC
      1. most have parent iocs, so you can usually go ahead and create a child (.cfg) version
      2. Use a similar device .cfg file as reference
    3. Remove 'old' files
      1. Command: 'make clean'
    4. Build IOC
      1. Command: 'make'
      2. If errors, will need to troubleshoot IOC
  5. IOCManager
    1. Purpose: Creates PV
    2. HOW?:Create entry on iocmanager
      1. double-click on most left hand side section, and select create new ioc
    3. Need?:
      1. host name
        1. Dependent on if IOC was created for rhel5 or rhel7
      2. IOC name
      3. directory location
  6. Testing/verifying
    1. Use archiver and/or grafana pswww.slac.stanford.edu
      1. Give iocmanager time for it to upload, will not be instantaneous 




















  • No labels