Hello everybody.
Trying to open an exercise from Data Acquisition Using NI-DAQmx and LabVIEW course but an error load message appears (please see the attachment).
Could anybody help me, please?
Hello everybody.
Trying to open an exercise from Data Acquisition Using NI-DAQmx and LabVIEW course but an error load message appears (please see the attachment).
Could anybody help me, please?
I have recently upgraded from 2013 to 2019 and when I go into my old code written in LV-2013 and toggle between cases in my state machine the entire structure grows each time I toggle to the next case. I tried disabling auto grow however this has no effect and the case still grows. I have made sure that all the updates are installed and am currently at a loss. As you can imagine this makes working on projects very difficult, as I can not seamlessly switch between cases. Any advice on things to try would be helpful.
Thanks,
J
Hi All,
Is it possible to program cRIO-9036 using Keysight VEE software via its USB port? Thank you in advance for your comments.
Hello all,
I am logging data to disk using TDMS write in a producer-consumer architecture. I noticed in my test data that there are few instances where there is irregular data intervals. For example, when I set my data logging rate to 1 per 10 seconds, there are few spots where data is taken at 10.1 seconds. See the attached images to get an idea of what I mean. In the example, data1 is written at 21.204 seconds and data2 is written at 31.214 seconds, while my data logging rate is set to once every 10 seconds. This also starts drifting the data longer and longer. I usually run day long tests, so this drift could be very bad.
Any idea what causes this? It seems to me to be some hardware timing limitation. I am, however, running LabVIEW on my laptop using a simulated PXIe 6361.
Thank you for your time
Hello,
I wanted to ask if anyone has worked on an implementation of a non-negative matrix factorization in Labview? I need some food for thought.
I use version 18.042 (64-bit)
Thanks a lot
Marco
I don't know how many people use the MGI Panel Manager for their panel management needs, but I've recently started using it heavily and very much like it. However, I almost immediately ran into an issue using the Persistent panel position type.
I have several Window panels up at the same time, and they all get closed at the same time. They all have their Window Position object set to a Persistent Position child class. This executes a Pre-Close Action VI when the panel is closed via the Window:Close method. The Persistent Position:Pre-Close Action method opens an ini file to save the window bounds as a string under a "unique" key name in the ini file. (I say "unique" because the ID can be provided by the user and there is no internal check to see if it is truly unique.) The "Window Positions.ini" file is created automatically if it does not already exist, the position key for the panel is stored, and the changes are saved.
This all appears to work nicely iff the Window Positions.ini file already exists. In my example, I have three panels running that use the Persistent Position class. All of these VI's are called asynchronously with reentrancy. Let's call them A, B, and C. A and B are the same VI; C is a different VI but very similar code. I close them all "simultaneously" by sending them all a user event (in a For Loop that does nothing but use Generate User Event) that triggers the Close method. The Window Positions.ini file is created as expected, but only contains the position keys for panels A and C. If I run and stop the application again, the Window Positions file contains the positions of A, B, and C as expected (and the A and C positions do change if the windows were moved).
So the issue seems to be that all of these functions are calling the Pre-Close Action method that opens the Window Positions.ini file at the same time. Unfortunately, the Pre-Close Action method is set to Shared clone reentrant execution. This allows it to simultaneously open a reference to the same ini file.
The fix for me was to change the reentrancy setting of the Pre-Close Action method to Non-reentrant execution.
Just wanted to put this out there in case anyone else has the same issue. Hope it helps.
Hello,
I'm quite new to LabVIEW and am trying to produce a VI for long term (weeks to months) continuous measurements of the voltage and temperature of a water electrolyser.
I've been editing the Continuous measurement and logging template for this- but can anyone explain to me why it is that when it comes to logging the data, the template involves asking for the number of samples that need to be saved? (see Log Data.vi as part of the Logging Message Loop.vi)
For continuous acquisition isn't it an endless amount of samples until logging is turned off?
My impression so far is that it needs to know how many to save so that it can count down, changing it's logging state to off when the samples left reaches zero- I'm assuming so it doesn't end up trying to log data from an empty queue (would this cause an issue?)
I only plan to have logging toggled on and off by the user, not by how much data is available, and I'm not sure we'll ever know how many samples it will be.
So can I remove it, or is it in there for some kind of memory saving or error preventing reason?
If it's of any relevance I also don't plan to save to TDMS, just haven't changed it yet
Thanks,
Siobhan
edit- logging zip alone missing (no so relevant) subvis, so attached whole template too
Buenas tardes.
Estoy trabajando con el software para realizar una grafica que muestre dos variables: temperatura y presión. Esto es apenas una simulación, puesto que aún no tengo el sensor que utilizaré.
Lo que me interesa lograr es que la gráfica muestre los cambios de ambas variables a medida que pasa el tiempo, puesto que ahora mismo en la simulación solo se ve la bajada de cualquiera de las dos pero de forma lineal, es decir, no se visualiza el cambio, por ejemplo, cuando la presión baja de 80 a 70.
Pienso puede ser por el tiempo al que está configurada mi gráfica o porque aún no se encuentra obteniendo información de un sensor en tiempo real.
De todas formas, si es posible lograr esto en simulación me gustaría saberlo, o de alguna otra forma en que pueda comprobar que mi gráfica, y mi código en general, están funcionando correctamente.
¡Gracias!
I have noticed that from time to time the LLB file in my project directory will transform itself into a plain folder.
Are they supposed to do that?
Has anyone else see this?
LabVIEW 2018, W10 pro. I am using TortoiseSVN for version control.
Hello all,
I have an issue writing boolean values to a TDMS file. I have 6 buttons on the front panel in an array. I want the boolean values of each button to be written in a column of its own using TDMS write at a frequency I specify. I've tried using a producer/consumer architecture but to no avail. I'm not sure how to proceed. The data that is written in the TDMS file is one column long and full of boolean values that doesn't make any sense.
Hi guys
How can i pause the waveform chart execution for some time making it constant and then continuing its execution hence making it for example linear constant linear
Hi,
I have an issue with an executable that will not work on a few PCs. The executable contains sub-VIs that have special characters in their name (e.g. "µs to ms.vi"). When I start the exe it will try loading the sub-VIs but those with special characters cannot be found (see attached image). It should be noted that in the title bar Labview claims to look for "�s to ms.vi" instead of "µs to ms.vi". If I select the correct file ("µs to ms.vi") Labview will continue loading without warnings or errors, but the VI has a broken start arrow.
I cannot change the names of the sub-VIs and the program is running on all other PCs without problems (all Windows 7 or Window 10).
It's obviously some kind of unicode-character problem, but any suggestions how this can be solved?
Thank you,
Thomas
How can I create a polymorphic or malleable giv in LabVIEW NXG?
The only information I can find is: https://forums.ni.com/t5/NI-Blog/Designing-LabVIEW-NXG-Configurable-Functions/ba-p/3855200?profile.language=en
But it does not tell or share how to do this in LabVIEW NXG? Where can I find this information? Or am I just missing something?
Hello,
I am a student working on strain measurements on axially loaded steel sections.
For this work, Ni compact Rio and NI 9237 module are being used. A labview code interacts with the system to record the strain from electric strain gauges. The steel section has a full bridge setup in the axial direction.
The question i am not sure about is,
what data is being recorded without any calculations done in NI codes? is it,
1. voltage difference across the bridge (or)
2. mV/V (i.e. Vo / Vex)
To calculate the mechanical strain, can I use this formula if its mV/V, which is for Full bridge type 3 configuration.
strain, ε= (-2Vr) / (GF [(ν – 1) – Vr (ν + 1 )] , where Vr is the mV/V
How can I convert to mechanical strain if its difference across the bridge.
Thanks for the response.
I have a project that contains numerous xctrls that was originally developed in LabVIEW 8.6 and when I try to import this project into LabView 2020 I receive the following errors when 3 of the xctrls attempt to open.
The expected filename does not match the expected file name.
the listed filename has what appears to be a space at the start of the file name in the error message, yet the actual filename does not. For example "c:\ Low Speed Pot V2.xctl"
The Xctrl also uses a GUID vi that is also distributed with version 8.6 I am aware of this problem and a solution it is not a contributing factor of the filename issue.
I have attached the source files for the xctrl.
I have an xlsx file of data obtained using Labview 2015 that I am unable to open. The data was collected and the laptop screen froze. Once this was working again the file was saved but when I tried to open it there was a message that the file could not be opened due to file format or extension. Is there any way I may be able to open this?
I am using the 2019 version of Labview to create a new program.
The old program is made of Labview 2015, so if i want to make modifications, Labview 2015 is required.
DAQmx 2019 version does not support Labview 2015
Labview 2019 is not supported when using DAQmx 2018 version.
Is there a way to use both without using VMware?