-
QIs custom algorithm development supported?A
Yes, we highly encourage developing custom algorithms or solutions based on our chips! We provide flexible hardware and software platforms to fully support your custom development.
-
QWhat is the difference between MRS262 and MRS261L?A
The MRS261L is the ultra-low-power version, making it suitable for power-sensitive applications.
The MRS262 is better suited for applications with a continuous power supply.
-
QCan the data be accessed directly?A
Please refer to the provided product technical documentation for detailed instructions.
The SDK is currently under optimization and will be released gradually in the future.
Please stay tuned! Please monitor our official website www.possumic.com for the latest updates on the corresponding product documentation.
-
QIs the power consumption difference between the MRS262 and MRS261L caused by differences in software?A
The MRS261L and MRS262 are separate hardware modules with different specifications.
-
QWhy does the radar fail to detect targets after the enclosure is installed?A
If the enclosure (radome) design does not meet the specified requirements, the radar may exhibit abnormal detection behavior. Symptoms include the inability to detect targets regardless of parameter adjustments, or an abnormally high average operating current in the radar chip.
This is likely due to receiver saturation caused by strong reflections from the enclosure. To restore normal detection, you can try manually reducing the "RX Gain" in the MRS2xxx_Demo_Tool GUI. (Note: If using the MRS251 model, configuring power back-off is required.)
-
QWhy is there a discrepancy between the actual measured current and the current displayed on the GUI tool?A
Possible Cause:
1.The active data reporting function is not disabled, leading to a longer active time and resulting in wasted power.
2.The pin output functions are not disabled, causing power consumption by loads such as LEDs.
-
QWhy do the configurations dispatched from the GUI tool to the module fail to take effect?A
Developers should first verify whether the development board was power-cycled (powered off and then back on) after flashing the firmware and dispatching the configuration table. Please note that dispatched configurations are volatile and will be lost upon power-off!
Solution:
Navigate to the "Release Image" interface to merge the configuration table and the firmware into a new firmware image. Ensure the "Download firmware to Flash" option is checked, and use the GUI tool to flash this newly merged firmware. This ensures the configurations are permanently saved and retained even after a power cycle.