Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. single step sounds good - and should work in both direction Last/Next Step dynamic state generation - maybe JSON imported State"Objects" (export fct would be nice 2)
  3. I think I may have found a fix for this. I ran a search on the Access Violation string generated by the LabVIEW crash reporter and found this page: https://www.tsxperts.com/forums/topic/ausnahme-access-violation-0xc0000005-bei-eip0x01013310/ In my case I deleted C:\Program Files (x86)\National Instruments\LabVIEW 2016\project\Plasmionique and C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\Plasmionique I had already tried removing and renaming some files in an attempt to avoid a possibly long reinstall. None of that worked, but removing the above two folders did. I had not run LabVIEW 2016 for awhile. In that time, my license had been renewed. When VIPM initially started LV, it timed out because I didn't notice the splash screen in the background waiting for me to "Launch" LV. I launched LabVIEW and then repeated the install on VIPM. But this time LabVIEW crashed after the DQMH install started. Not sure if the license renewal had anything to do with the crash. This is the first time I've ever seen anything like this. This is on a bit of a legacy dev machine with multiple versions of LabVIEW living together nicely for a long time. So it's quite relief having it up and running again.
  4. Windows 7, LabVIEW 2016 32 bit, VIPM 2016.0.0 LabVIEW 2016 working before attempting to install DQMH package. VIPM failed to connect to LabVIEW 2016 initially due to re-activate splash screen. On second attempt with LabVIEW 2016 already running, LV 2016 crashed on connection attempt. After that, LV 2016 crashes on every start. I've tried to find any files that may have changed, or some other way of perhaps saving this install of LabVIEW. Is there anything I can look for? Perhaps someone has already experienced this and found a fix.
  5. Can someone from JKI tell me why this package doesn't build? It is relatively simple with no Pre/Post VIs, no file renaming, only a functions palette. But there are some XNodes and they are going into the vi.lib. On attempting to build it gives the following error: During the build I navigated to those folders and they exist and the files are there. If I remove that one XNode and its support files it builds properly. If I add it back with the support files it fails to build. I've tried mass compiling, resaving, and renaming VIs but it still errors. If I delete all other XNodes, and all other support leaving Common and the Compare to Constant, it also fails to build. Any help is appreciated. EDIT: LabVIEW 2018 SP1 F3 32-bit, VIPM 2018 0.0.f2, Windows 7 x64. XNodes Won't Build.zip
  6. Earlier
  7. Hi, I am building a small automation tool to build packages for my project. As a part of it, i would like to display the VI icon that will be displayed the Functions/control palette. I tried reading the build spec as an XML file, but I am getting only a series of Hex numbers. Could someone suggest me a way to generate the icon which is displayed in the build spec. Thanks, Pranay
  8. You might need to install some extra libraries. See here. I'm not sure about your package manager, but something like: apt-get install libxinerama1:i386 libgl1-mesa-glx:i386
  9. Hi Jim I have a Centos 7 and Labview 2018 installed I install VIPM, however I received the same error as Francesco. I'll try to install the LVRT engine, but I received the following errors (even if it is in italian, it is simpleto understand what happens...) sudo ./INSTALL (or with su privileges, is the same...) Preparazione in corso... ################################# [100%] Aggiornamento / installazinone... 1:labview-2015-rte-15.0.1-11 ################################# [100%] Preparazione in corso... ################################# [100%] Aggiornamento / installazinone... 1:labview-2015-rte-32bit-15.0.1-11 ################################# [100%] Preparazione in corso... ################################# [100%] il pacchetto nisslcerts-18.0.0-3.0.noarch (il quale risulta essere più recente di nisslcerts-15.5.0-3.1.noarch) è già installato Preparazione in corso... ################################# [100%] il pacchetto nissli-18.0.0-f0.i386 (il quale risulta essere più recente di nissli-15.5.0-f1.x86_64) è già installato il pacchetto nissli-18.0.0-f0.x86_64 (il quale risulta essere più recente di nissli-15.5.0-f1.x86_64) è già installato errore: Dipendenze fallite: nissli-32bit < 16.0.0 reso obsoleto da (installato) nissli-18.0.0-f0.i386 nissli-32bit < 16.0.0 reso obsoleto da (installato) nissli-18.0.0-f0.x86_64 errore: Dipendenze fallite: nicurli >= 18.0.0 necessario a (installato) ni-visa-lxi-discovery-18.2.0.49152-0+f0.x86_64 nicurli >= 18.0.0 necessario a (installato) ni-wsrepl-18.1.0.49152-0+f0.x86_64 nicurli >= 18.0.0 necessario a (installato) ni-488.2-sysapi-support-18.0.0.49152-0+f0.x86_64 nicurli >= 18.0.0 necessario a (installato) ni-visa-lxi-discovery-18.2.0.49152-0+f0.x86_64 nicurli >= 18.0.0 necessario a (installato) ni-wsrepl-18.1.0.49152-0+f0.x86_64 nicurli >= 18.0.0 necessario a (installato) ni-488.2-sysapi-support-18.0.0.49152-0+f0.x86_64 errore: Dipendenze fallite: nicurli-32bit < 16.0.0 reso obsoleto da (installato) nicurli-18.0.0-f0.i386 nicurli-32bit < 16.0.0 reso obsoleto da (installato) nicurli-18.0.0-f0.x86_64 errore: Dipendenze fallite: nisvcloc < 18.1.0 reso obsoleto da (installato) ni-service-locator-18.1.0.49152-0+f0.x86_64 Preparazione in corso... ################################# [100%] il pacchetto nitdmsi-18.0.0.49152-f0.i386 (il quale risulta essere più recente di nitdmsi-15.2.0-f0.x86_64) è già installato il pacchetto nitdmsi-18.0.0.49152-f0.x86_64 (il quale risulta essere più recente di nitdmsi-15.2.0-f0.x86_64) è già installato errore: Dipendenze fallite: nitdmsi-32bit < 16.0.0 reso obsoleto da (installato) nitdmsi-18.0.0.49152-f0.i386 Installation completed. and then sudo ./vipm Can't load library /usr/local/lib/liblvrt.so.15.0 libXinerama.so.1: cannot open shared object file: No such file or directory To download the LabVIEW Runtime engine, go to http://www.ni.com/rteFinder?dest=lvrte&version=15.0&platform=Linux&lang=en what can I have to do? dh
  10. Hi @Naoki. Yes, you can just put the call to "Idle" inside of your sequence of calls, and then the JKI SM will handle the subsequent states after checking for user interface events. There are some considerations, but it's totally possible and works well. Remember to set a Timeout greater than zero (but NOT zero, due to CPU usage concerns!) so that if there are no events, the Timeout frame will execute and your sequence will resume.
  11. Hi @Bhargavi, I’m glad to hear it’s working for you. Thanks for testing it out. -Jim
  12. Hi Naoki, You can explicity call the “Idle” (“Event Structure”) state, in your measurement sequence, to check for events. There some lessons on how to do this in the JKI State Machine Online Training. -Jim
  13. Hi @Jim Kring , I have tried out the new build(3.0.2) and it works fine for me. Thanks for the immediate fix Thanks, Bhargavi Gowri.
  14. Hello. I am trying to make a measurement program. Since this measurement takes a long time, it is necessary to be interrupted by the user's operation so that it can return to the measurement standby state. Is there a smarter way than inserting lots of checking the local variable of the break button during the measurement sequence?
  15. Hi @Jim Kring, Thanks for sharing the build:). I will try it and let you know if it works fine for me. I am accessing the reference in TestCase by passing it through functional global. I didn't find any other way to do it as of now. Please let me know if there is any other way. Thanks, Bhargavi Gowri.
  16. Hi @Bhargavi, Can you please try this pre-release build 3.0.2, and see if it works for you? Please let me know how it goes. Also, how are you planning to access the reference (inside the TestSuite) from within the TestCase?
  17. Hi @JimKring, You are right. Similar to the one in test case "setUp.vi" we have to fix in test suite "setUp.vi". If you are going to make those changes, can I know when I can expect the fixed version? Thanks, Bhargavi Gowri.
  18. OK, I think that's the best approach. I think that we may still need to fix some of the flattening/unflattening issues inside of TestSuite.lvclass:WaitOnTestComplete.vi (and the TestSuite runner), in order for the reference to be valid.
  19. Hi @JimKring, I have moved to the approach of creating the DOM reference in setUp.vi of Test Suite. I will let you know if I face any problem. For now, Thanks, Bhargavi Gowri.
  20. Hi @Bhargavi, Thank you for posting this example project. The breakpoints do a great job of showing the problem you're seeing. I did find that some of the deprecated control value methods are being used and the typecasting issue is present (and those should probably be replaced with the variant counterparts). However, that's not the only/main problem at hand. Another big issue I see is that the TestSuite's New.vi method is being called when VI Tester first loads the Test Suites, and then the New.vi goes idle, which means that any references created inside of New.vi will get disposed of automatically by LabVIEW (when the VI goes idle). VI Tester works around this with the TestCase and TestSuite setUp.vi using the TestCase.lvclass:WaitOnTestComplete and TestCase.lvclass:WaitOnTestComplete VIs, which keep setUp.vi running until the test case/suite completes. However, that's not exactly what you're after -- you're trying to initialize the data of the TestCase inside the TestSuite New.vi. I'll need to think about this some more, to see if there's a good solution.
  21. Hi @JimKring I have attached the sample project, which demonstrates the issue that I am facing. I have also attached the image, which shows the DOM ref values in New.vi of test suite and setUp.vi of the test case. Please let me know if you need any details. Thanks, Bhargavi Gowri. Sample Code.zip
  22. Hi @Bhargavi Would you be able to create a very small test project (and zip+attached it) that demonstrates the issue? That will make it easier to debug. Thanks!
  23. Hi @Jim Kring, I am facing the same issue(document reference getting lost) when I create my object(this object private data contains document reference) in the "New.vi" of Test Suite. I observed that when I create the document reference in "New.vi" and use it in my test case the document ref is lost. Please let me know if this issue can be solved or I should find other alternatives to make my test work. Thanks, Bhargavi Gowri.
  24. Hi @Jim Kring, Thanks for the update and the new release works fine for me
  1. Load more activity
×
×
  • Create New...

Important Information

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