Hi, I encountered a similar issue. When the QR code reader is in auto-scan mode, if the barcode is scanned more than once while the main program is in a delay state (e.g., 5000 ms), the barcode reader stops responding after the delay ends, and the data can no longer be read. I also tried reading the barcode from the image in the previous post, but nothing changed.
Additionally, I have confirmed that communication is restored and the device becomes usable again by unplugging and reconnecting the I2C cable. Is it possible to reset the barcode reader programmatically?

@RPI25 said in Is it possible to use the M5GO Bottom 3 with the Tab 5:

M5GO Bottom 3

Hi RPI25 (and felmue)

I am guessing (as you didn't say) that you want to use the Battery function of the M5GO to power the TAB5? Or is there another reason you wish to add the M5GO to the TAB5?

With that said on the M5Stack Store it very specifically states that each "version" of the M5GOs are designed to work with a specific Core ONLY. I included a graphic as well:

M5GO.PNG

I did compare pinouts that were provided by Felix (thanks!) and again I am only guessing is that you are after the battery function? With that said I would simply purchase the battery (which I did do with my TAB5).

I am curious about your project?

Thanks-Brian

Hello @KAYDE1

maybe checkout this example here?

To make it work I had to adapt the GPIO used for the LEDs:

// buscfg.pin_data = 26; buscfg.pin_data = 25;

I also added a delay(1000); at the end of the loop().

Thanks
Felix

@cleatus007 using grove cable and connect to port on side of cardputer

@felmue @mlindholm
I recently had the same problem with I2C on an M5STAMP C3U.
The appropriate solution seems to be the @mlindholm one, but its sample code was a bit incomplete
Here is a working example in the context of a DS3231 RTC
A TwoWire structure needs to be inititalised specifically, then referenced by the used I2C library (if any ; RTC library in my case).
No need for pullup resistor (in my case)

#include <Wire.h>

// Declare alternate I2C pins
#define I2C_SDA 5
#define I2C_SCL 4

// Setup the TwoWire instance (static memory !)
TwoWire I2CM5 = TwoWire(0);

void setup ()
{
...
// Initialise the TwoWire instance
I2CM5.begin(I2C_SDA, I2C_SCL, 400000);

// Ask the library to use this setting
// (most I2C libraries accept a TwoWire object as argument of begin)
rtc.begin(&I2CM5);
...

@iorex I’ve had partial success using the Roller485 with the pwrCan module. Your setup looks similar to mine, except I’m using a Core3, so my pin numbers are different.

First, check whether your motor is in RS485 mode. The screen on the back should show COM: 485.
Second, make sure the motor ID is set to 1. The third line on the motor screen should read ID: 0x01.
Lastly, confirm that the motor’s baud rate is 115200 (this is the default).

If all of the above is correct, you can move on to the pwrCan module. Did you flip the resistor for RS485 to the ON position? Are the DIP switches configured correctly?

I was able to control motor speed over RS485, but I still get the error: “Unexpected response length: 32, expected: 17.” It looks like there’s a communication issue from the motor back to the pwrCan module.

As an alternative, you can power the motor using the power pins on the RS485 terminal and send commands via I²C. It requires more wiring, but it works with much less hassle.

@felmue That did it! Thanks a lot!

@dov I think I ran in to the same thing if I understand your question. See if this post helps. It works for my situation

https://community.m5stack.com/topic/7458/midi-synth-unit-with-din-trs-connectors-sam2695?_=1760294339690