Problem of LabVIEW addons

Similar Questions

• Avast detects URL: HURT when opening firefox. No problem with IE or Chrome, after a repair carried out problem is NoScript addon. Can he have been infected?

  Avast - network shield

  Details of the infection

  URL: http://188.24.140.190/
  Process: C:\Program Files (x 86) \Mozilla Firefox\firefox.exe
  Infection: URL: LTA

  I doubt that the No script addon has been infected. However, try the following:

  First of all, try resetting Firefox. Refresh Firefox – reset settings and Add-ons. This simple step will eliminate the many problems in Firefox with just one click.

  Download and install MalwareBytes Anti-Malware, run a full scan. http://www.malwarebytes.org/. This check allows that there is no virus on your computer, causing problems. You can uninstall this program after having cleaned the infections.

• Problem in Labview DSP

  I have a DSP problem to be realized in the labview. However, I am not very familiar with a few boxes to tools. The goal is to detact the pulse whose duration and intensity of a noisy signal in real time. Given the pulse signal, the points how to locate the failure?

  Thank you

  It seems that the signal on the great transitions is superior to most of the noise.  I think I might try looking great transitions, say > 8-10 in 2 or 3 samples.  When I find such a leap, then look at the average before and after to see if we're a real pulse or noise.

  If the width of the pulse is known or have a narrow range of values, you can also use this information to help distinguish between the signal and the noise.  The transitions very wide encompassing the negative part of the pulse are much easier to detect.

  Lynn

• Signal Express version unknown problem with Labview VI

  Hi all

  I am trying to run 2010 Labview Signal Express VI. It gives me "unknown version" problem. When I checked for Labview versions, he said 10.0f2 and Signal Express can read the version of LabView 2010. I don't understand this. 10.0f2 is not just a patch for version 10.0? I will appreciate if someone can help me with this.

  Kind regards

  Kanu

  Hi Kanu,

  I tried to write a simple VI and its importation to the Express Signal and I have not had any problems. I use 32-bit LV2010f2 and Signal Express 2010. I have attached the VI I used so that you can try it yourself. I followed the instructions of this KB to create a distribution of the source file. If you follow this KB and still can't make it work, can you please post the VI?

  Thank you

• Problem between Labview and Melanie 2602

  Hello world

  I think my question is a bit silly, but I really don't know what the problem is. I just want to read my current solar cell by changing the level of my blood to get an IV curve, which is normally pretty easy. So, I created a loop, where I increase my voltage step by step, and used a function named VI from Labview library that connects the Keithley and Labview together, "Keithley 2600 Series.lvlib: Source Level.vi. I start at 0 and increase by 0.01 volt each time. If I use execution of climax, I see clearly the value is correct, and if I go inside the SourceLevel VI, I clearly see the command string: "smub.source.levelv = 1.6," for example, if I want to put my voltage at 1.6V. The attached picture shows a part of my code.

  Despite all this, it is clear that the Keithley does not react properly. It only works v of v 1V, 2V, 3V, etc... but never the values between. My IV curves are ok to read the Isc, but no VOCS. Never happened to any of you? I would be really happy to understand what I'm doing wrong, because it seems easy enough to solve. :/

  Thank you very much!

  It is quite difficult to debug a picture of a tiny part of the code.

  But I'll take what I see.  Your constant shows a 0.01 (comma).  So I guess that you are in a country that uses a comma instead of a decimal point.  I don't see what is happening inside the code Keithly, but I'll make an assumption that he made some conversions where it is expected that the comma is a period.

  Look closely at the code Keithly and see if that explains it.  Try to set your PC to use a period for the decimal point and try to re-run your code and see if it works better.  It is possible that Keithly conversion uses a system, rather than setting using a decimal point, which is that your sentence says it's sending.

