Modbuss problem with Labview 12 DURATION

Similar Questions

• 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 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.

  
  

• 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.

• 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.

• Problem with LabVIEW 9.0f2 and VISA 5.0 on Mac OS x 10.6

  Hello

  I'm using MacOSX 10.6 and Labview 9.0f2. I installed the lates VISA (5.0.0) drivers, as they are the only support OSX 10.6.

  Now, I try to run the "basic series write and read" example and get the following error:

  Error 1073807343 has occurred to the property node (arg 1) visa set up a Serial Port (Instr) .vi-> basic series writing and Read.vi

  Possible reasons: VISA: information about insufficient localization (Hex 0xBFFF0011) or the device or resource is not present in the system.

  As I am a newbie to Labview, I'd appreciate any help on this...

  Thank you

  Daniel

  Hello

  You do not have a device series on behalf of resource, you use to write and read and take?

  Did you check with Max OR and log on to this device.

• 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

• problems with labview 2013 build specification

  I have a few screws of LV2010 I want to use to create an application to run with RTE2013. I have LV2013 on my computer.

  Without a massive compilation of the LV2010 screws, the element of selection of source files in the build specification has no project file to choose and it won't allow me to go looking for.

  Any ideas why this happens?

  Thank you

  Right, you must create a project and put in all of the screws to be included in the compilation - including one that is the top-level VI. Once this is done, you can save the project, just not to re-record the EIS.

  Now you should be able to define your spec to build according to normal.

  Mike...

• IP in chain - timing problem with Windows 10

  Hello

  I was working on a project and noticed something that I wanted to highlight to others and to see if I could get a reasoning as to why this is happening.

  I started this about four months ago and recently updated my computer to Windows 10 up-to-date project. I am under Labview 2014 V14.0f1 (32 bit) and had not seen any problems with labview until I activated an error logging code which reports data to a syslogger.

  We started noticing that the recorder took much longer than usual to deal with errors and in turn slowed down the whole program.

  When we dug in the question, we found the slow down was the INVESTIGATION period to the block of the string that is used to extract the host name. It took about 4.5 seconds to complete. I have run the same code on a windows 7 VM and it run under a 1 ms...

  No idea why IP chain is taken almost 4 500 x times more time in Windows 10 vs Windows 7? We have worked around the issue by making a control that can be set from a file configuration of the value, but I wanted others to know and hopefully get an answer to why this is the case.

  Thank you

  Chris

  LabVIEW 2014 is not technically compatible with Windows 10.

  Compatibility of the versions of Windows with LabVIEW.

  Maybe the search time is affected by something that has changed to win 10.

• Possible GPIB communication through interactive control of Visa, not with Labview

  Hello

  I have a communication problem with Labview with GPIB instruments (with functions of visa).

  I get:

  "Error 1073807298 occurred at the VISA opening

  Possible reasons:

  "VISA: (Hex 0xBFFF003E) failed to perform operation due to i/o error."

  However, it works with an interactive control visa and this is where I am confused!

  Here is my setup:

  -Labview 2011 assessment

  -VISA 5.1.2

  KUSB - 488B with the associated drivers (adapter USB to GPIB of Keithley)

  Because I can speak with my instruments in visaic, I guess the installation of drivers for the Keithley interface is ok.

  Trace IO NOR I see beeing of commands passed through Labview to VISA so that they "see" between them.

  I found a thread where someone had the same problem and its solution was downgrade to Labview 8.5.1, which is not possible for me.

  http://forums.NI.com/T5/instrument-control-GPIB-serial/Keithley-2700-driver-problems/TD-p/1474212/PA...

  You have an idea to solve this problem?

  Kind regards

  Baptist

  Here's a follow-up on this issue.

  I tried with Labview 32-bit on main machine: it works.

  The pleasure is that I have to use Labview 64-bit.

  So the ultimate solution is now to run a client and a server of visa on the machine: Labview 32 bit can directly access my resources GPIB, Labview 64-bit must go through the closure of the network.

• Problems with migration from LabVIEW 2012 VBAI 2012.

  Hello.

  Someone had problems with the migration of the VBAI 2012, 2012 to labview?
  I'm filing this disadvantage when use migration in VBAI everything works fine, when I use LabVIEW with 'Vision Acquisition Express' for example, everything works as it should.
   
  The solution I've done has been to work with the control VBAI API and it worked perfectly, but I wonder, if a bug or a known error on this process.

  Thank you.

  Finally, I solved it by installing the "Vision Development Module 2012 SP1". With this update worked correctly migration.

• problem with a block of memory in labview 2009

  Hi all

  I have "ERROR: MapLib:979 - LUT4 symbol" during the compilation process (lots of errors like this), and I discovered that the reason of my problem is block of MEMORY.

  To be sure that the problem is in this block, I did a very simple project in LabView 2009 (on FPGA Target PCI5640R) only with the use of this block you can see in the photo, as well as in file test_memory block.lvproj attached link: https://www.dropbox.com/sh/u87f1oihelmm4dq/Jo_6-bICSf

  

  I have a problem with compiling VI with this block, and I have so many errors like:

  ERROR: MapLib:979 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<0>1.
  (output = window/Thatcher/res000001ed_wi<2>) is the input signal
  "window/Thatcher/res0000020d_wo<1>" that will be deleted. See Section 5 of the
  Map a report file to find out why the input signal will become conveyors.

  or

  ERROR: MapLib:978 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<23>1.
  (output = window/Thatcher/res000001ed_wi<25>) is an equation that uses
  input pin I2, which no longer has a connected signal. Make sure that all the
  the pins used in the equation for this LUT are signals that are not cut
  (see Section 5 of the report file map for details on which signals were
  adjusted).

  Entire report, you can see in the file report.txt on the attached link.

  I would appreciate if someone could take a look at my problem with simple project and suggest me a solution.

  I'm really stuck with my biggest project which need to have this memory block.

  I'm looking forward to hear from you,

  King looks

  ING. Damir Hamidovic

  Hi all

  I find a sollution to my problem.

  In memory-properties-general-setting up, I changed the block to look up Table memory, and I compile memory.vi and run it successfully.

  I did change as you can see on the picture:

  

  Just, can you tell me is it all "bad properties" and limits the use of this type of memory (Look up Table) of the implementation?

  King looks

