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.

First samples in datablock with Command : "06" with Firmware version 0.3.0.0

Other Parts Discussed in Thread: LDC1000EVM, LDC1101EVM, LDC1101

There seems to be some strange behaviour on the start samples of each datablock when using New firmware and command "06". The data is normal when reverting back to old firmware using firmware linked in the post "LDC1000 EVM GUI 1_0_4_1"

The problem is that there is a jump in sample value for both type of samples.

I first thought the jump was between the Blocks, but the jump is from first sample in the block to the next sample.

Here is a Picture of 1520 samples of Frequency Counter

Next Picture is a closeup of samples round sample 512. Samplecount start at 0.

The last Picture is Reading With old firmware.

No jumps With old firmware so the sampleperiod is not corrupt for first to samples in Block.

I have reverted to old firmware and that has the needed functionality for my Applications.

I Guess this do not affect New GUI as it no longer read 2k Blocks.

Kind regards

Torgeir Skomedal

Here is a greeting from Norway

LDC1000EVM , coil about 1mm from speakerdiagraph. Heavy eq.

  • Greetings Torgeir,

    Thanks for this info.  We are working on a fix.  In the meantime, if you understand C, you can look in the firmware folder to see how data is being sent out.  You can use command "11" to receive 3k blocks; extra 1k is for 24-bit L.

    Thanks,

  • I have now had a look at the LDC1101EVM. The same thing is happening there.
    The first 8 samples have a much larger sampleperiod than the next 248 samples. At least 2 to 1 difference.
    I can't connect with EVM software so I gather the data with my own COM port USB commands.
    I have looked at earlier versions of LDC1000 firmware and the problem, I think, is caused by simultanious dataretrieving from the LDC1101 and sending data out on USB. I suspect the 5528 can't sustain the rate of data fetching over SPI, when simultaniously sending USB data?

    Do anyone else see this behaviour when using the original user interface?

    Should be easy to see when moving a metal object by hand in front of the coil. Looks like the first 8 samples has more rapid rice or decay than the next 248. (Guess first block of data (512 samples) are OK because no USB data is sent yet).
    Response Time 2, (192)
    Rp+L measurement
    The rest is the values used on startup of EVM

    Is there an option to use data fetching by interupt, dataready on SDO intstead of (in theory) fixed SPI polling rate?
    Regards Torgeir