C1001 Semantics of fall detection configuration settings

I want to use the c1001 for fall detection. I have some questions about the configuration and the data returned by the fall detection functions. For some I have an idea based on github or by experiments, but for others I have no clue. Could you help me understand what the different configuration options mean and what data is returned by the fall detection functions?

Configuration:

   - install height: Set installation height, it needs to be set according to the actual height of the surface from the sensor, unit: CM.

   - fall time: Minimal time in seconds that a fall must be detected before a fall is reported.

 * Fall config:

    - eFallBreakHeightC: ? What does it mean? Setting it to 100 seems to work with fall detection, but 20 or 150 not.

    - eHeightRatioSwitchC: ? 0 = off, 1 = on ? But what does it switch on?

    - eAltTimeC: It seams that it cannot be set when the height ratio swithc is turned off. But what does it do? It has influence on how (fast) fall is detected.

    - eFallSensitivityC: Set fall sensitivity, range 0~3, the larger the value, the more sensitive.

    - eResidenceSwitchC: ? 0 = off, 1 = on ? I assume that this turns checking the residence on or off

    - eResidenceTime: Set dwell time, when a person remains still within the sensor detection range for more than the set time, the sensor outputs a stationary dwell status. Unit: seconds. Can only be written when residence is switched on

    - eReportSwitchC: ? 0 = off, 1 = on ? Sets reporting on/off?

    - eReportFreqC: Set the report frequency? But what kind of reporting? What is reported?

 *  Human config:

    - eSeatedHorizontalDistanceC: ? No idea what it does

    - eMotionHorizontalDistanceC: ? No idea what it does

Data returned:

  * Human data:

    - eExistence: is a human detected? 0 = no, 1 = yes

    - eMotion: is there human moving? 1 = no motion, 2 = motion detected

    - eBodyMove: How much motion is detected 0-100

    - eTrajectorySwitch: ? Cannot be read? Gets no or wrong data back?

    - eSeatedHorizontalDistance: ? Get always 0 back, maybe wrong configured. Should it return the seatedHorizontalDistance config? strange that it is in this fall data function

    - eMotionHorizontalDistance: ? Get always 0 back, maybe wrong configured. Should it return the motionHorizontalDistance config? strange that it is in this fall data function

    - eFallState: fall state? 0 = no, 1 = fall detected

  * Fall data:

    - eFallBreakHeight: The configured fall break height

    - eHeightRatioSwitch: The configured height ratio switch state

    - estaticResidencyState: Is a human present that does not move: 0 = no, 1 = yes

    - estaticResidencySwitch: ? 0 = off, 1 = on ? What does it switch? When off the estaticResidencyState is still changing.

    - eFallSensitivity: Configured fall sensitivity, range 0~3

Any help is welcome. Even when based on experience