Irene_he

The iUSBDAQ - U1208LOG is a dual mode USB data acquisition module which

can work as a regular computer controlled USB DAQ, as well as standalone data

logging system without a computer. Compare to our existing very low cost

iUSBDAQ-U120816, it has almost the same pin functions, but with increased

analog sampling throughput rate over 50ksamples/s, plus standalone data

logging mode.

Also some unique functions that you don't usually find in a data acquisition

module hardware and software will be added. More details will be released when

the product is available sometime in late April or early May, 2007.

Stay tuned!

Irene

I think they broadcast for the benefit of the community. ]

I said we don't mind to listen!!

Hi, aren't you guys (I mean Michael and Jim) suppose to sit side by side in an office? Or you like to broadcast your office conversation? But I think we don't mind to hear . Just curious

Irene

QUOTE(Michael_Aivaliotis @ Mar 3 2007, 07:51 PM)

I'll just use http://babelfish.altavista.digital.com/babelfish/tr' target="_blank">Babel Fish...

I wish that I can help to translate some, but that was my last life, can't do it now. Have read few of the already translated words, pretty close, I think the translation tool does a pretty good job.

Irene

QUOTE(superslug @ Feb 22 2007, 07:04 PM)

thanks.

I have a new problem.

I am trying to get the Ivision window (for both playing and recording) into a tab.

I can get the window into the frontpanel and posistion it but I have been unable

to get it so that it is only on a single page if a tab.

Since video window is not a native LabVIEW component, you can't put in just one tab like other LabVIEW controls. But you can work around this, by visible and invisible the video window. Only when the video tab is clicked, then video is show, otherwise unshow. IVision2.2 have vis to show/hide video window, but not in the demo version of IVision1.8. But you can always use windows managerment vis from NI to do the same thing since video window is just window.

Irene

QUOTE(superslug @ Feb 19 2007, 06:27 PM)

I am trying now to do the same thing with 2 avi's running.

Is it possible to run 2 ivision windows with different avi's in them or is there a pause and setPosistion for using blendavi?

Yes, you can run two avi files with two separate file session, this way you can control each one to jump to any location you want. No, you can't do "set Position" with blending two avi functions.

Irene

QUOTE(sachsm @ Feb 19 2007, 08:45 PM)

I encountered the same problem on my machine (Dell Dell Dimension E510) and was not able to fix the problem despite trying for several days. I have never seen an error like this before and would like to know why the IVISION software is sensitive to the DEP mechanism.

Hi sachsm,

It is because IVision uses some customized directshow filter which is a COM object that needs to be registered with regsrv32.exe. Winxp sp2 with hardware DEP enabled machine will have problem registering unless you disable the DEP on your machine or register the filter in safe mode. You may also meet the same problem if you have some ActiveX control that needs to be registered. The bottom line is regsrv32.exe can not run under DEP protection. But once you get over that, it should be easy to load up IVision in LabVIEW as many people have made it to work.

Irene

QUOTE(superslug @ Feb 15 2007, 07:44 PM)

Hey,

I am trying to use the ivision softare to play an avai frame by but I am unable to work out how i can do this.

Has anyone done this before and have some pointers? I would appreciate any help.

Thanks,

Bernard

i think i have worked this out,

using the ivision_MediaSetPosition.vi i can set the frame number and by setting the stop value to 1 it will stop on that frame.

Hello Bernard,

That is good that you figured out by yourself. There is another way to do, that is:

Starting with the example "IVision_MediaFileExample2.vi", this vi has a button to let you jump to any frame you set, but will continuously run. So in order to run frame by frame, you can first pause the media file with the vi "IVision_PauseMediaFile.vi", this will pause the video clip. Now if you call the "IVision_MediaSetPosition.vi", it will jump one frame at one time or only jump to the frame that you specify and stop there.

Irene

Hello,

