Scilab Gateway under Labview 8.2 and 8.5

Hi Newsgroup,
i am a Labview Starter and working for a longer time with Scilab.
Herefore, the gateway function is a nice tool for me.
When i create a VI with the Scilab Gateway, it works really perfect
under Labview 8.2.1 (Jubilee Edition), but under Labview 8.5 the VI
seems to be not correct. The "Run"-Arrow is displayed broken, nothing
works.
Funny Effect in Labview 8.5 beside: In a few cases i've seen the
effect, that my VI works just one time, then never again ?
Have i done mistakes while installing anything. Or are there hidden
registry entries ?
Best Regards
Andreas

Andreas wrote:
i guess, i find one point: In the block diagram window in LabView
8.2.1 i make a right click on the script-box and open the menu item
"choose script server". Here, Scilab is displayed and choosen.
When i do the same in LabView 8.5, the menu item "choose Script
server" does not show me Scilab. The entry "Scilab" is not available.
Works just fine here in LabVIEW 8.5. Did you restart LabVIEW after installation?
Message Edited by altenbach on 10-31-2007 01:00 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
SelectScilab.png ‏11 KB

Similar Messages

Data acquisition of CV7-V wind sensor under labview using NI 9403

hello
I want to measure a numeric type RS232 signal at the output of a CV7-V wind sensor (attached PDF file)
I used the module CDAQ 9191 and NI 9403 under NI MAX and I got the result on the attached figure
how I can retrieve the information from this sensor under labview using CDAQ 9191 and 9403 Module
Attachments:
2015-01-25_120704.png ‏10 KB
CV7-V_OM_GB_150910.pdf ‏499 KB

If it's an RS-232 Serial Device - why don't you use a serial port instead? That way you can just read the data using simple serial functions.
If you have to use a digital I/O device - then you will need to convert the signal into digital data (using the timing information of the RS-232 device) and then convert it into the numeric data output by the device. It's not something I've ever tried to do but have a look at the digital waveform functions in LabVIEW as that might help you convert the analogue signal into binary data which you can then convert into a string.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Problem with running a program under Labview 8.6

Hello,
I am writing you this to ask for your technical support to fix the problem I am facing at our Lab at University of California, Irvine.
Ms. Vanessa Trujillo has kindly come to our lab a couple of times and tried different things to resolve the issue, but unfortunately the issue is not resolved yet. Here is a summary of the problem:
We used to use Labview 6.1 for our fatigue testing and data acquisition.
Our
program worked just fine under the 6.1 version We recently upgraded our software to Labview 8.6. We have also purchased a new computer that has higher capacity than what your website requires for Labview 8.6. The new computer has Windows Vista We transferred our old program/subprograms from the old computer under Labview
6.1 to the new computer with labview 8.6. However our program that worked fine with the 6.1 version is not working with the updated version (ver 8.6).
There
are 6 errors in the error list. It appears there are six files of my program missing under the new version, even though we transferred all files.
The software searches for those files but can't find them.
        For example one the box pops up indicates:
        loading:
                    <vlib>:\Daq\lvdaq.dll
        searching:
                    C:\Program Files\National Instrument\LabVIEW 8.6\instr.lib\Agilent34401\public\utility
        I get several message like this. I have to cancel/ignore them all to be able to open the program.