• Problem with LabVIEW

  I met a problem when using the peak detection function in LabVIEW...

  Basically, I load a waveform in VI to detect peaks using the function of Ridge detection. of the waveform, it is obvious that the first peak will happen about 10570Hz...

  Using size 3 subgroup, it detected 1 pic to 10567Hz (correct)

  When you use the size of subgroup of 4, it detected 1 pic to 10569Hz (correct)

  When you use the size of subgroup of 5, it detected 1 pic at 12737 Hz (bad)

  When you use the size of subgroup of 6, it detected 1 pic to 10588Hz (correct)

  When you use the size of subgroup of 7, it detected 1 pic to 10588Hz (correct)

  And using other different sizes of subgroup, the freq agrees with waveform... Why when you use the size of subgroup of 5, it does not give good playback? Is there a theory or a reason for this? or just a bug with the LabVIEW function?

  A VI is fixed and the default values are loaded.

  Appreciate any assistance/advice.

  
  

• Communication problem between LabView and acquisition of data USB 6259

  I want to monitor a data USB-6259 acquisition using LabVIEW 8.6. However, when you try to create an explicit task (using the DAQ assistant) in order to acquire a signal, I get the message asked supported device found¨. I can see the USB-6259 under ¨Devices and interfaces¨ to the MAX, but when I try to import the configuration data for NOR-DAQmx 8.7.2 in MAX, I get the message ¨Can´t import file configData.nce.  File not found¨. I use NEITHER-DAQmx 8.7.2.  Any suggestions?

  Corneliu

  Hi, Corneliu,

  This question could be generated due to a corruption of database of MAX. Here is a link to restore the database to the MAX.

  http://digital.NI.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9?OpenDocument

  Just follow the steps and let me know if that solves the problem.

  A greeting.

  Jesus.

• Problems of LabVIEW with Test Unit under lvoop

  Hello

  I try now provided with LV2012 with a LVOOP code Unit Test infrastructure but seem to be a few problems.

  I have built a unit test for a base class in the attached draft who is the source of class (it is another class in the project as it is an example of a method for recovering, but it is not used in the unit test). My problem is that I get results that fail for one of my tests, when I think they have to work.

  Basically, the unit test is configured as follows

  Case 1) test the VI without installation VI and ensure proper operation default values

  Case 2) test VI by setting specific values in the test in VI of disassembly and also check the single release of "Source Method.vi" configuration VI

  Case 3) Test of the VI with the VI of installation using the default values and confirm them through the VI of disassembly

  When running case 2 fails and indicates that disassembly of the VI return values by default not those fed to the installation VI. I don't see why.

  As per

  

  Any suggestions?

  All the best

  David

  Hi David,

  The behavior you describe is planned. When you first call the 'Source_Method.vi' by using the 'SourceAccess Unit Test Manual.vi", the"Unit Test Manual.vi SourceAccess' creates and instance of the "Source_Method.vi". In this specific case of the VI it will boot with the default values but will then retain the values passed by the "Unit Test Manual.vi SourceAccess' until the project we closed, or specifically tell you to reset defaults. Whenever she is called by 'SourceAccess Unit Test Manual.vi' it will access this instance of it. If another instance of the "Source_Method.vi" was created by another parent it would be initialized with their default values, until crushed by the top-level VI calling. Then would he behave exactly as the instance created by the "Unit Test Manual.vi SourceAccess". Whatever your type typedef and its configuration, as long as everything is connected correctly, this should be the expected behavior when you configure things through object-oriented programming in LabVIEW.

  I hope this information is useful to your application. If you want to see a LabVIEW example that demonstrates this behavior, you should consider referring to parts of the ReferenceObject.lvproj. It is found by searching in the example finder LabVIEW object-oriented. This is accessible via

  Help > find examples.

