3D Studio Model Control

Hi!
I'm a engineering student, and I need all kind or information like tutorials, exampes, links,etc about how can i control a 3d studio model with LabView . I'm pretty new with LabView, so all help you could give will be very helpfull. What i need to do is control a 3D studio model with several parameters, like aceleration, velocity, pressure and so on. The model is a tunnelling machine.
Thanks a lot!
Juan

This post is currently active under this link:
http://forums.ni.com/ni/board/message?board.id=6170&message.id=1927
SO use the other link for answers,
Please do not duplicate posts,
Regards,
Jaime Cabrera
NI Applications Engineering Spain

Similar Messages

Essbase Studio Model Availability Issue

Hi Essbase Studio Guru's,
My Essbase studio is on a different Linux server from the server where I'm running my Maxl script to execute deploy all command. Maxl fails as it is not able to find the essbase studio model. The server I'm running Maxl is a part of the epmsystems in our environment. Can anyone please let me know if there is a way or a setting which can make the essbase studio model available from any of the server in the epmsystems.
Thanks

Are you definitely sure that is not an issue with the syntax of the deploy command, are you saying the Maxl works when running it from the Essbase Studio Server?
Cheers
John
http://john-goodwin.blogspot.com/

Visual Studio Adding Controls to Full-Featured

I am trying to modify the Full-Featured GUI - the C++ Using MFC version- in Visual Studio 2010 but nothing I do to the resource file seems to "take".
I went through and added a TestStand ActiveX Listbox along with a standard button and listbox. While I can see my changes when I test the dialog box (see attached), when I actually run the application (either in VS 2010 or outside of it) it's like I didn't make a change at all (see attached).
Any ideas as to what's going on here?
Attachments:
UI_Running.gif ‏183 KB
UI_Test_Dialog.gif ‏65 KB

Nevermind. I got it.
I'm used to just placing the controls and running in in older versions of Visual Studio. VS 2010 is new to me so I figured I was doing something wrong. It took me a while to figure out that these GUI samples size/move the controls programatically.

Visual C++ 6.0 error with Measurement Studio ActiveX controls

Hi,
I'm triyng an evalutation version of Measurement Studio for VC++ 6.0 for my company.
I'm working on a single document application with a menu bar.
I have several dialog linked to the menu bar but, at run time, the application crash with memory leaks error.
This problem appear only if I attach a Measurement Studio controls on the dialog.
If I add a control on the main document this error don't appear.
Could you help me?
Is there some Measurement Studio patch solving my problem?
Thanks a lot
Federico Bettin
Applied Materials - Baccini spa

Thanks Lucius for your help but I'm not developing any software code!
.... I think this problem depends on the installation or the software version .... I think and I hope !
I'm very doubtful because I would like to buy the Measurement Studio for my company ..... obviously, before I have to solve this problem .......
Bye
Federico Bettin
Applied Materials - Baccini spa

Using Powershell Studio to control Hyper-v VMs and VHDs

Hello everyone! I'm kind of new to Powershell in general, and to Powershell Studio
alltogether.
I'm trying to use Powershell Studio to write a script (with a GUI) that behaves like
this:
Two Windows. On one side there's a window that shows me the list of VMs on my machine.
Once I click on one of them, the window on the right shows me the attached VHDs that VM has.
I can't figure out how to integrate the Get-VM command to display unto a window. I'd
be happy for any help anyone can offer. Cheers and Merry Christmas to all :D

Hi Noamatan,
I also recommend you can consult Sapien expert:
http://www.sapien.com/forums/viewforum.php?f=21
In addition, The Powershell Studio project below is for your reference, which build a drop downlist, then we can display the result by selecting the item in dropdown list:
Building GUI for PowerShell Scripts using PowerShell Studio 2012
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How can I use Measurement Studio components in SharpDevelop?

I tried to use NationalInstruments.UI.WindowsForms.Led in sharpdevelop (http://www.icsharpcode.net) and I got a message about the product not being licensed for use with this program. Is it possible to attain licensing for use with sharpdevelop or is Visual Studio .NET required?

SharpDevelop does not support the .NET Framework licensing model (particularly LicenseManager and LicenseContext), so unfortunately there is not a way to use licensed controls in the current version (0.99b) of the SharpDevelop Windows Forms designer.
Visual Studio .NET is the recommended environment for the Measurement Studio UI controls. Another option is Borland's C# Builder, which also has a Personal edition that is free for non-commercial development and can be downloaded from the C# Builder downloads page.
- Elton

Multi-authoring with source control with RH10 and RH11

Situation:
Writer A is running RH10. Writer A opens Project A, from Visual Studio Source Control, which is connected to a Team Foundation Server.
A new employee, Writer B, has been given RH11.
Writer A can't install RH11 until after mid-June because of tight schedules (can't afford any upgrade problems).
Writer B is supposed to work on the same Help project. (We know that RoboHelp does not support checking out the same file at the same time.)
If Writer B configures her version of RH11 to work with TFS and Source Control, can she open Project A and work on it (from Source Control) without causing problems for Writer A?
Thanks.
Carol Levine