When we go to VI's under Measurement I/O there is nothing (empty).
We use a PCI-MIO-16XE-50 for our data acquisition During Labview installation on the new computer, I was asked if I wanted to install the device drivers. I had two options, "Now" or "Later", I picked Now but I didn't have the DVD's/CD's for the device drivers. Therefore I had to select later to complete my software installation Later after Labview 8.6 installation, we installed the device drivers (traditional Ni DAQ and Ni DAQmx) from the two old CD's we had in our lab from a couple of years ago (the CD's were Ni DAQ 7). after installation, the PCI board on the computer was recognized by the device driver. However we still could not run our program under the new version of Labview (same situation and the same messages) I called 1-866-275-6964 on 9/2/08 and talked to Grant (service number:
1228841). He recommended that I download and install the updated version of device drivers.
Since I didn't have the DVD/CD for updated device drivers, I contacted Vanessa Trujillo. She gave me the DVD for the updated Ni DAQ (Traditional and mx).
But
when I tried to install the updated device drivers I got a message something like "some unsupported filed have been detected,..." so the updated device
drivers were not installed. It should be noted that up to here we still had the Ni DAQ (traditional and mx) installed on the computer from our old CD's (Ni DAQ 7).
Vanessa and I talked to Tom at the technical support department. He recommended that we download and install the Beta xx version for Ni DAQ since we were using Windows Vista. Mike put the Beta software on the Ni website/outgoing so I could download and install it. He asked me to uninstall the traditional Ni DAQ that we had on our computer from the older CD's. He
asked me not to un-install the Ni DAQmx (that we had installed from the old
CD). I was able to download the Beta software, however I could not install it since I got a similar message that some unsupported files were detected.
Right now we don't have any version of traditional Ni DAQ installed on the
computer but the NI DAQmx (from old Ni DAQ 7) is still installed on the computer. Vanessa let me borrow her new Ni DAQ DVD but as I explained I am not able to install the device drivers.
Vanessa - Did I miss anything?
Please advise. My cell number is 619-778-2033. I will be at our lab at UC,
Irvine at 2:00pm (CA/Pacific time). Please call if you have any questions.
Thank you

To me, it looks like you are missing some of the drivers and subVI's used in your program.
Whatever device you are using to measure fatigue or any other device probably came with a driver.
You need all of these drivers installed on this new computer.
Also, any subVI's and libraries you use in the program must also be installed on the new computer.
Whenever you get a message that says you are missing some component (the ones that you said you press 'ignore'),
see if you can find that library or subVI on the older computer. If so, save it to something so you can transfer them to the new computer.
Cory K

ERROR: Excel 97, LabVIEW 7.1 and Windows XP

Hi,
I began this discussion on another forum but I was mistaken in forum.
http://forums.ni.com/ni/board/message?board.id=4170&message.id=4919#M4919
I cannot continue my development. Christophe S. sent VIs to me which work but I do not manage to open my own Excel file. As soon as I add a node of property or method not present in his VIs, I have the same error again.
I need to open an Excel file already filled. I must modify the value of cells and the name of the various sheets of the workbook. I must also launch macros. I already did all that at a customer with Excel 2000 under Windows98 and Windows2000 but my program does not work with Excel97.
I practically tested all the examples codes and took all the advice of the site NI on this subject but they do not work even if they must work with Excel97. I thought that perhaps it was because of the pack 2 of Windows XP but on a PC with the pack 1, I have the same result. I should pass soon on Excel2003 but I do not know yet when and I cannot stop my développment for that.
Did somebody already encounter this problem? If so, how did you solve it? Thanks.

In this moment, I am overloaded of work and I did not have time to carry out the tests which Chritophe S proposed to me. On one PC, I had Office 97 but also Word2000 and Works2000. It is possible that LabVIEW saw only ActiveX control 2000 and not 97. From where my problems with Excel97. I must uninstalle all that is 2000 and to remake a test with Office97.
I think that it will be difficult even impossible to develop VIs compatible with all the Excel versions. When you call a node of property or a node of method, LabVIEW "looks at" which version of Excel is installed on the PC and, if the test required by Christophe S. is conclusive, that means that it would take into account only most recent ActiveX controls.
If you create your VIx on PC having each one a version of Excel then that you recover on each one the program and that you finds a solution to see the version of ActiveX controls installed, you can perhaps develop your program. But is this really useful? On the forum, we can find examples for each version. Nobody use all version in same time (more exactly of the very different versions unit).
I think that it is better to develop a new program for each version.
Rmq: it can perhaps exist various versions of ActiveX control for the same version of Excel. You see that your program can quickly become painful to keep up to date.
I don't know if there are the same ActiveX problems with another programming language. So not, you can develop a DLL with another programming language and calls it under LabVIEW, if you want to really develop your "universal" VIs.
I did not understand which complete documentation you sought. On "Excel and its ActiveX controls" or on "LabVIEW and Excel"?
Good luck

Web server log files under LabVIEW RT

