Rolf Kalbermatter

QUOTE (manojba @ Apr 3 2009, 02:27 AM) No. While the VI is not executing, the menu bar and toolbar will always be visible. And you really should rethink your application design. A VI that has to be started with the run button is ok if it is a lab type experimental setup to be run in the LabVIEW IDE. But once you built an application you want it to behave as such and not as VI. So create a main loop in your diagram with an event structure inside and make a start button or something on the front panel to start whatever operation you have in your VI now. Rolf Kalbermatter

QUOTE (Mark Yedinak @ Apr 3 2009, 02:43 AM) Are you sure you have really enabled "Defer Front Panel Updates". 3.2 ms for an Add Item Tree element sounds fairly long although I don't have specific numbers. Or was this 3.2 ms with an already heavily populated tree? I do think the suggestion to built up an internal data structure first that represents your tree as an array of clusters and after that populate the tree from that is probably not a bad one. It also gives you better performance check abilities to see if the file enumerating or the tree population is really munching up the big part of your processing time. The other suggestion to only update the tree as it is getting needed (when a folder item is expanded) would be my first approach anyhow. No need to go through a lengthy recursive folder enumeration when the user newer will look at 99% of those items anyhow. Rolf Kalbermatter

QUOTE (ssteven121 @ Apr 1 2009, 04:11 PM) Have you tried reinstalling (or repairing) DAQmx? Rolf Kalbermatter

QUOTE (zythum @ Apr 1 2009, 07:24 AM) No you do call RegisterWindowMessage() but then you do not call SendMessage() but you have to receive that message from the other application and that requires at least intercepting the internal LabVIEW message queue (example I pointed out earlier) but since it is a system message maybe even installing a real Winddows message hook. While the Windows Message Queue example I mentioned earlier would help you with the first, you will have to REALLY write a C code DLL to do the second. Rolf Kalbermatter

QUOTE (SandeepC @ Apr 1 2009, 04:24 AM) Lot of work and I'm sure you can never reach the short latency in this way that the native USB port would provide, at least if you have no bad hubs or such in between. Rolf Kalbermatter

QUOTE (SandeepC @ Mar 31 2009, 11:40 AM) Are you seriously considering to write an USB protocol stack in LabVIEW using the RS-422 IO lines of the 1426 card?????? I would really reconsider that again. USB is NOT RS-422 although with an RS-485 port (bidirectional) you probably could simulate it electrically. But that still leaves you with the USB protocol stack to be implemented. The TTL pins definitly wouldn't be electrically compatible to simulate even the electric aspects of USB. Why are you even considering to connect that device to this framegrabber. Wouldn't be a direct USB port on the computer where this board is plugged in be a lot easier? Rolf Kalbermatter

QUOTE (zythum @ Mar 31 2009, 03:26 PM) Yes a good start but the most easy thing of all. That example is about posting a message to another application. That is simple, even trivial. You need to wait for a message from the other applciation, that is a lot more involved. Rolf Kalbermatter

QUOTE (karthik @ Aug 17 2007, 09:06 AM) One thing I have noticed is that at some point Agilent, then still HP was marketing Vee rather agressively trying to get every LabVIEW account they could. This has changed a lot in the last 8 years. Now they try to market it together with their devices to Agilent shops (customers heavily using Agilent devices) mostly and seem to have abandoned most other venues to sell it. As such it would seem to me to have a rather limited user base. It certainly is second to none if you only have to deal with Agilent devices and like the way you have to think and program in Vee, but for most anything else it has no advantages to LabVIEW and IMO, a lot of disadvantages, but it's been a long time since I played with an evalution version of it. Rolf Kalbermatter

QUOTE (No.1 @ Mar 30 2009, 08:56 PM) Neither am I. I use my own ODBC based VI library and ODBC does not know an explicit cancel method but you simply close the statement handle (a specific query or other SQL statment execution) with an option to force it. What that does on the server side is however quite a different story since it is ODBC driver specific. It could communicate the closing of the statement to the server and cause it to abort any ongoing activity on that statement but it could also just close the handle on the client side and let the server continue with whatever it is doing, eventually discarding any response from the server it gets for this particular statement. Rolf Kalbermatter

