Show all posts by user
Printing issues ...
Page 1 of 9
Pages: 12345
Results 1 — 30 of 265
Before 2.1.1 linear advance was not compatible with 2208 drivers and would cause them to lock up. This was finally fixed in the new release.
by
MMcLure
-
Firmware - Marlin
It could be the order of the motors - you need to make sure the positions of the motors Z1/Z2/Z3/Z4 match the order of the points listed in Z_STEPPER_ALIGN_XY or if you're using auto point selection you need to set Z_STEPPERS_ORIENTATION correctly.
Also, if you're specifying the points using Z_STEPPER_ALIGN_XY you need to make sure all points are reachable.
That said, I know that 4-motor leveling
by
MMcLure
-
Firmware - Marlin
With PEI and PETG the secret is to have a relatively high Z offset for the first layer. I use an offset of 0.08mm higher for PETG than I use for PLA, and I could probably do a whole 0.1mm and the PETG would still stick well enough. You essentially want no "squish" on the first layer.
That said, you can buy the spring steel sheets with no PEI:
by
MMcLure
-
General
Note that the Z offset value you set with M851 only applies the next time you home (G28). Also, it's only valid if you're homing with the BLTouch.
What does the LCD show for the Z position immediately after homing after you set the Z offset to -1.6? It should show 11.6 if the Z offset is working correctly (10 minus the Z offset).
by
MMcLure
-
Firmware - Marlin
By default Marlin only checks the end stops when homing. You can change this behavior with ENDSTOPS_ALWAYS_ON_DEFAULT or the M120 gcode, or you can enable NO_MOTION_BEFORE_HOMING and/or HOME_AFTER_DEACTIVATE to ensure that motion does not occur before the printer knows where the home position is.
by
MMcLure
-
Firmware - Marlin
Quotetok199hz
To better explain if I send G0 X100 Z100 F3000 both axis are moving at the same speed, which is Z_max_feedrate
Not really. Each axis will move at the speed required for both motions to complete at the same time. If you move X more than Z then X will move faster. G0 X1000 Z100 will result in X moving 10 times faster than Z. It sounds like what you want to happen is to desynchronize
by
MMcLure
-
Firmware - Marlin
M220 is the gcode that sets the feedrate percentage - for example "M220 S120" would set 120%.
by
MMcLure
-
General
If you mean the asterisk and number added at the end of each gcode line, that's not a speed multiplier - it's a checksum used for error correction. It's a necessary part of the protocol for communicating between a print host like OctoPrint and the printer. It does not affect the print speed at all.
by
MMcLure
-
General
Also, it is important to understand that mesh bed leveling (i.e. the Bilinear or UBL in Marlin) is not meant to compensate for a tilted bed plane, but rather for any deviations between the actual bed surface and an ideal plane. It is still important to get the bed as level as possible to the nozzle/gantry so that the leveling is only adjusting for differences in the bed surface. Bed leveling can
by
MMcLure
-
CoreXY Machines
Are you actually doing an explicit "M206 X0 Y0"? I wonder if that's affecting X_MIN_POS/Y_MIN_POS. One thing to experiment with is to compile with NO_WORKSPACE_OFFSETS enabled (which completely takes M206 out of the picture). Though as far as I can tell "M206 X0 Y0" should have the same effect as not setting it at all. I'm honestly stumped. You seem to have your configuration right.
by
MMcLure
-
Firmware - Marlin
Make sure that the probe offset is actually being used. If you send 'M851' it should show what probe offsets are stored in EEPROM. If they are not correct, then you need to use 'M502' and 'M500' to reinitialize your EEPROM with the values stored in the firmware.
Otherwise everything looks fine with your configuration.
by
MMcLure
-
Firmware - Marlin
QuoteRonArt
SOLVED! Now my nozzle is tightened flush with the heating block
This is not a good idea. There should always be a small gap between the nozzle and the heat block so that the nozzle is tight against the end of the heat break - otherwise you're just asking for plastic to leak down the threads of the nozzle. You need to screw the heat break a little further into the heat block so when t
by
MMcLure
-
Printing
It's not extrusion but oozing. You might try setting ADVANCED_PAUSE_RESUME_PRIME to a small negative number (around what you'd usually use for a retract) and see if that helps.
by
MMcLure
-
Firmware - Marlin
Pretty much all boards supported by Marlin already have FAN_PIN configured appropriately. You just need to hook up whatever you need to the appropriate fan port on the motherboard and use M106 to control it. On the SKR 1.3 the defined fan pin is P2_03 (src/pins/lpc1768/pins_BTT_SKR_common.h line 92).
by
MMcLure
-
Firmware - Marlin
M106 is defined as enabling the fan. So whatever pin is defined as FAN_PIN in Marlin will be controlled by M106. By default on a RAMPS FAN_PIN is already defined as D9 (src/pins/ramps/pins_RAMPS.h) so there's nothing you need to do if that's the board you're using.
by
MMcLure
-
Firmware - Marlin
There is no way to do this in Marlin without recompiling it.
by
MMcLure
-
General
You can't use the Arduino pins numbering (19) with Re-ARM - you need to use the 'P1_28' syntax (note the 'P' - you can't just say '1_28').
On a Re-ARM you should disable ENDSTOPPULLUPS since the Re-ARM has hardwired pull ups on the board so you don't also need to enable the CPU pull ups.
May I ask why you're moving the BLTouch to the Z max pin? Most people connect it to the Z min (Z_MIN_PROBE_U
by
MMcLure
-
Firmware - Marlin
How are you homing Z? Are you using a probe or an end stop? If you're using a probe the NOZZLE_TO_PROBE offset is subtracted from 0 to determine the location of Z after homing. Use M851 to see what your probe offsets are and make sure that the Z probe is correct (in the majority of cases it should be negative).
You should also look at MANUAL_Z_HOME_POS.
You might want to post your complete config
by
MMcLure
-
General
I would recommend cutting the pins and using a hydra cable. That's what I do on my Re-ARM/RAMPS combination. However, don't use pins 20 and 21 - that was a mistake on my part since those pins are not change interrupt capable - later on in that thread it's explained further. I'd recommend pins 63 and 64 on the AUX2 connector. Any of the following pins can be used:
10, 11, 12, 13, 14, 15, 50, 51,
by
MMcLure
-
RAMPS Electronics
This may be possible if you have the RAMPS connected to an Arduino Mega, however this will _not_ work with a Re-ARM since several of the pins used by BigTreeTech to connect UART are not available with Re-ARM.
Unfortunately, the FYSETC 2209 drivers have the resistor on the TX pin which is the pin connected to the UART on the RAMPS, and this might interfere with communication. The following pins w
by
MMcLure
-
RAMPS Electronics
OK - the most probable issue is a problem with the driver enable signal. You don't happen to have SOFTWARE_DRIVER_ENABLE turned on? That is known to cause problems and should only be turned on if the hardware does not have a physical enable pin for the drivers, which is definitely not the case for an SKR 1.4.
by
MMcLure
-
Firmware - Marlin
You say "hotends heat up and are under PID control" but are the hotends hot when you attempt to move the extruders? By default Marlin will not move the extruder motor (PREVENT_COLD_EXTRUSION) unless the extruder temperature is above a certain threshold (EXTRUDE_MINTEMP, 170C by default).
by
MMcLure
-
Firmware - Marlin
Hmmm... I just looked at the Ender 5 Pro configurations at https://github.com/MarlinFirmware/Configurations/tree/release-2.0.7.2/config/examples/Creality/Ender-5%20Pro and https://github.com/MarlinFirmware/Configurations/tree/bugfix-2.0.x/config/examples/Creality/Ender-5%20Pro and they appear to correctly home to MAX.
by
MMcLure
-
Firmware - Marlin
By definition, Xmin/Ymin are bottom left of the print area. For a printer that homes to top right, there are two possible ways to define things:
Define the home position as Xmin/Ymin - this will result in the effective print area being rotated 180 degrees, so you need to look at the printer from the back to match the view in the slicer. Define the home position as Xmax/Ymax - this will result in
by
MMcLure
-
Firmware - Marlin
It's possible that Creality has changed the design of the Ender 5 - they have been known to constantly change things without notice. I know that many people on the Marlin discord would mention that the nozzle could _not_ physically reach the whole bed on their Ender 5s which is why the bed size was reduced for the example configurations. I am in the process of writing a document on how to set up
by
MMcLure
-
Firmware - Marlin
The reason the bed is defined as 220x220 is because the nozzle cannot actually reach the full area of the bed. In this case it's better to define a "virtual bed" that is smaller than the physical bed to ensure that you don't run into the limits by mistake.
by
MMcLure
-
Firmware - Marlin
There are three locations where configuration information is stored in Marlin. First, there is the firmware itself which is configured using Configuration.h and Configuration_adv.h, next is the EEPROM, and finally is RAM when Marlin is running.
When Marlin boots up, it will copy the configuration from EEPROM to RAM. When you use any of the gcodes that change configuration settings, these will ap
by
MMcLure
-
Firmware - Marlin
Please, do yourself a favor and stop trying to use Arduino. Switch to VSCode + PlatformIO: Install Marlin with PlatformIO - it is much more reliable, faster to compile, and produces better compiled code.
by
MMcLure
-
Firmware - Marlin
Have you tried connecting the bed heater sensor to the hot end sensor input and see if that also reads 20C? Perhaps they are not the same sensor type.
by
MMcLure
-
Firmware - Marlin
The VET6 has more flash and the same amount of RAM as the RCT6 which is already supported by Marlin 2.0, so there should be no reason it couldn't be ported to that chip.
by
MMcLure
-
Firmware - Marlin
Page 1 of 9
Pages: 12345