Similar Questions

• Had problem with this tut :D

  Hello.

  I want to understand ho to make the text of the flame. I mean text flame really like this tut:http://10steps.sg/tutorials/photoshop/text-on-fire-effect/ but I want to do in illustrator.

  I fount this tut: http://www.ehow.com/how_12030846_make-flaming-text-illustrator.html but I had problem with step 6 in efect coz > transorm and disort > tweak (I invited this tweak in English) are nothing else then move object transform :/

  I want to ask you guys what is the shortcut for the tweak option coz I thikn im using the wrong option but others in this menu drop-down doesn't seem to have good option too when we reading this tutorial.

  Thx for the answer

  See you soon

  There is no shortcut...

  Maybe a picture will help you...

  

  I hope never tutorials if they did not all images. At the very least, an image showing final results.

• Problem with form container tut. 2.1

  Here is my code:
  < mx:Form = "439" x = "10".
  width = "318" height = "349".
  borderStyle = "solid" borderColor = "#d4d4d4."
  dropShadowEnabled = 'true' dropShadowColor = "#b3b3b3."
  shadowDirection = 'right' shadowDistance = "10" >
  
  < mx:FormHeading label = "Contact Information" / >
  < mx:FormItem label = "full name:" >
  < mx:TextInput id = "name" / >
  < / mx:FormItem >
  < mx:FormItem id = "address:" >
  < mx:TextInput id = "address" / >
  < / mx:FormItem >
  < mx:FormItem id = "City:" >
  < mx:TextInput id = "City" / >
  < / mx:FormItem >
  < mx:FormItem id = "State:" >
  < mx:TextInput id = "State" / >
  < / mx:FormItem >
  < mx:FormItem id = "ZIP Code:" >
  < mx:TextInput id = 'postal code' / >
  < / mx:FormItem >
  < mx:FormItem id = "phone:" >
  < mx:TextInput id = "phone" / >
  < / mx:FormItem >
  < mx:FormHeading label = "Room Information" / >
  < mx:FormItem label = 'Date needed' >
  < mx:DateField id = "dateNeeded" / >
  < / mx:FormItem >
  < mx:FormItem >
  < mx:Button label = "Submit" id = "Button" / >
  < / mx:FormItem >
  < / mx:Form >
  
  But the FullName text entry. Am I blind? I don't see my error...

  Looks like the problem is that you are missing the attribute 'label' for the FormItems following the element name. You have 'ID' instead of the label.

• Problem with pointstyle custom

  Hello, I want to create a pointstyle customized for my plots scattergraph. I want to create a rectangel with a black border.

  I have read the following of section http://zone.ni.com/devzone/cda/tut/p/id/10526 and that it really helps.

  But there is a little problem with the black border. The following diagram shows this problem, that the border is only on the 2 sides of my rectangel.

  

  This is my code in my tiny class.

  class BorderPointStyle of Ref: NationalInstruments::UI:PointStyle
  
  {
  
  public:
  BorderPointStyle (void)
  
  	{}
  public: virtual void Draw (Object ^ context, PointStyleDrawArgs ^ args) override
  
  	{
  
  	Graphics ^ g = args-> graphics;
  Rectangle rect_b = Rectangle (0,0,7,7);
  
  	Rectangle rect_i = Rectangle (0,0,6,6);
  System::drawing:pen ^ pen = New System::Drawing:Pen (Color::Black);
  
  	g-> FillRectangle (gcnew SolidBrush (args-> Color), rect_i); Draw the innerarea
  g-> DrawRectangle (pen, rect_b) ;// draw the border
  }
  
  };
  

  Maybe someone has a resolution of my problem

  Hello-

  Your points are currently limited by the PointSize property.  You can change your code as follows:

