Industry Online Support
Technical Forum
5/13/2012 1:47 AM | |
Joined: 11/4/2011 Last visit: 8/25/2024 Posts: 253 Rating: (53) |
Hello Tagolover, I tried to find out how the FC369 SelST16 is working. I removed a protection off the FB1900 VlvMotL and looked at the operations made under ST_Worst variable. Oh, they are weird . A piece from the source file made from unlocked FB1900: L #FbkOpngOut.ST;Temporary memory area from LB 94 is not defined. The stcInST temp variable is defined according to the input variable of FC369: stcInST : STRUCT //Input 0..15 Signal Status..and has local address 26 but there's no clue on how it is passed to the FC369 :) but let it be, maybe the true source file shows everything in the other way, in the currect way. I tried to use FC369 in my test program and as for me everything works fine. I filled stcInST 's bits from 0 to 11 and called the function: CALL "SelST16" InST :=#stcInST Num :=12 SelPrio:=0 RET_VAL:=#ST_Worst Interesting parameter - SelPrio. Something about the statuses and their priorites is written in "PCS 7 - Manual for Advanced Process Library V7.1" manual: 1.1.5.2 Forming and outputting the signal status for technological blocksSo if SelPrio=0 the priority of choosing the status corresponds to the table. If at least one of the parameters equals 16#60 this value would be returned. If SelPrio=1 the priority order is strange :) 16#80 - 00 - 28 - 68 - 78 - 60 - A4 etc Best regards! ______________________________ Excuse me if I'm talking to much |
This contribution was helpful to2 thankful Users |
Follow us on