Error -70217 Comunicación LabView - SolidWorks

Estoy tratando de hacer un proyecto que involuctra solidworks y labview, el diagrama a bloques ya está hecho y cuando le doy correr uno de los bloques que corresponden a ejes me lanza el error 70217
Ya he intentado varias soluciones como borrar el eje desde my computer y poner otro, he verificado que los ejes esten activos, que el NI Engine se active con la función deploy
alguna ayuda?

Saludos majo_90,
Gracias por utilizar los Foros de Discusión de National Instruments, he dejado una respuesta en los otros dos posts que creaste:
SolidWorks.LabView error 70217:
http://forums.ni.com/t5/LabVIEW/SolidWorks-LabView-error-70217/m-p/3146893/thread-id/906055/highligh...
Comunicación LabView - SolidWorks:
http://forums.ni.com/t5/Discusiones-sobre-Productos-NI/Comunicaci%C3%B3n-LabView-SolidWorks/m-p/3146...
Por favor procura no abrir dos post para la misma consulta, saludos cordiales.
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

Similar Messages

SolidWorks.LabView error 70217

Hi!
I´m trying to make a project witch solidworks and Labview, the problem is that when im run the VI, appears a message with the error
70217
I´ve tried to add nes axis, the scan engine runs and the simulation in solid works runs too hte problem is in the blocks diagramm
could you help me please?? It´s a very importante work

Hello majo_90,
Have you tried the steps mentioned in the following forum post?
Error -70217 when trying to run NI SoftMotion/SolidWorks:
http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/Error-70217-when-trying-to-run-NI-SoftMotion...
Best regards.
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

Error -77080 LabVIEW- Solidworks

Hi there.
I'm having some trouble connecting LabVIEW Solidwork some inexplicable because I have not changed anything and now the Start Simulation give me the following error message:
Not I find the reason.....
Es un placer echar una mano siempre( Base de una sana convivencia). Si mi respuesta te sirve por favor agradecemelo con un Kudo
Un especial saludo a mis hermanos latinos. Un mundo mejor es posible.

Hola ingenieromecatronico,
Cuando le suceda este error. Guarde todo. Cierre todos los softwares y repita los pasos en el orden correcto. Comente si le funcionó.
Saludos.
Es un placer echar una mano siempre( Base de una sana convivencia). Si mi respuesta te sirve por favor agradecemelo con un Kudo
Un especial saludo a mis hermanos latinos. Un mundo mejor es posible.

Linker.cpp error @ line 2075 w/Labview 6.0.2 and Appl. Builder

So frustrating! The libraries run in the debugging environment just fine. No errors and two minor warnings. I have to constantly tweak and upgrade these libraries because each has about 40 VIs and are rebuilt on average two times a week. The executables are used at a dozen places and I can't place the developer system on each computer, that is what the Builder and the Labview runtime engine is for.
About a month ago after doing very minor changes in one VI I rebuilt the library into an executable using the same build file and BANG, I get this linker error. After acknowledging Labview disappears (stealth crash). Well eventually I figured I had to copy the diagram of the VI I had changed (yes, complete with changes) to another blank VI. After deleting the old VI and renaming the new (it used to be blank) VI, I rebuilt it. Everything was fine.
Well I have tried to rebuild frequently after each change and save often several copies back a month but somehow this has been futile as the error is back in both libraries. In the two libraries I maintain there are as many as 20 VIs identical between the two libraries. I make a change in one VI in one of the libraries then use the library manager to copy it to the other library. This has worked hundreds of times over the last year and half. Well somehow the problem has come back in both libraries and I can't isolate the bad VI.
Obviously one (or maybe more!) of the VIs are put together wrong but Labview doesn't detect it. I don't use any fancy linking to anything other than DAQ and SERP drivers, everything else are simple VIs (just Labview code) with only the Labview supplied VIs talking to DLLs. I have tried my little cut and paste trick with the last few changed VIs but it didn't work. I tried to use Application Builder to build VIs seperately but that was useless. I tried elminating the lastest changed VIs from the library and rebuilding but to no avail. It fails approximately 1/4 to 1/3 into the build process bar indicator but the Builder doesn't say what file it is building so I can't relate it to any specific VI. Tried relating the bar position to a latest changed list and an alphabetical list but that was inconclusive.
This issue is currently being worked on by NI support but I want to try the resources of the developer community because this is such a rare problem with big implications (at least to me).

