epics-base

Files

T

Andrew Johnson c5ded30684 Extended asTrapWrite to provide put data

Backwards-compatible enhancement to the asTrapWrite API to provide
listener routines with the data being put by the client.
The asTrapWriteMessage structure is extended with 3 new fields
for data type, element count and a pointer to the source buffer.

Tim Mooney requested this enhancement for his caPutRecorder code,
which doesn't work if the record overwrites the new value within
its process() routine, e.g. when jogging a motor record.

2015-02-16 16:30:52 -06: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

documentation: Various updates...

2010-10-26 10:49:26 -05: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

documentation: Various updates...

2010-10-26 10:49:26 -05: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

Extended asTrapWrite to provide put data

2015-02-16 16:30:52 -06: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