Citi AA Executive

CreditCuriousity wrote:
Irish80 wrote:
CreditCuriousity wrote:
Wow Congrats Irish! Alot of spend, but you have alot of AA miles now don't you? How many do you have if you don't mind me asking.. Assuminig the ones from this offer are included? 200k? Some nice trips ahead of you!With this, I'll have close to 300K AA milesNice lots of mile.. I still can't get over that spend of 7.5k, think that might be the highest I have seen on a non-business card for bonus? Yeah, it's pretty high but I have plans in place :-)

Imperfectfuture wrote:
Irish80 wrote:
CreditCuriousity wrote:
Wow Congrats Irish! Alot of spend, but you have alot of AA miles now don't you? How many do you have if you don't mind me asking.. Assuminig the ones from this offer are included? 200k? Some nice trips ahead of you!With this, I'll have close to 300K AA milesWow, congrats. Might want to consider diversity in lenders for keeping purposes, and see how often Barclays runs the 50% more miles promo.I'm definitely leaning towards the Barclays card as my go to AA card. I upgraded to the Silver and with that I get 3X miles instead of 2X with both the Citi cards. Ideally I'd love to be able to eventually close out the two Citi AA cards and end up with a $75K limit on the Prestige but not sure they'll go for the CapOne approach.

Similar Messages

Improving load times in Linux LabVIEW executable

I'm looking for (simple) ways to improve the loading times in a Linux LabVIEW executable. We're using a low performance, low cost CPU board, and loading times are terrible. The CPU is capable of doing everything after the application is loaded, but takes forever to get there.
One of the problems is the size of the executable, that grows everytime you just look at it. Are there ways to create smaller executables? It runs from a Compact Flash card, which is ofcourse much slower than hard disk.
Another problem is a dynamic vi, that is started for every TCP connection that connects to the application. It takes a long time to load, and connecting too fast can even effectively hang up the system. Starting a handler task takes about half a second, up to a few seconds for the first task.
We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.

Dennisvr wrote:
I'm looking for
(simple) ways to improve the loading times in a Linux LabVIEW
executable. We're using a low performance, low cost CPU board, and
loading times are terrible. The CPU is capable of doing everything
after the application is loaded, but takes forever to get there. One
of the problems is the size of the executable, that grows everytime you
just look at it. Are there ways to create smaller executables? It runs
from a Compact Flash card, which is ofcourse much slower than hard disk. Another
problem is a dynamic vi, that is started for every TCP connection that
connects to the application. It takes a long time to load, and
connecting too fast can even effectively hang up the system. Starting a
handler task takes about half a second, up to a few seconds for the
first task. We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.
I'm
not sure about the first part of your question. LabVIEW is highly
binary and does a lot of memory allocations before even one VI is ready
to be started. So maybe the memory manager is a problem. Another issue
is that the Macintosh like resource file format that is used by LabVIEW to store its VIs etc. results in
lots and lots of individual disk accesses with a rther random like
character inside a single file. So if you can configure the read
caching of your disk to use more memory this may significantly increase
the speed of loading LabVIEW VIs or applications.
And finally spawning VIs through VI server is a rather costly operation
especially on low resoruce systems. A VI is more like an executable in
many ways as far as resource consumption is concerned rather than a
thread. A much better way would be to avoid spawning subVIs altogether
and implement a queued TCP/IP server similar to the Date Time Server
example. It is a little extra work to work with this shift register
architecture but it will not have the issues of long load times for
every new TCP/IP connection coming in.
Rolf Kalbermatter
Message Edited by rolfk on 03-07-2006 06:33 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Do I need to set something when using Dynamic VIs to pass control values to an executable VI

I am using VI server to pass control information from one VI to another.
In the development system this works fine.
How ever once I build the VI's into an executable the values from one of the VIs does not get passed.
I use the same method in three different applications, 2 of the applications work fine, but one does not.
The only thing I can think of is that there is something that needs to be set that I did (without realizing) in the first two but not in the third.
All the Applications run fine.
The problem that occurs is in the values passed. The same value gets passed everytime this turns out to be what ever the default was prior to running application builder.
I a
m currently using 6.02.

Kandrew wrote:
> I am using VI server to pass control information from one VI to
> another.
> In the development system this works fine.
> How ever once I build the VI's into an executable the values from one
> of the VIs does not get passed.
>
> I use the same method in three different applications, 2 of the
> applications work fine, but one does not.
Are you using Call by Reference or Set Control Value method? The second
absolutely requires the Front Panel to be present to work properly. The
LabVIEW application builder wants to remove the Front Panel by default
if the VI hasn't been configured to show its front panel when called or
doesn't have at least one Control Property Node in its diagram.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