OK, NI support came through! If the library is mass compiled the typedef in my controls won't mess with the linker. Labview 6.1 solves this problem.
Since my email to NI support got returned I'm not sure they received it. The message is: it worked and thanks.

Error 1706 when installing LabVIEW 7.1

Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob

Robert_Deschambault wrote:
Hi,
When installing the device drivers that come with LabVIEW 7.1, near the end of the installation I get the following error message:
Error 1706: No valid source could be found for product LabVIEW 6.0.2. The Windows installer cannot continue. Continue?
The installer completes after this but says that the installation has failed. Any suggestions? Thanks.
Bob
Hello Robert,
You can find out more information about this error at the following post.
what does Error 1706 mean during LabView 6.1 installation
This error is not specific to the install of LabVIEW but with the upgrade of the IMAQ device driver.
Please let me know if you have any other questions
Regards,
Matt F
Keep up to date on the latest PXI news at twitter.com/pxi

Error number 7 when LabView tries to open file

I get the following error when LabView tries to open a file -
" Error 7 occoured at Open File+.vipen File.
Possible reasons:
Labview: File not Found .
or
NI-488: Non-existent board.
Having searched through the archives here the error usually occurs when LabView cannot find the file. Well this time i know the file is there, i have even used the 'read from spreadsheet file' vi with the dialog box option to show LabView where the file is. When i copy just the open file code into another (blank) vi it runs correctly but in the middle of all my other code it kicks up this error. I ahve had the code working no problem before so this problem has just arose over the past week. Very frustrating.
Any help appreciat
ed

Hi,
You need to check the full path that you are passing to the Open File+.vi. Make sure that if you are deriving the file from say the file constants such as the Current VI's Path, that if the VI is contained in a LLB, then this will be in the path name. eg ..\myLib.llb\myActualVI.vi. Therefore, you will have to strip out the llb. Similarly, if you have built an exe file, the pathname will contain the myEXE.exe.
Hope this provides some pointers. If not then post your VI, so others can help pin point your problem.
Regards
Ray Farmer
Regards
Ray Farmer

-18001: An error occured accessing the LabVIEW ActiveX automation server

Hi,
I'm currently investigating a problem with a Teststand 2.0 sequence. The
sequence makes use of VI's that call methods of an ActiveX. After a few
successful loops through the test sequence the error "-18001: An error
occured accessing the LabVIEW (6.1) ActiveX automation server" is brought up
in Teststand. I think that somehow the ActiveX automation server is dying
during the execution of the sequence but I don't know where to start
searching...The problem does not seem to lie within the ActiveX istself, but
I'm not sure. Using the same ActiveX within a Visual Basic Application and
performing the same commands several times does not produce a failure. Has
anybody an idea what could be the problem
Thanks, Sven.

Thanks, but I already know these entries from the Knowledge Base. I found no
help in there and my error text is also not mentioned there.
JRA schrieb in im Newsbeitrag:
[email protected]..
> There is actually a few Knowledge Bases on NI's website which deals
> with this exact issue. You will probably want to start there.
> 1. >
"http://digital.ni.com/public.nsf/websearch/55574CB4E0F326DF862567FD0077E303
?OpenDocument">-18001
> ...
> 2. >
"http://digital.ni.com/public.nsf/websearch/D8690EC8044C7B3586256C63005D4D84
?OpenDocument">Why
> do ...

Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!

Hi,
I have been trying to simulate ODE but getting following error:
Error -23011 occurred at LabVIEW Analysis ODE Solver/inconsistency in dimensions of X(0), F and X!.
The screenshot of the code is attached.
Please let me know if anyone knows the reason of having this error.
Thank you.
-HB
Solved!
Go to Solution.
Attachments:
Screen Shot 2014-12-02 at 09.58.08.png ‏60 KB

Hi,
I have added another code which includes the "simple chemical reaction" which I am trying to model using ODE in LabVIEW, but I am continously having the same problem.
Kindly see the attachment and try to help me out solving this issue. I couldn't found this kind of error listed on NI forum.
Thank you.
Regards
Hasan
Attachments:
test_hb.vi ‏22 KB

Error -70217 when trying to run NI SoftMotion/SolidWorks

I'm trying to play with setting up NI SoftMotion and SolidWorks to control a very basic motion application. I am getting the above error when I click "execute." The example programs run fine, so I am faily confident I'm missing something really easy. The error is an NI Motion error indicating a required resource is in a fault state. Any suggestions?

