| Title: | VAX on VMEbus: KAV30 | 
| Notice: | Could have been as fast as 68K but its a VAX! | 
| Moderator: | CSSVMS::KAV30_SUPP | 
| Created: | Thu Apr 18 1991 | 
| Last Modified: | Fri Aug 02 1996 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 159 | 
| Total number of notes: | 645 | 
    thanks a lot,
    I explain the reason.....
    
   	I'm trying to use an existing driver for rtc of VMEAX-300 written by 
    IRTV for a DEC project and seems that the rtc structure is the same 
    to KAV-30 but the address has to be different.                                                  
	Moreover I must start a routine every 4.88 msec that is not simple
    with KAV$RTC.
     
    thanks for your help
    
    	Marino
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 149.1 | why RTC - timers might be easier... | EICMFG::KAV30_SUPP | Tue Jan 17 1995 10:08 | 14 | |
|     Hi Marino,
    
    if you need to have some time signal at predefined intervalls, why
    don't you use the KAV$timer calls ? These run with a 'tick' of 400nsec,
    so it should be easy to create an intervall of 4.88 msec - the examples
    coming with ELN show how to use the timers.
    
    I will also look into the differences of VMEAX300 and KAV30 to tell you
    wether it's easy to use the IRTV driver on KAV30 or not...
    
    best regards,
    
    	Thomas
    
 | |||||