CompactRIO and LabWindows

Similar Questions

• How can I take pictures with a regular usb camera and labwindows

  How can I take pictures with a regular usb camera and labwindows

  Hello

  What do you mean "ordinary USB camera? It's a Vision camera with a communication based on the API Vision camera or a 3rd party (such as a webcam)?

  In the latter case, you may need to consult the documentation of the manufacturer, it should be sent with her library (C DLL, ActiveX automation, .NET assembly) with functions to communicate with drivers.

  Best regards

• CompactRIO and 9237 start-up

  Hello

  I'm new in Labview. I have a 9076 Compactrio, connected with a 9237 module and a set of scales. I have already connected with success (NI 9237 Getting Started.vi is connected and functional without problem), but when I try to compile the example: .vi NI 9237 Getting Started (host) some son display the error. I have attached the image.

  How can I solved it, in order to compile the example (host)?

  Thanks in advance.

  You must configure the FPGA open reference to point to the bitfile you generated for the FPGA.

• Opal kelly builders and LabWindows/CVI

  Hello, all.

  I try to get a Council Opal Kelly XEM3005 running with LabWindows/CVI 8.5.

  I have been in touch with Tech Suppt of OK and overthrew the original questions of type 'bool '.  After (at the recommendation of OK) with "char" types, I can now include the headers without errors.

  There are, however, a new problem:

  When I call the constructor function, which should return a pointer to a type of "okFrontPanel_HANDLE", I get an error for a prototype missing for initialization.

  Dredged in the .c (pp) file I found the following:

  //----------------------------

  Hi tomii,.

  Looks like you posted another very similar thread on the compilation of mistakes with the DLL of your Opal Kelly here. I follow upward in this thread to help get traction with those questions.

• JNI and Labwindows/CVI linking problem

  I am trying to connect to the server in Java through LAbwindows CVI DataSocket.

  I am able to create a dll. Everything works fine with no error in compilation or execution, but when I run the DS_OpenEx cannot return a native class.

  If anyone can help me with the problem.

  Thank you

  Hello

  Could you better clarify the implementation that works properly and implementation that does not work properly?

  1 are you connected to the DataSocket with Java source code and you are trying to communicate through this source of Java through LabWindows/CVI?

  2 are. what environment you able to successfully create a DLL?

  3. can indicate you what environment survey code error and what this code?

  ADri - K

• Windows 7 Starter Edition and LabWindows/CVI

  Hello

  I have two questions/problems with an application written with CVI 9.0.1 and CVI 2009 respectively Windows Vista professional.

  First if I have a distribution of my software package (or a version of a sample distribution package) and you want to install it on a netbook with Windows 7 Starter Edition Setup displays the following error message:

  "This product does not support Windows Starter Edition."

  Is this just a restriction of the installation program, or CVI will never support the Starter Edition?

  We often sell these netbooks as well as our units of measurement as an input/output device. But I think that in a future close all netbooks will use Windows 7 instead of XP and above all the Starter Edition.

  So if it is not taken in charge this will help upgrade netbooks to Windows 7 Home Premium? I have already tested Windows 7 Professional and it works, but I do not want to install Professional on a netbook...

  My second question also the Starter Edition.

  I'm building a kit of distribution of working space example "interp.cws" (curve fit and Interpolation) with the runtime engine installed in the application directory. If I run the .msi instead of the setup.exe package then the software has been installed on the system.

  So I can run the software, and it seems to work. But if the software calls a function in the library of analysis advanced (for example, the Spline Interpolation) it does not work. With remote debugging I discovered that there was a nonlethal runtime error "the analysis DLL library is not found or could not be loaded" during the spline function calls.

  The same sample works fine with Windows 7 Professional.

  Is this also a restriction of the CVI, and will be the reason (or one of the reasons) did not support the Starter Edition?

  Or is there a workaround for these errors?

  Best regards

  M.S.

  National Instruments supports Windows 7 Starter; However, just as now, our facilities are defined to stop any Windows Starter Edition is detected.  This is because XP and Vista Starter Editions were marketed to emerging markets and had severe limitations of performance.

  You should make sure that your specific product supports Windows 7.  If this is the case you can follow the instructions in the knowledge base

• The CompactRIO Modules are not connected

  I'm currently developing a compactRIO, but modules are not detected in system OR distributed, Manager even after hitting refresh Modules in the scan engine. LabView is able to detect modules, but the code does not compile. Watching the memory usage in the Distrubted System Manager it shows that there is no available memory and he has no memory allocated. I tried to reboot the device, uninstalling and reinstalling the software, but nothing has worked. Any ideas of what I could do to try to fix it?

  Thank you!

  This was the tutorial I used to implement http://www.ni.com/getting-started/set-up-hardware/compactrio/assemble.

  He has got to work! I reformatted the compactRIO and reinstalled the software and that seemed to do the trick. Thanks for your help!

  For anyone who runs into this problem, I found the following documentation to be a good reference:

  http://zone.NI.com/reference/en-XX/help/370622K-01/lvrtconcepts/deploying_running_vis_rttarget/

  I followed the steps described in the section "Troubleshooting steps" OR Scan Engine deployment.

