I am measuring a varying voltage value and when it exceeds some threshold, currently set at .25, as shown in the image, I want the power supply to be cut off.
I thought I could just use a 'greater than' comparison to activate the power off button but it does not seem to work.
Any wire on a LabVIEW diagram can only have one source. It can be wired to any number of inputs but only one output - otherwise, what should the value on the wire be, if the two outputs returned different values?
If you want to use the result of your comparison to activate the 'off' case, instead of the Off control, you'll have to either:
Disconnect the Off control and connect this wire to the output of the Greater Than comparison function instead, or
Insert an Or function in the wire and connect the output of the comparison to the unused input of the Or. That way the 'off' case will be activated if either the comparison is True, or the button is clicked.
Related
I am adding a metric to a view's page caption. When it's null, it's showing "Null" or "None". What I want is to not show anything when it's null. Is there a way to make it happen?
I am thinking to cast the metric to string so I can add "else ''" in the editor but didn't work. Any ideas?
I added these two metrics and want to show the green one when it's good and red one when it's bad. however as you can see in the caption, the red one is "Null" instead of showing nothing.
the metric for good
the metric for bad
From the way you have defined your calculations, only one of them will be true while the other one is false (ie. either your ARR Churn Rate... is higher or equal than 0 making the "good" calculation true, or your calculation will be lower than 0 making the "bad" calculation true).
If a calculation is false, then no value will be calculated for it, making it end up as null (while the other calculation will be true and will have a value).
Why don't you use a single calculation with 2 different result options (ie. IF.... condition THEN..."good" ELSE "bad") and assign colours based on the good/bad result?
I apologize for the long title, but that is exactly what I am trying to achieve.
I'll try to explain more briefly here:
So I have a Zebra ZT610 with a scanner that checks every single label as they are printed. The problem is that we're trying to print labels solely, not in batch, and the issue with that is that the printed label will always be in a position where an operator will not be able to take the label without destroying it. The issue with this is it will become a waste of labels and ribbons if this process remains as is.
How it is now (it is not really in production, but to give you an imagination):
Operator clicks on print
Zebra prints a label (and the scanner checks the label simultaneously)
Operator feeds a label (in order to take the label without destroying it)
Operator takes the label
Repeat the process
That is the issue, in theory we would have to waste HALF of the amount of available labels (assuming that all printed labels passed the inspection) in order to finish the job, which is definitely absurd and no one in the world would do this hahah
What we're trying to achieve:
Operator clicks on print
Zebra prints a label (and the scanner checks the label simultaneously)
The printer feeds a label automatically (or maybe half of a label at least for the printed label to be taken without any issue or destroying it)
Operator takes the label
Operator prints another label
Printer backfeeds the latest fed label
Printer prints on the backfed label
Continue on from step 3, and so on.
I searched for anything related to this and all what i found was this:
^XA
^FD
^XZ
All it basically those is "print" a space on a label, thus technically feeding a label. But i was never able to get that label to go back inside the printer.
Thank you for reading this far.
EDIT:
We have also tried this:
Went into the printers settings via its IP address and login
Click on 'View and Modify Printer Settings'
Click on 'General Setup'
Below you will find 'Tear Off Adjust', we've set it to the maximum (120) but that was not enough, it is still too far inside.
But i hope the solution above helps other people out there.
Take a look at the ~JS command - Change Backfeed Sequence. By overriding the default backfeed, you can force the label media to feed forward after printing, then retract on the next print.
Not knowing how much backfeed you will need, start with 50% (~JS50) and adjust from there.
I am trying to solve with Comsol the problem of the figureTwo blue big electrodes with fixed potentials V1,V2. One red small electrode that moves above the others along x axis at constant distance and voltage V0. The charge in V0 depends on the electric field at each point 8(x). I have one small electrode with a potential V0 moving along x axis above two bigger electrodes with fixed potentials V1,V2.
I can easily compute with comsol the potential and field at each point in 3D and the resulting charge in V0 electrode. However i would like to simulate this charge along the x axis and eventually map it also for z and y direction so i have a V0 charge 2D map at a fixed distance.
How can i do this in COMSOL without changing the geometry coordinates manually and computing again the charge at each point?
Thank you for your answers,
Jorge
I'll describe how to setup the system so that you can move V0 around. Note that this requires changing the mesh throughout the simulation. For this reason, I don't think you want a "time dependent" study but instead you want to use the "parametric sweep" option.
First, go to your Global Parameters and create a parameter called block_x_pos or whatever you want.
Go to Component → Geometry and select V0 and in the appropriate field under the "Position" tab (in the Setting Panel), write block_x_pos in the X Position. This makes that position controllable by whatever value is in block_x_pos.
Right click on the appropriate Study and select "Parametric Sweep". The purpose (as far as I know) for the Parametric Sweep is that when the geometry is changing during computation, it updates the mesh accordingly, so you don't have to do it manually through some painful repetition. Select the "Parametric Sweep" node which has now appeared. Look in the Settings Panel and find the "Study Settings" tab. Below the empty table, you'll see some arrows and a "+" sign. Click the "+". This will add a new sweep parameter to the table. Click the dropdown menu on the table and select the "time" Global Parameter. In the "Parameter Value List" field, write the range of values you'd like to have it take.
i.e. if you want the block_x_pos parameter to vary from 0 to 10 in steps of 0.1, you would write range(0, 0.1, 10). Or you could write '-3 0 1 2 4 5 9 11' and it will take those values.
Now Compute using that same Study.
When you are making plots, be sure to use the correct Solution. It will be labeled something like "Study1/ParametricSolutions1". When you select this as your "Data Set", you will find (in your Settings Panel) a new dropdown menu below the "Data Set" field called "Parametric selection (time)". You can choose to show multiple values for the "time" parameter on most plot types.
I am implementing flipflops in logisim. Usually, their output gets back to the circuit as their own inputs. This only works if I manually insert an initial value to the flipflop and then reconnect its output to the input - otherwise, Logisim mark the connection in red and I get no output value.
Is there an easy way to set up the initial value of a flip flop in Logisim, so that I avoid having to break the connection all the time, adding an input and then reconnecting output and input?
The problem was that I was using a D-flip flop designed manually. Using logisim built-in flipflops works perfectly.
I am working to flush out some defects from an older program and I'm running into an issue with negative numbers in aebacus textboxes.
Basically, whenever a negative number (i.e. -1) is entered into a textbox, on focus lost the textbox shows the number with a trailing negative (i.e. 1-). On focus again, the number is displayed correctly as -1.
I have seen this in excel and maybe it is a formatting setting, or possibly just a limitation of vb6?
Apparently using a different font can fix it, in our case we made a custom font to alleviate the issue.