Jump to content


  • Posts

  • Joined

  • Last visited


Everything posted by m3nth

  1. Can anyone open this LabVIEW 5.1 code and save it in a later version of LabVIEW that can be opened/upgraded by v8.5?
  2. To followup... NI moved the functionality around a little (although I didn't read about it anywhere), so technically it's not a bug and can be mitigated by opening the VI reference with the option to save the VI on close if there are any unsaved changes (Options = 0x04).
  3. Did this problem get fixed? The VI isn't broken when I open in 8.0.1.
  4. I'm pretty sure this wasn't a problem in previous versions. If a subVI is not reserved by another higher level VI, closing the FP from the BD will cause you to lose all changes to that VI. http://forums.ni.com/ni/board/message?boar...ssage.id=182816
  5. Without the auto-tool on, you can't get the little grabby hand to move the block diagram around when the VI is running because (per NI support) they purposely killed the popup menu. Nice. If it's not broke, don't fix it. This has been reported, and the hand is automatically available with the auto-tool on. The real request here though is simply for horizontal navigation with the roller ball. Currently you can get vertical navigation and fast vertical navigation (hold down Shift), but no horizontal navigation by holding down Control, or Control+Shift, as is used in other programs (Microsoft Visio for example). This feature would make navigation really really easy.
  6. m3nth


    i finally made it down the property node tree to be able to set the front panel origin. what a pane(!) :thumbdown: i used to just drop fp.origin and set it to zero so my fp would reset every time but now i'll have to have a vi handy or a vi with a set of code to merge off the palette. i agree with previous suggestions: they should have left it with an updated description and consigned it simply to pane[0] origin. actually, i expected this to be a settable property in the vi's property list since the window size is now a settable item. that is really convenient. but then if i scrolled around the FP, it would resize with my new origin and i couldn't see anything. doh! i'm sure they left this out because there is now an entire pane[] array to deal with, but it would still be really handy for single pane vi's.
  7. m3nth


    Can someone point me to the FP.Origin replacement in LV8?
  8. Yes, a null string meaning the zero-length string constant (shown as a little square quote) located on the palette. I have all types of cluster, usually just different data, and usually not including a string where length information is stored with the data
  9. ...and doing your own mean is actually faster than calling the LabVIEW dll... I can't remember who posted that awhile ago... put them in a high-count loop for comparison.
  10. The more basic information of just your different IP #'s and Computer ID's can also be obtained by placing the String to IP function and then right-clicking to selecting multiple outputs. This yields a U32 array that can be converted in a for loop using the IP to String function to return names and dot-notation IP #'s. Also if you're looking for the connection status of a specific device on your network there is code availalbe (I believe it's on NI's website somewhere) that will let you monitor the ping time natively (using raw winsock calls, as compared to performing a shell exec of the ping command)
  11. That may be 1 bit flip from zero... I'm not sure. there are issues sometimes with numbers that approach zero when using double/single data types. Besides that however, I wire a complex into the squareroot and get the correct answer out (0 + 3i)... what were you using exactly to get your result? The expression node didn't seem to work with a complex number and neither did the formula node so I couldn't figure out what you were doing.
  12. I can't follow the video link but I'm guessing I've seen it before judging by what's been said. The article below has more information on the guy that did it (and a photo) http://www.foxnews.com/story/0,2933,177861,00.html
  13. Another possible workaround to this is to add a blank bookmark vi (inside of a disable structure if you want) and then add that to your palette. Then you can place as many as you want and search for them as desired.
  14. That's interesting. Is it still twice as fast if you put it in a subvi?
  15. Your post is somewhat unclear about whether you are using a low level library or code interface node, or whether you are using a VI (which possibly encapsulates the low level call). Your best bet (if you aren't already using a single VI for the call), is to replace the low-level calls with a single (possibly reentrant) VI. That will let you perform driver swaps very easily as already noted.
  16. Can you post a link to a previous thread or more info on what this is and how to use it...
  17. I'm pretty sure (at least hoping) this is a basic question... Background Info: I'd like to set up a web page with: A single picture A single text file A web page with two frames so you could see the picture and the text file at the same time (and be able to scroll the text file) This is something along the lines of a webcam but it would just be keeping track of a LabVIEW program. This would mean very low space requirements... maybe a few hundred k for the picture and a few hundred for the text file. So the info I'm looking for would be: How to make a web page with two frames (I can probably find that myself) How to update the image and text file on the web server from the LabVIEW app What (free) services are there that I could use to host the web page Is it possible to host the web page on a non-internet computer that would just be available on an internal intranet?--The pc running the LabVIEW app for example--this would make updates easy.
  18. Sure that works. If I'm not misinterpreting what you're saying, you could just wire a >0 comparison with the numeric input and the boolean output to your LED. Or <0 if the logic was the other way around.
  19. Jim.... I like your solution. It will only work if you're calling one DLL at a time though right? I don't think it was a requirement to call more than one at the same time but I was just thinking things through.
  20. I'm pretty sure there's not a way to do this in LabVIEW. I don't know about version 8. As painful as it sounds, what I would be prone to do if I were you would be to make your own wrapper DLL. Depending on how many different calls you were making (how many different interfaces you were attempting to import into LabVIEW) it could be simple or really time-consuming. At any rate, you could just pass the dynamic DLL path to your static DLL and let it make the calls and return data... that way your LabVIEW Call Library Function node would have a fixed path to your DLL, but it would call the other DLL's and get data from different places.
  21. Alright if you haven't heard of Einstein's puzzle you can just look it up. There are plenty of sites telling what the problem is and how to solve it, such as this one: http://www.mindspring.com/~mccarthys/puzzle1.htm Who in their right mind would want to read the solution before trying to give a try and test their brain power though... even better, why not try it in LabVIEW! Alright so attached is a LabVIEW version for you to burn some of your free time with if your screen resolution can handle it. This game isn't extraordinarily great but it is a little addicting until you get the right answer. It's a good puzzle at least. And yes I know, their are a ton of improvements that could be made to the user interface but I just whipped this out as fast as I possibly could so I could play it as soon as it was barely functional. Maybe one day if I get around to it, I'll fix it up. Instructions: Drag & drop baby. Dragging a house will cause everything in the house to switch places. Also, I didn't implement a way to clear out mistaken items (oh well, just restart). Enjoy... Download File:post-360-1131844672.llb
  22. I don't have much insight but that sounds like a pretty practical idea to have an inventory system. Have you talked w/ NI about this? I wonder what those ModInst VI's are actually for, because it doesn't make sense that they wouldn't find your hardware if that's what they were for. Obviously whatever MAX uses to enumerate the hardware devices would get you the info you're looking for and it's a question of whether or not those enumeration functions are available in LabVIEW through some interface. I don't have the ModInst files handy at the moment but it might be interesting if they use some DLL's (from MAX or something)... to see if the DLL's have other functions that might do what you want.
  23. I guess it's unfortunate that NI implemented this 'bug' in such a methodical and thorough fashion... changing the underlying routine when two references are compared--you'd think they did that on purpose or something.
  24. You can: A) Get a copy of LabVIEW v6.1 or B) Save an LLB of all the files you want to convert and then post it either here or on NI's forum and hope that someone will help you out.
  • Create New...

Important Information

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