Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by bbean

  1. Sorry don't have too much time to help here, but try example code here for some guidance maybe: C:\Program Files (x86)\National Instruments\LabVIEW 2014\examples\Graphics and Sound\3D Picture Control\Using Meshes.vi
  2. Some self promotion here, but have you tried or seen this:
  3. Make sure all your power options are set so that the computer doesn't turn off when not being used (no hibernate, no sleep, no usb suspend, etc)
  4. Maybe this can help a little until 2016...Re-label Event Wire Xnode
  5. I put together a simple xnode to relabel event registration reference wires that feed into dynamic events of event structures. With the increasing use of event based messaging systems, I found myself manually changing the name of event registration references to clarify the event name when multiple event registration references were used in an object. I did this by manually creating a cluster constant on the build cluster before the dynamic registration terminal on the event structure and renaming each registration reference. Being a lazy programmer, this seemed tedious after a few times so
  6. Thanks for the heads up. I guess I'll have to sign up for the beta testing to get a peak.
  7. Thanks, I'll probably try the Copy ability. For future reference, can you upload an example Post-Install VI with the actions you described? Also is there a list anywhere that describes the syntax for "Reply" commands/states in the Xnodes? For instance, is there a way to force the AdaptToInputs ability.. (UpdateInputs maybe?)
  8. I created an Xnode that pops up a dialog when the user drops it on the block diagram for configuration. However, when I put the Xnode inside a Merge VI (so I can add it to a function palette menu), the On Drop Ability doesn't fire when the merge VI is used. I guess this is because its not really dropped but merged. Is there another ability that will handle this situation in a Merge VI? Couldn't find an OnMerge ability so I tried using "On Owner Change" ability, but it fires anytime you put code around the xnode (like a case structure, etc) or copy it to another diagram which could mak
  9. Thats where I was headed, but wasn't sure what the downsides to using the control reference were (other than speed I presume).
  10. In the attached example, I'm having trouble figuring out why the references Traverse G - objects.vi returns for typedefs do not have the control name embedded in variant data when they are registered for Value Changed Events (enabled diagram). It seems to work fine for controls that are not typdefs. If I explicitly find the controls using VI panel properties (disabled diagram), everything works fine but I have situations where the traverse Gobjects would be preferred since it can go through nested tabs / controls etc. Am I missing something simple. Typedef Value Change.vi
  11. Code looks the same as before. Where is new technology?
  12. Hi Porter, Very nice library you put together. One quick question. Is there any reason the RX/TX data and timestamps are not available as a Read Property from parent Modbus Master Class. In situations where a device could be either a serial or tcp modbus, it would be nice to have access to that information at the parent level since it appears (unless I'm missing something) that the data is common to both the TCP and Serial Class. Brian
  13. Can anyone give a link to Amazon or CDW to purchase the Microsoft Windows 7 license they run on their Virtual Machines (for a single developer/machine)? You will be my hero and I will owe you multiple rounds of beers. Or do people develop on Win7 VM's in the cloud on Rackspace or AWS? Or a tutorial about how to accomplish developer VMs / snapshots with a Windows 7 license? Added bonus LabVIEW version snapshotting/licensing. I gave up on Windows VMs after getting stuck in an infinite loop entering the Microsoft Licensing Vortex .
  14. I like the idea of having separate project based configurations stored on the local machine and being able to switch quickly between them. Would there be a way to "trick" VIPM/LabVIEW to point to "project specific" user.lib / vi.lib directories using symbolic links?
  15. Your code looks Ok. Have you tried using a serial sniffer (such as device monitoring studio) while the OEM software is running? This will give you a clearer idea of how it communicates if you are able to make the OEM software work. It looks like you have a bunch of duplicate COM ports left open, probably a result of not stopping the program gracefully. You can modify or use the attached VI to close these duplicate ports. (There may be a better version out there to do this but I can't find it right now) But I don't think thats the root cause of your problem. Also, try starting at
  16. The best way to debug would be if the mfg'r provided a test software and you get that working first (without labview open) that will verify your hardware layer. Then move to LabVIEW and software layer. 99% sure its not the "functions" you are using. If you don't have access to the mfg's software, start at the hardware level and read the OEM manual (i couldn't find it on line): Is the interface RS-232, RS-485, or RS-422? Does your USB to Serial converter support the hardware layer above? If its RS-232 to you have the TX and RX lines swapped incorrectly? Are you sure the COM port is
  17. 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
  18. 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.
  19. 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
  20. Been waiting for an excuse to install 2015
  21. 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.
  22. 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.?
  • Create New...

Important Information

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