Steppers won't move after firmware update

I have a mpcnc that I bought off of someone. Everything was working fine but I updated the firmware and now the steppers won’t move. I have no control over any axis. Repetier will connect to the Rambo board and the display shows the movement commands but the steppers aren’t actually moving.

04:50:41.454 : OpenGL version:1.1.0
04:50:41.454 : OpenGL extensions:GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture
04:50:41.454 : OpenGL renderer:GDI Generic
04:50:41.454 : Fast VBOs for rendering not supported. Using slower default method.
04:50:44.882 : Printer reset detected - initializing
04:50:44.882 : start
04:50:44.882 : Marlin 515S 2.1.1
04:50:44.882 : echo: Last Updated: 2022-08-06 | Author: (V1 Engineering, Ryan, 515S)
04:50:44.882 : echo: Compiled: Apr 13 2023
04:50:44.890 : echo: Free Memory: 2851 PlannerBufferBytes: 1728
04:50:45.066 : echo:DIGIPOTS Loading
04:50:45.066 : echo:DIGIPOTS Loaded
04:50:45.074 : echo:DIGIPOTS Loading
04:50:45.074 : echo:DIGIPOTS Loaded
04:50:45.082 : echo:V86 stored settings retrieved (629 bytes; crc 46795)
04:50:51.915 : FIRMWARE_NAME:Marlin 515S 2.1.1 (Apr 13 2023 04:43:10) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1CNC 515S EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
04:50:51.915 : Cap:SERIAL_XON_XOFF:0
04:50:51.915 : Cap:BINARY_FILE_TRANSFER:0
04:50:51.915 : Cap:EEPROM:1
04:50:51.915 : Cap:VOLUMETRIC:1
04:50:51.915 : Cap:AUTOREPORT_POS:0
04:50:51.923 : Cap:AUTOREPORT_TEMP:1
04:50:51.923 : Cap:PROGRESS:0
04:50:51.923 : Cap:PRINT_JOB:1
04:50:51.923 : Cap:AUTOLEVEL:0
04:50:51.923 : Cap:RUNOUT:0
04:50:51.923 : Cap:Z_PROBE:0
04:50:51.923 : Cap:LEVELING_DATA:0
04:50:51.923 : Cap:BUILD_PERCENT:0
04:50:51.923 : Cap:SOFTWARE_POWER:0
04:50:51.923 : Cap:TOGGLE_LIGHTS:0
04:50:51.923 : Cap:CASE_LIGHT_BRIGHTNESS:0
04:50:51.931 : Cap:EMERGENCY_PARSER:0
04:50:51.931 : Cap:HOST_ACTION_COMMANDS:0
04:50:51.931 : Cap:PROMPT_SUPPORT:0
04:50:51.931 : Cap:SDCARD:1
04:50:51.931 : Cap:MULTI_VOLUME:0
04:50:51.931 : Cap:REPEAT:0
04:50:51.931 : Cap:SD_WRITE:1
04:50:51.931 : Cap:AUTOREPORT_SD_STATUS:0
04:50:51.931 : Cap:LONG_FILENAME:0
04:50:51.931 : Cap:LFN_WRITE:0
04:50:51.939 : Cap:CUSTOM_FIRMWARE_UPLOAD:0
04:50:51.939 : Cap:EXTENDED_M20:0
04:50:51.939 : Cap:THERMAL_PROTECTION:1
04:50:51.939 : Cap:MOTION_MODES:1
04:50:51.939 : Cap:ARCS:1
04:50:51.939 : Cap:BABYSTEPPING:0
04:50:51.939 : Cap:CHAMBER_TEMPERATURE:0
04:50:51.939 : Cap:COOLER_TEMPERATURE:0
04:50:51.939 : Cap:MEATPACK:0
04:50:51.939 : Cap:CONFIG_EXPORT:0
04:50:51.947 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
04:50:51.947 : echo:DEBUG:INFO,ERRORS
04:50:51.947 : echo:No media
04:50:51.955 : echo:Unknown command: “M80”
04:50:51.963 : echo:DEBUG:INFO,ERRORS
04:51:02.528 : Reporting endstop status
04:51:02.528 : x_min: open
04:51:02.528 : y_min: open
04:51:02.528 : z_min: open
04:51:05.080 : FIRMWARE_NAME:Marlin 515S 2.1.1 (Apr 13 2023 04:43:10) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1CNC 515S EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
04:51:05.080 : Cap:SERIAL_XON_XOFF:0
04:51:05.080 : Cap:BINARY_FILE_TRANSFER:0
04:51:05.080 : Cap:EEPROM:1
04:51:05.080 : Cap:VOLUMETRIC:1
04:51:05.080 : Cap:AUTOREPORT_POS:0
04:51:05.080 : Cap:AUTOREPORT_TEMP:1
04:51:05.088 : Cap:PROGRESS:0
04:51:05.088 : Cap:PRINT_JOB:1
04:51:05.088 : Cap:AUTOLEVEL:0
04:51:05.088 : Cap:RUNOUT:0
04:51:05.088 : Cap:Z_PROBE:0
04:51:05.088 : Cap:LEVELING_DATA:0
04:51:05.088 : Cap:BUILD_PERCENT:0
04:51:05.088 : Cap:SOFTWARE_POWER:0
04:51:05.088 : Cap:TOGGLE_LIGHTS:0
04:51:05.088 : Cap:CASE_LIGHT_BRIGHTNESS:0
04:51:05.088 : Cap:EMERGENCY_PARSER:0
04:51:05.096 : Cap:HOST_ACTION_COMMANDS:0
04:51:05.096 : Cap:PROMPT_SUPPORT:0
04:51:05.096 : Cap:SDCARD:1
04:51:05.096 : Cap:MULTI_VOLUME:0
04:51:05.096 : Cap:REPEAT:0
04:51:05.096 : Cap:SD_WRITE:1
04:51:05.096 : Cap:AUTOREPORT_SD_STATUS:0
04:51:05.096 : Cap:LONG_FILENAME:0
04:51:05.096 : Cap:LFN_WRITE:0
04:51:05.096 : Cap:CUSTOM_FIRMWARE_UPLOAD:0
04:51:05.104 : Cap:EXTENDED_M20:0
04:51:05.104 : Cap:THERMAL_PROTECTION:1
04:51:05.104 : Cap:MOTION_MODES:1
04:51:05.104 : Cap:ARCS:1
04:51:05.104 : Cap:BABYSTEPPING:0
04:51:05.104 : Cap:CHAMBER_TEMPERATURE:0
04:51:05.104 : Cap:COOLER_TEMPERATURE:0
04:51:05.104 : Cap:MEATPACK:0
04:51:05.104 : Cap:CONFIG_EXPORT:0
04:51:05.112 : echo:DEBUG:INFO,ERRORS

