{"id":23215,"date":"2022-12-29T14:55:05","date_gmt":"2022-12-29T13:55:05","guid":{"rendered":"https:\/\/genesys-offenburg.de\/?post_type=smart-docs&p=23215"},"modified":"2023-11-02T12:34:54","modified_gmt":"2023-11-02T11:34:54","slug":"add-on-delta-data","status":"publish","type":"smart-docs","link":"https:\/\/genesys-offenburg.de\/en\/support\/adma-manual\/add-ons-and-add-ins\/add-on-delta-data\/","title":{"rendered":"Add-On – Delta 1:1 (Legacy)"},"content":{"rendered":"\n

The DELTA Data is an additional functionality (Add-On) of the ADMA. There are two ADMA\u2019s needed:
\u2022 one in the Target vehicle (called EGO-ADMA) and
\u2022 one in the Hunter vehicle (called DELTA-ADMA)
The DELTA ADMA computes internal relative data calculations of distance, velocity and angle between the two vehicles.<\/p>\n\n\n\n

Note<\/strong>: For being authorized using DELTA Data a License is required.<\/p><\/div><\/div>\n\n\n

\n
\"\"
AEB testing with ADMA Add-On DELTA<\/figcaption><\/figure>\n<\/div>\n\n\n

The DELTA Add-On calculates the distance between two moving vehicles. The measurement reference point is in the coordinate system of the DELTA-ADMA vehicle (Hunter vehicle). In this coordinate system, the Longitudinal direction (x direction) of the DELTA-ADMA is the INS-Angle-YAW. All data is defined in terms of ISO coordinate system, in reference to the configured POI. The data output rate at of the DELTA data is fixed to 100Hz.<\/p>\n\n\n\n

The DELTA Data measurements between the vehicles include:
\u2022 delta Longitudinal
\u2022 delta Lateral
\u2022 Distance (sum vector of delta Latitude and delta Longitude)
\u2022 delta Velocity
\u2022 Angle of Orientation (Yaw-Delta-ADMA – Yaw-Ego-ADMA)<\/p>\n\n\n\n

EGO-ADMA and Delta-ADMA Data:
\u2022 Forward Velocity
\u2022 Lateral Velocity
\u2022 Forward Acceleration
\u2022 Lateral Acceleration
\u2022 Pitch Angle
\u2022 GNSS Mode
\u2022 Lateral Position
\u2022 Longitudinal Position<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n


<\/p>\n\n\n\n

Schematic ADMA Delta data synchronization<\/h2>\n\n\n\n

The latency of the Addon Delta data depends on the WLAN delay. In best case scenario the latency can be 10 milliseconds, but in the most situations under real circumstances, the latency varies between 15 and 40 milliseconds. The data of both ADMA systems get synchronized from the hunter ADMA as soon as the remote data of the Ego ADMA arrive.<\/p>\n\n\n

\n
\"\"
Schematic ADMA Delta data synchronization<\/figcaption><\/figure>\n<\/div>\n\n\n

Wiring Delta-ADMA<\/h2>\n\n\n\n

The following diagram shows an example wiring of the DELTA-ADMA (Hunter vehicle).<\/p>\n\n\n

\n
\"\"
Example wiring diagram of the DELTA-ADMA<\/figcaption><\/figure>\n<\/div>\n\n\n

Wiring EGO-ADMA<\/h2>\n\n\n\n

The following diagram shows an example wiring of the EGO-ADMA (Target vehicle).<\/p>\n\n\n

\n
\"\"
Example wiring diagram of the EGO-ADMA<\/figcaption><\/figure>\n<\/div>\n\n\n

Network configuration<\/h2>\n\n\n\n

The ADMA\u2019s communicate via UDP. The ADMA use datagram sockets to establish host-to-host communications. An application binds a socket to its endpoint of data transmission, which is a combination of an IP address and a service port.
A port is a software structure that is identified by the port number, a 16 bit integer value, allowing for port numbers between 1024 and 65535. For different data output, another service port must be used.<\/p>\n\n\n\n

Source IP\/Port number:
This field identifies the IP\/Port of the sending system. If the source host is the DELTA-ADMA, the port number is likely to be a well-known IP and port number of the EGO-ADMA.<\/p>\n\n\n\n

Destination IP\/Port number:
This required field identifies the IP\/Port of the receiving system. Similar to source port number, if the DELTA-ADMA is the destination host then the port number will likely be a well-known IP and port number of the EGO-ADMA.<\/p>\n\n\n\n

The IP settings of the ADMA Ethernet ports can be changed on menu 2\ufe0f\u20e3 DATA LINK<\/strong>. The DELTA settings can be made on menu 7\ufe0f\u20e3 ADD-ONS \/ DELTA DATA<\/strong>.<\/p>\n\n\n\n

The following diagram shows an example configuration of the DELTA- and EGO-ADMA via Webinterface.<\/p>\n\n\n\n

\"\"
Example of ADMA ADD-ON DELTA configuration<\/figcaption><\/figure>\n\n\n\n

Point of Calculation<\/h2>\n\n\n\n

The DELTA Add-On calculate the delta values between the defined POI at the Ego-ADMA and POI at the DELTA-ADMA. This allows to compare the DELTA data directly with the VUT (Vehicle under Test) sensor measurements.<\/p>\n\n\n

\n
\"\"
DELTA Measurement POI<\/figcaption><\/figure>\n<\/div>\n\n\n

Offset Corrections<\/h2>\n\n\n\n

In some cases, an offset correction of the lateral or longitudinal distance can be useful. To make a quick adjustment, user defined offset values can be added or subtracted from the lateral or longitudinal distance.
Once the point of interests has been defined, the ADMA has been initialized the correct way and RKT2 is available, the offsets can be determined automatically by using the function zero lateral \/ longitudinal distance.
By using the button Save setting to ADMA, the configured offset values will be stored at the ADMA without a restart of the measurement mode.<\/p>\n\n\n\n

In the figures below, you will find the definition of the lateral and longitudinal offset to the defined DELTA point of interests.<\/p>\n\n\n\n

Note<\/strong>: Using the longitudinal and lateral offsets to correct the delta measurements will not work when the DELTA-ADMA (Target Vehicle) is rotated compared to the EGO-ADMA (Hunter Vehicle).
Lateral and Longitudinal offsets do not influence the delta resultant distance value.<\/p><\/div><\/div>\n\n\n\n

Delta_Lateral = Lateral_distance + Lateral_offset\nDelta_Longitudinal = Longitudinal_distance + Longitudinal_offset\nDelta_Resultant\t= sqrt(Lateral_distance2<\/sup> + Longitudinal_distance2<\/sup>)\n<\/pre>\n\n\n
\n
\"\"
DELTA Lateral offset<\/figcaption><\/figure>\n<\/div>\n\n
\n
\"\"
DELTA Longitudinal offset<\/figcaption><\/figure>\n<\/div>\n\n\n
CAN recurrence interval<\/h2>\n\n\n\n
The CAN recurrence interval determines how long the last valid DELTA value is repeated after a loss of the EGO data (Target data) until the DELTA result is output with 0.<\/p>\n\n\n\n
Example 1: Configured CAN recurrence interval of 100 msec with an ego data loss over 100 msec.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Example 2: Configured CAN recurrence interval of 100 msec with an ego data loss over 150 msec.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
List of data packets V7.0<\/h2>\n\n\n\n
Please find the list of Addon Delta data packets in the article Delta Data \u2013 List of data packets v7.0<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
The DELTA Data is an additional functionality (Add-On) of the ADMA. There are two ADMA\u2019s needed:\u2022 one in the Target vehicle (called EGO-ADMA) and\u2022 one in the Hunter vehicle (called DELTA-ADMA)The DELTA ADMA computes internal relative data calculations of distance, velocity and angle between the two vehicles. The DELTA Add-On calculates the distance between two […]<\/p>\n","protected":false},"author":148,"featured_media":30266,"template":"","meta":{"_acf_changed":false,"_links_to":"","_links_to_type":0,"footnotes":""},"smartdocs_category":[809,849],"class_list":{"0":"post-23215","1":"smart-docs","2":"type-smart-docs","3":"status-publish","4":"has-post-thumbnail","6":"smartdocs_category-adma-manual","7":"smartdocs_category-add-ons-and-add-ins"},"acf":[],"_links":{"self":[{"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/smart-docs\/23215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/smart-docs"}],"about":[{"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/types\/smart-docs"}],"author":[{"embeddable":true,"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/users\/148"}],"version-history":[{"count":1,"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/smart-docs\/23215\/revisions"}],"predecessor-version":[{"id":32085,"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/smart-docs\/23215\/revisions\/32085"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/media\/30266"}],"wp:attachment":[{"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/media?parent=23215"}],"wp:term":[{"taxonomy":"smartdocs_category","embeddable":true,"href":"https:\/\/genesys-offenburg.de\/en\/wp-json\/wp\/v2\/smartdocs_category?post=23215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}