• Negative results with strain gauges

  When I run my VI the results are always negative. I use the NI9237 with the NI9945. I wired my installation as one quarter bridge. There are three wires from the strain gauge. I went on the wires and I think it's okay / characteristics of NEITHER. Is there something in the MAX that I should be looking. Not sure why the values are negative.

  Thank you

  Harry Stone

  Hi Harry,.

  There are a few things I want to clarify:

  -Traction deformation is positive and compression deformation is negative, what is described a high level in the tutorial below.

  Strain with gauges
  http://zone.NI.com/DevZone/CDA/tut/p/ID/3642

  As strain compression is negative, you would see negative within MAX results if your strain gauge knows any compression. Please keep in mind that a shift can be associated with each transducer, that's why some sensors use a calibration certificate. It is produced by the manufacturer and is provided with the sensor as is the specific sensor. The sensor goes through a testing process to determine its actual response compared to the ideal. In this case, a scale of table can be created to include these values.

  How to do a custom able scale & Automation Explorer (MAX)?
  http://digital.NI.com/public.nsf/allkb/3F6558112FD2C776862575B5004F7F87?OpenDocument

  Not all manufacturers of sensors provide a calibration certificate. Or you can create your own table by placing known quantities of pressure, force, etc. on the sensor and map it to the corresponding voltage, or you can create a linear scale in MAX adjusting the intercept (b) the value necessary to remove any compensation.

  You use the NI 9237 that compensated supports deletion. A null offset is executed with the sensor fixed without load placed on the sensor. Actually, a measurement of voltage is taken and this value is subtracted off the coast of each subsequent measure therefore removing the start offset. This takes up space you creating a linear scale and in doing so manually.

  The two links below show how to use a custom scale created in MAX in LabVIEW, as well as coding the custom in LabVIEW scale to remove the dependency of MAX.

  Acquisition of DAQmx with custom scale
  http://decibel.NI.com/content/docs/doc-3706

  Create a linear scale customized for each channel AI in LabVIEW using DAQmx
  http://decibel.NI.com/content/docs/doc-11136

  I recommend using a task sequence. Input parameters for the information about your strain gauge needed to perform the conversions of strain. There is an example of a measure of deformation in the example Finder LabVIEW (* open LabVIEW * help > find examples) designed specifically for the NI9237 that incorporate deleting the offset and shunt calibration devices. If you do not have external wires connected for calibrating shunt such as cited in this document , you will receive an error. Here is an explanation from the NI-DAQmx help Shunt calibration (start > all programs > National Instruments > NOR-DAQ > NOR-DAQmx help) to help better explain this feature.

  Shunt calibration (adjustment of Gain)
  You can check the output of a measurement system based on a bridge by comparing the measured output bridge with a calculated value if the physical load on the sensor is known. NOR-DAQmx can then use the difference (if any) between calculated and measured values as a factor of adjustment of gain for each measure. You can simulate the application of a load at the bridge by connecting a significant resistance in parallel with the bridge. This resistance, known as a shunt resistance, compensates for the voltage from zero of the bridge. Because the value of the shunt resistance is known, you can calculate the physical load corresponding to the voltage drop of the resistance.

  Use the Shunt calibration perform the Assistant DAQ or DAQmx VI/function to perform a calibration shunt, which defines the the gain setting for a virtual channel. NOR-DAQmx then uses this adjustment of gain when you descale readings from the bridge. Some National Instruments products are internal resistance.

  This may seem like information overload, but I wanted to provide you with a detailed explanation of your understanding, in addition to immediate responses. As a logbook, I recommend that you use the 9237 strain example and use the removal compensation. Negative values are expected for compression and positive for blood. The handy Guide below gives an excellent overview of the strain gauges, which also includes a video.

  Measurements with strain strain gauges: practical Guide
  http://zone.NI.com/DevZone/CDA/tut/p/ID/7130

  Hope this helps!