515S is the serial firmware. Do you have anything wired to the E0 or E1 ports?

It looks like you compiled this yourself. That’s fine. Did you change anything? You got this from the MarlinBuilder releases, right?

You can flash the provided .hex with xloader. But compiling it while flashing it is fine.

Can you share a picture of the rambo all wired up?

I got it from the link: v1e/electronics/marlin-firmware/

I tried your idea and flashed the hex with xloader but I have the same problem. Here is the new output:

05:49:18.558 : Reporting endstop status
05:49:18.558 : x_min: open
05:49:18.558 : y_min: open
05:49:18.558 : z_min: open
05:49:21.167 : FIRMWARE_NAME:Marlin 515S 2.1.1 (Sep 25 2022 17:43:03) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1CNC 515S EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
05:49:21.167 : Cap:SERIAL_XON_XOFF:0
05:49:21.167 : Cap:BINARY_FILE_TRANSFER:0
05:49:21.167 : Cap:EEPROM:1
05:49:21.175 : Cap:VOLUMETRIC:1
05:49:21.175 : Cap:AUTOREPORT_POS:0
05:49:21.175 : Cap:AUTOREPORT_TEMP:1
05:49:21.175 : Cap:PROGRESS:0
05:49:21.175 : Cap:PRINT_JOB:1
05:49:21.175 : Cap:AUTOLEVEL:0
05:49:21.175 : Cap:RUNOUT:0
05:49:21.175 : Cap:Z_PROBE:0
05:49:21.175 : Cap:LEVELING_DATA:0
05:49:21.175 : Cap:BUILD_PERCENT:0
05:49:21.175 : Cap:SOFTWARE_POWER:0
05:49:21.183 : Cap:TOGGLE_LIGHTS:0
05:49:21.183 : Cap:CASE_LIGHT_BRIGHTNESS:0
05:49:21.183 : Cap:EMERGENCY_PARSER:0
05:49:21.183 : Cap:HOST_ACTION_COMMANDS:0
05:49:21.183 : Cap:PROMPT_SUPPORT:0
05:49:21.183 : Cap:SDCARD:1
05:49:21.183 : Cap:MULTI_VOLUME:0
05:49:21.183 : Cap:REPEAT:0
05:49:21.183 : Cap:SD_WRITE:1
05:49:21.183 : Cap:AUTOREPORT_SD_STATUS:0
05:49:21.191 : Cap:LONG_FILENAME:0
05:49:21.191 : Cap:LFN_WRITE:0
05:49:21.191 : Cap:CUSTOM_FIRMWARE_UPLOAD:0
05:49:21.191 : Cap:EXTENDED_M20:0
05:49:21.191 : Cap:THERMAL_PROTECTION:1
05:49:21.191 : Cap:MOTION_MODES:1
05:49:21.191 : Cap:ARCS:1
05:49:21.191 : Cap:BABYSTEPPING:0
05:49:21.191 : Cap:CHAMBER_TEMPERATURE:0
05:49:21.191 : Cap:COOLER_TEMPERATURE:0
05:49:21.199 : Cap:MEATPACK:0
05:49:21.199 : Cap:CONFIG_EXPORT:0
05:49:21.199 : echo:DEBUG:INFO,ERRORS

