Jump to content

Bob Schor

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Bob Schor

  1. Thanks, Hooovahh. Didn't think about size. I also didn't say, but I'm running 32-bit LabVIEW 2012 on Windows 7 64-bit. I started tearing down the code that failed, got it down to two error clusters and the Fit VI function, still failed. So I went the other way, wired two error clusters to Fit VI and put a decoration on the FP, no error. Time to check panel sizes ... That was it! I never set this (don't know what my colleague was thinking), so didn't even bother to look here ... Bob (sadder but wiser) Schor
  2. My colleagues and I use the Fit VI to Largest Decoration function in OpenG all the time, and it (usually) works like a charm. I've got a fairly small Project, a simple State Machine that takes readings from a Vernier SensorDAQ device and plots it on a graph. I'm using a Queued State Machine pattern, so I begin by creating the State Machine Queue and enqueuing the Initialize State. The first thing I do inside Initialize is Fit VI to Largest Decoration, and it throws Error 1, pointing to the final FP.PanelBounds Property node that it is setting to resize the Window. I also watched this function run with Highlight Execution turned on, and sure enough, the Error line was OK until it got to that final Write to the Property node. My initial suspicion was the SensorDAQ function, even though it hadn't been called. So I took it out, but the error persisted. I also tried making the Fit VI to Largest Decoration the first VI to be run -- same error. Ohh, an idea. The VI in question was written by a colleague, who is not big on LabVIEW style. This morning, I rewrote the entire program, keeping only the Front Panel which has, among other things, a Graph on it. This problem is so weird that it almost has to be something "unconventional" -- I'm going to leave this post here, in case anyone has other insights, but I'm then going to replace the Front Panel and will report back, especially if it fixes the problem. Bob Schor
  3. I noted with great interest Phillip Brook's "Brown Invoke Node" to manipulate LabVIEW's .ini file. I've written some code to do this for me (I use it to clean up the "Getting Started With" list of Projects and VIs), but wouldn't mind learning how to do it this way. But I can't find the "brown node" -- any hints? Bob Schor Never mind, I figured it out, in private ... BS
  4. I came here three years later following a post in the NI LabVIEW forums. I also had developed a set of ActiveX routines to "do things" in Excel, but found it tedious to get the documentation for the ActiveX functions, particularly with Windows 7 and LabVIEW 2012 (looks like Microsoft is moving away from ActiveX, anyway). I "bit the bullet" and tried using the newer LabVIEW Report Objects, and life got much easier. [Oops, can't figure out how to paste snippet in here, so I'll try to Attach my VI]. Hope this is helpful. BS EXCEL Delete WorkSheet.vi UTIL Ask Sheet Exists.vi
  5. I'm working on a Real-Time project and wanted a way to programmatically update the Version Number in the Build Specs for both the Host and Remote targets. A Web search led me here for the solution. My code differs a little, as I'm doing this from within the Project -- in addition, the names of the Version Tags seem to have changed (in LabVIEW 2012). I tried to post snippets of my VIs here, but couldn't figure out how to do so! I'm using Chrome (if that matters). I'm guessing I should use the "Image" button, but don't know what to put in for URL (the PNG images are on my desktop machine). Bob Schor
  6. I'm trying to view some forums and material posted here. Any time I do, I get a page that says Lavag.org Driver Error, suggests I "reload" (doesn't work) or Notify Administrator (this message). I've tried getting in using IE and Chrome, same errors. I'm kind of surprised I was able to Post a New Topic ...
  7. Bon jour, Fran├žois. I just downloaded UI Tools 1.3.059 from the LabVIEW Tools Network. The series of VIs that you have provided look really nice, and I can believe that they will solve many "annoying" problems I'm having with UIs (I've got one application, for example, where I need to create a TouchScreen interface using, at various times, round Boolean controls, square Boolean controls, etc., and need to both "right-size" them and place them "nicely" (like evenly spaced, at 1/3 in from the left and 1/3 in from the right for two buttons). Painful, messy code that mostly works (except when it doesn't, and then it's a nightmare to debug). So your routines sound like "just what the doctor ordered". What I could not find is clear documentation and a manual laying out the "how to use these VIs to solve your problems" steps to take. I did find the examples in the NI Example Finder after I installed the code, but they were a little terse. I'm pretty sure that I can follow (most of) what you've done, but this certainly isn't something I'd want to hand to one of my students, trying to build a more user-friendly application, and say "Here, these will help with your UI efforts" ... Is there more complete documentation and/or a manual or a "How To" paper on these VIs? If not, would you be willing to work with me to develop such things? Bob Schor University of Rochester Rochester, NY
  8. I'm having the same symptom, but have some further clues on its origin. I've been developing a real-time data acquisition project using Project in LabVIEW 8.5. I'm still at an early stage of development, so my code is not yet "full-blown". My basic model uses state machines, both on the Host (PC) and on the Remote (PXI, eventually), with communication between them using Shared Variables. Because I'm trying to develop a "generic" code base that will be used for various lab projects, I have two Host VIs, a top-level VI that mainly handles the real-time communication with the Remote, and a called Host VI that contains the specific Host code for the particular experiment (i.e. it has a user-specified Front Panel, displays, etc.). Top-level Host calls "user-specific Host", which, in turn, starts the Remote VI. At the present time, all three VIs (and their dependencies) run on the PC -- I have not yet "dragged" the Remote folder to my RT Target (I'm simulating data acquisition for now, just trying to get the basic architecture worked out). When I run Host VI, it invokes "User-Host" VI, which starts "Remote VI", and everything works fine. Over the weekend, I upgraded all(!) of my three development PCs to LabVIEW 8.5.1. The LabVIEW code that I've been developing hasn't changed (I know, because it is under Source Control, and I've checked the revision level). The difference is that now I'm getting the error message described here! One scenario that provokes the message is the following: (1) Start LabVIEW 8.5.1 [i'm going to do this in parallel with writing this message, so bear with me ...]. (2) Open the Project, and load the Host VI. (3) Run the Host VI. What I notice is that I see it "deploying" its shared variables, but then I get a dialog box with the text Failed to auto-save "PROJECT S-Lab.lvproj" for recovery. On at least one machine (the present one) that I tried this, after clicking "OK", the code seemed to run all right. On a hunch, I tried disabling part of the code in my top-level Host VI, specifically the call to the "User-Host" VI that also calls the Remote VI. There was still code left that attempted to initialize the Shared Variables, and I again saw a dialog box that I think talked about Deploying, and I again got the "Failed to auto-save" message. So I'm going to guess that this particular "feature" (which, to re-emphasize, does NOT appear in LabVIEW 8.5, but DOES appear in LabVIEW 8.5.1) may have to do specifically with Shared Variables. Oops, might not be that simple! I just disabled more of my Top Level Host VI, including all of its calls to VIs using the Shared Variables. It now does almost nothing (and, specifically, I don't see dialog boxes talking about deploying things), but I now immediately get the Failed to auto-save message! Well, it's getting late, and I want to post this. However, I may try tomorrow to make a copy of this Project, throw out large sections of it, and see if I can't get down to a "simple" system that exhibits this particular flaw. If so, I'll post it (or pictures of it) and we can see if NI can figure this out. I suppose I could also try to "downgrade" one of my PCs back to LabVIEW 8.5 and see if the problem goes away ... Bob Schor
×
×
  • Create New...

Important Information

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