LabView 6.0 and data bank

Hi;
Its possible i use labview conected with a data bank like mysql for example ?
Im needing implement a data bank for future consult ....

Yes it is. Here is a link, LabSQL which works with LabVIEW 6.0
System
requirements :
LabVIEW
6.0 or higher, running on Windows. In the future, we hope to add
JDBC modules
so that LabSQL can run on other platforms
The
database you are connecting to should have an ODBC driver (almost
all databases do: Access, SQL Server, Oracle, Pervasive, etc.)
MDAC
2.6 installed. You may already have MDAC installed, but if you
don't, download
it from Microsoft here.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Similar Messages

Labview remote control and data transcation

Hi,
We have a complicated timing control system written in labview
6.1 running on our lab PC-1. Since it is not easy to upgrade to a most
recent version and limited PCI-slots, and we need to add a few device
control programs (written in C++ or updated labview), we are thinking of
an ultimate control system with two PCs and let the old timing program
be a "slave" of "master" computer PC-2. OS for both PCs are windows XP.
The communication between the two PCs are
fairly straight forward: suppose on PC-1, the program breaks into two
parts: part A and part B. PC-2 sends selection messages to PC-1 to
determine which part needs to be running during a particular shot. It is
true that to our best interest we might need PC-2 to send data to
PC-1, in case for a particular run we have to change some data values of
timing program.
The problem might appears to be a piece
of cake to you experts. It is worth mentioning that on PC-1, any
changes made to the timing program is nontrivial due to its structual
complexity. The program is DAQ based (finite) pattern generation (using a
lot of PCI 6534/PCI 6713/counters, external clocking).
The
reqiurement for speed is not high. PC-2 can in general wait for 1
second before PC-1 receives a message and start to output. On the
other hand, the smaller the delay, the better.
We have
considered a few communication options like TCP/IP, RS232 ports, etc.
But before we start implementing the changes, we would really appreciate
your suggestions/comments!
Thanks very much in advance
for your time!
Kunyan

Kunyan,
there are really several different ways to solve this. The major question is: Is this a handshake protocol or simple "notifications"?
If it's simple notifications, things are getting quite easy.
You can use TCP/UDP/DataSocket/STM if there is a network connection between both PCs. Otherwise, RS232 might be a good idea as well for sure.... but i suggest a network technology in order to reduce delays.
STM is a protocol built up on TCP and even if you do not use it (it is not available for LV 6.1!), it might get you some ideas about defining a custom protocol.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Need help using LabVIEW 7.1 and data socket to transfer images

I need help transferring images across a company network using: LV 7.1, IMAQ 3.0 and a PCI 1407 image aquisition card. I am trying to use datasocket to transfer video image across a company network. I have attached sample vis. Thanks in advance for your help.
I. Cyr
Attachments:
Vibration Chamber Vision_Cyr.llb ‏129 KB

Hello –
Something that you need to consider is the fact that when you are sending an image over Data Socket, it is not really the image what is being transferred but a pointer to the image. Please take a look into this Knowledgebase.
Also, you might find this Example Program useful.
Hope this helps.
S Vences
Applications Engineer
National Instruments

Best way to move date between LabVIEW 7.1 and 2010

We have a large LabVIEW based control and data acquisition system that for reasons beyond the scope of this post is at and needs to stay at LabVIEW version 7.1 for the forseeable future... We are soon to add a camera diagnostic to this system that, again for reasons beyond the scope of this post, needs to be written in LabVIEW 2010... The 2010 piece of code will run and need to receive some information such as shot number, when to trigger, etc. from the 7.1 side of the system... Then after a shot has occurred and a camera image has been acquired, the 2010 code will do some on the fly processing of this image and within a few seconds will need to send back some results data to the 7.1 side...
The 7.1 code uses a tag engine approach to sharing data among different codes running on different machines... I think now that more modern versions of LabVIEW use a shared variable approach... But I need to communicate as I've described above between the two versions, 7.1 and 2010 (or it could be 2011 if that would offer some advantage)...
I'm new at this moving of data between versions like this so if something could offer some advice, especially if there is some tutorial information on this topic, that would be much appreciated... Thanks in advance for any help that you might be able to offer... thanks... bob...

