Quantcast
Channel: All LabVIEW posts
Viewing all 202002 articles
Browse latest View live

Re: displaying a signal in a waveform chart in "slow-motion"

$
0
0

I'm attaching a second Down-Sampling Demo that I think does a more useful job of illustrating the point.  This is the "Driver", which generates a 10Hz Sinusoid with amplitude 1 + Gaussian Noise with Amplitude 1, 1000 points sampled at 1KHz.  It feeds this into a DownSample Utility with a Decimation Factor (e.g. 20 means "combine 20 points into a new point, either by taking the Mean of the 20 points or simply choosing the first one"), returning two Down-Sampled Waveforms, plotting everything.

DEMO DownSample.png  Here's a Result:DEMO DownSample FP.png

Note that the Meaned Waveform has less "noise" (the Mean acts as a Low-Pass Filter), while the Decimated version "preserves the Noise".

 

The process of the Down-Sample Utility is straight-forward:

UTIL DownSample.png

The attached VIs are in LabVIEW 2015 (though the Snippets are LabVIEW 2016).

 

Bob Schor


Re: Can I transfer data through FIFO in two different myRIO FPGA Targets?

$
0
0

Hi Ahmad,

 

when you already used a "digital" pin to signal a trigger from one myRIO to the other, then why can't you use the very same connection to send information on the "zero degree" or "start of next rotation"? This way your 2nd myRIO can synchronize to each full rotation…

Re: How do I use a USB hard drive with ext3 starting from scratch

$
0
0

Attached is a snapshot of a few fdisk commands (while in fdisk)

Re: Problem in getting accurate measurement using NI 9227

$
0
0

Thanks a lot for your reply

 

1. Yes it is within calibration

2. Its ground referenced signal, I have grounded the shield of the Lapp cables and connected A+ and A- respectively.

3. Yes, they are indicating differently when multimeter is placed inline with NI9227

4. Acquisition rate 1ks and no of samples per channel is 100

5. I am using cDAQ 9185

Re: Digital to analog conversion labview

$
0
0

Yes, but I can not get the correct frequency. If I insert a 100 Hz frequency I obtain 4Hz in an oscilloscope. I don't know how synchronised the samples for be read correctly

Re: Problem in getting accurate measurement using NI 9227

Re: Importing WSDL to LabView / .NET issue

$
0
0

Thank you for your reply!

 

I tried to pass inputs (see below). Unfortunately, I do not know how to pass GUID to the .NET.

Could you please point me in right direction?

SessionID         00000000-0000-0000-0000-000000000000

ApplicationID   870f02e5-9516-44ac-b1af-03c2cb4349ae

ClientID            76EE01BD-7369-4252-BBB1-85D9EB77EC10

 

 

Deployment Completed with Errors on sbRIO-9651 using LabVIEW 2017 SP1

$
0
0
Howdy!
 
I have a question regarding a nagging problem that we've been having lately with our LabVIEW RT Application and sbRIO-9651 SOM controllers. I'm trying to run the top-level RT VI for our application from the project explorer window. When I do that, LabVIEW begins to deploy all of the VI's within the application but at the very end of the deployment there is a message that states "Deployment completed with errors" as you can see in the attached screenshot. Then the board restarts and I lose connection. I have gone through the list of deployed VI's and do not see any VI's that are broken or have been deployed with an error. The only indication of an error in the deployment is at the end of the deployment
 
I tried running a simple example program on the RIO called sbRIO-9651 Read On-Board Temperatures. The RT code for this example project has an enable/disable diagram structure surrounding the FPGA interface reference section of the code. I was able to duplicate the error when this section of code was enabled. However, when this section of code was disabled and only the RT code was run on the controller (no FPGA interface) the code was able to deploy and run successfully. The additional attached screenshots show this as well.
 
We have 2 custom carrier cards that two separate SOM boards are docked on. This problem has occurred on both of these systems. We also have a third SOM with the NI Reference Carrier Card in-house. I've also swapped out the SOM from the reference carrier card with the SOM on our custom board and the error persists. I've also used 2 different development laptops to try and deploy the code and the error persists. The only way I'm able to run the top-level RT VI on the SOM and custom board is when the FPGA interface VI's are disabled. However, the VI's run with no problem on the NI Reference Carrier Card (FPGA Reference VI's enabled).
 
We're running:
 
Windows 10
LabVIEW 2017 SP1
NI CompactRIO 17.0 on the SOMs
 
I'm communicating with the SOM's via the USB connection.
 
Any help would be sincerely appreciated.
 
Thank you,
 

Alex


Re: LIN Communication - Slave doesn't answer

$
0
0

Maybe I wrong the slave NAD. Can I sniff the address of the slave?

 

Thank you,

Fabio 

Re: LIN Communication - Slave doesn't answer

$
0
0

ha scritto:

Maybe I wrong the slave NAD. Can I sniff the address of the slave?

 

Thank you,

Fabio 


sorry, I read the ID from the NI-XNET Bus Monitor

Re: How to write header to CSV automatically ? my vi attached

$
0
0

Hi Ozgur, 

 

Thanks for the VI, but it seems that I still need to write the string of header myself right?  I need to give that string to the header input..   Or there is no way to do that all automatically ? 

e.g like you create any indicator, the indicator always has a name automatically. like, you use the plus vi,  the output indicator name is x+y .   

Re: Write to measurement file (.xlsx)- Append new data but in new sheet/table

$
0
0

