bmoyer

I'm not saying this is the cause, but if you say 64-bit XP to NI they say:

http://digital.ni.com/public.nsf/allkb/C4EC0C87B6D70AA886256E61006568C8

Also see:

http://zone.ni.com/devzone/cda/tut/p/id/5709

Bruce

This library is only available in 8.6+.

I guess I could back save it to previous versions. I currently use the .NET method for my programs which are currently in 8.5.1 and I sometimes got complaints that a .NET error occurred (when they didn't have .NET installed). I put in a workaround (hardcoding the version in the code and use that if .NET isn't installed), but this would be better.

Thanks for the pointer!

Bruce

Try asking your computer lab admin if you can borrow the CDs. Nowadays the Evaluation and other versions are the same, just different activation.

I tried searching the FTP site for you but couldn't find it. The new version is at http://ftp.ni.com/evaluation/labview/ekit/other/downloader/LV2009_ENG_32_downloader.exe but when I manually went to that directory I could not view the files even though the download works.

LV2009 Evaluation is at: https://lumen.ni.com/nicif/us/lveval/content.xhtml

Bruce

Just a idea, (I have not tested this)

A array of diffrent image(yes I know that will be many ). and some code in the back that select the correct image based on the local time.

This isn't easy but you would have to make a picture for each state of the needle (with a transparent background) and then import it into a transparent picture ring. You would need 4 picture rings. Hours, minutes, seconds, and pendulum.

I've create a VI to prove the concept but it's nowhere near complete. If you have a gif of what you want to do you could probably extract the pictures and then import them into the picture ring.

Good luck,

Bruce

Clock.vi

