Jump to content

Jim Kring

JKI Team
  • Content Count

    1,484
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by Jim Kring

  1. Hi @ammouri. Thanks for reporting these issues. > Just installed the design palette from VIPM and when i scroll down, LabVIEW freezes and i am forced to end its task. Check attached screen capture. Are you able to use the Design Palette if you don't do any scrolling? Or, does it tent to freeze after a certain period of time? I'd like to know if the freeze is related to the scrolling, or if it's just happening regardless. > I also noticed another weird behavior: if i open a project, the Design palette will open with it, but when i close the project, the design palette will remain open and will prevent the LabVIEW welcome screen from opening (can't browse recent document or create new projects). I can still however press ctrl-n to create a new VI... Yes, we've had some other people report this, too. We're working on a fix. Thanks! -Jim
  2. Thanks for reporting this @SABARI SARAVANAN M! We'll add these bugs to our issue tracking system. FYI @Eric Welden.
  3. Hi @TaimoorMajeed. We've had a few other users report this issue. We think it's an IT/networking issue, where the JKI Design Palette cannot reach the server to submit the request for an activation code. We're working on an off-line activation solution, so please stay tuned.
  4. [Update: Version 1.0.1 supports off-line activation] We are looking into an off-line activation solution for users without an Internet connection. Thank you for your patience.
  5. How do I activate JKI Design Palette if I don't have an Internet connection?
  6. Adding your Own Themes and Controls Note: Adding your own themes and controls is not officially supported, since we may be making improvements to how this works, but we wanted to tell you how to do it, so that you can make the most of the JKI Design Palette in your LabVIEW work. We hope you like it. Installing Theme Files Themes are stored beneath LabVIEW, in the following location: <LabVIEW>\resource\JKI\Design Palette\Themes To create your own theme, for example for your company named “Acme Corp”, just create a new folder such as the following: <LabVIEW>\resource\JKI\Design Palette\Themes\Acme Corp Inside that folder, place your controls as *.ctl (Custom Control) files, such as the following: File Path Control (Acme Corp).ctl Listbox (Acme Corp).ctl Have fun! And, if you’ve created some controls that you’d like to share with others (especially the built-in themes like Classic, System, NXG, etc.), please post them to the JKI Design Palette Community Discussion Forum. File Naming and Search Keywords The words in the file name are used as keywords for finding search results when typing into the search box of the JKI SDP -- so, you want to name the file with keywords that users will typically use when looking for your control. So, you’ll probably want to include the following words in the filename: The type of control (e.g. “Button”, “LED”, “Chart”, “Date Timestamp” etc.) The Theme Name (e.g. “Acme Corp”, “Classic”, “System”) since people may want to type the theme name into the search box, rather than using the Theme selector/filter drop-down list. “Control” or “Indicator” if your theme has both control and indicator versions of the control file Regular Custom Control vs Type Definition If you make your *.ctl file a “Type Def.” (type definition), then the dropped control will link to the type definition *.ctl file and will be updated accordingly, if you change the type definition file. This may or may not be desirable for your users. If you don’t want the dropped instances linked to the type definition file, then be sure your *.ctl is a regular type definition.
  7. How do I get my own custom controls (or theme) to appear in the JKI Design Palette?
  8. My answer: You can flush the queue by writing an empty string to it — do not use the "add state(s) to queue" VI, but instead wire an empty string into the state string shift register. That will clear all the remaining states.
  9. A user asked me: How do you flush the state queue of remaining states?
  10. 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
  11. 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.
  12. 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
  13. 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?
  14. 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
  15. 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.
  16. 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
  17. 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
  18. 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.
  19. 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.
  20. 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
  21. 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.
  22. Hi @Bhargavi, I’m glad to hear it’s working for you. Thanks for testing it out. -Jim
  23. 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
  24. 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?
×
×
  • Create New...

Important Information

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