Setting up my new MPCNC with a mini rambo. Using the LCD, I can move the Z up and down. X-axis moves back and forth with no problems. But the Y-axis motors just grind and don’t move.
When I switch the connection on the Mini-Rambo (swap the x motor connection with the y motor connection, it moves fine, so there’s not resistance on the conduit preventing movement. I’m pretty certain that I have something mixed up with the wiring, but I can’t track it down. I’ve traced the wires from end to end and they match the X-axis wiring (which works). I’m stumped. Has anyone else had this issue? What am I missing?
Did you try just flipping the stepper connections? One might be working against the other. Mine did something like what this sounds like and I just had to flip the plug on the board - not the plugs between the steppers.
I’m confused. When you switched the X & Y connections at the mini-Rambo, which one moved fine? Did they both work? Can you upload some pictures of your setup?
I’ve had similar issues in the past due to connectors that were poorly made up (by me) such that when I inserted the connector into the board, one of the pins would back out slightly, within the connector body, making poor or no connection.
Here’s a very professional drawing of my wiring. To make sure I wasn’t crazy, I duplicated the wiring that’s on the X-axis, and is working fine. The wiring is from Ryan’s shop.
[attachment file=78348]
I swapped the connection from the board to the 2 Y-axix motors so it runs off if the X-motor connection on the Mini Rambo. Using that connection, the Y motors move as expected.
I swapped the X-motor connection on the board with the Y-motor connection on the board (so the X-motors were running off of the Y-motor control) and the motors just grind.
So, all of that confirms that the wiring is OK. Which makes me wonder if there’s something on the board that is different on the Y-motor connection (not working) than the X-motor connection (working).
This is what mine looked and sounded like when it happen to me. Mine was a bad crimp on a molex connector. Anything under your plastic connector? Anything fall into the second Y connector?
So, Y motors and wires on X output work, X motors and wires on Y output work, X motors and wires on X output works and Y motors and wires on Y axis fail? Or is it the Y motors and wires fail even when connected to the X axis output?
I had a similar situation on a self-built wiring harness with grinding motors. It turned out to be an open circuit on a connector crimp. The crimp looked OK, but when checked with a multi-meter, there was no current flow.
Well, I originally flashed the firmware with my windows pc, and I haven’t used Windows in years. So I switched to my macbook. But when I compile the firmware with the mac, I get this error:
Arduino: 1.9.0-beta (Mac OS X), Board: “RAMBo”
sketch/src/lcd/dogm/u8g_dev_uc1701_mini12864_HAL.cpp: In function ‘uint8_t u8g_dev_uc1701_mini12864_HAL_fn(u8g_t*, u8g_dev_t*, uint8_t, void*)’: sketch/src/lcd/dogm/u8g_dev_uc1701_mini12864_HAL.cpp:114:29: error: ‘U8G_SPI_CLK_CYCLE_300NS’ was not declared in this scope u8g_InitCom(u8g, dev, U8G_SPI_CLK_CYCLE_300NS); ^ sketch/src/lcd/dogm/u8g_dev_uc1701_mini12864_HAL.cpp: In function ‘uint8_t u8g_dev_uc1701_mini12864_HAL_2x_fn(u8g_t*, u8g_dev_t*, uint8_t, void*)’: sketch/src/lcd/dogm/u8g_dev_uc1701_mini12864_HAL.cpp:143:29: error: ‘U8G_SPI_CLK_CYCLE_300NS’ was not declared in this scope u8g_InitCom(u8g, dev, U8G_SPI_CLK_CYCLE_300NS); ^ exit status 1 sketch/src/lcd/dogm/u8g_dev_ssd1306_sh1106_128x64_I2C.cpp: In function ‘uint8_t u8g_dev_sh1106_128x64_2x_2_wire_fn(u8g_t*, u8g_dev_t*, uint8_t, void*)’: sketch/src/lcd/dogm/u8g_dev_ssd1306_sh1106_128x64_I2C.cpp:117:29: error: ‘U8G_SPI_CLK_CYCLE_300NS’ was not declared in this scope u8g_InitCom(u8g, dev, U8G_SPI_CLK_CYCLE_300NS); ^ Error compiling for board RAMBo.
So, Y motors and wires on X output work, X motors and wires on Y output work, X motors and wires on X output works and Y motors and wires on Y axis fail? Or is it the Y motors and wires fail even when connected to the X axis output?
No. X motors and Y motors work on on X output only. Nothing works on Y output.
You flashed your board before? My boards come pre-flashed. What did you flash on there? I would say go back to the windows machine as I can’t really be any help on a MAC, Some have had baud rate issues, yours kinda looks like it is missing the ug8lib, not really familiar with that sort of error.
Yeah, in Arduino you have to add the library before it’ll compile. If you have baud rate issues it won’t show up until after the compile finishes so it’s too early to tell if you’re going to run into it. For reference the default rate is 250000, not 115200.
If nothing works on the Y output on the board then we’re looking at Y output settings and the actual hardware. If you have the default image flashed, which is what Ryan did before sending it to you, then the settings are close to what they should be. If you don’t have his image flashed, such as flashing the stock Marlin instead, you may not have the Y drivers setup to move with the right force…
Well, I’m not really sure what I did, but I reflashed the mini rambo again from the windows PC and everything is working great from the LCD. X, Y, and Z are all good.
I also setup a Raspberry Pi 3 B with V1Pi. It loads fine and I can view the MPCNC through the webcam, but I can’t figure out how to remotely control the motion like I can on the LCD. Is that supposed to work? Are there some tricks to make that happen?
