TDMS file isn't created during the run (saving acquired data)

June 12, 2018, 5:29 am

≫ Next: How to Draw Bounding box onto the detected cells

≪ Previous: Data Processing- Filter data in tdms using Labview

$

0

0

Hello, I am quite new in Labview and need some help in saving acquired data to TDMS file format. So I have FPGA project and want to save data to TDMS file (you can see VI for saving attached). I created VI for saving by the way written in the NI tutorial for data logging http://www.ni.com/tutorial/11198/en/. 

But the TDMS file isn't created after the run. All VIs projects are running and there is no any error in VIs, so it seems everything is ok, besides there is no TDMS file. I tried different locations but It did not help. Could someone help me with this issue?

---

How to Draw Bounding box onto the detected cells

June 12, 2018, 6:07 am

≫ Next: fixed rate acquisiton decimated to different rates and saved to tdms with correct timing

≪ Previous: TDMS file isn't created during the run (saving acquired data)

$

0

0

Hello,

 

 

I working on project where I have to find the cells and draw the bounding box onto the detected cells .

 

For the same I made a Vi which can detect the cells, but in next step I do not know how to draw the bounding box onto the detected cells, while I have pixel values(React(Left,top,right,bottom) for each cells to create a bounding box.

 

I have attached the Vi better understanding.

 

I have tried function overlay and IMAQ Draw, but not getting the result.

Should I use for loop ?

 

fixed rate acquisiton decimated to different rates and saved to tdms with correct timing

June 12, 2018, 6:32 am

≫ Next: Can't use PACE 5000 drivers

≪ Previous: How to Draw Bounding box onto the detected cells

$

0

0

I am attaching a vi that I made to try and show what it is I want to do. The data will be captured at 10K Hz and 2000 samples. I want different rates used to decimate the data and then get proper timing stored to tdms. I seem to be able to get the data decimated properly as far as sample size. I just can't get the data into tdms so it show the proper number of samples and proper time stamps.

Can't use PACE 5000 drivers

June 12, 2018, 6:37 am

≫ Next: reading from file

≪ Previous: fixed rate acquisiton decimated to different rates and saved to tdms with correct timing

$

0

0

Hi.

I'm trying to use labview to control my GE PACE 5000 using the drivers given there. But i can't even run the exemples. All i get is timeout errors or insufficient locations.

I plugged it with USB and installed VISA beforehand.

I'm new to labview, so i fear i'm missing something really basic but important.

Thanks for the help

reading from file

June 12, 2018, 8:58 am

≫ Next: Debugging with DSA8300 Library

≪ Previous: Can't use PACE 5000 drivers

$

0

0

Trying to search string in the file by read delimited spreadsheet, but result is not accurate.

for example,

i need to find the operator name so im finding the index of operator name.

Debugging with DSA8300 Library

June 12, 2018, 11:42 am

≫ Next: Data Monitoring

≪ Previous: reading from file

$

0

0

Hello,

 

Firstly, I am very new to LabView and somewhat unfamiliar with the way it calls libraries, especially utilizing "Non-NI Supported/Offical Libraries".

In my case, I am using the Tektronix DSA8300 Library and I believe I am having issues with the way my VI is referencing the library I am using.

This program is working on another machine and I am only adding some minor features/edits on my own system. Is this an issue where I am not importing or using the directory correctly? The errors seems to show that it isn't recognizing all of the files that it is being referenced to which gave me the impression that it's not reading the library at all or the files that are connected to the VI aren't being referenced. I was told that I needed to install MAX in which I have.

 

LabVIEW 8.6.1

DAQmx 18.0

Tektronix DSA8300

 

The above are what I have installed, I am not sure if it is an issue with the block diagram that I am not using the software correctly or not.

Please let me know if there's any additional information I can provide.

 

Error Messages

The lines outside of this structure seem to work fine...

Data Monitoring

June 12, 2018, 12:05 pm

≫ Next: Backwards compatibility with .lvlibp files from Labview 2011 to Labview 2017

≪ Previous: Debugging with DSA8300 Library

$

0

0

Hi , Im using kintex 7 FlexRio with 6585B adapter .

Im loading binary files to the DRAM , and from the DRAM im sending the data using a unique protocol (IP-Core). Before the data sent outside , another IP core Calculating CRC32 , it conjugated to the original data , and then sent out.

Is there a method/option to monitor or write the data(includes the CRC32) to a file for debugging ?

Backwards compatibility with .lvlibp files from Labview 2011 to Labview 2017

June 12, 2018, 12:31 pm

≫ Next: Using the Gaussian surface with offset fit.vi to detect focal drift in ultrafast laser microscope

≪ Previous: Data Monitoring

$

0

0

Years ago a fully functional code for our control system was created using Labview 2011, and that code is still functional to this day, however, it is running on a very old computer and so we attempted to transfer it to a properly supported computer which is now running Labview 2017, almost everything transferred over nicely except a .lvlibp file with a few subVIs and CTLs. I have tried to go into Build specifications and rebuild it so that it is accessible by later versions but the option seems to not be available in the 2011 version. I'm very very new to Labview and am not the original creator of the system therefore i cannot rebuild the library from scratch since i do not know the purpose of the library. Is there anyway to unpack the library so that I can retrieve the files so that I can pull them onto the new system and pack them again in a new packed library that will be compatible with both the old and the new systems?

---

Using the Gaussian surface with offset fit.vi to detect focal drift in ultrafast laser microscope

June 12, 2018, 12:32 pm

≫ Next: Combining Ultrasonic Sensor and Motors MyRio

≪ Previous: Backwards compatibility with .lvlibp files from Labview 2011 to Labview 2017

$

0

0

I am looking for a way to quickly check for focal drift in my laser microscope using calibration beads. I ran across the "Gaussian surface with offset fit.vi" in the example folder and I would love to edit it to where I can upload my 2D array data of my bead at the desired focal position, tell the code to hold this plot, then upload the new 2D array of the bead into the plot to check for any differences indicating that the bead has drifted. 

 

Right now, I am struggling to see where I can edit the code to upload my data in the block diagram. I know how to add the path to my data and extract the file and inputs I need; I'm just not sure if I need to modify the 2D gauss model function on the block diagram to add my data.

If anyone has any suggestions for editing this code or better ideas for quickly checking focal drift using .dat file or .tif files, I'm all ears (and eyes in this case)!

Combining Ultrasonic Sensor and Motors MyRio

June 12, 2018, 12:32 pm

≫ Next: Problem in installing Embedded Module for ARM Microcontroller

≪ Previous: Using the Gaussian surface with offset fit.vi to detect focal drift in ultrafast laser microscope

$

0

0

Hello,

I'm apart of a team that's trying to develop an autonomous vehicle. We've acquired a HC-SR04 ultrasonic sensor to detect objects in our vehicle's path. To test our codes we've been running the VI on a Tetrix rover along with a MyRio. Currently we have a VI for the ultrasonic sensor that triggers a digital output if an object is within roughly 9 inches. Additionally we've written a VI that can be executed to make the rover avoid an object by going around it.  What we are having trouble with is integrating the ultrasonic sensor and motors. What we want to do is have the sensor trigger the motors if there's an object within the range previously mentioned. We've tried putting in the motor VI into the sensor VI but it'll run the motors code continuously without going back to the sensor. We've tried a state machine, having the sensor VI call the motor VI, having both VI's running in separate while loops but nothing has worked. Is there anything y'all could suggest us doing to get the programs to work?

 

Ideally we would like for the programs to be separate and having one VI call the other. 

 

We've attached screenshots and the files as well for anyone who is willing to help us.

 

Motor VIUltrasonic Sensor VI

 

Thank you,

Team EOS

Problem in installing Embedded Module for ARM Microcontroller

June 12, 2018, 1:22 pm

≫ Next: CLAD Preparation guide questions

≪ Previous: Combining Ultrasonic Sensor and Motors MyRio

$

0

0

I had installed Embedded Module for ARM Microcontroller on two computers with no problem in the past but today I was faced with a new problem while installing this module on a new computer. The image is shown below. 

 

How can I fix this problem? I should mention that this error happens at the first step of installing when 0 percent of installing is done.

 

Another matter I want to know is that, is there anyway instead of using  Keil ULINK2 USB-JTAG adaptor in order to use this LabVIEW module for an ARM as the target or not? For example, using USB port on the board?

 

Thank you.

CLAD Preparation guide questions

June 12, 2018, 2:20 pm

≫ Next: Save Output from "niUSRP Fetch RX Data (poly).vi"

≪ Previous: Problem in installing Embedded Module for ARM Microcontroller

$

0

0

   

Hi

I am preparing fro the CLAD and using simulated DAQ 9178. The same VI below producing me 19000 row but the answer book says should be 2 rows 5 column. Please give some advice.

Save Output from "niUSRP Fetch RX Data (poly).vi"

June 12, 2018, 3:07 pm

≫ Next: DAQmx acquisition and waveform generation in same loop

≪ Previous: CLAD Preparation guide questions

$

0

0

Hello all,

 

I'm trying to save data received by my USRP 2955 device for offline processing. The trouble is that the blocks I added to handle the file i/o portion cause overflow errors for the fetch rx data block. 

 

If we were to look at the example niUSRP EX Rx Multiple Inputs (Single Device, Multi Channel).vi, I want to save the output of the fetch rx data block, which is essentially shown in the "IQ Graph."

 

Attached is my adjustments to niUSRP EX Rx Multiple Inputs (Single Device, Multi Channel).vi with some blocks in the while loop to handle file i/o. Take note that the default values on the front panel have been changed to match my application.

 

Thank you for you assistance!

DAQmx acquisition and waveform generation in same loop

June 12, 2018, 4:21 pm

≫ Next: LabVIEW FPGA I/O Configuration

≪ Previous: Save Output from "niUSRP Fetch RX Data (poly).vi"

$

0

0

Hello,

 

In the attached VI I'm trying to write a program that moves two sliders. Slider 1 is controlled by force output and slider 2 is controlled by a sine wave oscillating at a set frequency of 0.2Hz. The task is a force tracking task where the user has to modulate force output to keep the object above the water. 

 

The problem I'm having has to do with timing. If I include a wait ms function in my loop to acquire data at 100 Hz, my target slider oscillates at the correct frequency, however, data is not acquired using daqmx read. I understand that a wait ms function should not be used in a while loop with dawmx read. Can anyone help be acquire the target force sine wave (slider 2) and force output (slider 1) at 100 Hz?

 

Regards,

Daniel

LabVIEW FPGA I/O Configuration

June 12, 2018, 4:59 pm

≫ Next: Abort Button Not Working

≪ Previous: DAQmx acquisition and waveform generation in same loop

$

0

0

Hello all!

 

I only recently began using LabVIEW and the FPGA module is confusing me a lot. I am trying to accomplish something as simple as turning an LED on and off at a controlled time. I have the while loop delayed with a count, but the board I am using, the USB-7845R connected to a board of inputs, uses I/O pins rather than DI or DO pins like in the tutorials. 

 

I really would appreciate if someone could point me in the direction of how to configure my DIO23 pin. I want to be able to read and write values to the pin, which is controlled an LED (1 = On, 0 = Off).

 

I have attached what little I have as a screenshot - I apologize that it is not much, but I am really struggling on it. Thank you in advance for the help.

 

The Arduino code would look something like this -

 

pinMode(DIO23, OUTPUT);

 

void loop () {

digitalWrite(DIO23, LOW);

while(1){

if(digitalRead(DIO23) == LOW){

digitalWrite(DIO23, HIGH);}

else{

digitalWrite(DIO23,LOW);}

delay(1000)

}}

 

---

Abort Button Not Working

June 12, 2018, 5:28 pm

≫ Next: Typedef TAB control - consistent behaviour?

≪ Previous: LabVIEW FPGA I/O Configuration

$

0

0

Hi All, 

I have a LabVIEW VI that used to work well, and it seems to have stopped working even though I didn't make any changes that I know of.  Now when I hit the arrow to run the program, the program appears to start and arrow says that the program is running, but nothing happens in the program at all.  If I press the abort (stop sign on the top bar) nothing happens, and the program appears to continue running.  The STOP button in the VI also does not stop the program.  After I close the LabVIEW window, I get a little LabVIEW box that says "Resetting VI" and I it won't go away until I open the Task Manager and kill LabVIEW.  

 

Can someone tell me what is going on here?

Typedef TAB control - consistent behaviour?

June 12, 2018, 9:48 pm

≫ Next: Acquiring AI in PCI 6143

≪ Previous: Abort Button Not Working

$

0

0

Hello,

 

I wonder if this is an expected thing or not. Scenario: open a VI, go to the front panel. Place a TAB control into it. Make it a type definition. This is a common scenario, because if later you change pages, then you do not need to remake your Tab constants in your BD.

Ok, now place an object into your TAB control. Like a numeric or boolean, etc. Right click, and select "Change to array". This is a no op! No warning, no msg, nothing. If you make an array outside, of course it works, you can pull the array into the Tab control page.

 

Is this expected behaviour? For example, when we deal with a type definition cluster, the deal is simple: you have to open the type definition, and edit elements there. But a TAB control is a different thing. I would expect that we can change between element/array types right in the Tab page...

Tested in LV2017 SP1, LV2018.

Acquiring AI in PCI 6143

June 13, 2018, 12:01 am

≫ Next: Axis Issues in labview

≪ Previous: Typedef TAB control - consistent behaviour?

$

0

0

Hi

 

I am trying to acquire constant Analog signal of 65mV from a sensor to computer through PCI-6143 and for that used a DAQmx.

However the signal is constant but during acquisition it seems its oscillate, Here picture attached. How i can acquire constant signal without averaging.

I have tried, sample on demand,continuous sample and N samples mode but in every condition signal is varying.

Need suggestion to resolve error, without averaging my signal.

 

thanks in advanced

 

 

Axis Issues in labview

June 13, 2018, 12:02 am

≫ Next: NI GDS difference of class provider

≪ Previous: Acquiring AI in PCI 6143

$

0

0

I have a real time data. I read it in Labview and did a FFT on it which was then connected to a waveform graph. Now I tried plotting it and I got the expected graph shape. 

I tried doing the same thing with "Origin Lab" software and it also gave me the same graph(same in shape). However, the X-axis units were completely different for both. In origin I get the peak frequency as 550 Hz where as Labview gives me something like 4 or 5 units in the x axis. I got to know that the Origin result is right and the labview result is wrong. Only if I change the multiplier value in the graph properties in Labview, I get the required result.Why is that? How do I correct this error? I want to correct this error as it is much easier to collect and store data using Labview. 

I have attached my VI here(It might look messy,but you only need to check two graphs: Fast  Fourier Transform( Scaled) and Fast  Fourier Transform(Unscaled).

Also, I have attached the Origin Lab graph.

 

 

NI GDS difference of class provider

June 13, 2018, 12:37 am

≫ Next: PXI compatible with Labview 2018?

≪ Previous: Axis Issues in labview

$

0

0

Hi,

 

I'm using NI-GDS and I'm wondering why I can't find some information about the difference between the class provider in the GOOP options. (EndevoGOOP300, EndevoGOOP400, LabVIEW GOOP Native)

Can someone give me an advise, please?

 

Regards

kaba