• How can I configure a port Ethernet NI9792 gateway to communicate with a cRIO CAP?

  Salvation OR engineers,

  I intend to use my gateway NI9792 in the following way:

  1. a single Ethernet port for network connection. That's how I'm developing, download the software and monitor my request through my PC in my office.

  2. the other port to communicate with a cRIO device? If so, how can I do it?

  It seems to be a stupid question, but I really couldn't work this!

  Thanks in advance,

  Luiz

  Good afternoon, Luiz

  Follow the first link to guide the module which can be used and other links to the best part of bore configuration CRIO. For any question, please contact us.

  How to set my time on the NI WSN-9791 or NI 9792 gateway server?

  http://digital.NI.com/public.nsf/allkb/44FA322FAFF8D58D862575BD00591A54?OpenDocument

  Configuration and NI WSN product guide
  http://zone.NI.com/DevZone/CDA/tut/p/ID/8710

  Configure the Ports of double Ethernet on real-time controllers

  http://digital.NI.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument

  video installation and installation CRIO

  http://www.NI.com/SWF/demos/us/cRIO/outofbox/

  Automatic configuration of network for the cRIO-9073 and cRIO-9074 CompactRIO controllers

  http://digital.NI.com/public.nsf/allkb/37C790309A210A748625757000570938?OpenDocument

  Sincerely,

  Mauro Vera.

• Can LabVIEW Embedded for ARM works with any Board or just with a few predefined?

  Hello

  Can LabVIEW Embedded for ARM works with any evaluation committee or just with a few predefined (MCB2300, MCB2400 and EK-LM3S8962)? I ask this question because even if I chose "another processor" in the definition of the new project only 3 options are the corresponding arm of Phillips and LuminaryMicro.

  Thanks in advance,

  Howdy,

  LabVIEW for ARM supports the feature of targets for tier 1 (the mentioned Evaluation Committee) following this schema:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/7066

  But you can transfer to other weapons if you follow this porting guide:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/6994

  The uProcesser SDK is intended for the port of other targets of DEPENDENCE (32-bit, of course) and technically it covers ARM as well. Alternatively, there are the LabVIEW C Code Generator: http://sine.ni.com/nips/cds/view/p/lang/en/nid/209015

• Using measure computing library UL (device USB-1208FS) with CVI

  Hello

  I'm trying to implement the system of company Measurement Computing USB-1208FS (www.mccdaq.com) in our test software tool which has been programmed in Ansi C using the CVI compiler.
  To make the first steps, I am building an executable based on the Ansi C «DaqInScan01.c» example code
  While I have no problem with the compilation of the code, the linker complains with errors shown below. Although the cbw32.lib is registered with my project, ICB seems not to be able to reference the functions of the library.
  What I am doing wrong?
  Is there the CVI samples available to guide me in the first steps regarding this device?
  I use WinXP SP3, CVI is version 9.01

  Thank you for your support

  Hello IEE_newsoft,

  Looking at the screenshot you posted, a recommendation is to make sure that the header file and library with the same name, also have you been able to call the dll or lib successfully in another environment, IE such as visual studio to check there is nothing wrong with the files. Also look at this Developers Zone,http://zone.ni.com/devzone/cda/tut/p/id/3453 it shows you how use a third party dll of CVI and http://zone.ni.com/devzone/cda/tut/p/id/8503 shows you how you can use either dynamic or static linking to call your dll.

  Hope this helps

• CRIO-9073 is compatible with LabVIEW 8.5.1?

  I just got a cRIO-9073 and a cRIO-9074.

  When I set up, both of them appear correctly in MAX.

  When I add them to a project LabVIEW, the cRIO-9073 does not show the target FPGA. The cRIO-9074 shows.

  I'm using LabVIEW 8.5.1, is compatible with the cRIO-9073?

  Thanks for any help.

  Michel

  Hi Michel!

  According to this link, the interface FPGA and Scan of the cRIO 9073 are only supported in LV 8.6 using the NOR-RIO 3.0 driver.

  The link where you can check the compatibility is:

  FTP://FTP.NI.com/pub/DevZone/tut/crio_software_versions.htm

  Good day!

  Oswald Branford