10133 ADF: How to stop search button to execute when there is an error

Hi,
I have two dropdownlists in a search criteria on a search page. The search result is at the bottom of the same page. The two values in the dropdownlists need to be validated when the search button is clicked. The validation logic is put in the searchBtn_action method binded to the search button. In the logic, when an invalid combination happens, I am able to post some error message on top of the page. But how can I stop the application to execute the sql statement? I mean if there is any method I can call to exit if there is an error? Thank you very much.
Regards,
Annie

This is most likely an optimization problem. I know such behaviour existed in the past with some functions and NI usually fixed it in some later release, but the recent changes in the LabVIEW compiler to use LLVM and various optimization improvements may have added this "feature" back in. The default value behaviour is certainly correct and consistent but the behaviour without default value feels not right to me for LabVIEW. In C I would say ok this is simply undefined behaviour and that means the produced code is entitled to even format your harddisk, since C explicitedly says all undefined behaviour is subject to choices by the implementor and is allowed to do whatever the implementor sees fit, including changing behavior between any version of the compiler.
But LabVIEW as a high level language has explicitedly so called default default data, which in this case should be used. Just having read a bit about LLVM I know they are wrestling with C undefined behaviour as well and LLVM being used a backend by several C compilers already has to deal with them. The reason that C explicitedly has many undefined behaviours is to allow various and sometimes significant optimizations, that could not be done, if the C standard would explicitedly require specific behaviour in certain cases (for instance uninitialized variables).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to assign file extension and custom icon to executable?

