LabVIEW
Graphs are not updating
(Diadem does not have VIs, so I assume this is a LabVIEW problem and you posted in the wrong forum. I'll move the thread)
You should do a "save for previous" (2019 or below) before attaching. Many here don't have not upgraded to LabVIEW 2024 yet and cannot look at your VI. If the code is very simple, even showing a picture might be sufficient.
OK, I had a quick glance at your VI and it has horrible code smell.
There are no graphs, so I assume you talk about charts. Two They will only update when the "add" event fires and since they are in a FOR loop with a 10 second wait, you'll only get one point every 10 seconds. Since the event is set to lock the panel, not much can happen until that's over. the other four will add one point.
None of this has anything to do with "real time".
glaring problems (just the tip of the iceberg):
- Why do you have all these shift registers if you never use their output ever? THere is no reason for 3D arrays.
- Why is the front panel maximized to the screen if the active size is much smaller?
- A one iteration FOR loop is just a glorified sequence frame.
- I only have a 2560x1440 screen and thus cannot efficiently debug your VI. Your diagram is way too large!
- Your report button has the wrong mechanical action and only works 50% of the time because you need to check the value in the event case. Make it latch action!
- etc.etc.
Sorry, I am out. This needs to re-architected from scratch. Start with some basic tutorials.
Your VI is again in LabVIEW 2024, which I cannot currently open. Did you real my note about "save for previous"/
You need to define what you mean by "real time" (typically it has a very specific meaning involving RT hardware and software). If the charts should update on a a regular basis, they cannot be inside an event structure that triggers manually and takes at least 30 seconds to complete, locking the panel for that duration.
If the loop needs to spin at a defined interval, you probably don't even need an event structure.
Since the code I saw yesterday was such a mess, can you take a step back and explain in simple terms what the VI is supposed to do in what order and time interval, and how it should respond to user interactions. Do you have the "requirements" document? I have the nagging feeling that it could be done from scratch with 20% of the current code.
You have gaps in your comparison, what happens if you e.g. read 0.95?
You might show 0-0.9 (which is ok), but i assume it in reality is 0 <= x < 1?
For starters, do this improvement and remove your waits, why are they there?!
