Hi Vittorio,
This sounds like part of the problem is that the calibration routine in the firmware update procedure went awry. This means that your EVM defaults are not optimal - they could be completely off. In the case this happens, you set your values in the register page to:
Texas Instruments,LDC1000 EVM GUI,1.0.4.1,Register Configuration File,LDC1000,0x0300
Address,Value,Default,Type,Register Name
0x00,,,Byte,Revision ID
0x01,0x10,0x10,Byte,Rp_MAX
0x02,0x3F,0x3F,Byte,Rp_MIN
0x03,0x15,0x15,Byte,Sensor Frequency
0x04,0x17,0x17,Byte,LDC Configuration
0x05,0x00,0x00,Byte,Clock Configuration
0x06,0x00,0x00,Byte,Comparator Threshold High LSB
0x07,0x14,0x14,Byte,Comparator Threshold High MSB
0x08,0x00,0x00,Byte,Comparator Threshold Low LSB
0x09,0x15,0x15,Byte,Comparator Threshold Low MSB
0x0A,0x04,,Byte,INT Pin Configuration
0x0B,0x01,,Byte,Power Configuration
0x20,,,Byte,Status
0x21,,,Byte,Proximity Data LSB
0x22,,,Byte,Proximity Data MSB
0x23,,,Byte,Frequency Counter LSB
0x24,,,Byte,Frequency Counter Mid-Byte
0x25,,,Byte,Frequency Counter MSB
Then, click "Save Values as Defaults"
I've attached the configuration file you can load:
(Please visit the site to view this file)
Are you running multiple instances of the GUI? In the new version of the firmware, the INT pin is set to DRDYB, which is constantly aggregating data. Was any rework done on the EVM?
Thanks,