QUOTE (Mark Yedinak @ Mar 30 2009, 04:35 PM) This would seem mostly a useless restriction to me unless for security reasons, when you want to restrict the firewall passthrough both on the outgoing and incoming side. Rolf Kalbermatter

QUOTE (No.1 @ Mar 29 2009, 10:41 PM) By not using high level VIs but taking apart your query into at least an Execute query and the actual data retrieval. If you close the statement or result set reference before you actually retrieve the data, the query should be dropped and any already generated data with it. You probably need to find a way to see if the query already produced some data before starting the retrieval as it might not be possible to cancel an already started data retrieval. You can try it out however if closing the result set reference in another part of the code does maybe abort the data retrieval too. Rolf Kalbermatter

QUOTE (hma @ Jun 8 2007, 08:02 AM) I understand now what you want, but don't feel this type of Tab Control is ergonomic in any way. I usually feel annoyed whenever I see a tab control that goes over more than one line of tabs. The variant with scrollarrows to the right to scroll through more tabs than what is possible to put on the screen is only slightly better IMO. Personally I prefer for cases like this the array index display approach with a Pull Down menu control or a List Box control being the element selector and the rest of the page presenting the currently selected array element. And that is not just because it is easier to do in LabVIEW than the multi row tab control . Rolf Kalbermatter

QUOTE (Clio75 @ Mar 27 2009, 04:37 PM) Scan from String will not have this problem. And if you know you could have numbers with a specific decimal point instead of the current system decimal point (instrument responses for instance) you just prepend the %.; to the format string. Rolf Kalbermatter

QUOTE (xavier30 @ Mar 27 2009, 11:17 AM) So you are supposedly using the Call Library Node to call those external Libraries. Ever checked (really really throughfully) that you pass all the right data types to the Shared lib, and most importantly never pass in an array or string buffer to the lib to be filled in by this library that could be to small? The fact that it works in the IDE or on Windows means really nothing in the case of such problems. The buffer you pass into the library might often border non vital data that gets corrupted too, but won't cause a fatal crash or it might be even so that it is a buffer for a filepath that is shorter in those other situations never overwriting illegal memory except in the runtime installation. Lots of things to consider here, but using the Call Library Node and testing your application to not crash on one specific installation/built is really not enough. You really ought to validate every single Call Library Node to have all the data types right and most importatnly either have no output data buffer (array or string filled in by the library) or that those buffers are under all possible circumstances preallocated large enough in the LabVIEW diagram. Rolf Kalbermatter

QUOTE (ned @ Mar 28 2009, 02:01 PM) Ben is right. No need to request the TCP Open to open a specific local port at all. Just leave the local port input empty, which tells LabVIEW to let the OS select whatever port it can. For a client (No TCP Listen used) only the remote port is normally important, except with some strange protocols sometimes. Rolf Kalbermatter

QUOTE (zythum @ Mar 27 2009, 11:33 AM) While File Mappings aren't that difficult, the Windows API to deal with that is a bit more complex then just accessing a single function. So this part while in theory possible to be dealt with directly from the diagram using the Call Library Node is actually better handled in an external C DLL, that deals with these problems directly and offers LabVIEW a clean and easy to access interface. The real killer however is the Windows message handling that is required. To implement that in LabVIEW only is not possible, since there is no way for you as LabVIEW programmer to intercept specific Windows messages. There is a Windows_Message_Queue example on the NI site that offers a C++ DLL to do that, but it is not exactly for what you need and you will have to modify it to work for your purposes. So I would simply create a complete new DLL and put everything in there. If I would have to do that I would estimate about 1 day of work for this to get a reliably working DLL and two or three LabVIEW VIs to access this. Now I do have a lot of experience with external C code integration in LabVIEW, so if you are gonna do that expect to have quite a bit longer for this and be willing to learn C to a level that goes well beyond beginners level. Rolf Kalbermatter

QUOTE (EHM @ Mar 26 2009, 10:37 PM) Not sure about your proxy but I did not add the Host: xxxxxxxxxxxx in the past to my proxy requests and that worked. The Host can be added according to the RFC for forward compatibility but I don't think it is required. The absolute URI however seems to be at least for older HTTP versions a requirement. I did however use HTTP/1.0 as version indication so maybe that is why. And last but not least: are you sure there is an index.html document on the server. It could be index.htm or something entirely different so as a start I would try just the server address http://www.example.com/ without any document path. Rolf Kalbermatter