Please read the IVision_FAQ, item No.6, it provides the solution. It's caused by DEP (data execution protection) enabled machine (only some Winxp sp2 machine that has hardware that is capable of DEP). Below is the link to IVision_FAQ:

http://www.hytekautomation.com/Products/IV...IVision_FAQ.htm

Irene

I thought about contacting Rolf directly when I first started this project. It does seem like he is a master when it comes to understanding the creation and use of DLLs in LabVIEW. I was hoping he might be reading this. I started a forum thread on NI discussion forum regarding this very topic (direct use of input and output arrays when creating LabVIEW DLL) awhile back but I have not gotten sufficient resolution to this issue. Passing by value cannot be done for arrays, and in my preliminary testing early on, I was not able to resolve how to interpret the output pointer to array and the like. I'm tied up now but need to revisit this again as time permits. A simple example regarding use of arrays rather than stored disk images pertinent to our PCA DLL creation effort would be appreciated if anyone would like to contribute.

Sincerely,

Don

Hi Don, maybe you can try to ask the question in info-labview. Rolf seems to be more active in info-labview. Or maybe you can send him a PM.

Irene

Yes, sorry for the late reply. Its operation has been validated against other language versions of PCA. I have a neater version of this code in state machine format that has separate steps in separate cases - but I think this version reading from left to right should be easy to decipher....Don

One other thing I would like to figure out is how one would create the LabVIEW DLL if the inputs and outputs were arrays rather than stored images. The handling of arrays, allocations of memory, and determining interpretation of outputs that I believe have to be passed as pointers rather than by value has confused me to this point with respect to DLL creation. I would be interested if someone has some thoughts on this.

Sincerely,

Don

Hi Don,

I know the way to pass in LabVIEW allocated array for C program to process, but never done the reversed way to pass in a C allocated array for LabVIEW to process, but I think there is a trick that you can use a C allocated input array (usually pass in as array pointer, the pointer can be treated like U32, so the pass in parameter maybe an integer, not an array directly) for LabVIEW to use, just I never need it, so I didn't bother to remember how, but I think Rolf has mentioned in info-labview some time, I didn't read very carefully :-(. But on the other hand, maybe there is a setting when you create LabVIEW DLL, that let you specify the input array as pointer, have you check this? Maybe then everything will be taken care of automatically.

The output array is easier, I think, because you can allocate the output array in LabVIEW, then output the array pointer to C program, C program can make use of this pointer.

I am not sure if I talked my mind clearly or not, anyway, something is better than nothing:-)

Irene

Dear all,

I'm experiencing with a problem, which I can't really solve. I use Labview 8.2 and the last version of vision

In an application I need to have an image preview, and I need to do this showing on the desktop (just to show, without save) the analog input in the video-in of my ATI graphic card.

Is there some example code which already do this? or can someone suggest my how I could approach this problem?

Thank you very much and happy new year!

Hello,

If you use IVision LabVIEW toolkit, it can capture video from ATI all-in wonder card. This card can be used as TV tuner as well as frame grabber card, so that you can connect analog video input to this ATI all-in wonder card. You can download IVision LabVIEW toolkit 1.8 from below link. Starts with the IVision_CameraDemo.vi, you will see the video right the way. (IVision treats ATI card as video device). IVision 2.2 has new functions to programmatically switch the ATI card between TV tuner mode and frame grabber mode and also route the sound source correspondently.

This is where you get more information about IVision LabVIEW toolkit:

http://www.hytekautomation.com/Products/IVision.html

Irene

IVISION would be nice if it didn't need a runtime engine. I think a runtime engine is fine for heavy industrial applications, but for a small webcam application it is overkill.

Hello Marcel,

There is no real runtime engine for IVision, at runtime you only need to distribute few DLLs which you will do anyway with any other toolkits or drivers. I think you may have confused and mixup the runtime engine with runtime license's fee. IVision charges runtime license fee, but only $20 each.

Irene

counting people

I am not sure if you pointed to the wrong link above??

