Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

Using UDT as Input to FC, invalid handle

Created by: DLittlejohn412 at: 6/18/2012 9:59 PM (4 Replies)

Rating (3)

Thanks 5

5 Entries

6/18/2012 9:59 PM	Rate (0)
DLittlejohn412 Posts: 55 Rating: (1)	Hello Again I created UDT100 (symbol AI_PARENT), then created DB1000 (symbolTE01) of type UDT100. Icreated FC1000. Declarations: IN: AI_RAW_IN Data Type Word IN_OUT: TEST_A; Data Type AI_PARENT (UDT100) NW1: MOVE #AI_RAW_IN to #TEST_A.RAW_VALUE. NW2: FC105 When I put FC1000 in OB1, it allows me to usePIW280 (TE01_IN) for the AI_RAW_IN parameter, but when I try to use TE01 (DB1000 of UDT100)I get error message "Compiler information: handle not valid" When the TEST_A field is blank on the FC1000 call, the input line says "Expected Data Type: INOUT: UDT"
DLittlejohn412 Posts: 55 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users dom8703

6/19/2012 4:17 PM	Rate (2)
Jazz_M Posts: 1121 Rating: (86)	Hi Call the UDT in shared DB and then give the DB a symbolic name. Then call your FC in OB and then delcare the db name, a drop down box will appear, select the name that you used to store the UDT in Shared DB. your instance shall be taken from the DB. If you use UDT you can not delcare it directly, you will have to declare via the DB. Take care that the FC size will increase in the process. Have fun...
Jazz_M Posts: 1121 Rating: (86)
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users DLittlejohn412 S.Filipov dom8703

6/19/2012 4:48 PM	Rate (0)
DLittlejohn412 Posts: 55 Rating: (1)	Thanks. I will try that. Are there some examples doing this in one of the Siemens libraries? Is it ok to do this in ladder, or is it better done in STL? <EDIT>OK.. so I tried that and it looks like ladder is OK. So now my question becomes, is this the proper way to do what I am hoping to do? What I am trying to do is create a UDT for the analog inputs to the machine. Inside the UDT, I think I will have additional UDTs. The end result will be DB with information on the analog inputs. TE01 " ".SCALE_HI " ".SCALE_LO " ".EU " ".HIGH_LIMIT " ".LOW_LIMIT TE02 " ".SCALE_HI etc... Then use those tags throughout the program in various FCs to do sub call to FC105 "Scaling" sub call to a FC to perform alarms etc... Am I on the right track this way?
DLittlejohn412 Posts: 55 Rating: (1)	Last edited by: DLittlejohn412 at: 6/19/2012 5:13 PM
Suggestion To thank Quote Answer

6/19/2012 7:00 PM	Rate (1)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 12/25/2025 Posts: 12474 Rating: (2722)	Hello DLittlejohn; Have a look at the following FAQ on UDTs and function param,eters, you might find it interesting for your application: How do you create and parameterize variables and the IN, OUT and IN_OUT parameters of the UDT data type? Hope this helps, Daniel Chartier

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users DLittlejohn412

6/19/2012 8:53 PM	Rate (0)
DLittlejohn412 Posts: 55 Rating: (1)	Thank you. This does help some more. In using the array, as in the sample, how does one tie one of the array members to a specific tag/symbol? I.e. call MOTOR[1] PP-01 or something like that? In Allen-Bradley, you can do tag alias, so PP-01 alias would be MOTOR[1]. Later in the HMI, I would like to use the tags by the individual identifiers, PP-01, PP-02, etc....
DLittlejohn412 Posts: 55 Rating: (1)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on