Jump to content

Gan Uesli Starling

Members
  • Content Count

    67
  • Joined

  • Last visited

Everything posted by Gan Uesli Starling

  1. Can someone example a VI for obtaining the current X & Y screen position in pixels for the mouse? This is for a little widget I'd like to make to assist me in judging sizes of objects from a photograph. I'm going with LabVIEW instead of Perl, etc, just to save myself from having to mess with writing a GUI. So the idea would be this, In a photograph I know the size of one item and want to derive the approximate size of others by comparing their relative lengths (ignoring parallax) and just doing the trig. I have that working already but only in combination with GIMP while eyeball re
  2. Needing to capture a peak value. Not willing to rely on sofware timing for fear of missing the actual peak in between LabVIEW read cycles. So...might anyone know of an NI hardware (module or standalone) which can capture peaks on its own, holding that value until the next LabVIEW read query? That is to say, an amplifier with this built-in (possibly as analog) inside the module? Sure, I can build one from scratch, but it seems a feature many others would want. I rather think that NI might have it as an option in one or another module for CompacDAQ, etc. But I fail to locoate it and NI's
  3. I half expected as much. I'll just re-write it. Thanks for saving me the futility of trying in vain.
  4. I have a built *.exe which I wrote myself two years ago but for which I have since lost the source VI. Said original VI was small so that I could write it anew, but am hoping for a lazier way. I'd like (if that's possible) to just un-build that foo.exe so as to get the original foo.vi if that is possible. I was thinking to put it in the public domain once I do. How I losts the VI is that between then and now I'd got a PC upgrade at work and must have neglected to copy that over (it not being an official work project). What the little program does is only some math. I have attached it a
  5. Good to know! Made immediate use of that. Thanks. Our test lab here mostly uses a generic, all-purpose LabVIEW program which I've been adding to and modifying the past three years. There are umpteen channels of each kind of cDAQ module we have in house. All are addressed via reference. Over the years it had grown...and grown...and grown yet more into quite a LOT of references. So things were starting to bog down from the overhead to such a degree that some of our slower PCs didn't like to run it at all (still a few Dell GX620's in service). So I was just recently getting around to wri
  6. I have attempted to address the issue with the Icron Ranger 2204 unit pairs by updating them to latest firmware supplied by Icron Support (91-00083-R05.exe). This update of firmware had no beneficial effect on this particular problem with communicating to the NI 9237. I have informed Icron of this and await their further suggestions. Meanwhile know that the Icron Ranger 2104 unit pairs continue to serve my LabVIEW purposes well. It is only the 2204 units which have this issue.
  7. Update: I've spent two hours mixing and matching my USB2-Cat5-USB2 extenders and have more complete results. While none of the Ranger 2204 pairs I have tried perform reliably with the National Instruments cDAQ-1978 having a NI-9237 installed, all of them cause the LabVIEW program to hang at some point, I do have another model, an Ranger 2104 pair having SN’s ICL2101903-009845 and ICR2014903-005975 which appears to be working fine, at least so far. Models & SN’s of Ranger 2104 pairs which work okay: Model P/N 10-00117 SN ICL2101903-009845 Model P/N 10-00119 SN ICR2104903-005975 Model P/
  8. Alas and alack, I get this... Your request to URL "http://imgur.com/" has been blocked by the McAfee Web Gateway URL Filter Database. The URL is listed under categories (Media Sharing), which are not allowed by your administrator at this time. Likely it will be the same with any of those. When I'm desperate, I got to B&N and use their WiFi, but it's a fair drive from work.
  9. To Jordan & Mellroth: No worries, I'm not so thin skinned. Among an infitity of things in which I am not an expert, LabVEIW is just another. That said... If I take the Icron Ranger 2204 USB2-Cat5-USB2 extender out of the connection link, replacing it instead with a pair of daisy-chained, USB2 repeater cables, then my LabVIEW program works as expected, sometimes for up to two hours. If I do get any error on the those, daisy-chained cables, it's temporary failure to recognize the cDAQ at all, whereupon I get a "device found" pop-up from windows. The program also works fine as is if I bring
  10. This is the specific error I keep repeatedly getting, but only when trying to read a channel of the NI 9237. Sometimes it stopps immediately, other times it chugs along nicely for a few readings first. Error -200284 occurred at Inputs_Read_All.vi Possible reason(s): Some or all of the samples requested have not yet been acquired. To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It i
  11. To "Jordan Kuehn" and "Hooovahh": Our IT Dept pushes us to use these small form factor Dells which have only one Ethernet connection and our Ethernet has a lot of restrictions. Very specifically, I'm forbidden to put in a switch (which might add latency there, as well).
  12. To JamesMc86: These are all the cDAQ units I presently use. Green have given me no difficulty whatsoever. Only the red ones have been a problem. I mix and match them variously for different tests. Obviously I don't have the bucks to just replace 9 USB cDAQs. Qty Model Description 9 NI-9178 Compact DAC, USB Chassis, 8-slot 7 NI-9203 Analog In, Current, 8 Ch SE 10 NI-9205 Analog In, Voltage, 32 SE/16 DI 11 NI-9213 Analog In, Thermocouple, 16 Ch DI 1 NI-9263 Analog Out, ±10 V, 4 Ch 11 NI-9265 Analog Out, 0 to 20 mA, 4Ch 1 NI-9274 Digital Out, 24 VDC Max , 8 Ch 6 NI-9435 Digital
  13. To "asbo": The problem manifests with plural, identical NI 9237 modules. To "hooovahh": I would like to have considered that before having acquired almost ten of these cDAQs slowly over the last five years. At the time the idea was to have them compatible with any PC. We only have a two, 3-instance, Full Development licenses and propagate some VI's as built applications. Also, our IT department has fairly draconian views with anything we do on Ethernet.
  14. For years I have successfully used the Icron USB Ranger 2204 Cat 5 Extender with both cDAQ and SCXI. But now I have one very annoying issue. I only recently purchased some NI 9237 units for my pressure transucers. Those, and only those, modules don't seem to like being polled over the USB-to-Cat5 extenders which I have in both of my test cells. I have timing issues. Not with all of them all of the time. But with all of them some of the time and with some of them all of the time. I get that pop-up message that says not all of my channels have been read. Increasing the timeout even to ridiculou
  15. Iteration loop speed is much, much too slow to capture a spurius event happening at, say 1250 Hz. The probability of the spurious event happening right at the time of an iterated reading is very remote. It just wouldn't work. Reaching back into my electronics days, the way to do this in hardware would be to charge a zero-loss capaciter through a shockty diode. Two pair of such circuitry, one for peaks the other for valleys. Said charge(s) would be tapped without loss by an amplifier of near infinite input impedance. The max pean and min valleys would be stored between iteration loops for rea
  16. Am wanting to know if it is possible to acquire peak & valley readings for voltage (amplified signal from accelerometer) over long durations but with non-huge data files. So not a time history file representing waveforms. Rather a collection of max peaks and min valleys (or even just envelope span as an absolute magnitude) at regular intervals. That is to say the greatest one which occured during said interval. Say my vibration table is running a 10-hour dwell at 1250 Hz, what I'm wanting to do is splice into the acclerometer feedback signal (post amplification) and keep a running log of
  17. When trying out a new program most error messages that LabVIEW gives me are not very helpful because they refer to "unnamed task" such and such. And so I would like to give names to my tasks. It ought to be simple but still it illudes me. So now I ask... How do I give a name to a task so that error messages then will be helpful?
  18. Have configured my NI-9237 as an AI bridge, reading in CONTINUOUS with a very low sample rate and SAMPLES at ONE. I'm running on a FAST Dell Precision T7500 with USB to a cDAQ-9178. But I still get warnings of memory overrun due to not being able to read data fast enough. Tried a bunch of other values and none of them work. I rebooted the PC and the cDAQ and still no go. Any ideas?
  19. Thank you everyone. I tried both ways and decided to go with the Panel Close Event structure.
  20. I've had a request to disable or modify the RED X at top right of MS Window for a LabVIEW program. Everyone here knows to ONLY use File->Exit to quit from LabVIEW. Sometimes, though a harried operator on a PC with plural windows will accidentally click that RED X thinking it's the overlaying ap's window. This, of course, wreaks havoc on the test underway. Would be nice to make that impossible, or at least doubly hard. So...is there a way to do that? Or alternately, to cause an ARE YOU SURE? intermediary window? TIA, Gan
  21. Thank you, that works. Strangely, it is exactly what I was wanting to do in the first place, had I known (or remembered) that the INDEX ARRAY widget could be pulled down for multiple lines out (versus indexing one at a time inside a loop). For the cluster function, that much is obvious in the visual icon, and was the only reason I was going with clusters for this particular sub VI. Problem is I am allowed to do LabVIEW only seldom (even though I'm the designated 'guru' [coughs embarassedly] for all things LabVIEW) and usually only with other engineers waiting anxiously for me to update whatev
  22. Thank you all for those. I'll be looking into them. Meanwhile, please help me to understand my problem because it still perplexes me. Here is a screenshot of three windows overlaying eachother. At bottom, showing through, is a tiny part of the main VI. You can see where I've put two probes, before and after my problematic cluster_to_array VI. At bottom is the probe results, showing (to my interpretation) a simple array of strings as input and the anomalous cluster of single-string arrays as output. At right is a window showing the contents of my custom VI from which the array-of-strings derive
  23. Paradon, but you clearly did NOT read my question. Setting cluster size is NOT a problem. I already do that. But from an ARRAY_OF_STRINGS it gives me a CLUSTER of 1-STRING_ARRAYS. And that will not do. I need a CLUSTER_OF_STRINGS from an ARRAY_OF_STRINGS.
  24. My Problem: I start with an array of N strings. Using the function "Array to Cluster" I get a cluster of 1-element arrays (each containing one string) when what I want is a cluster of N strings. My Question: How can I do any one of the following: A. Produce a cluster of strings from an array of strings? B. Break an array of arbitrary length into N strings? C. Build a cluster, adding strings one at a time (like pushing onto an array)? Why do I need this? Am saving widget values to a file at end of probram. Then on a cold restart, the user can elect to re-populate those same widgets with t
  25. That built up nicely. Thank you! As for Real-Time, we have it on some stations but not on others. I found the PIDs only on the Real-Time installations, not on the 2010 Full Development ones. And I was wanting a single closed-loop feedback control which would work for all. I'm mostly self-taught in LabVIEW, so know mostly only what has worked for me to date. I write my VIs by guess and by gosh then debug them by trial and error. When that doesn't work I beg enlightenment form they who know. Thanks.
×
×
  • Create New...

Important Information

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