Return to VME  (Edit)

MROIDelayLineSW.VME History

Hide minor edits - Show changes to output

January 06, 2010, at 10:24 AM by EBS - Moved some issues from "open" to "resolved". Modified some resolved issues.
Deleted line 0:
Changed lines 7-8 from:
Software is built with C++ compiler, to accommodate library for accessing VME bridge.
to:
Software can be built with either C or C++ compiler, as dependency on VME bridge library has been removed.

Non-RT tasks scheduled using glib events.

Low-latency interface to Fringe Tracker will be RTNet.
Deleted lines 17-20:

How to schedule non-RT tasks?

What hardware is used for low-latency interface to Fringe Tracker?
March 26, 2009, at 12:10 PM by 131.111.48.85 -
Added lines 1-26:

!! Closed Issues

One RT task for all delay lines, triggered by single interrupt source. RT task performs somewhat different functions when seeking datum switch (always in slew mode).

Want capability to run software in an emulator mode, on VME platform under Xenomai, but without any interface boards.

Software is built with C++ compiler, to accommodate library for accessing VME bridge.

!! Open Issues

To what extent do we use C++ features?

Define classes and principal methods.

How to schedule non-RT tasks?

What hardware is used for low-latency interface to Fringe Tracker?

Algorithm for step pre-filter.

How is software configured (e.g. ASCII configuration file) ?



Recent Changes (All) | Edit SideBar Page last modified on January 06, 2010, at 10:24 AM Edit Page | Page History
Powered by PmWiki