Hello,
Is there any log files for the web server under LabVIEW RT running on a PXI? The log file checkbox is disable in the target options.
Also, is there a way to find out if the web server is running on the target?
I'm asking the question because I can't access anymore a remote panel (and even the root of the web server) on my PXI. I reinstall everything and I still have the issue. I'm pretty sure that IT changes some network settings but they say no. I need to validate that everything is working on my side before before taking further action.
Thanks,
Patrick

Hi Patrick,
I would suggest having the log file checkbox enabled in the target options. That should show if errors are occurring while it is running. Are you running remote front panels and web services, or just remote front panels?
Can you provide a picture of all the software you have installed on your PXI? You should be able to find this in MAX under the PXI in Remote Systems.
Scott A
SSP Product Manager
National Instruments

Controlling the agilent 89441A under Labview

I am trying to communicate with our 89441A Vector Signal Analyzer via GPIB under Labview 7.1. I downloaded the intstrument driver (v1.2) from the National Instruments website.
The application example works fine. But this example uses the instrument mode "vector", and I'd like to use the "scalar" mode. When I change the instrument mode, the returned data is unexpected. The shape of the plot doesn't change, but the X-data (frequency bins) are in the range -7kHz to +43kHz, were I expected 0..+50kHz. The analyzer displays 0..50kHz on the screen, but the plot on the computer is shifted 7kHz to the left!
I have no clue on where to look: Is it a driver bug, an instrument bug, or am I doing something wrong? Please help me out here... Anyone experience with this issue? Does anyone at all have experience with controlling the 89441A?

Yes, I have looked at the programmers manual (I even have a hardcopy ), but unfortunately that didn't bring me any further.
I'm afraid not so many people have a 89441A, but if anyone has one, please let me know is you have any experience with remote controlling.

Pass a value to a dll under labview

I have to build a dll under cvi and use it under labview. my problem is to pass a value to this dll from labview.
But when I use it, labview return an error code and close the software...
I can return value from the dll to labwiew but not the contrary. can you help me please.
I am a beginner and I am sorry for my english..."
don't think it's a calling convention beceause When I use the box "call a dll" in labview and I select my dll, I can see all functions I have create in the dll (just the extern functions). for the datatype, I use int or unsigned int and sometimes char. and I can receive this value in labwiew...
but for the pointer that's certainly my problem
this is the sourcecode of my function. I drive a digital
to analogue converter and I want to select the exit (There is 4 exit 0x00,01,10,11 )and a voltage (0 to 255 in décimal):
void __stdcall dac_sortie_tension (int sortie, int tension)
outp(LPT1+0x000,4); /* not important*/
outp(LPT1+0x400,sortie);
outp(LPT1+0x000,2); /* ecriture de l'adresse2*/
outp(LPT1+0x400,0x00); /* not important*/
outp(LPT1+0x000,3); /* not important*/
outp(LPT1+0x400,tension);/*write voltage*/
if I use a constant to "sortie" & "tension" it's OK...
I try to use this:
void __stdcall dac_sortie_tension (int *sortie, int *tension)
but it's the same..."
when I select the fonction in labview, I can see them
but there isn't argument' ("sortie" & "tension") and I have a void like this:
void fonction (void)
what is the problem..
I can give argument to the function but there aren't used..."

/*draven*/;
You need to configure the function manually. Once you select the dll and select the function, select the button Add a Parameter After. You can change the name of the parameter to sortie, keep the Data Type as long and then change the Pass field to Pointer to Value. Click again the Add a Parameter After button and do the same for the your variable "tension".
For more information about calling external code in LabVIEW, refer to the following document (which should be also included with LabVIEW):
Using External Code in LabVIEW
Instructions on-line are here:
An Overview of Accessing DLLs or Shared Libraries from LabVIEW
Check also examples here:
Communicating with External Applications
Regards;
Enrique Vargas
www.visecurity.com
www.vartortech.com

Modify extension of txt file under labview

I've got a.log file or .txt file than i copy in new directory and i would like to use this file under excel, but I don't know how can i change the extension under Labview???
I hope than you understand me.
Thank you,

drikc,
avoid asking several time (3 !!!) the same question on this forum !
tst,
your previous icon was a disaster, but this one is even worse !..
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...

