slide1
Download
Skip this Video
Download Presentation
TELL1 How to make your User Specific Framework Component

Loading in 2 Seconds...

play fullscreen
1 / 9

TELL1 How to make your User Specific Framework Component - PowerPoint PPT Presentation


  • 62 Views
  • Uploaded on

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).

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'TELL1 How to make your User Specific Framework Component' - neveah


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1
TELL1

How to make your

User Specific Framework Component

Status Report

what do you need
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

slide3
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

slide5
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

slide6
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

slide7
scripts:

you may want to have a function like:

fwTell1SubDet_Configure(domain, device, runType, partID, nSteps);

Status Report

slide8
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

slide9
How to tell the installation tool:

- with a xml file next to your sub-directories (on top):

fwTell1_SubDet.xml

e.g.

fwTell1

2.3.5

12.12.2007

./config/yourInit.init

./dplist/fwTell1_SubDet.dpl

./scripts/fwTell1_SubDet_yourManagerScript.ctl

./scripts/libs/fwTell1_SubDet.ctl

./panels/fwTell1/SubDet/yourPanel.pnl

- Install everything on top of the fwTell1 component

Status Report

ad