• Problem with the Excel add-in-TDM

  Hi-

  I used the ExcelTDM snap-in on other machines w / no problem, but I tried downloading it on a new computer (w / office 2003, Vista) & the icons do not appear in excel.

  I tried to follow the instructions on this page: http://zone.ni.com/devzone/cda/tut/p/id/5874

  I am stuck at step #3 b/c the ExcelTDM.dll file isn't the case on the computer.  Is it possible that the add-in is not download correctly?  I tried uninstalling and reinstalling the add-in twice now, with the same results.

  Any halp would be appreciated!  Thank you!!!

  Erin

  Hi ErinH,

  We want to confirm that you get the latest installer from the web download of the first http://zone.ni.com/devzone/cda/epd/p/id/2944 .

  Then, you will notice at the bottom of the download page there is a trick:

  After installing the TDM Excel Add-In in Microsoft Vista , you need start Microsoft Excel at least once by using administrator privileges.

  So if you use the Add-In in Vista, you can disable the UAC (User Account Control), or right-click on Excel.exe and "run as Administrator" for the first time.

  Good luck!

• Data acquisition tool NOR-DAQmx with Matlab R2012a

  Hello

  I'm trying to control NI USB-6211 of Matlab 2012 using NOR-DAQmx Data Acquisition tool:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/3005

  I'm working on win7 64 bit. And I see the device AND Measurement & Automation Explorer.

  The tool does not work: DAQ_Demo_Browser do nothing. And I got the error "unexpected or unbalanced parenthesis or support" of AcqNUpdates_nonUI.m

  What is the problem?

  Thank you and best regards,

  Arthur Shulkin

  Hi Arthur,.

  Tools OR DAQmx for Acquisition of data with the Software Inc. MATLAB® from The Mathworks, supports up to the 2008 version of the MATLAB® software.  In order to use our products DAQ Multifunction with MATLAB® software, you could get back to 2008 or earlier, or instead use the Data Acquisition Toolbox provided by The Mathworks, Inc.

  Another option would be to import your ".m" files in a node MathScript in LabVIEW and use the functions of NOR-DAQmx everything in the LabVIEW development environment.  For more information on the Module LabVIEW MathScript, you can consult the information available on this link:

  Inside of the LabVIEW MathScript RT Module

  MATLAB® is a registered trademark of The MathWorks, Inc.

  Katie

