1 / 8

Lab #2 IOC Database

In Lab #2 of the IOC, you will explore advanced database functionalities using the Vortex Development Configuration Tool (VDCT) editor. This lab involves creating and modifying records, testing new features with CAU, probe, or EDM, and implementing a sawtooth pattern generator. You'll learn how to configure database fields, manage IOC processes, and enforce security measures on records. By the end of this lab, you'll be adept at enhancing database capabilities and securing access to specific structures within your IOC setup.

debra-brady
Télécharger la présentation

Lab #2 IOC Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lab #2IOC Database

  2. Lab #2 Outline • Look at the example database used for Lab #1 • Learn how to use the vdct database editor • Create some new records and functionality • Run the IOC and load the new records • Use cau, probe or edm to test the new functionality • Repeat steps 3-5 until it works

  3. Examine yesterday’s database • Use the linux more command (or your favorite text editor) to look at the file ~/example/db/dbExample1.db • Work out how the $(user):calcExample record field values configure the record to generate the sawtooth pattern we saw yesterday • Look at the file ~/example/dbd/example.dbd • Start the IOC by typing cd ~/example/iocBoot/iocexample ../../bin/linux-x86/example st.cmd • Look at the commands it executed from the st.cmd file, and what messages were reported • Type help at the epics prompt for a list of commands

  4. Example1.db record(ai, "$(user):aiExample") { field(DESC, "Analog input") field(INP, "$(user):calcExample.VAL NPP NMS") field(EGUF, "10") field(EGU, "Counts") field(HOPR, "10") field(LOPR, "0") field(HIHI, "8") field(HIGH, "6") field(LOW, "4") field(LOLO, "2") field(HHSV, "MAJOR") field(HSV, "MINOR") field(LSV, "MINOR") field(LLSV, "MAJOR") }

  5. Example1.db (cont’d) record(calc, "$(user):calcExample") { field(DESC, "Counter") field(SCAN,"1 second") field(FLNK, "$(user):aiExample") field(CALC, "(A<B)?(A+C):D") field(INPA, "$(user):calcExample.VAL NPP NMS") field(INPB, "9") field(INPC, "1") field(INPD, "0") field(EGU, "Counts") field(HOPR, "10") field(HIHI, "8") field(HIGH, "6") field(LOW, "4") field(LOLO, "2") field(HHSV, "MAJOR") field(HSV, "MINOR") field(LSV, "MINOR") field(LLSV, "MAJOR") }

  6. How to edit databases in vdct • You can either create a new database file for your PVs or add them to the file ~/example/db/dbExample1.db • To start vdct: cd ~/examplevdct & • Select a database definition file: In the dialog box, select and open dbd/example.dbd • To modify the existing db/dbExample1.db file: Use the File/Open menu item, or the left-most toolbar button • Edit away (see Help Topics menu item or vdct manual for keys) • Save the edited (or new) database ... From file menu, pick Save or Save as ../db/_.db • If you created a new database, edit ~/example/iocBoot/iocexample/st.cmd and add a line to load your new database.

  7. Suggested Database Changes • バイナリ入力レコードを追加し、caclExampleレコードのカウント動作を停止・継続を制御する。 • How many other ways can you devise of controlling whether calcExample cycles or not? • Adding new records is allowed and even encouraged • Add another binary input record, and some logic to only permit oscillation when both records are “On” • Extend this so that the sawtooth only stops after the permit has been withdrawn once its value reaches zero • Replace the sawtooth generator with one that is smoother (i.e. doesn't just go up in integer steps)

  8. Implement Channel Access Security in your IOC so that only studnt_ can modify studnt_:calcExample. • Create an access security configuration file named rules.cas in ~/ioc/iocBoot/iocexample Additional Database Exercises • Add the following line to ~/ioc/iocBoot/iocexample/st.cmd asSetFilename("rules.cas") • Changestudnt_:calcExample.ASG to SUPERUSER. • Add other security conditions as desired. UAG(users) {studnt_} ASG(DEFAULT) { RULE(1, READ) RULE(1, WRITE) } ASG(SUPERUSER) { RULE(1, READ) RULE(1, WRITE) { UAG(users) } }

More Related