Show all posts by user
Printing issues ...
Page 1 of 237
Pages: 12345
Results 1 — 30 of 7109
In marlin it sets the following as as default contrast
#define _LCD_CONTRAST_INIT 140
But this can be update with M250
Is this what your changing?
by
Dust
-
Firmware - Marlin
It took me all of a minute of googling to find
#define SHORT_BUILD_VERSION "-bugfix2.0.x-MKS-2.1.3"
from Version.h of
by
Dust
-
General
"and the correct setting is NO (normally opened)." no not really.
normally closed endstops are the standard, as it means that when you break a endstop wire (or unplug it) the endstop is triggered, vs just crashing the machine into the end of travel when the endstop is disconnected
by
Dust
-
General
Marlin developers are all individuals, 'we' only find out what they are working on when they create a PR to request it to be added to Marlin
by
Dust
-
Firmware - Marlin
reprapfirmware uses the SPI port with their own esp wifi code.
by
Dust
-
Firmware - Marlin
no...
Wifi port has
ESP-CS PB12
ESP-MOSI PB15
ESP-MISO PB14
ESP-CLK PB13
There are all directly connected to the MPU SPI2 port io pins
The sdcard on the screen is
#define SD_SS_PIN PA4
#define SD_SCK_PIN PA5
#define SD_MISO_PIN PA6
#define SD_MOSI_PIN PA7
This is directly connected to the MPU SPI1 port io pins
by
Dust
-
Firmware - Marlin
Marlin settings basics 101:
Settings that can be changed via gcode or LCD are saved in EEPROM
The EEPROM setting are independent of firmware settings.
Updating firmware will not update the values stored in EEPROM (1)(2)(3)
NOZZLE_TO_PROBE_OFFSET is one of these variables.
(1) On the first time you update with new firmware, if the EEPROM version does not match or the saved checksum is invalid,
by
Dust
-
Firmware - Marlin
You do not define hardware uart pins in the pins file or the configuration files
You don't need to define them at all, this is done for you as parts of the build environment, and yes they should be named like they are.
-DPIN_SERIAL3_RX=PD_9 -DPIN_SERIAL3_TX=PD_8
yes you need #define SERIAL_PORT_2 3
by
Dust
-
Firmware - Marlin
The most common reason for serial ports not working is your trying to use buggy 4 year old code on the BTT github
This old broken code sets the cpu clock frequency wrong and messes up most timing, especially baud rates (except for port -1 which actually ignores baudrates)
by
Dust
-
Firmware - Marlin
Re serial port
You look at the pins diagram
There is also a copy in Marlin/src/pins/stm32f4/pins_BTT_SKR_V2_0_common.h
/**
* -------
* GND | 9 | | 8 | 3.3V
* (ESP-CS) PB12 | 10 | | 7 | PB15 (ESP-MOSI)
* 3.3V | 11 | | 6 | PB14 (ESP-MISO)
* (ESP-IO0) PB10 | 12 | | 5 | PB13 (ESP-CLK)
* (ESP-IO4) PB11 | 13 |
by
Dust
-
Firmware - Marlin
This sounds like it is just like a BIQU MicroProbe with a PROBE_ENABLE_DISABLE pin to deploy/retract
by
Dust
-
Firmware - Marlin
Communications with this board is two part
a) the board has a FT232RL serial to USB chip.
Your operating system needs drivers to see this and talk to it.
Also due to ftdigate (google it) , this converter chip may be bricked (its old enough to have been caught by this)
b) the MPU has to be running some code to respond to serial.
This includes the baud rate
Most common baudrate is 115200 or
by
Dust
-
General
You need to make a few small code changes to have a second uart on esp32
In standard diff format.
Make these changes
diff --git a/Marlin/src/HAL/ESP32/FlushableHardwareSerial.cpp b/Marlin/src/HAL/ESP32/FlushableHardwareSerial.cpp
index 145662215a..29804d34e9 100644
--- a/Marlin/src/HAL/ESP32/FlushableHardwareSerial.cpp
+++ b/Marlin/src/HAL/ESP32/FlushableHardwareSerial.cpp
@@ -25,5 +25,6 @@
by
Dust
-
Firmware - Marlin
esp32 does not have sufficient IO pins for most 3d printers, so an IO expander chip is used
There are two different types of io expanders currently implemented
One is via serial, pins >= 100 on this type of IO expander are on the expander.
The other is via i2s when pinis with bit 8 is set ie >= 128 are on the expander.
See Marlin/src/HAL/ESP32/fastio.h for more details.
by
Dust
-
Firmware - Marlin
The linked URL is the default Configuration, its only use was to show you where the two lines where
QuoteDust
check these are correct
#define X_MIN_POS 0
#define Y_MIN_POS 0
These are your home positions
Ie When you home X, the X endstop trigger point sets where X0 is for the hotend , if the hotend is actually left of the bed X_MIN_POS should be a negative number, so moving the positive of
by
Dust
-
Firmware - Marlin
It is in the Configuration.h file on Lines 1731 and 1732
see
by
Dust
-
Firmware - Marlin
Please try a little harder to help yourself.
Searching text files for a string is a very basic computer skill.
by
Dust
-
Firmware - Marlin
check these are correct
#define X_MIN_POS 0
#define Y_MIN_POS 0
These are your home positions
Ie When you home X, the X endstop trigger point sets where X0 is for the hotend , if the hotend is actually left of the bed X_MIN_POS should be a negative number, so moving the positive of that value will nove to X0
When you home Y, the Y endstop position point sets where Y0 is for the hotend. if the
by
Dust
-
Firmware - Marlin
Long discussion about it on github
MP_SCARA Issue is basically fixed but user is not using a mp_scara but a scara arm with individual endstops and other changes
by
Dust
-
Firmware - Marlin
you have Z_PROBE_SERVO_NR 0 this is fine.
are you sure its a ramps 1.3 ?
as the only difference from a ramps 1.3 to the ramps 1.4 (firmware wise) is the servo0 pin changed
#ifdef IS_RAMPS_13
#define SERVO0_PIN 7
#else
#define SERVO0_PIN 11
#endif
by
Dust
-
Firmware - Marlin
No one has done this yet,
I gave it a quick look, but it looks like stock platformio doesn't recognize the board yet, a known issue
This would be a lot of work.
Every new type of board needs a HAL level (since it is a STM32H747XI, may be able to use stm32 HAL)
eg there is AVR and DUE a GIGA would need added
by
Dust
-
Firmware - Marlin
The 5A power in provides power to:
fans
hotends
vin (atmega2560 power supply)
and stepper motors
If you remove D1 then the mega is safe from getting to much voltage.
but what of the fans or the hotend?
You don't have to replace the 11A fuse if your not putting any power into that circuit.
You may want to take look at
by
Dust
-
RAMPS Electronics
There should be no need to use the reset button.
The CH340 DTR line is connected to avr reset, avrdude knows to assert this line to reset the controller to start upload.
This can bee seen on the last page of the circuit diagram
You either have a hardware fault or the boot loader has been damaged,
Install stock atmega2560 boot loader, using a avrisp. see as one example on how to do this.
by
Dust
-
Firmware - mainstream and related support
"But I do use a micro-sd card on the printer. Will this still work?"
Yes it works fine, you just tried to tell marlin you have the deluxe hyper speed sdcard when you only have the standard slower one.
by
Dust
-
Firmware - Marlin
the MKS_TS35_V2_0 screen is driven by marlin firmware, there are 3 user interface options
* TFT_CLASSIC_UI - Emulated DOGM - 128x64 Upscaled
* TFT_COLOR_UI - Marlin Default Menus, Touch Friendly, using full TFT capabilities
* TFT_LVGL_UI - A Modern UI using LVGL
only TFT_LVGL_UI uses has assets to be copied to the sdcard
You selected TFT_COLOR_UI in the provided Configuration.h
by
Dust
-
Firmware - Marlin
You have added #define ONBOARD_SDIO to the Configuration.h
The BOARD_MKS_ROBIN_NANO_V3_1 does not have the SDIO feature.
This is the robin onboard sdcard circuit diagram from
And this is from a btt octopus that does have SDIO from
Note how the btt octopus has Data0,Data1,Data2 and Data3 This allows for 4 bit data transfers ie SDIO while the Robin only has a single data bit, so it is on
by
Dust
-
Firmware - Marlin
You have 2 things using P2_04
by default FAN1_PIN is using P2_04 nd default chamber fan is going to use this fan
but you have set #define HEATER_CHAMBER_PIN P2_04 /// pin for the chamber heater
by
Dust
-
General
you are pressing the encoder arnt you? It goes left/right and it clicks down
by
Dust
-
Firmware - Marlin
Page 1 of 237
Pages: 12345