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

Re: C# and LabView .Net Interop DLL: Cannot pass a GCHandle across AppDomains and System.Reflection.TargetException when calling into LabView DLL

$
0
0

No solution. We ended up using wholly C#. Think the problem was because it is to do with hardware created in CLR and passing to LVRT and LV probably has an issue with that. Hence the problem. If image capturing is wholly in C# then image data is just passed to LV as simple types then you may get that to work. However, this does not guarantee whether you will work-around it today and hit another wall a month later so using hybrid solutions are probably bad ideas unless you are doing something very specific and short lived tasks.

 

Hope it helps.


FM radio using NI USRP 2901 problem in sound file read

$
0
0

hi every one, i have written a program for FM TX in labview block diagram. but this program throws a error of 4810. which i tried in many sound file formats such as wav, mp3, amr etc, 

 hardware is usrp 2901

 

here i attach a image for it.

 

kindly reply

Re: problem in sound file read

$
0
0

Hi Kashizudoto,

 

but this program throws a error of 4810.

This error has an explanation text: "Cannot recognize sound format".

 

which i tried in many sound file formats such as wav, mp3, amr etc, 

Well, the function you use only supports WAV as is written in the help for this function.

Additionally not all different kind of encodings in the WAV file are supported - as is also written in the LabVIEW help!

 

Can you attach your WAV file here (atleast a smaller one, packed in a ZIP file)?

Re: Not able to connect USB camera with MyRIo

$
0
0

Hello ,

Thank for pointing out issues. Will you please suggest a list of USB camera that is compatible with NI MyRio or link where I can find the list of USB cameras Compatible with Device. 

Thanking you for your precious time.

 

Regards, 

Kumar K 

Re: Not able to connect USB camera with MyRIo

$
0
0

rolfk wrote:

It most likely means that your USB camera doesn't fully comply to the USB Video Class specification. The Linux driver on the myRIO is a standard driver from the Linux kernel project and does implement a certain subset of functions from the USB Video Class specifications. Your device may use a non standard function somewhere or not implement a specific feature completely correct. Or the Linux kernel driver has a bug that doesn't fully work with your camera.

NI is very unlikely to fix this driver as it is not their product and your best bet is to try with a different USB camera.



Hello ,

Thank for pointing out issues. Will you please suggest a list of USB camera that is compatible with NI MyRio or link where I can find the list of USB cameras Compatible with Device. 

Thanking you for your precious time.

 

Regards, 

Kumar K 

Re: communication between the host VI and the FPGA VI

$
0
0

thank you very much  

Re: UDP open error 54 issue

$
0
0

Hi Romain,

 

which ports do you try to use?

 

UDPOpen only requires a port number. The remote IP/port is only needed for UDPSend.

Did you use the UDP Sender/Receiver example VIs?

Re: 'Write to Text File Function' Data Error

$
0
0

If you are logging binary data, then you need to use Write To Binary File.  What is likely happening is the "Convert End Of Line" is changing your data from 0x0A to 0x0D0A.  You can turn that off by right-clicking on the Write To Text File.


Start deployed cRIO application from PC

$
0
0

Hi,

 

Do I have any possbility to (re)start a deployed RT application from PC?

Use case: deploy cRIO app --> start PC app --> check if cRIO app is running --> if not start running of cRIO app

 

Thank,

 

Balint

 

Re: communication between the host VI and the FPGA VI

Re: Start deployed cRIO application from PC

$
0
0

RT systems are meant to be headless.  This means they start their application as soon as the boot process is complete.  You should have a state machine for the communications to detect if a host application is trying to talk and potentially run the main code then.

Re: Update xcontrols in hidden fronts panels

$
0
0

Thanks for your answer,

 

I solve my issue. The problem is the way i updated my xcontrols. I used a reference and a property node to change the value because I wanted to have a clear diagram.By using local variable, I dont see any perfomance's issues.

 

On my front panel there are 16 xcontrols and I managed my xcontrols's cluster (the data in) in an array. For me the best way to code this was to use an array of reference so I would be able to select easily the xcontrols I want.

 

I think changing the value by property node add every data in a kind of stack, and every data in will be treated and showed, thats why it seems to slow. Local variables seems to only update the data to be showed.

 

PS : In my case, Defer.FP.Update doesn't help.

Re: Bit packing and unpacking

$
0
0

@Rolfk:

Thanks. I'm not sure if it's intuition or that I actually benchmarked it years ago.

 

Of course, if you're going to do a lot of this (bit-packing\unpacking), it makes sense to make a small set of VI's to do this. By making the VI's inlined, performance should be high.

Re: countdown alarm

$
0
0

Thanks for replying GerdW, 

 

i already did, but still when the counter finish, and the next state is start again. 

 

the counter still decreasing. so the time will be (-1:59:59) i want to make it (00:00:00) then count second time and so on. 

 

 

thanks 

Re: Start deployed cRIO application from PC


Re: Bit packing and unpacking

$
0
0

billko wrote:

I do it because it most visually represents what is being done with no ambiguity whatsoever.


When I am doing this bit packing, I tend to have my numerics displayed in hex and/or binary and show all of the preceding zeros as well.  For example, an U32 I will use %08x for the format.  This QuickDrop shortcut helps a lot: Format Numeric.vi.  And also make sure the radix is visible when you do this (I have not had the time yet to add that to my plugin).

Re: PROPERTY NODE PROBLEM

$
0
0

Automation Refnum.png

After that right click on it and select Select ActiveX Class->Browse...

Re: Bit packing and unpacking

$
0
0

rolfk wrote:

Arrays of booleans are definitely suboptimal even on other platforms than FPGA. There is a small chance that the FPGA platform does some specific optimization under the hood to convert boolean arrays of limited size into integers anyways as that is more efficient to implement into hardware but on non-FPGA platforms each boolean always uses up an entire byte and so an array of 32 booleans uses 32 bytes, needs to be dynamically allocated and deallocated and incurs extra overhead when referencing the bits. If you use integers with boolean arithmetic instead you keep the code the same on all LabVIEW platforms and also get the most performant solution on each platform too!


I am almost certain that the boolean array in an FPGA compiles down to individual lines and gates.  So a boolean array with 8 items will use 8 lines/gates.  So it should come out to the same fabric size as the U8.  Though, I am willing to bet the U8 can use the DSPs instead of LUTs and other fabric.  So that is another risk on the FPGA side.

Re: UDP open error 54 issue

$
0
0

UDPopen.PNG

I have already looked for the example VIs

I am using the port 6000 as you can see.

 

Best regards,

Romain Legrand

 

Re: PROPERTY NODE PROBLEM

$
0
0

i thank you very much, you just safed my life

Viewing all 203171 articles
Browse latest View live


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