Michael Aivaliotis

Hey, just realized you could detach the event data nodes from the event structure. Is this a new feature or a bug?

Ok, I feel like a fool, but all of a sudden I don't seem to be able to find the icon on my palette to browse for a VI on my file system and place it on the diagram. I was sure I saw it there before. Maybe this happened after the 801 upgrade?

Anyway, I figured out how to add it to the palette myself, but I thought this was standard... Strange.

I'll ponder over the ideas raised in this thread...

One thing I also want to add. Please everyone (Students and Otherwise), Add a decent title and description to your posts. Would you open an email that had the title: "help needed...please" probably not. Obviously you need help, be more specific. Skimming the title helps everyone weed out the noise. Also, the act of writing a title forces you to organize your thoughts.

How could you say that ? how do you know that my problem is not urgent. Actually, it is.

Why shouldn't I ask on several forum ? It's forbidden ? I don't think so.

Indeed, I have read your answer in labviewforum.de. I am gratefull for that, but maybe you could read the question more carefully.

I think what i2dx means is that most of the regular LAVA members are also visitors of all other LabVIEW forums as well. Sometimes it becomes a decision that a regular has to make and decide in which location they should post a reply. On top of that, after they reply in one location, they must follow up on all other locations with a link to the original reply. If they don't do that then they may give the impression that those other forums are not as important as the one they responded in. In other words, this puts more work on the person responding.

Please don't take this as a personal attack . You are welcome to post in the LAVA forums or wherever else you see fit. You should understand that the LabVIEW community is very small compared to other development languages so even if you post to one website, we will all see it right away.

As a side note, I find it kind of strange that you would post in English on a German LabVIEW site.

Ok, some more patch wierdness...

What the hell happened to my icons on my splash?

The time Y'all are reporting are making this update look very expensive!

Ben

Just send your Invoices for time spent compiling your code to NI corporate. I'm sure they'd love that...

ok, let's start a poll... how long did it take you to Mass Compile your code after upgrading to 8.0.1?

It took me 1hr:45min... :clock:

Download Here:

ftp://ftp.ni.com/support/labview/updates/...bview_8.0.1.exe

Docs:

ftp://ftp.ni.com/support/labview/updates/...adme_8_0_1.html

I sure can't wear it, but here's my earliest NI relic:

Hey, I like the flying eagle on the side. Similer to the NI logo I guess.

Ok, here comes another strange LAVA Forums thread.

I know you have them. Freebie T-shirts handed out by NI at various trade shows. Most of you wear them to sleep, or to hang aroung the house on weekends but I know you never even think of throwing them away right? Post pictures of the ones you have so we can try to fill-in the collection. I'm hoping someone has a LV2 T-shirt. Let's not just limit it to T-shirts. Why not thow in a few mugs and mouse pads...

Now you can try ANY string for a property or method name! Who knows, maybe you will find something new! Well, after a while, I guess... :headbang:

Ok, now we're finally getting interesting... :thumbup:

Well, not really giving us all our toys back... Still can't get to the Diagram property...

It's a Pretty cool tool, none the less. Thanks for the great contribution!

Yes, this is a very nice feature. However, I don't think that it will solve either of the problems mentioned above.

Ya, it seems like NI did a half a** job on this one. If they only showed the custom items placed in the Tools menu in the Options screen menu editor then this would be a good solution. Now, as it stands, you can only see the NI items.

Guys, thanks for your replies! No, I don't use 'DeferPanelUpdates'. Actually it seems to start working now, after I made a change which is in line with PJM's comment: earlier I used to embed a panel of a subVI and then call it (statically). When the call finished (i.e. the subVI stopped), I removed its panel and embedded the panel of the next subVI. It worked most of the time, but after 20-30 calls it failed with the front panel of the main VI (and everything embedded) becoming non-responsive.

What I did now is calling my subVI first, and then, within the subVI, embed its panel into the subpanel container of its caller. When the subVI is ready to finish, it removes its panel from the caller's container and then finishes. This seems to work so far, at least it still works after I cycled through various panels more than 50 times!

That this is the solution. Even if you look into the NI embedded panels examples that ship with LV. They always start the subpaneled VI's first before they embed them. This is the key to smooth operation.

Just discovered that if you take any decoration and stretch it. It will only allow you to stretch it to a size of 4095x4095 pixels. This is is LV7.11. This is not a show stopper but was curious why?

Well, it appears that LabVIEW 8 does not have this limitation...

