Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in order to leave a comment Create Can you have negative sets? Philip_Courtois Active Participant 10-14-2004 07:58 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator There are two things you This is the error Code 1172: Error creating instance of SSPParameter in assembly SPCSDK.Protocols.SSP.SSPParameter, SPCSDK.SSP, Version=220.127.116.11927, Culture=neutral, PublicKeyToken=null, (SPCSDK.Util.Error.InvalidInputParameter: Invalid input parameter(s).)
Sign In Now Sign in to follow this Followers 1 Go To Topic Listing Calling External Code All Activity Home Software & Hardware Discussions LabVIEW (By Category) Calling External Code .NET It's easy! Other considerations for calling a .NET Assembly from LabVIEW are: Private assemblies must be placed in the same directory as the calling application. Our merchants keep turning into villains! http://digital.ni.com/public.nsf/allkb/B15CE9F2715434C386256D3500601878
If you need more information I will provide it ASAP - but there will probably be about a one-day delay, because I have to forward the questions to the team in If building an application, make sure to include the assembly in the build. The first VI in the image does NOT close all the .NET references properly because the parameters output is null. I could see all the properties, but when I ran the VI, I got Error 1172(see the attachment)My 2nd idea was to use a Constructor (for the object I wanted), then
It's easy! Everytime I try this I get an error in the build process, error 1172. Thanks, PC1 vs PC2.JPG 75 KB 0 Kudos Message 4 of 5 (644 Views) Reply 0 Kudos Re: Error Code 1172 Constructor Node Mojito Member 10-30-2014 09:49 AM Options Mark as The primary channel of communication from LabView/PC to the test fixture is via good old-fashioned printer port. (We toggle lines high and low on the printer port to send commands to
My first thoughts with Asian-only issues are the problems (and Labviews issues) with Unicode string handling. System.ArgumentNullException: Key cannot be null. 00000015 114.37963104  Parameter name: key 00000016 114.37963104  at System.Collections.Hashtable.get_Item(Object key) 00000017 114.37963104  at NationalInstruments.LabVIEW.SyncInvokeTable.LookupControl(Object key) 00000018 114.37963104  at NationalInstruments.LabVIEW.DNRuntime.InvokeMethod(Int32 invokeType, Type type, My primary guess is the latter. But when the developers in China tried to call the DLL they get the error.
The C# programmer tested the DLL pretty thoroughly, including downloading LabView 2011 and making sure LabView could call the DLL. ADDQ VIPM"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones." 1 Kudo Message 5 of 7 (1,269 Views) One method (called numberToNumber) has a input type double, and a double output. Share a link to this question via email, Google+, Twitter, or Facebook.
Share this post Link to post Share on other sites vugie 153 Extremely Active Members 153 388 posts Location:Warsaw, Poland Version:LabVIEW 2009 Since:2006 Posted May 27, 2011 Another common international Sign In Sign Up Browse Back Browse Forums Downloads Gallery Staff Online Users Activity Back Activity All Activity My Activity Streams Unread Content Content I Started Search Jump to content Calling This is a great forum. How to professionally handle sexist remarks by a student?
Lycangeek Active Participant 08-09-2007 12:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator How exactly are you increasing this contact form Other than what Nathan suggested, you can also ask the .NET dev to add logging to the constructor and the CreateUN8 method and add your own logging to the code (try The project comprising of one labview class. Then I try to build the project again, including this new method in the build source.
Do any of you have other suggestions to avoid getting Error 1172? PJM Share this post Link to post Share on other sites Clinto 0 LAVA groupie Members 0 5 posts Version:LabVIEW 2010 Since:2009 Posted May 28, 2011 Not exactly what you Register a new account Sign in Already have an account? http://robertwindows.com/labview-error/labview-error-1172-net.html Do you need to constantly obtain and destroy a new reference to the same named notifier?
It contains a .NET control (version 3.5) on one of my front panels. I'm assuming that the reason is that either the names there are localized (although I wouldn't expect them to be for something like this) or that they're using characters which are But what I don't understand is why the file can't be found (Le fichier spécifié est introuvable) since all the .DLLs that are needed are in the same directory.
I really have my fingers crossed that this forum can help us solve this problem. This assembly needs to be placed in the same folder as the calling application. By default, when a.NET program is compiled, the assembly produced will be a private assembly. Then I wrote a new function that wrote to a file and called that when the VI loaded.
I realize that this is probably not an option at that stage, but I though that I would mention it. I attached an error indicator to the invoke node, which is showing me this error: Error calling method InstrumentDataGridView.InstrumentDataGridView.LabVIEW_FillTableFromXML, (System.ArgumentNullException: Key cannot be null.Parameter name: key)
Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign in with LinkedIn Sign Up All Content All Content This Topic This Forum Advanced Unfortunately, LabView and the DLL don't seem to want to talk to each other. Click theAddbutton and navigate to the location of all the assemblies that you want to call. I would like to build a labview project into a .net assembly.
As soon as I receive their answer, I will post it here. All rights reserved. | United States MY ACCOUNT   INNOVATIONS SHOP SUPPORT COMMUNITY Home Community Home : Discussion Forums : Most Active Software Boards : LabVIEW : Why am I getting I will forward your questions/comments to the engineers in China. You can start by using probes to see exactly where the error comes from (it says "creating", so it's probably the constructor).
Tst, I have added the logging on the LabVIEW side with the"+.NET Error Info" VI. And responses come back via lines being toggled high and low.) But the DLL is written to communicate with the board under test via a second communication channel. Register a new account Sign in Already have an account? Thanks in advance for any help.