1 / 9

TELL1 How to make your User Specific Framework Component

TELL1 How to make your User Specific Framework Component. What do you need?. - ctl library for your own functions (e.g. called by FSM) - panels (e.g. for MEP-parser, registers, recipes) - datapoint type (the specific part) (recipes & device unit types can be modified as well).

neveah
Download Presentation

TELL1 How to make your User Specific Framework Component

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. TELL1 How to make your User Specific Framework Component Status Report

  2. What do you need? • - ctl library for your own functions • (e.g. called by FSM) • - panels (e.g. for MEP-parser, registers, recipes) • - datapoint type (the specific part) • (recipes & device unit types can be modified as well) Status Report

  3. The basic structure: • - create a directory called fwTell1_SubDet • - with subdirectories: config, dplist, panels, scripts • - in config you can put a file called fwTell1_SubDet.init: • e.g. • main(){ • fwInstallation_appendManager(0,”yourName”, PVSS00ctrl, “always”, 30, 2, 2, • “yourScript.ctl”) • } • This installs an additional ctl manager – if needed. Status Report

  4. The basic structure: Status Report

  5. panels: - create a sub-directory with the path: panels/fwTell1/SubDet - put in all your specific panels in this directory (feel free to add additional sub-subdirectories) - Panels are called by: e.g. ChildPanelOnCentralModal(“path/yourPanel.pnl”, “name”, makeDynString(“$1:”+$1, “$2:”+$2)); - this demonstrates how to pass the Dollar parameters to the panel - please be tidy: complex procedures to be put as functions in scope lib initialization procedures to be put in initialize of panel do not spread everything into widgets! (not easy to debug) or e.g. if you are calling from a tab register: there is an editor where you have to give the correct path and $-parameters check our example in fwTell1.pnl Status Report

  6. scripts: - in this directory you put your scripts to be called by your ctl manager - in a subdirectory called libs you can put your own library. Use our fwTell1.ctl as template so you can profit for already existing comments for doxygen. Status Report

  7. scripts: you may want to have a function like: fwTell1SubDet_Configure(domain, device, runType, partID, nSteps); Status Report

  8. dplist: - hardware is stored in fwTell1DPT_ALLTYPES.dpl - use ASCII manager (see tutorial 2 – fwHw) and create your fwTell1_SubDet.dpl - It will overwrite the default datapoint ( - In case you want to store minor modifications in the FSM you can make a dpl of the device unit.) Status Report

  9. How to tell the installation tool: - with a xml file next to your sub-directories (on top): fwTell1_SubDet.xml e.g. <component> <name>fwTell1</name> <version>2.3.5</version> <date>12.12.2007</date> <init>./config/yourInit.init</init> <dplist>./dplist/fwTell1_SubDet.dpl</dplist> <file>./scripts/fwTell1_SubDet_yourManagerScript.ctl</file> <file>./scripts/libs/fwTell1_SubDet.ctl</file> <file>./panels/fwTell1/SubDet/yourPanel.pnl</file> </component> - Install everything on top of the fwTell1 component Status Report

More Related