• LabWindows 2013 does not

  I'm using Labwindows 2013 SP1 on Windows 7

  This morning I made a few changes to the code for my project when I clicked on the icon "Debug Project", project generation succeeded, then just Labwindows hang up, saying "not responding". I killed the project and labwindows revived and tried again and it did the same thing. I backed all the changes I did today what it was yesterday, when I did not have this problem and tried again and it's always hanging with "not responding".

  I went to labwindows 2013 about 4 months ago and I have never had this problem until today and now it won't go away.

  I'm completely at the stop. Can someone help me solve this problem?

  Thank you

  John W.

  Hi, John.

  The newspaper that you sent seems to indicate that you have more than 750 watch expressions in your current workspace. This blockage you encounter is probably the result of LabWindows/CVI, trying to update all watch expressions.

  I have reproduced a substantial blockage by adding only 700 watch, all for a single int value expressions in my application.

  To resolve this problem, you can delete the watch expressions. If you can't access their interactive way to the LabWindows/CVI environment, you can remove them from the bottom of your SCF file. You can do it in a text editor.

  I would like to know if it works for you.

  Thank you

• Module NI 9214 and cRIO, where is the example for the scan Mode

  Hello

  I'm new to programming of cRIO. I'll use a cRIO 9022 with different modules, such as 9214, Labview 2010.

  However, when I go to the examples, I can't load the get started scan for 9214 module Mode, it says that I have to reinstall. I don't know what examples are not installed, as I reinstalled my software already once and I could not find any change. Anyong can tell me where I can find this example, so I'll try to find more easily the example and install it.

  Thank you very much

  See you soon,.

  Antonio

  Hi Antonio,.

  I recorded the example mentioned to be compatible with 10.0 using the function 'Save for the previous version' of LabVIEW and attached the new document below. Please let me know if it works.

  The course will be very useful if you want to use it much in the future. Real time quotes are most relevant to develop on CompactRIO and the FPGA course will be very useful if you plan to use the FPGA in your applications. Do you have a course of training before sitting?

  Thank you

• Best method for updating CompactRIO data to Server "National Instruments.Variable Engine.1"

  Hi all, I have an OPC Client of third-party I want to use for testing with the CompactRIO. Can I specify 'National Instruments.Variable Engine.1' in the OPC server, create a new item of the mutual FUND, go to a variable and then see its value. I use a CompactRIO and I want to send the updated data that I am acquisitionning of for third-party Client OPC, then, what is the best method? Currently, what works, is that I created a shared variable published to network on the LabVIEW host that I dragged in the CompactRIO project. I've created a small loop increment value every 500ms. I then created on the host computer, a little VI, who issued this national value to "" Instruments.Variable Engine.1". Now, is there a better way to do his? Is it something that can automatically fill in manually the Variable of the CompactRIO motor without publishing the shared inside a LabVIEW application variables? Thank you for your time, best regards!

  Thanks a lot for your replies, Drew,.

  I downloaded the OPC UA API and it will next week.

  Thanks again!

• Can I download a background on the system in real time and run it?

  Hi, I would like to take advantage of some tools in the system in real time.

  I thought that I could download it by file transfer,

  

  and then did something like this in the system in real time.

  

  Probably it is not...

  However, there is other ways to achieve my thought in the system in real time?

  Do you mean the exe was built for windows, so that it is not allowed to run in time real system?

  Fix.

  I have to communicate between CompactRIO and servers through an ethernet cable...

  so... you write a program runs on the cRIO and bring it to your servers over TCP.

• How to remove the additional window when I start LabWindows/CVI or will execute my program?

  For a short while (maybe a week or more), I get a small extra window behind my request. Also, when I start LabWindows/CVI, I get the same window. It is a small blank window with the same title as the application. Press close (X) closed the application too.

  I don't remember seeing this before and that he doesn't know what has changed on my PC. It also happens with old LabWindows (previously compiled) programs, it seems that something in Windows has changed.  I use Windows XP and LabWindows/CVI 9.0.0 (348).

  Thank you

  Rob

  Hi Rob,

  The window that you see is part of the CVI. It is the parent window for all windows of the CVI so much in the environment and execution. As a general rule, this window is hidden way off the screen so that you don't even know it's there. But some video cards have a parameter that requires all windows off the screen to move to the screen. Take a look in your video card settings to see if this setting exists on your pilot. If so, then disabling the setting will allow the window to hide off screen.

