LAVA 1.0 Content
Members-
Posts
2,739 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by LAVA 1.0 Content
-
Hello every one! i wanted to hire virtual employees for web designing and SEO. Actually i am looking for whole virtual team. Because now it's become very expensive for our organization to recruit employees And we need reliable and quality virtual employees. We were prepared to post our requisite on freelancers’ site. But we have observed that it's very time as well as money consuming process. And also I heard that “The bigger problem on Elance, in my experience, is dummy projects. Some buyers post projects simply to get an idea of the cost or to try to find free work” So, what next? Our team comes out with conclusion to directly contact companies who are providing virtual employee services. But the question is "RELIABILITY and Hiring charges". We have got replies from some forums and communities. So, now we have one option company www.marketraise.com. it's nice. But we want best service provider with better package. Thanks in advance Sophia
-
Today I sat down and wrote an application using LabVIEW. This thread is feeling like Twitter.
-
Loop rate of DAQmx PXI-6259 in LabVIEW Real-Time
LAVA 1.0 Content replied to bono02's topic in Real-Time
QUOTE (bono02 @ Nov 2 2008, 03:48 AM) No, I wasn't very clear. QUOTE Did you mean using external trigger? I am not planning to use ext. trigger though, since I desire only to use the source from a single machine. That's close, but not entirely, what I mean is to use one of the clounters as a clock source. An example shipped with LabVIEW (examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-Synch Dig Read Write With Counter.vi) shows how to use a counter as a clock for a read and write routine, just remove the read or write to fit your needs. Remember this can only be done on port 0 (which has 32 inputs on the 6259). Ton PS, if you post screenshots of your code I recommend you to use the http://wiki.lavag.org/Code' Capture Tool' rel='nofollow' title='LabVIEW Wiki article on Code Capture Tool' alt='Wiki article on Code Capture Tool' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">Code Capture Tool -
Hi, Are you using IMAQdx and IMAQdx If youre using the snapshot VI then probaly thats the problem. This Vi only allows you to get one image at a time (using a lot of time to do so). Perhaps a better idea is to use the low-level Vi. First open a session to a camera, then configure it (set the mode the continuous and set a large buffer), then start the aquisition proces. The camera will now send a continuous stream via DMA into the NI(ring)-buffer with the set size. Now you can use the GetImage VI to copy the image from ring buffer into a user image and proces it. The camera will stream Hi, Are you using IMAQdx and IMAQdx snap function? If this is the case probaly the snapshot VI is your problem. This Vi will only bring you one image at a time (using a lot of time to do so). Perhaps a better idea is to use the low-level Vi. First open a session to a camera, then configure it (imaqdx configure aquisition.vi). Be sure to set the mode to continuous and setup your buffersize, then start the aquisition proces (imaqdx start aquisition). The camera will now send a continuous stream of data via DMA into the NI(ring)-buffer. Now use the imaqdx getimage.vi to copy a image from ring buffer into a user-image and proces it. You can select the image you interrested in (buffer number, last (n) or next (n+1). If your processing is faster then your processing (for CCD normaly below 40ms) you can proces every image on-the-fly. If it takes longer you need to setup the image buffer large enough, and copy the image out on a lower rate using the buffer number. Dont forget to stop the data stream from the camera using imaqdx stop aquisition and close the reference at the end of your application. These two examples would be interresting: [Low-Level Grab Async.vi] and [Grab and Detect Skipped Buffer.vi] Regards Patrick
-
Hi Dan, Because you are using a webcam (probaly cmos), I would advise you not just to compare the images pixel for pixel. CMOS cameras mostly have a lot of noise so you have illiminate that first. Make a so called kernel (n x n matrix) that calculate average value of those pixels. In IMAQ you can do this with a filter function. Alternative you can divide your image into sector (e.g.32x32 pixels) and check for differences using a threshold for each sector, then threshold on the number of changed sectors. Lots of succes Patrick
-
Loop rate of DAQmx PXI-6259 in LabVIEW Real-Time
LAVA 1.0 Content replied to bono02's topic in Real-Time
You could build an auto-initialize function, in the first call you create and start the task. In succeeding runs you only read the DAQ. However I advice you to timed IO within DAQmx, so the timing is handled by the daqmx driver and not by LabVIEW. To do this you should create a clock on your 6259 of 5 ms, and do a burst read in LabVIEW of 1 sample, no timing needed the speed will be limited by the DAQ card. Ton (look at the NI examples for timed IO) -
Total Votes in a poll doesn't add up
LAVA 1.0 Content replied to TobyD's topic in Site Feedback & Support
It's the vote that matters, the 'null' vote. Ton -
QUOTE (Louis Manfredi @ Oct 30 2008, 09:38 AM) Why low level people have increased by 0.6% since last week. At this rate we are going to reach 100% soon.
-
Namespace confusion
LAVA 1.0 Content replied to Daklu's topic in Application Builder, Installers and code distribution
QUOTE (Daklu @ Oct 29 2008, 02:27 AM) XControls (but namespacing is a side effect, the main target is creating a new control) LLB files don't do namespacing, the actual VI name (as it can be called via a Open VI reference function) stays the same so you can't have to 'Start' VIs in two LLBs in the same project. QUOTE (Daklu @ Oct 29 2008, 06:54 AM) As much as I'd like to use it, cost is the barrier stopping me from using it. Yeah, it would pay for itself by saving me time, but my incremental cost is somewhat hidden while cutting a PO for n VIPM licenses is sure to raise a few eyebrows. You don't need n only one will be enought (i assume) just for the person that is creating packages, loading packages and installing them needs no license, however you could tell your management that you have a bargain 10 licenses for the price of one. Ton -
Memory consumption chages when minimising window
LAVA 1.0 Content replied to John Lokanis's topic in LabVIEW General
QUOTE (pdc @ Oct 25 2008, 11:30 AM) Now I know, see this http://support.microsoft.com/kb/293215' rel='nofollow' target="_blank">link. -
How do YOU manage different languages?
LAVA 1.0 Content replied to DanielChile's topic in User Interface
QUOTE (rolfk @ Oct 26 2008, 12:28 AM) QUOTE (crelf @ Oct 26 2008, 04:47 AM) Not for us - we use a professional translation service Yeah, but Rolf is from Switzerland so he speaks, Italian, French, German. His Dutch is quite good , not too sure about his English. Ton -
Memory consumption chages when minimising window
LAVA 1.0 Content replied to John Lokanis's topic in LabVIEW General
This a behavior you can observe with any other application. Try Internet explorer or any other application and you will observe the same thing you describe. Start Iexplorer = 42 MB Minimise Iexplorer = 3 MB Maximise Iexplorer = 8 MB I don't know why windows have this behavior. -
Obtaining system directory information
LAVA 1.0 Content replied to Mark Yedinak's topic in LabVIEW General
This link could be useful. -
Developing a LabVIEW Add-in
LAVA 1.0 Content replied to Charles Chickering's topic in Development Environment (IDE)
QUOTE (Charles Chickering @ Oct 24 2008, 03:54 AM) From the wiki page on menu launch VIs QUOTE Private Feature Exposed There is a private VI server method called Application:Menu Launch VI may be found exposed on the diagram of the "Web Publishing Tool" (.\project\webdoc.llb\_Web Document Tool.vi) this property returns the last VI to call a "Tools" menu VI (it doesn't work for "Help" menu), but returns it only once then returns a null string until another "Tools" menu VI is selected from the menu. Use this feature to create a tool that operates on the VI that the user launched it from, like "Check into Source Code Control", or something similar. Unfortunately this does not work for the File (.\wizard) or Help (.\help) menus. See this post. Ton -
Somehow I have the feeling this should belong to the LAVA lounge. Stephen, do you happen to read Disc World by Terry Pratchett? Still sourcenders is not a word I would grip in one time. What about a feature in the project window, where you select a dependency and right-click, relations->Callers inside project? The last time I checked the list context menu was just 40 items long, so 41 wouldn't matter. Ton
-
QUOTE (alfa @ Oct 23 2008, 03:05 AM) But aren't you talking about prostitution? I guess this is a self-contradiction. An unromantic poet is a self-contradiction. —Frost, Robert Lee
-
For the signal range I would look at a signal conditioner that divides the signal (we use Dewetron modules, they provide isolation and anti-aliasing). Why not continiously sample your data and only save if a trigger condition is met. Ton
-
QUOTE (crelf @ Oct 23 2008, 10:55 AM) I agree. The Reconfigurable I/O (RIO) R series cards are designed for exactly this type of application. It just happens that they have an FPGA on the card and you use LV FPGA to define the behaviour of your reconfigurable I/O device. The analog input range is still +/- 10V on the card. You also have the option to add C series signal conditioning modules on the front end of an R series card. The 9221 C series module provides 8 channels of +/- 60V at 12-bit resolution.
-
QUOTE (Antoine Châlons @ Oct 22 2008, 04:22 PM) Time for cool LV clocks. http://lavag.org/old_files/monthly_10_2008/post-3370-1224711345.png' target="_blank">
-
UDP multicasting
LAVA 1.0 Content replied to Blackbyte's topic in Remote Control, Monitoring and the Internet
QUOTE (Blackbyte @ Oct 22 2008, 09:41 AM) Could you show us your current code that you use to read the file into LabVIEW and split it up. It will be easier to provide feedback if we can see what you are doing now. Typically a binary file read should work for any file type.