• Problem with window painted and scrollbars when editing (LabVIEW 8.0.1)

  I'm under LabVIEW 8.0.1 in Windows XP SP3.  For my main VI, I came across a strange problem about 5 months ago.  The front window - both in edit mode and run mode - arrested repaint itself on the right side which is no longer visible when you scroll from top to bottom, but also visible overlapping Windows.  Coinciding with the repaint problem, both bars scroll search disabled grey arrows and no boxes in the bars that you can click and drag to scroll the window.  The scroll bars work still partially if you pass the mouse over it and roll the mouse wheel but does not work by clicking and dragging.

  The façade has a lot of controls and indicators, including containers of tab control and is greater in the horizontal directions and vertical so the two scroll bars must be active.  But I deleted everything in the Panel before and everything in the schema and the problem persists.  If the problem is not directly related to a control/led display.

  I saved the simple VI to this problem (using a line of large text and a high box rounded to test), and then created a new VI and copied the two elements at the new VI.  This new VI didn't paint it and the problem of the scroll bar.  The two screws are slightly different in the memory usage and the revision number (bad is review 1785 and the good is revision 3), but otherwise the two screws are identical.  I have attached two screws at this announcement.  When you first open the bad VI, you will see the scroll bars disabled while the good VI has active scroll bars.  To replicate the repaint problem, scroll the window up and down with your mouse wheel.  If it's good when you first open the VI, click on another window, then click on the window of VI and try again the mouse wheel.  This by clicking sur-loin-and-return always causes the problem of repaint for me.  I tried the screw on two different computers, both running Windows XP SP3 and LabVIEW 8.0.1 with identical results.

  Here's what I discovered simple troubleshooting with the screws:

  always off scroll bars

  * repaint the problem in the main window for larger then 680 pixels of window widths

  * repaint the problem in the menu bar of the main window for widths of more than 646 pixels

  * entire window becomes disabled than 1348 pixels window width

  * can paint window minimize and restore, but only repaints only once

  * scrollbar boxes sometimes flicker in the display, but then disappear

  * Scroll left and right hovering mouse over the bar and horizontal scroll by using the mouse wheel

  I found something similar on this forum (thread: problem with refresh of façade)-it could be linked to the CAR on the Panel being offset internally.  I don't have access to LabVIEW 8.5 or later and do not plan to upgrade - I have not tried the trial version, as this user has done.  I could try to copy and paste my set of the block for a new VI diagram but the VI is so important I'm afraid something would break, plus I don't want to do it again in a few months.  The problem seemed to occur after a certain number of stops (or revision number).  I save copies of backup often and when the problem first happened, I was able to go to a previous version, make the missing changes and save it without any problem, but this only delayed the problem and he came later.  It is therefore perhaps the revision number.  It seems not related to a change or a particular addition in the front panel and the graph.

  The attached picture shows the repaint problems and scroll bar in bad VI.

  This raises a question I have - if this problem is a bug has been fixed in 8.5 and later, is it possible to apply bug fixes for older versions?  Or what I need to pay for an update fix these bugs?

  Seems that something got corrupted with this VI. Things to copy on a cool VI and things should be OK.

  See also this recent report of a similar problem.

• a problem with one of the files in the TestStand\AdapterSupport\LabVIEW directory

  When looking at the module a LabVIEW VI called for TestStand, I get the following message:

  A problem with one of the files in the TestStand\AdapterSupport\LabVIEW directory.  Please reinstall or repair.

  I made the mistake of cleaning C: in my computer.  Clean the C:\National Instruments downloads

  Why would someone put bits of applications or modules, etc. in such a directory?

  I'm not too crazy about restoring 11FR in this folder.  It's just crazy!

  If anyone has encountered this before?  No "easy"? outside re - install TS...

  Side note: I do not touch anything in the \Program files. National Instruments\TestStand\AdapterSupport\LabVIEW

  What version of LabVIEW and TestStand do you use?

  In 2012, TestStand, this directory is mapped to:

  C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 2012\AdapterSupport\LabVIEW

  Have you tried mass compiling the screws in this folder?

  I had to create a new 'TestStand - default values XX.llb"file, where XX is the last version of LabVIEW you use, but I have not seen this message before.

  Good luck

  PH

• LabVIEW 2010 FPGA: problem with the mean and the variance Subvi

  The Subvi 'Average, Variance and standard deviation' seems to not work properly. The calculation of the average value is ok but std and variance are bad and the results change with representation in an unexpected way. Everyone knows about this problem? Is there a problem with the use of this function?

  Thank you

  Andrea

  Hello Andrea,

  Here is a test for the configuration of your VI (entered I16, 16 samples), saved in LabVIEW 2010 SP1 and the new Subvi. It is relatively simple to adapt it to other configurations, but it does not reconfigure several nodes and constants on the diagram. Let me know if it will work for you.

  Kind regards

  Jim