SmartSonic™ MEMS Ultrasonic ToF Sensors

Hello!

In the datasheet for the MOD CH-101, it states on page 10:

Hi all,

In the document AN-000154 "CH-101 Example Driver Hands On" Chapter 5 USING ALTERNATE SENSOR FIRMWARE IMAGES

To use a special firmware version that uses less power when the device is idle, define USE_LOW_POWER in main.h (at or near line

107). This version has a significant disadvantage, however – the performance of the CH-101 sensor is negatively affected by sunlight.

Therefore, it is not recommended for most applications.

We already use Normal and Short Firmware provides in SmartSonic_HelloChirp_v1_0_3

Hi all,

We have been integrating the SonicLib Library and the “SmartSonic_HelloChirp_v1_0_3” example with our software architecture to run the program on the PCB that we have designed (with STM32L4).

We tested with MOD_CH101 horn. (AH101-180180???)

Where can we get these other horns?

Acoustic Interface Part Number
AH101-180180
AH101-045045
AH101-045045-MR
AH101-030060

And the Ingress Protection Acoustex 042?

Best Regards

Hi all,

We have been integrating the SonicLib Library and the “SmartSonic_HelloChirp_v1_0_3” example with our software architecture to run the program on the PCB that we have designed (with STM32L4).

Is the SonicLib library available for use it with CH201 instead of CH101?

In the source code I have seen the Firmware for the CH101 (const unsigned char ch101_gpr_open_fw[CH101_FW_SIZE]), but not for the CH201.

Best Regards

Sergio

Hi all,

We have been integrating the SonicLib Library and the "SmartSonic_HelloChirp_v1_0_3" example with our software architecture to run the program on the PCB that we have designed (with STM32L4). After solving some problems we think we have everything working correctly.

the existing chirp driver assume a group of sensors so bsp requires to implement quite a few group related API. (chbsp_group_xxx)
however for most viable use case we have only single sensor and very limited code/mem budget to implement such useless API.
is there possible to consider this scenario to have a light weight driver/API for easier integration ?

also the driver contains firmware of CH-101 (2kB) that must be in MCU storage, is there possible a model which carries default firmware that MCU don't need to prog the CH-101 with such firmware ?

Hi All,

in chirp driver ch_driver.c the fucntion chdrv_wait_for_lock() :

int chdrv_wait_for_lock(ch_dev_t *dev_ptr, uint16_t timeout_ms) {

	uint32_t start_time = chbsp_timestamp_ms();

	int ch_err = !(dev_ptr->sensor_connected);
	while (!ch_err && !(dev_ptr->get_locked_state(dev_ptr))) {

		chbsp_delay_ms(10);

		ch_err = ((chbsp_timestamp_ms() - start_time) > timeout_ms);

	}

Hello, I am having trouble connecting to the DK-CH101 developer kit via SonicLink. I was able to successfully flash the MCU firmware, however when I hit "Connect", I get a window with the title "Core error" and text "FW open error". Here is the contents of the console from my session:

2 new documentation has been added for the CH-101. They are the

1. AN-000209 MOD_CH101-03-01 Retrofit with 45 FoV Horn v 1.1 - which details how you can take a DK-CH101 or a MOD-CH101 board which has a 180 deg FOV cap included, and add on a 45 deg FOV horn on top of the cap to change the CH-101 FOV to 45 deg.

2. AH-10133-045045MR.STEP - this is the 3D STEP file for customers to 3D print their own 45 deg FOV horn.

Enjoy!

Hello,

Gesture recognition is one of the applications for the CH-101 I have found in online videos/articles.

I was wondering if anyone had attempted this using the Smart Sonic development platform?