You’re not going to like this: That should work. I don’t see anything wrong.

How are you sending movements, and are the motors doing anything at all?

The rambo looks like an official one from ultimachine.

I know you changed the firmware. But that all looks fine. Is it possible the wiring came loose or something isn’t plugged in after the update?

Obligatory: check the grub screws. I doubt that is the issue, but it is always worth mentioning. The pulleys slipping on the shafts are an annoying problem.

No, they aren’t doing anything at all. No movement or trying to move. I have already tried reseating all of the connections just in case and I verified that both power ports have 24v. I could understand the grub screws if they were slipping but the motors don’t “fire” at all.

1 Like

It’s almost like a driver issue or something with the board.

The rambos have been very hard to hurt. They are the most reliable.

You should check the fuses. If you turn things on, you shouldn’t measure any voltage if you measure across each fuse. If you measure 24V, then the fuse is blown.

You can also safely remove the endstops. They aren’t needed for motion, only homing. (They aren’t actually helpful at all for serial firmware. In CNC, the zero is determined by the workpiece, not the machine).

The thought on the end stops was to have the router return to “home” after bit changes so it will go back to the work piece in the same place if the carriages move during the tool change. The 24v is measured at the screw terminals at the input. The fuse looks fine. Also, not a newb to milling. I also run my own business and have this at my shop, I just run this at home for me.

W.r.t. endstops, you can set up your coordinates that way. But just beware that most of us don’t, so it hasn’t had as much testing. Machine coordinates vs workspace coordinates are more common in grbl.

You also need a way to make the gantry square. If you have the serial firmware and wiring (like you do), then you need to use some kind of hard stop before enabling the motors. They will move in lock step once you have them enabled, but if you lose steps while tool changing, you need to reset them to square. The single endstops won’t help.

Dual endstops puts each motor on its own driver. That doesn’t do anything except allow the firmware to control the two motors independently when homing. It drives each motor to its own endstop to reset the squareness of the machine. That is probably what you will want to head towards, eventually.

But the motors need to move first. And they should. Disconnecting the endstops is a useful debugging technique, just to ensure they aren’t shorting ground and 5V. Once you have the motors turning, you can mess with the endstops and use them however you want (it is your machine, I am just here to help). Or leave them connected, it is your machine. There is a slim chance they are the issue, but we don’t have any leads.

Ok, powered off and removed the end stops. Still not moving. New run of commands shows x and y min triggered with them unplugged.

1 Like

There are a pair of pins labeled “X30.” In the picture of your wiring, the pins are in the upper left under the cabling and above the big capacitor. These are a pair of aux power out pins on the motor rail. Carefully take the voltage at these two pins. This will tell you if you have power at the motors. Do you know what version of the firmware you were running before?

It wouldn’t hurt to do a factory reset. I think you can do one from the display, but if not, send an M502 followed by an M500.

I do not know the previous firmware version. X30 pins are dead so the motor rails don’t have power. Replaced the only fuse I saw and still no power.

There are at least two additional fuses. Looking at the pinout diagram, they are labeled F2 and F3. These are small fuses. Ryan sells replacements in the V1 store. I’m not sure which fuse is the motor fuse.

So if my research is right, that’s the nano fuse below the capacitor and not the blade fuse.

I took a brief look at the schematic, but could not find the fuses. I suspect the blade fuse controls the heated bed, and the fuse you’ve identified is the motor rail. What is puzzling to me is how updating the firmware resulted in a blown fuse.

Edit: Fuse F2 (the one you’ve identified) is definitely the motor fuse. It says right on the pinout diagram.

Thanks for the help everyone! I have my marching orders.

1 Like

Thanks for the help all. I have confirmed it was the fuse. All is working now. On a related note, in this week’s episode of “don’t try this at home” :rofl:

(This is just for testing purposes. My actual 5A SMD fuses will be here tomorrow)

2 Likes

Oh my. Well, glad it is working for you.

close older topics to help with spambots, and faster new user questions.