To attach a file, please click on "Browse..." to select your file, then press "UPLOAD" at bottom when you write your post. Just scroll down and you will see.

Irene

hello genios of LabVIEW.

I have a litle problem:

I make an aplication that track people in a region. I'm adquiring the video whit a webcam (creation). The aplication is runing but I need to see the diferent stages of the video proccesing. I try to put diferents image displays to see the video(for example one at the RGB image stage and another at the binarization stage, but the image look like all the procces were view in one image display (all the stage at the same time) .

I hope you can help me ..............

thanks.

I forgotten, here is the aplication:

Hello,

What toolkit do you use for video in LabVIEW?

It's possible to display video and processed video in separate windows, or in the same video window in picture in picture mode, for example, or in the same video window showing the selected dispay mode (raw video or processed video). It's all possible with correct toolkit.

By the way, didn't see your application that you mentioned.

Irene

Hi Irene:

Not exactly clear what you mean by 'function calling document' - do you mean the documentation on the inputs and their types as I described in one of my first messages above?

Sincerely,

Don

Hi Don,

That is exactly what I meant, sorry for the confusing term. It's the function description (like vi, what does this function do and the input and output parameter's type and descriptions).

Regards,

Irene

Hi,

We received a complaint from one of our customers today. We make sound analysis software which runs sequences in factories, etc. We have a Chinese client who told us that our sequence seems to run slower the more it runs in their factory. We were curious, because on the English Win XP there are no such problems. So we created a test machine with the exact same setup and ran the sequence. Well guess what? It does run slower the more it runs! In fact it seems to cycle. It begins fine with ~3.2s per measurement and then after about the 30th sequence, it start going up in time to about 4.5s and then to 5.5s and then drops back to ~3.2-4s and starts this cycle again. These would all be signs of a memory leak except for the fact that this does not happen on the english windows xp and nobody is having this problem except the people using chinese windows xp.

I was wondering if there are any experts or Chinese XP users out there who are aware of this problem and LV execution times. One more thing to note is that our software is in English but is being run on Chinese XP at a factory in China. I've heard that Chinese characters use 4 bytes per letter instead of 2 bytes like in English. Could this be a possible problem (we do a lot of string flatten/unflatten in our software)? Please help.

Hi linnx,

I heard something that Chinese XP may not be optimized...but I am not sure. Why would ancle Bill doing that?

ps. Irene: I retested your C executable after putting the original images in the correct directory in your heirarchy - it worked fine. Sorry about not doing that originall. I got 4 images, not 5, so I expect you hardcoded 4.....

int numPCA=5;

int startFrame=11;

int endFrame=15;

GREAT!

Now when I hand this installer off to the c++ programmer who knows nothing about LabVIEW DLLS, what documentation do I need to provide him with other than what I originally mentioned to you (the inputs, outputs [in this case = none], and formats of such). In other words, after the installation, what do I have to tell him to do to get this working in c++? Is there anything special that he needs to do or you did?

Thanks much!

Don

