Anu Kalidas

This effort is worthy of upgrading to a Premium membership. if only I could figure out how...

As mentioned here, for the time being you will have to PM Michael.

Michael and team,

Thank you very much for the great work.

Done :thumbup:

BTW now one has to sort by "Most Recommended" and your comment will be the first.

QUOTE (Gary Rubin @ May 12 2009, 09:27 AM)

2. Counter1 generates a pulse train which is synchronous with Counter0 and delayed from it.

How did you implement the delay between counter 0 and counter 1 generation?

QUOTE (jgcode @ Apr 4 2009, 12:20 PM)

Thanks Kal. I was told by NI Support that this configuration is correctly setup to use an external timing source - i.e. the clock is supplied by the NI 9237 module.

Are you saying this is not an external clock?

JG,

My cDAQ knowledge is very limited, so it is possible that what NI support says is correct.

Till now, I was of the thinking that the cDAQ chassis provides all timing (clocks) to IO modules. Hence I assumed that the ai/SampleClock or timebase is an internal source and not an external source.

One thing I am not sure is, when we specify ai/sampleclock as the clock source, how will it get routed to the 9411 module? There is a direct route between sample clock and mod5 PFI lines, but will NI-DAQ do the routing or do you have to route the clock to a PFI line and then use that PFI line as clock for the position task?

QUOTE (jgcode @ Apr 3 2009, 05:34 PM)

Unfortunately both gave the same results.

Cheers

JG

In one of the example VIs they say that you cannot use internal timebases for clock and should be supplied 'externally'. I guess this means you will have to give the clock signal to one of the PFI lines of 9411. Internal routing (which is the case when you use cDAQ1/ai/SampleClock) may not be supported.

While using the real hardware, don't you have to set the sampling rate for the 9237 module? Not sure whether without this the ai sample clock will generate pulses. It looks like the acquisition timed out before any sample is acquired. A quick check can be to replace 'cDAQ1Mod1/ai/SampleClock' with 'cDAQ1Mod1/ai/SampleClockTimebase'...

You can password protect your VI so that no one will be able to open the block diagram.

File>>VI Properties>>Protection and select 'Password-Protected'.

Hi John,

Thanks for posting this example.

I tried installing the web service using 'with RTE' installer in PCs not having LabVIEW. In some PCs the installed web service failed to work while in some other PCs it is working perfectly. Is there any way to check why it may not be working in some PC? I have enabled all the ports mentioned in the PDF document and even tried disabling the firewall. Still no luck.

Thanks

You can use Zoom FFT to get higher resolution. This VI is available with the sound and Vibration Suite.

Yet another 8.0 feature that nobody talks about is the DIAdem Report Generation Express VI - which is partly because not everybody has DIAdem installed. So I have made talking about it really easy by videotaping it for you :thumbup:

This video and your other posts on TDMS and DIAdem are very helpful...thanks a lot :thumbup:

Thanks Jim.

I was using the installer for SVN (was not quite sure whether it is the Windows one or not). Actually while installing SVN, it didn't detect that Apache is installed. So I manually copied the .SO files to the ..\Apache\Modules folder and modified the httpd.conf file.

After this I uninstalled Apache 2.2 and installed Apache 2.0.59 and followed the same process (without uninsatlling SVN). This works pefectly, which suggests that i am using the correct (windows) .SO files.

Is there any location from which I can get the correct compiled .SO files.

Also just now I downloaded SVN 1.4 Windows installer. I will try to use this also with Apache 2.2.

Kalidas

hi,

I got following error message while trying to setup Apache 2.2 and Subversion 1.3.2

httpd: Syntax error on line 119 of

