Labview 6 problem

When I try to Run Labview 6, it always comes out Error 37, which seems related to Error I32 and out ref on computer? How can I solve this problem. I am looking forward to help. Thanks in advance.

If this program was provided with the laser, maybe you should contact them. This does not seem to a problem with LabVIEW per se, but with the provided code.
Did it ever work before, or is this a new installation? Could it be you are using the wrong serial port?
Do you have access to the block diagram of the program or is it passworded? Hit "ctrl+e" when the VI is not running. Anything?
If the program instructions require you to run the program using the "Run Continuously" button, it seems that not a lot of thought and time went into the code development and it is probably buggier than an ant farm. WIthout seeing the code, it is impossible to tell.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Connection tcp labview problem with command.

Hello ,
I Have one qustion.
I have card relay with communication TCP .
my commands is char .
simple
char(254)
char(108)
char (0)
I have array [254,108,0]
my communication is good with out error. but I dont know problem .
why this command not work ???
this command on the relay in bank 0
ncd relay card.
Attachments:
Communication TCP.png ‏37 KB

maklevit wrote:
Hello ,
I Have one qustion.
I have card relay with communication TCP .
my commands is char .
simple
char(254)
char(108)
char (0)
I have array [254,108,0]
my communication is good with out error. but I dont know problem .
why this command not work ???
this command on the relay in bank 0
ncd relay card.
this is from the NCD site: http://assets.controlanything.com/Software/labview/RelayDriver.vi maybe you can adapt this to what you need? It looks very similar...
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Labview problem invoke node event

Salve a tutti,
ho questa classe in C#:
public class GUIRequest
private Client Clnt;
public GUIRequest()
this.Clnt = new TerminalEngine.Client(true);
public void CallAccountRequest(string ID)
this.Clnt.getRFAccount().AccountRequest(ID);
Clnt.getRFAccount().SendResponse2BLLabview += new RFAccount.SendResponse2BLLabviewHandler(ReceiveIdentificationResponse); //to check if it is the right place
public void ReceiveIdentificationResponse(object sender, OtherClasses.IdentificationResponse e)
if (SendResponse2Labview != null)
OtherClasses.IdentificationResponse argument = new OtherClasses.IdentificationResponse();
argument.UserName = e.UserName;
this.SendResponse2Labview(this, argument);
public void provamethod(int a)
int b = a;
public delegate void SendResponse2LabviewHandler(object o, IdentificationResponse e);
public event SendResponse2LabviewHandler SendResponse2Labview;
Quando vado ad usare la dll di questa classe in labview, come prima cosa uso il constructor node Successivamente, prendo un invoke node ed ho il seguente problema: non vedo metodi da utilizzare. Stranamente, se provo a commentare il metodo ReceiveIdentificationResponse, magicamente riesco a vedere (e quindi usare) gli altri due metodi. Quindi mi viene il dubbio che usando un metodo che ha come parametri (object sender, OtherClasses.IdentificationResponse e),crea qualche problama labview. In pratica questo metodo che crea problemi viene usato da C# (non da labview) per generare un evento che labview dovrà raccogliere.
Sapete aiutarmi per favore?
Grazie in anticipo,
Chiara

Grazie Marco. Funziona

DCOM in LabView Problem

Hi,
I'm trying to use our librarie in LabView 8.5, I reference this one using Automation RefNum and then use Automation open(Input: RefNum, "", True), everything is working fine while invoking nodes if these ones use COM, but if I invoke a node using DCOM, this one returns an Unknown error code (-1073467384);
I had a similar problem while developping in .NET, my solution was to indirectly call coInitializeSecurity() from ole32.lib; I tried to do the same with my LabView file, calling a dll (Call library function node) that correctly initializes the Security but nothing changed...
I also configured my local security settings and those of the LabView application from dcomcnfg (I only have the Basic Version of LabView...)
Thank's for your help .

Hello,
Are your DCOM settings correct?
Take a look at this link:
How Do I Launch a LabVIEW Executable Remotely using ActiveX/DCOM?
Did the error code come with any explanation?
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/

Labview problems, file corruptions, hang ups, etc..

