Documentation Home Page RT-LAB Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Block

Mask

Description

The OpEngine Position & Speed Manager Block provides the capabilities to generate a pulse train with high resolution on the frequency. The pulse train is used to feed the clock entry of an event generator hardware module allowing accurate generation of engine related signals that are synchronous with the engine position. This block can operate in Master or Slave mode.

In Master mode, the block generates high-resolution pulses (Crank)and Index signals (Cam). In this mode, the engine rotational speed is provided to the block expressed in revolution per minute (RPM). Furthermore, the underlying hardware module provides a position register that is latched at the beginning of each calculation step. This feature allows, by the mean of the Position Output, to report accurately the simulated engine position to other model blocks such as the OpEnginePulse block.

In Slave mode, the blocks evaluate the speed and the position of a real engine from the external position and index signals. This evaluation is accomplished using the data that are captured and reported within a calculation step by the underlying hardware module. These data are the occurrence time of the first and last position pulse, the number of pulses, the value of the external position register. This block reports as well a position error and a status. The former is estimated using the position register values (simulated and external) and the later is evaluated by monitoring the correctness of the external signals.

This block provides the capabilities to generate a pulse train at a higher resolution than supplied external signals (see the OpEnginePulse Controller). It is mainly used in conjunction with the OpEnginePulse in order to generate signal patterns that are synchronous to the engine position. For more information on these blocks refer to the related documentation.

Parameters

Controller NameDefines the label of the controller block.
SSelects between the Mater mode where the engine speed is supplied by a block input in RPM or the Slave mode where external signals are used to evaluate the engine speed and position.
Refresh Rate of Output Speed (RPM)Specifies the averaging period in a millisecond of the instant engine speed. This field is used only in Slave mode.
Synchronization Angle (deg)Specifies the synchronization angle of the Cam signal. This field is used only inSlave mode.
Synchronization EdgeSpecifies the edge polarity of the "External Index" signal. The user selects either rising or falling edge. This field is used only in Slave mode.
Position EdgeSpecifies the edge polarity of the Crank signal. The user selects either rising or falling edge. This field is used only in Slave mode.
Sample TimeSpecifies the sampling period for the external signals.

Inputs

Speed (RPM): Provide the Engine Speed, available in Master mode only.

Outputs

StatusGives status of the Engine Position & Speed Processor. See table below for more information.
Error (deg)Reports the position error that is estimated using the simulated and external position register values. Available only in Slave mode.
PositionSupplies the current engine position as evaluated by the simulated engine speed.
RPMReturn the average speed of the engine over a period of time. Refer to the Refresh Rate of Output Speed (RPM). This output is available only in Slave mode.

Status:

Possibles Values Description 
1SIGNAL IN SYNC
-1WAIT FOR SYNC SIGNAL
-2LOST SYNC SIGNAL
-10SPEED OVER MAXIMUM
-99SPEED BELOW MINIMUM 

Characteristics and Limitations

Board Index limitations

Board index is user-selectable in the range [0-15] via a connector on the board. However, boards OPHSDIO64 labeled v0.01 do not implement this feature, and the board index of these boards is set to the default value 15.

Connector Pin Assignments

The hardware module is generic and can be instantiated in different electronic boards. The first release of this IO block has been implemented into the OPHSDIO boards that are usually shipped with custom-made cables. These cables are adapted to the Opal signal-conditioning cassette required by the system they are to be connected to. Please refer to the documentation of your system for your specific connector pin assignment. If you need to prepare your own custom cable, please contact support@opalrt-com.

Direct FeedthroughNo
Discrete sample timeNo
XHP supportYes
Work offlineNo
  • No labels