Just discovered that if you take any decoration and stretch it. It will only allow you to stretch it to a size of 4095x4095 pixels. This is is LV7.11. This is not a show stopper but was curious why?

Well, If you haven't already read this, here is an article I wrote for NI's website a while back:

Changing the Face of Design Patterns with LabVIEW 7 Express Event Structure

Most of it is a list of design patterns but pay attention to the Event Structure With State Machine. This should be the direction of your program. This is probably a lot of work to transform your program to this design but worth it in the long run.

You say your code is 1MB. This is actually pretty normal size. The number of cases is not important and you shouldn't worry about this. It is important to abstract certain functionality into sub-vi's. I cannot stress the importance of sub-vi usage. This will make your Main vi lighter and your overall code easier to manage.

As far as multiple event structures. I've done this before and it works but there really is no benefit. Is this to split up code? Why? There is no reason not to put ALL your events in one event structure. You say the "event structure might get flaky" define flaky. There is no logic behind this assumption. Is there something else specific that you are worried about?

There is a file here:

C:\VXIPNP\WinNT\NIvisa\visaconf.ini

That file has a bunch of comments and allows you to comment out unused interfaces. That may solve your problem.

Here are some pictures from the Mindstorms NXT preview at the Las Vegas CES show:

Pictures of Mindstorms NXT

After you take the exam, add your score to the poll. No need to give your name, just the results.

Take the FREE LabVIEW Fundamentals Exam

LabVIEW Fundamentals Exam

The LabVIEW Fundamentals Exam is a FREE, online assessment offered in conjunction with the NI Training and Certification Program and is ideal for those wishing to quantify their level of LabVIEW knowledge. The exam provides students and professionals with an opportunity to demonstrate their proficiency with the fundamental concepts and programming practices that are integral to success as a LabVIEW programmer. It also acts as preparation for the National Instruments Certification Program.

Details of the Exam

The LabVIEW Fundamentals Exam consists of 40 multiple-choice questions with a 45-minute time limit. The exam encompasses essential LabVIEW concepts such as:

• Arrays and Clusters
  
• Charts, Graphs, and Loops
  
• Data Acquisition and Analog Input
  
• General Programming Structures
  
• Strings and Error Handling
  
• SubVIs and Printing
  

Passing the LabVIEW Fundamentals Exam requires an understanding and ability to employ fundamental LabVIEW programming techniques, logically analyze and debug various coding schemes and architectures, and navigate the LabVIEW environment with the skills necessary to develop efficient LabVIEW programs. The skills tested are commensurate with the level of knowledge contained in the LabVIEW Basics I: Introduction Course with an accompanying one to three months of LabVIEW programming experience.

I used an ODM (Object Data Manager), which is simply a non-running While Loop with a shift register and a case statement to Set & Get the required data.

ODM! that's a new one for Jim's list.

Maybe I should just re-write all of my code in a better architecture because right now I'm getting overwhelmed just looking at it.

I don't think you need to re-write, just yet. I've managed to shoehorn-in gradual enhancements to software in a similer situation.

There are many file IO implementations to do what you want but I won't get into that. I've attached some code that implements an architecture for handling configuration data within your program. You have to fill-in the code for reading and writing to the actual config files. For this you can plug-in the openG config VI's if you want but that is not the point. The point in the attached example is that the locals are replaced by a functional global. Wherever you need to read from the config data you place this down and unbundle the required parameter, or all of them. You should only write to these parameters from the configuration window. The nice thing about this is you can place the functional global deep within any subVI's you may use and you can avoid wiring messes.

Download File:post-2-1138297260.llb

Thank you Michael

i try the modify suggested by you and its work fine.

Now i have 600ms for 1000 select and about 400ms for 1000 update.

Bye,

Alessandro.

That is still slow. What SQL statement are you using? Also, have you indexed your table?

I just did a simple test with: SELECT * FROM `databasename`.`tablename` of 1000 records and it takes: 15ms.

Sorry guys,

I use "Match Pattern" in my program, and that's where the program stops........

Problem solved!! Thanks anyway for your help!! :worship:

Joost

That's awsome! Also thanks for replying and letting us know the fix.

I've created a CVI based DLL that can be called through LabView that lets you read and write to / from a SQLite database. This DLL simplifies the process of calling the SQLite DLL from LabView by taking care of some housekeeping and reformatting of data that are needed to make LabView happy.

Whould you be willing to post this DLL here so we could try it out?