Jump to content

Neil Pate

Members
  • Posts

    1,156
  • Joined

  • Last visited

  • Days Won

    102

Posts posted by Neil Pate

  1. Not directly answering your question but I would say the biggest favour you can do yourself is not use tabs, subpanels are your friend here.,

    To answer your question, I know that in the past LabVIEW's "cleverness" sometimes caused bugs with charts where data would just not be present on the indicator if was not visible, but I would not bother about unloading panels.

  2. I am looking through some RT code, and am a bit confused by the following node. Can anybody tell me how I would make the node with the "chip" icon on it? The VI with this in in under the RT CompactRIO target folder in the project.

    I am pretty sure this has something to do with Scan mode on the FPGA or shared variables or user-defined variables, however I am not very familiar with any of these.

    Any ideas? 

    Edit: the C-Series module that this node refers to is currently tucked away under my FPGA Target, so perhaps this is old test code from when the module was used in Scan mode? If I move the modue out from the FPGA to just under the chassis the little glyph looks different, like a  little blue square wave with a triangular wave just about it.

     

    DIO0.png

  3. 21 minutes ago, hooovahh said:

    Using the Variant to data, turn it into an array of variants.  If it returns no error, then your input is either an array, or a cluster.

    Bingo! Seems to work. I think all my clusters will be properly named as they will come from my code, it is only the arrays which come from the OPC-UA toolkit that may have this problem. 

  4. 2 minutes ago, hooovahh said:

    How did you end up with an array that thinks it is a variant? 

    Courtesy of the OPC-UA API that comes with the DSC toolkit.

    I did try to check for a variant in a variant, but it seemed to keep going down the rabbit hole. I will try the variant to array of variants I do use this elsewhere.

    At the moment this is getting me out of jail, but it feels wrong on so many levels. The OPC-UA toolkit kindly tells me what the data type is, it just does not bother putting that into the variant.

    Capture3.PNG

  5. I have a variant, for some reason it does not seem to have it's type information inside, the variant thinks it contains a variant (which I don't believe it does). I cannot do anything about this, this is how it is being handed to me.

    Does anybody know how I can retrieve the original data type? (do not really need to know specifics of SGL or DBL etc, just want to know it is an array).

    In the example attached I know this particular variant is an SGL array, so the Variant-->Data works fine as I have manually put in the type. However I am expecting various different array types.

    Variant Trouble.vi

    Capture.PNG

    Capture2.PNG

  6. I would be pretty hesitant at trying to run mathscript nodes at anywhere near this rate. Not that I have tried to do it, just gut feeling tells me it would end badly.

    Marc, that thread you linked to regarding cRIO performance is very interesting, pity there was no real answer from NI other than buy the new controller :-(

    TimA I like your avatar :-)

  7. 6 hours ago, bbean said:

    Is the Variant Tree indicator available in the Dev environment?  Not sure I remember correctly, but I thought after looking into using it in a program I found the primitive only ran if it was a probe.

    Ditto to what the others have said. I have not yet tried building my application but just dropping the XControl down on the FP works almost as expected. One minor thing which I have not investigated the reason for yet is that you cannot resize the tree column widths.

    I am probably going to modify it a bit as I want to actually use it as a GUI component and I don't want it displaying the text "Attributes" and a few other things.

  8. I thought it might be (I do have it installed), but it behaves much nicer than any XControl I have come across (no usual edit time strangeness I am used to with XControls), and is that not a Probe?

    OK, done some digging, seems like it definitely this. Thanks James (and Ton and Brian)

  9. 5 hours ago, smithd said:

    Oh...no. I mean NI System Configuration API, for managing software etc. on RT targets and in theory doing other stuff with hardware but people who really use it for this totally get 100 pts extra credit. Very creative name obviously, and the shortened form is nisyscfg: http://zone.ni.com/reference/en-XX/help/373107E-01/nisyscfg/software_subpalette/

    Basically everything is synchronous and everything totally ignores its timeout. To quote the help:

    connect timeout in ms specifies the time in milliseconds that the VI waits before the operation times out. The default is 4000 ms (4 s). In some cases, this operation may take longer to complete.

    *by 'some cases' they mean 'pretty much all cases' and by 'longer' they mean 'go fetch a snack'.

     

    You mean the same System Configuration API where changing the time could cause a hard-crash of the cRIO. Yes lovely stuff that.

    • Like 1
  10. 23 minutes ago, hooovahh said:

    You can still perform a Find All Instances of a particular VI, which is probably more useful because you will only find the VI for a particular method call of a FGV, instead of finding every instance.  I believe what you are asking is if you can search for the polymorphic VI, to which I believe the answer is no, you can only search for members of the polymorphic VI, which in this case would be a particular method.

    No, I am asking for the first scenario. Good to know it can be done.

    I have never really found the necessity to create polymorphic VIs, individual wrapped API VIs was sufficient for me in the past.

  11. 33 minutes ago, hooovahh said:

    Yeah I like this idea and made a (half complete) tool for generating these polymorphic VIs from FGV, posted over here.

    If you have something going wrong with your code, and you know it is one of the particular methods of the AE then (that have wrapped been wrapped so as to not expose the enum and all controls), you can easily just search for that particular VI in your code.

    I was under the impression you could not do this with a polymorphic VI?

×
×
  • Create New...

Important Information

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