Jump to content

jacobson

NI
  • Posts

    150
  • Joined

  • Last visited

  • Days Won

    8

jacobson last won the day on August 17 2020

jacobson had the most liked content!

About jacobson

  • Birthday 06/05/1992

Profile Information

  • Gender
    Male

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since
    2013

Recent Profile Visitors

3,220 profile views

jacobson's Achievements

  1. In past years there was often a meetup at some random bar on the Sunday night before NIWeek to get some drinks and hang out. Anyone know if there are similar plans in motion this year? If not, does anyone want to meet up somewhere Sunday night?
  2. If you're working for a larger customer they also might have brand guidelines that you can follow. A long time ago I worked with someone from UT Austin and just followed their published branding material. https://brand.utexas.edu/identity/color/
  3. For more general data acquisition systems I'll hear about UEI, VTI, Dewetron, and HBM. Beckhoff comes up plenty but the remote I/O or industrial control space does lead to them having different strengths/weaknesses.
  4. The question below that seems to indicate that there may not be a call for presentations because they'll just pull from previously accepted sessions but who knows. Hopefully there will be good technical presentations still.
  5. The two times we had people in our AE team do this we never got them back 🙃
  6. As an NI employee am I part of the legion of doom in this analogy?
  7. VSCode's October update changed it so directional formatting characters are displayed by default. https://code.visualstudio.com/updates/v1_62 GitHub also added a warning if you are looking at a file with these characters so hopefully more IDEs are being updated to make this vulnerability more obvious.
  8. I would generally suggest just using the language you're most comfortable with. I think Python is generally easier to integrate with but you are limited in data types (no classes). If you're just doing some signal processing though that may be able to develop an interface around that limitation without much difficulty. I also don't think LabVIEW supports the ability to call Python from a specific virtual environment which is definitely annoying. I think the C/C++ integration is a little less straightforward than Python but if you're comfortable with the language and you read the help documentation on the Call Library Function Node and how LabVIEW stores data in memory it's not that bad. You may also have to mess with some LabVIEW memory management functions which can be annoying the first time you use them.
  9. Are you talking about VBAI? I thought Vision Acquisition Software is just the different IMAQ camera drivers so I'm not sure exactly what you're looking to embed from the drivers.
  10. You are correct that phone/email support is now being handled by a separate Technical Support Engineering (TSE) team which is now a career position (meaning they have senior/principal level engineers working in the department). As examples, you now have folks like Darren N and Norm K working as TSEs. This is still a relatively new change (2 years?) so there are still a lot of newer engineers but I think things are moving in the right direction with hiring very experienced engineers and being able to keep engineers within the department rather than constant attrition to other areas within NI. I know a few people in that group who started there out of college and are still there 5+ years later which definitely would not have happened previously.
  11. You can always try calling in on a new case or transfer to a different technical support engineer (I know if used to give you this option if someone wasn't picking up). You don't have to ask them the same question but they should be able to tell you what's going on at least (someone's OOO, case is in some bad state, or more often than not both people think they're waiting for information from the other).
  12. I have two 9074 cRIOs I use as bookends at work and even a couple of books I got from stuff people were trying to get rid of. Most of the hardware I would be able to take home is old enough that I don't really want it (I'm not into home automation or maker stuff so I really don't care about old tech).
  13. Even though we know we will never go to the True case, I doubt LabVIEW would ever be able to determine that and properly remove dead code. It would require LabVIEW to know that the timestamp output of a primitive converted to a double will never be less than 0. If you wire a false constant into the case selector the VI won't lock up so it does work in that instance. I remember running into issues with events being queued when the VI is only reserved to run by (accidently) embedding VIs that weren't running into subpanels. The VI isn't running but clicking anything can still enqueue events and cause everything to lock up.
  14. You're doing better than jeffk, he's still a newbie. I guess LAVA just has high expectations.
×
×
  • Create New...

Important Information

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