bmoyer

QUOTE (Neville D @ May 13 2008, 02:44 PM)

A 16bit image that your working with.

N.

http://lavag.org/old_files/monthly_05_2008/post-4985-1210707604.png' target="_blank">

QUOTE (Neville D @ May 13 2008, 12:28 PM)

Can you ignore the least significant bytes ?

Can you also upload a 64-bit image as well?

I'd prefer not to, but I guess I could make it an option. A conversion speed or quality option.

I'm not sure what 64-bit image you are asking for. A 64-bit RGB ramping image? With same value in each color? What will you try and do with it?

Thanks,

Bruce

Neville,

Thanks for the tip. I tried implementing what you suggested and it works really fast, but the IMAQ ColorUserLookup only works with 32bit color images (no support for 64bit color) which means the 16bit image is truncated to 8bits before the lookup table is applied making the conversion less accurate. I've included some test code if you want to take a look (the subVI "Convert Image Ref to IMAQ Display Color Image Ref.vi" has a conditional disable to select the 2 different code methods).

Any suggestions?

Thanks,

Bruce

I'm acquiring 16-bit images and displaying them using the IMAQ display control. I allow the user to choose different lookup tables (LUTs) so that the grayscale image is displayed in pseudo color in the IMAQ display.

When the images are saved to disk they are saved in their native grayscale format. I'd like to give an option to save the images in display format as well. Has anyone ever done something like this before? I have an idea of how this could be done (by using the Interpolate 1D Array function and the LUT to convert each pixel to obtain values for each color), but this seems like a very slow way to do this since there may be 100s of images to convert.

Any ideas?

Thanks,

Bruce

QUOTE (TobyD @ May 8 2008, 05:14 PM)

I have not seen anything in my inbox from NI.

After about 2 hours and about a dozen emails, they seemed to have stopped. It's rare that I turn on autologin for the NI website except at my desk at work and that was where I was when I was receiving these emails. It may have been an error on NI's part, but who knows.

Thanks,

Bruce

In the last hour I've gotten about 6 emails from NI saying that my cart has been autosaved. Has anyone else seen this? I tried deleting the items in my cart at first, and then they reappeared. Then I changed my NI login password, and still received the emails.

Is anyone else getting these?

Bruce

QUOTE (Antoine @ May 6 2008, 05:48 AM)

/pedantic

Am I bigger than someone smaller than me AND smaller than someone bigger than me ?

How good is that !

pedantic/

Or am I taller than myself when I where thick soled shoes and shorter when I take them off.

Bruce

QUOTE (PJM_labview @ Apr 29 2008, 02:13 PM)

anyone?

http://lavag.org/old_files/monthly_04_2008/post-121-1209492708.png' target="_blank">

I have to agree with the previous posters. The title doesn't make sense (hopefully they were doing a dry run of the presentation and caught it first).

Where was this picture posted originally? Where was it from?

Bruce

I'm tired of these people cross posting in all of the different forums to get help with their homework!

http://forums.ni.com/ni/board/message?boar...d=27330#M312759

I don't think you are going to find anyone who wants to do your homework for you here, but if you are truly interested in figuring out a solution to the problem you describe, try to break the problem down into pieces that you need to learn.

How do I express this equation in LabVIEW? Hint: Find the Numeric palette.

How do I evaluate this equation using an array of V? Hint: For Loop.

How do I graph the output? Hint: Graph

A good place to learn about these "pieces" is in the LabVIEW Help-->Find Examples... menu.

It's going to take time (maybe more time than you are willing to take) to ramp up to do even a simple problem like this one, but everyone here went through the same growing pains at some point too.

QUOTE (Steve Mate @ Mar 27 2008, 05:35 PM)

Bruce - I had a problem with project files in LabVIEW 8.5. My symptoms were different; whenever I selected created new LabVIEW project, LabVIEW would immediately shut down. The solution was found in this link, and then the subsequent link in step 4.

http://digital.ni.com/public.nsf/websearch...A8?OpenDocument

It refers to a corrupt MAX database, which seems unrelated but in my case fixed the problem. It might be worth taking a look at just in case.

Like you, my problem occurred right after installing.

Good luck,

Steve

www.co-efficient.com

Steve, thanks for the tip, (I had previously seen your entry when searching the NI forums) although, like you said, I think this problem is different. I'll see if I can install a VM like Tomi suggested, but it's usually difficult to get a hold of XP disks at work to install it (I think that's why I never was successful at installing a VM before).

Tomi, thanks for your help too. I see the benefit of practicing on a VM and installing 8.5 on it (hopefully I can get this to fly with IT), although I don't know if this would fix the problem with the lvproj file containing an entry for the LV8.2.1 runtime (since a clean install of 8.5 wouldn't have 8.2.1). Fortunately I only have a couple of projects (2) in 8.5 (1 large project and 1 small) and am almost finished recreating the project structure of the large project, but this was days of work wasted that I wasn't expecting.

Bruce

QUOTE (Tomi Maila @ Mar 27 2008, 03:20 PM)

Just to make sure you did everything correctly.

- Did you uninstall everything before reinstalling?

- Did you install LabVIEW version in the order from oldest to newest?

- Did you use the same LabVIEW version to open the project file as you created it with?

- Did you install all the possible libraries and toolkits you might have been using for all LabVIEW versions?

If you have done everything as described, please try to open the project file with LabVIEW 8.5. It has more advanced support for solving cross-linkage problems. Also try to open the project in another computer. It may be that your new LabVIEW installation has corrupted for some reason. Or maybe some DLL LabVIEW is using is corrupted.

