Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/18/2018 in all areas

  1. 1 point
    I'm using Open AF Method plugin and today when I installed Design Palette with Flat UI 2.0 I noticed that whenever I click on Open Method.. popup menu option, Design Palette gets opened too. It's annoying to close it every time I go from "Send message" vi to the method. Cheers, Patryk
  2. 1 point
    So far it looks like issue is not existing anymore. Thanks
  3. 1 point
    Yes, I meant Quick Drop, but couldn't remember its proper name. I'm using the latest version of JKI Design Palette. However, the problem disappeared. It seems that it disappeared after I first tried Ctrl+Alt+Space to pop up the Design Palette. After that Ctrl+Space correctly opens Quick Drop window.
  4. 1 point
    An easy way to do a super simple resizeable UI, I think, is to use splitter bars and then choose one pane that has some kind of big UI element that is easy to resize like a graph that you can just set as "size to pane". Then set the sticking of the splitter bars so that one pane is the only one that changes size on panel resize events and all others stay the same. Then you don't have to worry about scaling all the little buttons and dealing with decorations getting pixelated. But for a tab control, yeah there is no easy way sadly (at least that I know of). For this, I usually just use radio buttons as the tabs and then a subpanel and switch out which VI is displayed in the subpanel based on the radio buttons.
  5. 1 point
    I am having difficulty creating a UI that scales well for monitors of different resolutions. For programs that have numerous indicators and controls the scaling issue can be especially challenging. The solution provided by NI to this issues as I have read it is to use splitter bars https://forums.ni.com/t5/LabVIEW/Different-Screen-Resolutions-What-is-the-best-method/td-p/1749514 By using splitter bars you can get front panel objects to 'scale' within their pane by first grouping the controls/indicators and then right clicking the group and selecting 'scale object with pane' (although the controls often look distorted when scaling). However, this solution is only viable if you have a limited number of front panel items. When I have too many objects to be displayed on a single window I use tab controls to organize my front panel items. However, you can not use splitter bars within a tab control to so the objects placed on the tab control pages won't scale. https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Tab-Controls-with-Splitter-Bars/idi-p/990693 Are there any other viable solutions that people are using to solve this issue? Does it require sub panels? Are there any best practices?
  6. 1 point
    I knew there should be an alternative 🤓
  7. 1 point
    The design palette seems to work well for Boolean buttons, but is more difficult to use for other controls. For example, if I type "graph" I get firstly various buttons, then a number of graphs, but there's no way to tell what type of graph: waveform, XY, Intensity - even a chart gets shown here (because the filename on disk includes the word "Graph"). Suggested enhancements: text showing the name of the control currently selected (or under the pointer) in the same way as the LV Control menus the list of control types filtered to show only those which are part of the current search (same as the sizes are only those relevant) where the search text is a standard control type, then those are shown first before buttons that also match the text - and/or ability to sort by type rather than theme a list of other words relevant to the current search that can quickly be clicked on to limit the options shown, either sorted alphabetically or by frequency of use
  8. 1 point
    Hi not sure if I'm misunderstanding but what's the use of "I want different colors" and "allow interaction" ? I don't see any different behavior when clicking on the UIs in "interactive" and non-interactive mode (colors do work). I also don't understand the colors, when dragging a UI to a FP (with different color) it changes back to default colors on the FP. Also "Allow interaction" - checkbox and left color box collide (see picture). Last but not least: how do you exit interactive and color mode? I had to restart LabVIEW. Regards Christioh
  9. 1 point
    First of all: Thanks for another great LabVIEW tool - highly appreciated! It seems that the ports you are using to activate the design palette and/or download the content is blocked by our corporate network. Using my private internet I could activate it properly, but back again in the company network I get an error message again when I am starting the palette the first time. Would it be possible for you to use other, usually open ports? Or at least let us know which ports need to be opened?! Is there any plan when we can expect the palette for the 64 bit version of LabVIEW? Thanks, Ingo
  10. 1 point
    @Jim Kring Just tried it out. I downloaded and installed from the download link from option A, which installed 1.0.0.155 again. Then VIPM said there was an update available which installed 1.0.1.176. I entered my email address and was prompted for an offline activation. The link took me to the form with all of my information pre-filled (nice touch!) and I was able to activate with no issues! All good here now. Thanks for the quick fix
  11. 1 point
    Hi all, I am having problems with running the JKI Design Pallet. I am getting this error when I sign in. Followed by Has anyone solved this problem with the sign in? I have JKI Flat UI Control 1.0 installed. Any help will be appreciated. Many Thanks
  12. 1 point
    Hi Volks, i've tried out the new Flat UI 2.0 Controls. Therefore I installed the package using VIPM. First of all I found it quite annoying that every time labview starts the window with the control platte popped up and there's no quick to find way to disable this hence i uninstalled it. Every time I try to compile an application or start labview I'll get another annoying message: Can you name me a fix for this issue? I've no idea where the new control palette nested in. Thank you very much. Nice greetings and thank you for sharing your outstanding plugins / VIs 🙂
  13. 1 point
    Hi Jim, thank you the error has gone.
  14. 1 point
    The design palette shows up every time I open a LabVIEW project, is it the intended behavior? And is it possible to change this? Cheers
  15. 1 point
  16. 1 point
    Hi @Antoine Chalons. Can you please try out the new 1.0.1 release and let us know if this resolves your issue. I think we've fixed it, and would love to hear your feedback.
  17. 1 point
    DP.mp4 it also shows up at unexpected moments, e.g when doing a save all from the lvproj window see video
  18. 1 point
    Yes, when the DP shows up as I open a project it is pinned. See attached video : I have a small project already open with the main.vi running Then open a DQMH project >> DP shows up pinned Untitled.mp4
  19. 1 point
  20. 1 point
    I'm having the same issue, looking forward to a fix.
  21. 1 point
    I suspected that but could not pinpoint which one could be causing the issue. I monitored the memory consumption to see if it is spiking during scrolling but it is not. I am not able to scroll all the way in neither classic nor Flat... And out of no where, i am sometimes getting the error below (even when the design palette is not open). I guess the palette continuously check for communication with the server in the background for some reason. Ali
  22. 1 point
    It wasn't my video, just a forum topic of the tool i'm using. You can find my recorded example below. Even though I unpin the palette and close the window, it is still being opened.
  23. 1 point
    Hi Jim Yes i am able to use the palette if not scrolling. It is not freezing after a period of time. Below are also some observations: The palette will freeze if I: Select "System theme" from the combo box (the classic and flat works fine) Maximize the palette The palette will NOT freeze if a I scroll with a limited number of controls shown (for example when filtering to show only boolean controls)
  24. 1 point
    Dear JKI Team, unfortunately the VIPM could not download the JKI Design Palette from the remote server. No problems with other packages. Kind regards from Germany and thanks for your really great tools! Peter
  25. 1 point
    Hello JKI, I found two issues on your recent release of JKI Flat UI controls V2.0. Those details are follows, 1. When I changing to true state on settings control, it shows different image instead of settings image. 2. When I try to enter values on numeric controls, the cursor hover expending beyond that control size. Typically, the cursor hover size would be within the numeric control size. I hope, these information's may help to improve changes on your Flat UI controls V2.0 Regards, SABARI SARAVANAN M
  26. 1 point
    I ran across a problem in a project where, after creating and initializing the class under test in the setUp VI, unbundling it in the test VI returns a default object rather than the one I instantiated. setUp.vi testCount.vi I've attached a project with the class under test (ListImp) and two test cases. Both test cases have (as near as I can tell) identical setUp code and identical code in the test method (testCount). However, one test passes while the other test fails. Any idea what's causing this? [Edit - The about box reports "version 3.0.1.294 (Feb 11 2019)".] [Edit 2 - Another piece of potentially relevant information is the Test_ListImp..._2 test class was brought forward from an older version of VI Tester. I don't know what version, but according to my repository it was sometime before Feb. 2013. The other test class (the one that passed) was created with the current version of VI Tester.] VI Tester Error.zip
  27. 1 point
    Can i Link this case structure viewer to my existing case structure. i already created one VI using Enum based state machine.Now i want to convert it to JKI state machine.is there any possibility to convert with minimum changes instead of re-implementing.
  28. 1 point
    Hi JKI team, Firstly I want to thank you for generating the REST toolkit for LabVIEW, it seems pretty easy to connect the IoT cloud. I do, have some glitches when using it. I came across to this youtube demo ( Are you able to make an example to show how to use the tool? If that takes a while, would you please comment on 1. What's the input of Base URL? I used "api.favoriot.com" in my case. 2. Do you define the apiKey in one of the Default Headers? I did this but didn't seem to get anywhere. Your help is appreciated.
  29. 1 point
    Never mind. It appears my JKI state machine was a older version after the upgrade I was able to access explorer option.
  30. 1 point
    I have installed LABVIEW 2019, and I followed the procedures to make sure VIPM can communicate with VIPM 2018.0.0f2: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW But, still I do not see LABVIEW 2019 listed within the VIPM window: Any clue on how o solve this? Thanks
  31. 1 point
    Hi, in our company we changed the Parse State Queue VI, so that we get the previous state in case we had an error. With this it was so much easier to debug the JKI-SM, because we were able to display the state, where the error occurred. Maybe this this an idea for the original Parse State Queue?? Here is an snippet based on the "old" Parse State Queue VI.
  32. 1 point
    Hello! Where can I download the latest versions of the state machine and the state machine editor as a vip file (there is no Internet access on that computer)? Or maybe you can get out of any directory when installing via vipm? https://github.com/JKISoftware/JKI-State-Machine/releases? here?
  33. 1 point
    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.
  34. 1 point
    Open "Compare to Constant.xnode" with a text editor. Near the bottom, delete the two items "Untitled 4 (SubVI)" and "Untitled 5 (SubVI)" Then it will build.
  35. 1 point
    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)
  36. 1 point
    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.
  37. 1 point
  38. 1 point
    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?
  39. 1 point
    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.
  40. 1 point
    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.
  41. 1 point
    Hello, I am having trouble loading tests. When VI tester starts it doesn't find my tests. I can manually load 1 test by File/Open File or test class. I can't load multiple tests. I have my classes in folders. Do the test classes need to be in the top level of my project? I have them in a auto populating folder called "Unit tests? Thanks Dan
  42. 1 point
    @Robert Smith I know this is four years later and probably not very helpful, but I just used VI Tester for the first time and found that my tests would not appear in the UI if the test classes were in auto-populating folders. This may have been your problem. Hopefully this helps someone else who might come across this thread.
  43. 1 point
  44. 1 point
    Ruslan, I will suggest to leverage VIPM's capability. Refer this link: https://support.jki.net/hc/en-us/articles/214135803-How-do-I-transfer-packages-with-VIPM-to-a-non-networked-computer-
  45. 1 point
    It would be great if there is a preview window along with the description editor. Right now, after formatting the description with various tags (like bold/italics etc.,) I would need to build the package in order to see the formatting. If there is a preview pane along with the description, it would easy to see the final formatting. Thanks, Ajay.
  46. 1 point
    I've got a problem with JKI SM Editor (JKI SM ver. 2018). In one case, it increases the CPU resources consumption. The procedure is as follow: 1. Open New VI or existing VI with JKI SM. 2. Open block diagram. 3. Open JKI SM Editor. 4. Close front panel of the VI. CPU usage increases - in my case (i5-4210M) up to 38 - 40%. Have to reset the LabVIEW. Has anyone observed silmilar behaviour? [Update: This has been fixed in version 2018.0.1.36 of the JKI State Machine package, which has been published and is available for download and installation using VIPM.]
  47. 1 point
    Yep, the new version works well. Many thanks!
  48. 1 point
    We figured it out -- it was getting an error during Macro Exit (shutdown), that was causing it to go into the error handler, which was going into Macro Exit (an infinite loop). You can work around this issue by tweaking the code inside the JKI SM Explorer window to look like the following. (You can open the JKI SM Explorer then press Ctrl+Space to stop the VI, then Ctrl+M to go into Edit mode). Update: This has been fixed in version 2018.0.1.36 of the JKI State Machine package, which has been published and is available for download and installation using VIPM.
  49. 1 point
    The issue is because I renamed the event case to "Idle" from "" (empty string). Renaming the case name will resolve this issue.
  50. 1 point
    Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
×
×
  • Create New...

Important Information

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