From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
LabVIEW
temperature to waveform chart urgent homework help!
Solved!
@EngineeringBizi wrote:
... but when I search for blinking it's impossible to find...
You can either turn it on/off in a loop or you can look into the blinking property.
Above is my block diagram. Firstly, does it look ok? I didn't understand this whole blinking so I left it. I got some help for this from my class mates. In the true/false box the false has a green plot color and that's the only difference.
Those were the parts that I didn't understand. I understand the history being connected to 0 so that no history is retained every time it restarts i.e. the wavechart is not continuous, right? But why do I have to connect the scale multiplier as you can see. Also what's the benefit of connecting the outouts to DBL, why can I not connect difrectly? Sorry everyone...
First of all, you should be more careful with representations. The ms delta and the "points to acquire" should be blue (right-click...representation). The x-scale multipler translates between point number and actual time. For example if the loops spins once per 100ms, each update is 0.1 seconds and that what should show on the axis. If you don't set the multiplier, it defaults to 1 (or whatever the last setting was) and the x axis would be labeled as 0, 1, 2, 3, 4 ...
The dice gives you a random value between 0 and 1. Multiplying by 100 gives you a value between 0 and 100, a more typical range, e.g. encountered with temperatures.
The bundle node allows you to graph two plots at the same time. One showing the data and one showing the upper limit. Keep the operator informed!
I assume that the other case is otherwise identical, but contains a green color constant. You need to be aware that you cannot change individual color points. The color will appy to the entire plot. Also, duplicate code should NOT be inside the case structure. The property node belongs after the case structure. The case should only contain the color box (You should even replace the case structure with a select node instead!). It might be better to wire the data to one or the other plot, depending on the condition, while filling the remaining plot with NAN. Now the color seems to change for over-range values.
There is also a race condition, because the current code does not guarantee that the history gets erased before the the first data point is written. Wire the error out of the outer property node to the loop boundary to enforce dataflow.
You should also disable the delta control once the VI starts, because once the program starts it cannot be changed anymore in a way the code is aware of it. The terminal gets read only once.
You are already using property nodes, so this is not any different. Just select the blinking property and wire a true or false to it, depending on the condition.
