Labview 8.6 to 8.5 conversion

Similar Questions

• LabVIEW Manager (labviewv.lib) target RT Linux support?

  Hello

  I have a cRIO running Linux RT (x 64). I would use a 3 rd-party to a VI RT C++ library. The library has features that are not compatible with the library function node call LabVIEW (for example, functions that accept a C++ string entry). Under Windows, I would create my own wrapper library using LabVIEW Manager functions to perform a conversion between the types of C++ and LabVIEW.

  Is it possible to do the same thing for RT Linux targets? Is there a version of labviewv.lib (32-bit or 64-bit) for Linux targets? (I don't have a Windows development machine)

  Thank you!

  Hello

  You don't need labviewv.lib intall on your linux RT target. Simply develop your application using Labview MAnager on Windows functions and then deploy it on Rt Linux target.

  Best regards.

• By specifying the screen coordinates in printf using LabView RT 2009

  According to the 2011 help in LabView documentation 'Printf (Manager of LabVIEW function)", the character of the conversion of 'q' is supposed to refer to a point. The actual help text is "q Point (passed by value) as %d, %d, representing the coordinates horizontal, vertical. It is a valid conversion for LabView RT 2009 character? If so, then someone has an example of using these characters to print at line 10, column 1 on the console? I tried a lot of combinations like: printf ("% dqTest Row", (10.1)), etc.

  LabVIEW Real-time has not intrinsically a "console" - it has an "output stream.  There is no API added to allow you to jump all over the console in native mode (don't cross the streams) - you can't even do it with the functions of Manager of LabVIEW (literally, it prints a point in this place of pixel, not text).

  Now, I tell you this, but if you happen to have a target with a video memory (like a PXI system, certainly NOT a cRIO or PCP) and you happen to know the address of where the video memory is on your 0x0B8000 system, you can directly write ascii characters on the screen specific areas - just as they did in the days of DOS.

  #include 
  #include 
  
  void VGAChar(unsigned int row, unsigned int col, char c, unsigned char attr) {
      static volatile char *video_mem = (char *)0x0B8000;
      unsigned int pos = ((row * 80) + col)*2;
  
      video_mem[pos] = c;
      video_mem[pos+1] = attr;
  }
  
  void VGAString( unsigned int row, unsigned int col, char * str, unsigned char attr) {
      int i = 0;
      while (str[i] != '\0')
      {
          VGAChar(row+(col+i)/80, (col+i)%80, str[i], attr);   /* print each character */
          i++;
      }
  }
  
  int main (void)
  {
      char buffer[ 100 ];
      sprintf( buffer, "Hello, my DOS world!" );
      VGAString( 10, 10, buffer, FOREGROUND_BLUE | FOREGROUND_RED );   // prints in PURPLE at ROW 10, COL 10.
  
      return 0;
  }
  

  Of course, I don't condone this and it is certainly NOT taken in charge (and only works on targets based on the PharLap with a video console), but there is a lot of fun.

  -Danny

• Convert a typedef enum in a non-typedef enum?

  Is there one had to ride an enum that is connected to a typedef for a typedef no had version?

  I have a case structure (defined by typedef enum case) which also includes an event of default. In the default case, I convert the enum to a string and parse the string for a particular value. This as well as the numerical value of the enum element is the kind of assistance until a case of 'real' is set for this item. Now the conversion and analysis could be used in another structure of business I had. But to make a universal Subvi the enum must be NOT typedef. LabVIEW does not make the automatic conversion here and a 'type cast' loses the value enum completely. Is there a way to remove the connection to the typedef enum programmatically before transmitting it to the Subvi?

  The entrance to your Subvi make a Variant. You can get the numeric value of it by the conversion of a numeric type; You can also get the list of corresponding channels using GetNumericInfo in vi.lib\utility\VariantDataType. Combining these you should get the information you want.

• update version

  I hope this is the right place. I try to use some more older (v12? its telling me) VI with tiara by using the run Labview server.  However, the execution server dislikes what age they are. I was wondering, if I posted, someone could open and save them to v13?

  I do not have Labview, and we don't need. These VI were actually taken from http://www.boulder.nist.gov/div838/theory/refprop/Frequently_asked_questions.htm#LabViewApplications

  I'll post it here just in case someone is bored and can help with this.

  (For anyone performing a generic web search, this is the NIST RefProp VI for Labview.)

  Jump to version conversion Commission and someone should help out you.

  http://forums.NI.com/T5/version-conversion/BD-p/VersionConversion

• change the text unit-error bounds 1128

  Hey everybody,

  I develop a VI that uses the native power of LabVIEW units to do all the conversions of my numbers.

  Here my question, once variables are defined for a control when editing can I change the text of unity to something not related to execution in order to prepare my indicator for a different signal? For example, lets say channel 1 is a temperature for Test1 so programmatically feray Cdeg conversion and back without problem for LabVIEW. For Test2, the same VI is used, but now the channel 1 is a pressure. Programmatically change my of feray indicator units now a unit of pressure psi, atm or bar? I am getting error 1128 "input unit is not compatible with the device current." even if the device is correct when it is entered at the time of publishing.  Any thoughts?

  Thank you
  Craig

  Hi Lucie,.

  No, you cannot change the type of unit when running. This will be fixed at compile time. You can modify other representations of the same physical property (as the Pa to the bar or some obscure lb/po2 of pressure).

  An old trick when using units:

  You can use '$1' as a control unit. Using a function to "Convert the unit" also set to "$1"you can then strip the unit." If your Subvi accepts any control unit connected-, but that does not solve your problem of perticular

• float to bytes conversion using c code in labview

  Mr President, I made the taste of the float to bytes conversion using type cast in labview. now I want that conversion using the code c. means I want to know that how labview can suport code c. farmula node is not suporting my code which is working wel in labwindows. kindly help me on this subject so that my skil can be improved using labview

  The node of the formula as its name suggests is to facilitate the access of the algebraic formulas in text form and uses a C like syntax, but is in no way a fully featured parser/compiler. It supports only a subset of the syntax of C for obvious reasons. Why would you need to implement entire code C in LabVIEW for LabVIEW program supports the same functions and to do it with LabVIEW nodes, you will always have better performance you can get in the formula node.

  If you have real C code you wish to call in LabVIEW you use the node form but create a DLL from it and call it via the node library call.

• Identification and the conversion of an old version of LabVIEW

  I have an old program .vi I try to access to and run now. I don't know what version of LabView, it was written, but I don't know that he came on a Windows 95 computer.

  Any Suggestions?

  Huntley will

  If you try to open it, and you get an error, the message tells you what version it is unable to convert. If it fails, post to the Jury of Conversion of Versionthat you see marked at the top of the main page of LabVIEW.

• 2651 a conversion of TSP Script for LabVIEW

  Hello

  I have a problem on the conversion of all TSP scripts that contain functions and appeal for the end loops. I'm new to the TSP with models of trigger scripts. I used the Script Builder (TSB) Test tool and am able to run any TSP and generate raw data, but I don't seem able to convert most of the codes in the command of LabVIEW VISA or loader LV TSP TSP and run it to generate data... I can't find any tutorial or examples how to do it.

  Let's say that... Use the example of KE2651A_Fast_ADC_Usage.tsp (pulse) and I'll just focus on the portion of function CapturePulseV (pulseWidth, pulseLimit, pulseLevel, numPulses). I have seen a few examples of LV that says loadscript myscript and close on endscript.  I did a lot of different approaches, and I kept getting errors in particular the print function that I am not able to generate data through LV by to read the data in the buffer to inside the instrument. Some approaches, I have had no errors but no data... Some approaches, I got error-285.

  The part of the code TSP pulse that works in TSB is here (I'm not including loadscript and endscript) and what is the RIGHT way to modify the code for LabVIEW and run it and obtain data? Thank you:

  function CapturePulseV(pulseLevel, pulseWidth, pulseLimit, numPulses)
      if (numPulses == nil) then numPulses = 1 end
  
      -- Configure the SMU
      reset()
      smua.reset()
      smua.source.func            = smua.OUTPUT_DCVOLTS
      smua.sense                  = smua.SENSE_REMOTE
      smua.source.rangev          = pulseLevel
      smua.source.levelv          = 0     -- The bias level
      smua.source.limiti          = 5     -- The DC Limit
      smua.measure.autozero       = smua.AUTOZERO_ONCE
  
      -- Use a measure range that is as large as the biggest
      -- possible pulse
      smua.measure.rangei         = pulseLimit
      smua.measure.rangev         = pulseLevel
  
      -- Select the fast ADC for measurements
      smua.measure.adc            = smua.ADC_FAST
  
      -- Set the time between measurements.  1us is the smallest
      smua.measure.interval       = 1e-6
  
      -- Set the measure count to be 1.25 times the width of the pulse
      -- to ensure we capture the entire pulse plus falling edge.
      smua.measure.count          =
                      (pulseWidth / smua.measure.interval) * 1.25
  
      -- Prepare the reading buffers
      smua.nvbuffer1.clear()
      smua.nvbuffer1.collecttimestamps    = 1
      smua.nvbuffer1.collectsourcevalues  = 0
      smua.nvbuffer2.clear()
      smua.nvbuffer2.collecttimestamps    = 1
      smua.nvbuffer2.collectsourcevalues  = 0
      -- Can't use source values with async measurements
  
      -- Configure the Pulsed Sweep setup
      -----------------------------------
      -- Timer 1 controls the pulse period
      trigger.timer[1].count          = numPulses - 1
      -- -- 1% Duty Cycle
      trigger.timer[1].delay          = pulseWidth / 0.01
      trigger.timer[1].passthrough    = true
      trigger.timer[1].stimulus       = smua.trigger.ARMED_EVENT_ID
  
      -- Timer 2 controls the pulse width
      trigger.timer[2].count          = 1
      trigger.timer[2].delay          = pulseWidth - 3e-6
      trigger.timer[2].passthrough    = false
      trigger.timer[2].stimulus       =
                  smua.trigger.SOURCE_COMPLETE_EVENT_ID
  
      -- Configure SMU Trigger Model for Sweep/Pulse Output
      -----------------------------------------------------
      -- Pulses will all be the same level so set start and stop to
      -- the same value and the number of points in the sweep to 2
      smua.trigger.source.linearv(pulseLevel, pulseLevel, 2)
      smua.trigger.source.limiti      = pulseLimit
      smua.trigger.measure.action     = smua.ASYNC
      -- We want to start the measurements before the source action takes
      -- place so we must configure the ADC to operate asynchronously of
      -- the rest of the SMU trigger model actions
  
      -- Measure I and V during the pulse
      smua.trigger.measure.iv(smua.nvbuffer1, smua.nvbuffer2)
  
      -- Return the output to the bias level at the end of the pulse/sweep
      smua.trigger.endpulse.action    = smua.SOURCE_IDLE
      smua.trigger.endsweep.action    = smua.SOURCE_IDLE
      smua.trigger.count              = numPulses
      smua.trigger.arm.stimulus       = 0
      smua.trigger.source.stimulus    = trigger.timer[1].EVENT_ID
      smua.trigger.measure.stimulus   = trigger.timer[1].EVENT_ID
      smua.trigger.endpulse.stimulus  = trigger.timer[2].EVENT_ID
      smua.trigger.source.action      = smua.ENABLE
  
      smua.source.output              = 1
      smua.trigger.initiate()
      waitcomplete()
      smua.source.output              = 0
  
      PrintPulseData()
  end
  
  function PrintPulseData()
      print("Timestamp\tVoltage\tCurrent")
      for i=1, smua.nvbuffer1.n do
          print(string.format("%g\t%g\t%g",
                              smua.nvbuffer1.timestamps[i],
                              smua.nvbuffer2[i],
                              smua.nvbuffer1[i]))
      end
  end
  

  I finally solved it myself! I first create support shell, according to the documents, but the problem was with functions of scripts but I solved by introducing VISA separate, feature writing and THEN retrieve the data from the instrument directly by VISA buffer read more. I did TSP_Function Script Loader that allows simply copy/paste codes teaspoon (any * .tsp) of: TSB program or incorporated into this type of function and loader.vi, name (parameters), defined by its own pasted script then it will generate RAW files directly in the array of strings that can be broken into pieces or restructured into what you want as for the graphics, etc..

  That's all I really need to do, I can do codes of tsp in LV and get the data off of it easily via the function defined. Now, this Loader.VI behaves in the same way that TSB keithley-made program I use.

  Here I add Loader.vi Script TSP_Function (in LV 2011 +).

• conversion of LabVIEW 8.5 in 2012

  Hello

  I'm trying to convert my application written in LabVIEW 8.5 with NOR-traditional Daq OR DAQmx LabVIEW 2012.

  You can find the code as an attachment

  Thank you

  Are you aware of that very specific baord is available for applications for upgrading / downgrading.

  http://forums.NI.com/T5/version-conversion/BD-p/VersionConversion

  In addition, a VI that is created in LabVIEW 8.5 version can be opened in the 2012 version & later recompile (upgrade) it.

  Edition: Find VI improved with DAQmx functions in the attachment.

• LabVIEW file conversion toolkit

  I have a lot of files in the version of Labview 5.1.

  I can't open it in my version of Labview 8.5.

  Source code in labview 5.1 should be changed after the current requirement.

  I so need a run conversion toolkit labview.

  Attach the file to download.

  I use the windows xp operating system.

  Please, help me at your earliest.

  Hi grugh,

  did you read what I wrote?

  There is a thread upconvert to such request...

• Conversion of LabVIEW 5.1 VI LabVIEW 8.0 or newer

  Hello

  Anyone have the opportunity to open a Labview 5.1 VI and could convert to a newer version for me?  I currently use 2010 and have access to 8.6 as well.  Thanks in advance!

  -Adam

  Here's a conversion to 8.2.

  Be aware that, for example, the temporal delay code is not healthy and probably belongs in the threads of Rube Goldberg .

  See if you can simplify it...

• Required conversion from 2014 to 2012 Labview LabVIEW

  Someone help me kindly to ge the attached file converted to a 2012 version of Labview. Currently, it is in 2014 of Labview.

  http://forums.NI.com/T5/version-conversion/BD-p/VersionConversion

  There is a forum just for that.

• Conversion/appeal of an application created with CVI in Labview

  Hello

  I have a third-party application code created with labwindows CVI (attachment: scissor lift CVI code.rar) which is used for our control of movement of CT scans. I want to serve the Labview 8.6 my main software for data acquisition and software interface for my development. My idea is to create a dll from this CVI code and called the dll with Labview library import function is shared.

  My problem is that I am no expert in CVI programming if anyone can help me how to create a dll from this code? or any other suggestions to implement this conversion?

  Code CVI attached for reference.

  Thank you

  Lojius

  A starting point can be found here

• Conversion of files from LabView 2012 to 2011

  Hello

  I'm new to Lab View. I'm stuck with the conversion of this file of LabView 2012 to 2011. Help is highly appreciated

  Thank you

  With respect,

  Jagadish

  double post