we are having endless and constant problems with labview.
The problems are all reproducable on 3 different machines.
Im going to list the 3 most troubling.
The biggest problem right now is that our vi files keep getting corrupted approximatly every hour of work. The files cannot be reopened. Upon repopening the file, the processor utilizes 100% of the cpu. The three comptuers are all checked out to be okay, hard disks, ram, etc, and one is ever brand new with 8gb or ram.. I suspect the problem has to do with the matlab script environment. On one of the comptuers, after installing labview, i cant even get matlab to start up, it gets stuck utilizing 100% of the processor. This is the latest and greatest edition of matlab and labview 8.2 but was 8.0 a week ago. The reason we upgraded is to fix this. This is a huge disapointment and has costed many weeks of work. We are now going to try to remake all teh sub vi and matlab script, again. I feel the problem is the programming langugae at this point.
Another problem is that labview keeps hanging up when we are double click some of the graphical charts. It happens sometimes but not others but generally a few times a day.. Again, the problem is reproducable on all three computers. I think the problem has to do with the graphical objects being created by being copied rather then recreated each time from the front end but i dont see why this would matter as they should not be inheriting any properties.
Each time we create a new graph or object on the back panel, it goes to some artibrray position on the front panel which seems to be a huge distance from the rest of the objects. Moving these objects takes a great deal of time, around a minute each time, there has to be a better way then recreating the object and duplicating its properties each time on the front panel. No matter where we align the grid, the new objects go to some arbitrary position.
Just wondering if anyone has seen problems like this before....
I doubt is just us.
Message Edited by JimmyinCT2 on 02-05-2008 08:37 PM
Message Edited by JimmyinCT2 on 02-05-2008 08:37 PM

