Jump to content

Mike Le

  • Content Count

  • Joined

  • Last visited

  • Days Won


Mike Le last won the day on July 6 2018

Mike Le had the most liked content!

Community Reputation


About Mike Le

  • Rank
    Very Active

Profile Information

  • Gender
  • Location

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since

Recent Profile Visitors

1,214 profile views
  1. I have extensive experience in the medical device industry with a focus on systems testing/automation. I am highly skilled in LVOOP and Actor Framework. Please see my LinkedIn for details and references. https://linkd.in/mikele I can be reached at mike.q.le@gmail.com for inquiries.
  2. I swore off XControls because they don't play nicely with classes. I untangled one too many corruption issues from using an XControl with a class...
  3. I'm trying to create functionality similar to browser tabs. The main containing VI is a split pane with a tab control in the top pane and a subpanel in the bottom pane. If the user hits a "close" button for a given tab, I want to stop that VI's execution and (if it's currently being displayed) unload it from the subpanel. I wanted the framework to be as flexible as possible, so even programmers unfamiliar with Actor Framework could use it to launch any VI into a tab simply by feeding in a path name or reference. Basically I need a way for the VI to detect if it's "done." When it's been torn out of the Tab Container into a separate dialog, everything's fine. But when it's "x'd out" as a subpanel, then I don't know what option I have other than explicitly defining a reference for it (such as by launching it as an Actor and restricting the framework to only loading Actors).
  4. Hi all, So I'm trying to create a general use UI framework. One of the things this framework can do is load VIs by file path into subpanels or dialogs, then switch the behavior of the launched VIs between subpanel and dialog. If the VI is currently running as a dialog and is closed, then cleanup is easy: I use the "Panel Close" event. But for the subpanel case, I don't know if there's a handy event ready like that. Any suggestions? I want the framework to be as generic as possible. If I can't come up with a good solution I might just require that all subpanel VIs being run like this must be an Actor and simply use a Send Stop Msg. Thanks.
  5. I've used this solution before; how many elements are you looking at and what do you mean by "inconvenient"? I've been able to do it with an array of ~50 elements with no problems. I find the cluster elements automatically by searching through the main cluster's sub-references. If you're talking hundreds or thousands of references then it would be slow to start up, but if it's in the dozens, I don't notice a performance hit.
  6. So I just started trying to submit some activities for the "CLA-R by points" program. Does anyone know what's going on behind the scenes, or why there have been so many delays? Is NI still planning on supporting it? Based on the comments I'm reading on the recertify board and a few conversations with other CLAs, it seems like things have been slow for a good long while. I guess there was a brief period last year when they were responsive, but then the replies have slowed down to a crawl again?
  7. I ran into this same issue recently. It happened right after I added a DVR containing a typedef to the private data of one of my classes. Do you know if you did anything like that beforehand? What do you think fixed your code before and after the rewrite?
  8. Look just in the enabled case. I actually did try making a simplified version but I couldn't get the error to occur there. So there's something slightly more subtle going on with the actual implementation.
  9. I'm not sure if this is still permitted, but when I took the exam I was allowed to bring a copy of my LabVIEW INI file. Definitely recommend asking your proctor if this would be all right.
  10. Named WF Array Project.zip I created a project that demonstrates what I'm trying to do and the error. I'd really appreciate it if someone familiar with the Advanced TDMS palette could take a look. This was coded in 2013SP1. If you need it back-converted, let me know. Sorry about the file hierarchy, the project is located here: Workspaces\V12000\_V12000 Common Labview Code\Named WF Array\Named WF Array.lvproj
  11. No, I'm trying to write each channel separately as a 1D array, using the "Set Next Write Position" function to select channels. I'm using 2013SP1. Yes, asynchronous is set to True and I'm using the Advanced palette for all subsequent read/writes. For now I've given up on trying to use multiple references and am just trying to get a single reference to work. Even here I'm running into problems. I'm using the Advanced TDMS palette to create an on-disk circular buffer. I was able to successfully implement the buffer for a single channel of data. However, when I try to write multiple channels of data, I continuously get "End of File Encountered" error 4. I am pre-allocating 60,000 data points for each channel using the "TDMS Set Channel Information" function. I am able to (1) Set Next Write Position and (2) perform an Asynchronous Write to the first channel. But when I try to Set Next Write Position to the second channel, I immediately get an error 4. The examples have not been helpful as none of them write to different channels in sequence.
  12. I was converting to Extended Precision and then back to Double, but "Always Copy" is probably the better fix. Thanks!
  13. I've attached a VI that illustrates some weird behavior with an Advanced TDMS Write node. I have a work-around but figured it was bizarre enough to share with the group. Basically, trying to input a 1D double array from a "Split 1D Array" node causes a broken arrow in some situations. Advanced TDMS Write Polymorphic with Broken Wire Behavior.vi
  14. Hi guys, So I have an application that uses TDMS for data-logging. There's a continuous memory leak as I write new data. It's alleviated somewhat by setting disk cache high for each channel, but as I'm acquiring data continuously over long periods of time, this isn't a great long-term solution. I've tried switching over to the Advanced TDMS palette, but I'm having a lot of trouble getting an implementation going. A single TDMS file is accessed concurrently by multiple processes. Ideally, I want each process to open its own reference to the file. This wasn't a problem with the standard TDMS palette, but I'm getting errors with the Advanced palette. For example, error -2539 states: "LabVIEW: This file cannot be written to, because it is opened and locked by another thread or process. This typically happens when a file is written by a hardware driver, for example NI-DAQmx." Is concurrent access not allowed in the "Advanced" palette? Or do I need to do additional work in the Open step to allow concurrent access?
  15. I find myself in this situation a lot, where I have an Actor that inserts itself into a subpanel. I want to look at what's going on in the Actor Core block diagram. Typically I'd stick a breakpoint there so that the particular Actor clone's BD will pop up. But in that case, the front panel also opens, which very often leads to buggy behavior or errors when the Actor later tries to stick itself into a subpanel. Anyone have some workaround suggestions for this? I run into the problem a lot and always slug through somehow but I figure someone's got a better procedure.
  • Create New...

Important Information

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