It really depends if your tag engine like communication approach is a home brown solution or something like the LabVIEW DSC engine. If homebrown and well written you should be able to reuse the client library part of it in newer LabVIEW versions without to many hassles. If it is LabVIEW DSC it may be a bit more complicated since the only means to share DSC tags in version 7.1 was as far as I can remember their proprietary TCP/IP tag interface, which was replaced in newer versions with he shared variable engine.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Does anyone know how to display (in LabVIEW) the memory use during execution of an image and data acquisition VI to predict when it is time to cease the acquisition to prevent the program crashing?

Does anyone know how to display (in LabVIEW) the memory use during execution of an image and data acquisition VI to predict when it is time to cease the acquisition to prevent the program crashing?
I am acquiring images and data to a buffer on the edge of the while loop, and am finding that the crashing of the program is unpredictable, but almost always due to a memory saturation when the buffers gets too big.
I have attached the VI.
Thanks for the help
Attachments:
new_control_and_acquisition_program.vi ‏946 KB

Take a look at this document that discusses how to monitor IMAQ memory usage:
http://digital.ni.com/public.nsf/websearch/8C6E405861C60DE786256DB400755957
Hope this helps -
Julie

Does anyone know how to display (in LabVIEW) the memory use during execution of an image and data acquisition VI to predict when it is time to cease the acquisition to prevent the program crashing?

Does anyone know how to display (in LabVIEW) the memory use during execution of an image and data acquisition VI to predict when it is time to cease the acquisition to prevent the program crashing?
I am acquiring images and data to a buffer on the edge of the while loop, and am finding that the crashing of the program is unpredictable, but almost always due to a memory saturation when the buffers gets too big.
I have attached the VI.
Thanks for the help
Attachments:
new_control_and_acquisition_program.vi ‏946 KB

got these vi's off ni site a while ago - see if they help
Attachments:
Memory_Monitor.zip ‏132 KB

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I can think of two possible stumbling blocks:
What are your 8.6 options for "byte order" and "prepend array or string size"?
Overall, many file IO functions have changed with LabVIEW 8.0, so there might not be an exact 1:1 code conversion. You might need to make some modifications. For example, in 7.1, you should use "write file", the "binary file VIs" are special purpose (I16 or SGL). What is your data type?
LabVIEW Champion . Do more with less code and in less time .

Bank challan number and date

hi
remittance challan created and doing bank challan update,
how should i find bank challan number and it date.which number have to give or where does it created and how to see
just- i have given the no.1 and to day date but it is showing 'bank challan date is prior to internal challan date' error
thank you
sowmya

Hi
Checkt at
J1INCHLN - Post
J1INREV - Reverse
J1INBANK - Update Bank Challan Number
Srinivas

To read COMTRADE file in Labview there is an example provided. Can somebody provide the sample .cfg and .dat files required for its working?

To read COMTRADE file in Labview there is an example provided. Can somebody provide the sample .cfg and .dat files required for its working?

Thanks for the reply.
But this library doesn't contain any sample .cfg and .dat files which can be read and understood. Can you please provide the same?

Why the time and date is not correct when I save a waveform in txt format, using Labview 6.1?

I am using Labview 6.1 and my operation system is Windows 98. The date/time properties is configured in the Windows (time and date in the control panel is correct). I generated a waveform using Basic Function Generator.vi and saved this using the Export Waveforms to Spreadsheet File.vi. When I opened this file the date and time was wrong. Only the delta t was correct and it did not show the date neither the time, only a float number. How can I adjust the correct time?

Actually, the date/time is correct, it is expressed as seconds since January 01, 1904.
In order to print the string version of the date/time from your file, you will need to write a utility that converts the date/time to a string or series of strings in whatever format you wish. This can be done by reading the first line (I assume that is the line with the time on it), formatting the date/time into a string, and writing over this information in the file.
The waveform VIs were meant to be used internally to read and write waveform data. Any use beyond that should require you to add formatting and other information/data as necessary.

I want to know memory manament and data display algorithm in LabViEW.Where can I get some materials about them?

I want to know memory manament and data display algorithm in LabViEW.Where can I get some materials about them? I need them to complete my essay .Thank you for your help.

Memory menagement:
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/732cec772aa4fbe586256a37005541d3?OpenDocument
About data display: what type of data you wat display?

