Is teh LIS2DH12 deveice sesitive fro RF signals. We have mounted it near antenna's and see some movement in all directions where there is none ....

[HRoer]

..

[HRoer]

Type: is the LIS2DH12 device sensitive for RF signals.?

[Miroslav BATEK]

It is very generic question.

Can you share some example of the outputs from the sensor?

What is the frequency of the RF signal and what is the intensity of the magnetic field?

[HRoer]

The RFID is at 13.56MHz.

What we have done so far is to test the accelerometer on the PCB with and without the RFID active. When we saw that the chip showed undesired behavior with the RFID active, we tried relocating it. This was done by removing the device from the board and glue a new device on top of the microcontroller (which is slightly further away from the RFID antenna). This new device has been connected to the PCB by wires.

What we had seen earlier was that this did not resolve the issue. Interrupts still occurred even though the accelerometer was completely stationary on the desk. It did also respond correctly to actual movement as we expect. Today I also hooked up a logic analyzer to the SDA, SCL and interrupt lines to see what the exact behavior was on the signal wires that connect to the accelerometer in the stationary situation.

In the attachments I have included 2 pictures, the first is the overall behavior of these three signals observed (both analog as digital). The second is a zoomed in view on one of the interrupts.

These figures show that the signals on the wires are well defined in the sense that they do not show any spikes. Every interrupt that occurs, is a well-defined transient from 3V3 down to 0V. This leads us to the conclusion that there is no coupling of signals into the wires. So any misbehavior of the sensor can only be caused by external effects that occur due to coupling of signals directly into the sensor itself.

In the attached pictures, the RFID field is only activated after 17.5 seconds. So it seems that the relocation of the sensor made the problem worse in the sense that now even the microcontroller alone influences the interrupt-behavior of the sensor. And even on this new location, the RFID field (13.56MHz) still seems to have an impact, as after 17.5 seconds, the amount of interrupts increases significantly.

The tests above seem to indicate that the sensor is extremely susceptible to external electronic field influences. In the documentation it is clearly stated that below the chip (between the pins) there should be no PCB tracks. In the PCB we have a ground plane below the chip. Please advise on what the preferred solution is for the PCB design / neighborhood with or distance from other signals.

We are currently also evaluating moving the device to a location next to the Bluetooth module. This module is completely shielded by a grounded cage and should therefore negate most of the effects of the RFID field. Although then the Bluetooth module may interfere with the sensor, which is what we still have to evaluate.

These are the only tests we have performed so far. The RFID antenna is completely surrounding the entire board, it is not really possible to test this without significant board changes.

We have received a few sample modules (STEVAL-MKI151V1 - Evaluation Board, LIS2DH12 ) to do some additional measurements independent from the current PCBA design.

[HRoer]

​files

[HRoer]

..

[Miroslav BATEK]

Thank you for the information.

Can you please share your sensor configuration? I would like to know the mode of the interrupt.

Isn't the interrupt only too sensitive? I see many interrupts even if the RF is not active.

The ground plane under the sensor is not good.

Sensor close to Bluetooth should be a problem, set have several demo boards like SensorTile where the sensor are next to the Bluetooth and it works well.

[HRoer]

Hello, below the setting we use. Note the system behaves as expected if the RFID field is off.

register Register name  value bit              setting

0x20      Ctrl 1     0x57      datarate 100hz, Low power enable off, all axis enabled

0x21      Ctrl 2     Not set Default, all filters off

0x22      Ctrl 3     0x40      interrupt active pin 1

0x23      ctrl4       0x08      block data continuous update, BLE LSb, full scale selection: 00 => full scale, High resolution mode, self test off, SPI 4 wire interface

0x24      ctrl 5      0x00      fifo disabled, reboot memory: content normal mode, interrupt requests: not latched, 4D detection disabled

0x25      ctrl6       0x02      active low interrupts

0x2e     ctrl fifo 0x00      triggering on int1

0x30      int1cfg 0x7f     6 direction detection

0x32      int 1 threshold 0x05      threshold = 5*16mg

0x33      int 1 duration   0x01      10ms

[Miroslav BATEK]

This question is being solved by online support (OLS) it will update this post when a result will be found.