Jump to content

Jim Kring

JKI Team
  • Content Count

    1,451
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by Jim Kring

  1. A user asked me: How do you flush the state queue of remaining states?
  2. Hi @Naveen. This is a great idea! It’s not currently supported, yet I can see that it would be extremely useful to be able to interact with an existing state machine, and to facilitate migration to a JKI state machine. Note: i’ve moved your question/idea into this new “ideas and future requests” forum, and I’ve given it an upvote! Jim
  3. Hi @Daklu. Thanks for reporting this, and sorry for the trouble. I wanted to give you a quick reply to let you know we got your message and will look into this.
  4. hi @holyna For the base URL, you would want to put the part that's common to all your method calls. Note: You might want to use HTTPS instead of HTTP, so it's more secure. Looking at some of their documentation, the base URL includes the version (e.g. "v1") as shown below: base url: https://api.favoriot.com/v1 Yes, you will need to put your API key in the "Default Headers" structure, and you'll also need to set the "Accept" header to "application/json" Accept = application/json apiKey = <YOUR API KEY> Hope that helps get you going. Good luck! -Jim
  5. Hi Guillaume. When VIPM builds a VI Package, it makes a copy of your source folder right next to it and with a "." in front of the name. So, the ".BB Series x32" folder is that temporary copy of your "BB Series x32" source folder. I'm not sure why the DLL path is getting messed up. One possible work-around is to dynamically load the DLL by passing in the path to it yourself -- the CLFN supports passing in the DLL file path. Maybe that could be a good solution?
  6. Hi Jatin, I’m glad you were able to figure this out and upgrade to the latest version. Hope the course is going well for you so far. Let us know if you need anything else. Jim
  7. Hi Helcio, Yes, this happened in 2018. Our official statement about this is included in the release notes: "In order to best support our customers and ensure LabVIEW compatibility, VIPM supports new versions of LabVIEW as they are released. There are many instances where older versions of VIPM do not work well with newer versions of LabVIEW, due to changes in where/how LabVIEW and its files get installed." JKI has to provide support for each new version of LabVIEW as it's released, so we needed to align our support and releases with LabVIEW.
  8. Hi Helcio, Yes, you will need to use VIPM 2019 in order to manage LabVIEW 2019. You can upgrade via the menu in VIPM (Help >> Check for VIPM Updates) or download from vipm.jki.net/download -Jim
  9. That's a great idea, which we've been considering. We've posted a related idea and request for feedback, here: https://github.com/JKISoftware/JKI-State-Machine/issues/11
  10. Hi @Jonathan. I'm glad you find the JKI tools helpful! It's possible, but will probably take some tweaks. There's a post here about how to use a Proxy with LabVIEW's built-in HTTP client VIs, which the JKI HTTP REST Client uses, under the hood. If you need support in figuring this out and implementing a solution, you can also Contact JKI to discuss your project.
  11. Hi @Antoine Chalons. Yes, I can see how layers of nested array/cluster containers can be tricky 🙂 I'm glad you were able to figure it out, and get it working! Hope all is going well for you in general and on your LV projects.
  12. 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
  13. 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.
  14. Hi @Bhargavi, I’m glad to hear it’s working for you. Thanks for testing it out. -Jim
  15. 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
  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. 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.
  18. 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.
  19. 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!
  20. Thanks for reporting this @Bhargavi. We've just released VI Tester 3.0 with a fix for this. Please let us know if this works for you.
  21. Hi @jamesmc86. Thanks for letting us know. I'd like to get this fixed, if possible. Would you be willing to put a very small/simple example .vipb project together and share it, so that we can easily reproduce and investigate? Thanks.
  22. Jim Kring

    Loading Tests

    @Croohcifer Thanks for reporting this. I've filed a bug in the issue tracker, here: https://github.com/JKISoftware/JKI-VI-Tester/issues/33
  23. Thanks for reporting this. I've filed a bug in the issue tracker, here: https://github.com/JKISoftware/JKI-VI-Tester/issues/33
  24. Hi SGI, Sorry for the delay in response. Have you tried using the Enum as String argument?
×
×
  • Create New...

Important Information

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