Problems with labview 7.1

hi all,
i had posted this question before but no one replied so i am posting it as a new message.
i am using labview 7.1 and wanna use fp-1000 and fp-tc-120(2 of them) to measure 16 temperature values from t-type thermocouples.
i connected the fieldpoint hardware with labview through RS-232 and also installed fieldpoint 5.01(with support for labview 7.1) in my system. but MAX does not detect the device. why is this happening. i checked the port settings and they are fine.
if the following info helps then i must mention that a pci-gpib card and a scxi daq system is also attached to my pc. i also made sure that the addresses are different for each one of the hardware devices.
something more, previously i was using labview 8.2 on which the device was working fine. but i had to migrate from one pc to another on which there is labview 7.1 and i cannot install labview 8.2 on this system. so please let me know what to do?

Hello Kuna,
Looks like your other forum post was replied to. In order to maintain the efficiency and organization of NI Discussion Forums, please refrain from creating duplicate posts in the future.
Cheers,
Emilie | Applications Engineering

Similar Messages

Problems with LabVIEW 7.1 and lock-in amplifier Stanford SR530?

Does has anybody had problems with LabVIEW 7.1 and the instrument driver for the lock-in amplifier Stanford SR530?
With LabVIEW 6 there are no problems at all, but with LabVIEW 7.1 it is impossible to communicate with the instrument.

amr_attia wrote: (Private message, no need to private message)
My problem is to get the data out from the divice x and y readings . Can you help me
Here is the code and snippet. I had it from before. It reads Channel 1 and Channel 2 from the SR530, that is whatever the display is for Channel 1 & 2. You set the display manually or programmatically, I let you figure that part out.
Cheers,
mcduff

Problems with Labview and Windows XP with error -2147217865

Hello. Im a new beginner in Labview and am having a problem with a error message
I dont understand. Im running Labview on a pc-logger with windows XP.
The program is written by a guy on my university, and logs voltage from
a solar cell panel. He doesnt have the time to check in to it, so Im supposed to
find out what's wrong.
The error message is as follows :
Error -2147217865 occured at Cmd Execute.vi->DB Tools Insert
Data.vi->Solcelle.vi
Possible reasons :
Exception occured in Microsoft OLE DB Provider for ODBC Drivers,
[MySQL][ODBC 3.51 Driver][mysqld-3.23.38-log]Can't open file :
'solcelledata.MYD'. (errno: 145). in Rec Create - Command.vi-
>Cmd Execute.vi->DB Tools Insert Data.vi->Solcelle.vi
I really hope someone can tell me what's wrong and specifically what to do
with it, or possibly guide me to someone who could suggest a solution to this
problem.
Reguards
chrisdee

Hi Chrisdee,
(.. not to discount what TimoS has suggested, however...)
Embedded in the error information you provided:
... Can't open file : 'solcelledata.MYD'.
Sounds like the program needs this file? Has the program been moved to a new location?
just a wild guess!
Cheers
Message Edited by Dynamik on 10-06-2005 04:53 AM
When they give imbeciles handicap-parking, I won't have so far to walk!

Linux font problem with LabVIEW 7 Express

Is there a change in how LabVIEW 7 Express for Linux
uses fonts? When I run LabVIEW 6.1 (on the same
machine) the standard font (10pt Application) looks
very nice (in menus, front panel and diagram). With
LabVIEW 7 they are not so good to read. What can I do?
Thanks in advance,
Armin Herzer

Hello Evan,
Sorry for the late replay, but I was on holiday last week.
I am using Debian GNU/Linux woody 3.0 (testing). The video driver is the one which is shipped with XFree86 in this Debian installation. I also used the newest video driver from NVidia but the problem is the same (btw. is this a NVidia problem? Unfortunally I can only test on machines with NVidia cards). I attached a screenshot to visualize the problem.
The problem is not VI specific. All text (menus, comments and so on) have this ugly font.
Thanks in advance,
Armin Herzer
FH Ravensburg-Weingarten
University of Applied Sciences
Attachments:
lv6170.png ‏15 KB

Any problems with labview runtime v 7.1 on one host interacting with lvrte 6.1 on another host?

Using OPC, UDP ant TCP on the host running lv 7.1 runtime, communicating with a second host running lvrte 6.1. Both hosts communicating with cpfp 2020 and using similar IAK files. Need to know if there are any known problems with this scenario. I cannot convert st this time, the legacy 6.1 side.

