Why the Poor Run Time Refresh Quality?

Good day,
I've developed a little piece of software to monitor a small amount of inputs from NI DAQ hardware (4 inputs). On my developing computer, everything looks fine but this is not the case on the Run Time computer. Usually the software starts looking fine, but when anything gets redrawn (whether it be from a button press or from another window being placed over it), the image quality is poor. Kinda looks like the color palet in whatever redrawn area gets dropped to 8-bit. I notice this only in the Labview application. Everything else on the PC looks fine when redrawn. Attached is a little image that compares two buttons, the top one having been redrawn. Note the quality difference.
Developed in LV 7.1. Using the RT drivers installed from the NI-DAQmx driver disc (v8.3) (RT 7.1.1)
I've tried rebuilding my app, re-installing my app, re-installing all NI software (on the RT computer), updating video drivers.
Any ideas and help as always will be most appreciated.
Sean
Attachments:
buttons.JPG ‏2 KB

Sorry I didn't respond right away. Got busy on other matters and this issue slipped my mine. Developements have happened...
On coming back to this project, the HD on my laptop died (development comp). Never had any display issues on this machine (was previously posting about issue on computer where app will be run from, where issue still exists). After re-installing everything on my new HD, I'm now experiencing this problem on my development laptop as well.
I'm using an IBM Thinkpad T30 (P4-M, 2.0GHz, 256MB, ATI 7500 Mobility). So it used to display fine on this machine, now it doesn't, and I'm experiencing the same symptoms: grainy display from what appears to be a lower resolution colour palette (maybe 256).
Here too, this is only an issue within the development environment. The startup Labview splash screen looks fine (again LV7.1), the blue bar along the top of all windows transitions from the darker shade of blue to the lighter shade, properly. This issue is on the toolbar and in the developement area within Labview only.
It's weird how this appears to just come or just go. I don't remember who, but somebody here mentioned how their problem just stopped as suddenly as it started. And as this is localized to LV, I'm inclined to think this is not the video card, but perhaps some file/driver/dll that perhaps gets modified/updated without direct visibility. I briefly had this issue aswell on an older Toshiba laptop about a year ago, but it eventually "fixed" itself aswell (don't remember model/specs of older Toshiba).
Anymore help and research into the issue will be most appreciated.
Sean

Similar Messages

Why do different versions of the LabVIEW Run-Time Engine not compatible?

LabVIEW Run-Time Engine to become more and more big
Why do different versions of the LabVIEW Run-Time Engine not compatible?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview
Solved!
Go to Solution.

jwdz wrote:
LabVIEW2020 ....... ，it look like?
You need to express your ideas more clearly. We cannot fill in the blanks and read between the lines if the post has no substance.
jwdz wrote:
It will affect the future development of LabVIEW, right?
What is "it"?
There are many things that affect the future development of LabVIEW, starting with NI management, all the smart people in LabVIEW development, the economy, the LabVIEW users, etc.
If you are worried about the increasing size of the distribution, the good news is that the cost of data storage and data transmission has dropped much more dramatically. Even though newer versions are bigger due to great and welcome new features, the improvements in infrastructure have actually made the distribution and storage significantly easier over the years and will continue to do so. Trust me!
Nobody wants to go back to a LabVIEW version that fits on a floppy disk!
LabVIEW Champion . Do more with less code and in less time .

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
Uninstalled DAQ and reinstalled. MAX still throws an error.
Any Isead besides uninstalling 3/4 of my software?
Merry Christmas!
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility. To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue. Thank you!

Unable to locate the LabVIEW Run-Time engine

Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
I can't go forward or backwards!
Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
What could be causing this problem, and how do I get past it??
Thank you.

One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
Good luck.
Dan

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

System Error 998 While loading the Labview Run-Time Engine

Hello.
I have a DLL made with LV 7.1 I run the dll using a C compiler and works great in WINXP, but cannot run in Win2K. Error is:
"System error 998 while loading the Labview Run-Time Engin(c:\program
files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
READVOLTAGE requires a version 7.1 (or compatible) Labview Runtime
Engine. Please contact the vendor of READVOLTAGE to correct this
problem"
READVOLTAGE is my function inside the dll. The runtime is already
installed. I tried it in another WINXP running machine and works fine.

This is actually a Microsoft bug with statically loaded DLLs. There are a couple of workarounds for it, and I have included two links below to posts that address this issue:
Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC
I get error 998 when calling a LabVIEW buildt DLL from MSVC++
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC? I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
Thanks!
Solved!
Go to Solution.

I'm guessing this is a bug that NI needs to fix. I see no reason you shouldn't be able to install the run-time engine of an older version. I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine. There are some command line switches for NI installers as mentioned here:
http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
I wonder if there is a force install option.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

How to include the visa run-time into the installer?

Dear All,
          I made an USB device whose driver is developed by "NI visa driver development wizard".
          In my program, the COM is also be used. When it is builded and creats the installer, I have checked the Serial Port Suport in Advanced settings in Installer which I thought the visa run-time engine is concluded. In fact, when it is installed, the COM can work correctly, but the USB device's driver can't be installed. To fix it, the visa run-time engine must be setupped again.
          I see that I can add it to "run executable after installation" but during the installaion of run-time engine, some pages will be displayed which need user to choose some option.
         Would you please give some suggestion that the process of installation is automatic. Certainly the part of visa run-time engine which the USB driver is needed can be integrated to the installer of vi(like COM) is best.
          Thank you!
Hugo
PS: I am using LabVIEW 7.1