Hi all,
I was reading an old thread about this issue:
http://forums.ni.com/ni/board/message?board.id=170&thread.id=116925
I need to try to do this. My application uses a custom file extension (i.e. .abc). Upon installation I would like to:
1. Assign My App and custom icon to the file class (extension .abc).
This could be done by manipluting the registry (http://msdn.microsoft.com/en-us/library/bb776856(VS.85).aspx)? This could be a problem with Vista s unless registry operations occur during installation any changes are placed in a VirtualStore, correct?
2. Enable the double-clicking of .abc file type to pass the data in the file to my VI (exe).
According to the File Handling Guidelines of Jean-Pierre Drolet (http://www.openg.org/tiki/tiki-index.php?page=File+Handling+Guidelines) the best way to do this may be using LabVIEW as an ActiveX server.
I know that when I build an executable (or installer?) there is the option to enable LabVIEW to act as an ActiveX server. This much I know I need to do.
I thought I would open this discussion again as others may be interested and there doesn't appear to be a completely clear solution available. Please do contribute where you can.
Cheers,
Battler.

battler. wrote:
My application consists of Event Structure.
How to register for ommand line event so that when a user double-clicks on a .abc file I can handle the opening of it?
This needs to work (the files need to open) not only when the application is closed but also when it's already open.
Anyone have ideas?
The solution to that is to implement a DDE server in your application (and add DDE entries to the registry on installation). There are still DDE functions in LabVIEW vi.lib\Platform\dde.llb but they are considered depreciated and have been removed from the palette, also because Microsoft is trying to tell everyone that DDE is depreciated and sort of unsupported too. But it is still the mechanisme to pass actions from the shell to running applications.
I hesitate to send you over to lavag.org where there have been some discussions about this years ago. If you go there you would do good to employ a friendly attitude. That board is run all by enthusiasts and idealists and they are all great folks but react not very friendly to people with an attitude.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to Add New Parameter in Cluster with LabVIEW Executable Program?

   In this VI，it can write the parameter in Cluster to the database (Access 2003).it run well.
   But When I add another parameter in Cluster,such as EE,I have to modify this Cluster. And at the same time,I have to modiy the database (I should add a column of EE).if this vi build to exe, how can I achieve it?Can LabVIEW have any way to increase new parameter EE in Cluster and in Database in executable program?
   Would you give me some advice?Thank you
Attachments:
Add ParaMeter In Cluster 20130206.zip ‏105 KB
Cluster.JPG ‏9 KB

It's rather unclear what you try to do here. In your first post you talk IMHO about the high level Datatbase Toolkit functions that take a cluster and translate it automagically into the appropriate SQL Query/Update.
Your second question seems to be about the user interface of your application.
Proper application design would mean to separate the user interface aspect from the actual database query in some ways. I definitely wouldn't use the same cluster for both. Also if you simply hide a control on the frontpanel (possible also in an executable) it still is present logically and if you end up using the high level database toolkit functions with that cluster it will result into a query or update of the database with all the data in the cluster, also the hidden ones.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Best way to create a Windows service from a LabVIEW executable?

What would be the best way to run a LabVIEW executable as a service? I needed this recently and I think I have set up such a service using srvany.exe from the Windows 2003 Resource Kit, but that seems like a bit of a hack. The Kit is not offically supported in Server 2008, but seems to work. I don't know about Server 2012 or beyond.
So what would be the "proper" way of going about creating a Windows service from a headless LabVIEW application?

The proper way is to interface to the according Windows service control API. That is however not a trivial task to do. We used to sell a LabVIEW toolkit which supported a full interface to this, but it's not currently actively marketed.
srvany.exe is sort of a hack but works reasonably well for most use cases, as long as you do not need any further interaction with the service manager interface in Windows than to start and stop your service.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Is it possible to run a Labview executable on a Windows 8 Phone?

If I create an executable from Labview,will it be possible to run it on a Windows 8 phone?
Solved!
Go to Solution.

No, as Mike already said.
The reason being that a LabVIEW executable contains binary code that is compiled for the x86 CPU architecture and accesses the Win32 API. Windows Phone typically runs on ARM or RISC CPUs and did only provide a very limited Win32 subset in the past. With the new Windows RT technology it actually moved even further away from Win32 compatibility as it's entire architecture is based on the .Net technology.
So even if you happen to get an Intel Atom based Windows Phone device which would be x86 compatible it couldn't work, since a LabVIEW executable is a Win32 portable executable format not a .Net bytecode image.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Error when building an executable in BridgeVIEW

Hi,
Every time I try to build an executable in BridgeVIEW I get an error that I have to close all VIs before building an EXE, but I only have the top level VI open. I tried shutting down the PC and restarting but nothing works. I have seen this in LabVIEW, but LV closes them for you.
Any ideas?
Thanks.

Lupita wrote:
HI,
You are probably right. So here is what Ive tried:
1) Restarting my PC. Opening a blank new VI and trying to build an application by adding my "main.vi" as a top level VI. This way I make sure there are NO VIs opened.
The list that appears on the Build Application menu contains ALL VIs called by my main.vi.
Thanks again.
I can't really say that I remember a behaviour like this but considering that the latest BridgeVIEW version corresponds to LabVIEW 4.1 (which was never released) or so, I would say that this is so long ago that my memory might be flaky here.
And the application builder back then was also not the same as it is now. I'm afraid unless you are going to use a more recent version of LabVIEW together with the DSC Toolkit (which is basically what BridgeVIEW evolved into) there is little cahnge that anybody can help you with this here.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Wine & Labview Executables?

Is it possible to run LabView executables under wine? Has anyone ever attempted to do this? Thanks for any information.
Regards,
Ken

Kenneth.Miller wrote:
Is it possible to run LabView executables under wine? Has anyone ever attempted to do this? Thanks for any information.
Regards,
Ken
I've tried it several years ago with
LabVIEW 5.1.1 and 6.1 and didn't really have any significant issues
except that everything was sort of sluggish and certain screen updates
left artefacts on the screen. Now Wine has come a long way since but so
has LabVIEW and I doubt somewhat that LabVIEW 8.0.1 would be as
complient with Wine as older versions have been.
All the .Net, Active X and what else more is quite involved and LabVIEW
8.0.1 does not for nothing require Win2000 or XP to run. Wine has on
that area quite some deficiencies related to specific functionality
such as ActiveX/DCOM and does not attempt to provide .Net functionality
at all. Of course you could get Mono into the picture here but last
thing I heard they were trying to sort of modify Wine to get their
system to load properly.
I believe that .Net is optional in that LabVIEW will only weak link to
.Net functionality and did so before with ActiveX/DCOM but since
Win2000 comes with ActiveX support out of the box, this weak linking
might not have been tested properly anymore and might actually fail.
All in all not exactly a good constellation and since LabVIEW for Linux
is available since a long time I haven't bothered about LabVIEW on Wine
for quite some time.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Can I extract the orginal VI's from an executable created by Runtime Engine?

I have an executable program created using the Labview Runtime engine and need to edit the subVI's contained within. Unfortunately, I don't have the original VI's the program was created with.
Is there any way I can extract those VI's?
Thanks,
Mike C.

First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Error 1097 in executable VI

Hi!
I am building an executable version of the VI I created with LabVIEW 2010 to control an oscilloscope we use in our laboratory.
The acquired data are passed through pointers, and the VI uses the DSNewPClr function to create the pointers and the MoveBlock function yo make the data available.
If I run the VI with LabVIEW, I have no problems and everithing works fine.
If I build the executable, I find two problems:
- the program does not find the two functions unless I put a copy of the LabVIEW.exe file inside the same folder (I have the runtime engine installed);
- both functions return a 1097 error, so that the oscilloscope is properly working, but the data are not accessible.
The first problem is solved, but I was wondering if there is a better way to do it.
The second problem makes the program useless...
Is it a known problem or am I doing something wrong?
Thank you for your help!
MikeNuke, PhD student
Politecnico di Milano
Department of Energy, Nuclear Engineering Division
Solved!
Go to Solution.

If you call any LabVIEW memory manager functions through the Call Library Node make sure to define in the Library Name "LabVIEW" sans quotes, and the upper/lowercase is important. This tells LabVIEW to link to whatever kernel is currently executing your VI code. If you enter LabVIEW.exe (case is unimportant under Windows) instead, the Call Library Node correctly wants to see a file LabVIEW.exe to link to. However that will likely cause all kinds of nasty problems since the heap manager in LabVIEW.exe executes in a different process space than your build executable which uses lvrt.dll to execute.
Also be aware that just because you do not get any errors doesn't necessarily mean that your code is correct. Memory pointer management on your own is a very tricky business to do and it is very easy to mess up there. That does not always have to result in an error that LabVIEW can detect to generate the 1097 error, but it will always in some ways corrupt memory.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Labview executable installer cannot find windows favorites

When attempting to install an LabVIEW executable, using the Installer created with LabVIEW, before copying any files or making any changes to the local PC, the setup.exe queries for the location ‘My Favorites’ from the registry (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Favorites). If this has been moved to a mapped network drive, the setup will error saying that it is unable to access this location. Using Sysinternals Process Monitor, the setup.exe process does not try accessing this location.
Thanks in advance for any help
Inigo Rotzer

mikeporter wrote:
But why have favorites mapped like that in the first place?
Possible reasons:
1) Internal IT procedures
2) floating user account setups across the entire network
It's not uncommon to do these things but I have found to many problems with this also outside of LabVIEW to find it a practical solution.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Lancer un executable dans une fenêtre de mon VI

