Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by jacobson

  1. Where can I sign the petition to hand over NI's social media accounts to you?
  2. As a contributor to other packages I would like acknowledgement for those contributions. This was from our user group and the general idea was that package owners can build a self-brand of sorts by being attached to popular packages but if someone makes significant contributions to many successful packages there should be some sort of recognition. I think the OpenG libraries are a good example where there may only be one owner but I'm sure there were some large contributions from several people that led to the overall success of the project. I don't know the best way to do this but the simplest might be to have a list of projects that you are a major or minor contributor to. You might be regarded as a minor contributor for any packages which you submit any meaningful code (some bug fix or new feature) while being a major contributor might be an acknowledgement from the package owner. In my mind a package may have a field for major contributors and the package owner could curate that list and link to other users.
  3. In 2014 I took a 1 credit Fotran course. I got a degree in Mechanical Engineering so it actually ended up being the only programming course I ever took in college.
  4. Sounds like a good idea if your goal is to get other programmers to hate you.
  5. I noticed all of the repos have their own ToDo.txt. Many are empty but for those that are not, you might want to create an issue for each item. I don't know if you can create a wiki for an organization but I would also want to be able to find information on how to contribute and some specifics like what LabVIEW version is being used for development, expectations on testing, and build/release process.
  6. I know right? Reality always gets in the way of our perfect plans.
  7. JK, surprise customer onsite means I won't be back until Wednesday night (hopefully in time for the dinner).
  8. I'll probably be able to attend a presentation or two each day. I'll also be there for the Tuesday night meetup at the Hideout.
  9. I see two general classes of errors. The underlying communication is just TCP/VISA primitives so, in many cases, the API will just throw standard connection errors (error 56). For specific Modbus protocol error codes (ILLEGAL DATA VALUE) should also be thrown as errors and look to have the value -389110 - ErrorCode. Now what exactly you do with those errors is up to you.
  10. I would say here you are just describing what an Actor does and nothing specific to OOP. An Actor can be an object but doesn't have to be from my experience. I personally think that this use of inheritance can be the most difficult to actually understand/maintain as well. If you've ever used an NI's Actor Framework where the inheritance reaches depths of 5+, trying to understand what the Actor does can be quite difficult (though someone might claim this is because they violated SRP). Perhaps I'm missing some historical context though and should read some older papers.
  11. Not a lawyer but I suspect it's a bit of a good faith kind of thing similar to Visual Studio Community Edition or Visual Studio Code. I also imagine the licensing cost might be cheaper than the potential of getting caught and NI wanting to do something about it.
  12. 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.
  13. 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.
  14. Would you be able to summarize your findings in a table? I'm also interested in what frameworks/methods you were thinking of.
  15. jacobson

    LabVIEW Memes

    Screwdrivers are $29.99 though, that's how they get you.
  16. 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
  17. 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.
  18. Monnie would be the pleased-est to know how many terminals a VI could have in NXG.
  19. Just ask Bob L. It's Flarn, just assume he's talking about something that you're not supposed to touch.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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.