• Files reading TDMS problem in Labview 2010, created in 2009, error-2503

  I did my measurements on my laptop with Labview 2009 installed.

  The file format has been TDMS v1.0

  I can read these files with the TDMS files viewer and I am able to do analysis on my laptop.

  On my desk I have Labview 2010.

  If I run the vi in Labview 2010 analysis, I get the following-2503 error: specified file does not have the PDM file format standards.

  What's wrong?

  I can open the file in Excel with the add-in.

  I've included a tdms file created on my laptop in Labview 2009

  For this problem, it's a bug in LabVIEW 2010 (not in previous versions of LabVIEW), sorry for the inconvenience. While the side R & D to fix this problem, we also a workaround solution, but perhaps a little more complicated:

  (1) Please use older version of LabVIEW (like 2009 or 8.6) for defragement file by using the node TDMS defragment, if it works fine, you can then open it défragmentée TDMS in LabVIEW 2010.

  (2) if the PDM defragment returns an error, then you can always find your defragmened files in the temp directory of Windows, but under a different filename (randomly generated), you can type "%Temp%" Run windows to open your temporary file.

• Problem with Labview communication with Arduino Uno

  Hello

  I tried to run a simple program in labview through my Arduino Uno R3 all morning and keep running into the same problem: no response from my Board of Directors. I'll catch you up on what I've done so far:

  -flashed LIFA Base to my Arduino
  -Downloaded the driver update of VISA

  written-a the block diagram (I hope) for a led on off function

  When I run the program in labview, the RX flashing intermittent, continue for 30 seconds before stopping. The led on pin 13 is not turned off as it should, and I have no control over the power function light. I also tried a program of control of servo with no response and the same flash of RX. Never the TX flashes.

  I am quite stuck, so any help is greatly appreciated. Also I'm not a comp sci guy, I'm just an engineer in mechanics with a half of C++ so keep pg when it comes to the language of the computer.

  I've attached a picture of my diagram of LED, see if you can spot a problem.

  Thanks in advance!

  SOLVED: Reset the Arduino card after that labview had sent his orders (while the RX light was still flashing). Works like a charm.

• NI USB box problem when Labview ends abnormally

  Hi all

  recently, I had a problem with the NI USB box used in Labview.

  I wrote a very simple program and it runs in Labview 2011. Basically, it reads data from a NI USB box and also send data back. According to my knowledge (I don't know if it's good or bad), when the Labview is arrested shortly how it is completed, the USB box should also stop working. But the thing is, when the Labview program ends abnormally, let's say I directly terminate from the windows task manager when it is running, all the ports of the box USB will hold their final statements until I restart Labview and write new values to them.

  This could be very dangerous. For example, when I use the USB box to control the power of a power supply, the Labview program crashes (which happens often), the power supply box and USB power will continue to work until I restart the program again. I tried several different types of boxes NI USB on PC and the problem still occurred. So I was wondering if there is no mechanism that prevents such problems or if I can do something programmatically to avoid it.

  I thank very you much for your help and your time.

  Best regards

  Sun

  Sun,

  Another area where you can have a misconception: LabVIEW is not control USB DAQ device. The LabVIEW program called the DAQ driver program (typically DAQmx or DAQmx Base) and pilots say the OS to send messages via the USB port of the DAQ hardware. So stop the program LV, intentionally or accidentally, does not say the data acquisition driver and the OS USB driver to put the DAQ hardware in a State course.

  If you have a configuration where the LV program can be stopped before it can send orders "Safe state" DAQ hardware, you cannot ensure the DAQ hardware stops correctly.

  There are a few screws that have been written in LV "watchdog", but even those who depend on the operation of LV execution engine.

  You should carefully rethink the entire system, make security issue, one of the main objectives at the beginning.  Most likely, you will find that you need to a separate device, hardware clock or PLC, if the software fails to stop him.  You should also consider whether you need a real-time operating system to avoid some of the problems associated with the standard desktop operating systems.

  Lynn

