Quantcast
Channel: LabVIEW topics
Viewing all 66899 articles
Browse latest View live

NXG 2.0 Installation

$
0
0

When istalling NXG 2.0 with the NI Package Manager I get following window:

 

image.png

Invalid checksum for the ni-pxiplatformservices-17.5.1-released.nipkg.

 

Try again doesn't work .....

 

Help, BR ws.


Automated Maze Solver - Real Time Path Planning Algorithm

$
0
0

Hi, I am planning to create an automated maze solver, (like the one shown below), using 2 servos and a webcam on the top. I am wondering if somebody could guide me a little bit about the NI module I need to use, the way to approach this problem and how to create an algorithm able to find the shortest path and somehow avoid the inner walls.

 

Thanks in advance

 

 

Instrument LabWindows/CVI Driver Import Wizard fail to convert Init, Init With Options and Close IVI driver functions

$
0
0

I have an IVI driver build with Nimbus tool. The IVI driver is an IVI-COM driver with an IVI-C wrapper on top of IVI-COM. After installation the driver install .fp,.h, .dll files under IVI Foundations Drivers folder. I run the Import Wizard Too and this creates LabVIEW wrappers of IVI-C interface under instr.lib folder of LabVIEW 2012. The Import Wizard Tool version is 2.2 and is part of LabVIEW 2012 => Tools => Instrumentation => Import LabWindows/CVI Instrument Driver.
All IVI driver basic functions are converted OK with few VI exceptions.
The conversion tool spit out a report in html format that shows that IVI basic functions "Init", "Init With Options", "Close" and 2 other functions fail to convert these VIs.
The conversion report gives few possible reasons for this failure .

 

Driver VI Not Executable
The following instrument driver VI(s) are not executable. This might indicate one of the following issues:
(a) There is a problem with the instrument driver DLL, or the function is not exported by the DLL.
(b) All necessary support files or DLLs are not found.
(c) The first parameter of the function is not a Driver Handle.
(d) The LabVIEW Call Library Node is not correctly linked to the appropriate function in the DLL.
(e) The function is not consistent with VXIpnp and IVI specifications. 
Open and review each of these VI(s) for errors.
Some non-executable VIs can be removed from the LabVIEW interface. Consider the relevance of the VI to the LabVIEW user and determine if you can safely remove the VI from the API.

    viMAP200 TFX Initialize With Options.vi
    viMAP200 TFX Initialize.vi
    viMAP200 TFX Close.vi
    viMAP200 TFX Get Next Coercion Record.vi
    viMAP200 TFX Get Next Interchange Warning.vi

 

In my case the error in these VI seems to be the error explained at point d) above

If I open these failed VI I may see that they use a generic function that is not the IVI driver expected function. The generic function that these failed VI connect to has nothing to do with the underlying IVI functions but connect to a generic function called "funcName" with the prototype shown below. 

int32_t funcName(uint32_t instrument handle, int32_t measurement function, double range, double resolution (absolute));

 

Did anyone had this kind of experience with Import LanWindows/CVI Import tool in failing to get conversion of IVI-C funnctions Init, Init With Options and Close functions into valid VIs?

 

 

Labview DLL call expected performace

$
0
0

Hi all

 

I'm about to create a new LV EXE application with pluggable modules.

For the sake of future compatibility and expandability, in this phase I'm planning to deploy plug-ins in form of DLL files, even if they are actually coded in LV.

Given all of the above, I'm experimenting a bit on the expected performance of such an arichitecture.

The test application is made of the following components:

- one DLL that incorporates the consumer, the consumer launcher, the exit command enqueuer, the data enqueuer, the consumer VI ref getter;consumer.png

 

launcher.png

exitenqueue.png

 DataEnqueuer.png

 VIrefGetter.png

 

 

 

 

 

 

 

- one EXE with a simple producer.
EXEproducer.png

 

 

 

With this stub, running on a i7 cpu, I obtained about 30 to 50 calls per millisecond with a 30% processor load.

Since the final work should accomodate a maximum of 10 plug-ins with a now difficult to estimate data exchange rate and at least one inbound and one outbound queue each, I'm about concerned of the final expected performance.

 

Do you think that the numbers I'm obtaining are something of realistic? Do you judge my code enough efficient or flawed in some aspect?

 

Thank you for your opinion.

 

Best

 

Raf

 

anyone share with me a VI with Implementing 2x1 MISO system with LabVIEW and NI USRP 2921??

$
0
0

anyone share with me a VI with Implementing 2x1 MISO system with labview and NI USRP 2921??

project ideas using MyRIo

$
0
0

I am interested in working with LabVIEW MyRIO.Can anyone suggest me some innovative  project ideas?

Rules for using Modern/Classic/Silver controls

$
0
0

I was talking with a friend about LabVIEW and when we use different control types in our vi's

 

Generally, we agree that an end user should see modern/silver controls while base level vi's are best represented with the classic controls. (except cases where you want to make a cluster truly transparent) 

 

However, I was curious if there are any official guidelines from LabVIEW or daily nuggets that have more experience and reasoning than "I feel like..."

 

When do you use the various control styles and why ?

Uninstalling NXG 2.0

$
0
0

I should have known better, but curious to see what the NXG 2.0 had to offer, I installed it, together with the Vision Module (or whatever it is called) because I use its little brother with LV OG 2017 (oldgen).

Short story long, I tried twice to create a new VI and drop a Graph on a blank FP and NXG went down in a crash each time. I promptly uninstalled all I could from the NXG stuff but apparently didn't do that fast enough...

