Jump to content

Yair

Members
  • Posts

    2,870
  • Joined

  • Last visited

  • Days Won

    44

Everything posted by Yair

  1. I have zero experience with the dynamic data type and the express VIs it uses, so I can't really help you, but the VIs in the Express>>Signal Manipulation palette should help you. Specifically, you can use the conversion VIs on the bottom to convert to a 2D array and get the data you need out of that and then convert back, but the sample compression VI might also do what you want.
  2. For an upcoming project, I was asked to monitor ~20 gauges. It looks like the vision VIs for reading gauges are simple enough, so the trick is now to connect to that many cameras. The cameras themselves don't have to be high performance (a resolution of 640x480 or less and a maximum frame rate of 5-10 FPS is probably more than necessary), so the main factor is the price of the cameras. I understand that GigE is the practical standard for doing something like this, but it seems that all those cameras are overkill and way too expensive. The USB drivers are limited to a single camera. Does anyone have experience\suggestions for connecting to multiple cheap cameras and getting the images at reasonably real time? Any specific models? Any warnings? P.S. I have no practical vision experience, so feel free to suggest anything (e.g. maybe saving snapshots and loading those files will work. I just don't have any experience with the cameras).
  3. QUOTE (BobHamburger @ May 19 2008, 08:43 PM) I think I know what you're talking about, and it's not inconsistent because it has its logic - when you disconnect the cable, the OS kills the network connection so that LabVIEW doesn't see the adapter any more. This would cause it to throw a different error.
  4. I don't have experience with the Write to Measurement File VI (most professional developers avoid using Express VIs for most things), but here's one simplistic option of how this can be done: If this doesn't help you, you should upload the code you already have.
  5. Frameworks which rely on features which are supported in RT should work, so Sciware GOOP should work (as you've seen) as well as dqGOOP (although I haven't actually tried it on RT). LVOOP is still not supported (and I don't think it's supposed to be in the near future) and I have no idea whether Endevo GOOP is supported or not.
  6. I assume crelf knows what he's talking about. Personally, I can say that I used Prolific USB to serial adapters from LabVIEW more than once and they worked fine, but I never tried that VISA window you used. As I said, you should check which property is throwing the error and what value you're wiring into that property (e.g. maybe you're setting a baud rate of 993423534) and try to fix that first.
  7. I never really manage to stop being serious, even when I do fun or funny stuff. That's just the way I'm wired and I don't mind it, because it doesn't mean I can't enjoy that stuff. QUOTE (neB @ May 16 2008, 04:15 PM) http://www.haaretz.com/' rel='nofollow' target="_blank">Haaretz, which literally means "the land" or the "the country". In singular non-specific form (which can also be used as "Earth") it's pronounced "eretz" which sounds quite similar to "earth", so I wouldn't be shocked if that was the source of the word "earth".
  8. QUOTE (Michael_Aivaliotis @ May 16 2008, 07:47 AM) I apologize for attempting to enlighten the masses by broadening their knowledge.
  9. QUOTE (shoneill @ May 15 2008, 12:34 PM) It's not really Mike's fault. Hebrew (at least the modern Israeli accent) doesn't have the U which English has (as in "gun"). That's why when you see a word transliterated from Hebrew which has a U, you can know it will be pronounced "oo" (like "pool"). Others which don't exist are A (as in "I can", not as in "mark"), I (always pronounced as "ee", so my name is pronounce ya-eer and Israel is pronounced yees-ra-el and Uzi is oo-zee), a long O (like bowl), W (although it exists in speech in words that come from Arabic) and probably some others.
  10. Find the property node which generates the error (using probes on the error wire). The second property used in that property node is getting an invalid value. Check which property it is and you can figure out what's wrong from that. In general, you should probably try taking some of the tutorials linked to here.
  11. Yair

    Dance!

    Here's why following Michael's blog is worth it. I can't embed the video, but someone else can do it if they want.
  12. QUOTE (dannyt @ May 14 2008, 11:54 AM) As I mentioned before, LVDiff can be found on sourceforge. http://meta-diff.sourceforge.net/' rel='nofollow' target="_blank">Here's a link.
  13. Download LVDiff from sourceforge. I seem to remember that it was updated to LV 8. Actually, I seem to remember that Jim worked on it, so I'm a bit surprised you guys don't use it on occasion. I know I do (mostly when I use my boss' computer and see that he has some modified VIs which he should not have touched and which he did not commit ).
  14. I doubt you'll find anyone here who uses it. Most people use NI's toolkit, their own solution or any of the free toolkits which are available online (e.g. LabSQL, the ADO toolkit). In general, you can view the code generated by express VIs by right clicking the VI and selecting Open Front Panel. You should note, though, that the code might be messy (since it's automatically generated) or password protected.
  15. Oh yeah, that was when they did the comeback season in the 90's, when he was really really old... To be honest, it does kind of look like you. You didn't happen to paste your own head there, did you?
  16. I looked at some of those briefly a long time ago (there are a couple of free ones on the bottom), but I don't remember if they're any good. You can look at the free ones yourself and decide. You can find links to more tutorials here.
  17. QUOTE (netta @ May 8 2008, 11:39 PM) It should be relatively simple using scripting. I can't do this at the moment, but it's probably a matter of getting a reference to the VI's diagram and calling a method on that to add a VI or something similar. Of course, this won't help you with the memory issue.
  18. I can think of some cross-overs: This summer, coming to a theater near you - Police Academy 16, with Harry Callahan and Axel Foley as the teachers.
  19. QUOTE (jpdrolet @ May 7 2008, 09:08 PM) :laugh: The only problem is that we haven't been that good on the flaming part.
  20. I wanted something like this for a long time as well. QUOTE (Jim Kring @ May 5 2008, 05:14 PM) If you're refering to concatenating different strings into a single one, you can sort of do that - build them into an array and then concatenate the array:
  21. There are many ways to do what you want. One example would be to build a simple action engine which would hold an array of configured tests. I would suggest that you also use this to maintain the list of tests instead of using the shift register in the main VI. Another option would be to use an array of LVOOP objects, but you might not want to go into that yet. By the way, your deselect case is very Goldbergish. Other than the fact that it uses the Value property instead of the terminal (which isn't very good), it uses a while loop to create what is essentially a for loop. Also, you can do the removing more easily sorting the array and then reversing it in order to delete the elements from the end of the array first. If you want, there are links to some tutorials here.
  22. QUOTE (Aristos Queue @ May 6 2008, 07:49 PM) Yeah, I remember seeing one of those.
×
×
  • Create New...

Important Information

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