Jump to content

LogMAN

Members
  • Content Count

    454
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by LogMAN

  1. I don't know if there is any documentation for this, but a link points to a resource external to your project. You can create your own links by adding files that are not located in your project folder. It looks like your component is located on a shared network location? Maybe the conversion tool uses UNC paths and the project expects mapped paths? Maybe you can re-add those files to get it to work.
  2. There might be a typo in @Bryan's example. The first byte should be 7E instead of 7F (based on the previous data). Still, this is guesswork at best and not much better than brute forcing every possible combination. You have proven that your code works, so this is a good time to talk with the supplier. Maybe they can provide you an example or verify that the data you are sending is correct.
  3. In the article it says: "The ability to create modes and overloads isnโ€™t publicly available in the newest version of LabVIEW NXG; however, weโ€™re looking to extend these features to our user base soon."
  4. Are you okay with people using your work and selling it as their own, perhaps making a lot of money with it? Do you want to be attributed for your work, if someone uses it in their project (or sell it as their own)? Are you okay with other people using your name to sell your work as their own? In my opinion BSD 3-Clause is a good choice if you want to be attributed without any liability or warranty. Look at SQLite Library and JSONtext for reference (they use BSD 2-Clause). Note that BSD 3-Clause is the same as BSD 2-Clause, but "with a 3rd clause that prohibits others from using the name of the project or its contributors to promote derived products without written consent." Unlicense puts your work into public domain, so there is no copyright holder. You also don't reserve any rights to your own work (anyone can do whatever with it). MIT is in some ways similar to BSD but without the need for attribution. It is a pretty popular choice though. DBAD and WTFPL need to be placed in every source file, because they apply to single files only. They also don't really address the issue. If an author didn't want anyone to sell their work as their own, they probably shouldn't place it under public domain in the first place. I'm always surprised by people who make their work open source or public domain and then complain if other people use it. What did they expect?
  5. There is an option to mass-edit VI documentations in VIPM, although it's probably not the right tool. Maybe you can hack a solution. I don't recall if there is a function for this in the OpenG libraries, but they all have license notices and I would be surprised if they were edited by hand. There is a tool for that (of course): https://choosealicense.com/ If you don't want to accept contributions or issues for your repository, make it an archived (read-only) repository or put a notice in your readme file (anyone is free to fork and change it anyway). There is a blog post on how to do it on GitHub: https://github.blog/2017-11-08-archiving-repositories/ Vision is not my area of interest, so I wouldn't use it as a product, but I like to browse projects to learn about problem solving strategies and perhaps find a few nuggets. Don't worry about style or documentation, especially if it's a gift. I'm sure there are a few people on LAVA that are more than happy to get something new to fiddle with ๐Ÿ™‚
  6. Very strange. Ping looks fine. TTL=128 also indicates that the machines are on the same network, so packages should send fine. Are you able to copy large files between the systems with reasonable speed? Also, you can use Wireshark to monitor traffic between your machines. That way you can check if a package gets lost, resend or blocked by other data. In the past I had trouble with cheap NICs that weren't able to keep up with many small packages because of checksum offloading. This was particularly problematic on Windows 7 and seems to be fixed on Windows 10. You can try disabling it in your NIC settings. Note that there are multiple offload options.
  7. @kronoseleven What is the ping between your clients? As @drjdpowell mentioned, 16.2 seconds is not normal. The no-delay function won't do much of a difference.
  8. It works slightly better if you select the control first (the dots stay visible). Still, poor design choice. They actually don't work well on different zoom levels. Edit: How do you attach videos but not display them into a post (does it automatically for me)? This thing is freaking huge... NXG Resize Array Zoomed.mp4
  9. Here are some of mine. SystemDesigner - Although it is essentially MAX and only works with NI hardware, I like the fact that it provides an overview of the hardware, access to various documents (pinout, specs) and the ability to create and test measurement tasks from within LabVIEW. Not to mention the auto-generated code when placing tasks into VIs. Captured Data - Finally I can easily capture, export and import data without having to write custom code. Capture data once and use it often. This is very useful for testing code in development and prevents misuse of "Make Current Values Default", which tends to bloat VIs. It is also possible to just drop data into any compatible control (i.e. graph) without any manual labor. Build Queue - It is somewhat broken, but I like the fact that it can build packages in parallel. There is great potential for much faster builds when compared to CG, especially for large an complex projects. Learning - I like the way NXG guides users through learning projects (of which there are quite a few). Highlighting elements in the UI is very helpful for self-paced learning. Online Help - Not specifically a feature of NXG, but I like the way the new manual is structured. The context help could use some improvement though. Controls and indicators - I like the design of NXG controls and indicators. They look much better than modern controls in CG, especially when used in combination with a Windows 10 theme. That said, I hope they add support for system controls soon. Automatic File Organization - This is probably number one or two of features in NXG I really like. Moving files inside a project now automatically moves files on disk. No more housekeeping. Still, I miss virtual folders a lot.
  10. You probably got it from this KB article (also includes VIs for other platforms): https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NZfSAM
  11. If memory serves right, this is because LabVIEW does not take Windows themes into account. Essentially, the window drawn by LabVIEW gets surrounded by a border that is provided by Windows. You should see different results if you change your theme to one that has smaller or no borders. Also, Window Bounds does not include the window border. It is implicitly mentioned in the context help: "The four elements in the cluster are the top, left, bottom, and right values of the front panel window, which includes the interior region, scroll bars, title bar, menu bar, and toolbar." Your best bet is to use Window Bounds and subtract the border size manually. Unfortunately, it will break again if the user changes themes.
  12. I think what you are looking for is this: I haven't tested it, but your VI should stay within the boundary of a single screen.
  13. This is what happens when you change the UI scaling while NXG launches (because what else is there to do?) And icons can be a little frustrating at times... Icons make me happy.mp4
  14. One thing I absolutely like about NXG is the fact that it goes to extreme levels for absolutely no reason. What could possibly go wrong? Yes, this is a single VI. NXG 4.0 has a terminal limit of 128x126x126x128. Yay, no more clusters
  15. I'm putting this out here in case anyone missed it. NI has made all of their online training courses available for free to the global engineering community. The period was just extended to at least May 31, 2020 (previously April 30, 2020). Those who are new to LabVIEW and want to start with LabVIEW Community Edition should take a look at Getting Started with LabVIEW Community Edition. For further reading, check out NIโ€™s Response to the Evolving COVID-19 Situation.
  16. You are unable to activate the community edition with a pro license. It is always activated with a 365-day community license.
  17. During installation you must accept the license agreement. Only for non-commercial use. It installs to "<National Instruments>\LabVIEW NXG 5.0" (same as pro) VM seems to work for me this time (probably because installation is actually offline).
  18. This works for me: https://www.ni.com/en-us/support/software-technology-preview.html And I always thought the only way was via the beta program: https://www.ni.com/support/beta-program/
  19. That is even better, haven't thought about it. Is there any chance of this changing? It would also be really great to have an idea exchange for NXG to discuss things like this. I want to support the effort, but sending out one-way tickets is very frustrating Thanks for reminding me, this is something I'm very excited for (and almost forgot about ๐Ÿ˜…)! You are right, those icons make it super easy to distinguish. Kudos for spending time on this
  20. (Un)fortunately only someone who actually worked with CG is able to tell the difference, which makes NXG easier to sell to new customers than existing ones. Just a few clicks and you get your shiny graphs, overviews or packages. @Aristos Queue mentioned before, that NI lost business opportunities because of the old fashioned UI of CG. I'm pretty sure we are not the target audience of NXG at this point. Maybe in the future. Until then we can still spend our money on CG. Really, there is no incentive for NI to listen to our complains right now and I don't expect them to. Nevertheless, I'll keep an eye on NXG and on how it evolves in the future. Until then we can share our experience and ideas here and prevent each other from regretting horrible decisions ๐Ÿ˜‰
  21. Yes, the execution system hasn't changed but the appearance did, at least from a users perspective. LabVIEW CG has a clear distinction between the two, which doesn't exist in NXG. Classes and typedefs are both represented by the same kind of object (G Type). Although their abilities and representation is different, they are represented as the same kind of thing. If you take a control in LabVIEW CG and turn it into a class, you choose "Convert Contents of Control into class" and it becomes an entirely new type. In NXG, however, you can simply add class functionality. Now, unless a typedef is a class in secret, there is no way to simply add class functionality without converting it into a class first. Maybe I'm reading too much into it, but this is how it appears to me. Yes, the amount of types and what they represent didn't change and I understand the technical reasons for how they are implemented, but why use the same file extension? I work with engineers who don't know the difference between a class and a struct (and they don't care). What I'm afraid will happen is this: Here is the same thing in CG For all I care, the file contents of a typedef can be equivalent to a class. I don't even mind if a typedef was a class in secret, as long as they are easily distinguishable by the end user (i.e. me). That is currently not the case. That is good news. Maybe it was addressed in 5.0, can't wait to try it out. Need to wait for the VM to finish though.
  22. You mean the same committee that works with Visual Studio all the time? I wonder where they get their ideas... Yes, that is a bummer. Actually, the thing they call "G Type" serves as a strict typedef, but it is really just a class that doesn't inherit from gObject (it inherits from Void). Since classes cannot be nested in LabVIEW CG/NXG, the only way is to put both of them inside a common library. Now, where have I seen this concept before...
×
×
  • Create New...

Important Information

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