Jump to content

MrYoung

Members
  • Posts

    6
  • Joined

  • Last visited

MrYoung's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. This is most probably the issue I'm having. I didn't think it ignored the port input! Thanks heaps!
  2. Hi!! I've used VI server before for some simple tasks, and it has always worked as expected. However, for this task, it is becoming increasingly frustrating. What I'm Trying To Do: Look into any previously made executable in LV and get the memory information of the VIs internally. We're suspecting a memory leak in one or many of our named LV2 Globals within a range of our applications on the production line. Instead of painfully editing the EXEs on the production line, we want another EXE to go in and analyse the VIs we're interested in. What is Going Wrong: The tool I've created only sees the list of VIs within its own EXE and not the other!!! I'm connecting to port 2020 (set in the ini file of the EXE I'm trying to access) and set the port of the analyser to 2022, and it STILL somehow connects internally!!!! What I've Tried: server.tcp.port=2020 in target exe server.tcp.enabled=True in both Simple "Open Application Reference" VI with the port number set to 2020 Read the "Srvr.Port" application attribute of the analyser to check it is set to 2022 (and it is) Checked out this CONFUSING NI link http://digital.ni.co...62571DA005B896C The last option seems to suggest you can just go ahead as always.... I don't get it I'm expecting at the very least to get an error when it tries to connect to port 2020 when it's not there, but it doesn't. It just somehow connects to itself and returns the list of VIs within itself. NOTE: The application is in LV8.5.1 and the Analyser is in 2009 SP1. I didn't think that would matter as the TCP layer should abstract all that right? I've compiled it in 8.5.1 now and still exactly the same result.....I'm fresh out of ideas now Any help would be greatly appreciated. Thanks in advance, Youngy
  3. Wow....I expected to wait until tomorrow for a reply at the earliest!!! Thanks heaps for getting back to me on this issue. You guys are tops.
  4. Hi, I work with a team of very experienced LabVIEW developers, but none of them can answer this question! I seem to remember being able to drag and drop a diagram snippet from the block diagram of a subVI from it's icon. Imagine you have your function pallet open, and you grab a VI, and instead of its icon being placed, it's the code snippet from its block diagram. Kinda like a template. The VI DOESN'T HAVE A FRONT PANEL!! Have I simply dreamed this up!? I don't really need this functionality, but I would love to clear my head. Thanks in advance, Andrew
  5. QUOTE(Justin Goeres @ Nov 29 2007, 01:58 AM) Hi Justin, Thanks for looking into it for me. The project was converted from 8.2. When I created a new project file, it all went to plan. I have no idea why it wasn't working originally but it's all solved now! I thought it a bit strange that nobody else had seen the same thing, but at least this post will reassure the next person that recreating your project from scratch will be worth the effort if they see this happen. Take a look at the screenshots I've attached. (I can't figure out how to insert them when it asks for a URL ) Thanks again! Andrew
  6. Hi! This may seem like a trivial question, but I can't get around it! When working with 8.2, it is simple to build dynamically loaded VIs into the EXE using the "Source Files" and the "Source File Settings" tab in the app builder. Wen you generate a preview of the build, the dynamic VIs are not visible. When working with 8.5, you cannot set the destination of the source files to the EXE. The only choices you have are "same as caller", "Support Directory", and "Destination directory". When you generate a preview, the dynamic VIs are pasted. How do I get the same result as in 8.2? :headbang: Thanks, Andrew
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.