Jump to content

Neil Pate

Members
  • Posts

    1,156
  • Joined

  • Last visited

  • Days Won

    102

Posts posted by Neil Pate

  1. I think ShaunR is in to something here. On LV2015 Quite often LabVIEW will get itself into a mode where in order to box select something I have to go completely around it rather than just partially around iy. No idea what causes this to change, but it pops up on my dev PC every few weeks. No driver change has happened inbetween and then it usually just fixes itself.

    @Darrenhave you got any of the "speedup" keys in your LabVIEW.ini set?

  2. As a consultant I have to work with whatever code my customer has developed. Some of it does indeed take several monitors to scroll across and I just have to deal with this. The IDE should not choke or do "stuff" constantly while I am editing. Also, as is pretty common during development my code spends a lot of time broken as I develop or refactor stuff, and I have to deal with missing VIs all the time as I integrate other team members code back into the main branch.

    As LogMAN pointed out, the behaviour of the selection rectangle is so much quicker in 2015 (at the expense of the "amazing must have could not live without" feature of shading the contents of the rectangle). I bet ShaunR is having a quiet chuckle about this whole thing as he gets to use 2012 or something like that.

    Sorry if I am coming across angry, but I am. LabVIEW is not exactly a new immature product that is given away for free. We really should not put up with this rubbish. If I have to wait for my IDE to draw a shaded rectangle, regardless of the quality of code underneat, something is deeply wrong.

    • Like 1
  3. Definitely not a notebook. It is a two week old PC, the fastest thing I have ever used. 32 GB of DDR4 RAM, Xeon CPU, extremely fast SSD and a good GPU.

    LabVIEW struggles to draw the grey selection box around stuff; it is actually a bit embarrasing.  If I open a new VI and draw the selection box around a single structure it is "ok" but still quite sluggish. Trying to edit anything sensible leaves me with a slide-show for any editing operations that cause stuff to be redrawn. I have now turned off all options like auto wiring etc and its a bit better, but it is 2019 now. Editing operations in an IDE should not feel slow.

  4. Don't think you can do that, I think a queue ref cannot be dynamic dispatch, even if it contains a class.

    I am not sure I really follow what you are trying to do, but could you flip the logic around a bit, and have the queue ref as like the second input terminal, and have a StartRun input as the dynamic dispatch input? So you Enqueu Serial Number class which you have shown would have the StartRun object as the primary DD input?

     

  5. Still not getting you, sorry. You want to wire a queue of classes into a class terminal? Can you post your demo project? Just because the classes might have a hierachy surely that does not imply anything about a queue that may contain these?

    You cannot set dynamic dispatch on a queue ref, can you???? (it is not a class itself)

  6. I cannot seem to get this to work on 2017 SP1 (64-bit).

    Tried various combinations of these:

    DragAutoWire=False
    LiveDrag=False

    But nothing seems to help the editing experience which lags so badly when doing "complicated" operations like a a box selection 😞

    This is on a brand new dev PC with 32 GB of RAM, very fast SSD and processor.

  7. Sorry if I have mislead you, looking back at my post I have to make a correction to my vocabulary. The whole system probably had about 10 nodes in total and the LabVIEW based controller had to implement several OPC-UA clients and servers (I think two each). In total the system had about 500 tags (not nodes, sorry!).

    I tested things at a maximum rate of about 1 "update"/s where an "update" was changing all the tags of a particular subsystem. Performance was never an issue at all of this portion of the application, I cannot say I ever saw the CPU particularly taxed. What did cause performance issues was trying to update my tree control view and name based logging. What I gained in elegance in the code I sacrificed in performance. Also, if I never have to write another recursive tree updating routine based on hierarchical tag names I will be quite happy.

    I am not at liberty to share anything as I did it as consultancy for another company, sorry.

    In the end OPC-UA worked fine, and I would certainly consider it again. I will never use NSVs in a project; I just have too much distrust of them. In fairness though it has been nearly 7 years since I was scarred by them...

  8. 31 minutes ago, Aristos Queue said:

    Definitely a bug. If you can share the code, it's worth escalating to an AE at NI to see if it is still broken.

    Unfortunately I cannot share the whole project but I will see if I can trim out the broken bit and escalate.

    At the moment that particular VI is reliably broken, if I take out the "Always Copy" it still shows the weird behaviour, so at least it is consistent.

  9. For one of my projects that used OPC-UA I had probably 500 different nodes in the system. I did not really want to handle the data read using a case structure with 500 cases, so I went 100% down the route of name based lookup data structure implemented using Variant Attributes. I managed to extend this to a tree based system data viewer and configurable data logger, without ever actually using explicit node names (well, not perfectly but close enough).

    For the most part I did not have to fight with OPC-UA, it just worked.

  10. 15 hours ago, hooovahh said:

    Throw in an always copy liberally and I'm guessing things will work start working.  If you can isolate it well enough send it to NI for them to investigate.  What version of LabVIEW and patch level?

    This is LV2015 SP1 (not too sure the patch). I suspect the moment I start to chop things out to isolate the problem will just go away.

    4 hours ago, smithd said:

    Definitely not crazy, I've seen this a few times before.

    I'm curious though what happens if you put the indicator on the connpane?

    Will try this when I get a moment. 

  11. I have used the NI OPC-UA toolkit in a bunch of projects. Both as a client and server.

    Had an issue with an earlier version of the toolkit (2015) where it was not working correctly with authentication, but NI released a patch for that.

    The only other strange thing is that the client (or server, cannot remember which it is) does not support Data Change events, so you have to poll. Oh yes the other weird thing is that when you do get a Data Change event you get the data coming in as a variant, but unlike regular variants this one seems to know nothing about its own type. This actually caused a bit of drama for me but managed to find a work-around as the data change event does actually include the type, so I was able to shove it back into the variant.

×
×
  • Create New...

Important Information

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