Hello,
Thank you for contcting National Instruments.
I am not sure I understand your question. The LabVIEW Run Time Engine (LV RTE)is used when you will be running an executable on a target. If you want to run executables on your cFP-2020 that were built in LV 6.1 and 7.1, you will need to make sure that LV RTE 6.1 and 7.1 are installed on the cFP 2020.
If you wish to run VIs (not executables) targeted to your cFP-2020, you can use LabVIEW Real-Time 6.1 or 7.1, but not both.
Let me know if you have further questions.
Sean C.
Applications Engineer
National Instruments

Strange math-problem with LabVIEW 7.1

Hello!
I am using LabVIEW 7.1 and I came to this strange math-problem. Could it be that it is a problem of LabVIEW 7.1?
Ok try this with LabVIEW 7.1:
open a new VI
place a subtract-VI (pallet numerical) on the block diagram and try to subtract 0.2 from 1.6
place a less-VI (pallet compare) on the block diagram and wire a numerical constant 1.4 to input x
wire the result of the subtraction to input y of the comparison
place an LED to the output of the comparison
and start this.
What does it say?
The LED should turn on and this means here that 1.4 would be less than 1.4 .
But I would have expected that 1.4 is not less than 1.4 .
This works also if you add or subtract upto 0.2 to/from the values 1.4 and 1.6 (or equivalent with 0.2) .
If you change the inputs of the comparison then the result is as expected and 1.4 is reported not to be less than 1.4 .
If you compare two constants with the same value 1.4 you will not get the same strange result.
Does anybody have an explanation for this?
Espelkamper

