Core 2 and GoPlus2 - how to connect ?
ramaker last edited by
Today I received a Core2 andwant to use it together with the GoPlus2 Modul, that is specially for Core2.
But how can I connect it ?
I try to connect it direct - pulled the extension PCB out and try to connect it.
But the pins are absolutly to short. and there are 4 litte screws on the GoPlus2 module, that are blocking the connection.
The moduleis about 3mm away from the Core2
I unscrewed the plastic part from the Core2. Now I can connect the module to the Core2, but only if I unplug the battery. I
found no way to connect GoPlus2 module and battery.
If the GoPlus2 module is specially for Core2 --- how shall I connect both ??
Arno last edited by
Unfortunately the GOPLUS 2 is not specific to CORE2 it is also the same problem with the FACE2 which is not compatible with the CORE 2 ... It is a big marketing error of M5STACK.
For a better connection I added small pieces of schotch under the PCB at the level of the screws on the GOPLUS 2.
I'm glad I saw this post before I'm trying to buy GoPlus2 for my CORE2. So do you know which DC Motor and Servo Driver Module is specially for CORE2?
ajb2k3 last edited by
I'm working on a project at the moment using the Core2+goplus2 and have connected it all together.
You remove the batter and stick it to the core2 using double sided tape place the Goplus2 on and gently push together.
Next, unstick the battery from the goplus2 and place it in the base. it will just fit but be careful not to damage the batteries covering.
The core2 base will now fit together and it all works.
I don't have the screw sizes needed to fasten it together as I don't have any M3 countersunk screws long enough to secure it together.
@ajb2k3 Thank you!
I don't have GoPlus2 yet, but I can imagine what you said. We have to remove the CORE2 battery and use GoPlus2 battery as the power supply for both CORE2 and GoPlus2. Certainly, we need external DC to provide power for motors. Is my understanding correct?
felmue last edited by felmue
just a heads up. When you stack M5Core2 with GoPlus2 you'll loose I2C functionality on port A. The reason is that IR_OUT in the GoPlus2 uses the same GPIO as the external I2C (SCL) on port A.
Here is the full explanation and possible work-a-round.
Note: M5Core2 internal I2C is not affected.
@felmue Thanks Felix! I saw your comments about IR_OUT earlier in another post. Hopefully they will fix GoPlus2 before I order one.
I actually have another question for you. It's sort of off the topic from this one. But ...
I have a FIRE and 4 Channel DC Motor module. I connected a LEGO motor and used an external DC to power up both FIRE and DC Motor module. I tried their Arduino example. The code was compiled successfully with some modifications, but the motor doesn't move at all. I turned to UIFLOW and saw your post saying current version doesn't support lego board unless downgrade to 1.4.5.
Right now, I can't even make it work. Can you please help me out?
The is the Arduino example I used.
First, the screen didn't even display until I commented out the M5.update(). I changed the initial speed value to 255 and not use buttons to change the value. But the motor still doesn't rotate.
I finally made it. It turns out there are a couple of problems. First, to stack DC Motor Module on FIRE, I had to remove the M5GO Bottom which has the battery. In the example, they have M5.Power.begin(). It doesn't cause problem until it executes M5.update(). If I comment out M5.update(), the buttons don't work. Anyway, this is the first problem. I ended up with commenting out the M5.Power.begin()
The second problem is the if ... else if ... In the example, they used if...else if to catch the button released. It turns out this is not working. It had to be if ... if ...
Well, I'm happy that it finally works.
felmue last edited by
I am glad to hear you got it working. Thank you for reporting back.
I finally received the GoPlus2. I stacked first with my Fire, and used the GoPlus2 Example, the servos work perfectly. I haven't tested the PortB hub and DC motor on Fire yet.
However, when I stack with Core2, the servos don't move at all. The only change I made is replaced #include <M5Stack> with #include <M5Core2>.
Do you have any clue why it doesn't work with Core2?
felmue last edited by
hmm, I think on M5Core2 the I2C bus (using GPIO21 / GPIO22) might get initialized twice. Once through
M5.begin() - Touch.begin()using
Wire1and then again through below line, but using
Wire. That is a recipe for disaster.
setup()try commenting out line
raychmond last edited by raychmond
@felmue Thank you very much for your help. You are the best!
Simply commenting out that line seems not working. But I followed your idea and renamed all "Wire" to "Wire1" in GoPlus2.cpp. It then works. I don't even understand what "Wire1" is.
felmue last edited by felmue
M5Stack (Basic, Fire, Gray, etc.) use one I2C bus for everything. By default it uses
Wirewith GPIO21 and GPIO22.
M5Core2 uses two I2C busses. The internal one uses
Wire1with GPIO21 and GPIO22; the external one (port A) uses
Wirewith GPIO32 and GPIO33.
Since GoPlus2 was designed for M5Stack devices its I2C pins get mapped into the internal I2C bus of M5Core2.
@felmue Thank you Felix.
I tested the PortB hub. It works as well.