cadomanis
Member
I am finding a increasing need to log both faults and actions in my projects. I have typically done this ( at least for faults) by creating a latched copy of the fault, and then executing a logging subrouting whenever that latched version turns off. I also used the latched version of the faults throughout my code to control other actions/functions. When there are upwards of hundreds of these simple latching rungs, it can become a big mainteance drag / memory hog. I have come up with a new idea using a for-next loop strucuture to make things easier, but I am unsure about a few things.
1) Are the latched bits going to stay maintained from one execution of the subroutine to another.
2) Is the for/next strucutre going to prove very processor intensive and bog down my scan.
I have attached a PDF of the code in questions. There is a singel example of the old method, as well as the new subroutine. Any feedbak would be greatly appreciated. Compeltey differnet ideas and solutions are of course also welcome.
thanks,
C-
1) Are the latched bits going to stay maintained from one execution of the subroutine to another.
2) Is the for/next strucutre going to prove very processor intensive and bog down my scan.
I have attached a PDF of the code in questions. There is a singel example of the old method, as well as the new subroutine. Any feedbak would be greatly appreciated. Compeltey differnet ideas and solutions are of course also welcome.
thanks,
C-