How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

Jay del Rosario wrote:
>
> How do I troubleshoot installation/distribution of a LabVIEW .exe
> which processes data using Matlab when it works on some computers but
> not others?
Poke around zone.ni.com and
http://digital.natinst.com/public.nsf/$$Search/ .
Good luck, Mark

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Questions on Xontrol--How to update the state and data

Hello, everyone. I am new to use the XControl. I don't understand how the program in the facade update the "state" and "Data" after we click the button. I cannot do that, please give me some help on the XControl.
My vi is in the attachment.
Message Edited by McArthur on 03-24-2010 02:19 AM
Working...
Attachments:
Button.zip ‏51 KB

McArthur wrote: Now I understand the reason why the state can not update, because I didn't do as TCPlomp mentioned. It seems working now....
I mentioned this too, however without a pretty picture.
quote:
When you modify data or state, you need to update the action cluster to indicate that fact.
McArthur wrote: The example is just a dummy, not really make sense.
The example is really quite good and shows these things too as well as many other important points. Please try to fully understand it.
I would strongly advise you to also look at my other suggestions. You still haven't explained the purpose of the xcontrol. I am still curious.
LabVIEW Champion . Do more with less code and in less time .

100% CPU using LabView 7.1 and DSC module

Seven years ago I used BridgeView and PXI to execute a project, and the results were so good that after that initial system, I installed one more using BridgeView, and three more using LabView 7.1.
BridgeView is working very well, but lately, LabView 7.1 is giving me more and more problems. It all started in a system running LabView 7.1 and DSC on Windows XP, using a PXI-8187 controller with a PXI-1042 chassis. I have two PXI-6533 digital I/O boards, one PXI-6030E multifunction, one PXI-6713 analog output board, one PXI-6602 counter board and one PXI-8422 serial com. board. In may/06, all of the sudden, the CPU went to a 100% use. Since I am running PID's to control a flash-butt welding machine in a steel factory, this was extremely dangerous. I changed the controller and everything went back to normal. It was running fine until december/06, when the same behavior appeared again. This time changing the controller did not help. We increased the system memory, from 256 MB to 512 MB and everything worked fine. But one month later (january/07) the fault reappeared. This time we changed the chassis and from that moment to this time, we are running smoothly.
Application problems were suspect from the very first time this problem appeared, but I was unable to identify the source, if any. I used PROFILE VI's and apparently the write/read tags were taking all the processor resources. However, changing the routines and disabling communications, and optimizing CPU intensive programs never solved the CPU overload.
Until now, I was aware of only one system showing this erratic behavior. But today I went to check another system, with a totally different application. This one is used to measure the thickness of the steel sheet on a rolling mill. Is not so resource-intensive, but the maintenance folks told me that every time they turned off this particular system, they always had problems trying to turn it on.
I was suspecting of a PLC-communication related issue, but what I found turned my alarms on. I turned off the system, which was fully functional, and turned it back on, and there it was, CPU load at 100%!. Is exactly the same problem that I have on the welder. This system has a PXI-8184, a PXI-1042 chassis, Windows XP, one PXI-6030E, one PXI-6713 and one PXI-6533. I battled for 20 minutes to put the system back in normal conditions.
I specified every single board, installed everything and programmed all the applications. The BridgeView applications have never showed anything like this. I am using the DSC (Datalogging and Supervisory Control Module) on both applications, and the Lookout Protocol Drivers are communicating to Modicon PLC's.
Please, I need help to solve this issue. I believe none of your actual Knowledge Base "100% CPU" articles apply to my case...
Thanks in advance...
Antonio Jimenez
[email protected]

Thanks for your reply...
Yes, sometimes I have the feeling that the systems works again because some file or database gets initialized after so many reboots.
Intentionally I turned off all the events and alarm logging to disk. Also the historical data logging is disabled. This is done by code, every time the main VI is started. This was included precisely to save CPU processing power. However, I am communicating to PLC's, and of course I have to declare variables inside the citadel database to make the communication possible.
Right now I can't have access to the application, because the mill is rolling, but during the next maintenance stop I will check the database location and size, and I could change the directory location the next time the fault comes up.

LabView 6.0 and data bank

Similar Messages

Maybe you are looking for