I recently encountered a bug that is in 8.x versions of LabVIEW (and probably in 2009) and a CAR has been issued (#182933).

Hidden objects don't move when resizing a window, which causes display problems when you want to show them. I've attached a sample VI demonstrating the problem.

Bruce

http://forums.ni.com/ni/board/message?board.id=170&message.id=432116#M432116

Resize Window while Control Hidden Test.vi

QUOTE (BrokenArrow @ Jun 4 2009, 03:59 PM)

Yep, after two weeks of support calls and a VI method of exporting as a work-around, that's NI's take on it too. I was told to uninstall MAX, but that can only be done by uninstalling everything that touches MAX, which is everything.

MAX is a horrendously complex and ever-morphing, capable of changing its own code and causing ripples in the space time thingy.

I think the release of the software included with LabVIEW 8.6.1 NI Developer Suite was the straw that broke the camel's back. For some reason I've had utmost problems having this version of the developer suite along side of other versions of LabVIEW. Previously I had LV6.1, 7.11, 8.0, 8.5.1, all installed concurrently with little difficulty, but 8.6.1 doesn't seem to want to play nicely with these other versions! It's the bad brother of LabVIEW versions. I hope that the next release plays a little bit more fairly.

Bruce

QUOTE (sbev001 @ Jun 1 2009, 10:26 AM)

Hi, sorry I know that this question is probably very basic but I am new to LabVIEW and still figuring it all out. How would I go about building an algorithm tha will take the values from a 2-D array and integrate them (I need to integrate current with respect to time). Should I use a for loop or while loop?

My guess would be a for loop, unless you want to stop at a particular value or something special like that. You need to know the format of the 2d array as well. If you put a 2d array into a for loop it will automatically index on each row. If you have a column for time and a column for value it you may not even need a for loop at all. Look at the Index array function to get all the data from a particular column (assuming you have the data organized like this). There's a palette for doing integration in the Mathematics palette you can look at (but you may not have access to this palette depending on the type of LabVIEW package you have.

Spend some time and poke around. Ctrl-H gives a pop-up help and usually more help if you click on the link in the pop-up help.

Bruce

QUOTE (ShaunR @ May 29 2009, 02:03 PM)

The fact that you need a license unlike any other language maybe??

That's because LabVIEW developers are crooks! Unlike other languages where they are all law abiding citizens. NI, what have you done to us?!

QUOTE (PJM_labview @ May 21 2009, 01:18 PM)

This is a bummer (in my opinion I am "loosing" a column of about 120 to 150 pixels of real estate space because of this). I will try to remember to ping you about it at NI week.

PJM

The minimum size of the project window is actually larger than the default size! When you create a new project window, it actually snaps to a larger size when you resize the window and then doesn't let you put it back to the original size! Seems to be a "feature" in LV8.6 only (LV8.5.1 is still good).

Bruce

QUOTE (normandinf @ May 21 2009, 04:54 PM)

OK, I've reinstalled 7.1 and here's what I did:

I created a colorbox constant (7.1) and resized it. I saved and opened this VI in 8.6. I got a resized colorbox (not reverted to standard size) but it was no longer resizable...

That's what I suspected. It seems like they get locked when going from 7.1 to 8.x. Thank goodness they're still resizable as controls!

Bruce

Not sure about all the class hierarchy stuff, but in 7.1 it could be found in the palette, Numeric-->Additional Numeric Contants-->Color Box Constant. Now it's located in the palette, Graphics & Sound-->Picture Functions-->Color Box Constant.

I know this may seem a little bit whiny, but I just noticed that as of LV8.0 the color box constants on the diagram are not resizable (as far as I know).

A program that was developed in LV7.1 had a 2d-array of color boxes on the diagram to represent to the programmer the ratio of the dimensions of the actual object. Now I'm stuck with square color box constants (from the palette). :thumbdown:

I'm sure there was a good reason for this. Maybe it was an attempt to make the color box constant more constant.

Bruce

I was able to get my code to compile to an exe that is executable by uninstalling IMAQ 4.1 (Vision Acquisition Software 8.6) and installing IMAQ 3.8 (VAS 8.5). I avoid IMAQ 4.0 because the structure of the .iid (for instance img0.iid) files is messed up (see NI forum iid file structure in IMAQ 4.0 changed). This bug is fixed in IMAQ 4.1 but apparently there are other new bugs that were introduced.

Days lost, totally frustrating. Not a good LabVIEW/NI experience. And I'm stuck using old software versions to get things to work.

Bruce

P.S. I've been cross posting to NI as well (Why is Building an exe in LabVIEW 8.6.1 so slow?) about similar issues regarding my upgrading experience.

Bruce

I am in the process of upgrading a program from LabVIEW 7.1.1 to LabVIEW 8.5.1 (I've also tried LV8.6.1f1) and am having difficulties getting the built exe to function. When running the exe, Windows gives a crash error dialog "Blah Blah Blah.exe has encountered a problem and needs to close. We are sorry for the inconvenience.". When I click the click here link it refers to the "nivision.dll".

AppName: Blah Blah Blah.exe AppVer: 5.0.0.0 ModName: nivision.dll

ModVer: 8.6.0.49152 Offset: 00014715

I'm not sure why this error is occurring since I was able to build (and run) the exe in LV7.1.1.

I also noticed that when building the exe it gets to the end and then takes a long time to complete (almost like a timeout is occurring).

Is there a way to search for this dll to temporarily remove it to see if this fixes the problem? (I know that it is from the VISION toolkit).

Thanks,

Bruce

QUOTE (paramesium @ Apr 14 2009, 09:45 AM)

halo ...this is part of my programme

everything is working fine including the saving and open part

but heres the problem...

when i trying to cancel the save... it show me the error message as below

This is probably caused by the Automatic Error Handling which only takes effect when running in the development environment (when running the source code). Either wire up the error cluster to properly handle this error or turn off automatic error handling (from the "Tools" menu, select "Options..." the click "Block Diagram" and then uncheck the "Enable automatic error handling dialogs" checkbox).

QUOTE (nature @ Mar 16 2009, 07:18 AM)

hi u have alredy completed rs232 interfacing with hyperterminal.i m trying on dat from 2 weeks bt it showin nothin in hyperterminal.i have set baudrate of 1200 for 16mhz crystal is it k na? i m attaching both dia n code here u plz tel me wat to do?

hi...m doin my final sem pro n in dat i want to interact pc with rs232 n rs232 wil get data via 89c51.i want to create such platform in labview..can u plz suggest me hw?

i have tried for 2 weeks interfacing rs232 n 89c51 n watching output in hyperterminal bt its nt showin anything.

i m attaching hardware n code here u plz check it n tel me whr its wrng?

Srry, i dn't spk/wrt th sm lngge s u (Sorry, I don't speak/write the same language as you). This is an English forum, so please write in English.

Bruce

It took 0.046 seconds to read for me! Seems pretty fast actually.

Bruce

I haven't used it, but the Image Toolbox http://www.geocities.com/gzou999/imgtool.htm has a PCX read file VI.

Wikipedia also gives a very good description of the file format: http://en.wikipedia.org/wiki/PCX

Bruce

After LabVIEW loads select the Help-->Find Examples... menu.

See screenshot for the details in the NI Example Finder.

QUOTE (rolfk @ Feb 20 2009, 01:10 AM)

DAQmx on VirtualPC??? VirtualPC is simply a virtual machine from Microsoft much like VmWare. I can't really believe that VirtualPC does virtualize the PC Hardware to the point that DAQmx can really work on there.

Well, it seems it does work , which is quite amazing if you ask me.

Rolf Kalbermatter

I would imagine you can probably get the USB-DAQ devices to work since most virtual environments support USB functionality. Even if the DAQ devices are not USB you can probably still get the simulated devices to work.

I agree that the error dialog should be improved. When I had an IMAQ error with my app (because IMAQ wasn't installed) at least it showed a dialog with 100 or so VIs that it couldn't find that were needed for the exe to work.

Bruce

QUOTE (george seifert @ Feb 19 2009, 01:26 PM)

It's fixed. Installing NI-DAQmx 8.8 solved it. Which is weird because the installer installed MAX and NI-DAQmx. The installer did a minimal install though so maybe the full install provided something else.

George

That was my guess too when you said that you were using DAQmx, that the driver wasn't installed properly. Well its good that the problem has been resolved (although not fully understood).

Bruce

QUOTE (george seifert @ Feb 19 2009, 11:07 AM)

I'm not trying to be a wise guy, but how else would I have done it?

Sorry, wasn't trying to insult your intelligence. Wasn't sure if you or your user was installing it. Sometimes users think they can install an application by just copying the exe.

I don't use VirtualPC much anymore (I've switched to the free Sun VirtualBox because it wasn't free for the Mac and VirtualBox is also available for Ubuntu, RedHat, etc.) because I have both Mac and PCs operating but I have tested Installers on VirtualBox to see if they're any problems when installing to a "clean" PC on Windows.

My apps didn't have DAQmx but they did have hardware drivers (such as Vision Acquisition Software (VAS/IMAQ)) and they worked fine, as long I had IMAQ installed on the VirtualBox (of course I got an error when trying to use hardware that didn't virtually exist). If I didn't have VAS installed my executable broke (like you described).

Not sure if this helps at all, but these problems are usually easy to fix but difficult to find.

Bruce

QUOTE (george seifert @ Feb 19 2009, 08:34 AM)

I've built an executable that installs and run fine on a normal PC running Windows XP. But I have a user that installed it on a virtual PC (never actually heard of that before) and it comes up with a broken run arrow. The error says the VI is not executable and that the full development system is needed to run the VI. I checked and it looks like all the components are installed (run time engine, etc.). Any ideas what could be going on?

George

You used an installer to install it on the Virtual PC? Does it post a dialog saying anything is missing? Do you have any specialized calls (such as .NET) that are not installed on the Virtual PC?

Bruce

I'd like to create an application with a GUI that is similar to a Airport Flight Info display and the application needs to periodically check for changes to an excel file (for now, we'll talk about adding database support later) and then update the display. The information would smoothly scroll vertically through all of the rows and then repeat continuously. At first I was thinking about using Powerpoint to do this (but I don't know if this is easily possible in PP). I think this could be done in LabVIEW quite nicely. What do you think is the best way to go about this?

Using LabVIEW, my idea is to use multiple panes and have a header pane and a table pane and use property nodes to scroll the table pane continuously. Any thoughts? Is there a better way to go about this?

Thanks,

Bruce

QUOTE (hooovahh @ Feb 9 2009, 09:30 AM)

Also not sure if people have seen this or not but NI has officially released their unit test framework

http://zone.ni.com/devzone/cda/tut/p/id/8082

I haven't used it yet but I hear that it should become a common used tool around the office.

The ~$1500 price tag should slow that down a little. Is it included with the Professional version (my guess would be probably not)?

Bruce