• Block in the amplifier with high material sampling rates no DSA

  Hello

  I intend to use the starter kit OR locking amplifier to detect a harmonic signal of 400 all about. I intend to use the PCI-5105 digitizer (I don't him have not bought until now, but I will soon). The start kit lock, I downloaded and unpacked the files and was hoping to give it a try with an NI USB-6363 however the vi does not open because it says that there are a lot of sub - VI lack (Subvi read.vi I HAVE... clear.vi, etc.). The LockinDemo.vi also seems to use NI 4472 as a default material. My questions are if the lock-in-amplifier starter kit OR 1) can be used with PCI-5105 and 2) cannot vi missing of the be downloaded from somewhere or be replaced by other blocks on mine?

  Thanks in advance for any help

  Benoit

  Hi Benoit,.

  First to start development with LabVIEW Real-time, you can check if your system supports LVRT. You can make use of RT disk utility that will test your system as shown in this article: http://digital.ni.com/public.nsf/allkb/9209361E17708D548625744A007FF353

  We have lists of equipment belonging to systems tested here: https://decibel.ni.com/content/docs/DOC-10692 and you can always check for the other hardware compatibility here: http://zone.ni.com/devzone/cda/tut/p/id/8239

  We do not have a driver available for the PCI of pledge cards but if these cards use VISA calls, you can develop and LVRT recognizes your card by following the KBs:

  (1) acknowledge the third peripheral part with LVRT: http://zone.ni.com/devzone/cda/tut/p/id/3142

  (2) expand LVRT peripheral Driver PCI: http://zone.ni.com/devzone/cda/tut/p/id/3251

  I hope this info helps!

• 220VAC measured with CompactDAQ?

  Hi all

  I'm building a testbed automated, where I need to measure both single-phase (120 and 277VAC) and two phases (208/240V ca... I am aware that nobody calls him two phases, but that's what you are actually measure... anywho) I have single phase works fine as seen in VI 'DAQ_Sample3', but when I try to apply the same logic to two legs of power my output is only sends me data for a leg.   I went and added two other channels so it measures both legs and two amp clamps... I can connect the DAQ assistant for a graphical output and it shows all four readings, but when I'm trying to transition to power VI it will only calculate one leg.  I have attempted to combine the signals from several different ways, but have not had a bit of luck to get a result that passes the test of reasonablilty... someone who knows a bit more on this taking a glance at the VI I for two can live (DAQ_Sample4-2ph) and point me in the right direction?

  Thank you!

  Chad

  OK, well I finally realized what was going on... Apparently If connect you single phase (one leg and one neutral (120/277VAC) or legs (208-240 VAC) you must measure between a0 and a1 (differential measurement) and not on each leg to land is represented here...) http://zone.NI.com/DevZone/CDA/tut/p/ID/8216  For some reason any if you measure single phase 208-240 VAC and try to measure each leg down the numbers aren't right. I am now in a position through a channel and my numbers are dead on with my parser.

  As a side note, that power might want to add more information to this series of videos... http://sine.NI.com/NIPs/CDs/view/p/lang/en/NID/208111 and comment on the actions of power for all single phase (120/277VAC and 208-240 VAC) should be taken on a single track on the module 9225.  .. .or include a wiring diagram specific for various applications.

  A big thank you to all who tried to help!  I hope that this thread will save someone some time and frustration.

  THX

  Chad

• by deployed/launched RT App with "Open FPGA" no executable program

  Howdy-

  According to the instructions in these links:

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

  http://zone.NI.com/DevZone/CDA/tut/p/ID/9640

  and others I've read, I wrote a PC-side VI which FTPs a Source of RT dist. During my cRIO (9076), then use it "Run VI' method to launch the application.»  For test purposes, the RT VI has a call option to a simple VI FPGAS:

  

  With the FPGA disabled call, everything works fine.  With the call of the FPGA, the method of "Run a VI" in the code PC side returns error 1003: "the VI is not Executable.

  The cRIO VI works in interactive mode (front) with and without the call FPGA.

  Any ideas why this happens?

  I'm under LV 2011 on the PC and OR-RIO 4.0 on the cRIO.  I've included with this post project files if it can help.

  Thanks a lot and have a nice day.

  Well, it seems that I had accumulated a bad bitfile associated with the FPGA VI (there were 2 of them in the bitfiles folder, where only should have one).  The solution was to remove the old bitfiles and rebuild the FPGA of the project part.

• No problem with the enumerations of Drivers of Instruments

  I noticed in the National Instruments standard guidelines driver whenever a reference to a control that would have different options based on the test came, a ring selector was recommended and a listing... Is there a good reason to stick with the selectors to ring and not use enum? For example, one of my drivers has 4 different channels CH1, CH2, CH3, CH4... An enumeration settle well here because I can use value of the text-based config file format and create the appropriate enumeration value I want.

  "CH1" (text)--> form to value--> CH1 (enum value)

  Thanks for your help

  Are you referring to this document: http://zone.ni.com/devzone/cda/tut/p/id/3271 ? There is no explicit mention on is not the use of an enumeration. I think that it is essential to use some for control menu to facilitate the selection of the function. In some cases, a ring can be more convenient than an enum. For example, if a selection requires the actual value to be something other than the normal value of the control. Example, the selection of "DC" requires sending a value of 101 to the instrument instead of 0. In this case a ring would be more convenient because you can set values for the elements of the non-sequential ring.