Irene_he

The past influenced by the present it's a nice topic.

Hmm... well, maybe we should respect anyone whoever has a firm believing in whatever what .

I had a good laugh on few posts recently. Thanks.

Irene

I don't know what the other guys talking about here, seems to be quite off topic

To the original post, I think those "habit changing" toolkits (maybe more official term should be "management toolkit") maybe hard to be accepted. In a already "civilized" or "advanced" world, people simply just don't like to be driven...

just joking

Irene

Perhaps if there was a tool that would gather all of the control and indicator descriptions into one place to be edited and reloaded into thier respective subroutines (and saved back out).

I'll be watching this topic with interest.

Chris

Yes you can do it with vi server. Load all vis you want to document into memory, then get all vis in memory with vi server, open references to those vis (using a for loop with index) and get all controls' descriptions of each vi and save them into a text file with proper formating for easy read back and decode later. That way you can edit the text and read back to assign to each controls using the vi server technique again.

Thanks.

Irene

There are two types of activeX server you can use with LabVIEW. One is an activeX server provided by other windows application. If your window's application provides activeX control, you can call this activeX control's methods and properties within LabVIEW. You can search LabVIEW examples for that, for example, Excel provides activeX control, LabVIEW has an example to show how to read and write to Excel within LabVIEW.

The second type of activeX is LabVIEW itself as an activeX server. You can call LabVIEW activeX server from C++ or VB. Below are the links from NI side:

This is the link of calling LabVIEW activeX server from C++:

http://sine.ni.com/apps/we/niepd_web_displ...034080020E74861

This is the link of calling LabVIEW activeX server from VB:

http://sine.ni.com/apps/we/niepd_web_displ...034080020E74861

In your case, it sounds like the first case that if your third party window's application provides activeX control, then you can call it within LabVIEW. It is the easier way than the second type because all work is just LabVIEW wiring, not writing C++ or VB code.

Hope this will give you some hints on activeX control.

Irene

Thank you Christopher and others and this forum, you all not only give great LabVIEW help, but also provide some very thinkable opinions on life attitude.

Thank you.

Irene

if the minimum Value of the scale is 0, you wire -10 to the e.g. tank, it will only show a very small line at the bottom of the tank, which can be quickly overseen, and does not differ much from an "empty tank"

In that case, you may want to show the digital display or flashing a light when the value is out of range other than zero value.

Irene

Actually I felt not very good for my above reply, that's why I have to reply again here it maybe some of my headaches drive me into narrow thoughts, although I haven't really replied to anybody yet with "Don't ask me to do your homework", I always tried to answer... The "Don't..." answer apparently is not the correct answer to any questions...

Generous people are always a look up model and respectful person for me.

Sorry for haveing answered the question with "Don't...", it's worse than not answering

Irene

Where to start?

my coffee tastes especially good this morning, so I was feel gentle and generous. Now where was that post on how not to ask your first question ... )

I guess I understand how you feel... well, I like the statement "Don't ask me to do your homework". This would be the final answer to rescue some headaches for being nice.

Irene

Hey, don't tell me you have white hair! In my age that is something that comes to men naturally but for you I had thought that will take some more time :-)

Good luck and may IVision still bring you some compensation for whatever you've put into it.

Rolf Kalbermatter

Thank you Rolf. Your kind words all the time is always an encouragement for me.

Regards,

Irene

I have a LabVIEW software written for golf that was showed on ESPN channel last year. I heard this February it was showed in one golf magazine (golf digest?) although I haven't seen it myself.

-----

I tried the evaluation version of IVISION. My video card is all-in-wonder, and the toolkit worked well. I could catpure video signals by using demo vi included in IVISION kit. But one problem is that I got 'squeezed' images when I did snap images. I think it's because some VIs included in the IVISION toolkit (IVISION_ImageToArray.vi, maybe) have a fixed-size ROI (320x480, in my case). The VIs blocked, so I couldn't find a way to change the ROI settings. Have anyone suceeded capturing unsqueezed images?

Hi Feynman,

Snap will get you the realsize of your video device output image. So that is the image size for all-in-wonder. But there are two ways you can make it look more "normal". The easiest is changing the video window size either programmatically or manually drag into the size you want. This does not change image resolution, only for visualization purpose. The other way is changing the image resolution using "IVision_ResizeImage.vi" after snap.

Irene

An IMAQ runtime is

... Since we are talking about a LabVIEW application I assume you are creating an executable and one other precaution you might want to take is to not name your security VI with anything descriptive of the method you are using since it is possible to look inside a LabVIEW executable and see the names and even extract the VIs within the application. Don't worry too much, they cannot get to the diagrams or even the front panels of subVIs.

Maybe best embedd your security code in main vi so that no subvi for that used, that way no one can extract that vi from exe file and replace it if they know how.

Irene

I think this moving control feature is pretty nice. One usage case can be that customer may want to layout their own screen, even for the same product, but they want different look for their own brand:-). I guess we can save the last locations of controls to a file so that when loaded up next time, it will keep the previous look.

It's good that LabVIEW opens up more new opportunities.

Irene

