LabVIEW programmer in the Minneapolis area desired

Similar Questions

• How the resets are generated in LabVIEW for FlexRIO

  All,

  My background is VHDL and Verilog for FPGA and ASIC implementations.  I guess LabVIEW has a point, an only synchronous reset to all of its logic.  I create a design that is going to be sections of VHDL IP, through IP integration node is instantiated. When writing to the top of my spec, I need to describe how a reset is spread to all the flops in the design that will be peer-reviewed of accuracy of the results. I need to understand exactly how LabVIEW handles resets to other areas of the clock.

  A simple case is the following: I have a 50 MHz external source synchronous data interface and will be a limited treatment of data in this area of 50 MHz using an IP integration node. This IP is designed to have the flops to reset synchronous on the 50 MHz clock.

  Separately, I have my most of my treatment and storage to the host (via DMA FIFO) in a field of 100 MHz clock, derived from the clock of 40 MHz I base I must transfer data from 50 MHz to 100 MHz using a FIFO.  This treatment at 100 MHz contains a floating-point operations that are reset to zero synchronously to the field of 100 MHz.

  In this scenario, you see I have two areas of clock with synchronous resets.  I need to understand how LabVIEW FPGA create reset signals which are entries to my integration IP nodes, in order to understand if I need to incorporate any reset synchronization within my VHDL circuits.

  Thanks for any help and if you need further details or context, please let me know and I find out additional details.

  -Jim

  Hey Jim,.

  So, option 2 then... in this case, you are looking at a signal of asynchronous reset and must realize in your VHDL similar to the following to ensure that your resets are say synchronously.

  