Hello,
For floating point math: Rounding to multiples of 0.1 is problematic as
those numbers are infinite fractions in base2 representation...
So maybe you should change your numbers to integers using fixed point math. If all your input values are in the range of 1.4 to 1.8 you can multiply by 10000 and round to next integer. Then do your comparison on that integer (there's also an 'InRange' function in the comparison palette).
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Problem with Labview and an ARM Cortex

Good morning,
I am currently trying to use Labview with a board from ST Microelectronics (MCBSTM32) with an ARM Cortex Processor.
I use the SDK and have followed the tutorials.
But, when I try to launch the program (the simple loop as write in the tutorial n°2 : http://zone.ni.com/devzone/cda/tut/p/id/7029 ), Keil gives me an error via Labview:
"Argument 'DARMSTM' not permitted for option 'device'."
It seems that Keil does not allow an ARM Cortex from ST as the device.
Moreover, after having this problem, I am unable to use a Keil project ,even a project which worked before, without Labview. I need to restart the computer.
I also try to launch the Keil project generated by Labview, without using Labview, and it works. But as soon as I use Labview, I have the error.
Did anyone already have this error or know how to solve it
Thank you for your answer and sorry for my bad english.
Regards,
Raphaël VAISSIERE

Hi Raphi,
So let me make sure I understand,
The project created in LabVIEW errors out with the message "Argument 'DARMSTM' not permitted for option 'device"
If you open the same project in Keil uVision, it runs fine
Here are my questions:
1. So how does the code run when run through Keil? does it deploy and run fine?
2. Did you follow the porting procedure completely?
Your target STM32F103RB is techincally supported by Keil but you need to port the RTX kernel to it. This paragraph explains it:
To determine if your target already supports the RTX Real-Time Kernel, browse to the \Keil\ARM\Startup directory, then browse to the folder that corresponds to the manufacturer of your ARM microcontroller. If there is an RTX_Conf*.c file for your target, then the RTX Real-Time Kernel has already been ported for your ARM device. If no such file exists, skip to chapter 4 for more information on the RTX Real-Time Kernel and a guide for porting RTX to your ARM microcontroller.
You also need to port the Real-Time agent to it.
I just want to make sure that you have followed the guidelines. If you have and are still having problems, we will continue to explore this.
Thanks,
National Instruments
LabVIEW Embedded Product Support Engineer

Having a major problem with LabVIEW programming

I have been a faithful supporter of National Instruments hardware and software since 1997. During that time I have worked in academic laboratories using NIDAQ boards and LabVIEW for basic and applied biomedical research. To date, all my work has revolved around using the amazing analytical capabilities of LabVIEW for on- and off-line processing of analog input signals. I have not been involved in the programming of multifunction input/output vis.
Now I am at a point where I am ready to construct and design experiments that require what I suspect are some very basic multi-function DAQ capabilities.
But I am having very little success after several weeks of concerted efforts. Each attempt is partially successful, but fails to address the exact components I need.
For example, my most urgent need is to read an analog input channel set, and stream it to disk. I would like one channel to trigger a single TTL-like pulse based on a known, period signal. But, I absolutely need an accurate, user adjustable (not necessarily on the fly) delay from when the trigger is received to when the pulse is delivered. What I have so far is a combination AI-CO vi that outputs a perfect CO-driven pulse. It is phase-locked to the periodic signal, but I cannot adjust the delay; the 'inital delay' input to the CO channel does not reset when the trigger is set to 'retriggerable.'
I would like to stay with hardware timing, but I'm not sure I need to. If I go the software timing route, I don't think I have the skill/ability to make a stable vi.
I have extensively searched, used, modified, and tried almost all of the DAQmx example vis, and extensively searched the NI website and discussion forum. This has been very successful, and I have learned from these, and incorporated them into my vis.
Specifics of my set-up are: PCI 6023E, Labview 7.0 express (Full), Nidaq 7.3.
My question is this: is there an enthusiast, or NI guru that would be interested in corresponding with me to help me solve some of these problems? I am a resident physician with only a limited amount of time to construct a successful project. I absolutely know LabVIEW can do what I want, but clearly I can't make happen without some help. For an expert what has taken me several weeks can probably be optimized in a very short while.
I am available to correspond by phone or email. If anyone is interested, I can post or email code. Thank you very much, matt ([email protected]).

Dear Matt,
Thank you again for contacting National Instruments.
You are correct to notice the initial delay will not reset. It is not meant for that purpose. So I've been working on a workaround for you.
I believe you'll need to implement a new counter. This counter will be triggered by your current trigger, counts down for a certain amount of time, and when it reaches the terminal count, outputs a pulse you can use to trigger the other counter.
There are a few difficulties in making this work. The count down must be reset every time you trigger. Also, the count down must only occur for a finite amount of time, otherwise multiple triggers will be fired when the count reaches the terminal count. Therefore, creating a pause trigger to activate the
first counter is the way to go.
Using a pause trigger, the count down will occur whenever the trigger is high, and will cease to execute when the trigger goes low. If we put this count down mechanism in a continuous while loop so that it is reset every time the pause trigger executes, you will be able to specify an exact delay (due to specifying how long to count down).
Then, we just use the counter internal output - that is set high whenever the terminal count is reached - as our second trigger to execute what you already have.
I've included an example. In this example, it shows the idea behind what we're trying to do, but it isn't right yet. There is a conflict in routing I still have find a workaround for. I think if we route one of the counter outputs externally, and then back in, it may work. Both parts of this program work separately (for example, the triggering off the counter output, that you also set up, works correctly, and the countdown triggered off a different d
igital pause trigger, also works correctly).
Let me know if you have any further questions or if this does not resolve your issue.
Thanks again and have a great day!
Chad AE
Applications Engineer - National Instruments
Attachments:
retriggerable_analog_input_with_delay.vi ‏189 KB

Problem with LabVIEW color options?

I've tried to set the front panel and menu colors to the predefined system color 'Panel & Object' in Tools > Options > Colors dialog. When LabVIEW is restarted the front panel and menu is black rather than the expected grey!
I use LabVIEW 6.1 on Windows NT.
I guess that this is a bug. Is there a fix or work-around?
Selecting the color from the palette works fine, but will not make the vi adapt to system colors.
Kind regards / Med venlig hilsen
Torben

I think that there is a workaround that will work for the PC and the Mac, but not on XWindows. You just go into your ini file and find the place where the front panel (or whatever) color is set. In your case I think it will be set to 000016. Change this and set it to 01000016. You can do this with any symbolic color that you like and it should work.
Good Luck.

Having problems with Labview 7.0 after installing Windows XP Pro

After updating Windows XP Pro from Windows 98, my programs give me the following error:
The procedure entry point SUnMapLS_IP_EBP_12 could not be located in the dynamic link library KERNEL32.dll
I tried reinstalling Labview 7.0, but to no avail.

Hello Becky,
I performed all the windows xp updates when I installed xp.
Our computer has labview 6.0 and 6.1 on it. I thought maybe they were causing a problem, so I tried uninstalling them. I downloaded msiblast and tried to remove Labview 6.0 and 6.1, but since they used to be on a network, and the university does not carry those programs anymore, they gave me errors. I was able to uninstall 7.0 and reinstall it, but it still gave me the same error as described in the original post.
I went into the registry and removed 6.0 and 6.1, but it still gives me the same error.
I need a way of removing 6.0 and 6.1 so that I can do a clean install of 7.0.
Thanks for your help,
Sergio
Attachments:
Serg_usf_Screen_Shot.doc ‏550 KB

Problems with LabView 7.1.1 and Report Generation

I have just upgraded from LabView 7.1 to 7.1.1. As per the release notes, I did a mass compile of the vi.lib/addons/_office folder (which contains the Report Generation Toolkit for Microsoft Office v1.1) but I get a lot of error messages complaining about "Bad VI". These VIs are no longer available after this operation. If I don't compile them (ie leave them in 7.1 format) then LabView complains that some subVIs are not executable.
Are LabView 7.1.1 and the Office toolkit 1.1 compatible? How do I get them to work together?
Simon

Maybe you have figured this out by now.... But after reinstalling/upgrading LV you must reinstall your Report Generation Toolkit.
If you care for the why.... There are a few files that both the Report Geneartion Toolkit and LV install, only the the Report Generation Toolkit installs a more beefed up version of the files. When you upgraded LV, LV copied a new version of these files (a version that doesn't have the Report Gen support in it) over the Report Generation version. So you have to run the toolkit installer to get the toolkit version back.
Deborah
Message Edited by Deborah on 10-06-2005 12:37 PM

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

Run-time engine problem in Labview 2009 and Labview 2010

I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation related to Labview is not permitted and the same error came up every time. it is very annoying.
So, What is the deal?
I attached the error here. Any comments or advice are welcomed and appreciated.
Attachments:
error.docx ‏2305 KB

By chance is this machine's language set to any non-English locale? You would check the locale setting by:
Opening Control Panel.
Opening "Regional and Language Options".
Looking Under "Regional Options" >> "Standards and Formats"
If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
Regards,
- WesW

Problem with printing graph larger than screen size in labview6 (plots are shopped).

I have attached with my message the report I try to print. It is a Labview 6 vi.
I had no problem with Labview 5. But with Labview 6, the plots are shopped (all the rest of the report is correct). What is printed is not what I see.
The graph is intentionnaly built very large, then rescale to fit page, in order to improve the print quality of the plots. I repeat it, it worked fine with Labview 5.
Thanks if you can help.
Lionel.
Attachments:
Print_of_large_scale_graph.vi ‏284 KB

Hi Lionel,
I experienced a similar problem days ago: re-compiling a vi from LV 5.1 to LV 6.0.2 its front panel could not be printed anymore; no error, just a blank sheet.( The mass compile procedure did not reported any error).
The only way to get out from this headache was to re-build the vi in LV 6.0.2, I simply selected all its diagram and copied it in a new vi, saved it and I got print-outs!
Try it.
Good luck,
Alberto

Problem with data table and internal and external command button

thanks for your time,
i have this problem
<t:dataTable binding="#{manejadorAsociarEvaluadoresProyecto.tablaPosiblesEvaluadores}"
cellpadding = "6"
cellspacing = "3"
value = "#{manejadorAsociarEvaluadoresProyecto.listaPosiblesEvaluadores}"
var = "posibleEvaluador"
preserveDataModel="false">
<h:inputTextarea value="#{posibleEvaluador.correoActualCuerpo}"
cols="50"
rows="50"
rendered="#{posibleEvaluador.detalle}" />
<h:commandLink immediate="false" action="#{posibleEvaluador.editar}" value="Editar Correo"/>
</t:dataTable>
<h:panelGroup id="panelBotonEvaluadores" rendered="#{!manejadorAsociarEvaluadoresProyecto.b_mostrarEvaluadores && manejadorAsociarEvaluadoresProyecto.tieneProyectos}">
<h:commandButton action="#{manejadorAsociarEvaluadoresProyecto.mostrarEvaluadores}"
value="Asociar evaluadores"/>
</h:panelGroup>
this is the method of posibleEvaluador
public String editar()
setDetalle(!getDetalle());
return "";
all run perfect, until y click in "asociar evaluadores" button, after of this the commandLink "editar Correo" not run, this commanlLink is for not show the inputTextArea, i don't know what happend.
thanks for your help

Hello,
I have replicated and confirmed the problem with LabVIEW 2010, Report Generation Toolkit 2010 and Word 2010. I have filed this to R&D under CAR ID #257414. As a workaround you can manually set each cell using Word Edit Cell.vi. I have attached a simplified representation of this unexpected behavior as well as the workaround. Hopefully this helps everyone out!
David_L | Certified LabVIEW Architect
LabVIEW Tools Network | LabVIEW Tools Network Developer Center
Attachments:
Word 2010 Table CAR.vi ‏17 KB
Word 2010 Table FIX.vi ‏22 KB

Problems with labview 7.1

Similar Messages

Maybe you are looking for