Re: Error msg

[Andrew Johnson <anj@aps.anl.gov>]

Hi Stefen,

On 06/15/2016 02:35 AM, Stefen Paul wrote:
> The apsRebootHook.c file apparently needs a header file "apsLib.h" which
> I am not able to locate in EPICS installation or on the internet. Could
> you please provide the same.

Sorry, you shouldn't actually need that header, it just declares all the
API routines that I add to my BSPs and I include it there so the
compiler will check that my declarations match their definitions. Please
try removing the relevant #include line from the .c file.

> For the second problem (NTP):
> - I installed TimeTools NTP server on host PC. 
> - In st.cmd file I am setting EPICS_TS_NTP_INET as the  IP address of
> this host using putenv call. (before calling munch file and iocInit)
> - Above step is successful as I am able to verify it on the target's IOC
> with epicsEnvShow. 
> - But somehow the time is not getting synced. The NTP server shows time
> as UTC and Local system time. Is it the right TIME_ZONE that EPICS
> accepts ? 

Which version of VxWorks are you using, and does your VxWorks image
configuration define INCLUDE_IPSNTPC? Recent VxWorks versions also have
some related configuration parameters that set a primary and backup time
server IP address for the built-in NTP time synchronization task, and it
might be easier for you to configure this instead of using the EPICS NTP
provider. In that case you'd want to stop the EPICS NTP provider and OS
clock sync task by running NTPTime_Shutdown and ClockTime_Shutdown in
your startup script (in Base 3.15.4 and later the NTP provider and OS
clock sync tasks won't be started at all if the OS time synchronization
task is running).

When using the EPICS NTP provider, if your boot host is also the NTP
server you don't have to set the EPICS_TS_NTP_INET variable at all, the
osdNTPInit() routine in base/src/libCom/osi/os/vxWorks/osdTime.cpp will
use the boot host IP address from the VxWorks boot parameters if that
variable isn't configured at all.

You will need to configure the EPICS_TIMEZONE variable in your
base/configure/CONFIG_SITE_ENV file for use when the IOC has to convert
a timestamp into text, but that's the only place where the time-zone
really matters on the IOC. The server's timezone setting has no effect
on its clients, NTP always passes UTC over the network and relies on the
client to convert to local time when needed.

The following IOC commands are useful for seeing what your time
providers are doing:
  generalTimeReport 1
  NTPTime_Report 1
  ClockTime_Report 1

Hope this helps; if you still have problems please post the output from
the above report routines.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon