SmartSonic™ MEMS Ultrasonic ToF Sensors

Hi,
I'm testing using DK-CH101 and EV_MOD_CH101-01-02 to apply to short range sensing.
In the datasheet, it is mentioned that at least 4cm detection is possible if CH101's Short range FW (CH101 GPR SR) is selected and used.

As a result of the short range detection test, up to about 8.6 cm was detected normally, but from 8.6 cm, the normal range and the error range were alternately detected. (Target is dynamic)
At a short range(below 8.6cm), when the target is stationary, the normal range cannot be detected, and only the error range is detected.

The datasheets say multiple times that there is a way to change the operating frequency fop, yet I never found out how to actually do this in software. Anybody figured this out?
And if fop is the frequency that is used to generate the tx signal and IQ demod the rx signal, why is this something we need to calculate in stopre_op_freq. Shouldn't this be a value we can change in the firmware?

unable to download the SW - SonicLink 2.1.0 for SmartSonic Boards (Updated 2022.02.11)
someone know how?
any help?

I am working with the CH101 in its EV_MOD_CH101-03-01 form. I am integrating it with a microcontroller from MICROCHIP the pic24f16kl401.
I connected the sensor as in the datasheet with the pull-up resistors.
However I cannot communicate with the sensor in I2C. In my protocol I set the PROG and RESET pin to HIGH and I want to read the values in the first two registers of the sensor which is supposed to answer me 0x0a and 0x02. This allows me to check the presence and proper functioning of the sensor. I use as I2C address 0x45.

Hi, I am currently creating a custom board for measuring distance using nrf chip and CH201. In this case, my code always stuck when it is try to write a long buffer message to sensor.

So I just port the code from DK to nrf52 sdk code, but when I run it, it just works on find_sensor function. But at the rest, it doesn't work, no signal communication at all. As you can see in the attached image, there is a logic analyzer, it only shows the signal for find sensor. But at the rest, there is no signal for that.

Hello!

I have been trying to use the CH201 and CH101 sensors with a custom board.
I am able to achieve communication with sensor and do the initialize process until the chdrv_wait_for_lock function, which my setup is not able to perform. Also, it seems the device address does not change accordingly, as expected.

Due to the fact that the previous steps works, is it possible to conclude that it is not a hardware problem?

I have seen other people with the same problem, does anyone know how to solve? Can it have any relation with the INT pin?

Hello guys,
I am working with the DK-CH201 as part of a university project, but I just can't get it to work.
Always (in SonicLink and Microchip) error 4109 appears (see attachment). I have tested several cables and settings etc., but the error remains. I suspect it has something to do with the security bit, but I can't get any further...
Does anyone have any ideas or tips?
Many thanks in advance!

Hello all:

Is it possible to connect to RS-232 directly from the DK-201 board? I can see the output properly when I use USB over serial. But if we use USB to RS-232 cable, we are not seeing any output. I see TEST1, TEST2 and a couple of there connectors. Can I get RS232 from any of these pins? Much appreciate your help.

Thanks,
Prasad

HELLO,the mcu i use is stm32g070cbt,my ch101 can successfully download fw into flash,but when i change the i2c address to application i2c address, and execute the function ch_common_prepare_pulse_timer,i get a NACK from ch101.the attached pic shows that when i send the i2c address and register address, i get ack.But when i send the num_bytes,the sda is very strange,and after that ch101 reply NACK.Anyone know the problem?thx

Hi all,

I'm currently trying to integrate the CH201 eval module with an nRF2840 feather board from Adafruit (Arduino compatible). I've written the required functions for the bsp and run into problems during the setup. Like several other users, I was initially running into problems in the get_locked_state function but as I did some more testing, I traced the root of the problem to the chbsp_i2c_mem_read function in the bsp that I wrote.