Jump to content

bbean

Members
  • Posts

    252
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by bbean

  1. Is it OK to put an Actor's "Internal Data" into its class control? or does it need to be empty? I ran out of space on the actor diagram and had to make SubVIs to parse some messages and handle some follow on actions. The internal data is a relatively big cluster and takes up a lot of space on the front panel of the SubVIs and could be cleaned up if it was a class wire. Do you try to keep everything on the top level block diagram as good practice? I think I remember one of JKI's style guidelines for their "state machine" recommending to keep the state string constants at the top level for clarity. Also opening another can of worms...do you often have parent-child inheritance situations where an actor inherits from another? For instance, for an "instrument" do you have an abstract parent and implementation in a child actor or do you make the messages abstract (message names shared between the same instrument type) such as "measure" and "set range" and the actors of the same instrument type do not inherit?
  2. I can't really narrow down what causes it. But it seems like if you copy the read var xnode from the existing diagram and wire the same cluster type to it, its fine. But if you select a new instance of the xnode from the addons pallette and place it on the diagram and wire to the same constant, then save it crashes. I don't know if that helps narrow it down to an ability or not. Also it doesn't seem to happen with the string data type. So far I have just seen it on clusters. It may be a labview bug and be unrelated to the xnode. I have no idea.
  3. I've been having problems with intermittent crashes and LabVIEW hangs recently using the Variant Repository xnodes in LV2015SP1. More specifically Read Variant Repository.xnode. Has anyone else had problems in LV2015SP1? http://www.screencast.com/t/tj15qFGRc
  4. Been waiting for an excuse to install 2015
  5. In the spirit of dreaming, I think what would also add to this idea would be a new LabVIEW primitive called TypeDetectDisableCase Structure that would work like a case selector for datatypes, but would automagically (like an Xnode) disable the irrelevant case and enable the relevant type case for the inputs. I think having all the code in one VI (even for different types) is key so you don't end up with a Xnode solution that circles back to the polymorphic situation where you have a bunch of template subVIs to manage.
  6. Interesting. Good find. If you look at the front panel enumerator for Terminal Behavior there is another option "Depends" and also a "dependency chain array" control and "index of dependency" control below it. Any speculation as to what that option would be for.?
  7. Are you suggesting one could copy/modify that Xnode to extend its capabilities to their liking?
  8. After reading this LabVIEW Idea exchange request: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Provide-a-better-way-to-implement-a-polymorphic-VI/idi-p/920487 I was inspired to create VI macro(s) to attempt to address the problem mentioned in the request. Attached is my first attempt and I'm looking for feedback since I know people here have strong opinions. The benefit of this method is that a single vim (or 2 could replace a polymorphic VI with over 48 separate VIs....unless I'm missing something. I know that VI macros are not officially supported by NI, but that hasn't stopped us from using unsupported features before. Some people have probably already done something like this, but I couldn't find an example. To use the files, unzip them and copy them all to your \LabVIEW (version)\user.lib\macros\ directory. Create the directory if it does not exist. For example: C:\Program Files (x86)\National Instruments\LabVIEW 2014\user.lib\macros\ And as described in the wait-ms-with pass through post below, modify your LabVIEW.ini file to have the following ExternalNodesEnabled=True and Optionally XNodeWizardMode=True http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Wait-ms-with-error-pass-through/idc-p/3178218#M31820 Open the Example Changed.vi and review. Changed Example.zip
  9. Just a quick warning....based on the image you attached you have some parallax going on so the measurements of particle size will become more inaccurate (appear larger than actual) as you move away from the center of the image. You can see it in the ghosting of the droplets in the upper-left corner of the image. Depending on how accurate you need to be, you may have to go to a telecentric lens or move your camera farther away so that the majority of the image is in the center of the FOV.
  10. Does anyone have any experience good or bad with the PicoLog 1000 and LabVIEW? https://www.picotech.com/data-logger/picolog-1000-series/multi-channel-daq
  11. I have been having problems with Remote Front Panels not working anymore with IE as of the lastest MS security update. See here https://lavag.org/topic/19216-labview-ie-plugin-blocked-following-latest-win-7-update/ NI is still working on the issue, but based on my discussions it appears support for Remote Front Panels is bleeding a slow death. Here's how I would summarize the situation to date if you have the latest and greatest software versions and OS (Win7) updates: Internet Explorer - Does not work, reason unknown (may be an ActiveX signing (Not Verified) or registration issue), being investigated (slowly) by NI Chrome - DOES NOT WORK, npapi plugin no longer supported by Chrome and will not load in the latest version of Chrome Firefox - Does not work by default, requires changing plugin settings to work. Opera - Works currently, but plugin will not be supported in the future according to Opera Regarding your situation with Firefox, I think you should be able to get it to work. My colleague was able to get Firefox working by changing some plug in settings. I am having trouble finding a link to the steps he took. This page looks old but may work: http://digital.ni.com/public.nsf/allkb/CF91AE26198992A686257B79006959C0 Opera browser should work out of the box
  12. bbean

    VIM Demo-HAL

    Think of the scenario where you were a manufacturer who made single axis motion controllers and sold them to LabVIEW developers. You want to create a single axis "service" so the user can just plop down the VI as many times as he has axis (SP?) and you have no idea how many axis are in his system. could be 1 could be 100 I mocked up a crappy example in the project file After going through the exercise, I think you may be right even though it was unintentional . You just have to add an extra item to the event cluster contents that describes which axis sent the message. But the reason I went down the path of trying to have a variable name for the SREvent was so that there could be separate unique events / event handlers in the caller VI to handle each axis separately. But looking at the approach I took in the code attached, I think its cleaner and less work. VIX Event w Motion 2014.zip
  13. bbean

    VIM Demo-HAL

    Should be fixed in this one. Sorry about that. VIX Event 2014.zip
  14. bbean

    VIM Demo-HAL

    Ok. I updated the code as follows renamed the project to VIX Event to avoid confusion since this version doesn't use VI Macros but rather the Xnode. Added the TCPIP Telemetry Service and Client Updated the SREventXnode Help to show help and also the terminal name in the help indicates what the event created is named Modfied the SREventXnode Image so it updates with datatype Fixed some bugs in the SREventXnode code I tried to downsave to 2012 but had some problems converting and errors when I ran the code. The Xnodes needed to be manually updated and for some reason the in place element structures threw an error saying their reference was invalid in user event cases associated with the Xnode. This might have to do with UpdateState2 ability in the Xnode which I'll have to look into. Also, I think I want to add back in the variable "name" terminal to the top left of the SREventXnode as the way to name the lookup SEQ. Automatically generating the SEQ name from the data passed in limits the ability to have multiple "services" of the same type on a diagram. For instances if you had multiple motion controller axis you would want to have three of the same VI services on the diagram and pass in a name to the service and its VIX events. The other weird thing that happens when you update the name of an input to Xnode is that when its finished generating the code, a mouse click is generated on the diagram and a selection box appears. Don't know why this is happening. VIX Event Test 2014.zip
  15. bbean

    VIM Demo-HAL

    Sure, just don't have time now. It needs a few more ability VIs to make it robust and a lot more testing but I don't see why not.
  16. This is a continuation of conversation from here https://lavag.org/topic/19163-vi-macros/?p=115771 So I decided to update ShaunR's VIM Event Demo with Xnodes. Its still rough around the edges, but I think it cleans up the diagram pretty well and adds some benefits to displaying relevant Event names in the Event Structures. For now I got totally rid of the "name in" input on the event / event register Xnode so you have to name all the constants or controls that go into the Xnode or it won't work. I could put the name in back in and make it so it would override, but I don't have time right now as I'm preparing for more important things...vacation. Take a look and tell me what you think. Hopefully I didnt leave out any VIs. Many thanks to hooovahh as I used his Variant Write repository Xnode as a starting point and have learned a bunch of stuff from his Xnodes. Xnode Event 2014.zip
  17. One other comment after looking at the VIs a bit more. Why do use different conventions for identifying the recipient/sender for MSG Get (the caller VI's name or name override) and MSG Send (parsed out of the Msg input string)? This is confusing. Why not just do the Msg Send the same as Msg Get (using the caller VI name)?
  18. I have an idea regarding the "Name" issue. Would an Xnode be a better solution instead of a .vim file? I think you could use the AdaptToInputs and GetTerms3 functions to figure out the "Name" of the data input (at development time only of course) when it was wired to a variant data terminal. Then in GenerateCode wire up a static name to the SEQ input of your template VI. Not sure if its possible, but you may also be able to dynamically (in dev env again) rename the "Data" input terminal in GetTerms3 to have the same name discovered during AdaptToInputs... potentially also fixing the generic "Data" Event in all event structures to something more meaningful.
  19. Thanks for the example of VIM events and the hard work that went into that example. I noticed the VIM Event Test.vi ran a little choppy on the first run, hesitating every now and then. After stopping and restarting it seemed to be fine. Wonder what's happening here. Attached are recompiled versions for 2012 / 2014 to save others the pain of manually re-linking the .vim file. Do .vim files work more reliably if they are placed in the user.lib/macros/ ? Just a quick question....In your "subsytem" VIs (File and Sound) is there a reason for putting the srevent.vim file inside the while loop? could it be outside the while loop to prevent unnecessary calls to the subvi to just return the reference? Or is it necessary to be in the while loop for some reason? Edit - Updated 2014 zip file to have relinked Main.vi VIM MSG Example 2012.zip VIM MSG Example 2014 - Rev1.zip
  20. Coffee hasn't kicked in yet and I feel a little slow this AM. Can you explain: the use of the queue primitives and what they are for in the .vim? why register flag doesn't get passed to the "created new" True case and wrap around the Reg Events Primitive? And is the jist of the naming issue:
  21. Still waiting on this front. LabVIEW needs to move to 3d diagrams like CAD programs. https://en.wikipedia.org/wiki/Dalek http://www.thedoctorwhosite.co.uk/dalek/
  22. Asynchronous wires seem to be an extension of the wireless wires I was working on with the Wormhole xnode. The wormhole xnode would have had the wireless cleanliness of a local variable with the speed of direct wire. Oh well. Disclaimer: do not use this anywhere in your code...its just for fun WormHole.zip
  23. "Return Settings" doesn't need file terminals. If you look at the code I added to delete terminals, I use a very rudimentary approach where I check to see if the case selector tunnels are wired to anything in the case structure and delete the controls with the same name as the tunnels that are unwired. Its crude and probably not very robust at this point. I agree with you concerns about code bloat which is why I dislike polymorphic VIs. Would there be a generic way to do this with an Xnode FGV wrapper that goes through similar operations as hoovahs script, but self creates its inputs and outputs based on the case (enum) you selected from the Xnodes menu item? Would it be worth it? Or do you just transfer the complexity to the scripting environment where the potential for mistakes (and code errors) is more likely and less transparent?
  24. I added a delete feature to your latest version that will delete the controls for each case if they are not wired inside the case structure of the FGV. Its not perfect and I had to rename the initialization constant in the example FGV so it doesn't delete the input terminal (the constant had the same name). Anyway thought I'd throw it out there. Generate VIG Wrappers with Delete 2014.zip
  25. Yes No Use a DAQ Assistant (1 for each device) in a loop. Its a beginners friend (and sometimes advanced users). It automatically sets up things for you so you don't have to worry about starting and stopping every loop. If possible write to the whole port at the same time. Hint:
×
×
  • Create New...

Important Information

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