(B) Setting "outputLatency" and/or "getLatency" does not work.

[UweR70]

Firing these commands are showing the issue:

"...
06:30:37.227 -> (1) >>
06:30:37.227 -> (2) >> leapMMW:/>sensorStop
06:30:37.227 -> (3) >> sensor stopped already
06:30:37.272 -> (4) >> Error
06:30:37.272 -> (5) >> leapMMW:/>outputLatency -1 100 400
06:30:37.272 -> (6) >> Done
06:30:37.272 -> (7) >> leapMMW:/>saveCfg 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89
06:30:37.272 -> (8) >> save cfg complete
06:30:37.272 -> (9) >> Done
06:30:37.272 -> (10) >> leapMMW:/>getLatency
06:30:37.272 -> (11) >> Response 0.025 10.000
06:30:37.272 -> (12) >> Done
..."

Firing "outputLatency -1 100 400" results in the response "Done".
So the command were worked out without any error.

Firing the save command ends also without any error.
So the change should be saved.

Firinng "getLatency" results in the above shown response where the first value is equal to "0.025" and not to "2.500".
Also this command response is "Done".
So also this command were worked out without any error.

[UweR70]

No reaction after three weeks?
Lame and shame!

三周后没有反应？
蹩脚又可耻!

[UweR70]

No reaction after two month?
Lame and shame!

两个月后还没有反应？
蹩脚又可耻!

[UweR70]

No reaction after three month?
Lame and shame!

三个月后没有反应？
蹩脚又可耻!

[MaffooClock]

Firing "getLatency" results in the above shown response where the first value is equal to "0.025" and not to "2.500".

So, you've stumbled across a different configuration option, setLatency, which is not the same as outputLatency.

The setLatency is used to set a "confirmation delay" and "disappearance delay":

• confirmation delay - the amount of time (in seconds, range 0-100, default 0.05) during which presence activity must be continuous before the sensor will assert the presence status
• disappearance delay - the amount of time (in seconds, range 0.5-1500, default 15) during which there must be no presence activity before the sensor will de-assert the presence status

So the Response 0.025 10.000 you received are these two values.

The outputLatency command doesn't appear to have a get compliment.

[UweR70]

@MaffooClock
Thanks for the explanation.
My post / comment is about the first response value 0.025 (while 2.500 is expected).
My post / comment is NOT about the meaning of the two values 0.025 and 10.000

But anyways: Thanks.

[MaffooClock]

My post / comment is about the first response value 0.025 (while 2.500 is expected).

Which I explained is for setLatency -- it has nothing to do with outputLatency.

My post / comment is NOT about the meaning of the two values 0.025 and 10.000

You issued getLatency, expecting to see the values you set for outputLatency, but instead got the values that belong to setLatency. So yes, your post was exactly about those two values, and I was trying to show you that they don't belong to outputLatency as you thought they did.

That 2.500 value you were expecting comes from par2 of outputLatency, which is in units of 25ms. Thus, 100 x 0.025 = 2.5 seconds. However, there is no way (as far as I can tell) to read the value that was set into outputLatency, so you'll never actually see "2.500" anywhere.

Regardless of what you asked or expected, my comment was meant for anyone else who might run across this, so I wanted to be thorough and clear to prevent confusion.

[sagar448]

sen0521.pdf

@UweR70
You'll want to take a look at this. Everything is documented here, you don't know what I had to go through to find this, it's crazy. But all these commands I believe also work for the SEN0395.

[sagar448]

Heres the asian version

https://www.leapmmw.com/wp-content/uploads/1609/47/%E7%94%A8%E6%88%B7%E6%89%8B%E5%86%8CV1.3%EF%BC%9AHS2xx3A%E7%B3%BB%E5%88%97%E4%BA%BA%E5%AD%98%E5%9C%A8%E6%A3%80%E6%B5%8B%E6%A8%A1%E5%9D%97.pdf