Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Manudelavega

  1. We have a position opened for a LabVIEW developer in the Vancouver area, British Columbia, Canada. Please find out more here: https://greenlightinnovation.betterteam.com/labview-software-developer-2
  2. I haven't. Thanks for the posting it, will definitely check it out!
  3. Thanks ensegre and Mads. I think the CAR related to what you two talked about is CAR 202900. Unfortunately I don't think this applies to my problem.
  4. Thanks Bob and Bryan, I'll try to dig into this.
  5. I've been asked to escalate the issue related to CAR 185890 where text that should normally be interpreted as ASCII suddenly starts being interpreted as Unicode, which means the text is replaced by random Chinese characters. It seems like this CAR has been opened for 10 years now. I found some NI forums related to this, but nothing on LAVA. So I'd love to know if you also still experience this really pervert bug. It's hard to reproduce, it usually occurs after weeks of running our application (executable). Note that in my case, I do have some text (mostly control captions) that is Unicode on purpose so we can localize it, and this works fine. But the rest (table and listbox content in particular) is always displayed as ASCII and works fine most of the time, expect when LabVIEW decides to suddenly interpret EVERYTHING on the front panel as Unicode. Most of what I could find about this is from 2010-2013, so it would be nice to see what people experience about this in 2021
  6. Hi everyone, my apologies if there is already a topic about this, I couldn't find one. My company is looking into acquiring an automation testing tool to troubleshoot and validate our LabVIEW-built application (and maybe one day perform some CI but we're not there yet). I did some research and found a lot (Ranorex, TestArchitect, TestComplete, TestProject, Katalon, Telerik...) but as I read, I think none of them will work with LabVIEW. I need the tool to be able to click buttons in our application, fill text fields, and analyze what it sees on our application windows. Do you know if any of those tools would be able to do that? The only one that seems to be based on picture recogniction is Sikuli, apparently now renamed Sikulix. Could anyone confirm? And is there any way other than picture recognition to interface that 3rd party tool with our Labview application? (I guess we could add a bunch of LabVIEW code to have some TCP/IP communication, but the goal is not to have to modify our application...) Thanks a lot for any advice!
  7. My advice is to completely rewrite this VI with a proper state machine. I'd recommend the JKI state machine. Have a single while loop containing a case structure, where each case of the structure is a state. You should at least have an Init state, an Idle state, and an Exit state. In the Idle state you want to have your event structure so you can detect that the Pause or Stop buttons were pressed. If no button were pressed then the Timeout event will occur, and this is where you want to handle your pump and do your math... Good luck
  8. Hi, I've known for a while that Tree and MC Listbox controls can embed the custom symbols that I set through the Set To Custom Symbol Array method inside the VIs that contains them. After compiling, the executable can skip that method and still remember the custom symbols. So I guess my exe has to be bigger because it contains the png files I use for every single Tree and MC Listbox control. However, I just "noticed" that and don't fully understand it. I know I need to save the VI after running that method in the sources, but then I don't know how to tell the control to forget the symbols I gave it. And I cannot find any documentation about this. Anybody here knowledgeable about this topic? Thank you
  9. Good point, but I see 2 issues: - this would prevent the ability to open the file in notepad and change a key manually - if the application process is killed in the windows task manager, all changes will be lost since we never execute the INI Close, which is the only case to actually write to the file
  10. Thanks for the idea, but since I never leave the file open, I will make it as easy as possible and simply create a FGV2 with only 2 cases: Read Key and Write Key. Read Key will do Open/Read/Close Write Key will do Open/Write/Close That should do the trick.
  11. Thanks, you confirm my suspicion about the need for a locking mechanism like a semaphore or a LV 2 global. I thought I could get by without one, I was wrong
  12. Thanks rolfk, my real code has error handling but my example doesn't generate any error so I omitted the error handling on purpose for higher readability. Taking a step back: all I want to do is to rely on a configuration file to store parameters. I have been counting on the possibility to have several pieces of code asynchronously either writing or reading one parameter (not the same one). Was I wrong to count on this possibility? How do you manipulate your INI files? Do you wrap the INI Vis inside your own API?
  13. Thank you everyone. I should have insisted more on the fact that my issue is really with INI file. The only reason why I am tinkering with text file VIs is that they are the blocs used by the INI library. This new screenshot and attached VI shows that relationship. The 2 While loops are equivalent. The Text VIs of the top loop are the ones I found in the INI VIs of the bottom loop. As you can see, both loops encounter the same random rate of failure. In the case of the INI, the text VI returns an empty string, and therefore the INI VI tells us the key is not found. So my problem is not fixed yet. It seems I need a locking mechanism to prevent the reading and the writing of the INI file to happen at the same time. Read-Write TXT issue.vi
  14. So after troubleshooting a complex piece of code for a few hours, I stripped things down to the screenshot below. Apparently writing and reading a text file at the same time causes the read operation to fail. If you force sequential operations by wiring the error cluster from the Read to the Write OR VICE-VERSA, then things work fine. Does anybody know about this? Obviously my code is way more complicated and the read and write operations are done in different unrelated VIs and in an asynchronous manner. So it seems my only way to fix this is to add a locking mechanism such as a FGV2... However, the file I'm manipulating is actually an INI file and I manipulate it using the native Configuration Data palette, which deep down relies on the R/W Text file VIs. So the FGV2 would need to be added to the native Configuration Data VIs if I wanted to have a generic fix... The attached VI is saved for LabVIEW 2015. Read-Write TXT issue.vi
  15. As topics about LabVIEW NXG are going to start growing more and more numerous, it would be nice to have a proper folder to put them. Could an admin create a dedicated folder or category where it would make the most sense (at their discretion)?
  16. I took the time to search for existing posts about this but surprisingly I didn't find anything. Here is what I want to achieve: I have a tiny LabVIEW executable that can perform basic operations on a single file. So far I need to open the executable, and then browse for the file. I would like to have a way to navigate in Windows Explorer while that executable is not running, and when I find a file I want to open in my executable I can right-click the file, and in the Windows context menu I can see my exe in the "Open with" menu. Even better, I would like to associate the special file extension to my executable so that I can simply double-click on it in Windows Explorer. There are probably several steps required to achieve this. Could you guide me through either one or all of them? Or point me to a useful resource? Thanks!
  17. You should probably save your VI for an older version of LabVIEW. Not everybody has LabVIEW 2016.
  18. In a slightly more advanced way, you can use a property node to get the array of pages (references). The number of elements in that array is the number of pages, so you can use this number instead of the constant for the comparison LogMAN is using to stop the loop.
  19. I had memory leaks that I investigated and fixed in the past but never of that kind! Usually the symptom is a slow but constant increase of the memory, in the order of 1MB every few minutes which adds up to 100MB in a few hours and 1GB after a few days. When I look at the memory usage in a graph, I see a constant gentle slope and I know I have a leak. Usually a while loop which keeps opening a reference and never releases it. But this time I had 5 hours of no leak at all where my application stayed nicely at 356MB, and suddenly it jumped to 1.5G in a 2s interval! Then it increased by 69MB/s for about 20s before stabilizing at 3GB. Then it regularly jumped back to 2GB for 1s and then back to 3GB for 30s, 2GB for 1s, 3GB for 30s, and so on... How could that be possible? Can I really have a piece of code that could manage to allocate 69MB/s? Any comments welcome!
  20. Probably a good idea to delete this post now.
  21. I'd suggest modifying the mechanical action of the Keep button to "Latch when released" (or "Latch when pressed", doesn't matter). This will reset the button to FALSE as soon as LabVIEW detects that it was set to TRUE by the user. So this will execute the code that populates the 2D array only once each time the user presses the Keep button. Additional comment: don't you want to restart populating the 1D array from scratch each time the Acquire button switches from FALSE to TRUE? Right now you keep appending and never discard the old elements.
  22. Have you checked the error description? It is defined as follows: The application is not able to keep up with the hardware acquisition. Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem. The issue might come from the fact that you're in continuous sample mode, so the hardware is going to keep filling a buffer and your Read function is supposed to partially flush it each time, but you only flush 1 sample when the case structure is TRUE, and you don't flush it at all when the case structure is FALSE. So the buffer fills faster than you flush it and eventually gets full and generates the error. I'm not 100% sure of my description but it makes sense to me. Also the way you generate your array of X for your graph is weird. You reset your timestamp shift register each time the structure is false. So when it becomes true again you don't compute the elapsed time since you started the VI, instead you get the elapsed time since the last time the structure was FALSE. Is that by design?
  23. Dear all, My company is hiring a new developer to join our software team. Please see link below for details and to apply. http://www.greenlightinnovation.com/company/careers/articles/253.php
  • Create New...

Important Information

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