You can just give him the full installation (including the LV8.2 runtime engine) and the function calling document (you can also put that in the PCA.h file, commenting out with //). That should be enough. You can certainly also give him my very simple example project in C if you want.

Regards,

Irene

Hi Irene:

I sent you a private message regarding ftp.

Sincerely,

Don

Hi Don,

I got your message and I have tested it. The lvanlys.dll has to be in the Data folder, then no popup window anymore (I think LV installer puts it there automatically), but I must have moved it to different location the first time for some reason, that was my mistake . Other than that, your DLL works great.

Regards,

Irene

Hi,

We received a complaint from one of our customers today. We make sound analysis software which runs sequences in factories, etc. We have a Chinese client who told us that our sequence seems to run slower the more it runs in their factory. We were curious, because on the English Win XP there are no such problems. So we created a test machine with the exact same setup and ran the sequence. Well guess what? It does run slower the more it runs! In fact it seems to cycle. It begins fine with ~3.2s per measurement and then after about the 30th sequence, it start going up in time to about 4.5s and then to 5.5s and then drops back to ~3.2-4s and starts this cycle again. These would all be signs of a memory leak except for the fact that this does not happen on the english windows xp and nobody is having this problem except the people using chinese windows xp.

I was wondering if there are any experts or Chinese XP users out there who are aware of this problem and LV execution times. One more thing to note is that our software is in English but is being run on Chinese XP at a factory in China. I've heard that Chinese characters use 4 bytes per letter instead of 2 bytes like in English. Could this be a possible problem (we do a lot of string flatten/unflatten in our software)? Please help.

Hello,

I don't think 4 byte character will be related to the slowness of the measurement especially your software is English version... Maybe you can ctrl+alt+delete to bring out the task manager to see the memory usage and CPU usage, see when the measurement slows down, what happens to the memory usuage and is CPU usage rising?

Irene

Hi Irene:

Many thanks for testing this. Given the issue of the dialog below, it seems a good idea to follow this up by building the DLL installer to see if the LabVIEW VI searching dialog goes away. The problem is the installer is about 70 mbyte because it includes the RT engine which precludes uploading it here. I can put it on an ftp site for you to download if interested for one more round of this. Let me know. If you have run out of time, that is OK, and I appreciate this effort below.

Sincerely,

Don

No problem, I have some time. Let me know the ftp site when you are ready. But just doubting if including the RT engine will change things than install it separately. But you never know. I can give a try.

Regards,

Irene

Hi Don,

I have tested the PCA.dll. Attached is the simple console C program. Here are few points for the testing:

1.Yes, you do need to distribute the LV8.2 runtime engine to C programmer.

2.In the example I have hardcoded the image path to "C:\\Downloads\\Labview Downloads\\Ivst - with sample" if you want to run the "TestingPCA.exe" in release folder.

3.It produces many PCA images, not just one if I set "the number of principal component images to calculate" to say 5, it gives me 5 PCA images.

4. It seems there is LabVIEW vi searching dialog window poping up when runing the calculation. I thought that was because I moved the "lvanlys.dll" file to different location, but when I put under the same directory as TestingPCA.exe and PCA.dll files, it still poping up. So maybe some other dependancy files not in the same directoy as when you created the PCA.dll?

I hope this will help.

Best Regards,

Irene

Download File:post-42-1165855048.zip

This is the example that I sent to Darren to set the video format to 1600x1200. I will post the example here in case some other people has the same device. You need to download IVision LabVIEW toolkit 1.8 or up first.

Thank you,

Irene

Download File:post-42-1165540937.llb

I think you are right. I don't know why I thought differently. I have built installers for v8.2 applications and knew they were responsible for installing the LabVIEW RTE - I have to look and see what all is involved for building an installer for DLLs. Perhaps it is close to the same procedure. I don't know why I thought one did not need the LabVIEW RTE for DLL use in different environment. I had in my head that the DLL files contained all of what was needed. Irene: If you want me to try to build the installer for this, I can. But it might be that the RTE is all you need. Maybe Rolf or someone from NI can clear this up?????...

Thanks for your input.

Don

Hi Don,

I have downloaded the LV8.2 RTE. (thanks Ton). Will try out and let you know if I need more files.

Regards,

Irene

Hello:

I created a LabVIEW DLL in v8.2 that performs principal component analysis. I have successfully tested this within LabVIEW. Now I need to see if it will work in the C++ environment. I am asking for guinea pigs if anyone would volunteer to try this and tell me what is needed to get it working in that environment. In return, you get to keep this algorithm. I supply some sample time series of images within the .zip. Any help is greatly appreciated.

...

Hi Don,

I can help you to test by writing a C console program. Don't I need LV8.2 runtime engine to call LabVIEW created DLL? I haven't used LV8, if you have a quick link to where to download the LV8.2 runtime engine, that will help. I will test it over weekend if this is not too urgent for you.

Regards,

Irene He