Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/14/2021 in all areas

  1. I've just implemented this and posted a beta: https://forums.ni.com/t5/JDP-Science-Tools/BETA-version-of-JSONtext-1-5-0/m-p/4136116 Handles comments like this: // Supports Comments { "a":1 // like this "b":2 /*or this style of multiline comment*/ "c": 3 /*oh, and notice I'm forgetting some commas A new line will serve as a comma, similar to HJSON*/ "d":4, // except I've foolishly left a trailing one at the end }
    5 points
  2. I have been coming round to supporting comments in JSONtext, at least for ignoring comments on reading (which is quite simple to implement, I think). And possibly features to be more forgiving of common User error, such as missing commas.
    4 points
  3. I've encountered a black imaq image display in exes, solved by unchecking the box to allow running in a later runtime version. Don't know if that is related to your problem.
    3 points
  4. I've been toying with the idea of implementing a new TOML library for LabVIEW. I've been using OpenG variant config for years, but I would prefer to use a more standardized format for my ini config files. TOML is the best candidate for this. Erdosmiller's library is pretty good, but as the author points out, it is no longer maintained, and it didn't gracefully handle all of the datatypes that I wanted to use. It would be great to have the flexibility of jsontext but for TOML format. I'll post back here if I manage to get the project off the ground.
    3 points
  5. I recently ran into an interesting problem: some calculations I was doing in which I used parallelized loops were taking an inordinate amount of time (and consuming 100% of my i9 cores). Turning to profiling to figure out where I might be bugging out or able to find some optimization, I realized that the most active subVI was this: Error Cluster from Error Code.vi There is an interesting discussion elsewhere about why this VI is a nuisance (even in its modernized version), which is compounded by the facts that: - it is randomly used by NI in its code (some error codes are
    2 points
  6. I updated the Bug report to mention that this should be in the help. Also, I talk a lot about use cases for the Error Ring (including mentioning several of the points I brought up in this post) in my What To Expect When You're Expecting an Error presentation here: http://bit.ly/dnatterrors
    2 points
  7. I have reported the documentation issues (both the 'page not found' error, and the suggestion about placing error rings in case structures) to R&D as Bug 1413653. Don't forget you can deselect Visible Items > Error Explanation Text if you need your Error Rings to be more compact:
    2 points
  8. Yes it is, both ways. I'm glad you like it There is a new release which adds support for composition of maps and sets. Here is an example of what you can do with it: This is actually a very smart way of doing it. My library takes the keys and values apart into individual arrays. A key-value-pair is certainly easier to work with...
    2 points
  9. My intension for this template was to fill the gap between the Actor Framework and standard QMH. I never wanted to recreate the AF. When I first got a look at the AF I didn't get it. After a tutorial on youtube I got the understanding of AF but I feel somehow a distance I can't describe to the AF. It feels like AF is free floating in Hyperspace or so. Because of this I wanted to create a template with some benefits of OOP but more grounded and I started this template. And yes, AF is great way to get things done but in my opinion not very easy to understand. Thanks, Peter
    2 points
  10. Version 1.5.4

    927 downloads

    Package for working with JSON. Uses high-speed text parsing, rather than building an intermediate representation as with prior LabVIEW JSON libraries (this is much faster). Allows easy working with "subitems" in JSON format, or one can convert to/from LabVIEW types. Uses the new "malleable VIs" of LabVIEW 2017 to convert to any LabVIEW type directly. JSON text makes use of a form a JSON Path notation, allowing easy and rapid access to the subitems of interest. Requires LabVIEW 2017 and install by VIPM 2017 or later. Original conversation about JSONtext. On the LabVIEW To
    2 points
  11. As a note, a quick performance test comparing dropping a constant or an error ring in a case and running this over and over doesn't seem show much of a difference in terms of CPU (but benchmarking could probably done more carefully), so I may have just used up bandwidth for not much, as usual... 🙂
    1 point
  12. That's good advice, which could be added to the Help for the Error Ring, for instance...
    1 point
  13. BTW, one other use case I've had is "Multiple applications read/write to common config file", which requires careful thinking about preventing one App from overriding changes made by another App.
    1 point
  14. Oh, and by the way, the VIP is now available on vipm.io : https://www.vipm.io/package/lv_toml/
    1 point
  15. in "TOML to LabVIEW.vi" Here are the mods that I made. Those cyan VIs are from the JDP utility VIPM package that ships with JSONtext
    1 point
  16. The Linux Kernel does support them but of course they are not called that. The Kernel has to be compiled with the features and I don't know for that device. Check what is available (if at all) by issuing "cat /sys/power/state" in a command prompt. Check how it can be woken up by issuing "cat /proc/acpi/wakeup"
    1 point
  17. It's not listed on the repo, but it is under the MIT license. (It's now been added to the repo)
    1 point
  18. Based on the lack of feedback, I infer that there's little or no interest. But I've been using Y Controls, finding issues, and fixing them. Since no one else appears to have been participating, I haven't concerned myself with backward compatibility, I'm getting close to sharing a new version. Anything made with the old version will be broken.
    1 point
  19. Like most problems, once I had a workaround, I no longer spent any time thinking about it.
    1 point
  20. Have you talked with NI about that? I was debating whether that was worth for me to investigate further. I have learned to let a few versions go before upgrading and the thought of having to recommend using a RTE I haven't tested thoroughly (or even superficially) just for my app to be functional is not too exciting. Where is this written that checking that box meant you HAD to use the LATEST RTE? This sounds like a bug.
    1 point
  21. Your attribute Values need to be valid JSON. You are inputting just strings. Convert your strings to JSON first.
    1 point
  22. I reported the expression node too to the NI tech support guy who's dealing with this bug report.
    1 point
  23. I haven't checked the behavior now, but I did remember this discussion from some years ago - https://forums.ni.com/t5/LabVIEW/Queues-Enqueue-Dequeue-Element-Scheduling/m-p/2367134#M737149 Note that in the post I linked to AQ does say that "the writers are serviced in the order they put in their request to write, so there's never a starvation" and that only the dequeues could be starved, but maybe this behaves differently in limited size queues or maybe this is different in different LV versions?
    1 point
  24. It is a really nice format, but I'd recommend using something else in LabVIEW because of lack of support, unless the EM library covers everything you need. The repo is unmaintained. (source: I'm the author)
    1 point
  25. I've been a big advocate for the Enthought Python integration toolkit in the past. Unfortunately, the product was discontinued when LabVIEW introduced the native python node. I'm still scraping by on this product as I've not found a good alternative, and the built-in LabVIEW python node doesn't meet my needs. Under the hood, the Enthought product was just a TCP link to Enthought's flavor of python called Canopy... which has also been discontinued. This product was fantastic for a few reasons: Canopy environment could be packaged into a lightweight Python runtime engine, which
    1 point
  26. It's in the OP's first message. Then it's worth trying RTE 5.5 at least.
    1 point
  27. I used this library to measure ADT7410 (Analog Devices) and BME280 (Bosch). The Sample code can be found at the end of the link. https://momijimomimomi.com/makers/LabVIEW_MCP2221A_I2C_ADT7410.html https://momijimomimomi.com/makers/LabVIEW_MCP2221A_I2C_BME280.html (Sorry, these are the Japanese language)
    1 point
  28. Version 1.0.0

    52 downloads

    This VI program implements the Discrete Fourier Transform (DFT) to draw any drawn shape outline with epicycles as demonstrated in this video. For more information on the mathematical principles, please watch this video by Mathologer. How to Use: 1.Unzip the attached zip file. 2.Open Main.vi file. 3.Run the VI. 4.Draw a shape. 4.Enjoy animation!
    1 point
  29. I was working on this app over the past year. Happy to make it available under a "Non-Profit Open Software License" Allows any labview application on you computer to utilise your google drive and google sheets. This is achieved through a labVIEW executable (GDLVserver), that gets access to Google drive/sheets with a client secret json file, with OAuth 2.0 authentication. Other labVIEW applications can communicate with the executable, and request google drive and sheets function requests. A LabVIEW client library is included to add to your project files. The GDLVserver will work in the ba
    1 point
  30. With these types of parms I usually pass in an array of bytes. ZCAN_CHANNEL_INIT_CONFIG.vi
    1 point
  31. I can't give a solution for your specific problem, but .net callbacks are easy to understand: - Place the Register Event Callback node from the .NET palette into your VI - Wire the .NET class reference to the Event input (the third connector from top-left! not the first!) -> Now you can select an event from the drop-down box where all available Events are listed - Once you've selected your event, rightclick the VI Ref terminal and select Create Callback VI - Do whatever you want in the callback VI (like trigger a LabVIEW event) Now whenever the event is fired, your callback VI is ca
    1 point
  32. I had never known that the controls inside the cluster contained in the 2d array were unavailable to be used in the Edit Event Handling for this case dialog box. So I just did my best to trigger the events for the boolean controls. Please see attached my attempt. I will be glad to know there is a better way to achieve this. Any ideas? Kind Regards Austin Triggering Events For Booleans in an Array.zip
    1 point
  33. You need to use Dynamic Event registration to get the event. Use the following code register the event: And inside the event More info on dynamic events. Ton
    1 point
  34. Yair- Works! For our application, I just had to add a SetWindowPos (hWndInsertAfter = -1) afterward to keep the window in front (topmost)... Thanks for the help! Set Calling VI Wnd Topmost & Active.vi
    1 point
  35. Sorry, my examples posted earlier were in 8.5.1. Here they are back saved to 8.0. Bruce Create Shortcut.vi Set Shortcut Properties.vi
    1 point
  36. Apparently, NI has changed there Support's website. - you cannot write a description of a problem. You choose your preferred communication means and write a one-liner topic, press "Send", and... wait to be contacted by NI. - you cannot provide example files when filing a bug "report". You can only provide "steps to reproduce". I guess there are so few bugs nowadays in LabVIEW that NI figured they could get rid of the whole obsolete process of filing detailed bug reports.
    0 points


×
×
  • Create New...

Important Information

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