epics-base

Files

T

Andrew Johnson 3b8fd13152 libCom: NTP Time Provider adjusts to OS tick rate changes

Allow the NTP Time provider (used on VxWorks and RTEMS only)
to adapt to changes in the OS clock tick rate after the provider
has been initialized.

Changing the tick rate after iocInit() is not advisable,
other software might still misbehave if initialized before
an OS tick rate change.

Back-ported from the 3.15 branch (commit 12468).

2016-05-17 16:03:27 -05:00

BuildingR3.13AppsWithR3.14.html

docs: Replaced non-ascii space characters.

2010-10-06 11:41:49 -05:00

BuildingR3.13ExtensionsWithR3.14.html

docs: Replaced non-ascii space characters.

2010-10-06 11:41:49 -05:00

ConvertingR3.13AppsToR3.14.html

documentation: Update the Converting from 3.13 document.

2012-04-04 11:57:45 -05:00

KnownProblems.html

Document 3.14.12.1 changes.

2011-04-19 15:05:36 -05:00

README.1st

doc: fix typos and list of files in documentation directory

2015-02-18 15:46:05 -06:00

README.cris

Initial version - linux-cris files from Peter Zumbruch at GSI.

2007-11-09 16:12:24 +00:00

README.darwin.html

doc: Discuss ARCH_CLASS settings.

2010-10-13 11:21:17 -05:00

README.html

doc: HTML: fix typos and list of files in documentation directory

2015-02-18 16:55:09 -06:00

README.MS_Windows

documentation: Various updates...

2010-10-26 10:49:26 -05:00

README.niCpu030

Moved from $(TOP)

2002-07-17 01:41:24 +00:00

RELEASE_NOTES.html

libCom: NTP Time Provider adjusts to OS tick rate changes

2016-05-17 16:03:27 -05:00

ReleaseChecklist.html

Keywords: s/Release-Id/Revision-Id/

2010-10-06 12:17:25 -05:00

README.niCpu030

The CPU030 may need to have the nivxi path set correctly:
	From the vxWorks shell type "vxitedit" (you may need to
	loading the NI vxitedit package first)
	take option 2
	take option 3
	type list
	type modify 0
		type in the correct path when promped
		(the path should end in nivxi 
		and should traverse the niCpu030
		directories shipped with the 030
		ie something of the form "???/config/niCPU030/nivxi"
	type save
	type exit
	.
	.
	.

	see "Getting Started with Your VXIcpu-030" from NI

You may may need to setup front panel to backplane trigger
routing:

To take a TTL input and map it to VXI backplane ECL trigger 0
type in (to the vxWorks shell):

epvxiRouteTriggerECL(<logical address>, 1, 0)

where <logical address> specifies the card with the 
front panel trigger connection.

johill@lanl.gov