Jump to content

Tim_S

Members
  • Content Count

    850
  • Joined

  • Last visited

  • Days Won

    13

Tim_S last won the day on May 6

Tim_S had the most liked content!

Community Reputation

66

About Tim_S

  • Rank
    The 500 club
  • Birthday 10/17/1974

Profile Information

  • Gender
    Male
  • Location
    Michigan

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    1994

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Stopped having that issue once went to using win32 calls to make window frontmost and always on top (which has created new issues). Seems like would either hide the window while the file dialog was running or make the VI not modal while the file dialog was called.
  2. Fortran 77 still was taught in at least one college in 1993 on green-and-black and amber-and-black terminals. Was even a mandatory class for freshmen.
  3. I've gotten a test bench of 1 MS/sec of 32-bit data (24-bits plus 8-bits channel identifier) across FPGA->RT->Windows using DMA channel to RT FIFO to TCP and let it run overnight without drop of any data. Buffer was set to maximum size of U32. Now that was with a cRIO rather than a myRIO. Are you using NI's recommendations for best practices? Particularly the one where you check for available (request 0 samples) and then read all is a good way to read on the RT side. If you wait until the buffer is full then the FPGA can (and almost certainly will) overwrite before host side can service an interrupt.
  4. The DMA FIFO is what you're looking for with the data transfer.
  5. That error looks suspiciously like one I was getting when trying to uninstall software after something got messed up on my system (MSI files for uninstall were missing). There is (at least currently) a way around the package manager as listed in the knowledgebase article: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P70TSAS&l=en-US in the section "Software installed originally without NI Package Manager". This brings up the old interface which has the repair option. This was able to fix a bunch of installations which I couldn't uninstall before repairing. There are error logs that NI tech support had me send them which read pretty good for debugging the installer issue: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P6FcSAK&l=en-US
  6. The way I read the OP was first wanting to know if it was possible to create a bar graph (which does seem a strange question as the picture looks like a screenshot of a VI). If it's past that and getting the coordinates, then that's a mouse click event and an invoke node.
  7. There are 3rd party controls that do this. It's also possible in LabVIEW native controls, but it's a bit of work. Been quite a while, but seem to recall fill to zero and a property node to set custom axis labels was involved.
  8. You would need to associate the plot with the second Y axis: https://forums.ni.com/t5/LabVIEW/associating-a-plot-with-a-specific-y-axis-on-a-multiple-y-axis/td-p/63688?profile.language=en
  9. Directions on how to create two Y axes is at: http://www.ni.com/example/25089/en/. Directions on annotations is at: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019QhmSAE&l=en-US
  10. Not familiar with your setup, but was thinking that STOP immediate (NI term) could be a fast stop (drive term). Fast stop, with the hardware I've worked with, is usually a physical digital input on the drive that has to be configured to perform a fast stop through a drive setting.
  11. Your post is a bit confusing as you're interchanging string and array terms. Cleaning that up and posting a bit of what you've tried would help people give better feedback. It sounds like you're using primitives that would do what you want, so it would be helpful to see how you are using them.
  12. @Michael Aivaliotis, rereading my reply today that's a very fair criticism.
  13. What you are looking for exists, but not in the way you are looking for it. The documentation is in the context help for the the VIs installed. Some of the libraries do install examples with them, though most do not need examples as the information in the context help is rather good and any confusion can be resolved by looking the block diagram. One thing that I'm not sure is clear is that VIPM is a software package written by JKI that is used by many groups (including NI) to create easily installable packages, all of which is versioned and controlled separately so the VIPM version has no impact on the information the OpenG library provides for VIPM to display.
  14. Sorta. DAQmx is the software interface the same way a print driver (software) is the interface to a printer (hardware).
  15. To add to what smithd said... The biggest difference with LabVIEW versus other languages is that it is a data-driven language, meaning if something has new data at all of the inputs then it executes. LabVIEW is inherently multi-threaded because of this (there is some exceptions to that when dealing with DLLs and the like). So, looking at your code... The while loop has no inputs, so it will start immediately. The "input path" control has no data coming in, so it outputs a value that goes to the 'output path' which will display the value as that's the only input. The event structure will start and wait as it's input is some event to occur. The event structure and input/output path will occur 'simultaneously' as there is no data dependency (output of one to input of another) between the two. Similarly, other VIs you have can continue to run the same way if there is no data dependency.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.