If Writer B is not using Source Control or it is competely separate from Writer A, possibly but I still would not be comfortable.
I think I would rather upgrade Writer A and I note your reservations. It's your call but it's like being between the devil and the deep blue sea. Neither is ideal.
So far it looks like Rh11 upgrades have been OK.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

C:\Program Files (86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe Side by Side Error

I used the sxstrace tool to find the error but ill admit im not sure what im doing. If you can please help me identify whats wrong that would be great!
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = Wow32
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe
AssemblyDirectory = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\
Application Config File = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.Config
INFO: Parsing Application Config File C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.Config.
INFO: Parsing Manifest File C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe.
INFO: Manifest Definition Identity is WDExpress,processorArchitecture="X86",type="win32",version="1.0.0.0".
INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Reference: debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0"
INFO: Reference: Microsoft.VisualStudio.CompilerHostObjectsProxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0__6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Auto Servicing Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7601.17514".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.7601.17514_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0".
INFO: Resolving reference for ProcessorArchitecture WOW64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll\debuggerproxy.dll.DLL.
INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\debuggerproxy.dll\debuggerproxy.dll.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0".
ERROR: Activation Context generation failed.
End Activation Context Generation.

Hello,
I saw a related thread from here:
http://stackoverflow.com/questions/15130609/visual-studio-2012-side-by-side-configuration-is-incorrect
The dll in that thread is different from there but I think you can still try the solution listed there to repair your VS installation.
May I clarify some questions? Can you use Visual Studio before you get this error? Is it the first time you installed Visual Studio and when you try to open it it reports this error for you?
If you can use Visual Studio before you get this error, please try repair Visual Studio from control panel.
If you cannot use Visual Studio even when it is the first time to load, then it is a corrput installtion problem. Please remove the current installation:
http://support.microsoft.com/en-us/kb/2771441 Then download and verify the ISO:https://www.visualstudio.com/en-us/downloads/visual-studio-2013-iso-sha1-vs
And restart the installtion with a healthy ISO.
Anyway, in my mind refer to the first stackoverflow thread and repair the installtion to fix this missing dll problem is more reasonable.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Measurement Studio Visual C++ 6.0 Multithreads

I want to use the dialog editor to add NI controls to a dialog (or CFormView) and want to set CNiInterface to SingleThreaded. How do I do this. I do not want to create the controls dynamically because I do not want to deal with license strings. I get an error if I close the dialog box when a control is added with the dialog editor. Is this because the controls by default are created as multithreaded with caching? I get by this by calling destroy window on the control. Is this the proper way? Will I have to do this if I use singlethreaded?
Next the documentation says I need to initialize COM. Is this true. Is it not enough to call
AfxEnableControlContainer() in OnInitInstance of my application.
By the way
National Instruments, Your documentation leaves quit a bit to be desired!! Good grief.

The default thread access for the Measurement Studio C++ controls is CNiInterface::MultipleThreadsWithCaching. You do not have to dynamically create the control if you want to create the control with CNiInterface:ingleThread - just specify it in the dialog class constructor's member initialization list. For example, if you had a dialog class called CTestDialog and you had a member variable for the graph in the dialog class called m_graph:
CTestDialog::CTestDialog(CWnd* pParent /*=NULL*/)
: CDialog(CTestDialog::IDD, pParent), m_graph(CNiInterface:ingleThread)
Also, you should not need to initialize COM to use the controls in a dialog. The call to AfxEnableControlContainer in your InitInstance method should be sufficient.
- Elton

Coding error using measurement studio

hello..
can somebody tell me where can i get help on coding the measurement studio using VB.i'm doing an interface programing with a dc servo motor.i'm using a fuzzy logic controller(FLC) to make the output of the servomotor to follow the input, which i'm using a square wave input.i'm having coding problems on linking the FLC with the harware.i'm not quite good in visual basic, so can anybody help me with the coding?i can send the vb coding of the FLC and the hardware interface coding. i've successfully implement PID controller.. but i can't seem to make the FLC work. i think there's something wrong with the coding.
and how can i make the graph go more faster? output from the graph is very slow, compared if i probe the output from the servomotor harware using a digital oscilloscope.

Hi,
I recommend the Measurement Studio Reference as a resource. This reference is installed with Measurement Studio and can be found on your computer from Start>>Programs>>National Instruments>>Measurement Studio>>Help. The Measurement Studio Reference includes information on the Measurement Studio ActiveX controls and tutorials.
Next, is the FLC you are using part of a Measurement Studio Add On? Are you using the PID Toolset for VB?
Then, if the graph you are using is a CWGraph, you can access the properties of the graph by right-clicking and selecting Properties…. Click on the Graph Tab of the Property Pages window and check that Control Refresh is set to Immediate. This has the graph redrawn as soon as new data is available.
Regards,
Eric M

Getting Warning while assigning Dimension in to Model in version 10.0

Hi,
Iam getting an warning message "Control definition not valid because new Dimension are added in to Model" & "Control result was reset because new Dimension are added in to Model" while assigning Dimensions to the Model.
Please help me on this issue. Screenshot attached.
Regards,
Sudheer

Hi,
Controls might exist on this model.
To check for the existing Controls.Goto Aministartion-->Rules -->Controls . After you adding the new dimension you have to revisit the controls which were already existing.
Thanks,
Raju

Which ports are needed for SAP HANA Studio - HANA DB communication?

I want to connect SAP HANA Studio to a HANA instance. The HANA instance number is 40.
The SAP note 1592925 states that the ports 5$$13/5$$14 and 3$$15 should be open to allow communication between the HANA Studio and the HANA database. I even see the instance in the HANA Studio, but I cannot administrate it and the HANA studio gives this general "I don't want you to know what the error actually is" message:
!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-16 14:01:40.627
!MESSAGE [HDB hostname 40 (SYSTEM)] Error on refreshing system
!SUBENTRY 1 com.sap.ndb.studio.navigator 4 0 2012-01-16 14:01:40.627
!MESSAGE SAPControl request failed
!STACK 0
com.sap.ndb.studio.sapcontrol.SAPControlException: SAPControl request failed
     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:118)
     at com.sap.ndb.studio.sapcontrol.SAPControl.getInstanceProperties(SAPControl.java:439)
     at com.sap.ndb.studio.sapcontrol.SAPControl.collectProperties(SAPControl.java:466)
     at com.sap.ndb.studio.sapcontrol.SAPControl.open(SAPControl.java:297)
     at com.sap.ndb.studio.sapcontrol.SAPControlManager.getSAPControl(SAPControlManager.java:108)
     at com.sap.ndb.studio.sapcontrol.SAPControlManager.getSAPControl(SAPControlManager.java:81)
     at com.sap.ndb.studio.sapcontrol.SAPControlManager.needCredentials(SAPControlManager.java:57)
     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTrySAPControl(SAPSystemObjectUpdate.java:102)
     at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:63)
     at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:75)
     at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:67)
     at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)
     at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:94)
     ... 11 more
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
     at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)
     ... 13 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.SocksSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at sun.net.NetworkClient.doConnect(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.http.HttpClient.openServer(Unknown Source)
     at sun.net.www.http.HttpClient.<init>(Unknown Source)
     at sun.net.www.http.HttpClient.New(Unknown Source)
     at sun.net.www.http.HttpClient.New(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
     ... 14 more
Do I need to open any other ports to make HANA Studio work with HANA DB?
Regards,
Mark

Hi Mark,
The HANA Studio connects to HANA DB Instance with JDBC on port 3<Instance number>15.
For your HDB with Instance Number 40, the port would be 34015.
HANA Studio will automatically assign the JDBC port number when you assign the instance number when you add new system.
Looking at the error message that you posted:
!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-16 14:01:40.627
!MESSAGE [HDB hostname 40 (SYSTEM)] Error on refreshing system
It looks like the hostname entry was not entered correctly (you might have entered "hostname" value when adding the system in HANA Studio).
Here is an example of correct log entry on DCA database instance on hanasvr-01 server with Instance number 00:
!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-10 13:55:23.598
!MESSAGE [DCA hanasvr-01 00 (SYSTEM)]
You may want to delete and re-add your HDB instance in your HANA Studio.
Regards,
Ferry

Tree Grid Control

to show hierarchical list data we want to use a tree grid control like RadControl from Telerik (which is to slow for our needs)
after looking for alternatives we found something like
ezzylearning-asp-net-gridview-control. Ok, but we need collapse and expand functionality for our list data which are held in list folders.
better use JavaScript / AngularJS ?
Any advices which product to use or what s the best practise to simply build an asp grid control with expand / collapse feature?

Hi,
Based on the information you provided, you problem was related to Visual Studio TreeView control, so I recommend you to post this thread to Visual Studio Forums:
http://social.msdn.microsoft.com/Forums/en-US/category/visualstudio
Tthere are many experts focus on it, who can make a quick response to your question.
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Control's property pages at runtime???

I am currently implementing an ActiveX control with Measurement Studio for Visual Basic.
Everything is going fine, but I have one general problem which I cannot solve. The control should show the own property pages at runtime mode. Whit one OLE control, developed under visual c++ or ATL this is strength forward. But I have no idea how to do this from Visual Basic. I spend a lot of time to search in internet but unfortunately there is no information at all.
Please HELP!
Thanks in advance!
Nikolai

You can do this with the ISpecifyPropertyPages COM interface and the OleCreatePropertyFrame function. The hard part is getting definitions of the interface, interface methods, supporting data types, etc. that you can use from VB. Here's one way to do it:
Download tl_ole.zip, which is a type library that contains definitions for several OLE interfaces, structures, and functions.
Create a new VB project and add a reference to the type library.
Add a Measurem
ent Studio ActiveX control (i.e., CWGraph) to the form and add a button to the form.
Add the following code to your VB project:
Private Sub Command1_Click()
ShowPropertyPages CWGraph1.Object, "Graph", Me.hWnd
End Sub
Public Sub ShowPropertyPages(comObject As Object, name As String, hWnd As Long)
Dim specifyPages As ISpecifyPropertyPages
Set specifyPages = comObject
If Not specifyPages Is Nothing Then
Dim pages As CAUUID
specifyPages.GetPages pages
OleCreatePropertyFrame hWnd, 0, 0, name, 1, comObject, pages.cElems, ByVal pages.pElems, 0, 0, 0
CoTaskMemFree pages.pElems
End If
End Sub
Note that you pass in the Object property of the control, not the control reference itself. When you run this code, this will bring up the property pages of the controls at run-time. If you make any changes in the property pages and click OK, the changes will be reflected in the control.
Hop
e this helps.
- Elton

Creating CWDIO controls programmatically

I have two test fixtures that have different devices on them but I want to transfer my code back and forth when I can. Fixture A has a device 5 and fixture B doesn't. Once I use the property pages to set up the CWDIO control and give it a member variable all the calls to that member varaible work great. If the member variable is m_dio then m_dio.SetDevice(3) for example works great.
What I want to do though is only have device 5 on one station so I don't have to delete the control when I go from Fixture A to Fixture B. Right now I just change my #define FIXA to #define FIXB and recompile to switch fixtures. Well, everything works except for device 5 which is on FIXA and not FIXB. Well, the solution seems to be just don't
have a device 5 and only create one for use on FIXA.
I have the following in my .h.
CCWDIO m_diocontrol;
then in my *.cpp OnInit() I have:
m_diocontrol.SetDevice(5);
when I call
device = m_diocontrol.GetDevice();
device equals like 0x10003 or something and changes around which seems like it must not be getting assigned at all.
I have all the instruments working through MAX and like I mentioned before if I use the property pages of a dialog control I don't have a problem.
So, all this so I don't have to delete the control or recreate it each time I go between fixtures. Seems like I should be able to do it though.
Should I be trying more of a dynamic approach? I'm sure you can tell by my syntax that I'm more of a test engineer then a programmer. I appreciate your input.
Grant
ps. I should mention that device 5 is another PCI-6503 card. FIXA has 2 PCI-6503 cards and FIXB only has one so no device 5 for him. Since both have at least one PCI-6503
though all the files are installed for digital I/O.
Grant M. Johnson
Project Engineer
LECO Corporation

It sounds like that the control may not be getting completely initialized - are you doing anything else to initialize the control beyond calling the constructor? Specifically, I think that you need to call Create. For more information and an example of how to do this, see the Developer Zone article Embedding a Dynamically Created Licensed Measurement Studio ActiveX Control in a Visual C++ Dialog .... This article discusses dynamically creating a graph control, but I
think the same ideas apply to dynamically create a DAQ control.
- Elton

3D Studio Model Control

Similar Messages

Maybe you are looking for