Motor Problems Marlin Repetier Rambo1.4

New Home Forum Mostly Printed CNC – MPCNC Troubleshooting – MPCNC Motor Problems Marlin Repetier Rambo1.4

This topic contains 17 replies, has 5 voices, and was last updated by  Chas 2 weeks, 4 days ago.

Viewing 18 posts - 1 through 18 (of 18 total)
  • Author
    Posts
  • #118613

    Chas
    Participant

    Currently using Windows 10 on my laptop on a V1 Engineering MPCNC with Marlin Dual Endstop Firmware on my Rambo1.4. The following is the log of the Repetier Host connecting to the board and having 2, 10 step X, Y manual motor control moves being implemented. Thus far the mpcnc motors aren’t moving like they used to. How could I diagnose the motor problem with commands in Repetier?

    15:04:36.417 : Printer reset detected – initializing
    15:04:36.417 : start
    15:04:36.417 : echo:Marlin 412 bugfix-2.0.x
    15:04:36.417 : echo: Last Updated: 2019-10-02 | Author: (V1 Engineering, Ryan, 412)
    15:04:36.417 : echo:Compiled: Oct 11 2019
    15:04:36.417 : echo: Free Memory: 3472  PlannerBufferBytes: 1488
    15:04:36.589 : N1 M110*34
    15:04:36.589 : N2 M115*36
    15:04:36.589 : N3 M105*36
    15:04:36.589 : N4 M114*35
    15:04:36.621 : N5 M111 S6*98
    15:04:36.621 : N6 T0*60
    15:04:36.621 : N7 M20*22
    15:04:36.621 : N8 M80*19
    15:04:36.621 : N9 M105*46
    15:04:39.656 : N10 M105*22
    15:04:44.143 : echo:SD init fail
    15:04:44.143 : echo:Hardcoded Default Settings Loaded
    15:04:44.159 : echo:  G21    ; Units in mm (mm)
    15:04:44.159 : echo:  M149 C ; Units in Celsius
    15:04:44.159 : echo:Filament settings: Disabled
    15:04:44.159 : echo:  M200 D3.00
    15:04:44.159 : echo:  M200 D0
    15:04:44.159 : echo:Steps per unit:
    15:04:44.159 : echo: M92 X100.00 Y100.00 Z400.00 E100.00
    15:04:44.159 : echo:Maximum feedrates (units/s):
    15:04:44.159 : echo:  M203 X120.00 Y120.00 Z30.00 E25.00
    15:04:44.159 : echo:Maximum Acceleration (units/s2):
    15:04:44.159 : echo:  M201 X400.00 Y400.00 Z100.00 E2000.00
    15:04:44.175 : echo:Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
    15:04:44.175 : echo:  M204 P400.00 R3000.00 T400.00
    15:04:44.175 : echo:Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> J<junc_dev>
    15:04:44.175 : echo:  M205 B20000.00 S0.00 T0.00 J0.01
    15:04:44.175 : echo:Home offset:
    15:04:44.175 : echo:  M206 X0.00 Y0.00 Z0.00
    15:04:44.175 : echo:Endstop adjustment:
    15:04:44.175 : echo:  M666 X0.00 Y0.00
    15:04:44.190 : echo:Material heatup parameters:
    15:04:44.190 : echo:  M145 S0 H196 B92 F0
    15:04:44.190 : echo:  M145 S1 H240 B110 F0
    15:04:44.190 : echo:PID settings:
    15:04:44.190 : echo:  M301 P17.98 I0.98 D83.62
    15:04:44.440 : N11 M105*23
    15:04:44.440 : FIRMWARE_NAME:Marlin 412 bugfix-2.0.x (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1 E CNC EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
    15:04:44.440 : Cap:SERIAL_XON_XOFF:0
    15:04:44.456 : Cap:BINARY_FILE_TRANSFER:0
    15:04:44.456 : Cap:EEPROM:0
    15:04:44.456 : Cap:VOLUMETRIC:1
    15:04:44.456 : Cap:AUTOREPORT_TEMP:1
    15:04:44.456 : Cap:PROGRESS:0
    15:04:44.456 : Cap:PRINT_JOB:1
    15:04:44.456 : Cap:AUTOLEVEL:0
    15:04:44.456 : Cap:Z_PROBE:0
    15:04:44.456 : Cap:LEVELING_DATA:0
    15:04:44.456 : Cap:BUILD_PERCENT:0
    15:04:44.456 : Cap:SOFTWARE_POWER:0
    15:04:44.456 : Cap:TOGGLE_LIGHTS:0
    15:04:44.456 : Cap:CASE_LIGHT_BRIGHTNESS:0
    15:04:44.456 : Cap:EMERGENCY_PARSER:0
    15:04:44.456 : Cap:PROMPT_SUPPORT:0
    15:04:44.456 : Cap:AUTOREPORT_SD_STATUS:0
    15:04:44.456 : Cap:THERMAL_PROTECTION:1
    15:04:44.456 : Cap:MOTION_MODES:1
    15:04:44.456 : Cap:CHAMBER_TEMPERATURE:0
    15:04:44.472 : N12 M220 S100*82
    15:04:44.472 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
    15:04:44.472 : echo:DEBUG:INFO,ERRORS
    15:04:44.472 : N13 M221 S100*82
    15:04:44.472 : Begin file list
    15:04:44.472 : N14 M111 S6*82
    15:04:44.472 : N15 T0*14
    15:04:44.472 : End file list
    15:04:44.472 : echo:Unknown command: “M80”
    15:04:44.472 : N16 M155 S1*87
    15:04:44.487 : echo:DEBUG:INFO,ERRORS
    15:04:52.874 : N17 G1 X10 F2100*2
    15:04:59.580 : N18 G1 Y10 F2100*12
    #118615

    Jeffeb3
    Participant

    Thus far the mpcnc motors aren’t moving like they used to.

    What is different?

    #118620

    K Cummins
    Participant

    Thus far the mpcnc motors aren’t moving like they used to.

    What is different?

    Do you have any idea how hard it is not to post a reply that’s just “Ummm… They aren’t moving the same anymore, duh!”

    #118621

    Jeffeb3
    Participant

    Do you have any idea how hard it is not to post a reply that’s just “Ummm… They aren’t moving the same anymore, duh!”

    I guess too hard, since you said it anyway. 😛

    #118625

    Ryan
    Keymaster

    Maybe you selected the wrong firmware version, or try not using Arcs in you tool path.

    #118638

    Chas
    Participant

    I reflashed rambo1.4 with marlin dual endstop firmware.

    #118639

    Ryan
    Keymaster

    What is it doing or not doing?

    #118643

    Chas
    Participant

    The manual control won’t move the motor. I made the mistake of having the wrong baud rate initially but now am able to receive legible and relevant outputs. Also windows and linux both having same issue. However I can see limit switch triggers. Is there a command to test motors through Rambo?

    #118656

    Jeffeb3
    Participant

    M119 shows the state of the endstops. The commands to move are G1 commands. But that’s what’s being sent when you hit the jog buttons in repetier.

    I don’t think the problem is repetier. It looks right to me. That leaves power, wiring, or something in Marlin.

    FWIW Ryan, if it’s possible to add the firmware version (dual endstops, or whatever) to the version string, that would help with these repetier logs. Maybe dual is the only thing that really could change.

    2 users thanked author for this post.
    #118707

    Ryan
    Keymaster

    FWIW Ryan, if it’s possible to add the firmware version

    I’ll add a “D” I think there is enough room.

    2 users thanked author for this post.
    #118724

    Chas
    Participant

    115volts for power to my Rambo… one of my motor wires may have been disconnected when I fed the wire through the electrical conduit… I’ll quick check wiring, and try using my older board with the new “series” firmware. I’d really like to figure out if it’s wiring or the firmware version… or if the spider’s webs messed up my board…?? For the record I have an “old board” I flashed with “series” firmware and a “new board” with “dual endstop firmware”….

    order of operations:

    1)Check motor wiring manual w/ m119 commands sent

    2)change out to old board w/ “series firmware”

    3)reflash the boards with the newest firmware for “series” and “dual” respectively…

    4)post cool pictures and sleep

    #118726

    Jeffeb3
    Participant

    1) M119 only tests endstops. The rambo has no way to test the motor wiring. You can check it with a multimeter. Each coil should have some non zero, but small resistance.

    2) The wiring will have to change back to series for this test.

    Did you mean 11.5V? 115 would not work.

    #118845

    Barry
    Participant

    1) M119 only tests endstops. The rambo has no way to test the motor wiring. You can check it with a multimeter. Each coil should have some non zero, but small resistance.

    2) The wiring will have to change back to series for this test.

    Did you mean 11.5V? 115 would not work.

    It would make a good flash bulb.

    #119060

    Chas
    Participant

    115 Volts is what my power adapter is set for -the one I bought w/ my MPCNC from V1Engineering. On output it’s 12V. I’m still having trouble moving the motor… I should pry try using the LCD knob manually.

    #119063

    Chas
    Participant

    Another update. I finally got my LCD connection to my Rambo again and the first Rambo board of the two I have, I tested the motors and all of them moved. Therefore I deduce that my issue is a software problem or configuration problem I do not understand how to address nor correct.

    #119065

    Chas
    Participant

    I tried my 2nd Rambo board and with the LCD screen it’s also moving the x, y, and z axis as I adjust it manually. Therefore my Rambo boards work, it’s either a marlin, repetier, or configuration setting issue as to why I can’t manually move the MPCNC with the manaul repetier controls anymore.

    #119068

    Ryan
    Keymaster

    I would un-install and reinstall.

    1 user thanked author for this post.
    #119094

    Chas
    Participant

    Update after uninstalling and reinstalling repetier today and manually setting firmware option to be merlin and not repetier. I had two issues.

    1. Stop Server call was used
    2. Each of my boards use a different port com5/com10.

    Anyways I can manually control both boards from repetier now, and my plan is to follow up with the tutorials then attach the drill and laser mods 😀 Then manufacture my small scale wikihouse 🙂

Viewing 18 posts - 1 through 18 (of 18 total)

You must be logged in to reply to this topic.