MMM-GroveGestures / Python script is terminated

[MMRIZE]

@Egnos said in MMM-GroveGestures / Python script is terminated:

Too long cabling, > 30cm. The signal would be weaker or noisy.

It will surely be longer, 40 or 50 cm

Hopefully not, over 30cm long cabling could be the issue. (You wrote 40~50cm, is it right?)

[Egnos]

@MMRIZE Yes, from the GPIO to the sensor there will be about 40/45 cm…

[MMRIZE]

@Egnos
40~45cm seems somewhat too long. Could you build it shorter? or use a lower frequency than usual case.
Ref. these;

• https://learn.adafruit.com/working-with-i2c-devices/cable-length
• https://www.telos.info/faq/i2c-cables-the-shorter-the-better/

[Egnos]

@MMRIZE The path of the sensor cables (Yellow, red, white and black) is this:

Maybe I could shorten the wires a bit…

Thanks for the links.

[ankonaskiff17]

@Egnos Maybe Sparkfun Midpoint and Endpoint to give you ample length. They tout over 100’ with those devices.

[Egnos]

@ankonaskiff17 said in MMM-GroveGestures / Python script is terminated:

Endpoint

Hi @ankonaskiff17, wich one of these?
https://www.sparkfun.com/categories/304?page=1

[MMRIZE]

@Egnos
There are several “I2C Extenders” (Or “Active Terminator”)

I haven’t tried this kind of thing, but it is worth researching.

• https://sandboxelectronics.com/?product=active-i2c-long-cable-extender-p82b715-module
• https://www.adafruit.com/product/4756
• https://www.sparkfun.com/products/16988 (It needs QWIIC environment)

[ankonaskiff17]

@Egnos You want what is called a Midpoint which is
Also need an Endpoint which is this

I whipped this together in double quick time so pardon the lack of tidiness.
For reference sake I focused on a couple of BME688’s to give you sort of a benchmark.
First is screenshot showing both BME’s running. Had to do jumper on one to get a second address 0x76 and 0x77

[ankonaskiff17]

@ankonaskiff17 Here is screenshot of BME688 0x77
It is connected to one of my Endpoints.

[ankonaskiff17]

@ankonaskiff17 50 ft ethernet

And the money shot. 50 ft cable