Get your questions answered by LabVIEW developers.

[JRA]

Hey guys,

Chris, who some of you met at NIWeek, has fixed it for us. You should be able to get it now. Thanks, Chris!

[aartjan]

I couldn't get to the info page using the keyword mentioned..

[MichaelAivaliotis]

---

@chanlo23 wrote:As to the block diagrams, I should restate that.  You know how LV is graphically oriented for its design if you are not using custom cin's or dll's -- basically all I am asking for is what is in the exact steps performed for the three LV7 array editing functions of replace, add, delete row.  The documentation does not tell us what steps, in what order, are being performed in these functions and that is what is needed.  I don't need or want the proprietary code, just a complete description of what/how that particular function 'block' is working.  This is why part2 of my request for future development is complete documentation that fully describes the processes that are required.

---

What seems to be the problem here? You have certain basic array manipulation tools in LabVIEW 5.0. I realize these are limiting but you can do it all. You have the array subset functions, no? To delete a row just index out the subset before the row and the subset after the row. Then re-build the array from the 2 subsets. The same can be done with the add and replace. I've developed in 5.0 and I understand your limitations but there are always workarounds. I don't have LV50 installed so I can't give you a graphic of the solution. If you need more help, let me know.

[MichaelAivaliotis]

---

@tst wrote:
You can find more details in the scripting board of the LAVA forums. I think you have to be a member to read it.

---

Yes, you have to be a member, just like on the NI discussion forums... As always LAVA Forums membership is free.

[Naghi]

Hi Expert Developers
    The last few days i created an application that reads data from one of serial ports (contactless card reader). Today i noticed that my application had crashed and Windows had displayed a message that my system was low on virtual memory. I reset the system and i re-run the application, having the task manager opened. I noticed that the memory usage of my exe was taking more and more memory (starting from 21.520KB) as the seconds went by. In 5 minutes my app was using 25Mbytes! What i do in my application exactly, is opening the serial port  then i enter the main while-loop, then every 2 seconds i read from the  serial and write them to a tag.
I have used standard visa serial functions of Labview. When I trace my application and simultaneously run TASKManager of windows to see the memory, I saw that after running every Visa function memory usage goes up!!!
what must I do? Please help me to overcome this problem.
Thanks,
Mostafa

[tst]

Did you read what this thread was about? Your post has nothing to do with it.

Why not wait for an answer in your other thread?

[tst]

JR, I listened to the podcast, and I would like to thank you for that.

Now, can we expect some more of this? This taste was woefully small compared to the wealth of questions we have.

I also have another 2 questions:

1. Why do 2D arrays have automatic padding but 3D arrays don't? I'm having some troubles picturing exactly how this should work when using auto indexing or similar things, but at a glance this seems to be a glaring inconsistency.
2. In the podcast you said that NI writes its VIs based on the LV style guide. If you look at the VI.Lib VIs, this seems to be very much not so. The VI.lib internal VIs often have no icons, no descriptions, no documentation and overlapping\hard to read code. Is this because all the documentation is kept outside of LV?

---

 Michael Aivaliotis wrote:

---

@tst wrote:
You can find more details in the scripting board of the LAVA forums. I think you have to be a member to read it.

---

Yes, you have to be a member, just like on the NI discussion forums... As always LAVA Forums membership is free.

---

I was refering only to the scripting board, which, as far as I remember, requires the membership (unlike the other boards).

[MichaelAivaliotis]

---

@tst wrote:

1. In the podcast you said that NI writes its VIs based on the LV style guide. If you look at the VI.Lib VIs, this seems to be very much not so. The VI.lib internal VIs often have no icons, no descriptions, no documentation and overlapping\hard to read code. Is this because all the documentation is kept outside of LV?
   

---

I'm just curious, how many of the G developers at NI have CLD or CLA designation. It would seem that this would be a minimum requirement. Don't you think?

Let's start placing bets that none of them are certified.

Message Edited by Michael Aivaliotis on 08-22-2005 01:33 PM

[Bob_Y.]

When I was working there, there were NO CLDs or CLAs in the LabVIEW group.  The managers thought that it would be a bit of a waste of time as many of the LabVIEW group had written questions for the test.  Now that the testing scheme has changed, I think it is something that they should re-think (if they have not already).

And remember, most of the people developing LabVIEW don't usually use LabVIEW; they use C++.  So getting them to take and pass the test might be a good idea just to make sure that they had some experience using their end-product.

Hope that this helps,

Bob Young

[MichaelAivaliotis]

---

@tst wrote:

---

 Michael Aivaliotis wrote:

---

@ tst wrote:
You can find more details in the scripting board of the LAVA forums. I think you have to be a member to read it.

---

Yes, you have to be a member, just like on the NI discussion forums... As always LAVA Forums membership is free.

---

I was refering only to the scripting board, which, as far as I remember, requires the membership (unlike the other boards).

---

And I state again, membership is free and open to all. So it's really a moot point.