JimmyinCT2 said,
"The biggest problem right now is that our
vi files keep getting corrupted approximatly every hour of work. The
files cannot be reopened."
I have never seen this in many years of using LabVIEW, on multiple systems (desptops, laptops, even Dell's with Celeron processors ) Can you repeat this issue with a simple VI and post it here so others can test it?
"Another problem is that labview keeps hanging up when we are double click some of the graphical charts."
Do these charts contain large amounts of history data? Remember, if you are diplaying data in a chart, there is no need for it to contain 10,000 data points, as your screen is probably 1280 pixels across. Can you post a VI with one of these charts that gives you trouble?
"Each time we create a new graph or object on the
back panel, it goes to some artibrray position on the front panel which
seems to be a huge distance from the rest of the objects."
I don't know if LabVIEW has a feature that lets you control where the next new object on the front panel will be placed, but I have found it MUCH easier to click in the general area on the Block Diagram where you will want the object, then go to the front panel, copy the control or indicator or chart, click in the general area on the Front Panel and paste your object. The control or indicator in the Block Diagram will be placed where you last clicked. That makes copying so much easier, since the object in the block diagram is so much smaller.

DLM 40-15 LabVIEW problem

Hi, I would like to write a modular code to initialize and set the voltage for this power supply. I have downloaded the driver and I can see SNDCSDLM functions under the instrument folder. Has anyone had any experoience with this power supply in LabVIEW. I would like to power it on, initialize, set the DC voltage , set the max output current and voltage and leave it on until the user press the stop button.
Any help really appercaited

Yes, I've seen a similar error. Basically what I did was to verify that the RFC request was actually logging into the ABAP stack. You can do this by performing an SM50 trace of all the dialog processes during the RFC login and then using ST11 to read the trace files.
There should also be a more indepth rfc trace file created detailing the cause of the failure (I think it's in some temp directory). You can search your install directory for the latest log files generated after you run the test.
Please post the file so we can help analyze it.

To Altenbach Please email Put LabView problem in subject.

To Chris
This is the only way I know of to give you my email address.
"[email protected]" and remove the "-NoSpam" from address.
Thanks
Louise

setting email account blackberry HUB

Labview problem

how do i perform delay between characters to send to COMx
,due to a slow equipment.., and wait few seconds for the response
thanks in advance
simon

There are two VIs called "Wait" and "Wait Until Next Multiple" from the "Time & Dialog" pallette which you can use to delay your each send operation.
Joe

Problem with 'Word edit cell.vi' , Inputs transduced with the value of every row repeated

Hello,
Im using LV2013 with office 2013 report tool kit. I am trying to use Word edit cell to input values in table previously created in template .doc.
Indeed, i trying the example Generate report from template and didnt works well. I search for solution and I see it was a problem with previous version but it seems not solve totally in this version for word office 2010.
http://digital.ni.com/public.nsf/allkb/4041ECB5D02BA57D862579A00002FE8D
I checked this thread but i didnt get it to works. http://forums.ni.com/t5/LabVIEW/Problem-with-append-table-and-Word-2010/m-p/2190960#M702610
Any way to solve it?.
Thanks for help.
Fred
Attachments:
error.png ‏32 KB
Untitled 1.vi ‏19 KB
exampleTemplate.doc ‏37 KB

Hello, I solve it adding this to Word_insert_Table.
http://forums.ni.com/t5/LabVIEW/Report-Generation-MS-Word-Table-Bug/td-p/1605170
Thanks.
Open [LabVIEW installation folder]\vi.lib\addons\_office\_wordsub.llb\Word_Insert_Table.vi
There is a nested for loop that interprets the provided string array data and reformats it into a long ASCII string for the copy buffer. It should look like this:
Change the nested loop to look like this:
The changes I've made are twofold:
1. Within the inner loop, replace the "\n" char with a Tab character
2. Just after the inner loop, add a new "concatenate strings" function that adds "\n".

Using a "fopen" call in a DLL made with MatLab for Labview

Dear Sirs:
My name is Juan Crespo and I write you from Spain. I answer if you could help me with a Labview problem. This is the problem.
I want to write a DLL for being used in labview, and i want to use matlab for write this DLL. I have been searching in the web and reading the NI "using external code in labview" manual in order to know what I must do.
I know that if I want to use MatLab, I must build a "wrapper function" to avoid the different data type between MatLab and C. I have found on the web -Thanks to Alberto Sanchez- one example about how could a DLL could be written.
But it exist one diference: I want to read a plain text file that has the input data. so I must read the file, store
the data in an array and then pass this array to the "interface functions" but in a simple example this dont works
My question is ¿How could I open a text file in order to use it as input data in a DLL in Matlab?
Attached to this message is the code I use as "wrapper function". when I compile it there is no apparent errors, but when I try to use the DLL in a VI, an error appears.
If I change this code and the input is made "manually" (using the VI) there are no errors. So I think that problem is in the way that Labview consider "fopen" function when I build a DLL. The "num.txt" file, where the data input are, is on the same directory that dll file and VI file.
I hope that you can help me with this problem.
Thank you very much in advance and please sorry for my bad english
Best Regards
Juan Crespo
Attachments:
foo_wrapper.c ‏2 KB

Dear Juan Crespo,
normally I don't answer questions concerning Matlab because I have no experience with it. But your question was waiting a long time and had to do something with DLL I decided to look at it.
Your C code has a serious error. You are declaring a variabale named "in1" as "double *". You do not set this pointer to point to a variable. Then you use this uninitialized pointer in the fscanf function to read in from the file. The value is written somewhere in the address space at a place where "in1" is pointing randomly. This will cause an error or crash.
Declare "in1" as "double" like you have declared "out". You must change some other places where you have used "in1".
Waldemar writing from Germany
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

LABVIEW.LIB was not called from a LabVIEW process

Hi All,
I've inherited LV code that calls a CIN node to access a motor controller. I'd like to compile this code to a .NET DLL, but receive the following error when calling it from an external source:
I've read the knowledgebase article explaining the problem from here, as well as the following support questions:
http://forums.ni.com/t5/LabVIEW/Labview-lib-was-not-called-from-a-labview-process/m-p/232548
http://forums.ni.com/t5/LabVIEW/Problem-with-lsb-LABVIEW-LIB-was-not-called-from-a-LabVIEW/m-p/48809...
http://forums.ni.com/t5/LabVIEW/Labview-lib-was-not-calld-from-a-labview-process/m-p/718427
http://forums.ni.com/t5/LabVIEW/Building-a-LabVIEW-DLL-with-VIs-that-use-CINs/m-p/632817
The conclusion seems to be recompiling is the answer. I've tried recompiling the original CIN vi within LV with no success. Do they mean to recompile the original C code against the newer labview.lib (sorry, I'm not all that familiar with how the CIN nodes work)? Any suggestions would be awesome. Thanks.
-Joe

You can't make use of LabVIEW manager functions in non-LabVIEW based processes. Basically unless the C code is for a CIN or DLL that is to be called by LabVIEW (inside the development system or a LabVIEW built application), any function pulled in from labview.lib is not available. LabVIEW.lib is an import library that does not implement any functions but simply imports them from the LabVIEW kernel, either the LabVIEW development system or the LabVIEW runtime DLL. And no you can't just link in the LabVIEW runtime DLL into your .Net application. This DLL needs to be started up and initialized in very specific ways, that only LabVIEW itself knows about when building an application.
Basically if you want to recompile the code (yes in C/C++) for use in a non-LabVIEW application, you also have to remove all the link libraries from the LAbVIEW cintools directory, and replace any use of functions now unavailable (link error: unavailable external reference) with other similar functionality from your C runtime library. Or implement those functions yourself using C runtime library calls.
Another possibility could be to actually create a LabVIEW executable that exports the functionality as ActiveX Server. Or in LabVIEW 2010 you could also select to create a .Net Interop Assembly from inside the LabVIEW project.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Problems using event structure to write new parameter values to VISA

Attachments:
FMA_event_2.vi ‏28 KB
FMA_event_2.vi ‏28 KB

It seems I'm also having trouble using forums..not sure what happened...updated and corrected thread: http://forums.ni.com/t5/LabVIEW/Problems-using-event-structure-to-write-new-parameter-values-to/td-p...

What is the best way to organize LabVIEW VIs to be used with TestStand?

I'm using LabVIEW 8.6 with TestStand 4.1.1 and I'm trying to organize the VIs to later deploy them to a production PC. So, I organized them into a LV project and built a LLB with the "Source Distribution Tool". (Destination type: LLB)
Some VIs in the LLB use the "Call Library Function" (user32.dll) to simulate keyboard events. But, when any of these VIs is called from TS, LabVIEW is suddenly terminated. When these same VIs are not in the LLB and are called from TS they do not have any problem.
Is the LLB the best way to organize VIs to be used with TestStand? If so, What could I be doing wrong?
I appreciate your help.
H.P.
Mfg. Test Engineer
Certified LabVIEW Associate Developer
Attachments:
LabVIEW Problem.JPG ‏28 KB

Hi Ray,
I really appreciate your intention to help, but I believe I solved the problem already. However I still have some questions.
The problem was that when I built the LLB the configuration of the "Call Library Function" changed. When the LLB is built it is also created a Support Directory named "data" that contains some dependencies including a new copy of the user32.dll. The "Library name or path" field in the "Call Library Function" changed to be linked to a new Dependency Path. ( ...\data\user32.dll.)
What I did was select "Specify path on diagram" and create a path-constant ("C:\WINDOWS\system32\user32.dll"), so the "Call Library Function" will be always linked to the original user32.dll.
I still don't know why the "Call Library Function doesn't work with the user32.dll copy in the New Dependency Path. And I'm not sure if the LLB is the best way to organize VIs to be used with TestStand.
Do you know why?
Thank you,
H.P.
Mfg. Test Engineer
Certified LabVIEW Associate Developer

Timezone offset for dst in LabVIEW 8.5

I think there is a "bug" in LabVIEW 8.5.1 and probably 8.5 too. I used to have an application that was transmitting timestamp data between computers in some sort of HTTP protocol. The server application has been build in LabVIEW 7.1 and remains in that version for various reasons.
Now the timestamps are transmitted as UTC formatted strings according to RFC1123. In order to do that I used an old function developed in LabVIEW 6.x or so that calculates the current timezone offset from a timestamp value of 86400 seconds (eg. Jan 2, 1904, 12:00:00 AM GMT). Turning that into a date time rec I observed the actual day, hours and minutes to calculate the timezone offset.
With LabVIEW 7.1 the timestamps in LabVIEW started to use the actual timezone offset valid for the timestamp except if that timestamp was earlier than 1970 in which case it still used the current timezone offset as it did before.
LabVIEW 8.5(.1) apparently changed that behaviour to always use the timezone offset of the actual timestamp and since 2 Jan 1904 was probably in every country (at least on the northern hemisphere) non-DST it now gives a different timezone offset than it used to do since the beginning of LabVIEW 2.5. This is cause me an hour or two of debugging :-(.
Of course the new >= 8.0 solution to calculate the timezone offset is now to convert a current timestamp into a non-UTC date time rec and convert that date time rec back into a timestamp telling it that it is a UTC record and then subtract the original timestamp from that.
I would expect the Internet Toolkit to have that same problem unless it has been adapted for LabVIEW 8.5, since my original routine was at some point "loaned" from that toolkit.
Rolf Kalbermatter
Message Edited by rolfk on 06-13-2008 02:59 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

jimfoxy wrote:
I had a similar problem. I thought it was an intentional feature.
I frequently work with GMT date & timestamped data as an int/double number of seconds or hours. Is there a sensible philosophy of displaying such data on a graph (with X-axis selected as 'Absolute time') without having to first convert the times into system timezone-dependent numbers? What I am doing at the moment is reading the GMT data in, converting it into timezone dependent values to display and manipulate (by applying the method above), then converting the results back again in order to output correct GMT to various files.
I always find it hard to work with time in Labview because you need to keep a close eye on local system timezone settings, unless you ensure that you set the PC's clock to GMT non-daylight savings (not an option for me). It is great that there is now an on/off UTC option for some of the time related VIs.
I don't want to mess around with timestamp datatype because I need to perform manipulation such as division and can't get that to work with timestamps.
Thanks.
It is not a LabVIEW problem really but simply a problem of any application running on a localized date/time system. And since time in any other form than SI normalized is a ratherbeasty thing, it gets troublesome to deal with it in software.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Analoge shared variable read Problem

Can any body help me in reading analogue shared variable read in LabVIEW 2009 dynamic event structure. I have tried to read the above tag through Tag Reader VI but i have experienced too much delay in first read for real data i.e. Plant data from PLC. when this particular VI executes it take minutes to display the data. if some needs its code i can provide it. Thanks in advance

This seems to be a LabVIEW problem, so please post it over in the LabVIEW forum.
(the feedback forum is for problems with the website itself)
LabVIEW Champion . Do more with less code and in less time .

For Experts: Why does LabView cause System reboot while accessing hardware with driver?

Hello NI Developers!
I use LabView 7.1 under Windows XP
I have a programm console application which accesses through Jungo Windriver PCI-E board.
This program works fine - and performs DMA data transfer between PC and Board's memory.
In order to implement this console application work together with LabView I did following:
1) Added this function inside the source:
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
    AllocConsole();                   //Open new console window
   SetConsoleTitle(L"Debug Window"); //Set a title for console window
    freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                    // so we are able to see "printf" outputs
   freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                    // so we are able pass inputs from keyboard
   main();                          //Call applications main function which does all the work
2) Compiled this new source as DLL library
3) Call LVMainFunction(...) function from LabView using Call Library Node
In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
It works fine till the last function, which perform DMA data transfer - and reboots PC.
1) Why does this happen?
2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
   So does LabView have somekind of restrictions of accessing Hardware's functions?
I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
console window - and the result is the same.
3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
Thank you in advance!
ACiDUser
Message Edited by ACiDuser on 11-13-2008 09:37 AM

Hello!
At LAST!!!
I solved this problem!
From the beginning I was following National Instruments manual on how to build DLL with external IDE:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_library_project/
Set the Struct member alignment control to 1 Byte.
Now this option caused my PC to reboot!
So could someone explain why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
- wasting 2 monthes of time determining the problem.
I changed it to Set the Struct member alignment control to DEFAULT.
and now everything works fine.
Regards
Message Edited by ACiDuser on 11-13-2008 11:14 AM

Labview 6 problem

Similar Messages

Maybe you are looking for