Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 09/28/2021 in all areas

  1. Since Latin for six is "sex", we could have gone for "sexidecimal".
    4 points
  2. "The software you are refactoring had one and it is too costly to change the training materials". How's that? It is likely that a great deal of pressure had to be applied to even allow a rewrite and the manager probably had a hard time arguing for a budget to do it. Getting hot under the collar over a button isn't a hill I would die on. I would concentrate of making my life easier supporting it going forward than what it looked like-which was decided a long time ago.
    3 points
  3. Shameless plug but feedback would be great since there's a lot that's changed. A few more eyes on it would help immensely before going live. The Encryption Compendium for LabVIEW (ECL) has had a major update. It's completed and a couple of weeks away from release as the documentation is in progress so there may be a few errors on that front. It's a commercial package so the gibs free crowd will, I hope, be disappointed. So what's new? IPv6 support (Thanks Rolf for your help with that). I've been wanting this for sooooo long but it required moving away from the NI primitives and nasty text programming. I bit the bullet and now have it, although a lot less hair SFTP Since NI released their poultry offering I thought I'd productionise the SFTP I had in my back pocket for quite a while and offer something actually useful. It comes with a full client example and supports recursive uploads, downloads and deletions (be careful with that last one). It also uses events for progress and status feedback in a similar fashion to the Websockets below. The event topology will be come a common feature of protocols in future additions. Websockets The ECL is a better home than a separate product since it was very difficult to distribute when trying to support TLS. Reworked from the ground, up it sits nicely in ECL and is the start of more encrypted protocol support in the future. Oh yes. Almost forgot. The ability to use Windows Certificate Store because ... why not? (and I wish I had thought of it ) If anyone would like to play before its release proper in a couple of weeks time, I can give you a trial copy (valid for 30 days). PM me and I'll send you a link.
    3 points
  4. From your project image you seem to have many conflicts. It's likely that you are picking up another version or VI's in a different location in your project. You need to resolve the conflicts before any troubleshooting can occur.
    2 points
  5. What about this... https://www.jki.net/profusa?hsLang=en or this... https://www.jki.net/radx?hsLang=en or this... https://resources.jki.net/smarter_sorting or this... https://resources.jki.net/femtometrix-case-study or this... https://www.jki.net/apollo-fusion?hsLang=en or this... https://www.jki.net/kairos-power
    2 points
  6. I am actual about to commit to making the next release in LaVIEW 2019, rather than 2017, as VIMs were very new in 2017 and both buggy and of limited capability.
    2 points
  7. Today I Learned... you can convert from upper case to lower case like this! Clever design hidden in plain sight. See for yourself
    2 points
  8. At one point I heard NXG called "Better LabVIEW" and someone else suggested the real name was "Beta LabVIEW". I've also heard of it called to as LabVIEW 20xx, or Current Gen (CG). I like Lab-deja-VIEW.
    2 points
  9. If you are tryin g to dereference a string pointer then try this. PtrToStr.vi
    1 point
  10. Also these custom graphs, 100% 2D picture control. The lad who did that is a ninja!
    1 point
  11. I use to work at qmt (Qualimatest), a lot of effort was spent on UI/UX
    1 point
  12. In the example I posted earlier there is a tab at the bottom which (seemingly) scales nicely. It is a trick though...I described it a long time ago here. Maybe someday we get this implemented.... Or better yet, anchoring.
    1 point
  13. There's a UI User group over on the Dark Side. If you hunt through it there are a few UI's like Star Trek, Media Interfaces and iPhone simulations.
    1 point
  14. I have a few UIs and UXs that I'm proud of, but I don't know of many that I can share readily. Tabs are fine, but don't scale well. Often times when I want a tab I will end up replacing it with something else. An easy change that scales better is a single column listbox which inserts a VI into a subpanel instead. The listbox and subpanel can be in their own pane, and set to fit to the pane, and scale with it. I posted a few UI tools over the years like the Ribbon Interface toolkit, that can contribute to a nice UI. I have a sequence editor with drag and drop, looping, conditionals, go to's, that works pretty well. And I have used a set of images at the bottom as a tab replacement that shows icons along a process of setting things up. There is a back and forward button on the bottom that goes to the next step, or you can click on the icons at the bottom and it goes to that step in the process. This is a 2D picture control that can be updated easily with a new VI to be inserted in the subpanel. This sequence runs on real-time so no TestStand, and has other normal shortcut features like copy, paste, delete, save, and select all. It also has file extensions so double clicking on a file opens it in the editor, and dragging and dropping a file to this window will work, prompting for unsaved changes if there are any.
    1 point
  15. Stop isn't to close an application. It is closer to a reset. It is to stop/terminate/curtail the currently executing task and return the application to a known state. The application is still running. The application is still initialised and the application is still in contact with devices. In desktop terms; a "Stop" is to an exit/close as an exit/close is to a reboot. Not all applications need a Stop button (think of things like Notepad) but if you have a Start button you will probably need a Stop button.
    1 point
  16. Hi, My guess is that you have set the Get Image method to use 16 bit colors. Use 24 bit and it will show up correct (I recreated and solved the issue just now by generating a front panel image of a screenshot of your original colors).
    1 point
  17. Hi folks, Long time reader, 1st time poster (old account got deleted? couldn't recover it) LabVIEW and coffee? Heck yeah, any day. You'll see my spaghetti code come to life. 😄 No, but seriously ... I've always been a big fan of LabVIEW, and ever since NI discontinued their motion offerings, I was really sad for a while. (Maybe because motion was also my specialty as a systems engineer at NI. 🙁) Back in the day, NI had great motion products that worked well with LabVIEW. They worked great for pick-and-place systems, automatic positioning, test systems where you need to move the DUT or sensor around, etc. Well, now I left NI, and being located in Taiwan, this give us an advantage for sourcing various electronics and embedded systems. My partners and I started TENET Technologies this year, and I pitched to them and said ... you know what? What if we made a motion controller for LabVIEW users? I'm reluctant to believe that, just because NI has forfeited this market, that LabVIEW users don't need motion controllers anymore. Without NI's solution, users are burdened with having to risk compatibility issues with other motion controllers, AND also have to deal with APIs that look like dismissive afterthoughts. I've researched many different APIs from 3rd party vendors, and usually they look something like this: Uggh, yuck. This really defeats the purpose of using LabVIEW, by having an ill-defined API. We couldn't stand it anymore. With TENET GECO Motion, we set out to make motion control a first class citizen in LabVIEW once more. See our solution here: https://promo.tenet-tech.co/motion So recently we just released our first version, and we're continuously looking for feedback to make it better. I'm running a survey to get feedback for your needs and wishes in a motion controller for LabVIEW. We can't get to everything right away, but feedback from the LabVIEW community would be SUPER helpful. Survey is linked here: https://forms.gle/Zz31RcsaX5keS4Pg9. As a token of appreciation, I'll be giving out Starbucks $10USD gift cards to 5 lucky winners. Survey ends by the end of this week, hope to hear from you! 🙏 -John Wu TENET Technologies
    1 point
  18. It's just an integer value. You can either just pass 0, 1 etc to that parameter or create in LabVIEW an enum that has these values assigned to the individual enum values. What doesn't work?
    1 point
  19. The current pink wire datatype needs to remain as a "byte string" plus "locally encoded text string" to maintain backwards compatibility. A new type of wire (Purple? Darker than pink, paler than DAQmx wires?) should be introduced as a "universal text string" datatype. Explicit conversion (with user-selectable encoding) should be done to change pink wires to purple wires and vice-versa. Binary nodes like "TCP Read"/"TCP Write" should only use pink wires. Purple wires not accepted. Text nodes like "Read from Text File"/"Write to Text File" should ideally only use purple wires, but they need to allow pink wires too for backwards compatibility. VI Analyzer should flag the use of pink wires with these nodes. Perhaps a project-wide setting could be introduced to disable the use of pink wires for text nodes.
    1 point
  20. The lvanlys will return an error code if there is a NaN in the array, this extra feature probably explains a part of the difference in exec time.
    1 point
  21. Not natively in LabVIEW. You have to use the IShellwindows interface in windows 10.
    1 point
  22. You didn't look very hard; did you! We've just been discussing the callback functions and posted examples of using them. The answer to your question though is no. you cannot use them in the way you are thinking.
    1 point
  23. In the Window menu on the LabVIEW toolbar there is an "All Windows" [last] choice (CTRL+SHIFT+W) that pops up a dialogue which you can sort. There is also a VI hierarchy and Class hierarchy graphical representation of VI's that are in memory that are accessible from the "View" menu in the toolbar. That may be easier for you if you are familiar with the hierarchies and the project is not too large (also highlights the importance of VI icons).
    1 point
  24. You could implement it using the LabVIEW memory manager but it's not for the faint-at-heart. I once played with it for a circular buffer which isn't a million miles away from what you need. Oooh. Look. Words similar
    1 point
  25. Synology is great, I love it for my home NAS. But.... I have a strong suspicion we are all having a sensible conversation in response to a spam original post. 😂
    1 point
  26. I can say without any doubt that online clothing stuff is good quality or not.
    1 point
  27. Thank you for posting this. It's very helpful and informative. I was noticing icon font issues in LabVIEW 2020 Community Edition for Linux, so it doesn't look like NI has fixed (or knew about) the issue in LV 2020 for Linux either.
    1 point
  28. You will have to setup the triggering, similar to the snippet below. I don't have those DAQs, so I can't test it. Edit: You might have to do SW trigger, Each DAQ will have its own trigger source (PFI0), and the software will generate a transition on both lines.
    1 point
  29. Of course there is something they could do. I expect the use of the ANSI versions of the file operations is making them resistant. I've my own set of compane equivalent of the native file operations that do it just fine - it's the Path Control that is the problem.
    1 point
  30. And I incidentally just had an application that I had inherited from someone and needed to debug where GetValuePointer.xnode would return with an error 7 : File Not found, when executed in a build app. Rather than digging into xnode handling and find out why on earth it was returning such an error (for a reportedly valid pointer created with DSNewPtr) I simply replaced the whole thing with a call to StrLen and MoveBlock and was done with it!
    1 point
  31. Okay so I wrote some code back in the 2011 era for doing some graph stuff and never used it. As a result there are a few places that the code could take advantage of modern functions (limited events, array tunnels, conditional, and concatenating, VIMs, even Set and Maps) but in any case I have it here for others to take a look at and use as they want. I don't intend on updating this further. It all started when I found the built in graph controls to be limiting in terms of signal selection and control. I wanted a way for a user to select the signals they want and then show those on a graph with a shared time scale. The problem was at the time the checkbox selector on a graph could have a scroll that couldn't be controlled. So I started with a single column listbox showing all signals and allowing multiple to be selected. I wanted to see the current value so I added that. Scope creep kept going until I'm left with this thing that isn't done, but isn't terrible. In this demo there is a subpanel mode, independent windows, pause and resume, the normal graph palette controls, independent Y axis scaling, coloring, buffer size control, visible signals selection and values, and a few other things. It was intended to be used in places where speed and exact values weren't used. It was more or less a place where all signals of a system could be seen slowly. It uses a few things I've posted on LAVA before. My Variant Repository, Array VIMs, and Circular Buffer. Here is a video. Circular Graph.vipc
    1 point
  32. Over on reddit someone asked for suggestions on how to make a sliding UI like you might find on your phone. I thought it was a fun challenge so here is my very rough draft that could probably be turned into a QControl. And a video. At the moment you can only change the settings of booleans and of a selection like the days of the week I show. I planned on putting code for handling string and numeric value changes but probably spent too much time on this already. Android Sliding UI Demo.zip
    1 point
  33. Version 1.0.0.1

    205 downloads

    This VI allow an easy way to create HTML color table in the LabVIEW report generation toolkit. This VI should be connected to the "Append User Formatted HTML to Report.vi". For this version, all the column are the same size. But alignment and color of each cell can be defined. Please rate this file if you download it. It's free... you can at least give some second of your time to rate it... I spend some hours to make it... Enjoy
    1 point
  34. Version 0.9.4 LV7.1

    1,422 downloads

    Installation: Copy the contents to LabVIEW xxxx/resource/plugins Abstract: Speed up creating new vi's from templates! It's using the 'new vi'-hook to create the new vi from a custom template. A plugin architecture allows to map different templates to the keyboard. For a quick-start, try Ctrl+N followed by 'H' (without releasing the Ctrl key). Detailed Description: When using New -> Blank VI from the Startup Window File -> New VI from the menu of any vi or the Ctrl+N shortcut the lv_new_vi.vi hook is called. Releasing of the Ctrl key (when using the shortcut) uses the Default.vit. The next key-press k creates a new vi from the template [...]/plugins/lv_new_vis/templates/k.vit. This is case insensitve and only works with a..z and SPACE. If no template is found or if an error occures, the default action of LabVIEW (empty vi) is performed (Failsafe). In addition to normal vi templates it supports global vi templates and control templates. Even more customization is possible using special tags on the vi or vit. Use [...]/plugins/lv_new_vis/tools/lv_new_vi__TagEditor to read and set them: isBD_ToFront? bring the block diagram in front instead of the front panel isRunMe? will instead run the vi in the template folder. Use this for wizards, more sophisticated scripting and other dialogs. Examples (V0.9.3: seperate ogp package): Try the following keys to see the different possibilities: f: normal vi, FP at front b: BD at front g: global vi c: control w: wizard h: help You do not need to delete the demo templates, a w.vit will load even with w_example.vit present. Compatibility: Developed in good old 7.1 and tested with 2010. I don't know if it works nicely with the project explorer and did never try to use it with projects, libraries and classes. Planned Features: * Error logging * Redirections via Config file (I will link the standard templates) (Edit: It's faster to just place them in the templates folder.) V 0.9.1 Fixed issues with the Application Instances of LV8.0 and higher. Wizards are still launched in the diaolog App.Instance, they need to get the default App on their own. V 0.9.2 Changes: Closing all references Beta: Uses VI Activation Event to abort when the user switched to a different app. (See discussion for details). V 0.9.3 Uses VI Activation Event to check Ctrl-Key when user switches from a diffrent application. Now available as packages (ogp). Uses a seperate package for the examples. V 0.9.4 Fixed issues with 0.9.3: After start of LV, Ctrl+N didn't work the first time Enjoy, Felix
    1 point
  35. Not quote - if you pass the CLAD then you can ask for a present! :laugh:
    1 point
×
×
  • Create New...

Important Information

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