LabVIEW
Ramp function independent of Loop rate
@sgayen wrote:
these are the refined versions!!
You seem to try to answer a very old thread that has not seen activity in almost ten years. Why?
Please stop posting until you do a few simple LabVIEW tutorials.There is nothing "refined" about these VIs. They all suffer from blatant overuse of local variables and sequence structures, and if you analyze the code in more details, they are peppered with serious race conditions. In some of the programs, you read from terminals and local variables of the same terminal in parallel and there is no protection preventing different parts of the code operating on a different values. Similarly, you write to terminals and read from local variables of these same terminals in parallel. Since the order of operations is not defined, parts of your code might operate on stale values.
@sgayen wrote:
relax and have a look at it. experience matters, not certificates!
This is not a reasonable response to Gerd's helpful comments. I strongly urge you to gain some LabVIEW experience. As you say yourself, it matters! Learn about design patterns. None of the code you have posted would be pass any kind of certification or even internal company guidelines.
And no, a proud diagram comment of "no use of shift resistrar (sic)" is misguided. Shift registers are good!
Nobody should use these as examples. They are just plain bad!
sgayen wrote:I learn from bad people as well and think that bad programs also sometimes help us understand something good.
I agree that we can learn something from bad programs, but they should be labeled as such. You cannot label bad programs as "best ever" and "refined". That is just misleading!
If you want to post and discuss examples of bad code, we have the Rube Goldberg thread. 😄
If you want help re-architecting your code, just ask. We can give you some pointers. Especially if these programs are used locally in real applications, you need to get rid of the race conditions to make them more watertight. 😉
(... and please stop fixating on certification, or the lack of it. Code can speak for itself. No backstory needed. Everybody can immediately guess that you don't have any certification, and it does not need to be mentioned over and over)
