Avete appena stampato un cubo ed è venuto fuori un prisma? Volete un parere sulla qualità della stampa? Chiedete consiglio qui.Remove your stepper drivers and retest. A4988's module, for example, has a built-in pull-up on the sleep pinby Dust - General
Take a look and show your friend. that I just created You can see all the changes here: code diff Note this is completely untested beyond it compiling. It also only add TFT_SPI, it does not add any touch device supportby Dust - Firmware - Marlin
That's like asking, "Why can't I use a sledgehammer to do microelectronics?" You have to fit in with the already existing marlin systems Your code will display a few simple things, and that is it: no Marlin, no user interface, no supporting multiple display types, no supporting multiple hardware interfaces, no supporting a variety of touch controllers, no supporting different screen resolutionby Dust - Firmware - Marlin
re TFT_COLOR_UI, TFT_CLASSIC_UI, TFT_LVGL_UI These are the user interfaces available on the TFT screen. You need to pick one. (note TFT_LVGL_UI requires additional flash chip.) But no one has yet added SPI TFT support to DUE HAL. This is why you get "Sorry! TFT displays are not available for HAL/DUE" And FSMC_TFT is not an easy option, as not all the pins are broken out. DUE TFT SPI suppoby Dust - Firmware - Marlin
Default Configuration.h and Configuration_adv.h that come with Marlin are for a RAMPS. You literally needed to change nothing at all.by Dust - Firmware - Marlin
I don't know why/how you keep breaking things, but here are some things you need to know about the mega2560 and serial (UART) It has 4 hardware UARTS [0-3] these are not mappable; they always use the same IO pins. You can use these IO pins for other things; you just loose UART access The pins are: UART0 -- TX0 = D01 RX0 = D00 (Connected to UART to USB chip on mega, also on AUX1 on RAMPS)by Dust - Firmware - Marlin
Contradictory information: "Uploading to a Due, Windows sees it as a 3D printer." "Compiling and uploading to a Mega2560 V3, WIndows just sees it as a USB device." You cannot run DUE code on a mega2560 (or vice versa). You need to recompile for each processor. The log is showing that the board is not responding The Mega2560 V3 should be seen as a usb serial device. Depending on what it's uby Dust - Firmware - Marlin
The pin names are standard names and Marln knows to set those as input/output as required E.g., X stepper driver pins see Marlin/src/module/stepper/indirection.h // X Stepper #if HAS_X_AXIS #ifndef X_ENABLE_INIT_STATE #define X_ENABLE_INIT_STATE !X_ENABLE_ON #endif #ifndef X_ENABLE_INIT #define X_ENABLE_INIT() SET_OUTPUT(X_ENABLE_PIN) #define X_ENABLE_WRITE(STATE) WRITE(X_ENby Dust - Firmware - Marlin
Delete the directory C:\Users\SBK\.platformio Then restart VSCode. This will reinstall PlatformIO. Windows has either lost the path or removed the executable.by Dust - General
@sbkenn Level shifters have little to do with firmware. They simply translate voltages between devices. Marlin generally doesn't know or care whether a signal passes through a level shifter or not. The relationship is more like: Marlin ↓ HAL (SAM3X / Due) ↓ Pin definitions ↓ MCU GPIO pins ↓ Level shifters, drivers, sensors, etc. Eg Configuration.h you set MOTHERBOARD, this definesby Dust - General
That could be so many things Wrong motherboard definition incorrect kinematics (eg selecting corexy on a standard Cartesian) Corrupted firmware for some reason. Not really enough to go on.by Dust - Prusa i3 and variants
Please join a generic 3d printing Discord such as to ask such questions. We don't do commercial 3D printer appliances here; we make our own.by Dust - General
The simple version is what Mosaic Palette does.by Dust - Developers
The firmware looks fine, but since I dont have acces to this board I cannot confirm it 100% Two possibilities come to mind 1) You're using a charge-only USB cable. 2) The USB port or controller is actually damaged Since you say you tried Linux, does the USB device show up under `lsusb`? If it was a new Linux, did you add your user to the dialout group? `sudo usermod -a -G dialout $USER` soby Dust - Firmware - Marlin
Please do not support bambu, they are truly evil (my personal opinion) Most recent example and a video simplifying it all.by Dust - General
Well the running firmware says "Connecting... start Printer is now online. echo:Marlin 1.1.0-RC5 echo: Last Updated: 2016-04-01 12:00 | Author: Ray B Compiled: Feb 25 2026" So this doesn't match with "i'm working on firmware 2.*.*"by Dust - General
Yes those setting are fine Indicates a hardware fault. potentially a dead ADC pin on the mega In Configuration.h Find "#define MOTHERBOARD BOARD_RAMPS_14_EFB" and add this directly under it #define TEMP_1_PIN 14 // Analog Input #define TEMP_BED_PIN 15 // Analog Input This swaps the bed thermistor plug from to the unused thermistor plug in fby Dust - General
Thermistor type 5 is NTC device Ie it follows this graph So for a high temperature it has a low resistance. So your looking for a short. Unplug the bed thermistor at the motherboard, stick multimeter probes up the two plug pins so you can measure the wires and thermistor resistance. It should read 100K at 25℃by Dust - General
The ramps 1.6 (like the older 1.4) sends 12v to the mega2560 vin pin via diode D1, the mega2560 board does the 5v generation So check for 12v on both sides of D1 (with gnd on a gnd pins), if it has 12v on both sides, its likely an issue on your mega2560. To test mega2560 board unplug the ramps from it and power it via 12v dc jack. as for the screen, what screen does it have? (pictures if yourby Dust - General
Because most commercial options have serious flaws Creality: abusers of open source, just blatantly taking anything they want and ignoring the licensing requirements. Most of their machine are such low quality a DIY version will last much longer. Their Quality control is non existent, they ship it untested and your expected to work with support to get it working. Once a new printer model comes oby Dust - General
Note: Most people use a mosfet on the current mosfet ie you plug a mosfet into the bed connector, the mosfet gets 12v and switchess the 24v so you don't need to make any firmware changes But to answer your question. These defines are used for RAMPS #ifndef MOSFET_A_PIN #define MOSFET_A_PIN 10 #endif #ifndef MOSFET_B_PIN #define MOSFET_B_PINby Dust - RAMPS Electronics
On power up the machine does not know where it is. The only safe move is away from the hotend. "makes the bed move 15 mm toward the nozzle before homing all axes" and if the machine was already closer than 15mm you have just damaged your print bed and or nozzleby Dust - Firmware - Marlin
Marlin even provides example configs for the TAZ4 eg for Marlin bugfix 2.1.x And other releasesby Dust - Firmware - Marlin
Marlin makes every effort to continue to support 8 bit controllers like the RAMBo on Marlin 2.x What will not work is new features like ft motion. These require a 32 bit controllerby Dust - Firmware - Marlin
Sur les cartes RAMPS, il existe deux méthodes pour gérer deux moteurs pas à pas sur l'axe Z : 1) Les cartes RAMPS disposent de deux connecteurs pour les moteurs pas à pas de l'axe Z sur un seul contrôleur. 2) Si le connecteur E1 est libre, branchez le moteur ZA sur le contrôleur de l'axe Z et le moteur ZB sur le connecteur E1. Cela permet un mouvement indépendant de l'axe Z, comme pour l'aligneby Dust - RepRap Groupe d'Utilisateurs Francophone
You cant do anything with the finished firmware.bin file. That is like looking at a cake and wanting to change it from chocolate to banana. You just can't do it, you have to make a new cake. You need the firmware source code and Configuration files. You make the changes you want to the config files or if required the source. You then compile the source into a new firmware. The standard tools aby Dust - Firmware - Marlin
PID is stored in eeprom. It is not over ridden with editing Confguration.h and re uploading you need to either enable EEPROM_INIT_NOW to force eeprom to be set to config file defaults on new firmware upload or use gcodes M502 (reset to config defaults) then M500 (save settings to eeprom)by Dust - Firmware - Marlin
That error I have seen a bit of late, seems platformio is falling over itself. deleting the .pio directory under Marlin and trying again seems to fit it for me.by Dust - Firmware - Marlin
Yes, instead of trying to support the existing user interface they seem to have just used the creality one (after removing the creality boot screen)by Dust - Firmware - Marlin