2019 – Ajay

16Oct 2019 by Ajay 2 Comments

Not Enough Memory in TestStand + LabVIEW environment

If you have your test running in 32bit version of LabVIEW and 32-bit version of TestStand, and especially if your application is dealing with image processing algorithms, then there are numerous chances you end-up with a Not Enough Memory dialog from LabVIEW as below. There are some creative way and some workaround way to fix this memory issue. Not enough memory dialog from LabVIEW. 1. Unload option Find out the step which consumes most memory and change the Unload Option for that step in TestStand properties. I prefer Unload after step executes. This option would unload that step from the memory and thereby releasing any data stored in that module. Ensure if this module deals with any references, which upon closing, other modules might get affected. Choosing Unload after step…

Oracle ODBC Connection & Key Learnings

Blogs, Snippets

Using an Oracle database from LabVIEW is quite jargon journey. From Instant-Client to ODBC, OLE DB, SQL Developer etc, difference between ODBC, ODAC, OLE DB, ADO etc, all can lead one to confusion easily. NI has tried to explain well on this document, it's still not very lucid in other sources like stackoverflow. I'm not confronting here to clarify all those. I found some few key learning are worth sharing. Windows has implicit classification of files between 32bit and 64bit. If you create a file using C:\Windows\SysWOW64\cmd.exe, then it creates pure 32-bit file. Look at this link for more details. LabVIEW connects to the database provider purely based on the LabVIEW bitness. If you use 32-bit LabVIEW, then use the 32-bit data provider and UDL file.Never get confused with Oracle…

SVN Externals

Blogs, LabVIEW Blog, Snippets

If you are looking to reuse a project which already exists in another project and if you need that new project gets updates of the already existing project then-and-there, there is a very good feature in SVN called as externals to help on this kind of requirements. Advantages You can avoid multiple copies of the same source in SVN/source control repositories. Get updates from the root project as and when there is an update. So no need to manually copy the project again when there is an update. SVN-logs are maintained for the root project from the new project and hence better historical control. In case you don't need updates from root project, use specific revision to freeze to selective version. How does that works? This can be best explained…