QUOTE (jlokanis @ Mar 24 2009, 02:16 PM) Anything special about your setup? Project or project VIs on a network drive? LabVIEW starting up from a network drive? It seems that there must be something like this. Something similar though not to LabVIEW only I see on my machine if I do not have a connection to my VPN server. Presumably because I have a path somewhere in the registry that points to a location on a shared drive only available when logged in through VPN. But Widnows seems to check that path anyhow everytime I click on a file in Explorer . It's annoying but not annoying enough to really dig through the registry to find the offending entry. Rolf Kalbermatter

QUOTE (Yair @ Mar 24 2009, 01:55 PM) I hadn't noticed at first but if you go to his blog he has linked to, you can find some info about things he did. Seems he likes to tinker with computers and some of what is written there certainly is on the border of legality. Might be using dads LabVIEW copy or whatever and taking his last few inquiries together he might be just looking for things to crack, probably more to boost about than anything else. Rolf Kalbermatter

QUOTE (NeilA @ Mar 23 2009, 02:19 PM) What your ActiveX node requires is not directly a GUID but an object reference to one. Most likely because it requires it as the binary form of a GUID and not as string. Why someone would make an ActiveX interface like that is beyond me but here it is. You could try with Variant to Data. Failing that you will have to find out what reference class that node expects (you could try to right click on it and create a FP control and inspect its ActiveX class name). If that works you will have to find out how to instantiate such an object on your system and then find the method that intializes it with the string form of your GUID. Rolf Kalbermatter

QUOTE (BOBILLIER @ Mar 23 2009, 05:13 PM) So what speaks against making your LabVIEW application work in the format that the current user is using? LabVIEW's string conversion function give you every power to do that. If you know you need to deal with decimal point (for instance instrument communication) then disable the "use system decimal point" input at the string nodes or prepend %.; to all format strings for Format into String and Scan from String. If however you write out data to disk or whatever, such as a spreadsheet file to be read by the other application then just leave it as is and LabVIEW will use whatever is the current user setting for the decimal point. Don't try to outsmart your end user. They seldom can appreciate that . Instead make your application work as best as possible in the environment your users work. It may seem like a lot of a hassle to do what I explained above and after the fact it can be indeed quite a bit of work. But once you stick to this rule it does in fact not cost you any more work as it will get second nature to consider at all string formatting places if you do need a specific format or instead want to go with whatever the user has currently selected. It always depends who will be the other device/application dealing with the data. Rolf Kalbermatter

QUOTE (LVBeginner @ Mar 19 2009, 10:56 AM) WinHTTP should by default use the proxy server settings that you have configured for your IE. The local port is assigned randomly by the OS and should be of no concern to anyone. If you experience problems with the firewall you will have to create an exception rule in it that opens outgoing connections to the target port of the proxy such as 8080. Rolf Kalbermatter

QUOTE (BOBILLIER @ Mar 23 2009, 01:14 PM) MSDN is your friend. But if you intend to write an application for other users that is going to overwrite their preferred system settings you are going to annoy most of your users big time. A program trying to mess with my system is going to be uninstalled in a matter of seconds never to be looked at again, no matter how nice it is. Rolf Kalbermatter

QUOTE (Yair @ Mar 23 2009, 02:18 PM) It is indeed undocumented and has no editors that are available to people outside the LabVIEW R&D and I honestly doubt there are even many people in LabVIEW R&D that still would know how to use it :-) Basically it resembles the Mac PICT format with some modifications. Rolf Kalbermatter

QUOTE (KarstenDallmeyer @ Dec 5 2008, 06:34 AM) If you know you want to use the broadcast address you can also just simply plop a U32 constant and type in as large a value as you like with at least 11 digits. LabVIEW will truncate it to the max for an U32 which is 2^32 - 1 = 4294967295 = 0xFFFFFFFF which incidentally is the U32 value of the IP adress 255.255.255.255. So while the String to IP seems to have indeed technically a bug I never would have noticed since I do not go through the turnabout way of using String To IP to pass the broadcast UDP address to the UDP Write node. Rolf Kalbermatter