JustinThomas

Yes my images are 32 bit and I did try with the images you posted. I get the same behaviour as you do

I just tried this on LabVIEW 8.6 and am able to display the symbols correctly. The transparent images are displayed correctly. See attached file How are you reading your png files? Also which version of LabVIEW are you using?

Hi all, I typically use the context help in my applications to give useful assistance to users using the application. By writing a good description to Controls the Context Help would act as a powerful tool giving quick help for users. This works fine for normal VIs, but does not work for Sub Panels. The problem is the Context Help window will show the description of the Subpanel container only no matter where I move the cursor inside it. Any recommendations on how to get this feature to work would be greatly appreciated. Also I would like to know any others ideas for providing quick help to users. Justin Thomas

QUOTE (george seifert @ Sep 18 2008, 07:42 PM) The TDM Get Properties VI context help states "The function returns the group and/or channel properties if you wire the group name or channel name inputs with values. If those inputs contain no values, the function returns the property values for the specified .tdms file" So just give the channel name and leave the property name terminal unwired it should give you an array of the property names

QUOTE (crelf @ Sep 18 2008, 07:53 PM) I don't think the queue would be destroyed if its already in memory as the Force Destroy terminal on the Release Queue vi is FALSE by default

QUOTE (RAJKU @ Aug 30 2008, 01:55 PM) You can do this by looking at the type of arrow the Run button shows see the attached image

QUOTE (RAJKU @ Aug 30 2008, 01:34 PM) i am thinking that you are referring to a SubVI on the block diagram. You would be required to wire the indicator to the SubVI's connector pane for the indicator data to be available outside the subvi after execution. You can refer to LabVIEW Help for more details. If you can be a little more elaborate I can help you better.

QUOTE (Neville D @ Aug 26 2008, 01:18 AM) My file sizes are around 50 MB. Earlier I tried with a single file but the transfer was not possible always. I get a timeout error on the Windows Explorer. I have not tried the same with LabVIEW. I tried chunking the files into smaller sizes around 5 MB each but did not get any significant improvement. QUOTE (Neville D @ Aug 26 2008, 01:18 AM) Are you using binary files? (They might be smaller in size). N. Yes I am using Binary files, basically logging raw data acquired from the cRIO modules QUOTE (Neville D @ Aug 26 2008, 01:18 AM) Can you use Gig-E with your controller? N. I don't think the cRIO controller has a GigE port its a 10/100 port. Anyways I need to use wireless so cannot think of GigE as an option

My application is a remote cRIO based data logger. I use the 9014 controller with 2GB memory. My total sampling rate is around 3MBps. I use a WLAN module to communicate between the cRIO and my PC. I have tried sending the data over TCP/IP during acquisition but I am not able to support the 3 MBps data rate between RT and Windows. So I have decided to go with local logging on the RT. As my test duration is small in the order of 20 to 25 minutes the memory on the controller is sufficient. I get file sizes of around 1.5 GB after each test. I then transfer the files using FTP to my Windows PC. This process is painfully slow. It requires more than 45 min for me to copy the files from RT to Windows using the Windows File Explorer. Using the internet toolkit FTP vis have not helped much. The time taken to tranfer the files in this case is also around 45 min. The problem is for a 20 min test I need to wait for double to time after the test to analyse my results. I was looking for a more efficient way to perform this operation. My thinking right now is to implement a TCP/IP based file copy module which would compress file sections on the RT before transmitting and decompress on the Windows PC. I was wondering if members can point me to some useful information on this method. Also any other suggestions regarding the implementation are most welcome Regards, Justin Thomas

The coercion dot is due to the fact that the refnums are for different data types. An array will take data elements of the same type so the refnums are converted to a more generic class refnum when you use build array. This can be observed if you use a refnum from output of build array and wire it to a property node. You will see that only generic properties for control are accessible. My suggestion you can use a cluster instead of an array if you wish to preserve the original refnums. See the attached image to remove the coercion dots.

I would recommend WEBEX from www.webex.com. Its great for desktop as well as application sharing. Also its useful for presentations with integrated VoIP and Chat. Another nice feature is you need not download any software just a small ActiveX control and it works instantly.

