Jump to content

mcduff

Members
  • Posts

    28
  • Joined

  • Last visited

  • Days Won

    1

mcduff last won the day on June 26

mcduff had the most liked content!

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    2017

Recent Profile Visitors

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

mcduff's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare

Recent Badges

3

Reputation

  1. It looks like the external dll call has an extra buffer allocation, don't know if it is real or not, just what NI is reporting, whereas, the native implementation does not. See below. That may account for the speed difference. EDIT: Execution Trace toolkit shows the same.
  2. FYI, cross-posted on the dark side https://forums.ni.com/t5/LabVIEW/USB-6215-10-Hz-triggering-with-2-TTL-signals/td-p/4181960?profile.language=en
  3. Maybe not a new feature, but somewhere in the talk they mentioned a 2021 LabVIEW license would give you access to Windows, Linux, and Mac versions, no separate purchases required.
  4. Don't disagree at all with the increase of computational power, but JPL has rules for code. I think having a set of rules helps to reduce possible errors.
  5. You thought it out more than me. The test will be when I get 2021.
  6. Just reporting that I used the DMC image control, had the box checked, and did NOT have a black image display. (LabVIEW 2020SP1, 64bit, Win10) No commentary on whether to check/uncheck box. Just suggesting a possible work around for folks who may want to check the box.
  7. Not commenting on whether to allow future versions ... However, if it is checked and you want to use an image control that won't change colors in the EXE version, the Image Control in the DMC controls package available on VIPM does not suffer from this problem.
  8. MAT files are now just H5 files(HDF). Look at the library https://h5labview.sourceforge.io/ and find the example for writing a MAT file. You just need to add a special header in the beginning. I assume the dlls needed will work on Windows server, but am not sure.
  9. Maybe this link on the dark side may help: https://forums.ni.com/t5/Example-Code/Determine-Clicked-Array-Element-Index-in-LabVIEW/ta-p/3536340?profile.language=en (Some limitations in the code, may have to change for newer style arrays) mcduff
  10. The following will replace a row or column subset or complete row or column of a 2D array using native functions and no loops or IPEs. If your subset array is 1D all you need to do is reshape it before a replace operation. ReplaceRowColumnSubset.vi
  11. Probably slower than your method, but it is possible using primitives, and it is quite messy also. See below.
  12. Maybe this thread can help, if you haven't seen it before mcduff
  13. The Matio library uses the old .mat file format; the new .mat format is based on HDF. Try one of HDF libraries to read your .mat, or re-save your file using the old version. mcduff
  14. It appears that NI is a hardware company rather than a software company. LabVIEW is developed to drive sales of hardware. This is similar to Apple, OS X, iOS, etc, are all developed to drive sales of hardware. mcduff
  15. Please correct my misunderstanding, the biggest difference between Maps and Variant attributes are Maps: Keys can be anything (all keys the same type), but all "attributes" need to be the same type. Variant: Keys need to be strings, but "attributes" can be different types. The structure seems similar, although slightly different. mcduff
×
×
  • Create New...

Important Information

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