• CompactRIO Deploy Error "LabVIEW: resource not found.»

  Hello

  I use a 9002 CompactRIO and LabVIEW 8.5.  I made a simple FPGA VI to read a bunch of analog inputs and write a square wave to a few analog outputs.  Then, I made an another VI to run on the target in real time in order to convert the frequency scaling and updated entries nationwide cycle duty cycle values and frequency real accountability.  When I try to deploy the VI in real time, I get the following:

  Deployment r03fsae (the goal settings successfully deployed)
  Deployment of special audit Tags.vi (5.89 K)
  Deployment GetRTHostConnectedProp.vi (3,41 K)
  Deployment of search and replace Pattern.vi (8,11 K)
  Deployment nirviFillInErrorInfo.vi (8.09 K)
  Deployment niLvFpgaErrorClusterFromErrorCode.vi (11.27 K)
  Deployment nirviErrorClusterFromErrorCode.vi (5.93 K)
  Deployment error Code Database.vi (3.67 K)
  Deployment to find Tag.vi (10.43 K)
  Deployment of fusion Errors.vi (6.75 K)
  Deployment Whitespace.vi topping (3.71 K)
  Deployment nirio_MultilineStringToArray.vi (8,81 K)
  Deployment nirio_AppVersionToI32.vi (3.96 K)
  Error error Code.vi (23.42 K) Cluster deployment
  Deployment _nirio_device_attrSetString.vi (9.46 K)
  Deployment _nirio_device_close.vi (9.90 K)
  Deployment nirio_Read32.vi (13,07 K)
  Deployment _nirio_device_open.vi (11.59 K)
  Deployment nirio_Write32.vi (13,01 K)
  Deployment _nirio_device_writeBlock8.vi (9.83 K)
  Deployment nirio_Write8.vi (13,01 K)
  Deployment _nirio_device_configSet.vi (11.42 K)
  Deployment nirio_DMAReconfigureDriver.vi (16.63 K)
  Deployment _nirio_device_writeBlock32.vi (9.36 K)
  Deployment nirio_Read8.vi (13.04 K)
  Deployment nirio_DMAStopAll.vi (11,39 K)
  Deployment _nirio_device_attrGetString.vi (13.06 K)
  NirviReportUnexpectedCaseInternalError (String) (5.58 K) .vi deployment
  Deployment of .vi nirviReportUnexpectedCaseInternalError (U32) (4.72 (K)
  Deployment _nirio_device_readBlock32.vi (14.41 K)
  Deployment _nirio_device_attrGet32.vi (13.85 K)
  Deployment nirio_IsItOKToDownload.vi (7.07 K)
  Deployment nirio_MiteNTDeviceFamily.vi (5.30 K)
  Deployment of Format Message String.vi (7.35 K)
  Deployment CORE.vi General Error Handler (51,02 K)
  General Error Handler.vi (13.19 K) deployment
  Simple deployment Error Handler.vi (10.01 K)
  Deployment nirio_CheckDriverVersion.vi (10,58 K)
  Deployment _nirio_device_attrSet32.vi (13,62 K)
  Deployment nirio_Download.vi (29,31 K)
  Deployment nirio_ConfigureRegisterAddresses.vi (7.11 K)
  Deployment nirio_CleanUpAfterDownload.vi (6.22 K)
  Deployment nirio_PrepareForDownload.vi (6.44 K)
  Deployment nirio_EnableInterrupts.vi (13.76 K)
  Deployment nirviRIOSetUpMiniMite.vi (31.23 K)
  Deployment nirio_Open.vi (14.93 K)
  Deployment nirio_Close.vi (10.95 K)
  Deployment nirio_DisableInterrupts.vi (11,10 K)
  Deployment of nirviIntfOpen_cRIO - 9102.vi (85,54 K)
  Deployment of nirviIntfClose_cRIO - 9102.vi (12.24 K)
  Deployment of scale freq and duty.vi (4.46 K)
  Deployment XDNodeRunTimeDep.lvlib
  Deployment XDNodeRunTimeDep.lvlib:loadlvalarms.vi (5.47 K)
  Math.vi sensor deployment
  Could not download the math.vi sensor
  LabVIEW: Resource not found.
  LabVIEW: Resource not found.
  LabVIEW: Resource not found.
  LabVIEW: Resource not found.

  Download completed with errors.

  This error message is not particularly useful, someone knows what could be my problem?  Or how I can fix it yet?  Is there a detailed journal where I can look for more information about the error?

  Thanks in advance for any help!

  Hi David,

  You may be walking on ground dangerous with your fpga code, old and new.  You use the modules in what is known as 'calibrated' calibration mode that is of fixed point math.  Your generation of square wave fpga using whole math, which is normally used when the modules operate in mode calibration "gross". To change the calibration mode, you will need to right click on the module, then select it desired mode to use.  I'm not saying that you do.

  What you need TO do to ensure the proper functioning of your fpga VI is to make sure that you use U32 son of math required and then convert the U32 an FXP using the correct encoding (if it is signed, word length and integer).  In your case the 9263 requires signed word in length, 20-bit, 5-bit all over.  Insert an FXP conversion between the generation of square wave and either create a constant FXP of the appropriate type (or use a control correctly put in place of one of the other 9263 channels [AO0 AO1]) and connect to the node of type of fixed point on the conversion OR define the conversion of fixed point with a right click on the exit node and the appropriate settings in the popup box.

  As for your new code fpga, I don't know why you used a sequence structure that your reading of 18 channels on the 9205 will have 144 microseconds, and each write two channels on the 9263 will take 5 microseconds.  I've not worked on how long will take the square wave generation.

  I do not understand your last question.

  > "I've attached a screenshot of my pwm_out.vi if I remove control of read/write of background, or if I don't use of all none of the analog inputs, it works fine.

  > But as soon as I add the analog inputs it fails... ».

  Did you create a new stream of your fpga_new.vi and referenced in your pwm_out_new.vi on the RT?

  It is difficult to guess what you are showing in the screenshots.  If the project is not too big then maybe you could post here.

  As mentioned above, by JMoto, software versions help.  Check in MAX you have on your PC and also on the cRIO 9002 to make sure that there is no incompatibility.

  See you soon

  Stephen

• NI4350 (PCMCIA) and NI DAQ (traditional)

  I'm trying to get a NI4350 to work with VC ++. I downloaded and installed NI435X252, which is supposed to be specific to this device. When I use the Group MAX, the device appears and test panel shows that temperatures are read, if the equipment is operational. There is no other product OR installed on this machine.

  The problem is that when I use the functions in nidaq32.lib, I always get the response status-10403 (if the device number points to the device) or-10401 (if the device number is incorrect), so NIDAQ works. -10403 means that the specified device does not support the requested action. I get this for ALL functions that I tried to call, including AI_Read(), AI_VRead(), AI_Check(), DAQ_Rate(), SCAN_Setup(), Timeout_Config(), DAQ_DB_Config(), DAQ_Start(), when running the examples provided.

  Is there a specific startup sequence that is needed? I have not found something like this documented.

  Can anyone help?

  Hi aditus2,

  Installation is not without is a known issue with NOR-435 x 2.5.2, however the 2.5.1 version doesn't have this problem. It is the link below:

  NOR-435 x 2.5.1 - Windows XP/2000

  During installation, select the media of Visual Basic and LabWindows/CVI. This will install a few examples that you can model your application around. "" "" You will also be able to view a list of function under Start ' programs ' National Instruments ' NOR-435 x ' Documentation. Also to more completely answer your first question, driver OR-DAQ only supports devices 435 x with LabVIEW knowledge base by following the link:

  Can I program NI 435 x with NOR-DAQ function calls?

• How to use the target FPGA and co. on the same chassis cRIO?

  I have a cRIO system consisting of a master chassis 9074 with several modules IO and EtherCAT 9144 slave unit.

  I want to run a CIE (see: http://zone.ni.com/devzone/cda/epd/p/id/5333) on the chassis of the master, this uses the analytical engine. At the same time I have to do some very urgent measures if I want to use the Board in hybrid mode, using analysis and FPGA engine at the same time (as described here: http://digital.ni.com/public.nsf/allkb/0DB7FEF37C26AF85862575C400531690.)

  But as soon as I add the FPGA target at one of the chassis, the feature of the ice on this chassis stops working. After some research, I found that the CIE can initialize is no longer the modules belonging to the frame that has the target FPGA on it. Error in the method Init of the CIE is: 65700 (indeterminate). This occurs when you try to use "for a more specific class' on the modules configured with a target FPGA on it.

  Someone knows what can cause exactly this problem and perhaps provide a solution/work around?

  Many thanks in advance.

  Hybrid mode requires you to have a bitfile compiled running on the FPGA to be able to read the Scan Interface IO Variables.  Move the target FPGA at the RT target module will allow Interface of scanning for this module, but the frame will always mode Interface of LabVIEW FPGA.

  

  To get fair access to the scan mode for the frame, right click on the chassis in the project, and choose Properties.  Then, modify the Scan Interface programming.  If you want to continue using the programming of FPGA and the Scan Interface set (hybrid mode), you will need to compile a bitfile (empty if you do not want programs on the FPGA again or containing your FPGA code).  By compiling, the support of the module scan mode for the modules under your RT chassis is compiled in your custom bitfile.  Then, on your VI RT, you need to use reference FPGA VI open to your newly compiled VI.  Once this VI is deployed and ongoing implementation, you get the data from you are the CIE.

  For more information, see this knowledge base article and Reference Interface of Scan CompactRIO and procedures.