Hello Christian! Thank you for your feedback. Indeed, something is wrong, could you please send me your workspace file? To make it simpler you just need to go in the settings menu and hit "Send report to ikalogic". In this way, we'll have everything we need to solve the problem.
Hello ikamal, It's done. Thanks ! Christian
Hello Ikamal, Do you have news about the I2C T & H protocol? Thank you. Christian
Hello Christian, It's still in the pipe. I'll get back to you as soon as it's done.
Hello ikamal, I just installed version 3.0.17 and the problem still seems to be there. Have you any news ? Thanks you in advance. Christian
Hi Christian, I've assigned Vlad (from our team) to this issue, he's on it and will get back to you ASAP. Thanks for your understanding.
Thanks you in advance to both of you!
Hello Christian, I've just updated this decoder to the version 1.36. It should working now. If you have already an old workspace with previous versions of this decoder, you'll need to remove the old version first, otherwise you'll get "missing parameter" errors.
hello Vadislav, Thank you for your help ! But the new version of the protocol does not work either for me (while the basic I2C protocol works well), see screenshot attached. Maybe it's because the SHT20 does not work at a standard speed? (62.5KHz instead of 100K or 400K). Christian [I2C_SHT20_2018_08_25_](//muut.com/u/ikalogic/s3/:ikalogic:qvBT:i2c_sht20_2018_08_25_.jpg.jpg)
Hi Christian, I would like to know if your problem is solved by the modifications from Vlad. Please could you remind here if it works ? Thanks !
Hello Nicolas, no it doesn't works. Christian
Hi Christian, I don't understand what is wrong with your previous screen shoot. According to the SHT20 datasheet, 0xF3 is the command that read the temperature with no hold, isn't it ?
Hello, Indeed, you're right, it works !! (I was not looking at the right place in the frame). Thank you very much ! Just a quick note, when the humidity measurement is done on 12 bits, I think that on the 2 bytes of the measure the last quartet must be reset to 0 before doing the calculation. This is what I understand from reading chapters 5.4 and 6 of the datasheet. So in the attached capture maybe it would be 37.60% rather than 37.62%. But this is a detail, it is not significant on the final value (your opinion interests me anyway). Thanks again to the team for your help ! Christian [Protocol_I2C_T&H_37-62pc](//muut.com/u/ikalogic/s3/:ikalogic:9Tso:protocol_i2c_th_3762pc.jpg.jpg)
That reset isn't shown on the signal but the calculus is made the right way during the decoding. Even if it would have been forgotten, the value of the error due to this 2 bits, in the worst case, is 125* 0b11 / 65536 = 0.00572 (unity is %) that is not significant with our data display. Moreover, the sensor accuracy is about +/-3%. So I don't think it's significant at all :) I hope I had helped you !