Jump to content

tmunsell

Members
  • Posts

    18
  • Joined

  • Last visited

    Never

Everything posted by tmunsell

  1. QUOTE (Dan DeFriese @ Nov 14 2008, 09:37 AM) Thanks! I did some more reading after seeing your post and think I have it figured out now! Thanks again. I'll let you know how it works out.
  2. QUOTE (Dan DeFriese @ Nov 13 2008, 09:40 AM) Mainly, I don't want to hide the wires. It would make it easier on the other folks if they can see them all and trace them easily, as on a typical schematic. The other reason is that I'm not familiar with structures either. I'm still learning the software as I go. I've attached the app in v8.5. Any help is appreciated!
  3. QUOTE (Dan DeFriese @ Nov 11 2008, 09:36 PM) I just need to be able to select different profile for each model engine. We can only test one at a time. I had to insert the app that Doon posted into the main loop for it to run properly. If that won't use more memory, then I can leave it as is. I have also figured out how to read csv files for the data I need for each model, but I have to change it (and the x and y axis ranges on the charts) when we run a different engine. I just need to be able to select the model when the main app starts, or I will have to create copies of the app with different charts, and make the changes in each one so the appropriate app can be started when needed. That's no big deal, since I have plenty of harddrive space, and the app doesn't take up much space anyway. I'm just trying to make things easier and more configurable for the other engine operators. The reason for the multiple while loops may not be needed. I can still put everything in the main loop, but I'm not sure if that effects memory usage or not. Hope I'm not confusing anyone. I've attached my main app and subVIs if that will help. Please excuse the mess... I'm slowly working on cleaning it up. I want to avoid using structures if I can so others can more easily troubleshoot it if I'm not available. They are all good at reading basic wiring schematics, but the structures may confuse them (as structures do to me at times).
  4. QUOTE (tmunsell @ Oct 29 2008, 02:23 PM) Well, everything seems to be working now. There's only a couple things left to do. I would like to figure out how to run multiple While Loops simultaneously, and set up my app to allow me to select the chart/data files to use for each engine model. I'm not sure if that will be easy, so I may just have to make copies of the main app for each model, since each model has different limits and ranges (for the X and Y axis). I'm also reading about how to manage the memory better. What I've read so far has been very vague, with no specific examples. Got lots to read, I guess! Thanks again
  5. QUOTE (Paul_at_Lowell @ Oct 29 2008, 01:11 PM) Thanks Paul. I had a feeling that is what I needed to do, but I was putting the Build Array on the broken line, which obviously didn't work. I'll give it an ops check tonight with our Fluke 725 and let you know how it works. Every day I'm learning more and more about LV, thanks to the good folks on this forum!
  6. QUOTE (Doon @ Oct 23 2008, 02:27 AM) OK, I've tried adding your app to mine, but I'm running into an error that I can't quite understand. As shown in the attached file, I connected the data (tapped into the wires going to the digital indicators for Pt7/Pt2 and EGT, and removed the sliders) and ran it into where your "DAQ inputs" were bundled. I'm not sure that the error message means. The data that I'm reading is DBL, so I thought it would work by inputting it as is. I'm sure I'm missing something obvious, but I've been reading and troubleshooting for 3 hours now and I'm getting a headache! Please excuse my messy-looking block diagram. I needed to get it up and running asap, and I'm planning on cleaning it up as soon as I get everything working properly. Also, I placed everything in the main while loop for now, since I haven't read anything on running parallel loops yet.
  7. QUOTE (Doon @ Oct 23 2008, 02:27 AM) Thank you very much, Doon and Minh Pham! You have been very helpful. The app you posted should save me a lot of time. I've always been better at "reverse-engineering" things, especially when it comes to learning a new programming language.
  8. Thanks for the info! The data we are receiving is from a Daytronic System 10 DAQ unit. We are currently displaying the data in real time in digital displays. There are no arrays for the data that I will need to plot. There are two inputs that need to be plotted on the graph (i.e. Engine RPM vs Engine Pressure Ratio). One needs to go to the X axis, and the other to the Y axis. I've tried just using a simple XY graph, but the live data isn't displaying at all, although it shows up fine on the main digital indicators that I am already using. As the engine accelerates, the engine pressure ratio (EPR... Pt7/Pt2 in the graph above) rises, as does the exhaust temperature (EGT). The X and Y axis values (labels) needs to stay as it is displayed, but the live data (point or line) needs to follow the actual EGT and EPR as it changes. The dots on the graph above are individually saved points. Basically, I'd just like to be able to see a dot moving on the graph as the engine accels/decels. As for inputting the data, I don't have to use a spreadsheet. The limits are fixed data that just needs to be displayed so that I can see if the live data is falling within the min and max lines. I could input it manually using numeric constants for the values and build an array. The only problem is that different engine sub-models have different min/max limits. I thought it would be easier to just select the filename that is to be used for each one, rather than manually entering all the info into the app each time. Of course, I suppose I can use a switch control or something like that to select the data that is used for a particular engine. Can this all run within the while loop that I'm using for the rest of the application? Should I place the chart outside or inside the loop? Although I've been using LV for almost a year, I'm still in the process of learning it. I've got the basics down, but haven't experimented with graphs yet. Thanks again. QUOTE (Doon @ Oct 22 2008, 02:22 AM)
  9. Hi. I am currently attempting to display real-time performance values on a graph. I have the values needed in an xls file for the minimum and maximum limits. I would like to display these limits as lines on the graph, and then have the live data displayed on the same graph in real-time. This must be a continous process, during which time we are running a jet engine. This data will not be saved or printed, but only shown to aid the engine operator in judging the engine's performance during the test. I've attached a screenshot of the final graph which is created in Excel and printed for the customer. Is it possible to recreate this graph in Labview, with the limit lines, and live data showing up as a dot while the engine it moving through the band? Thanks in advance! Todd
  10. Thanks. I'll see if they can download the files needed. The nearest rep is about 200 miles away from the test cell. I'll also be making backup copies of the DVDs that I can keep in the laptop case when I travel, just in case I need them. Thanks again. Todd
  11. I'm sorry, maybe I wasn't explaining the problem clearly. This is a first time installation of the app for the target PC. I want to build the app so it will run with just the run-time engine installed on the target PC, without having to install the entire LV program. But, for the build to work, it needs certain programs such as MAX and the NI-Serial drivers. It's when I select these to be added to the installer that it keeps asking for the DVDs. I'm out of town now, so I don't have access to the DVDs. I want to create the installer and email it to my workplace. Thanks. Todd
  12. I have been trying to create an installer for my app, but even though I have all the drivers loaded on my laptop, the builder keeps asking for the DVDs. I don't want to have to carry them around with me all the time (I do a lot of my programming while at home). Is there a way to create an installer without needing the DVDs? Will I have to copy each DVD to a folder on my laptop (wasting a lot of disk space)? Thanks! Todd Munsell WGP&W Industrial Turbine Services
  13. QUOTE(crelf @ Feb 14 2008, 04:06 PM) Thanks to you both for the info and the link. I'll check it out. I guess I forgot to mention that when I placed the four channels in the second loop, I did not have any wires connecting the two loops. I tried to run the second while loop that way, but it still only ran the main loop when I clicked the run button. I'll read some more and see if I can work it out tonight. Thanks again! Todd
  14. QUOTE(gleichman @ Feb 14 2008, 01:38 PM) Thanks for the reply, Alan. I think I understand what you are saying..... Please bear with me, since I am new to Labview (and programming in general), but I've been reading a lot about it lately in the book "LabVIEW for Everyone". What I'm trying to do is set up the two loops to operate simultaneously as part of the main app. I tried seperating the loops by putting the channel read subVIs inside the second loop, but when I ran the app, only the main loop ran. Nothing in the second loop worked.... no data flow at all. Do you know where I can find some examples that I can learn from? I need to configure the second loop so that the data displayed on the front panel indicators for 4 of the channels (Vib1-4) have an adjustable time delay, but all the other channels in the main loop must run in real-time. I've been trying to find an easy way to do this (like a time delay subVI that will go inline with the data flow for those particular channels), but haven't had much luck. I'll read up on queues and see if I can understand how they work.
  15. Hi, Well, the main app is running well, but I've run into another problem that I've been trying to figure out for 2 days. I need to slow the front panel display for just 4 channels from the Daytronic System 10. All the other channels need to update in real-time, which it is doing now. I tried creating a new while loop outside the main one, and placed the indicators in the second loop. But, when I run the app using highlight execution, the data flow stops at the tunnel in the main loop. I'm not getting any errors, but for some reason the data just stops at that point. What am I missing? I've tried replacing the tunnels with shift registers, and still have the same problem. Help! I'm getting a wicked migraine! :headbang: I've attached a pdf of the block diagram. Todd
  16. Hi again. I was finally able to get the application working perfectly! There's only one problem now.... whenever one of our other PCs (one using Wonderware DDE w/ MS Excel, and the other using Autonet) is running and collecting data, the Labview PC's data get garbled. There are a couple of channels that come through, but most give errors or incorrect data. This happens no matter which port on the System 10 I use, or which serial cable I use. The other PCs work fine together, but Labview doesn't seem to want to work with either of the others. Any ideas would be appreciated! I'm so close to having everything working that I'd hate to get stuck now. Todd QUOTE(pallen @ Nov 2 2007, 11:57 AM)
  17. Thanks for the quick replies and the link to the driver. I was even able to find a more recent version (for Labview 8) on the Daytronic website that I will try also. I realize that I have a lot of reading to do, and found out today that our Daytronic rep is more than happy to assist me in setting up Labview for the basic displays we will be using. I'll keep searching the forum for more information. In the meantime, I'll be using the built-in help and tutorials to get this project moving. I have already noticed that Labview is a lot more versatile than Autonet... and best of all, it works without a proprietary operating system like Autonet uses. No need to set up a seperate partition on the harddrive. Currently, I'm working on our other PC that will display and record our data in MS Excel. I've been working on that system today, and should be done with it tomorrow. We use Datapack Server (not sure if "they" still exist anymore, either) to import the data to the spreadsheet. Eventually, we may convert to NI's interface for Office apps. Thanks again! Todd
  18. Hi, I am new to the Labview 8.5 software. My computer knowledge consists mainly of hardware configuration and basic software setup. I do have a small amount of programming knowledge in HTML, VBA and Visual Studio. I'm a jet engine technician with Wood Group Pratt & Whitney Industrial Turbine Services, LLC. We are upgrading our old Pentium III computers that currently use the Autonet monitoring software (now out of business). We are using a Daytronic System 10 2000 DAU (connected with a serial cable) and decided to try LabView software for real-time monitoring of our engine tests. Since Autonet will not run on our new PCs and we have long ago lost the password for it, we cannot reconfigure the display at all, even if it would run on the new PCs. We are starting to test a new model engine and need to display several more parameters than we have used in the past. Can anyone point me in the right direction for setting up a basic display screen for showing engine speeds, temps, pressures, etc. obtained from the Daytronic unit? Some sample VIs would be very helpful. Since I'm learning Labview from the ground up, some examples would accelerate my learning curve dramatically, since I've always been better at reverse-engineering software rather that learning it step by step from a book. We don't need anything extravagant, just a basic display to monitor about 25 parameters as the engine runs. If I can obtain a sample with just a few Daytronic channels configured to show up in LabView, I can most likely figure out how to do the rest. In the future, as I study the program more, I will be experimenting with the other features available in LabView. Thanks in advance for your help! Todd Munsell Test Cell Tech WGPW Plattsburgh, NY tmunsell@wgtest.com
×
×
  • Create New...

Important Information

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