Jump to content

Jordan Kuehn

Members
  • Content Count

    587
  • Joined

  • Last visited

  • Days Won

    14

Jordan Kuehn last won the day on July 21

Jordan Kuehn had the most liked content!

Community Reputation

79

About Jordan Kuehn

  • Rank
    The 500 club

Profile Information

  • Gender
    Male
  • Location
    Chicago

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    2009

Contact Methods

Recent Profile Visitors

3,844 profile views
  1. I think AQ is enjoying this role as the end user instead of the LV programmer 🤣 I do appreciate following these edge cases though. I use this tool widely and it is fantastic.
  2. I guess yes, for the registration. However, the scheduling service and whatnot has been a separate entity and changed every time. Though apparently there's no need to check for available courses and such with only 4 hours around lunch.
  3. I mean that's been the case many (all?) times in the past with the NI Weeks that I've attended. Wow. 10am-2pm on one day? I think you are absolutely correct about what we can expect to see here.
  4. A fair question. I've used notifiers with the wait on notification, but not with the get status. It's two sides of the same coin as far as I'm concerned, and what is the underlying transport mechanism for the notifier anyway? My point however, is that while the SEQ is a special use case of a Queue there are ways to use it other than how you typically do. I'm also not entirely sold on the N:1 definition you are placing on a Queue. Sure in a typical use case 1:1 or N:1 is common, but there are use cases where you may not care about order and have multiple consumers dequeueing which could b
  5. A bold statement. I've certainly used it in this way before for synchronization, de-queueing until something is available, en-queueing when space allows, etc. However, I've also used it in what I believe drjdpowell is referring to with DVR functionality. I would even say more often than the other use case. Lossy enqueue + preview queue element is a useful mechanism for providing a latest updated value to any place with the queue reference.
  6. Yes. edit// my apologies. I’m realizing now that I was combining that excellent event with the CLA event in my mind. Perhaps it could happen again in parallel?
  7. Hmm. Well the stuff that made last year’s great was it was largely community driven with some NI involvement and almost no fluff or upward trending graphs without axis labels/scales...
  8. I miss the BBQ and being in Austin, but I really enjoyed the virtual event last year.
  9. Any word if Silverlight is being replaced in 2021? (sorry don't intend to thread hijack, but I don't know if I'll be able to participate in the Beta this year)
  10. That deployment time does seem excessive, at least for deploying the application. Running interactively is a mixed bag in my experience. I have a few cRIO AF applications of various sizes at the moment. One crashes LabVIEW when I attempt to launch it interactively, another similar one works just fine. I use the debug tools to acquire queues (in a conditional disable structure) for the main Actor Core that has a small debug UI included with it. When deploying are you able to see what libraries or code seems to take so long while watching the items scroll past? Is it code you have wri
  11. I've used the aforementioned three and currently use Git+SourceTree. I've not had the problems others have had in that other thread with Git (yet) and in general it's straightforward to commit and branch. Any merging I have to do is a manual process, but when working on a branch I typically am altering a subset of files that I wind up just choosing over the previous ones. The integration with Jira is nice since I like the kanban boards and tracking issues with commits. We don't use this to its full potential, but I think that's also a good thing since it keeps productivity in focus rather than
  12. Software Engineer - LabVIEW Full Time Professional Norman, OK, US This position will be responsible for maintenance and development of software that is core to our Freedom Series Completion System. The ideal candidate will have demonstrable software programming capability (specifically in LabVIEW), control systems experience, mechanical aptitude, ability to direct others, and an ability to operate in a fast-paced environment. This position can be located anywhere in the United States, but will require some travel to Oklahoma City at the beginnin
  13. I have spent a lot of time with the RTI DDS toolkit and it is good. I’m using MQTT for a lot of similar use cases. I believe we chatted some time ago about this a little. However, I don’t think this or the messenger library are feasible with the expansion chassis (9147 in my case) unless I were to implement the communication protocol in their FPGA. I would be happy to be wrong here though.
×
×
  • Create New...

Important Information

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