Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Hi I had a package named "cfgCampaña xdas" but due to the special character ñ I had some troubles to publish. I can not remember exactly the problem. Finally I renamed the package, it it published in my repository but the old package "cfgCampaña xdas" continues in the vipc file, but it is impossible to remove, and once I try to remove with the right click menu I can not close the window dependencias xdas.vipc vipmsupport_02-19-20_11-45-01.bin
  3. Yesterday
  4. That's great that this LUT approach with in-line execution mode will work for you. Yes, it should be a lot less maintenance in the future. I'm glad it's looking like a good path forward. Thanks for letting us know how it goes. I've learned a bit from this discussion, too.
  5. Yes, I use the in-line execution mode on all the "constant" VIs that I generate as well. I tried out a quick POC performance test... There doesn't seem to be any real difference when using constants. I also tried the same LUT VI with the in-line execution switched off... that does make a HUGE difference. The in-line version is ~11x faster than the same VI with it turned off, and the VI that only contains a constant gets hit just as hard. Call overhead on such a tiny operation = ouch. I'm thinking the improved maintainability makes the LUT concept a winner. Thanks so much for the suggestion... now to rework my code conversion scripts and delete a lot of VIs I don't need anymore. 😅
  6. Last week
  7. This works. Thanks for the quick reply and fix.
  8. Yes, I’m pretty sure that if you use an array constant for your sparse values and you use a constant enum to index into that array, then labVIEW will constant fold the array indexing and look up. if you do this in a subVI, to use that look up in several locations, then you’ll probably need to set this up VI execution mode to in-line into the caller, in order for the constant folding to work I’m the calling VI. That being said, if the enum integer values are used as the indices into your look up array, then the operation should be lightning fast.
  9. Maybe... weird that nothing else seemed to be affected at all though. Not a major concern, just thought it was curious. That's a pretty good idea... Certainly easier to maintain, although I wonder how well Labview optimizes code like that. I'm thinking it would be less efficient since there would be the external VI call to index the look-up table, but in most cases it would be a constant enum indexing an constant array... I wonder if the compiler is smart enough to just evaluate that to constant value when I build the application for deployment. One again, mostly just a point of curiosity. It's not like that anything I'm doing is that performance sensitive anyway. Thanks for the suggestion. I may do that. 😄 Edit: I read the link after commenting on the suggestion; I assumed pushing every value into an array constant and indexing, but that example is using a case structure. I wonder if there's any significant difference/benefit to one way over the other. I guess the array based LUT could have a share of space allocated to undefined values, but it shouldn't really be that much.
  10. @Voklaif We dug into it and it turns out to be a LabVIEW bug. The solution is for the user (you) put a To Variant function before the call to Flatten to JSON String, since the bug seems to be inside the coercion dot (and the To Variant function doesn't seem to have that problem). Note: here's the bug (and fix) reduced to a very simple example (example VI also attached for anyone who wants to play with it)... Coerce to Variant Fail (LV2019).vi
  11. This looks like a bug. (Note: I've filed a bug report in our issue tracker here: https://github.com/JKISoftware/JKI-JSON-Serialization/issues/34) I see the same thing as you. The "bridge_data" is missing, here, when it's the only element in the cluster. However, if I add another element next to the variant (so it's not the only element in the cluster) then I see "bridge_data" in the JSON string. JSON Test ignoring single variant in a cluster.vi.zip
  12. We resolved the issue. Apparently some malware scanning setting in our web filter.
  13. Earlier
  14. I have been using JKI Design Palette and the EasyXML toolkit for a few weeks and I must say both are very useful tools, the former making my application look more professional and the latter saving a lot of time compared to coding a custom XML parsing. However, the "Best Attempt" Parsing feature of EasyXML turned out to behave differently from what I expected. Using the Easy Read XML File or Easy Parse XML functions, when passing an array of (type def) clusters as the "LabView Data (type)" argument, I expected that the missing data from the XML file (i.e. an element missing from a cluster) would be replaced by the default value defined in the type definition. It turns out not to be the case. The missing data is replaced by the LabView default value. This is problematic because this default value (0 for an int) is among the "legit" values I intend to use, as opposed to (for example) -1, that would allow me to immediately detect missing values. What surprises me most is that this behavior seems to have been acknowledged as non-optimal in this topic from 2010: Is there something I am missing here ? I tried using strict type definition, to no avail. The typedef enum I have inside my cluster also defaults to the first value, not to the default value I defined. Thanks, Henri
  15. Hi, I found today the JKI JSON tool, which looks great, but I've encountered a problem. When I try to "wrap" some data around a new object, with a cluster with a single variant it ignores it. Please see screenshot for clearance: The output is the same. I expect the left string to have the "bridge_data" in it. Is it a bug or am I not using it correctly? Thank you
  16. I've seen similar problems when VIPM gets an error checking the network for the package repository feed. If we solve the first issue, the second problem will go away.
  17. A.) Is it a "System" package that you're looking at? B.) Or, did you set the Target to System and then are you looking at a LabVIEW package?
  18. Another interesting observation: If I choose Not Installed packages, I get a list of packages. Regardless of which package I choose, I get the following when I try to install it: "Package is not compatible with your operating system or any LabVIEW version installed..." I am running Windows 10 with LV 2017
  19. One more idea... Is the clock (date/time) set correctly on that computer? If not, that can cause HTTPS connections to fail, since the certificates can't be verified correctly.
  20. The hover effect does not show when the VI is in Edit Mode. It should work OK when the VI is running or when it's in Run Mode (tip: use <Ctrl+M> to toggle between Edit and Run mode).
  21. Shoot. That setting was my secret weapon. Now, I'm not sure what it could be... If you're interested, you might try VIPM 2020 Beta and see if that fixes things. It's pretty stable at this point and we're actively fixing issues.
  22. Yes, I checked that setting. I tried both settings. Both give the same error when refreshing
  23. Thanks for posting to the idea exchange and letting me know more about your packaging use case. > Side question: Any idea why Chrome freezes will VIPM is processing a (very) large package? I'm not sure, but Chrome can use a LOT of memory with lots of tabs open. It could also be related to disk usage. I'm not sure. 🤷‍♂️ > over 1200 defined messages. Since LabVIEW does not support sparse enums Hmmm... Maybe you could create your own non-sparse enum that you pass into your VIs and then use a conversion VI with a look-up table to convert these non-sparse enum values to the sparse integer values used by your low-level library. This is discussed a little bit here on lava.
  24. One thought I have is that you might try the Options >> Network >> Configure Proxy to Access the Internet setting. Try testing VIPM with either "Use System Proxy Settings (Windows Only)" or "No Proxy (Direct Connection)" -- that can sometimes make a difference. PS - Your options page might look a little different, since I'm using VIPM 2020 beta. 😉
  25. Hi Jim. Definitely something with my PC. I tried from another computer and no error when refreshing the packages. I also tried running the Package Manager install and choose Repair. Not effect - still get the original error. My IT is scratching his head too. Any thoughts?
  1. Load more activity
×
×
  • Create New...

Important Information

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