• Problems with labview on TestStand deployment system (usually run without a license of labview)

  I'm trying to deploy a system using testStand for a machine of deployment for the 1st time. I built my Installer and image etc files The files of the installation on the target however machine when I try to run my program in mode operator TestStand I get errors relating to Labview. The only way I can work around this error is to activate a Labview license on the deployment computer, is not viable.

  The error I see when I turn off my Labview license simply indicates that an error has occurred accessing the Labview ActiveX automation server.

  I have included engines of execution etc. in my Installer. As this is my first build is there something obvious I've missed here?

  Thanks for any input.

  Vinny

  Vinny,

  My first guess is that the setting of the LV adapter on the deployment computer is always set to "LabVIEW development environment". You must change this to "runtime".

  hope this helps,

  Norbert

• Problem DaqMx LabVIEW

  Hello:

  Installed Labview 2012 yesterday, daqmx was already installed (9,6) since I used it with Measurement Studio 2012.

  LabVIEW does not recognize DAQmx.

  I'm using Labview examples and get daq mx errors.

  Thank you.

  You must install DAQmx after LabVIEW. Since LabVIEW did not exist when you have done the installation DAQmx, LabVIEW required records would obviously not created.

• Problem calling LabVIEW DLL with c#

  Dear all,

  I compiled a few DLLs in LabVIEW and called these DLLs using c#.
  I'm having trouble passing in strings and arrays as input and output of the DLL.

  Whenever I try to view the string I have entered in a dialog box (this part is written in LabVIEW DLL), a LabVIEW message dialog box appears and the program just stuck there.

  Whenever I try to enter a string or an array to the dll, Microsoft Visual Studio would display "attempt read or write protected memory. It is often an indication that other memory has been corrupted. »

  I attached the vi and also the c# .sln file.

  Can you guys please advise where am I wrong?

  Thank you very much.

  You must allocate strings and arrays of output!

  private void button1_Click (object sender, EventArgs e)
  {
  output string;
  int [] value;
  StringOutput ("A", "B", exit, 3, value, 4);
  }
  }

  Your variable output and value must be preallocated to ensure storage of 3 items respectively. 4. and since you want to receive the C string that you need to increase this to 4 characters terminated by a NULL value.

  String in c# is also a not a C string of object pointer. You must declare the StringOutput() function as follows:

  [DllImport("SharedLib.dll",CallingConvention=CallingConvention.StdCall, Charset=CharSet.Ansi]internal static extern int StringOutput(StringBuilder A, StringBuilder B, out StringBuilder StringOutput, int sizeString, out int[] output, int sizeArray);
  

  Then call like this:

  StringBuilder output = new StringBuilder(4);int[4] array = new int[4];
  
  StringOutput("A", "B", output, output.Capacity, value, value.Length);
  

  Please note that I'm not a pro in c# and usually do not do much in it. Also that this code has not been tested or updated at all, so probably contains some errors. He however point you in the direction of where to look further.

  What you need to understand, is that the C DLL that you created in LabVIEW has a so-called unmanaged interface. This means c# is not able to know how to manage the memory for the parameters at all and you have to do everything yourself, where the obligation to explicitedly initialize variables output and table with a block of memory préallouée.

• Modbus tcp 1.2 problem with labview 8.5

  I have a new upcoming project that involves a link to modbus tcp.  I downloaded version 1.2 of the modbus library and installed.  Everything appears on my palette, but if I try to open one of the examples he comes as for version 8.6.  I am currently using 8.5 but the download says it works all the way back to 7.1.  Any ideas?

  Are you sure that you have selected the correct folder for the "installation"? When you download the 1.2 OR Modbus Library (here: http://zone.ni.com/devzone/cda/epd/p/id/4756), you get a zip file. Inside this file, you will see 4 folders, one for LabVIEW 7.1, (issue 71), one for LV 8.2 (case 82) and also records 85 and 86. So make sure that you have done the installation with the correct folder.

  Let us know if this helps or not.

  Kind regards.

  Robst.