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
All I know of the screen is it is a serial device (as that is the connector it plugs into) Screens like this come in two main types 1) Screens that talk gcode and interpret the results. Basically they are a small computers with touch screens. Marlin only needs the serial port its connected to enabled. 2) DWIN/DGUS,TJC etc these talk a custom protocol, The user interface and Marlin code areby Dust - Firmware - Marlin
I've created a pull request to add this motherboard into main Marlin You can see all changed files hereby Dust - Firmware - Marlin
Oh look what I just found Says its for the pro, but has the same motherboard Pins file Build env # # AtomStack FB5 V2.0 (STM32F103RCT6 ARM Cortex-M3) # extends = common_STM32F103RC_variant ; board = genericSTM32F103RC ; board_build.variant = MARLIN_F103Rx board_build.encrypt_mks = Robin_e3.bin board_build.offset = 0x5000 boby Dust - Firmware - Marlin
Just because it looks similar does not mean they are 1.1 clones. for eg the usb, you saying it does not use a Ch340, which means instead of using two serial pins is is using USB CDC which uses different pins Enabling USB CDC also requires changes to the build environment to tell the compiler to include a USB stack. From FB post" "I had an Atomstack Cambrian Pro, that was great for a coupleby Dust - Firmware - Marlin
In theory you can use DFU mode But note in that mode you can easily brick the board or over write the boot loader This need access to the the boot and reset pinsby Dust - Controllers
provided config has #define DEFAULT_AXIS_STEPS_PER_UNIT { 80, 80, 400, 500 } but correct values are #define DEFAULT_AXIS_STEPS_PER_UNIT { 80, 80, 400, 100 } According to what I can find on the internet Note this value is stored in eeprom so updating it in config will not take effect until eerprom is also resetby Dust - Firmware - Marlin
you can extract a binary, but you cannot make source for that binary that like trying to get the ingredients list from a cake.by Dust - Firmware - Marlin
also that LED_PIN I found in a klipper config, I don't know if there is actually a led on the board or its something they added for testing. But you can try it add the following to your pins file #define LED_PIN PC14 If its there marlin will blink it to indicate code is running (as long as PINS_DEBUGGING is disabled in Configuration_adv.h)by Dust - Firmware - Marlin
regarding e check if the stepper is energized. When the enable pin is set power is applied to the stepper motor and you can't rotate it by hand, This is what we call energized This might tell us is if the step or the enable pin we need to look at And you are testing with hotend hot? as there are safety interlocks that prevent e moving when the hotend is coldby Dust - Firmware - Marlin
These are all the IO pin on a STM32F103RE as we understand them for the CR-200B board I've marked the things you say work STM32F103RE Pinout for Creality V4.2.5 Board (Marlin) ===================================================== Pin | Confirmed | Function / Usage ------|-------------|--------------------------------------------------- PA0 | YES | HEATER_0_PIN PA1 | YESby Dust - Firmware - Marlin
"1) extruder doesn't work" is it not moving or moving backwards? Regarding Z Part of the issue is a common misconception with printers with beds that move up and down Z- should decease distance from hotend to the bed. Ie the bed must move up Z+ should increase distance from hotend to the bed. Ie the bed must move down With this in mind "3) if i use arrows in octoprint the down arrow movesby Dust - Firmware - Marlin
"M201 X100 Y100 Z2000 ; set accelerations (mm/s^2)" This seems like a lot of acceleration for a Z, perhaps this is causing z to skip stepsby Dust - Firmware - mainstream and related support
For no bootloader operation you have to edit the build environment settings eg board_build.offset = 0x7000 board_upload.offset_address = 0x08007000 Says the firmware should start at 0x08007000, but without a bootloader it will never start since code starts at 0x08000000 So change to board_build.offset = 0x0000 board_upload.offset_address = 0x08000000 But I recommend restoby Dust - Firmware - Marlin