First, you can install a VISA Runtime Engine in the target PC, to verify it is VISA Run Time Engine issue.
If so, you can add a VISA Run Time Engine in LabVIEW when creating an Installer. It is much easy in LabVIEW 8 and still possible in LabVIEW 7.1. Follow the link.
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E?OpenDocument

System error 999 while loading the Labview Run-Time Engin

Bonjour à tous,
J’ai un PC avec un Runtime LV71.1 qui me retourne l’erreur suivante. Je ne trouve pas d’info sur cette erreur. Une Idée sur la cause ?
System error 999 while loading the Labview Run-Time Engin(c:\program files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW
Résolu !
Accéder à la solution.

Bonjour Maxime, merci pour ta réponse qui est très intéressante. Le soft est en LV7.1.1 est fonctionne depuis plusieurs années. Le PC est chez un client, dans un pays très « hostile », je n’ai donc pas accès à ce dernier. Un superviseur local m’a fait le retour qu’après redémarrage du PC ce dernier indiquait un problème, avec photo pour descriptif. Je n’ai pas plus d’info pour le moment. Je viens donc de demander un CHKDSK c: /F
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

Does Vision Development Module obviate the need for the Vision Run Time Engine?

I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated. In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons). Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs. I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers. I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine). Does this mean the engine is already installed and ready to run compiled applications? Or do we need to pay for the engine on each computer?

The Development module includes the RTE for that machine.
For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

System Error 31 while loading the LabVIEW Run-Time Engine

I'm getting the following error message. I've attached a screen shot of it as well.
System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
I'm trying to update an instrument running Windows95. What is system error 31? I can't find anything on it using Google or the forum's search function.
The instrument is a Romulus-IIIA from Quad Group. I'm pursuing assistance from them as well.
Solved!
Go to Solution.
Attachments:
Winzeta Error LabVIEW.JPG ‏17 KB

Howdy Szandstra,
Check out this KnowledgeBase article describing what you are seeing. Follow the steps there to correct the problem. Have a great day, and let me know if that solution doesn't work for you!
Sincerely,
Chris G in AE

Can I use the labview run-time engine 2010 with my LV 2012 program?

Hi all,
I will receive the new Labview Developer Suite 2012 DS2 in a few days and
I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
Stay Hungry, Stay Foolish
Solved!
Go to Solution.

Hi Benjamin,
You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications. Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
The following links direct you to our download pages for the run-time engine:
The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
Hope this helps.
Marshall B
Applications Engineer
National Instruments UK & Ireland

Package the Air Run Time

Hi Everyone,
I need to package the Air run time in my air application
When i am installing the my air application in a system if the system doest have Air runtime environment .My air application has to install run time and then application.
How to do this ?I dont want badge.swf approach..Please tell me any another way to do that..
Thanks in advance.
Thanks,
Tinu

Don't use Jinitiator, use Sun JRE.
Then, be sure that you have the correct Java version in your formsweb.cfg.
If you google for "oracle forms sun jre" you will find plenty of postings on how to set up the config file for IE and Mozilla.
A tip: if you are sure all the clients have the correct jre version (e.g. 1.6.*), skip the version altogether in the Mozilla section:
--jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06
jpi_mimetype=application/x-java-applet

Analog capture into DV format. Why such small files? Why the poor quality?

I am capturing 8mm video cassettes with an "ADVC 3000" converter, using an S-Video into the converter and then via FireWire into my PowerMac G5.
All is almost going well, but the files seem to take up so little space on my Hard Drive. That's a good thing, but I'm wondering if it's recording into Digital Video or not since the files seem so small. Smaller than normal for DV at least, or maybe I'm just paranoid.
In the scratch files, when I press Command-I for information, the Codecs on the QuickTime files are DV/DVCPRO-NTSC, Interger (Big Endian), Timecode.
So I'm guessing they are DV files even though they look like crap.
My question is this though. When I put these old analog tapes on iDVD, burn it, and put it in my DVD player, the quality of my video looks pretty crappy on my hi-def television. But when I watch them on my computer in a tiny window (the tinier the better), the video looks great. A large window, or my Television, gives a bad picture. My theory is that it's my hi-def television and computer monitor, and that on an old Analog TV set, the videos would look much sharper.
Should I play 8 mm analog video, converted to DV in Final Cut Pro, on an older Analog T.V. set for best viewing results?
Anyone have any comments to share on the science of this?

Yoshiman,
Forgive me if you did know this, the TBC is a Time Base Corrector. (I am pretty sure corrector is right). Anyway, the 8mm has time code striped on it with the image information. If the playback device is not able to read the time code, the picture quality suffers. (remember tracking adjustments?).
The TBC will intercept the time code coming from the tape and provide accurate, consistent time code to the system. I use one from DataVideo, and have been happy with it whenever I have to work with old tapes. If you have a lot of tapes to capture, you might look into one.
My two disclaimers: this is a very general explanation, I simply don't know the physics of what's going on, and secondly I am not a power user of FCS, but have gotten so much from this forum I am trying to give a little back. Take what I bring to the table with that in mind - I'm proficient, but not an expert.

Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

When I try to run a VI that is reentrant in parallel execution, I receive this error. The details of the error is: LabVIEW: The property or method is not supported in this version of LabVIEW.
This is run under the Simple Operator Interface in LV 2010. The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
Can anyone reproduce this error (bug?) ?
Solved!
Go to Solution.

have you got the latest updates for TestStand using LabVIEW 2010?
http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
Regards
Ray Farmer

Why the Poor Run Time Refresh Quality?

Similar Messages

Maybe you are looking for