Usually this is caused by a motion control command that caused the axis to go into a fault protection mode. Here are some debugging suggestions:
- Make sure the the SolidWorks Motion is active, navigate in SolidWorks to Tools->Add Ins and mark the check boxes on the left and the right of the SolidWorks Motion item.
- In the LabVIEW project, right-click on My Computer and got to Properties. Then go to the Scan Engine tab and make sure the box is checked next to Start Scan Engine on Deploy. You may also want to set the Scan Period to 10 ms if it's not already. If the value is above 5 ms, you'll get a warning message when you deploy but this is usually just fine for simulation with SolidWorks.
- Individually select each of the motion axes in your project and do the following: Select Properties and then click on the left-most button to configure the Axis Setup. Make sure the box is checked for Enable Drive on Transition to Active Mode.
- Now select all of the motion items (including My Computer) in the LabVIEW Project, right-click and select Deploy. Normally, since this is your first deployment it
will start the SolidWorks simulation running and so your are ready to
run the LabVIEW shipping example. If not, right-click on My Computer
and select Utilities>Scan Engine Mode>Switch to Active.
- Once you are in active mode and the simulation is running, right-click on the motion axis and go to the Interactive Test Panel. This should show you that the axis is enabled and there are no faults or errors. When you are finished, close the test panel and run your LabVIEW motion control application.

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

When I try to run a VI that is reentrant in parallel execution, I receive this error. The details of the error is: LabVIEW: The property or method is not supported in this version of LabVIEW.
This is run under the Simple Operator Interface in LV 2010. The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
Can anyone reproduce this error (bug?) ?
Solved!
Go to Solution.

have you got the latest updates for TestStand using LabVIEW 2010?
http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
Regards
Ray Farmer

Error 1722 when uninstalling Labview run-time engine 7.1.1

I have been trying to uninstall all NI software so I can start off with a clean slate. I have been going to the control panel under add/remove programs to remove the NI stuff. Everything is gone except the Labview run-time engine 7.1.1. Everytime i try to remove it, i get teh 1722 error followed by the 1603 error. I've tried repairing it but I still get the same results when i try to remove it agian. I've also tried removing it with MSI Blast. This did not work either. I've gone through the registry and manually deleted anything related to NI and that still didn't work. Is there anything else I could try?
Thanks,
Nick

Hey Steve,
I have tried repairing it through the control panel.
I tried reinstalling just the run-time engine and it said it was already installed. So I reinstalled Labview 7.1 and repaired the 7.1.1 run-time engine through the control panel. Then I uninstalled everything. Thanks for all your help
Thanks again,
Nick
Message Edited by Nick_C on 03-12-2007 03:57 PM

Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

Hi,
a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
(window title)
Microsoft Visual C++ Runtime library:
(message box text)
Runtime error!
Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
Do you know this behavior and do you have any ideas how the problem can be solved?
Thanks in advance.
Best regards
Manuel
Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
Solved!
Go to Solution.

Hi there
log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Error 6 while Building Labview Application OSX

Hello everyone,
I have an application I am trying to compile on OSX10.8 using Labview 2012. I built the application fine yesterday, however, after some work today I don't seem to be able to replicate the feat.
Everytime I try to build I receive the following error:
"Error copying files. Source: Macintosh HD:Applications:National Instruments:LabVIEW 2012:resource:lvanlys.framework Destination: Macintosh HD:tNIAB:appName.appupport:lvanlys.framework Delete in Copy From Folder To Folder.vi->Librarian Copy.vi->AB_Destination.lvclass:Copy_File.vi->AB_Source.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller<APPEND> Macintosh HD:tNIAB:appName.appupport:lvanlys.framework"
Anyone have any suggestions?

Nothing that should matter. I updated some logic in the VIs and added some OS dependent conditional disable structures. The project file has remained the same.
I think it might be a permissions error. Before this particular error, it randomly started giving me some errors when I tried to save things saying I didn't have permission to save certain things. So I attempted to fix all the permission mismatches with some good old chmod. And then it started giving this error.
It also does not appear to help to revert the code to the state it was in when it was first built. This leads me to beleive it is not something to do with the source code.

Error -70217 Comunicación LabView - SolidWorks

Similar Messages

Maybe you are looking for