Unfortunately, sensorless homing is not yet ready for prime time. There are too many variables that can affect the behavior.by MMcLure - Firmware - Marlin
Edit the platformio.ini file and change the line near the beginning that says "default_envs" so it reads like: default_envs = melziby MMcLure - Firmware - Marlin
This is because of an Arduino limitation on the maximum command line length for linking. There are several options you cad take to try to fix this: Move your Marlin folder to the root of your hard drive - i.e. C:\Marlin (or even C:\M) Delete the HAL folders (under src/HAL) for any boards you aren't using Switch to PlatformIO for compiling Marlin (as described in Installing Marlin (PlatformIO) Thby MMcLure - Firmware - Marlin
QuoteDark Alchemist Is the ~7hz we get on the avr boards the same as we get on the 100+ mhz ARM boards? The heaters use the same ~7Hz. The other PWM pins (servos, RGB and fans) default to 50Hz on LPC1768 boards.by MMcLure - Firmware - Marlin
QuoteDark Alchemistedit: Oh, the red led never flickers it is full on or full off and it doesn't flicker even on a smart phone camera. That's what you'll see if the bed is set to bang-bang (i.e. PIDTEMPBED is not enabled). If you enable PIDTEMPBED the light will be solid until the temperature is within a few degrees of the set point and then start flickering.by MMcLure - General
QuoteIt's been years since I used Marlin, but IRIC there are variables somewhere that set the PWM frequencies for the bed and hot-end independently, and they default to hundreds or thousands of Hz. At least in recent Marlin this isn't true - the default bed and hot end PWM frequency is around 7Hz, unless you change the setting of SOFT_PWM_SCALE.by MMcLure - General
By default UNIX based operating systems (like MacOS) consider files and directories that start with a period to be "hidden" and won't show them. I believe there is a Finder setting that will make them show up, otherwise you can use the Goto Directory menu option and explicitly type in .pio to go into the .pio directory.by MMcLure - Firmware - Marlin
When using TMC2209 drivers you can run up to 4 of them with a single UART pin.by MMcLure - Firmware - Marlin
Quotexdarko I've read the there's a downside in using software serial which is you cannot use multiple pins in the same instant. Does this affect negatively on the performance of 3D printing? As long as you don't enable MONITOR_DRIVER_STATUS (current Marlin 2.0.x disallows setting MONITOR_DRIVER_STATUS on AVR processors) there should be no effect on the performance. The UART is only used to confby MMcLure - Controllers
Another thing that can help is to switch to VSCode+PlatformIO instead of Arduino. PlatformIO will compile the libraries into archive files (.a) instead of trying to link all of the constituent files on one long command line, and also handles dependencies (such as ensuring that the right library version is used) much better that Arduino.by MMcLure - Firmware - Marlin
QuoteRcTomcat Thank you In Marlin 2 it is called PROBE_PT_1_X I will try it today. Yup - my mistake when typing it out.by MMcLure - Firmware - Marlin
The Lite6 has PTFE all the way down to the nozzle, so the PTFE is in the hot part of the hot end and will limit your printing temperature to around 240C at most. The V6 (if using 1.75mm filament) requires a shorter piece of PTFE that stops while it is still in the "cold" part of the hot end - there is no PTFE in the part of the nozzle that gets hot so the temperature is not limited by the PTFE.by MMcLure - Printing
Look for PROBE_POINT_1_X, PROBE_POINT_1_Y, PROBE_POINT_2_X, etc. in Configuration_adv.h.by MMcLure - Firmware - Marlin
Quotebentech4u HI i have configured marlin 2.0-bugfix on the same board and it got fixed. now G28 is working as expected, but G29 is probing out of bed. i have enabled AUTO_BED_LEVELING_UBL Did you reinitialize your EEPROM with M502 after uploading your new firmware? The NOZZLE_TO_PROBE_OFFSET is now stored in EEPROM and needs to be initialized correctly. Use M851 to ensure that the stored vby MMcLure - Firmware - Marlin
If you already have a RAMPS and the drivers, you might want to take a look at the Re-ARM - it's an almost plug and play 32 bit replacement for the Arduino Mega. There are some differences with respect to display connectors (it supports the RepRapDiscount Full Graphics display but you need a slightly modified cable) and the fact that it's 3.3V instead of 5V so if you have any peripherals that runby MMcLure - Firmware - Marlin
If you do power your board from USB, you can't just power up the power supply and have the drivers work correctly. You have to ensure that Marlin knows that the power supply has come online so it can reinitialize the drivers. The normal way to do this is by using the PS_ON pin and enabling PSU_CONTROL in the Marlin configuration. Then you can turn on the power supply with M80 and Marlin will reinby MMcLure - Firmware - Marlin
There are a couple of issues with Linear Advance and TMC drivers. The first is that if Linear Advance is enabled, it is possible that step pulses may be too short for the drivers. Recent versions of Marlin 2.0.x fix this problem, but if you're running an older release you need to use either the SQUARE_WAVE_STEPPING configuration option or set MINIMUM_STEPPER_PULSE explicitly to 1 or higher. If yoby MMcLure - Firmware - Marlin
QuoteRhartl Another maybe unrelated problem is that the EEPROM setting in Marlin is V56 and the EEPROM I have on the printer is V55. Do you know how to fix that? From terminal, execute: M502 M500 M501 The "M502" will reset the EEPROM values to the defaults defined in your configuration files. The "M500" will store the new values to EEPROM. The "M501" will read the values back. You should getby MMcLure - Firmware - Marlin
First of all, resetting your EEPROM (M502) should not overwrite your mesh as long as you have saved it with ''G29 S". You should be able to restore it by using "G29 L" and then activate it with "G29 A1". In case you are running into a bug where the mesh is being overwritten, or you need to replace your board with a new one, you can use "G29 S-1" to print out gcode commands that will reset the meby MMcLure - Firmware - Marlin
Make sure that the tabs on the RAMPS mosfets are not touching - that can cause all sorts of problems.by MMcLure - Firmware - Marlin
If you have enabled MONITOR_DRIVER_STATUS try disabling it.by MMcLure - Firmware - Marlin
Also, ENDSTOP_INTERRUPTS_FEATURE is really not needed at all. By default Marlin only checks physical endstops while homing, and homing moves are blocking, so polling the endstops does not affect performance. The only case where ENDSTOP_INTERRUPTS_FEATURE makes sense is if you also set ENDSTOPS_ALWAYS_ON_DEFAULT.by MMcLure - Firmware - Marlin
Try executing "M211 S0" to disable software endstops.by MMcLure - Firmware - Marlin
The M851 setting determines what Marlin will consider as the value for Z when your z-probe is triggered. So if you run "M851 Z0" and "G28" then it will home X and Y, and then move Z until the sensor triggers, and it will consider that to be Z=0. Assuming you're using your Z probe for homing: Use "M851 Z0" to reset the Z offset.Home the printer with "G28". Your LCD should show Z=0 at this point.Eby MMcLure - Printing
If you're using UBL on Marlin 2.0, the G29 K gcode does what you're looking for - it takes the current mesh and compares it to a different stored mesh. So assuming you want to compare the mesh in slot 0 to the mesh in slot 1 and save it in slot 2, you'd do: G29 L0 ; load mesh 0 G29 K1 ; compare to mesh 1 G29 S2 ; save to slot 2by MMcLure - Firmware - Marlin
It sounds like your Z_PROBE_OFFSET_FROM_EXTRUDER is wrong. Are you using the Z probe for homing (with Z_SAFE_HOMING)? If so: Use "M851 Z0" to reset the Z offset. Home the printer. Your LCD should show Z=0 at this point. Execute "M121" to disable hardware endstops, and "M211 S0" to disable software endstops. Jog the Z axis down with your LCD until the nozzle just grabs a piece of paper. The LCDby MMcLure - Firmware - Marlin
If you want to use sensorless homing on Z and run the nozzle into the bed then yes, the X and Y probe offsets would be 0. However, I would highly discourage you from trying to use sensorless homing on Z. Because the Z axis usually uses leadscrews and has a lot of torque, getting sensorless homing to work reliably on Z is very difficult - you need to set a very low threshold which introduces noisby MMcLure - General
As I mentioned on Discord, what you're seeing is correct for an Anet A8. The "home" position is off the bed, but if you move to X=0, Y=0 you should see that the nozzle ends up at the front-left corner of the bed. Slicers expect 0,0 to be the left-front corner of the bed so this is fine.by MMcLure - Firmware - Marlin
Uh... I'm not understanding the problem. When you do G1 Z0 it should move the nozzle to the 0 position, i.e. just barely touching the bed. That said, you really want your BLTouch trigger point to be when the nozzle is about 2mm above true 0 to ensure that when the pin is retracted it won't hit the bed when the nozzle goes to true 0. Note that the actual position of the BLTouch body is irrelevanby MMcLure - Firmware - Marlin
If I understand you correctly, the light on the sensor doesn't turn on unless you're touching the sensor? That light has nothing to do with the controller board or any connections, so it sounds like the sensor is bad. My guess is that the sensor ground wire is bad and when you touch the sensor you're making enough of a ground connection to trigger it.by MMcLure - General