147 replies to this topic

[ShaunR]

Just wanted to point out a small bug I found in Query Transaction.vi in 1.3.0. You have the cases switched in the case structure that includes the rowid. It's probably something leftover from when you switched the logic of the boolean.

Also, since this is my first time commenting on this, thank you. This has been a lifesaver for me.

Confirmed.
I'll leave it a week or two so to see if anything else crops up then release a bug fix.

[ShaunR]

Confirmed.
I'll leave it a week or two so to see if anything else crops up then release a bug fix.

Just to clarify the interim fix for this:

• Locate and open SQLite_Query-Transaction.VI (It is in the "Query" Virtual folder under "Core".
• Right-click on the case structure (there is only one)
• Select "Make This Case True" from the popup menu
• Save the VI

It should now work as intended.

Edited by ShaunR, 07 January 2011 - 10:36 PM.

[ShaunR]

Just to clarify the interim fix for this:

• Locate and open SQLite_Query-Transaction.VI (It is in the "Query" Virtual folder under "Core".
• Right-click on the case structure (there is only one)
• Select "Make This Case True" from the popup menu
• Save the VI

It should now work as intended.

Correction of this bug will also have a knock-on effect on SQLite Delete Column.vi and SQLite_Rename Column.vi causing them to fail.

In each of these VIs there is a boolean (True) wired to the SQLite_Query-Transaction.vi. This boolean needs to be deleted.

The VIS will then work correctly.

[subhasisbehera]

Hi,

I am trying to read sqlite files in labview of 350 mb size in a computer having 3 gigs of ram and has windows xp.
I could read txt files of that size in this computer, even with a 2 gig ram. but, unable to open files of size larger than even 80 megs.
I run into out of memory problem. Is there any way I could read this kind of files.

[ShaunR]

Hi,

I am trying to read sqlite files in labview of 350 mb size in a computer having 3 gigs of ram and has windows xp.
I could read txt files of that size in this computer, even with a 2 gig ram. but, unable to open files of size larger than even 80 megs.
I run into out of memory problem. Is there any way I could read this kind of files.

The SQLite API is quite capable of reading 350MB plus files (I've just read a 450MB one). Your issue is probably to do with LabVIEW memory management.

If you are putting an indicator on the front panel. Don't.

LV Memory Memory Management 101:

File-size 456MB win 7 X64 LV x32




500 for the VI 0 wire junctions Requires 500 MB during and after execution.




500 MB for the VI, 500MB for the 1 wire junction, 500MB for the 1 indicator. Requires 1.5GB whilst executing (assuming it has already run once) and 1 GB after execution.

Add 1 more indicator and it will run out of memory. Why?....Because.....


500MB for the VI, 1GB for the 2 wire junctions, 1GB for the 2 indicators. Requires 2.5 GB whilst executing (assuming it has already run once) and 1.5 GB after execution.

Very approximate calculations, but I think you get the idea.

1. You need n x wire junctions more memory whilst running than you do with a static VI after execution
2. you need n x indicators memory to store the results.

[tnt]

I could read txt files of that size in this computer, even with a 2 gig ram. but, unable to open files of size larger than even 80 megs.
I run into out of memory problem. Is there any way I could read this kind of files.

I while back a had a similar problem (LV 8.5.1):
when using the "Read From Spreadsheet file.vi for reading (and displaying) a 60 MB spreadsheet (text-file) my PC got a memoryincrease of approx 1 GB !!
When replacing the "Read From Spreadsheet file.vi" with "Read from text-file" (with Read lines active) followed by a for-loop to convert each line to a string-array,
I got the same result BUT ony a memory-usage of several 100ths MB.
(I would have expected 2*60 MB with a little overhead in memory-usage but this was way better than the original memory-usage)

Has anyone seen the same effect as well?

[ShaunR]

Version 1.3.1 released

This is a purely a bug-fix release (addresses the bug reported by MarcA) and adds an installer. Upgrading to this version is optional..

[Michael Aivaliotis]

This LAVA Code Repository Download is no longer distributed or supported by LAVA.


Please follow this link for further support.