Jump to content

Bhargavi

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    3

Bhargavi last won the day on February 14

Bhargavi had the most liked content!

Community Reputation

5 Neutral

Recent Profile Visitors

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

  1. Hi Ashish, Using f1 patch of VIPM 2018 solved this problem. Thanks, Bhargavi.
  2. Hi Ashish, That didn't work. I have repaired the VIPM and restarted my PC. I am seeing the same error though. Please suggest me if any other way exists. Thanks, Bhargavi.
  3. Hi all, I am using VIPM 2018. I am unable to open a VIPB file in my PC. I have attached the error that I see when I open the VIPB file. I am able to open the file in another PC which is having the same version on VIPM. Could anyone help me in understanding and solving this issue? Thanks, Bhargavi.
  4. Hi Ashish, I have logged into the PC as an administrator and faced this issue when installing the VIPM. Will run as administrator differ to this? Thanks, Bhargavi.
  5. Hi all, I have ran the exe present in "C:\National Instruments Downloads\LabVIEW\2018\Products\NI_VIPM_Installer\NIVIP00" location which didn't result in the above errors and installed the VIPM successfully. But, I am not sure why this error has occurred when I install through LabVIEW installer. Thanks, Bhargavi Gowri.
  6. Hi all, I am not able to install VIPM in my PC. The error is as attached below. Please suggest me how to overcome this error and complete my installation. I have tried to install the VIPM from the LabVIEW Installer.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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
  12. 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.
  13. Hi @Jim Kring, Thanks for the update and the new release works fine for me
  14. Hi all, I have faced an issue with JKI VI Tester. Here are the details.. I am creating a DOM reference in "Setup.vi" and bundling it into my TestCase Object. DOM reference can be created by using "Load.vi" from XML Parser palette(attached image-> XML Parser palette and DOM Ref.png). When I unbundle it in the test VI, the DOM is reset to '0'. It is getting lost. We digged into the VI Tester and found out that some deprecated property nodes are used in "_JKI Toolkits\VI Tester\TestCase.llb\CallTestMethod.vi" in order to pass data from one VI (Setup VI) to another VI (Test VI).Refer to attached images -> VI Tester_Set Control.png, VI Tester_Get All.png. When the DOM reference is flattened it is getting lost, because LabVIEW doesn't know how to convert DOM reference into flattened data type. We have done a quick internal fix by replacing the property nodes and using variant to data after getting the control value. These changes are shown in "VI Tester_Set Changed.png" and "VI Tester_Get_Changed.png". Also, in "_JKI Toolkits\VI Tester\TestCase.llb\WaitOnTestComplete.vi", we have replaced the property node when parent data is written to child class indicator. This change is shown in "WaitOnTestComplete.png". I am getting my DOM reference in test VI correctly after doing this change. As I said this is a quick fix done for internal purpose. If this is the right change to make it work, can you please make this change and distribute the package so that my customers can also use it. If this is not the right change to be made, please suggest us how to fix this. Also, let me know if you can fix this issue and and release the fixed version. Please let me know if any other information is needed regarding this. Thanks, Bhargavi Gowri.
×
×
  • Create New...

Important Information

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