You can add your custom Conditional Disable Symbols by right clicking on the My Computer Target in your project and selecting properties

Any ideas on how to estimate boot up times on a cRIO controller? My current solution is as follows I am currently deploying an executable to the controller with some tcp code to connect to a windows machine. I then monitor the time it takes for the tcp connection to get established after switching on the controller. But I am getting varying results every time I run the test. Also I have noticed that this time is dependent on the following 1. NI software loaded on the controller 2. Model of the controller 3. Size of my executable. I am looking for any suggestions to accurately measure this boot time. Also it would help if I can get any suggestions to minimize the boot time. Regards, Justin Thomas

QUOTE(bjsprem @ Oct 26 2007, 09:35 AM) Hey John If you are in India and you are a LabVIEW programmer Captronics is the place to be. Its one of the 16 SELECT partners Worldwide for NI and the only one in the Asia-Pacific region. Captronics also has some of the best LabVIEW talent in the country with 2 Certified LabVIEW arhitects, and more then 10 Certified Developers. Visit the company website http://www.captronicsystems.com for more details on the kind of work they do. At least two applications from Captronic Systems have made it to the NI Paper Contest Finals for the past five years. This year Captronics won the Best application in two categories. Checkout http://www.ni.com/niweek/insideniweek-2007-wed.htm I have been with Captronic Systems for the past three years, and let me tell you that I absolutely love my work. Hope to see so soon on the team. Justin Thomas

QUOTE(TiT @ May 10 2007, 01:23 PM) I would like to reduce the file opening overhead each time, so the file is kept open for the duration of logging. QUOTE(Herbert @ May 10 2007, 08:16 PM) If your system powers off without the OS properly shutting down, and that happens at a point in time when the system is flushing it's disc buffers, you might end up with a corrupted file. I thought in the RT system there was no shutting down sequence, it was just power off. Right now the solution I have come up with is to use a digital input wired to the power off in my main system as an input to my RT device. The RT device is powered off after two seconds of the digital line going high. I check for this input in my RT application and perform my clean up operations like file closing. I would like to know if there is a way to do this through software. Does the RTOS generate any event before switch off which I can use? Regards, Justin

I have a RT application which logs some events during the execution of my application. This is an event log which i later retrieve to examine in case of improper execution. This file is opened as soon as the application starts executing and is never really closed, as i expect events to be logged till the RT system is powered off. The problem is that once in a while I get strange values for the file attributes, and am unable to open the file. The most common problem is that the file size returned by labVIEW is a very large number, which does not match the actual file size. I don't get the problem if I explicitly close the file. This means the problem is because I do not close the file before power off. Any help would be appreciated. Regards, Justin Thomas

Hi, I am currently using LabVIEW 8.0.1 and the technique mentioned does not work in this version of LabVIEW. Regards, Justin

Hi all, This is just to add a personal touch to my code. I would like to differentiate my vi's from other vi's. I have seen two ways to achieve this. 1. by adding a comment in my block diagram saying its my code. 2. use a unique background color for your block diagram. But users can easily change these. Is there a better way like say putting a watermark image on your block diagram, and can this be done automatically for all new vi's I create. Regards, Justin

Thanks Yen, That was a good way of getting the balloon tips. Justin

Hi all, Thanks for the prompt replies. I found the Event Discard method the easiest way to solve my problem. But would have loved to see a balloon tip, on a front panel object. Justin

Thats a neat way to do it. But I have around 10 to 12 of these string controls on my panel and it would be a lot of objects on the front panel if I keep an indicator for each to display the error message. Justin

Hi all, I have been following this forum for quite some time now. This is my first post though. I have a front panel with some string controls. I would like to restrict the user from entering some special characters in them. I would like to know if I can display him the tip strip programmatically whenever a special character is entered. I can show him a dialog box but its really annoying. I have seen a similiar behavior in Windows Explorer. I have attached a snapshot of the same to let you guys know what I am referring to. The picture shows balloons not tool strips I could do with those too. It would be great if I get some help on this. Justin