Jump to content

jacobson

NI
  • Content Count

    102
  • Joined

  • Last visited

  • Days Won

    7

jacobson last won the day on February 11

jacobson had the most liked content!

Community Reputation

24

About jacobson

  • Rank
    Very Active
  • Birthday 06/05/1992

Profile Information

  • Gender
    Male

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since
    2013

Recent Profile Visitors

1,790 profile views
  1. The red dot just indicates that LabVIEW will be coercing the data for you so whether there is a loss of information depends on what the data is being coerced from and to. For instance, if a U8 is being coerced into a U16 there isn't any loss of data but if we instead coerce the U16 into a U8 we are losing the top 8 bits of data (depending on what we know about this data this may or may not be an issue for us). FXP conversion will likely lose information because LabVIEW tries to preserver the value rather than keeping the bit value and changing the interpretation of those bits. If you attach the project you are working out of we should be able help explain what would happen for your particular case.
  2. What c-series module are you using? In the project, if you right-click the module under the FPGA target, some have the option to change their I/O between calibrated and raw. In this case raw would probably be much easier to work with.
  3. Would you be able to summarize your findings in a table? I'm also interested in what frameworks/methods you were thinking of.
  4. jacobson

    LabVIEW Memes

    Screwdrivers are $29.99 though, that's how they get you.
  5. It looks like the morning sessions (as well as the keynotes) on Monday are limited to Alliance Partners but the afternoon technical sessions are open to everyone. Source: https://forums.ni.com/t5/NIWeek-Discussions/2019-NI-Week-Alliance-Day-open-to-the-general-public/td-p/3883876
  6. It's from "Connector Pane Pattern Reference.vi". There's no code it's just an indicator showing the pattern numbers and the terminal index mapping. Just a handy reference for scripting.
  7. Monnie would be the pleased-est to know how many terminals a VI could have in NXG.
  8. Just ask Bob L. It's Flarn, just assume he's talking about something that you're not supposed to touch.
  9. Did you post this before you started working for NI?

    Seems kind of funny to see an NI employee asking the community for help with XNodes of all things 😄

    1. jacobson

      jacobson

      Started working at NI in 2014 so this was after that. At the time, I was an Applications Engineer and this was a side project so I didn't really want to bother any of our developers.

      I ask enough of our R&D team for work problems so I'll bug LAVA or our local user group with problems I've run into from more personal projects.

    2. flarn2006

      flarn2006

      Ah ok. Just thought it was funny :)

  10. This may be a misunderstanding from my end but I thought if you did not include any license then your code defaults to "not really open source". I'm not a lawyer but choosealicense.com/no-permission/ is where I was reading that and I have used the site before to get the TL;DR for licensing.
  11. You might want to give https://tldrlegal.com/ a look although as I am also not a lawyer I can't really verify the correctness of any information they give. I would start by looking at the most popular but the ones I hear about most are BSD, MIT, and Apache. The NI DCAF tools are all under Apache 2 which lets users do basically anything they want to do with the code but doesn't hold you liable (again, not a lawyer). I don't know of a good way myself. GPM (https://gpackage.io/) looks promising but of these things very much rely on a network effect. GPM also looks much more focused on project libraries and not editor enhancements such as quick drop and right-click plugins or even templates like TLB' or DQMH. Because there isn't really an easily searchable centralized repository of LabVIEW code that I know of, I think you have to be a good self promoter if you want people to use any LabVIEW software. I think Fabiola (DQMH), Q (QControls), and Derek (Solution Explorer, GPM, MGI Stuff) all promote their stuff well if you want to see what they are doing (I think it's a mix of quality products, quality documentation, and continued promotion of the product) Also make sure to check out the Distributed Control and Automation Framework (DCAF) when you are starting your next embedded control application.
  12. If it's something meant to go in the Tools menu, a QD shortcut, or right-click menu then you might want to make a package. Other than that I would agree that the menus and packaging of an API would be the last thing I would do.
  13. What exactly would be put in this repo? Would the LAVA CR essentially become this repo? Also, would there be any gatekeeping process? I mostly want to understand what the quality of code I could expect from the repo would be. If anyone could submit anything they wanted I would probably not ever take a look.
  14. I couldn't find a method for "Convert Instance VI to Standard VI" as you can from the right-click menu but it looks like if you get the VI reference from the subVI you get a reference to the instance VI so you could potentially just copy the block diagram and put it into new VI (reconnecting the terminals might take some work). I'm not sure what the best way would be to figure out whether the subVI is a VIM. If you grab the subVI reference and try to pull the VI Path you just get <not a path> and the VI name returns some crazy UID.
×
×
  • Create New...

Important Information

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