Module afibex::fibex

source ·

Structs§

  • ArrayDimension
    service:FIELD-TYPE https://www.asam.net/xml/fbx/services/fibex4services.xsd mainly a Parameter with getter, setter, notifier. So we ARRAY-DIMENSION-TYPE: (can happen multiple time in seq and defines one dimension of the array each)
  • Channel
    fx:CHANNEL-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:REVISED-ELEMENT-TYPE extended by:
  • CodedType
    fibex: ho:CODED-TYPE (see https://www.asam.net/xml/harmonizedObjects.xsd)
  • Coding
    fibex: CODING-TYPE
  • ComplexDatatype
  • CompuMethod
    ho: COMPU-METHOD, see https://www.asam.net/xml/harmonizedObjects.xsd
  • CompuScale
  • Datatype
  • DynamicPart
  • Ecu
    fx:ECU-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:REVISED-ELEMENT-TYPE extended by:
  • Elements
    all elements are derived from fibex: REVISED-ELEMENT-TYPE containing:
  • Enum
  • FibexData
    structure holding the parsed data from multiple fibex files
  • FibexError
  • Frame
    fx:FRAME-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:REVISED-ELEMENT-TYPE extended by:
  • GetterSetterNotifier
    service:GETTER-SETTER-TYPE and NOTIFIER-TYPE merged
  • IntervalType
    ho:INTERVAL-TYPE (xs:double, opt OPEN, CLOSED(default), INFINITE)
  • Method
    service:METHOD-TYPE https://www.asam.net/xml/fbx/services/fibex4services.xsd todo: check params… vs. spec
  • Multiplexer
    fx:MULTIPLEXER-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd xs:sequence <xs:element name=“SWITCH” type=“fx:SWITCH”/> <xs:element name=“DYNAMIC-PART” type=“fx:DYNAMIC-PART”/> <xs:element name=“STATIC-PART” type=“fx:STATIC-PART” minOccurs=“0”/> <xs:element name=“TRIGGER-MODE” type=“fx:TRIGGER-MODE” minOccurs=“0”> </xs:sequence> <xs:attribute name=“EXTENDED-ADDRESSING” type=“xs:boolean” use=“optional” fixed=“true”>
  • Parameter
    service:PARAMETER-TYPE https://www.asam.net/xml/fbx/services/fibex4services.xsd extended with opt. getter, setter, notifier to handle the Field as well
  • Pdu
    fx:PDU-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:REVISED-ELEMENT-TYPE extended by:
  • PduInstance
    fx:GENERIC-PDU-INSTANCE-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:IDENTIFIABLE-ELEMENT-TYPE extended by:
  • ProcessingInformation
  • Project
    these structs should reflect the structure from the asam fibex 4.2.1 definition focussed on the needed elements for someip or dlt usage. todo check mandatory (non Option<>) vs use=“required”/minOccurrence=0…
  • SegmentPosition
  • SerializationAttributes
    fx:SERIALIZATION-ATTRIBUTES-TYPE
  • Service
    service:SERVICE-INTERFACE-TYPE https://www.asam.net/xml/fbx/services/fibex4services.xsd
  • Signal
    fx:SIGNAL-TYPE according to https://www.asam.net/xml/fbx/fibex.xsd It’s a fx:REVISED-ELEMENT-TYPE extended by:
  • SignalInstance
    todo proper type/doc
  • Switch
  • Utilization
    fx:UTILIZATION-TYPE https://www.asam.net/xml/fbx/fibex.xsd
  • XmlElement

Enums§

Functions§