C:/Programming/Apache2.2/conf/httpd.conf: API module structure `dav_svn_module' in file C:/Programming/Apache2.2/modules/mod_dav_svn.so is garbled - perhaps this is not an Apache module DSO?

I've included,

LoadModule dav_fs_module modules/mod_dav_fs.so

LoadModule dav_module modules/mod_dav.so

LoadModule dav_svn_module modules/mod_dav_svn.so

LoadModule authz_svn_module modules/mod_authz_svn.so

in the httpd.conf file.

Any ideas on how to solve this issue?

Thanks

Kalidas

Here is a small irritant...

If I use a strict type def constant, by default the autosizing option will be "size to fit" and will not change if I change it on the parent control. So each time I create a constant, I have to manually go to BD and change the option to "None"... :headbang: .Things become worse if you have nested clusters... Is there a way out of this.... .

Couple of days back I upgraded to LV8. The development enviroment looks really nice. But once I started using it I felt that its not as cool as it looks...particularly the project explorer window... Probably I will be able to appreciate the features once I start using it regularly...But I would like to know what other people think of the project explorer...Does it really make life easy( or complicated?).

One thing I would like to know is the reason for not creating a folder in the drive when you create a new folder in the project explorer window.

Also how helpful is the project explorer if one is using SVN which, I think, is not supported by LV8 SCC.

Regards

Kalidas

Recently I decided to use the TDM format for all my test data files. So as a first step, I read the document 'Introduction to the LabVIEW TDM Header Writer VIs'(http://zone.ni.com/devzone/conceptd.nsf/webmain/117CB3D512ED96928625707B004DC4E9) ( Yeah, I want to use it in RT). Everything went fine till I reached the "Creating a TDM Header File for a Multi Channel Binary File" section of the document. This section tells you how to setup a binary file that contains more than one channel. I created a VI as illustarted in this section to create a TDM file. Even the data file for multiple channels was created using the illustration given in this section. But when I tried to read the file back using the storage VI's, it was reading all the properties that were set for each channel but was not able to read the data and the warning message 2552 tells that "This property does not contain data."

The documentation for Setup Block Channels.vi says that " interleaved (Block) channels described in a TDM file will only load correctly in LabVIEW or DIAdem when USI version 1.1.1.2245 or later is installed (DIAdem 9.1 SP2 LabVIEW 8.0, or later versions).".

I used LV 7.1 for creating these VI's. So was this the problem? or I'm missing something...What exactly is this "USI version 1.1.1.2245 "?

I've also attached the V that I used to read the data.

Download File:post-304-1129887717.vi

This was one of the best threads that I have read till now... Covering three different topics...Scripting, Architecture and forum issue( :laugh: ). Anyway this was definetly informative...and that's why I love LAVA

With LabVIEW closed, open the labview.ini file and add the line

'hideRootWindow=True' without the quotes to hide the extra button for LabVIEW in the windoze taskbar.

Works for LV 4.0+

Well at last...Thanks Pana-man :thumbup: .I was searching for this ini setting for quite a long time. This will work with any exe running on windows

Change the menu order by dropping in a text file in the menu subdirectory with the same name as the subdirectory. In the text file put the name of the VIs in the order that you want them displayed. A - adds a delimiter line.

If you have source code control, you can go into that sub-directory for a good example.

Ummm... Didn't get that actually...Are you referring to the LabVIEW menu?

Hi Kalidas:

I use a package called SnagIt.

http://www.techsmith.com/

Fairly powerful, quite inexpensive, I'm happy with it. I'm sure there's other products out there & some might be better or cheaper, but for my casual use, SnagIt works pretty well.

Best Regards, Louis

Thanks Louis,

Just downloaded and tried the trial version. This thing is cool :thumbup:

Overheard: LV 8 may support some software testing tools.

Didn't see anything like that in the upgrade notes...

I liked the concept of Private VIs that can be defined in a project file. Can use it to implement goop more effectively..

I don't recall what they are but I'm sure someone here can give us a hand...

So hacking gurus... U guys have got some work to do...

Sad to hear that scripting is no longer supported in LV8 But as long as LV8 is backward compatible, we may be able to use LV 7.1 and do scripting somehow ...

Seen one or two posts in LAVA where a video file is used to show how FP or BD. How is this done? Is it available as a normal windows utility or is it a seperate software or.... a video camera is used :camera: !!!

BTW Michael, I really miss the spell checker..