SmartSonic™ MEMS Ultrasonic ToF Sensors

phpbb forum ID
38298
By chenpanpan8210… , 2 March 2022

I'm stuck with starting CH201.
1.it seems that I've finished program with firmware successfully .but I can't received a right ready flag from ch_common_get_locked_state().and it means that actually program and starting CH201 is failed .are there any suggestions ?
2.I don't know how to verify program sensor with firmware .Can I read the firmware from sensor and compare it with firmware I need to program ?if I can ,and then how do I have to do ?

By imnooee1gmailcom , 22 February 2022

Hello all, I am working on a device to detect potholes, I want to use the ch201 features like range and a-scan, I captured the data and plotted it, but I haven't seen any pattern or something that I can identify as potholes, has anyone developed something similar?, or does anyone have an idea of ​​a ch201 configuration that can help me with that?, I Attached 2 images where the red circle is the floor.
Thanks!

By kangus , 19 February 2022

On 2/18/2022 I installed SmartSonic 1.11.6 and following the directions in AN-000155-SonicLink-Software-Quick-Start-Guide-rev1.0.pdf I attempted to get the SonicLink application to work, it doesn't. I can configure the CH-201 but clicking the Done button closes the configure window without showing a configured device to work with. when I start Soniclink it see the configured CH-201 but does not display it.
The AN-000155-SonicLink-Software-Quick-Start-Guide-rev1.0.pdf it dated, links are broken, Atmel Studio 7 is now Microchip Studio and setup is completely different.

By kangusaaesus , 19 February 2022

I have tried three times to get this DK-CH201 $200 'kit' to work, it doesn't:
Download and follow AN-000155-SonicLink-Software-Quick-Start-Guide-rev1.0.pdf

Install SmartSonic_1.11.6_installer which installs SonicLink 1.11.6

Plug DK-CH201 into my computer with two UB cables

Launch SonicLink and Connect -> show FW Version 1.11.7

Configure Sensors and setup the CH201 on the DK-CH201

Click Done

and in the Sensors window where is nothing, without anything there I cannot do anything.

By jkline1catamou… , 18 February 2022

Hello All,

I am trying to interface the CH-201 ultrasonic range-finder with a dsPIC33CH512MP508 16-bit microcontroller using the MPLABX IDE. I see that the "hello chirp" example application is targeted towards the DK-CH201 development board using a SAMG55 MCU as the host. Does anyone successfully developed a board support package for a PIC MCU? Any help porting the BSP files to a PIC would be much appreciated! Thanks.

By helgemimbergph… , 16 February 2022

Hello together,

I am working on a project where the sensor is part of a traveling object and is aligned, so that the sensor faces 90 ° left to the direction of travel.
What I am looking for is the possibility to restrict the detection angle on the front side of the moving object.
The numbers are not set in stone and need more testing. But what I am looking for is close to this:

Angle of detection in reference to direction of travel: from 45° CCW to ~160° CCW.

By alexanderwalde… , 10 February 2022

Hi! I am struggling with interfacing the CH201 chip from my SAMD21G18A MCU.

I am currently trying to do a simple I2C scan of all available nodes on the I2C bus. This part of the program i working fine as other I2C devices on the same bus do respond.

My schematics is attached. As you can see, I have a standard 3.3V SDA/SCL I2C bus, where I do a level shift between the CH201 lines in order to get the 1.8V level. My oscilloscope does confirm this working.

So again, my problem is there is no reponse from the CH201 chip. Any suggestions??

By garymetallervlcouk , 1 December 2021

I have a design using the CH101 and I never seem to see the INT pin being pulsed either when the mode is free running or pitch/catch.

When it's free running I have the INT pin connected to an I/O expander device (yes it's 1.8V) and the pins are configured as inputs.
If it's configured for pitch/catch the I/O expander pin is set to be output and input as needed. I see my pulse being generated on the INT pin shortly before the pin is configured as an input, but never see the INT pin pulse. The pulse is rather longer than normal (compared to say the dev board) at around 100uS.