This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello.
I am trying the FDC1004 integration for an industrial project.
I noticed that the value I read with i2C slipped after a while (a few minutes later).
I tried it in a second period, thinking that the problem might be caused by the circuit.
I tried it in a second integration, thinking that the problem might be caused by the integration.
The value continued to slipt(or shift).
A second series in my hand; FDC2114
I did the experiment on this. After 1-2 days, the value continued to slipt(or shift).
The values I read with FDC1004;
value : 6950370
.... a few seconds
value : 6960318
... a few seconds
value : 6965237
... a few seconds
value : 6969183
... a few seconds
value : 6980709
... a few seconds
value : 6987472
... a few seconds
value : 6996295
... a few seconds
value : 7011774
...........7041088
These data are not raw data.
Bubble sort filter was applied in a 100-element array.
Hi,
We have received your question. I will get back to you in 2-3 days.
Regards
Sharath.
Hi,
Please share the raw data for this measurement. It is difficult to understand what could be wrong with the shared data.
Regards
Sharath.
Hello again.
Raw data;
8264127
8265718
8274179
8267474
8249038
8271534
....
8301048
8318869
8301832
8294324
8281856
....
8300944
8286262
8322932
8314002
8302491
8286243
...
8286875
8316973
8313650
8321543
8306253
8286603
What I'm trying to say is this;
Examine 3 digits on the left
Any object is approaching.
There is no change in the environment.
However, the values are increasing.
So even though the object is not approaching, I perceive it to exist
Hi,
Thank you for providing the raw data.
I am wondering if this is related to I2C reading issue? Did you make sure that the I2C communication has no issues while you are reading this data continuously? How many devices showed this behavior? Is it on a few boards or all of them are showing the same pattern?
Regards
Sharath.
Hello. Thankyou for answer.
Two of the 3 sensors showed.
Then I soldered the properly functioning sensor to another pcb.
it started shifting the values.
(I think) Unlike other companies, you do not provide code support.
I don't know if there might be an error in my code.
// CHA+ slct CHB- slct CH - offset
FDC1004_write(CONF_MEAS1, 0x1000); //0x08 ||000 < || 100 || 00001
FDC1004_write(CONF_MEAS2, 0x1c00);
FDC1004_write(CONF_MEAS3, 0x1c00);
FDC1004_write(CONF_MEAS4, 0x1c00);
FDC1004_write(FDC_CONF, 0x0580); //0x0c//0000110010000000 0x0580
FDC1004_write(OFFSET_CAL_CIN1, 0x3fff); //0x0D//0x0D 16.384 //3fff
FDC1004_write(GAIN_Cal_CIN1, 0x500F); //0x11 16.384
done = FDC1004_read(FDC_CONF);
if(bit_test(done,3))
{
MEAS1_LSB_1 = FDC1004_read(MEAS1_LSB);
MEAS1_MSB_1 = FDC1004_read(MEAS1_MSB); // 0x1c
MEAS1_LSB_1_H = make8(MEAS1_LSB_1,1);
MEAS1_LSB_1_L = make8(MEAS1_LSB_1,0);
LAST_VALUE = make32(MEAS1_MSB_1,MEAS1_LSB_1_H);
}
Hello there. Were you able to find a solution? I also used the last integration in my hand. Others are slipping too. :(
Hi,
Can you share the setup of the application? I am not sure what could be causing based on the provided information.
How many devices were showing this behavior? Can you test the sensor and application by attaching it to the EVM?
Regards
Sharath.