Jump to content

Norm Kirchner

NI
  • Posts

    822
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by Norm Kirchner

  1. You need to disable the 'Lock Panel (Defer Processing of UI) until event completes' option for the event case.

    What's happening is that the event structure is locking the UI thread until all code inside of the case completes.

    In your case you've got another UI coming up which you need to interact with for the case structure to complete.
    A bit of a catch 22.

    It might feel wrong that it's happening to you, but there are a variety of good cases that that feature exists and behaves as it does.

    More commonly, for what you're trying to accomplish, people will make action loops which might receive a message to start open another panel instead of calling immediately from within the structure.

    However that's a more complicated solution and if you're just trying to keep things simple, then just unclick that option and you'll be off to the races.

     

     

    2019-04-28_2249.png

  2. On 6/6/2018 at 9:33 AM, Mads said:

    you cannot use them in classes if the VI is to be public....:( It then breaks because inlining it means accessing private data in the calling function.

    Can you clarify a little or throw up an example.

    Do you mean you want the .vim to be a member of the class or used inside a public VI in the class?
    I presume you mean the former.

    What happens if you use private accessors in that VI instead of calling the unbundle directly?

  3. All,

    Thanks for chiming in. I actually hadn't heard of the promise of TS Lite and will be sure to bug the powers that be about it.

    All in all, most things here resonate with the themes I've heard before and am glad to have ammo in hand to go to the conversation with, as it's gotten delayed; so feel free to keep chiming in.

    If I had to sum up the big points

    • Cost: LV exe is free cheapest TS deployment gets 500+
    • Simplicity: Simple enough needs that can get away without the extra features in TS
    • Parallelization: not easy to implement or visualize parallel tasks
    • Training: Don't want to learn another tool myself to dev or for other people to use; just not intuitive enough
    • API woes: Buggy in important areas; hangs between LV
    • Data Access: Getting data around, into and out and between the modules can be challenging
    • Deployment: Just doesn't go smooth
    • History: Been burned before for one situation, why go back
    • TestStand Lite: when please?
    • UI Editor: complicated and overloaded to the point of distraction
    • UI Tester GUI: Understanding components and creating in LV is an untenable beast

    I hope that is a good representation.

    ~,~ The Captain was here

  4. This is a terrific little piece of code! Thanks for working it up.

    Have you thought of possibly making it filterable based upon what color it's going against?

    The reason being is that I see this as a great addition to the current coloring for plots and default color sets, especially when you change the background from light to dark, or vice versa.

    See plot 12 for example

    2018-05-30_1414.png

  5. I know many people never go the route of using TestStand, choosing to roll their own sequencer and make it work (as I did once upon a time)
    However I'm starting to hear from a few folks who adopted TestStand and are going back to try to make their own sequencers (as I hope to never do)
    So, I shook the corporate tree some and have a meeting tomorrow for which I'm representing y'all, based on what I was hearing at NIWeek

    That being said, if any have gone the route of TS only to turn back, and you'd like your voice shared inside the guts of the mothership, please do share here.
    FWIW, If you've got specifics as to why you've never tried, that would be best for another thread. Thanks for understanding

    ~,~
    The Captain was here

    Tag anyone you may know have done the same

    @Mark Yedinak@Mark Balla

  6. On 7/25/2017 at 2:29 AM, 0_o said:

     I remember NI pushed their new VSA device and had a special software to program it, however, at the moment I'm not going to use this device, I just want to control automate the current scenario through LabVIEW.

    <for future reference>

    You might be speaking of RFmx for doing RF measurements on our VSA products.

    This 'Measurement Driver' makes short order out of taking common RF measurements, generic and standards based alike.

    It does not have a personality specific to doing EMC testing or EMC specific measurements.

    There is likely a good deal of overlap between the ESU40 measurements and what we can accomplish with RFmx, however I can imagine that the ESU40 has a lot of EMC usability features that you won't find in RFmx.

    Another item that might be of interest is investigating RealTime Spectrum Analyzer functionality, in the future should you need something more flexible than the ESU
    http://www.ni.com/webcast/3693/en/

    What ends up happening with the above is that you gain some serious power to do things like frequency mask triggering as well as custom pre-processing data reduction; but it comes at the cost of not having as complete a solution out of the box.

    Hope that all helps

    ~Norm

  7. In order to better answer the question, having some knowledge of exactly which VI (blocks) you wish to put your data into would be helpful.

    However to emulate what I believe you're trying to accomplish see below.Capture.PNGthink you're looking for 

    Now as far as measurements that you specifically need, you should start to explore the measurements built into LabVIEW. This image is just the top of the iceberg.

    Capture.PNG

    Good luck and welcome back to the LabVIEW world.

    Thanks for coming to the community to find your way

    Best,
    Norm Kirchner

    ~,~ The Captain was here

  8. To keep things complete, I've attached the actual presentation that resulted.

    Thank you all for your feedback, and I encourage anyone to take this and use at their local user group meeting.

    Believe it or not, I was able to pile-drive through these in 7 minutes 30 sec/slide on average.

    However it could have gone for 30 min or more. The audience gave positive feedback on the material

    Make Friends, Not Flames.pptx

  9. I'll be giving a presentation this week called "Make Friends not Flames :: Online Forum Etiquette"

    I thought I would pass this across the community to get a pulse on if y'all think this is a well balanced list and no massive misses on my part.

    I know that we have a great document at LAVA Forum Guidelines https://docs.google.com/document/d/1Ce1aE4Kz6h1W5vdQER8LIc_9ZvW8QhHLQoqoVjcWw10/edit
    But we all have our little peeves, and this might be a fun airing of the grievances.

    It's for a 7 minute presentation, so the idea is 30 seconds each on average.
    The idea is to hit things for people who are newbs and veterans.

    DON"T

    1. Abuse the Private Message (PM) Feature
    2. Admonish a newb publicly
    3. Turn a commuinty forum post into a 2 person flame war
    4. Presume that people have knowledge of what hardware your using and how it's API / Interface works
    5. Be a 1 hit wonder
    6. Post Across multiple forum sub-forums
    7. Be a clueless homework hustler; we know what you're doing, do it the right way

    DO

    1. Search the best you can with site:lavag.org {your search}
    2. Remember what it was like when you were young and clueless
    3. Be apprecaitive
    4. Give ample detail in the form of: high level diagrams, videos, pictures, code and big picture purpose
    5. Share novel things that you figure out
    6. Start out saving for previous and make everyone's lives easier
    7. Be an active participant and share the love!

    In the end it might be a flop, but I hope it encourages those CLA in India to kick things up a notch.
    Your short term feedback will be appreciated and rolled right in.

    ~,~
    The Captain Was Here

     

    /EDIT :: Presentation Added Make Friends, Not Flames.pptx

  10. Leave it to the RF guy to whip out the DSP.

    The easy way to compare the phase of two sinusoid of the same frequency. 

    Multiply the signal by another sine of the same frequency at 0deg phase and in parallel multiply it by another sine of same frequency at 90deg phase. Take the average of both of those signal into a re/im to polar, snag out the phase value and convert to degrees. 

    Do that to the other signal as well and find the difference between the signals 

    That is the easiest way to get what you want and is very immune to noise. 

    I'm about to board a plane otherwise I'd attach the example. 

×
×
  • Create New...

Important Information

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