Just got the DK-CH101 dev kit and had some issues getting it to work with SonicLink. So i reflashed it with the SmartSonic_HelloChirp_v1_11_0 firmware with Atmel Studio without any issues. But when reading from the dev kit through RealTerm, i don't get any sensor readings, see attachment.
I'm reading this through the EDBG USB port at baud 1000000. the FTDI USB does not output anything.
- Log in to post comments
phpbb Topic ID
38705
hmm.. doesn't seem like attachment works.
https://imgur.com/6SZwBbo
The switch on the sensor board is toggled to U15 position. Both 1-2 and 3-4 are shorted on J3, and 1-2 and 3-4 are shorted on J1
Seems it reads 0xFFFF from register 0x18
So when time_of_flight == 0xFFFF object is not detected?
https://imgur.com/jCSb74O
But the return value means i2c is working atleast? So something is not right with the initialization of the sensor perhaps?
i've encountered the same issue. both with sonic link software and with the hello chirp example. did you find any workaround?
Unfortunately not.. And the activity on this forum is lacking to say the least.
I've been trying to get in contact with invensense technical support but the only suggestion i got was to flash the firmware with atmel tool instead of the tool provided in the soniclink.
Attached CH101 to STM32F0 Discovery board and ported SmartSonic_HelloChirp_v1_11_0 HAL to STM32. I2C communication seems to work according both osciloscope analysis and CH101 triggering interrupts in free running mode - so I'm assunming CH101 firmware is loaded and operational. However data returned look like random garbage (register dump added):
Also other firwares present in SmartSonic_HelloChirp_v1_11_0 were tested, none of them privides relevant results.
For verification purposes DK-CH101 SmartSonic platform was bought and tested, with pretty much the same result. Any hints? Is it possible to use CH101 for any distance measuring at all?
Thank you.
Having the same issue with CH201, wrote to tech support, lets see if we can have some reply!
Hey michltriopscz,
Have you solved the problem?I would appreciate it if you could provide some information.
Best regards,
Victor
The answer is quite simple. It doesn't work. At least with a reasonable effort.
I soldered my own board with the CH101 and ported to a stm32f-series mcu. It delivered strange results. Due to the CH101-MOD (180 degree FOV) beeing in stock in the meantime I ordered to to verify my boards or the soldering process weren't faulty. I even made an adapter board with the TI SN74 bus driver to ensure I stick as close to the datasheet as possible.
The results are better but far from usable (so my custom horn is definitely part of the problem). In a static scenario (object remains in static for approx one sec) the range measurement jumps from 40 mm to 87 mm straight. If the object is moved the measurement jumps back to 40 mm and so on. I don't see the usecase of such a picky sensor.
By the way: porting was a nightmare. A simple datasheet with register description would have been a huge help.
I simply hope this is a firmware error. The chip itself would have such a wide variety of benefits.
Hello and sorry for late reply,
after some more trial and error, I was able to achieve quite good results. It seems firmware needs some time and target movement to detect obstacle to measure distance to. After that, it gives millimeter accuracy with some samples to be complete off range, which I'm simply discarding (target is always within specific range in my scenario). I was however unable measure the distance without moving the target first.
As a side note, providing library and not documentation is indeed a bit unfortunate.