Jump to content

Mike Ashe

Members
  • Posts

    1,626
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Mike Ashe

  1. Interesting the the LabVIEW webserver shows up at http://localhost just fine, and you can run back and forth through several pages, but you cannot get a VI to be published in it.
  2. Thanks for that bit of info. I had installed, then uninstalled the latest update after having problems. Maybe now I can reinstall. I was hoping we would not see these types of problems with Flash. I got rid of RealPlayer due to it interfering with several other programs and have not reinstalled. I thought Flash was gone for good as well.
  3. Now I need to go look to see if it says anything about this in the upgrade notes. Prior warning would be nice. It makes you wonder what else might be happening under the hood, silently. I asked elsewhere if there were any previously exposed VIs that were closed now under 8. PJM said he had not found any. It didn't occur to ask if other licenses were affected.
  4. I second this. I'd like to do some mapping and was looking at OpenMAP, which is in JAVA. I already have access to some example code that calls the ArcVIEW GIS software, but that is $$$, whereas an open source solution would be very nice. Ideally, it would be great to be able to go in both directions. Anyone doing this type of Java-LabVIEW integration yet?
  5. Yep, you can get LabVNC at: L.O.S.T. - LabVIEW Open Source Tools Cheers
  6. You might also compile your plugins as DLLs, one for each plugin. Since you can call those DLLs from any language, you can also call them from LabVIEW and this should also let you mix LabVIEW versions, like having your main exe in 7.1 and a plugin DLL in 7.0
  7. Unfortunately, this is probably partly our own fault for talking about scripting, etc, in open forum as much as we have. When I first found out about some of the scripting, INI keys, etc, I told no one for weeks, and then only a single other person. It was only after several posts were made out in the open and the cat was out of the bag that I discussed it publicly. I wonder if we had kept a little quieter if NI would have still closed off as much of it as they did in the last two releases. Probably, they were probably just whetting everyones appetite before making scripting a paid for tool kit.
  8. Hmm, doesn't appear that you are initializing the port first. Look at the examples in the Simple Serial library in LabVIEW: C:\Program Files\National Instruments\LabVIEW 7.0\examples\instr\smplserl.llb\LabVIEW <-> Serial.vi The "LabVIEW <-> Serial.vi" will give you a very basic template to: Open -> read|write -> Close the serial port. You cannot get much simpler. Make sure you are reading at the same baud rate as the Ohaus (I used to use Ohaus years ago). Remember that these will only give you a single read. There is another example of how to do a read with a timeout. To get real communication you might want to modify this example to put the serial reads and writes in a loop. You can also look for examples on NIs DevZone. Assuming you are using Windows, go to Start > Programs > Accessories > Communications > HyperTerminal to get a simple application to read and write to a serial port. Use that to test out your device and make sure it communicates with the computer first, then use LabVIEW. Gotta go, good luck
  9. Well, you could slightly modify a RTSI cable to give you a wire out from the RTSI trigger line you are using, then route that into one of the inputs of the 6509 card, which has input change notificaton. Probably good enough for sync to the order of a few milliseconds, maybe better. Certainly fast enough for what you're trying to do.
  10. I can second this. It is pretty simple. I recently needed to transfer a license. NI made it easy. You do not even have to fax it in (like it states on the form) I just printed, signed, scanned it to JPG and emailed. Took no time.
  11. Nope, not out of your mind. I recall some work at a tool manufacturer that did essentially what you are talking about, same for a large computer mfr. I think if you look at the Find All VIs Catalog and on NI's DevZone you might even find some examples. Similarly, if you Google LabVIEW and barcode you will get pages of stuff, mostly reading barcode, but some writes too.
  12. Could you tell us a little more about your application and/or upload a VI/LLB that shows what you are trying to do and the problem? Also, you should take a look at the examples in LabVIEW for serial communications. Finally, are you sure the hardware you are connecting to is working okay? Have you tried to talk to it using a simple serial terminal application on the same computer as you have LabVIEW on?
  13. I recall that there were certain private nodes that were exposed a couple of versins ago, that got closed/hidden when you installed LV7 (or was it 7.1?). Someone here (PJM?) recommended saving a copy of some directories prior to install and I think made a zipped copy of said dir available here on line. My question is: Is there anything we should save a copy of before installing Lv8? I just got my boxed SSP upgrade and have yet to install it. Has anyone found items to archive first?
  14. Jim Kring implemented something like this for boolean controls. You might search on the OpenG website. I seem to recall that it was available for download there.
  15. There have also been at least two toolkits for implementing neural networks in LabVIEW, one software and another that used LabVIEW to program neural chips. Don't recal where they were just now, do a Google on it.
  16. Look under the examples: C:\Program Files\National Instruments\LabVIEW 7.1\examples\general\menubars.llb There are several applicable demos there. Also in the same directory look for the uievents.llb which has a bunch of deoms and techniques you should become familiar with. There is an example in ther for using menu items with events. enjoy :-)
  17. I wonder if this could be solved by storage of the baseline/default control sizes, locations, layout, etc. Then scaling could be done on the fly, but always with the ability to restore to defaults. I would think a nifty subVI with this built in that manages its caller, or a given VI reference would be very useful. I once did something like this just for a subset of the characteristics of booleans about 3-4 versions ago, but never as general as an all purpose FP manager. Has anyone done anything like this?
  18. Actually, what you tried at first will work, you just need to have the constants. Use the example the previous post showed you to get from jpg files into your picture. On the diagram you can then right click and select make constant. This will give you a proper constant. You can then use those constants. I've added an attached updated version of both techniques showing how you can load from file or use the constants as a "factory default" setting for your images. Nice in that it allows you flexibility for your images.Download File:post-45-1131034607.vi
  19. Since you are always passing XY pairs, there is no reason to have two separate loops and timers, do both in one loop, with one timer. Better, do it in a timed loop. The earlier comment about using a state machine is correct. What SDK are you talking about, the one for the HW? If there is any way to tell that the HW is done with the previous entry, you could then use that to fire an event for your state machine.
  20. I have to respectfully disagree. For Uncle Bill it stopped being entirely about the money when IBM's big-wig manager snubbed them and walked off the stage at the OS2 joint conference decades ago. The next day (or so) MS announced they were doing something independent called "Windows" and its been a battle of honor and territory ever since. Now, please lets not have anyone flame that last sentence regarding whether MS is "honorable", thats not what I mean. Its about Bill's honor. IBM, the big guys at the time, slapped Bill in the face, in public, and he's been on the personnel warpath ever since. Sure Bill is very interested in making lots of billy-bucks [pun intended], but the money is secondary to taking over the territory and making sure no one can ever slap him and his company that way again. Here I completely agree. G programming is such a different mind set that a lot of MS (and other companies) software people would not be that productive for a while. In addition NI still has patents on a lot of features we now consider standard in LabVIEW. Only the basic, original patents are old enough to soon expire.Which reminds me, I have to retract my earlier statement about the original patents being expired. They were filed in 1986, but it took 4 years to award, and some of them were continued, etc, with the result that the original expires in Feb 2007 and the second expires in April 07 and Apr 2001 due to the continuation. So NI will still be in control of the basic G language for some time to come.
  21. So if I understand, you can create scripting tools in 7.1 and open a copy in 8.0 and it will work, but you cannot create new scripting tools or modify them in 8.0?
  22. I believe the original patents for the G language in LabVIEW have expired. Sooner or later, someone will agree with m3nth (graphical programming makes sense) enough that they will start on an independent version of the G language and graphical editor. That could be open source or proprietary, ie, "embrace, extend, take over..." The company that could do that easiest is Microsoft. And yes NI is big, but lets be real here, NI is hoping to become a billion dollar revenue company in two years ... last time I looked, Microsoft had about 40 billion cash reserves they could blow on R&D or patent fights, etc. Do you really think it would be a contest?
  23. A DAQ Occurence comes to mind, or set up a separate loop and queue or event it in...
  24. In your event handler add an event case to allow logging of registration. Each time a producer registers, have it send a single event to the logging case and store/display/log etc...Unfortunately so far we do not have a method like: enumerate all registered events, or the related, enumerate all producers for this Q or simply enumerate all Queues. (I do this last one myself since I use queues so much).
×
×
  • Create New...

Important Information

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