Now when I try to use my 2017 code including Vision Module VIs (2017), things are broken because, says the Error window:

 

The Vision Development Module library is expired or invalidly licensed on this computer. To purchase this product, contact National Instruments. If you have already purchased this product, select the Help >> Activate LabVIEW Components to activate this product.

 

Obviously, following this advice leads nowhere and I have shot an email to NI support for explanations.

 

Caveat emptor...

 

PS: and yes, there is something new in NXG 2.0: a "Split" view of the BD and FP. Oh well...

 


Get Project Items in executable

$
0
0

I have built a VI which looks through all of the project items to find libraries which contain a control called parameters.ctl and output an array of references to these controls. This works correctly in the development environment however when building to an executable the array of projects out of the application.projects property node is empty. Is there a way to get a reference to all project items in an executable?

 

 

How to write array elements in a file n times.

$
0
0

Hi, i have an array of 8 elements and i want to write this array n-times in a file (i.e 10000 identical copies of the array in a file) .. how to do it ?

 

tnx, Massimo.

Writing multiple waveforms to a single Excel file

$
0
0

I'm using LV17, a cDAQ-9174, and an NI9219.

 

I am collecting analog voltage data from three sensors...linear position, angular position, and an accelerometer. I need to send the converted data to excel. With one sensor it's no big deal, Export Waveform to Spreadsheet VI. The problem comes in when I'm trying to send the data from all 3 sensors to Excel.

 

What do I need to fix / change in this VI?

 

Thanks

Control Voltage of HP 661C DC Power Supply / 34401A Mutlimeter with LabView 8.5 conncted using GPIB

$
0
0

Hello Everyone,

 

I have been reading many forums and pages regarding Instrument Control Using LabVIEW. My system is old and does not have an Internet Connection. ( Windows XP) . The image shows the softwares installed on my computer.  

 

 

Softwares i have on my computerSoftwares i have on my computer 

I want to control HP 6611c DC power Supply and HP 34401A multimeter using LabVIEW 8.5. I have connected both these instruments to my computer using GPIB. I have problems in detecting these instruments on my system too. Kindly Guide me in steps to continue in my attempt to learn Instrument control using LabVIEW. Any help is appreciated.

 

Please help me, convert from 2016 to 2015

$
0
0
Moved to Version Conversion board

How does it iteration parallelism works?

$
0
0

Hi all,

         How iteration parallelism it's works?

         Can anyone give brief explanation about it?

         Q1.pngQ2.pngQ3.png

USRP B210 with LABview FPGA

$
0
0

Hello,

I need your help!!!

Is it possible to emulate a wireless channel using Labview FPGA, on USRPB 210 ?

 

Thank you for your response!

 

B.Regards,

 


Writing shared variable (Modbus), Error code : -1967353900

$
0
0

Hi all,

 

I am currently editing a LabVIEW program to help run an experiment for a Master thesis. I was ready to build the program into an .exe but after installation of some additional software I started getting the following error code when trying to write some shared variables: 

 

-1967353900
Shared Variable in valves-module.vi<APPEND>
This error or warning occurred while writing the following Shared Variable:
\\My Computer\Modbus-lib\000033
\\172.20.9.169\Modbus-lib\000033
Valve seq module

 

Here is the section of the block flow diagram where the error occurs:error.JPG

 

 

I was wondering if anyone had any ideas what the error code relates to? Perhaps I am still missing some software?

 

Angus

 

 

 

 

 

 

 

Using LabVIEW to control Lakeshore 350 Temperature Controller - Set Point and Ramp

$
0
0

 Hello 

I am using LabVIEW (2016) to control Lakeshore 350 with the software that available on NI site, to do temperature dependence of PL spectra. 

Most of the VIs works, but the "Configure Setpoint and Ramp" VI don't works (error 1073807339).  

I checked that the device is on remote mode. 

I can turn the heater on and off but can't control the Ramp and the Set point . 

Do you have any idea what could be the problem?

thanks 

Itay   

LabVIEW minimum version requirement in NI Package Manager

$
0
0

I'm exploring the new NI Package Manager and I couldn't figure out a very simple thing: how can I specify the minimum LabVIEW version require to run my package? I know that there is a "Depends:" section in the "controls" file, but I could not find the package identifier for LabVIEW 2016 32-bit...

 

In principle, I should be able to see it by hovering on the NI LabVIEW 2016 (32-bit) entry in the Package Manager, but all I get is a weird hex identifier like (I'm just making the numbers up) 3e675c-21f928878-4a76447...

Regarding simultaneous sampling rate

$
0
0

Hie I have a 4300 module in which simultaneous sampling rate is available.But I am unable to read different sampling rate for different channels.If i give different sampling rate for different channels it is taking last channel sampling rate for all the channels.Is there any solution(or any example programs) for different sampling rate for different channels for 4300 Daq. 

      

"Import LabWindows/CVI Instrument Driver" option is missing in my LabVIEW

$
0
0

Hello,

 

I am using LabVIEW 2017 and I need to use an old instrument driver for LabWindows/CVI. The driver is for power supply Digistant 6706.

I read here that I have to use Tools>>Instrumentation>>Import LabWindows/CVI Instrument Driver, but this option is missing in my LabView.

I have checked also LabVIEW 2014 and this option is missing there too.

 

Do somebody has an idea how to use this driver in LabVIEW?

 

Thank you!

Viewing all 66899 articles
Browse latest View live


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