Jordan Kuehn Posted October 19, 2022 Report Share Posted October 19, 2022 That is working to measure loop iteration time. Stores the initial time in a shift register. Then each iteration takes the current time and subtracts the previous, while also storing the current time in the register for use in the next iteration. 1 Quote Link to comment
Nazar khan Posted November 6, 2022 Author Report Share Posted November 6, 2022 thank you brother Quote Link to comment
Nazar khan Posted November 6, 2022 Author Report Share Posted November 6, 2022 you don't know here 59 for what is set what function is performed using this ? chasy-1.vi Quote Link to comment
Neil Pate Posted November 7, 2022 Report Share Posted November 7, 2022 (edited) Well, given that this is some kind of (bad) timing logic, and 59 is suspiciously like the number of seconds in a minute, I would suspect this is some kind of check to see if the elapsed time is > 1 minute. I strongly suspect this code is overcomplicated and there are signficantly simpler ways of doing things. These four sections of parallel code below look like they constantly evaluate if the elapsed time is greater than 45, 30, 15 and 59 seconds. The shift register on the boolean essentially latches (i.e. remembers) the previous value, and I think the XOR is used to reset the latch. I am not sure what is in the other cases of the Case Structures. Strangely the top one is active on a False, whereas the others are on True. Edited November 7, 2022 by Neil Pate Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.