Jump to content

Albert Geven

Members
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    3

Albert Geven last won the day on February 23 2021

Albert Geven had the most liked content!

Recent Profile Visitors

3,133 profile views

Albert Geven's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

4

Reputation

  1. Hi Jim That is a very good solution I never thought of. Even for NI it could solve a lot of effort to use VIPM...... I'm gonna try next week how that works, but I believe this is a nice escape. Also to have a VIPM package for a lot of drivers I have used or modified over the years.
  2. Hi Jim It seems to work, but I have to test for a new program because old drivers already saved their internal references to an absolute path for the first test. But it looks nice. The extension for instrument.lib seems to work. Folders are created. And a new recompile could be a solution.
  3. The normal instrument drivers are doable this way. DaqMX, GPIB, etc. that are maintained in MAX are more difficult. The best way is a virtual machine with separate drivers.
  4. I'm gonna put simply an instrumentdriver folder in lv-env/instr.lib and see what happens. In this case an Instrument systems folder placed in the lv-env/instr.lib folder was found after I pinpointed it when loading. Just the same as when I place an instrument in the folder. I probably have to change the instr.lib path to this new folder. In this way it is not yet recognized. And the just remove lv-env is also not an option anymore. What could help is an install or move of an instrument driver in dragon and an url from where it was available. This could be a local or www file path/url. I have one question: Can I save a kind of instr.lib in the lv-env folder?
  5. Thanks for the video. Download activating and all went smooth for LV2020SP1 I have one question: Can I save a kind of instr.lib in the lv-env folder?
  6. Hi In the VIPM 2020 beta I tried to install the error logger from CPE. And indeed that worked except that the include ppl was not correct for LV2019 or LV2018 so not useable. I have send a request to CPE to add those versions but only this morning so somewhat early to expect a reaction. Is it possible to check for ppl versions or should we leave that to the developer.
×
×
  • Create New...

Important Information

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