This is the song of Michael Buble

Most time you don't really need to write USB driver for the device you use unless that is your own created device. If using USB RS232 converter, it's transparent to your existing software that can talk to RS232, you don't need to change anything in your software, the only thing you need is install the USB RS232 converter driver, then it'll add a virtual com port to your computer like any other COM port.

If you decide to use other USB devices, like USB DAQ, you also don't need to write your own driver because most of the USB DAQs will come with drivers and programming interface for your languages such as LabVIEW.

Irene

I've recently worked with USB 6008's and I had problems with analog and digital together. My system used (5) USB 6008's and LabVIEW would hang about every 10 or so executions. Here are a few suggestions:

Install motherboard specific drivers for your USB chipset.

Remove other USB devices (mouse?)

Don't use a USB hub. Connect directly to the USB port on the back of your computer. (Although a hub worked better for me than PCI-USB cards.)

Acquire your digital data on an analog channel.

Revert back to NIDAQmx Base 2.0?

I hope one of these will help.

Alan

USB hub should be no problem as long as it's self powered, not bus powered.

I think NI USB 6008 and MCC USB daqs are using HID class, which is the same class for mouse, keyboard etc. Maybe that's why you suggested to remove other USB devices (mouse?), because they may affect the performance of the HID based USB daqs. I used one of them before from MCC, it hangs/freeze the computer once in a while.

Our iUSBDAQ uses microchip general class, not HID, so far we haven't experienced any hanging or freezing of computer. Maybe you would like to take a look?

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

Thank you.

Irene

I think it's the "G View"="LabVIEW". The view comes from the square, it's like a window and the content inside that square looks like a "G".

The first thing comes to mine mind is the output value maybe infinite ( I have to remind this to myself everytime now after many times forgotten and I couldn't see the real graph due to auto scale of Y). So could this mean that average Joe can be a supper power in certain case?

Yes, it's possible with usb daq to synchronize multiple usb daqs, at least I know with HYTEK iUSBDAQ - U120816. It has an external trigger line, if you tie all usb daqs trigger lines together, and use streaming mode of data acquisition (U120816 is up to 32ks/s, which means if you use 8channels in each module, each channel can do up to 4ks/s which is enough for your spec, 1khz). If you enable the external triggering option, all U120816 will only start streaming after the trigger lines go high. Since the detecting trigger line high timing is in the hardware, the delay will be less than 1ms.

And we tested in lab that multiple iUSBDAQs can stream data simultaneously. The testing computer is winxp, 2.4GHZ with 256MRAM, the usb 2.0 ports are prefered (root hub or extension hub).

And I think the windows timing for USB devices is very different than for RS232 devices.

For information about iusbdaq, check out below link:

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

Thank you.

Irene

Treat the pointers in LabVIEW as interger U32. Then pass that interger as pointer to next function you want to call, I think it's similar like how you do it in VB. But if your parameter is **(pointer to pointer) you may have some trouble in LabVIEW, hope you only have one *.

Irene

Do you mean that you have a 24bit color image and you want to extract the colors to 3 8bit gray image? If so, if you can get an array of the 24 bit color image, then deinterlace the array to 3 output arrays, each output array is your gray image data. But you need to know what is your color image color order, some are RGBRGB... but some image output in the order of BGRBGR... so that you know which output array is R, which is G and which is B.

But I guess I may misunderstand you. Maybe you just want an image window or picture control that can display gray image. If so, at least I know IVision LabVIEW toolkit can do it. The image window accept 8bit gray image or 24bit color image. Link is here:

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

Irene

Ok, Ok, I get what you guys all saying, using system/OS coloUr (Ok I want to be more canadian), attributes. But good programming habit maybe one thing, but not the only thing, colours will brighten up your mood which will make you more creative, don't you get that?

Another thought just came cross my mind, maybe the LabVIEW programming language should add personality toolkit to it. Personalities like cool (buttons when you press them, they don't react anything), emotional (buttons when mouse just barely over them, trigger the event) and maybe a nagging button for software protection and license warning.

Irene

I can understand both of you. You are dealing with the "Terminator" alike customers

What is your GUI color? I use to paint it colorful, blue, yellow, pink, brown, green...most time I'm getting along ok with my customers, but occasionally I get some "rework" request on my color scheme.

There was one time my customer called me said he had something to discuss with me. He first told me that how wonderful my software worked (ok, I like that very time he said that ), but then I could feel that he had something to say, he tried to put in a nice and easy way. "Is it hard or even possible to change the curve color? I hope it's not a lot of work. You know, Irene, the customers they don't like the pink." "Oh really! well...I'll see what I can do" I replied reluctantly. So I added to my change list.

The other case my customer wrote me and saying that they needed to have a meeting discussing the color scheme of the GUI and complained my GUI contrast was too high. (I guessed that hurted their eyes ). But I didn't hear from him for a couple of days until I got another e-mail saying "xxxxx" liked my GUI color very much. It turned out that the very end user is a female. See, there are same mind people on the earth.

I enjoy discrepancy.

What are your funny experiences?

Have a nice weekend.

Irene