Yes, I unistalled "everything" before reinstalling. I even used the msiBlast.exe to make sure which took an extremely long time because it asked me after almost every uninstall if I wanted to reboot.

I installed LV from oldest to newest except for LV8.2.1 which I installed after 8.5 (because I saw in the lvproj file that it had a line in it with for the LV8.2.1 runtime). My original thinking was, "why do I need to install 8.2.1 since 8.5 converts back to 8.0".

The project file worked fine with 8.5 before I reinstalled everything.

I did go back and install SignalExpress that comes on the 8.5 CD because apparently if you don't install this, the NI_AALPro.lvlib, NI_AALBase.lvlib, NI_AALBLAS.lvlib (Advance Analysis libraries?) are not installed (why am I forced to install SignalExpress in order to get this library?)

Bruce

QUOTE (rkanders @ Mar 27 2008, 02:17 PM)

I have had it happen as well, and fairly frequently. My solution has been source code control. If there is a problem I diff it and find offending VIs and then manually fix it or just revert.

Reinis

I usually can do what you described (using a backup lvproj file), but since I just reinstalled LV, I have a feeling that there are other reasons why it's not working. I noticed in the lvproj file that there was a reference to LV8.2.1 runtime in the Installer so I tried went back and installed LV8.2.1 but it's nearly impossible to tell if this helped any because the project file still hangs.

:headbang:

Bruce

My main reason for writing this post is not that I expect solutions to my problem, but that I need a way to vent the problems that I've been experiencing with the projects files.

I recently had to reinstall LabVIEW 8.5 (also 6.1, 7.1.1, 8.0.1) on my PC (basically I had to start from scratch) and now my LabVIEW project files don't work! LabVIEW hangs when opening them until I end-task LabVIEW. So basically I'm left with recreating them from scratch! You would think that if LabVIEW can't find a file in the project, it would tell you instead of hanging. I see project nightmares ahead (and now) if NI doesn't fix this soon. Every file has to be in exactly the right place or else you have to start over (or try to manually parse through the .lvproj xml file with hundreds of files in it to determine which one(s) "might" be the cause).

I've seen similar problems with LV project files in the past and fortunately I was able to retrieve an archive of the project file, but this time this isn't working!

Can anyone else relate?

Bruce

I use the IMAQ copy when saving snapshots of live images so that the image displayed when the user clicks the "save" button is the image stored (not what the image is after they finish typing in the filename). You'll notice that when you save images in MAX, you can't actually get the image when you click the Save Image button, it's the current image when you acknowledge the File Dialog (not what one would expect).

Bruce

I don't think this works for non-color images.

From the help:

IMAQ Merge Overlay

Makes a nondestructive overlay part of the image content. This process creates a destructive overlay. The VI then removes the nondestructive overlay. The resulting image is an RGB image.

Any workarounds you can think of?

Bruce

I know that this is not a supported tool from NI, but I'm curious as to what this tool really is doing under-the-hood? Does it remove registry info that is usually left behind too? Does it do anything different for uninstalling NI installations compared to non-NI?

Bruce

Sorry that nobody's responding to your question. I haven't used DeviceNet in years (it was for controlling mass flow controllers, valves, etc.) so I don't think I'd be any help anyways. I'm not sure if DeviceNet ever got very well established (which may be why your support questions are not getting much attention), but since I haven't been using it for a long time, I wouldn't be the best source to ask anyway.

I have a function that finds a polynomial fit of each pixel location through multiple images and it's taking a very long time to calculate (because of the hundreds of 1000s of pixel location it needs to iterate through). I would like to create a new function that works on all of the pixels in the images at once, but the subVI in the original function, "General Polynomial Fit.VI", makes a call to the lvanlys.dll, making this difficult to implement.

Any ideas?

Bruce

There's the VI property node FP.IsFrontmost that I've used to stop polling the serial port if the window is not on top. I'm not sure your application but this might work.

Bruce

QUOTE(lraynal @ Feb 26 2008, 10:31 AM)

Your conversion is probably more like the one in MAX, which would explain what I get...

But I don't understand why do we need to change the conversion range to get something approching the MAX image !

The display mapping in Full Dynamic should be enough !!! Don't you think ?

The default "Full Dynamic" range, means to scale the image so that the brightest pixel in the image gets a 255 (maximum brightness on the screen). MAX doesn't display in Full Dynamic range. You would think that the default display method would be the same as MAX but it isn't. NI would have to explain that decision for you.

Pressing Ctrl-H in the 16-bit Display Mapping screen will give you a description (somewhat crude) of what each option does.

Bruce

QUOTE(lraynal @ Feb 26 2008, 08:59 AM)

I've tried the different conversion method, without any correct results !

The correct one should be "Given range" from 0 to 255, but that's worst than the original...

I've tried as well to add "IMAQ Image Bit Depth", but no better results...

Does this VI work?

It doesn't seem like there's anything wrong with the example code, just the scaling of the values displayed is different. It seems as though the image is getting "autoscaled" to the range of pixels values in your image. Right-click on the "Image" control and select "16-bit Display Mapping...". Change the "Conversion Method" to get the correct display. I've also found that when the 16-bit Display Mapping isn't working the way I expect it to, that adding the "IMAQ Image Bit Depth" function VI after the image is acquired (keeping the "Bit Depth (0)" of the IMAQ Image Bit Depth VI unwired), usually solves the problem.

I was able to dig up some code that was able to get whether the current user is admin or not (it calls an admin.dll) and the login name of the current user. I believe I got the dll from NI's website a while back.

Try the OpenG toolkit. It has a function in the OpenG File Tools palette called File Info__ogtk.vi (File Info) that allows you to read the creation date and the modification date.