Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About mabolas

  • Rank

Profile Information

  • Gender
    Not Telling
  • Interests

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since

Recent Profile Visitors

781 profile views
  1. I think this kind of architect is OK to NI. I got 95.7 points at my CLA exam . Architeture development could still do a little bit better. And I didn't tag the requirement tags perfectly. Anyway, this result is good enough to me. I'll tag my last practice examples as the solution.
  2. Thanks the advice, I posted there and seems not enough time to get feedback. (I'll take exam next week, so, this style would be my final framework and architecture, the rest I can do just more practices and pray......)
  3. I made anther practice, this time I try typing more words and less coding work. ATM.zip Elevator.zip
  4. I've made ATM practice too. I think it's little easier than Elevator. I don't know why, maybe I've practiced at CLD. ATM.zip
  5. Hello, Recently I'm trying to get my CLA and this is my third time practicing this example. I took about 3 hour and 20 minutes to finish it. (Actually I planned spent 3 hour to finish it , it's already the third time, I barely analyzed it , just coding) The first hour I took was for establishing ancestor classes, set up public data, sharing mechanism / VI (open/close queue references, access data base, main running VI framework.....etc) The second hour I spent on modules (error handler, user console, display console and sensor ) The third hour is implementation of the main module : Contro
  6. Sometimes I do manipulate data members via data access VIs, but only in static dispatch VI. And I didn't mean erase this specific method from LVOOP, I just hope LVOOP could provide another way more easily to set up public data members. It also makes LVOOP has similar property as other OO language. I think it will help LV programmers to communicate other OO language programmers.
  7. the public data here I means the traditional OOP language declaration, could easily access outside Like, class Symbol { public: char ID; int Width; int Height; private: int pd; }; the public data here means "ID,Width and Height"
  8. Recently I use more and more LVOOP to build my project, the access data through property node helps me a lot. I don't need back to project explore to find out where the data member access VI is. (Sometimes it takes me lots of time if it's a big project , and most of time just annoying.....) And I can easily access the parent data too. One day suddenly I feel this action treat those data members really similar as the public data. To be honest, I don't know any details in computer science opinion how NI made this and what's the difference inside between public data and data access throu
  9. Sorry, reply it so late. No, I didn't use any Call Library Node in this project, it's just a small project for some simple purposes. And, although my Labview installed correctly, your description remind me that once I indeed messed up Labview itself, it was a bug that caused infinite loop popping out the dialog. I couldn't press abort bottom, so I had to enforce shutting down labview. Seems after this corruption, the LVOOP started crashing Labview. Would it cause LVOOP unstable too? Should I recompile all of the programs which LVOOP involved in? Or just methods/properties of
  10. One previous article, almost the same situation as mine. http://forums.ni.com/t5/LabVIEW/Access-violation-0xC0000005-at-EIP-0x013C7314/td-p/2258546 http://www.ni.com/white-paper/13164/en/#213279_by_Category the Issue # 213279, still unsolved. I'm not sure whether anything related with my problem. Someone helped me test my program with LV2013, and the crash still happened. I guess somehow the dynamic property nodes being stuck at the previous address of the pointer, so it loaded the wrong value, or crashed since the address of pointer is no more in computer, or occupied by other pr
  11. Thanks the information. : ) Now I'm using LV2011. This situation sometimes not just ouput the wrong data, getting worse, it crashed Labview. The erroe remained , crahed LV again and again.......even I reboot the computer...... I google the error code(Access Violation, 0xC000005), seems not only me but happened everywhere.(Maybe not the same, but very similar.) I'll read more articles to see more discussions about it.
  12. I'm new at LVOOP and recently I met a problem confused me , the image shows a simple example about it, and I have no idea how it happen. Did anyone meet this before? Are there some settings wrong or just a bug of LV? Thanks.
  • Create New...

Important Information

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