Bug in Formula node under LabVIEW 2010

appendix is my test project.
there is a test.vi in the project. The test.vi contains only a case structure with 5 SAME subdiagrams. Each subdiagram contains a formula mode. The formula code does some calculation with an 2d array of double.
If i run the test.vi under LabVIEW 2010(or SP1), it may cause LabVIEW 2010 corrupt occasionally. If I build application form the test.vi, and run the application ,the application will definitely corrupt.
if I delete one subdiagram of the case structure , the test.vi and the application both run well.
however, the same project works well under LabVIEW 2009.
so is it a bug with LabVIEW 2010?
Attachments:
Test.zip ‏7 KB

'corrupt' means the program exit unexpectedly without any warning or error message. it just disappeared and you can't find it in the 'process' tab of windows task manager after that.
If LabVIEW corrupted, once i reopened it, there may be a error message dialog pop-uped before the LabVIEW interface appeared. The dialog said something wrong with 'undo.cpp'. I zipped the failure long to the appendix. I can't find any other error or warning message from LabVIEW or Windows ( I checked the Windows Event Viewer).
If the built exe corrupted, There isn't any message for LabVIEW or Windows neither.
I tested the project on my own laptop with Windows XP(SP3) Chinese Version and NI PXI-8810 with Windows XP(SP3) English Version which is my target machine.
Appendix also contain a exe build in my laptop. If I run the exe file, once I click the run button , it will corrupt. I wonder if it works the same on your computer.
Thanks for your concern.
Attachments:
lvlog2011-05-13-23-23-35.zip ‏150 KB

LabVIEW NXT toolkit and Vista

Hi All,
This is not a burning problem, but have folks tried out the NXT toolkit with Vista? I've installed Vista Business Edition under our MSDNAA license on a development machine to start slogging through compatability issues with our current suite of software, and it appears the LabVIEW NXT toolkit may be an early casualty.
The toolkit installs fine under Vista BusEd, but the NXT console application crashes when I try to run it from the LabVIEW IDE menu.
Any thoughts/experiences with this?
Best regards,
-Bill =]

Hi Joel,
Thanks for your reply. The specifics of my development system are below:
OS: Windows Vista Business
Proc: Intel Pentium 4 CPU 2.80 GHZ
RAM: 1014 MB
Type: 32-bit OS
I chose to use the Vista UPGRADE of WinXPsp2 rather than a wipe and clean install. Before upgrading the OS I removed all previous versions of LabVIEW (7.1 and 8.0) and also removed the Mindstorms NXT-G system.
After the OS upgrade to 32-bit VistaBusEd, I installed LabVIEW 8.20, then Mindstorms NXT-G, several LabVIEW Toolkits and finally the LabVIEW NXT Toolkit.
When I try to load LabVIEW code that uses (for example) the sendDirectCommand.vi from the FantomSDK, I get the following block diagram error:
"Call Library Function Node 'fantom.dll:nFANTOM100_iNXT_sendDirectCommand': function not found in library
Details: The function name specified for this node cannot be found in the library. Right-click the Call Library Function node and select Configure, then choose the correct function name.
When I follow the Details procedure, I specify the exact location of the fantom.dll, select nFANTOM100_iNXT_sendDirectCommand from the Function name dropdown listbox, the Thread is set to Reentrant and the Calling convention is set to "C".........after closing the dialog I get:
Error loading "C:\.....path.....\fantom.dll".
A dynamic link library (DLL) initialization routine failed.
Also, when I create a blank vi and drop a function from the LabVIEW NXT toolkit, such as NXTToolkit.DC.FindNXT.vi on the block diagram, I imediately get the following similar error:
Error loading "fantom.dll".
A dynamic line library (DLL) initialization routine failed.
Does this help?
Many thanks,
-Bill =]
p.s. - BTW, the Minstorms NXT-G system works as expected under the 32-bit VistaBusEd using both USB and Bluetooth.....so I guess VistaBusEd is able to intialize and communicate through the fantom.dll when used by NXT-G.
Message Edited by qswitch on 12-19-2006 08:36 AM

How to open Excel Template save it under a different name and then write and save data to it at regualar intervals