Yup I also suggest the report generation toolkit.  It is free with several versions of LabVIEW (pro and maybe full?) and you can code it to do whatever you want.  The express VI Write to Measurement File is really only useful in small cases, and anything beyond that should be done with custom code.

Change detection event to read DI and AI

$
0
0

Hello,

 

I am having issues using the DAQmx change detection.

 

I am trying to measure 40 temperatures that are hardware multiplexed to 5 AI. The multiplexer board has about a 2Hz clock that increments a 4-bit ripple counter. The counter output is fed to the 5 multiplexers as the select line. So 000, it outputs temps for 1, 9, 17, and so on. 001 is 2, 10, etc. It counts from 0 to 7 and resets. My program is set up to trigger the rising and falling edge of P0.0 and fire an event that reads P0.0:2 and AI0:4. 

 

The problem I am having is that bit 2 of my digital line is showing to be changing between a rising and falling edge of bit 0. This is causing my count to show something like, 0, 1, 2, 3, 0, 5, 6, 7, 4, 1, 2,... I am using the number to sort the temperature into a size 40 array according to the position of the temp reading. So when it reads 0 and should be 4, it is putting the temperature for position 4 into position 0. I have found a way around this, but I still have an issue if it happens to start right on the spot that it is misread. It will shift all of my temperatures to the wrong position. When I run the program, I can get the error to happen about once for every 10 times I run the program.

 

I have set up an acquisition of just the 3 bits sampling at 25 Hz. The digital graph shows to be exactly as I would expect it, counting from 0 to 7 and resetting like normal. Has anyone seen this type of issue before? I have attached screenshots of the graphs I get when using the Change Detection event and when sampling normally along with the vi using change detection.

 

I am using a PXIe-6365 in a PXIe-1071 chassis and LV17.

 

Thanks,

David

RT data logging and control VI stopped working after upgrading from 2015 to 2017

$
0
0

I have a VI that is deployed onto a cRIO 9118 that is logging data from a few sensors and controlling some outputs. I am running it in scan interface and have it structured properly, with the read in a synchronized loop, and the tdms write in a separate loop. I had this VI running on a computer in labview 2015. We were having troubles with that computer so we moved to another and did a fresh install of 2017. Now on the 2015 computer I was able to log data, and then ftp it to the computer. But now with labview 2017 I get this error when I try to open the file that is created:

 

USI encountered an exception: TDS Exception in Initialize: Tds Error: TdsErrNotTdsFile(-2503):

 

Everything else works fine, and there are no errors coming from the tdms open, write, or close. Just when I try to open them in excel with the tdms importer. I also tried opening them on another machine to see if the tdms importer was corrupted and it gave me the same error. What am I missing? Could something have been corrupted during the install? or am I missing some software on the cRIO?

 

I actually just ran two tests. I created a VI on the computer and on the cRIO and wrote an empty tdms file. the one on the computer worked, and the one on the cRIO gave me that error. My best guess is that I'm missing some software on the cRIO? Any help would be great, thank you!

 

LabVIEW 2015 SP1, cRIO-9075, Restart command doesn't restart, hard reset required.

$
0
0

Hey All,

Early on in discovery here. I compile the RT, and then deploy the compiled startup app to the cRIO successfully. When I do a restart from the utility menu of the project, the cRIO goes away and doesn't come back until a hard reset.

 

Same behavior from within the RT code. The RT code calls the restart vi and the cRIO goes away and doesn't come back until a hard reset.

 

Anyone else have experience with this issue? What is the solution to be able to restart through the project or the RT code.

 

Thanks,

-Drewski


How to build executable file for a project with plugIn subVI?

$
0
0

 

Hi,

 

I want to build an executable file for my project which has plug in sub VIs. I have below error when I run the .exe file.

"

Error Code: 7, Error Message: Open VI Reference in mainGUI.vi<APPEND>
VI Path: <b> ************* </b>

Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.

LabVIEW Real-Time: VIs built into executables cannot be accessed through VI Server calls. Use Source Distributions to dynamically call VIs on Real-Time targets.

"

 

In my mainGUI.vi, I use below method to plugin a sub VI. And I had include the folder PlugInVI while building .exe file. What should I do to solve this error?

 

Thank you!

 

1.jpg

Re: Write to measurement file (.xlsx)- Append new data but in new sheet/table

$
0
0

... and the RGT has some good Examples (I wrote one, myself ...).

 

Bob Schor

Re: Anyone seen error 1508

$
0
0

Well I am saving the class at the end of each iteration, so that is not the problem.

I tried using a .vit instead and that made no difference.

 

Anyone have any other ideas?

"NI microsoft visual C++ 2015 runtime" error during installation from an installer.

$
0
0

I built an installer for my labview program using labview 2017. When I try to use this installer on a window 7 sp1 machine, I ran into this error message:

 

"The "NI Microsoft Visual C++ 2015 Run-Time x86" installation has faild with return code:1.

Continue?

 

This exact installer have worked on another computer with window 7 SP1. So I know the installer works.

I have tried the suggestion from this page:https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7hcSAC, but it didn't work. 

Re: New LabVIEW Signal Processing for Measurement Blog

$
0
0

Very nice!  One minor glitch -- your second article ("How Precise is my Measurement?") says "a famous mathematical theorem (Ref 5) relates that the mean value of an arbitrary signal is usually Gaussian."  Well, there are only 4 References in your list, and I'm not sure if any point the reader to the Central Limit Theorem (which says that for any distribution, the distribution of the mean of a series of measurements tends towards a Normal Distribution).

 

I look forward to reading more Blog posts ...

 

Bob Schor

Viewing all 202002 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>