Conference 49.910::kav30

    Hi Alan,
    
    This scenario could be caused by an insufficient auxilary power source. 
    Is the customer using the battery as the auxilary power source?
    
    The clock invalid test checks for a specific pattern in the RTC's
    internal RAM, if the check fails the diagnostic utility will still
    display the time (which may or may not be correct).  The kernel also
    performs a similar check of the RTC's internal RAM if the VAXELN system
    has been configured to set the VAX system time from the RTC.  If the
    contents of the RTC's RAM are invalid, the BOOTERROR message is
    displayed.  Setting the time in the RTC either using the diagnostic
    utility or one of the KAV30 system services (KAV$SET_CLOCK or KAV$RTC)
    will set the RTC's internal RAM contents to be valid.
    
    Graham
          

Hi Graham,

Thanks for the response.  I received some new info from the customer.
It turns out that he is having this problem only with their second ship of 
four KAV30's.  They are not having the problem with their first shipment.
The second set of KAV30's have ROMs with the numbers:

                23-156E8-00-A02
                23-157E8-00-A02

They have no problems with their first set of KAV30's with the -A01 flavor
of ROMs.

Some additional info.  The systems are ultimately going to be sealed and put
in underwater vehicles that will be placed on the ocean floor.  They won't
be able to get to a console to set the time.

In their tests, the systems are running for days at which time they are powered
down.  A day or two later they are powered back up and rebooted. At that point 
the -A02 systems get the invalid boot message.  ALSO, (new to me), the 
call to KAV$RTC is taking an accvio on these systems (reason mask 4) when
the RTC is deemed invalid.  I'm having him reverify what version of the
KAV toolkit he was using in his tests.  

As a test, I've asked him to use the call to KAV$CHECK_BATTERY to verify that
the power is ok.  Something tells me that something may be wrong with this
shipment with the -A02 ROMs since all four exhibit the same problem.

Are you aware of any differences between the -A01 and -A02 KAV30's?
(BTW, our KAV30 has the -A01 

Unfortunately, this will be a serious issue for the customer if it can't be \
resolved.

Thanks in advance for any additional info you may have.

Alan

    Hi Alan,
    
    How is jumper J9 configured on the customer's module?
    
    Graham

Hi Graham,

Do you mean jumper J8 for the battery?  I couldn't find a reference to J9?

I'll have him double check the J8.

Thanks,

Alan

    Hi Alan,
    
    J9 IS the battery jumper on the production KAV30s, all of the jumper
    locations and labellings on the production KAV30s differ from the field
    test prototypes.
    
    Graham

Hi again Graham,

Confirmed with the customer that he has the two J9 pins closest to J8
connected (i.e., KAV30 battery).

He states that with the -A02 flavor board, selftest 3 for the battery
does pass.

In response to my recommendation of using KAV$CHECK_BATTERY he is getting back 
a "bad parameter count" status return.  I'll check this out as well.  Any
thoughts here?  (He gets this on either the -A01 or -A02 boards).

He claims that the batteries should have had plenty of time to recharge
(over 24 hours with power on.)

Thanks again for any additional thoughts,

Alan

    Hi Alan,
    
    Thanks for providing the information about J9.  We'll need to
    investigate this behaviour here.
    
    Graham
    

Hi,

Believe it or not, another customer who has the -A02 ROMS is now wanting
to set the system time from the RTC.  We now have a KAV30 with the -A02 ROMS.
Unfortunately, if the selftest indicates that the battery check fails and
if one still attempts to use KAV$SET_CLOCK with the SET_VAX_TIME to set
the system clock from the RTC, KAV$SET_CLOCK fails with 

 		%TIME_NOT_SET, time has not been previously set

Hence, the battery check would not even suffice as a workaround in 
this case.

Has there been a new release of the user roms that corrects this?
And if so, where can a U.S. customer get a replacement set?

Thanks,

Alan

	This problem already was corrected with the release of rev A03
	EPROM (see note 8.5-7 on ECO details). KAV30 of the latest revision
	sipped in cw31 and later do have these EPROMs 'onboard'. If a customer
	with an earlier rev needs to replace the EPROMs, he should order
	it through field service (EPROM set is an FRU). Field service should
	order spare parts through fs organization in Nijmegen. The following
	picture shows the channels for FS US (I hope this is already
	known within Europe...)



		+--> Logistics --> William Sergeant@DAS --> Andre Dekker @JGO
		|
    US FS --->--+
		|
		+--> Ordering --> Cathy Odonnell@DAS --> Imke van de Linde @JGO

Thanks Thomas for the contacts.  We will order the replacement -A03 EPROMS
for our own KAV30 as well.

Regards,

Alan