@Alex-Kushleyev just learned you cannot set the exposure max to 1200. 1000 and 1500 work. If you set it to 1200 you get a vague IO error
ERROR: [ERROR] in _sensor_ioctl, ioctl failed: Connection timed out
ERROR: [ERROR] in voxl_cci_read, Failed ioctl call
ERROR: Failed CCI read
Just posting this here as an FYI to other wrestling with these new sensors.
@Alex-Kushleyev I will get the screenshots in a moment. lme_msv wasn't set and I noticed that power usage wasn't going down and figured there was just a bug in the config-reading code, so I recompiled with the default exposure value in the #DEFINE AE_{HIST,MSV}_DEFAULTS_TOF_LIOW2 overridden to 2000us and a printf inside the code chunk which sets it confirming that 2000 was being sent, so I am confident it was decreased. Good to know that setting lme_msv will get it to respect the exposure_max_us, that was pretty unclear.
Changes:
diff --git a/src/config_defaults.cpp b/src/config_defaults.cpp
index 096ff48..33c5a2e 100644
--- a/src/config_defaults.cpp
+++ b/src/config_defaults.cpp
@@ -223,7 +223,7 @@
0, \
0, \
0, \
- 6000,\
+ 2000,\
0, \
0.0, \
0.0, \
(END)
FPS is set to 5.
And here's another where one of the sensors is given a longer range to ping over:
@Alex-Kushleyev We've also been playing with these sensors, and installed aluminum heat spreaders and even decreased exposure_max_us to 2000 and we are burning up the beta sensors regularly (get overheat warnings, and then eventually they stop drawing power and we only get sporadic "flashes" on the depth returns). We've been running at 5V. We're now almost out of sensors, and out of patience. I see you now have them in the Starling 2 - could you advise on how you have it set up there to avoid these overheating failures?
Edit: we don't have a fan or airflow over these, and our design is nominally water resistant which doesn't permit us to put these in an area with flow from the rotors. We have a fan drawing air over the VOXL itself internally but the previous gen ToF had absolutely no issue with being mounted away from air flow and working reliably. I am looking for a solution which permits that. Extended range is useless to me if the sensors die on the ground.
@Inhan-Kang Did you ever resolve this issue? We may have a similar one. Ruled out power issues already by running straight off a powerful 5V supply. It does not reboot though, just goes dark and stops responding over ADB or over the network (we are using Doodle).
@Alex-Kushleyev Thanks! This is helpful. Definitely easier to overheat these than the last gen so good to have the specs on it.
@Alex-Kushleyev just learned you cannot set the exposure max to 1200. 1000 and 1500 work. If you set it to 1200 you get a vague IO error
ERROR: [ERROR] in _sensor_ioctl, ioctl failed: Connection timed out
ERROR: [ERROR] in voxl_cci_read, Failed ioctl call
ERROR: Failed CCI read
Just posting this here as an FYI to other wrestling with these new sensors.
@Alex-Kushleyev Thanks so much for your help. If 1200us was the V1 level we may just set it to that and move forward, making something that works at the previous level with minimal surgery to the drone is our shortest path to success at the moment.
@Alex-Kushleyev It seems to be behaving at present. I picked 2000us since it seemed to give similar performance to the previous sensor. I'm going to try installing the "regular" 1.9.4 with the updated ae_msv setting and run that debug/grep again and make sure the setting is being respected. If so I may be ok, and just had something weird happen earlier since it was running on the bench for a while. What do y'all run on the starling 2 for max exposure? 6000 seemed practically unusable unless very actively cooled and we toasted a couple of these seemingly irrecoverably at that setting when we had them in the enclosure like the old sensors.
Edit: running with default 1.9.4 and the correct settings in conf and it seems to respect 2000us limit. Also, to answer your temp question yes going from 6000 to 2000 made a huge difference in qualitative temperatures.
@Alex-Kushleyev It is M0169, we have yet to see M0171 go up for sale on the store or beta store, but would love some since the wire interface is clunky.
@Alex-Kushleyev Ah, right, sorry. 5V going to the power wires of the two ToF sensors.
@Alex-Kushleyev I will get the screenshots in a moment. lme_msv wasn't set and I noticed that power usage wasn't going down and figured there was just a bug in the config-reading code, so I recompiled with the default exposure value in the #DEFINE AE_{HIST,MSV}_DEFAULTS_TOF_LIOW2 overridden to 2000us and a printf inside the code chunk which sets it confirming that 2000 was being sent, so I am confident it was decreased. Good to know that setting lme_msv will get it to respect the exposure_max_us, that was pretty unclear.
Changes:
diff --git a/src/config_defaults.cpp b/src/config_defaults.cpp
index 096ff48..33c5a2e 100644
--- a/src/config_defaults.cpp
+++ b/src/config_defaults.cpp
@@ -223,7 +223,7 @@
0, \
0, \
0, \
- 6000,\
+ 2000,\
0, \
0.0, \
0.0, \
(END)
FPS is set to 5.
And here's another where one of the sensors is given a longer range to ping over:
@Alex-Kushleyev We've also been playing with these sensors, and installed aluminum heat spreaders and even decreased exposure_max_us to 2000 and we are burning up the beta sensors regularly (get overheat warnings, and then eventually they stop drawing power and we only get sporadic "flashes" on the depth returns). We've been running at 5V. We're now almost out of sensors, and out of patience. I see you now have them in the Starling 2 - could you advise on how you have it set up there to avoid these overheating failures?
Edit: we don't have a fan or airflow over these, and our design is nominally water resistant which doesn't permit us to put these in an area with flow from the rotors. We have a fan drawing air over the VOXL itself internally but the previous gen ToF had absolutely no issue with being mounted away from air flow and working reliably. I am looking for a solution which permits that. Extended range is useless to me if the sensors die on the ground.
@Moderator Thanks for the update and the datasheet. I have not tried building the code since I don't have a reason to until the module itself becomes available and hopefully the code will be out of beta by then. Is there an updated timeline on when this module and its adapters are likely to hit the store?