Jump to content

M_P

NI
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

3

About M_P

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2019
  • Since
    2003

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Not being dumb, but also not experiencing unexpected behavior. It is different than what you might expect from just running the code on the local Windows system. This behavior boils down to the fact that you are viewing a remote representation of what is running on the remote system, separated by a transparent communication layer that relays front panel and probe values back to the Windows machine you're viewing it on, rather than the actual front panels. You can get (2) to work if you enable the embedded UI (assuming it is a cRIO unit that supports embedded UI like the 903x, 904x o
  2. Much like a shared data plan. With associated overage charges if you're not careful.
  3. I highly recommend *reviewing* the sample projects, as there are useful design patterns to learn and emulate, but the effort involved in refactoring the sample projects to meet the exam requirements is usually higher than writing code from scratch that follows a similar design pattern but directly matches exam requirements. Bear in mind with this exam that it is primarily graded on functionality (50%) and design (30%), with style (15%) and documentation (5%) worth much less. Compare this to the CLD, where style and documentation are collectively worth 25 out of 40 points (62.5%). Your strate
  4. I'm in need of some use cases/requirements for actual LV applications that need 0MQ, AMQP, or similar middleware so I can justify spending additional time on this. I'm working on messaging/data distribution architectures in my spare time, but spare time has been increasingly difficult to come by. If any of you fine folks have requirements/use cases/application details that you can share with me, I'd appreciate it if you can send them my way. Specifically, what is the value you see in these libraries that is not met by existing LabVIEW libraries/capabilities? What kind of data d
  5. I had great fun digging into the depths of the fancy schmancy messaging protocol I was designing, until I discovered that it already existed, was called ZeroMQ, and was implemented better than mine was. That was simultaneously sad and exciting. I'd love to see a comparison between the different languages (ideally with the code to reproduce) - I'm trying to work up some recommendations for customers choosing what messaging architecture to use for a large mostly LV system.
  6. I figured somebody had to have already done this - it's too enticing of a project not to. Would you happen to have actual benchmark data or code that you'd be willing to share?
  7. I'm particularly looking into this (I'm also known as MattP on the NI forums, I work in the SE group like GoGators). From my perspective, it fills a gap that was partially filled by the AMC library (using same API for inter-loop and inter-node communication), network streams (automatic reconnect in background abstracted from the read/write, good performance), and shared variables (the pub-sub use case). What it handles better, IMHO, is that it handles not just the reconnect, but also the initial connect and intermediate send/receive queues entirely asynchronously. It also easily handles
×
×
  • Create New...

Important Information

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