I have an excel template that I have created. I am opening that template, saving it under a different name, and then writing and saving data to that excel sheet at regular intervals. It is giving me an error 5, I understand what this means and I am trying to work around it. However after too many hours spent trying to figure it out, I have asked for any help or input. I have attached an example vi, not the actual one since it is very involved.
Thanks
Solved!
Go to Solution.
Attachments:
Power Cycle Test 3.0 Excel Save Testing.vi ‏18 KB

This snippet encapsulates most of the previous suggestions, and adds a few of my own.
The first code shows one (simplified) way of building the output file name. It incorporates the Build Path function to combine Report File Path with the file name (don't need initial "\"), builds the File Name with Format into String, getting the Time part of the name from Format Date/Time String. I also use Build Path to get the Template path. Inside the For Loop, another Format into String gets the data that is placed in the 10 Excel cells. We don't write anything yet -- we're only filling in the cells in the WorkSheet (think of how you use Excel -- you could, but probably don't, save the WorkBook after every cell entry, you wait until you are all done and then do a Save, followed by closing Excel). Finally, when we are done, we save the file using the output name we want to use, then close Excel (which disposes of the Report Object). If we want to generate another report, with another (time-based) name, we can put this code into a sub-VI and simply call it again.
Don't worry if you don't have LabVIEW 2014 (which was used to save this snippet) -- most of the code comes from the original that you posted, so it should be a pretty simple edit to change that code to match this.
Bob Schor

LabView 5.1 and MS Access

Is there a simple way to communicate with MS Access Database under Labview.
I tried sample code found in the package but DDE is note very good and
require Access to run behind.
I also tried putting some DAO object (ADO+DBGRID using activeX object)
but not found the way to access object property such as recordsource,tablename, ...
Note : I'm a newbie with labview i'm a bit confused with the graphical language

In article <[email protected]>,
"y.leroux" wrote:
>
> Is there a simple way to communicate with MS Access Database under
Labview.
>
Hi,
yes, there is. Try our DAO toolkit (demo at www.xon.de), which is a
high-level-interface for the jet-engine.
Peter
Sent via Deja.com http://www.deja.com/
Before you buy.

What is a quick alternative to launching an enterprise DPS app if Apple Store rejects the App? We are under a major deadline and can't wait for Apple. We want to host the app elsewhere. How do we host our DPS app on our client's website?

What is a quick alternative to launching an enterprise DPS app if Apple Store rejects the App? We are under a major deadline and can't wait for Apple to approve. We want to host the app elsewhere. How do we host our DPS app on our client's website? Thanks.

Unless I misunderstand the question, you can't do what you're asking to do. Apple doesn't allow you to bypass their store and host public apps on a website. The exception is an enterprise app, which requires an Enterprise account with both Apple and Adobe. This type of enterprise app can be distributed only within the company. If that's what you want to do, you can learn more here:
Digital Publishing Suite Help | Creating viewer apps for private distribution
Distributing enterprise iOS viewer applications with Digital Publishing Suite | Adobe Developer Connection
Another option is to add the development app to several devices and use those for your demo.

Title Bar stuck under the Menu bar and I cannot select and move it.

I often arrange windows around the desktop and sometimes I inadvertently push a window up too far and the title bar gets under the menu bar. Once I let go of the arrow, the title bar is too far under the menu bar and I can no longer reach it to move it down. The only solution is to close out the program and start over. Is there a way unbeknownst to me to select the title bar again and move it?
Sharon

My E*Trade streaming watch list was stuck under the Menu Bar also. I tried reseting the screen resolution down to 1280 x 1024, and restarting the MarketTrader. There on the display was the stuck window, out from under. I resized and moved it to a central location, and resized the display back to my normal 1920 setting. And to my relief, the window Bar! Thanks Discussion!

I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008.

I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008. I have selected system target file as nidll.tlc,make command as make_rtw and template nidll_vs.tmf. When I try to generate .dll file I get the following error.
Attachments:
SITProblem.JPG ‏101 KB

Hi,
No . I could not solve the issue. Presently we are using microautobox (from Dspace)for doing the RCP.
Himadri

Scilab Gateway under Labview 8.2 and 8.5

Similar Messages

Maybe you are looking for