Recover Files Using Window’s “Previous Version” Property

Blogs, LabVIEW Blog, Snippets
Have you ever encountered that due to some bug in your software the imporant file has been deleted or overwritten?  May be that file could be important data logged in the production or could be your old source code.  Do you know that windows has some capabilities to recover those missed files? Recently I encountered such issue.  My own holy software which passed through all unit test cases, somehow misbehaved in the production site.  It adds more awkward moment if customer sees that issue and says "OMG..! My data are lost..!  Where is my data?". A quick google search on recovering windows files gave me a relief that Microsoft Windows in itself has some recovery given that if the restore points are configured in that Windows.  Since it's production PC,…
Read More

Subtle Problems in Multilevel USB Hubs

Blogs, LabVIEW Blog
A project recently got me through tough times.  We have connected almost all instruments using USB and ended up using multilevel USB hubs.  The hardware connection is something like below.  We thought that everything will be fine because All of these USB ports are detected by Windows without any issues The payload of these instruments' data are very low and We're able to test all these instruments in modular level. However we faced some subtle issues which is not lucid at the beginning. (more…)
Read More

How to use FTDI FT4222H in LabVIEW

Blogs, LabVIEW Blog
There is a very good device named FT4222H from FTDI Chip which can be used for multi-interfaces like GPIO, I2C, SPI, Interrupt.  The nicest thing is you could access all those communication protocols directly using LabVIEW.  Generally speaking, if you work with a controlling application where your end-device uses such protocols, you could use this device to communicate with the end-device and make the life easier and design would be low cost too (device costs only $2.30). [caption id="attachment_617" align="alignright" width="200"] Fig. FTDI FT4222H Device Image[/caption] GPIO Interrupt I2C Master I2C Slave SPI Master SPI Slave Initially I assumed that this device would be straight forward to use for my application which required three of those features viz.. a master I2C, a GPIO and an Interrupt.  However, it turned out…
Read More

Data Logging and Traceable Data

Blogs, LabVIEW Blog
One of the important criteria to consider while designing the data logging is the traceability of the data in future, in relative to the device/product under test.  Some logging is required only for temporary purpose but some data are required even till the end of the device life cycle.  A traceable data is required if you think you're logging product level details and and it needs to be persistent till the death of that product. Few scenarios where you would need traceable data are... When the product is out to end customers and end customers logs you with some defects with the product, you would need to trace back what exactly happened to the product during the testing phase using the traceable data.  Or whether there is similar pattern of…
Read More

Log Any LabVIEW data to CSV File or SQLite DB

Blogs, LabVIEW Blog
Have you ever tried to log your LabVIEW data to CSV or SQLite?  While logging your data from LabVIEW to a CSV/SQLite database, have you ever wanted to avoid the daunting job of creating the DB schema or creating the CSV headers for logging?  How daunting is the job of converting the LabVIEW data to CSV strings or SQLite data types?  We use to spend a lot of time for that.  Isn't it? Here is a tool which I have created recently can ease this logging activity in LabVIEW.  This is simple table logger which logs all your data to only one table (Yes! even your array data will be logged in the same table with other data). All you need to do is wire your LabVIEW data to the…
Read More