Bonjour,
Je souhaite lancer un executable dans mon VI, comme s'il faisait parti de mon code (pas à l'exterieur)
Pour simplifier les choses, mon programme fera la liste de tous les executables disponibles dans un repertoire défini puis les proposera dans une boite à onglet
Ces executables sont des SFP de ressource
Ainsi je me retrouve avec un applicatif qui contient tous les SFP que j'ai de disponible (je ne pense pas en avoir plus de 10 sur un banc de test)
Pour la gestion de la boite à onglet j'ai trouvé et ca marche bien
Il ne me reste plus qu'a lancer les executables dans les différentes pages et là, je ne vois pas comment faire
je sais que l'on peux lancer des executables à côté, mais cela ne m'interesse pas, je les veux dedans
est-ce faisable ?
D'avance merci
Cordialement
Résolu !
Accéder à la solution.

Hello,
Attention, cette méthode était valable avant, et sur Windows XP (ou antérieur) :
- http://digital.ni.com/public.nsf/allkb/8545726A00272EB0862571DA005B896C?OpenDocument
Pour les raisons citées, désormais on utilise plutôt les bibliothèques empaquetées. Elles sont compilées, donc pas de risque d'avoir de fuite de code :-)
Un très bon début avec cette architecture :
- https://decibel.ni.com/content/docs/DOC-19176
Alternative moins crédible : appeler les exe par la fonction "System Exec", et jouer avec les fonctions Windows (au fond de user32.dll) pour que la fenêtre des exe soit une fenêtre enfant du VI appelant...
A+
--Eric
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

A source distribution created in 32-bit LabView 2009 says that VIs aren't executable when opened in 64-bit LabView 2009. How do I run the main VIs?

A source distribution was made for a VI using 32-bit LabView 2009. The distribution was verified to work on another machine that ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the attached error message. How do I make the VI executable?
Solved!
Go to Solution.
Attachments:
source dist error.JPG ‏70 KB

Seems you have a problem with the installation of the Advanced Analysis Library (AAL) or the Intel Math Kernel Library that is used by the AAL on that 64 bit machine. Can't say for sure if these are already supported on 64 bit LabVIEW. At least a repair installation of LabVIEW seems to be in place.
The other error is from the HSD component not working. Again I can't say if this should even work on 64 bit LabVIEW. If it should a repair installation should be most probably done.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Citi AA Executive

Similar Messages

Maybe you are looking for