Weird behaviour of I2C connection, only irregular detection of sensor by scanner

Hello,

i have two Xsens MTi-3 sensors of which one is placed on a Development Kit and the other is placed on a PLCC28 socket adapter. I wired them to an Arduino Portenta H7 Lite and ran the I2S scanner script. Then i faced a weird behaviour.

When only connecting the MTi-3 on the DK with built-in pull-up resistors the scanner detects him everytime.
When only MTi-3 on plcc-socket connected with external pull-up resistors after a short time the scanner detects him most of the time in the cycle: detect, 6x no detect, detect 2x no detect
When both connected after a short time the scanner detects them both most of the time in the cycle: detect, 6x no detect, detect 2x no detect

So in conclusion, as long as the MTi-3 on the socket is connected, there is a irregularity in detecting the device(s). But because when both connected, there is also suddenly irregularity for the MTi-3 on the DevKit, it seems to me wiring is defenitely correct and the problem lies within the communication process itself. But i have absoulte no idea why. What do i have to do to detect both sensors everytime (and thus use the sensors as intented)?

Edit: When i connect both sensors, i remove the external pull-up resistors because there are already the built-in ones.

What does the manufacture say about their devices not working together?

A lengthy thread with several good suggestions of how to sole the issue has been done already with no solution. Why not contact the people who made the cht and ask them what's the deal?

I already contacted the manufacturer via his support forum:
Communicating with two Xsens MTi-3 devices

There was no answering yet.

I will now send them an e-mail and write a new post again to describe the new faced behaviour.

Maybe they will suggest to use I2C1 or I2C2. :slightly_smiling_face:

Hi,
What size pullups did you use?

Thanks.. Tom.. :smiley: :+1: :coffee: :australia:

The external pull-ups i added manually where 2700 (2k7) Ohms. But when both connected, as i want to use the setup, i can only use the built-in resistors. I guess they are also 2k7 Ohms, as i use them because of recommondation from an article of the manufacturer:
Interfacing the MTi 1-series DK with an Arduino (xsens.com)

Hi,

2K7 may be a bit low, try 4K7.

They are connected between SDA and 5V and SCL and 5V?
Why they say IOREF has we stumped, the standard is 5V rail.

Thanks.. Tom.. :smiley: :+1: :coffee: :australia:

I'm guessing, but the answer may be ... for ioref

  • The PLCC28-device does not have a single power supply pin (3V3) but two: VDDA and VDDIO.

I think you have to supply both... ?

:smiley_cat:

That could be the problem, some sensors need a time delay between supplies being applied to startup properly.

Can you please post a link to data/specs of the sensor?

Also can you post some images of the module/PCB that works OK?

Thanks.. Tom.. :smiley: :+1: :coffee: :australia:

@jkwilborn In fact i had to supply both VDD pins, i am now able to detect both the MTi-3 at the same and every time the scanner scans. What is what i didn't expected, because when running the MTi-3 alone, it was enough to just provide the VDDIO with 3.3V. I thank you all for your support :slight_smile:

@TomGeorge The standard is 5V, but this IMU runs on 3.3V. But as i wrote above it works now :slight_smile: So thanks to you both and have a nice day :slight_smile:

Okay i have a new problem :frowning:
Now that i can detect both IMU's when scanning all I2C ports, i still don't get values from the IMU on the PLCC adapter.
I already tried to read only from the IMU on the socket adapter (with the other IMU completely unwired) to ensure there is no problem like interfering in the communication process, but that doesn't work either. I also tried reading with resistors wired to a 5V power rail. Nothing helps. Any idea?
Maybe we can start at this point: What is the IOREF pin used for in general, and is it possible to imitate a IOREF pin on my Arduino Portenta H7 Lite?

I was reading the first link in the thread... It has a discussion on some of it's idiosyncrasies for electrical connections.

:smiley_cat:

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.