Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Yesterday
  3. I retract my earlier statement. I was confused by part of the code. I think I can use this.
  4. Not sure I understand. The data type is just an array in a cluster; it's not actually protected in any way. It makes a copy if you want an ordered array, but not if you want to just access the circular buffer itself. That you can do by "unbundle".
  5. Powell: I looked at your library. Useless to me because it doesn't expose the raw buffer for traversal... it allows a *copy* of the buffer, but not an IPE access to the buffer. You abstracted everything away.
  6. I did a Circular Buffer using VIMs, so I'm pretty sure one can get the same basic functionality, though i suspect there is advanced Xnode stuff that VIMs can't do.
  7. So for the most part I believe these could be replaced with VIMs. I think the only feature that is used that a VIM wouldn't support is that the icons change color based on the data type being used, but I'm not sure anyone would really miss it. This also supports writing a scalar or array of data but a well constructed VIM can do that too. Also I believe there was a bug in early versions of LabVIEW that supported VIMs, which wouldn't allow for an inlined VI that had the New DVR primitive, but I just tested in 2020 and it worked fine.
  8. Is the TVI - Tester Automation Framework an open source alternative? I see you also posted the exact same text here. Is it also a LabVIEW software validation tool?
  9. @hooovahh The XNodes in this library... can these be replaced with VIMs at this point? Are the XNodes doing any type adaptation that couldn't be done with VIMs? I haven't opened up the code to investigate... figured I'd ask you first in case you know off the top of your head.
  10. Hello i would like to present TVI - Tester Automation Framework software has been implemented in more than 1000 different tests and it’s applied in the defense industry and leading high-tech companies. Here are a number of the advantages we offer: • Save 30% -50% of the funds and time of software development and engineering • Full LabVIEW, Python, .net support using advanced software architectures • Flexible reports viewer and generator (Word, pdf, csv, Html) • Easy to use software and station configuration interface • Built-in steps – run EXE, display text or picture messag
  11. Hello i would like to present TVI - Tester Automation Framework software has been implemented in more than 1000 different tests and it’s applied in the defense industry and leading high-tech companies. Here are a number of the advantages we offer: • Save 30% -50% of the funds and time of software development and engineering • Full LabVIEW, Python, .net support using advanced software architectures • Flexible reports viewer and generator (Word, pdf, csv, Html) • Easy to use software and station configuration interface • Built-in steps – run EXE, display text or picture messag
  12. Correct about the LabVIEW chroot only being an issue on the Linx Targets. But several IPCs will actually work even across chroot jail borders such as good ol TCP/IP (usually my IPC of choice as it works on the same machine, across VMs, on different machines on the same subnet and with some proper setup even across the world). Even shared memory could be made to work across chroot border, but it's complicated, sensitive for correct configuration, and shared memory is difficult to interface to in any case.
  13. Correct, the LabVIEW Python Node currently supports desktop only, not cRIOs. Here is an Idea Exchange post calling for support to be extended to cRIOs: https://forums.ni.com/t5/LabVIEW-Real-Time-Idea-Exchange/Python-Node-support-on-LabVIEW-Realtime-systems/idi-p/3904897?profile.language=en No, that's wrong. In NI Linux RT, VIs can access the entire system (as long as the lvuser account is given the required permissions). It's the LINX Toolkit (for BeagleBone and Raspberry Pi) that puts LabVIEW in a chroot jail. So, although the Python Node isn't available on cRIOs, you
  14. Last week
  15. Lookup the LabVIEW Python Node for calling Python from LabVIEW. That may not meet your needs on a CRIO. Under the linux-rt the VI runs in a chroot jail and so you have to do some tricks like using SSH to call python. Google and the NI forums should have some information on that. Another option is to pass data via TCP/IP. Also there is a DAQmx driver for Python, if you want to do everything in Python. The latest CRIOs (at least some of them) support DAQmx within LabVIEW. Not sure if that support extends to Python. Hope that helps.
  16. Hi everyone, i would like to know if there is a library for Profinet IO for LabVIEW2020-linux. I want to simulate a Profinet IO master. thanks in advance.
  17. I too use InnoSetup to extract and install various products. Regarding the installer, I'm not sure if you are aware of this, but you can get offline installers from the downloads page. My installer also does a silent installation of NIPM and various packages. The details are explained in these KB articles: Automating the Unattended Installation of NI Package Manager (NIPM) - National Instruments How Can I Control NI Package Manager Through the Command Line? - National Instruments If I remember correctly, the parameters described in the first article should also w
  18. So one thing I have done in the past is generate an installer using Application Builder, but not include any VIs or EXEs. Then you can call this NI installer silently from something else like InnoSetup.
  19. Well. There's also the Windows PDF which you can send to a printer, if you're feeling brave, but the ones you have detailed are by far the easiest.
  20. I use InnoSetup for a custom installer and I also install the 2019 runtime this way. It may not be the "right" way to do it, but the way I solve this problem is to manually extract the runtime installer and then just include that directory in my installer and run the Install.exe from the installer.
  21. OK, summing UP, I found three different solution: 1) Using AcroPDF Activex Object 2) Using Ghostscript 3) Using Sumatra PDF And that's all. Thank you
  22. I can't find an existing font while editing the icon. Has anyone had this problem
  23. I use a third-party MSI builder and not the built-in NI installer builder. I want to include the latest MSI LabVIEW runtime installer. I looked through: C:\ProgramData\National Instruments\MDF\ProductCache but couldn't definitely determine the correct files to use. I used the NI installer builder as a guide to determine the dependancies. I know the LabVIEW runtime is also available as an nipkg file. is that the better way to go? If someone can suggest any other solution that would help, I appreciate it.
  24. 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.
  25. Thanks your kindly help, this is very useful, I think i need ask Matlab team if the ActiveX is support or not on winserver2016. because the original Vi's function is only write array/number(.bin file) to .mat file, I really want to find a new/official way to do this function, the ActiveX is hard to migration and get further support.
  1. Load more activity
×
×
  • Create New...

Important Information

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