Modeling Hints

First of all you create the ASCET project intended for transfer to INTECRIO as usual. You can make use of all ASCET facilities, but note the following points:

• Receive messages without corresponding send messages form the signal sinks in INTECRIO, send messages without corresponding receive messages form the signal sources in INTECRIO.

  By default, messages that are both read and written in ASCET are excluded from integration in INTECRIO. If desired, you can make these messages appear as signal sources in INTECRIO, see Project Transfer to INTECRIO – Messages.

• When your ASCET project contains unresolved messages (imported messages without corresponding export), code generation for INTECRIO produces an error message.

  You can resolve the messages automatically, or you can cancel code generation and resolve the messages manually.

• Using global variables and parameters is possible, but strongly discouraged.

• Enumerations and formulas in your project must have different names. If the project contains an enumeration and a formula with identical names, the code generation for INTECRIO displays an error message.

• You have to select the target Prototyping, RTPRO-PC (outdated), or ES910 in the build options of the project. INTECRIO is preselected in the Experiment Target combo box with any of these targets. INTECRIO code generated with this target can be used with each experimental target supported by INTECRIO.

  For the Prototyping target, SCOOP‑IX generation is always activated. You can select the SCOOP‑IX versions V1.2, V1.4, V1.5, or V1.7.

  For the RTPRO-PC and ES910 targets, you must explicitly activate the Generating SCOOP‑IX option in the "Build" node of the target options. Only SCOOP‑IX V1.2 is available.

  Note
  It is strongly recommended that you use the Prototyping target and SCOOP‑IX V1.5 or V1.7 for transfer to INTECRIO.

• After selecting the Prototyping target, the following setup options are deactivated in the OS editor:

  • Preemp. Levels and Coop. Levels fields (all tasks)
  • Enable Monitoring option, pre-/post hooks combo box (all tasks)
  • ISR Source and Period fields (interrupt tasks)
  • Max. number of Activations field (alarm/software tasks)
  • Autostart option (alarm/software tasks)

  In some cases, the number of preemptive levels is set to 0. In that case, you can use the Copy From Target function in the Operating System menu to copy the operating system settings to the Prototyping target. The deactivated settings are copied and the Preemp. Levels field is made available. You can now enter a suitable value, i.e. a number ≥ 8.

• Beginning with V5.0.8, INTECRIO supports the import of ASCET messages of the following types as single elements:

  • scalar (including enumerations) with numerical data type
  • array of scalar elements
  • matrix of scalar elements

  See Non-Scalar Messages for INTECRIO for specific modeling hints.

  Record messages, or array/matrix messages of record type, are not imported as single elements in INTECRIO. For a record message, each record element is imported as separate signal. For array/matrix messages of record type, each record element in each array/matrix element is imported as separate signal.

  EXAMPLE
  An ASCET project contains the record messages Msg_Record_R and Msg_Record_S, and the array[4] messages Msg_arrayRec_S and Msg_arrayRec_R with record elements. The record in the array elements contains two elements. Imported into INTECRIO, the model looks as follows:

• See ASCET and SCOOP‑IX for information on how some ASCET settings appear in the SCOOP‑IX file generated for use with INTECRIO.

Once you have completely specified the project, you invoke the transfer of the project to INTECRIO as the first step in code generation.

See also

Non-Scalar Messages for INTECRIO

Project Transfer to INTECRIO

Preparing the Project

ASCET and SCOOP‑IX