• Join us for the Q2 2009 Minneapolis area VMware Users Group meeting-5th edition Forum

  Join us for the Q2 2009 Minneapolis area VMware Users Group meeting-5th edition Forum

  Jason Boche, head of Minneapolis area VMUG - Email: [email protected]

  Thursday 28, may 2009 04:00 - 18:00

  04:00-04:30 General Affairs, open floor discussion

  04:30-05:00 presentation: Bill Oyler, St. cross Solutions: "ISCSI and NFS extreme Performance Tuning»

  Break from 05:00 - 05:15

  05:15:05: 45 presentation: Bill Oyler, St. cross Solutions: "Top 10 new features of vSphere/ESX4".

  05:45-06:00 Q & A, prizes, closing

  06:00-07:00 St. Croix Solutions Happy Hour to the 'Local' (931 Nicollet Mall, Minneapolis, MN 55402 612-904-1000)

  Stick around to win prizes from the gate of St. cross Solutions, technology dynamics and VMware.

  (Please bring business cards to enter your name in the prize drawings)

  Sponsors of the meeting:

  Location and snacks provided by St. cross Solutions

  •      http://www.stcroixsolutions.com/ -Providing innovative, cost-effective and easy to manage COMPUTER solutions

  Prizes provided by St. Croix Solutions, dynamic Technologies and VMware

  •      http://www.stcroixsolutions.com/ -Providing innovative, cost-effective and easy to manage COMPUTER solutions

  •      http://www.vibrant.com/ -Provide Technology Solutions around the world

  •      http://www.VMware.com/ -Virtualization Solution more innovative on the planet never

  Geographical area:

  Minneapolis Convention Center (room 205AB)

  1301, 2nd Avenue South

  Minneapolis, Minnesota 55343 USA

  Phone: 612-335-6000

  VMware User Group Event Registration (registration coming soon):

  http://www.VMware.com/resources/communities/usergroup/events.html

  Join VMware User Group (subscribe):

  http://info.VMware.com/forms/UserGroupSubscribe?session=Minneapolis

  
  
  Jason Boche, vExpert [i] [/ i]

  [boche.net - VMware virtualization evangelist | ] [ http://www.boche.net/blog/] [/i ]

  [VMware communities user moderator | ] [ http://www.vmware.com/communities/content/community_terms/] [/i ]

  [Minneapolis area VMware User Group Leader | ] [ http://communities.vmware.com/community/vmug/us-central/minneapolis] [/i ]

  Beautifully chiselled to so with the Forum of virtualization in the same place, intentionally no doubt.  Well done!

• This LabVIEW programmer needs to know

  Hello guys...

  I'm working on labVIEW for 1 year last on mine.

  If I have problems I will post my questions in the Forum of NOR.

  But I don't know that a small drop of sea water...

  So what should a labview programmer should know?

  In short, how avoid the 10 screen wide spaghetti complete code of the structures of the sequence, local variables and the race conditions

  Also I advice take you a look at the certificates of NOR and the "learning curve":

  http://www.NI.com/white-paper/13120/en/

  http://www.NI.com/training/certification/

  http://forums.NI.com/T5/certification/BD-p/certification

  Edit: perhaps, I would just add a few points that I usually have to keep in mind during the phase of a new project of planning:

  • Choose the right framework or model based on requirements
  • Keep in mind how to get and set values - indicators and controls. If possible, use the cable to transmit data. Keep in mind what's OK to do with local variables (for example updating a control), and which should be avoided (usually) (read/write indicators for example). If you cannot use the wire to go directly to information (parallel loops), learn the correct use of notifiers, queues, UserEvents, etc...
  • who will use the code (it is very important, you need a totally different approach if you develop for yourself, or others who are not programmers and perhaps even do not know the physical part of the system...)
  • GUI always be responsible. Avoid bad habits (longer time running things in the GUI event loop).
  • Avoid the overcrowded façade: use pop-up windows for the settings, etc. That the user don't need to see always.
  • Error handling! It is very important to make a robust error handling strategy: for example if one of your HW components creates an error, your application cannot just stop everything. Handle the error, close properly all HW and file references (do not forget if you don't properly close a file, you can lose a LOT of data : file write is buffered memory RAM). Also record the error information to a log file.
  • If you need to make an EXE or installer: use a configuration file to store the user's changes: If the user changed the colors (width, etc.) a chart/graph, store this information in a configuration file that you load at the next startup of the application.
  • Automatic detection equipment (or users the possibility to modify the port/channel): what happens if your application moves to another PC (numbering changes COM port, etc...)? Your application needs to adapt to the changes of HW.

• Link to the plot area slider

  Hello

  I'm having a problem with the cursor in a plot of intensity. I use two slider in the plot of the intensity and using these cursor position in my program. The input file is a 2D array and size of the file (table) differ from one experiment to another. Sometimes, when I load my file the cursor moves to a value of previous file and is so not visible in the plot (because the previous file can have larger size). Is there a way related to cursor to tell certain position (as in the center of the plot or half the value of size X and y axis). So in summary, I want that when I load my 2D cursor file in the plot of the intensity must be at a certain position depending on the size of the axes X and Y - but he should be able to freely slide so I can move and use the cursor position using node property to calculate other values.

  BTW, I'm using Labview 8.2

  Thank you

  Yogesh

  Just write the position of the cursor to move the cursor to the desired coordinates. For example if your new 2D matrix is 50 x 50, move to 25.25.

  Later, you can intereactively move elsewhere as before.

  You must also disable scrolling cursor (Right-Click Advanced...... Graphics Scroll cursors). This way you will not be able to move the curor outside the limits of the current area of the field.

• A project that I created is no longer works.  All video clips .mpg who ask to be reimported, and when I try to import from its original folder, all the files are slim.

  I currently have iMovie 10.1.2 and OS 10.11.6.  All except a video clip in a compilation of long hours are black with an exclamation mark.  They have the error statement, that the file is missing, re-import the original source media.  The clips are all .mpg and had imported fine when I created the film project of the month of May.  When I try to use the function "Import Media" drop, and I go in the folder on the desktop files located in, all the original .mpg files are low.  The two pictures that were in the project appear on the lower part.  Oh, and I did all that stored on the cloud.  I also wanted to start a new project, part II, but all the source files show a similar dim for all .mpg files.  Apple decided not to allow the .mpg files in iMovie?  If so, what is my next step?

  iMovie accepts more mpg files. The easiest way to work with them is in the finder do a right-click on the mpg file and select "encode the selected video files. In the dialog box that appears, choose the desired conversion. The converted file appears in the import iMovie window, and you can import it.

• LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs is not found. Open the VI in LabVIEW by using the file > > open and make sure it is executable.

  When you try to run a sequence on a deployment computer I get this error. When I pass the adapter in the system of development the problem disappears however I don't have the luxury to keep the full Labview development on the test computer. Is there a fix for this problem and what is the cause of this error. This is the software and versions that I use. It seems that the vi which are broken using Invoke and nodes of property in their breast, I don't know if this is a coincidence. It seems that it is more related to invoke than the property node node. Any help is greatly appreciated. Why is it that everything works fine until you try and deploy it on a test computer. This is not the first time that I had these problems using Software Instruments of the Nation.

  LabVIEW 8.2.1

  TestStand 4.0

  I solved the problem. I had a couple of files with the same name stored in 2 separate places in the 8.2/vi.lib a Labview has been found in vil.lib/printing and the other was found in the vi.lib/addons/vi.lib/printing. I don't know how it has been duplicated, but since I deleted the vi.lib file in the addons directory there are no more problems.

• [BUG] TestStand 2013 receives corrupt data to LabVIEW adapter if the cluster contains waveform array

  Hi all

  I am having trouble with the corruption of the data. My minimal test case is below.

  I have a VI that returns an array of clusters. My TestStand sequence simply call this VI and connects to its output:

  

  When I run the (with my open VI) .seq file, I can see the update of the Panel before LabVIEW with expected values:

  

  However, TestStand receives all these values. Waveform bays have the correct values, but everything else is empty / null:

  

  If I delete my typedef waveform table, all elements of the cluster are correctly registered by TestStand.

  I've attached an example of test (2013 TestStand, LabVIEW 2013) case.

  Any ideas on how to make it work?

  Hey JKSH,

  Thanks for the detailed on this report. I looked into it a little bit last week.

  I think that it is closely related to the 206892 of CAR, which describes a problem where data will not appear on the report unless a property or variable is specified for the output waveform parameter. However, this does not completely cover your case, because you see incorrect digital data in the row with the waveform of your cluster. I filed 462209 CAR for that matter, and we will investigate it more thoroughly.

  This problem only affects data that appears "below" the waveform in the cluster. In the case of the sample, if you put the waveform as the last element of the bunch, I think that it works correctly. I know that your real data could be more complex than this example, but this workaround solution would help in the meantime? You could also consider separating the waveform of the rest of the data, that would probably work too.

  As I said, please let us know, and it is classified in our system now for a developer to investigate the matter. Please let me know if solutions are not appropriate for your application, we would be happy to know a little more about your overall use case order to work around the problem.

• [Q] can Vision track multiple objects in the same area - objects that might cross?

  Hello

  Sorry for this long title, but this is my question.

  Can Vision track multiple objects in the same area - objects that could cross?

  Because I'm able to do, extraction of XY, but it seems that "IMAQ County objects ' don't follow framework after but framework opposed, but extract the coordinates XY always in the same way, as for example from top and whenever he sees an object, it retrieves the XY, but if the objects pass through (then it will extract XY without worrying that the objects was the earlier but just based on"scan from top to bottom").

  That's why I open this topic in the forum of Vision no part: http://forums.ni.com/t5/LabVIEW/Sort-XY-by-closest/td-p/2440428

  Thank you

  Sébastien

  Thank you for your response.

  My problem is that we work with very small insects and the shape/color is the same for all.

  Then the solution is: Let's wait for "IMAQ County objects 3 ' then .

  Thank you

  Sébastien

• On Windows Seven, how the LabVIEW to deploy the ws2_32.dll on my target right?

  Hello

  On Windows Seven, because ws2_32.dll is cited as a "KnownDLLs" (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs) when LabVIEW is making my custom DLL which depends on ws2_32.dll, he deploys the system32 DLL ws2_32.dll instead of the 2012 LabVIEW RT image, ws2_32.dll, causing dependencies error displayed on my lens... And it is not possible to change the "KnownDLLs" list because it is a powerful mechanism of Windows System.

  I noticed that on Windows XP, ws2_32 isn't in the "KnownDLLs" list and I thought everything would be fine (I have not tried).

  To solve the problem temporarily, I changed my DLL custom so that it only depends on wsock32.dll, but this is not satisfactory for me...

  Could you help me?

  Thank you for your answer, but I'm sure that RT de NI LabVIEW 2012 supports the WinSock2 API as the ws2_32.dll is located in the directory "C:\Program Files (x 86) \National Instruments\RT Images\Base\9.0" and "2012.exe DLL Checker" program seems to confirm.

  I did a few test since my first post and I have solved my problem:

  Warns we LabVIEW to automatically download the dll in the target (and download the bad ws2_32.dll), I downloaded manually with FileZilla right DLLs (for example the ws2_32.dll located in the directory... Instruments\RT national Images\Base\9.0) in the directory system/nor-rt/system of the target RT PXI. Now, when my program according to ws2_32.dll in the target, he concludes that the dependencies are already resloved and all transfers LabVIEW is fine!

• Input module of data acquisition can be read by two or more LabVIEW vi at the same time % 3F

  I use the DAQ palette in LabVIEW to read the virtual channels of the input data acquisition module. I've done several VI who read many entries of three modules of simulations. The problem appears when I run two or more VI´s reading entries from the same virtual module (for example. first.VI module 1 input ai0 and second.VI bed ai0 entry module 1 bed), when this happens the next errors are shown:

  Error-50103

  Platform AND Services: The specified resource is reserved. The operation could not be performed as indicated.

  and

  Error-200022

  Resource requested by this task has already been reserved by another task.

  It's worrying because I want to get the DAQ chassis and some modules, but if this problem is present with physical equipment my application may be unnecessary. This means that entry module only can be read once at the time?

  I m using global variables in each Subvi to share data with main VI, however, I found the solution in a different way... I just changed to single channel and dbl sample playback mode, so I Don t need to clean up the task of reading in my subVI´s, the zeros isn´t problem here, and the six subVI´s work at the same time!

  Thanks for the tips!

• How to use Labview for measuring the reflectance at different wavelengths automatically

  Hello!

  I'm using labview to communicate with MS257 (a monochromator). If I do not use Labview, I have to use the hand controller (set a wavelength from 300 to 1100 under a grating (a total of four grids).) It takes a lot of time. So I want to use labview to realize the automation. But I don't know how to do, I still can put only a wavelength as a command for MS257, not making any difference.

  Does anyone know how to deal with this?

  Thank you for your time.

  So where are you stuck? It is a fairly common task. Inside of a loop, you can increment the "xxx" and build a table of responses. Look at the Format function in the chain and a knot of shift register/feedback.

• Close the labview function in the discussion of the nugget

  I was looking around some of the Darren chips that go the way of the return over the years, and I wanted to ask a question about one.

  As the nuggets are so old, I thought that a new thread would be the best way to do it.

  The nugget is about adding that some relatives of code to make sure that all of the VI stop correctly.

  http://forums.NI.com/T5/LabVIEW/Darren-s-weekly-nugget-06-22-2009/TD-p/931158

  I get the ideas behind it, and as it happens I'm already doing the same thing myself, but without using the LabView "Quit" function.

  I make sure that I have closed all my sub VI before finishing with the 'closed group' invoke node.

  I can see the value in following the narrow Panel with labview Quit, but more thought, I became more ill at ease.

  My concern was that if there were two or more completely separate running on the same computer at the same time of labview applications

  the function exit Labview stopped everyone, not just the one that the user wants to stop.

  If close labview indeed close all running applications, so it is extremely dangerous to use it!

  I have no way to test it, so I was wondering if anyone has had this experience, or can give an answer.

  Bob wrote:

  I can see the value in following the narrow Panel with labview Quit, but more thought, I became more ill at ease.

  My concern was that if there were two or more completely separate running on the same computer at the same time of labview applications

  the function exit Labview stopped everyone, not just the one that the user wants to stop.

  Quit LabVIEW ends the current instance of LabVIEW.

  If it is called from an executable LabVIEW only that one instance of the executable is closed. (Yes, you CAN open more than 1 instance of an exe if you know how) other instances of the same exe or any what other exe will not conduct.

• Different behaviors in MAX vs LabVIEW when writing the attribute IMAQdx GigE

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  AnthonV wrote:

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  Hi AnthonV,

  "Weird" is a good way to describe the Spyder3 when it comes to the GigE Vision/GenICam interface (as opposed to the Dalsa driver that communicates using custom commands via ethernet camera series)...

  The Spyder3 has many questions focused on the calendar. It is possible that the time between the opening of the camera and the setting of this function is different by MAX vs your code in LabVIEW. In addition, there are some cases where MAX will be deletes the error to display. Ignoring the error indicated vs you see the feature to take effect in both cases?

  The base between MAX and LabVIEW behavior is the same. In both cases when you open the unit all parameters are responsible for our camera file that has the registered device settings. This file is created the first time that you open the unit and are updated every time you click on save to MAX or call an API function to save the settings. In any case, I know that the Spyder3 has various questions backup/restore the settings of our camera files.

  I suggest talking with Dalsa on the issues you are experiencing. They might be able to put up with a newer firmware that addresses some of these issues (we have worked with them in the past to identify several of them).

  Eric

• Launch a LabVIEW VI to the background of CVI

  Not sure if this is better posted in the LabVIEW or CVI forum...

  I need to start a LabVIEW VI "in the background" of the CVI.  In other words, I need to call a LabVIEW VI (which is embedded in a DLL) of CVI and have the function call immediately, while the VI called end of running in the background.

  I've had success making this kind of asynchronous call of in LabVIEW using an asynchronous start node name.  This works because it is supposed to: the node of the asynchronous call ends the execution immediately, while the called VI runs in the background.

  The problem arises when I integrate this into a DLL and call from the CVI.  If I build the DLL with active debugging and then walk through the code, stopping the code just after the asynchronous call, the background VI runs correctly.  But if I run all this full speed, the asynchronous VI does not run.

  I guess that the call of the DLL returning before the asynchronous VI can finish, the asynchronous VI is killed during the call to the DLL returns.  Obviously, I need the background / asynchronous VI ends once control is returned to the CVI code.  Am I doing this wrong?  Is there a better way?

  My code is highly integrated and probably not useful to publish.  If this could help write an example isolated post, I'll do that, but only if others cannot identify a better/different approach.

  Thanks in advance,

  Joe

  Hey JoeDG,

  Yes, as Evan mentioned in the thread you referenced, it's a feature of LabVIEW. As he says, for the ongoing enforcement there must be at least one open front. While I understand that this causes problems for the screws that are run without front panel, it seems that the workaround that you put in place is the best way to go. I apologize that you had to take an indirect route to achieve your final goal, but I'm happy that things are facing up and running for you now.

  Best,