god bless you , thanks you i will try to learn it then if i cannot understand the program you are giving i will ask again
Re: How to make a triangulation chart or graphic in labview
LabView GCD algorithm
How do you find the greatest common divisor of two numbers in Labview without using the built-in GCD function?
Re: LabVIEW 2018 64 Bit Crash
wrote: wrote: It's puzzling that when you tag "check for updates"during the installation, it doesn't notice there's a new SP... Seems like an update to me...
I thought that SP1 is not an "update" in the conventional sense, but a new version. I.e. you can only get it is you are still on SSP or similar.
That explains it, but often makes little sense from a customer's perspective. Then again, if I install 2018, I don't want an automatic update to 2019. I probably shouldn't expect the installer to 'know' exactly what I want...
Re: LabVIEW GCD algorithm
Hi Saadiq,
why don't you use the well-known Euclidian algorithm?
(Why do you need to use such a large font? And why do you write LabVIEW wrong - two times?)
Re: Waveform Chart Digital Display Blinks 0.00
Shouldn't some relation to the GPU's refresh rate be expected?
Hide the chart, and you'll get a straight line.
Not sure how that's related to the type pf the data. Also, I'd expect Synchronous Display to make a difference, but it doesn't. Nor does the size of the chart. The chart history length does make a difference.
Re: LabVIEW GCD algorithm
And why would you want to do that (, except for doing a homework assignment)?
If you open the GCD VI, you see how it's done. Spoiler alert: once you've seen it, it's going to be hard to can come up with an original idea.
Re: Waterfall display
Looks to me like you want a spectrogram.
Give "STFT Spectrogram PtByPt.vi" a try (use quick drop)...
Re: using data socket with ni opc server exceeding the max connection number
wrote: now we have totally 3200 connections built by data socket open vi, stored in DVR,
Why?
Or rather, why not open one connection, and read\write 3200 times over that connection?
connecting beaglebone with LabVIEW using UDP for Z-Wave
I am trying to connect my Beaglebone Black with LabVIEW by using the UDP Port(sample code in Pic.)
To run the Z/IP Gateway running on Beaglebone, I have written the sample test programm to check the communication between the Client and Gateway. Unfortunately I couldn’t find the right Port of Beaglebone to communicate with programm(I got the message:[ Destination Port unreachable] in wireshark ). Can anyone help me out to connect the Beaglebone with LabVIEW through UDP ?
Best Regards
Raja
Re: using data socket with ni opc server exceeding the max connection number
because we have 3200 items on the opc server
Re: Agilent digitizer U1082A query ID failed -1074003967
Hi rosinefish,
do you use a PXI system at all?
Where did you install that Agilent device? In your Windows computer or in an external (PXI) system?
You don't need VISA for your device.
MAX should not care about the Agilent device as it is no NI DAQ device…
Did you call the Agilent support?
Re: Linx Arduino to Arduino I2C Communication
Looking at the documentation at LabVIEW Maker Hub - I2C Open and similar, I'm not sure the value you want to pass is "9".
Probably, this is the port number (valid for the Arduino code) and instead you want whatever the channel number is instead (perhaps 0).
I also note that you don't have a value connected to the "Bytes to Read" input to the Read VI - I'm not sure what the default is in that case. Perhaps it reads all bytes, but because there's no timing in the loop you're reading values once then empty values a few hundred/thousand times in between. Consider both
a) checking the speed at which the "i" terminal increases, and
b) specifying a number of bytes to read (perhaps a large value will work, if the master also sends a terminating character (probably \n) - if not, set to 1 and see if you see 9, 9, 9, 9, 9, etc. with paired iterations every two seconds).
c) I'd also be curious about the error output from the VI within the loop, but this would probably appear in your final Error Out indicator, provided the following VIs don't drop it somehow.
How to use DLL when building Custom Device into Veristand
I am making a custom device for Veristand by LabVIEW, so as to help Veristand to inform some message though Internet remotely.
I firstly tried the Custom Device teleplate tool , and it seems easy.
In the Network part in the "…RT Driver VI.vi" I use a .dll file(to communicate with Internet) , and that .dll calls a fixed relative folder which contains several .dll files.
It seems a little(maybe, a bit) difficult for me to successfully buid the Custom Device's lib,some settings may not be correctly done when building.
what shall I do ?thank you all ~
Re: Running console application from LV7.1 problems
Hi,
sorry about the code - the last string formatting was put there later and since the code is really complicated I do not wish to “move” the other sections. It took about 3 days to clean it up to this level and I have no further time for that since the functionality is not yet properly working. Will clean up after it is working as intended…
If I use simply the string than a CMD window pops up with the application path as it’s name and it does not work. Meaning it just stays idle with 0% cpu load. After about 30 minutes (way past all timeouts) I close it and it generates a random error number. How it is currently with “cmd /c “%s”): a regular cmd.exe window is popped up and it starts what it should properly (but as mentioned, no text displayed).
As a reply to Bob_Schor: Sadly I can not attach any VIs. As company policy it automatically has company related info hardcoded in it (like my e-mail address) and I can not remove this data. Legally I think it would mean I am leaking software code since it is made on company PC -> It is the property of the company. + I can not create any kind of exe that would have similar calling method that someone could use for testing. At home I have no LV7 + not even the same os.
I attached what I could safely – besides only the system exec.vi is needed with a single string as code (+2 bool constants). It should not take any more time to create it than me giving away the VI and someone adapting it to his / her system…
I tried what you proposed – used dir to go to a network folder. What happens is that the cmd window pops up and instantly closes with return code 0. But this happens if I use no parameter, and also if I use /c or /k. So I am just even more confused.
Tested strings:
cmd /k "dir [path]"
cmd /c "dir [path]"
cmd "dir [path]"
cmd /k dir "[path]"
cmd /c dir "[path]"
cmd dir "[path]"
cmd /c dir [path]
cmd /k dir [path]
cmd dir [path]
Always the same – pops up, disappears, return code 0…
Python Node Function Name
Hello all,
How do I assign function name for python node in LabVIEW?
list = [8,10,1,8519,26,959] result = [] max = [0] # Start from first index j = 0 # Indexing one by one element for i in range(len(list)): #Find greater than elemnet from list while j < (len(list)): if list[j] > (max[0]): del max[0] max.append(list[j]) j += 1 result.append(max[0]) index = list.index(max[0]) # delete an element del list[index] del max[0] max.append(0) j = 0 print("Ascending Order:",result) result.reverse() print("Descending Order:",result)
Re: Waterfall display
I tried the same, but not able to plot properly.
Please find the enclosed VI.
Additional Info: Total 20480 samples, Fs=5000MHz, Measure Frequency = 1000MHz.
Kindly help me.
Regards,
S Nagaraju.
Re: RTM for VI in PPL
tl:r; If you can include the RTMs in your library, this is no problem. If they need to be separately edited (and not part of the lvlibp file), maybe it's tricky/impossible...
If I understand the problem you're trying to solve correctly, then I've attached some simple files showing it working (for LabVIEW 2017 32-bit Windows).
I included my compiled PPL, but of course for a different platform you can recompile.
Basically, I created a library with a single VI containing code much like you show in the image (taking a path input) and then a RunTime Menu with just the About LabVIEW dialog. I made sure to compile it with the default menu set. I then pass a path to the RTM, but in my case, (since the RTM is inside the PPL) the path looks like: <Current VI's Path (next to PPL)>/../MyLib.lvlibp/CustomRTM.rtm
Testing without a path connected shows the default RTM. Once I connect the path, I get the RTM compiled into the PPL.
If you don't want to use RTMs compiled into the PPL, you might have a problem (maybe this is what you wanted to do?) - I wasn't immediately able to use the same path (i.e with the MyLib.lvlibp section removed) to set the path - the indicators show it was found, but the menus didn't change.
Re: LINX + Startup Executable
What are you experiences ikaiser with RaspberryPi/BeagleBone or other boards?
Only Raspberrys, 3B and 3B+. All headless with Raspbian. Mainly for networking stuff, firewall, DNS filter, VPN server, nagios.
Have you developed LabView applications for them?
Never.
What OS did you have on Raspberry? I assume that the standard is Raspbian, but I am wondering whether the LINX target configuration work regardless which OS one has (for example Windows 10 IoT?).
From How does the LINX Target Configuration dialog work?: "The Target Configuration dialog connects to a BeagleBone Black or Raspberry Pi 2/3 via SSH and then runs a series of commands just as you might do through a SSH terminal." Sounds like this works only on Linux-based OS's. (I know that newer versions of Windows 10 include an SSH server, but other information shows it will not work)
From How do I start/stop the LabVIEW run-time daemon on a BBB/RPi2?: "[...] If you SSH into the target you can also run sudo systemctl stop labview.service to stop the LabVIEW run-time and sudo systemctl start labview.service to start the LabVIEW run-time." These commands are clearly Linux, not Windows.
Also What is a chroot? Why does LabVIEW run within a chroot instead of as a normal Linux application on the BBB/RPi2?: "The LabVIEW run-time engine is compiled with options that make it incompatible with the system libraries that are included in the default operating system images used with the BBB and RPi2/3, so the chroot allows us to include a set of system libraries for LabVIEW to use that are compiled with options that are compatible." Chroot is Linux as well, definitely no Windows-compatible LabVIEW executables here.
Re: Running console application from LV7.1 problems
And what would be the path you are trying to use? [path] isn't VERY helpful in this context.
As you are almost certainly running Windows 10, and at that almost certainly the 64-bit variant of Windows you have something called file system redirection when running a 32-bit process on such a system. Starting cmd.exe from a 32-bit process will start the 32-bit variant of cmd.exe from C:\Windows\SysWOW64. This process as a 32-bit process will be subject to the same windows files system redirection, so any path that references a so called 64-bit location such as "C:\Program Files\..." will be "helpfully" redirected by the Windows kernel to its 32-bit counterpart "C:\Program Files (x86)\..."
E voila, trying to dir for instance "C:\Program Files\My Super App" will instead dir "C:\Program Files (x86)\My Super App", which is likely to not exist at all and even if it does it probably is not what you want anyways.
There are Windows API calls to temporarely disable file system redirection for a process but using them can throw a wrench in other things inside that process that depend on the file system redirection to be done the way it is normally done.
3D-Graphs don't work on current target cRIO-9063
Hi,
i'm new to Labview and trying to find a solution for this.
I have the problem that my 3d-graphs don't work when i use them on my current target.
Setup: Professinonal Development system; NI cRIO-9063; labview 32 bit.
When i use the 3d-graphs in a blank vi then everything works fine. but if i open the same vi on my current target (cRIO- 9063) then the graph is broken. Or if a open a new vi in my current target then the option to insert a 3d-graph isnt even there.
When i add a vi with a 3d-graph to my project with the target cRIO-9063, then in dependices i see several 3d files. In the Error list some of these files show up with errors like "Wire:Type not supported in current Target".
My Question is: Does cRIO- 9063 not support 3d-graphs (couldn't find anything to that on the internet) or didnt i take a necessary step so that the graphs work on that target.
Thank you for your help!