5/2/2012 8:31 AM | |
Posts: 18 Rating: (0) |
Oks folks thanks for the help i think i get it |
5/2/2012 5:40 PM | |
Posts: 18 Rating: (0) |
Well I stop using set/reset instruction as temp vars, but what about pos/neg edge detection instruction. Let look that example. I have mowing object on a belt transporter. And optic sensor. Then the sensor close I have on delay timer ‘passTimer’ and after timer shot the sensor have to be clear - this means that the moving object is passed (the pass single is just one pulse) . If the sensor is active more than 8 s the ‘errTimer shot and that means that something wrong happed - fall object, dirty screen of sensor and so on. Then If I have 3 sensor like that I put function 3 instances in ob1 and then if I have M0.1 set and after T2 shots I have M0.5 set, but I have to be M0.2, and worst is not just pulse is permanend output. So what happed here why form conditions on first instance the output is on second. The only one way from my poit of view is to set ‘neg1’ as input var not temp. Is what mean that I can’t use set/clear, neg/pos instruction like temp var? Here are images of function and the interface are: FC1: input: sigIn – bool; errTimer – timer; passTimer – timer; errInterval – s5t#3s; passInterval – s5t#8s out: pass – bool; err – bool temp: neg1 – bool AttachmentFC1andOb1.zip (159 Downloads) |
5/2/2012 7:28 PM | |
Posts: 559 Rating: (87) |
We can save memory of creating DB by using FC in this way. But it is preferable if you have limited temp words Other wise u can go for FB |
5/3/2012 9:53 AM | |
Posts: 18 Rating: (0) |
Thanks for that idea. But I have to write this code in the beginning and end of every function …. may be I will choose FB instead. |
Follow us on