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