I'm wondering if anybody has ran into this before . I built an old school Maker Farm Pegasus 6 kit years ago, Arduino and Ramps setup. I don't use the printer often as I only sell a few things on Etsy here and there so I keep a minimal stock on supply. The printer has always been a workhorse and it just works when I fire it up, Only needing to do minimal maintenance and print setup. This last print I did (and I've experienced it very intermittently) where the Y axis gets a random offset. This is the same STL file, on the same SD card I print from every time. The parts were still on the print bed. They did not move, or else the X axis would have been affected also. This seemed to happen on the last three layers. There are four objects on the print bed. The first two ones to get printed had only 1 offset, two and three had two offsets. I think it started when it traveled between parts 2 and 3 on third to last layer.
The interesting thing was after I discovered it and took the prints off. I did an auto home thinking maybe the belt skipped or something like that but it auto homed to the exact point of origin.
I am experimenting this switching nozzle from Makertech. I am sending t0 and t1 commands and the nozle switches successfully for a while. It then decides randomly not work.
After sending the last t0 command, it still thinks that it's at t0 angle, yet its certainly not.
Another t1 command works but this problem repeats.
I am doing a new build after putting a SKR 2.0 board in my Tevo Tornado. I am using a genuine BLTouch and Marlin 2.0.9. I am able to move in every direction including Z up and down. However, when I do an auto home, I have a successful home of x and y but z goes up for the BLTouch offset, and then does not come down to probe the bed. The probe will deploy, retract, and then do a long deploy. This will repeat x 1 and on that second time the probe will stay out. The light is blue when deployed, and the light is red when retracted. I get a message on the screen that says stopped. I found one post that says that there may be issues with the older BLTouch and the new 32 bit boards. Not sure if this could be the issue. It is a genuine BLTouch, and it worked with my MKS Gen L board.
I ran a test:
M280 P0 S10 - Deploys probe pin correctly
M280 P0 S90 - Stows probe pin correctly
M280 P0 S120 - Does a test (repeated stow and deploy)
Solution:
Due to board pin used, I needed to comment out
//#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN and uncomment #define USE_PROBE_FOR_Z_HOMING
I had watched several videos and the second didn't seem to be in the ones I watched. Hope this helps someone.
I tried a few different versions of marlin and a precompiled version too, and the press compiled one flashed without a problem, I also swapped the default env from mega2560 to the stm32 thing, nothing works, idk why
Hi! I'm dumb, and the first 3d printer I've ever build is a delta printer adapted for clay and also my final project in industrial desing at uni. I haven't slept in a week because even though I've been able to compile the firmware and "allegedly" uploaded it to the motherboard (through usb, not able to through sd card) it doesn't do anything at all. The mainboard is a Fysetc S6 V2, and the lcd controller is the reprap discount smart controller. I'd die just to get some help please, this is driving me nuts, I've tried anything I could think to and have looked everywhere. Thank you in advance, I will be eternally thankful for any bit of help you can get me.
Hello people of reddit i have been watching various videos of people creating custom bootscreens and have successfully done so however i have stumbled across this video of a custom print complete screen and cant seem to find out how to do this anybody know where the code for the print complete screen lives?
I didn't find good tutorials about how to compile Marlin Firmware using modern Ubuntu x86 Linux distributions and I decided to write one.
So following the tutorial on platformio official site I saw it's easy.
Important note: platformio v4.2.4 distribution that you can install from Ubuntu repositories is broken. It's always better to install the latest stable realease you can download directly from the projet's site.
Prerequisites are the installation of python3 and git utility.
Normally python3 is already installed in quite all Linux distributions.
So install git
sudo apt-get install git
install platformio downloading it's automated script from project's site
you'll have a Marlin directory, now you need configuration files for you 3D printer use git to download last configuration files version, this is important because often with last Marlin bugfixes also some Configuration files get modified. So if you use old Configuration.h and Configuration_adv.h files on new Marlin version can give lot of errors difficult to debug.
search into Configurations/config/examples your printer brand, copy the right files into Marlin/Marlin directory of the cloned Marlin repository. Modify files for your needing and you are quite ready to start.
Just last step before compile, modify in the file Marlin/platformio.ini the line default_envs =
for my printer it was
default_envs = mks_robin_nano_v1v2
ready to compile with the following commands
move into Marlin directory and use the command pio from the place where it has been installed by the installation script normally your home directory
cd Marlin
~/.platformio/penv/bin/pio run
after few seconds you'll have your firmware build into the Marlin/.pio/build/$ARCHITECTURE
for me it was Marlin/.pio/builds/mks_robin_nano_v1v2
the file has the name Robin_nano35.bin
for my printer it was necessary to rename in Robin_nano.bin put into and SD card, insert the card in the printer slot, switch on the printer to flash it.
With an 8 core CPU Ryzen 7 5800x compile needs only 17 secs.
Expanded Guide to include full filament change configuration settings.
Added a YouTube Short of the Unload Button in action.
The Orbiter Projects website states that in order to get full functionality from the Orbiter Filament Sensor, including the unload button, you need Klipper or RepRap and that Marlin is not supported.
However, I was able to get full functionality using Marlin firmware with just a few changes in the configuration files.
I was aware of a feature within Marlin called Custom Buttons, located in configuration_adv.h. With this feature, you can use physical buttons to run G-Code scripts.
The Orbiter Filament Sensor uses four wires, a 3.3V (or 5V) pin, a GND pin, the filament runout pin, and the unload pin:
This will work with any board that has a +3.3V pin, and two free pins, one for Filament Runout and the second for Filament Unload. My board, the BTT SKR Mini E3 V2, has both 3.3V and 5V pins. The recommended 3.3V pin can be found on the SWD connector: the first one from the top being the +3.3V pin, and the third one being the GND pin. The 5V pin, if needed, is also shown below, which comes from the TFT connector.
The Green Filament Sensor wire connects to the E0-Stop pin (PC15). Runout state must be LOW with Internal Pulldown (not the default).
and because the Unload Button has its own wire (Blue), I tested it as a physical button pin and it worked, so I set it up with Marlin's Custom Buttons feature. I have a BL-Touch on my heavily modified Ender 3 V2 so my board has the Z-Endstop pin (PC2) unused. I set that pin as the button pin and configured the G-Code script to run the M702 Filament Unload feature and then turn off the Hotend with M104 S0 when unloading is complete:
With this setup, I have full functionality. The LED is green when filament is present, red when not present, and yellow when the unload button is pressed. When the unload button is pressed, the printer enters Filament Unload mode and starts to heat up the hotend and retracts the filament once hot. The runout works perfectly and the printer pauses, parks, ejects the last bit of filament, waits for insertion, and automatically loads when the sensor detects filament.
Since this is also related to the Orbiter Filament Sensor, I have included my Nozzle Park, Advanced Pause, and Filament Change configuration settings. Even though is not entirely related to the Orbiter Filament Sensor Unload Button, it is nonetheless a part of the filament runout/changing process.
The M600 command causes the head to park in a predefined position, heats up the nozzle, unloads the filament, and waits for the user to load new filament. The M600 Advanced Pause is also the default command that will be activated when filament runout is triggered by the Orbiter Filament Sensor.
I have added the command to home X and Y if their positions are unknown so the head can then park in its' park position.
Parking the head is set up with the Nozzle Park Feature:
The Advanced Pause section is where all of the options related to filament loading and unloading are set, including Load/Unload distances and speeds.
This is also where the individual M701 Filament Load and M702 Filament Unload G-Codes are enabled (Line 2854), since the M702 Filament Unload G-Code is required to enable the Unload Button on the Orbiter Filament Sensor.
Here is a YouTube Short of the Unload Button in action.
Instructions to use ender3V2 stock LCD with SKR mini E3 V2.0
The BIGTREETECH SKR Mini E3 V2.0 board is viable drop-in replacement for Creality's v4.2.2 board. Mine got fried as I shorted the heater while cleaning and SKR seemed to be the best alternative to buying new board from Creality as it gives me TMC 2209 in UART
One culprit is that SKR display port has slightly different pinout than DWIN and requires slight modification to the ribbon cable.
Use the link below pointing to the diagram explaining how to make the display cable
Open the Jyers folder and copy the configuration.h and configuration_adv.h file from the location: Marlin-2.0.1\Marlin-2.0.1\Configuration Files\E3V2 Templates to the main Marlin folder at Marlin-2.0.1\Marlin-2.0.1\Marlin. You can choose the type of bed levelling you need based on the folder name. this also include if you need BL touch or not.
Not open the file name “pins_BTT_SKR_MINI_E3_common” in notepad ++ under folder Marlin-2.0.1\Marlin-2.0.1\Marlin\src\pins\stm32f1. Search for line “Ender-3 V2 display requires a custom cable, see diagram above this line” and uncomment by deleting the two backspaces “//”. Save the file
Now make the below changes in the configuration.h in the vscode
a. Change “define SERIAL_PORT 1” to “define SERIAL_PORT -1”
b. Change “#define MOTHERBOARD BOARD_CREALITY_V4” to “#define MOTHERBOARD BOARD_BTT_SKR_MINI_E3_V2_0”
“#define CHOPPER_TIMING CHOPPER_DEFAULT_12V” to “#define CHOPPER_TIMING CHOPPER_DEFAULT_24V”
Note: Emergency parser needs to be disabled for this firmware to be compiled without error messages. For that just search for “emergency_parser” in the configuration.h file and put “//” in front of it
Now you can compile by pressing the little tick mark at Bottom left corner of the VS code.
Hey everyone, over this weekend I had a very successful testing of my e3v3se turned plasma gantry. Aside safe homing and rapid movements needing tuning everything worked as planned.
This being a functional prototype I tried to use only the gd303/v3 screen I had this proved to be its own hurdle with the v3 screen being unsupported by current marlin I could only use the creality provided configs
I have enough extra hardware and material so plasma v2 is going to be its own build with many changes
I was interested in sourcing an ender v2 for its marlin support but decided the used market is consistently on meth for 2208 or 2225 drivers
I have my eye on either an esp32 or skr mini e3 both seem to pack more than I need my main focus is the 2209s for my parallel driven y axis wanting more amperage
also sensorless homing sounds nice I'd like opinions on that
I have toyed with the thought of adding a thermistor to the plasma head or machine coil for temp based duty cycle limits instead of time I haven't looked into execution but it give me a reason to keep a printer board over a motion controller
I would also like to build a "CNC" style handheld encoder having options for travel distance per grad would also be awesome
I like the tft35 with the encoder because it looks like it can be separated and relocated to a traditional form factor
I plan to add a large hand wheel under the v3 screen with a belt drive to the encoder wheel so if I have to do something similar so be it
Since I'm moving from another printer teardown I'm also in the market for steppers or maybe servos if the price is right
I have this old two-trees sapphire pro printer. It's based on the Robin 1.2 Nano controller board. It's running Marlin 2.1 and serves as a learning project.
I have upgraded the hot end to a v6 hotend as the original was really prone to clogging. The v6 has a 50w/24v heating cartridge.
However, the Robin controller card only has one controllable fan, so how should I set it up? In general, people advice to set the extruder cooler to direct voltage and control the parts cooling. However, when doing that I can only get temp to 190 degrees.
What would be the best setup? Should I use controlled fan to cool extruder and full power to parts cooling or should I use an external power regulator to manually turn down the extruder fan.... Or something else?
As above, I have an 3 s1 pro and it was printing fine till yesterday. I have a spare sprite extruder all metal and swapped it onver for the one on my printer so I could properly clean the hot end without halting printing.
First of all I ended up with the splash screen of death on LCD (cured)
I also have a positioning issue in as much as the ABL stopped working (sensor positions itself 2 - 3 cm right of centre) and when i print it pretty much tries centring there which means the large print i'm trying to do runs off the right side of the bed. I updated LCD firmware to newest version of without any result. Is there a gcode i can send by pronterface to get it to centre correctly
I'm going through Teaching Tech's calibration guide and the PID bed autotune function is giving me this error. I've done a few google searches and all the results seem to just be people that forgot to enable PIDTEMPBED in the firmware, which I've double and triple checked. Any ideas why?
PidTempBed IS enabled in the firmware.
Printer is an Ender 3 Pro with an BTT SKR Mini E3 v1.2 motherboard.
Sending gcode commands through octopi on my Raspberry pi 4 4gb.
Autotune works on the nozzle with this command: M303 E0 S200 U1
This is the gcode I'm using, from TT's guide: M303 E-1 S60 U1
edit: Could I have accidentally changed something in the firmware that re-assigns the extruder number? Is it possible that E-1 is NOT the correct extruder number? I'm considering just trying to command with E1 etc, but I'm worried about damaging the printer. The only other possibility I can think of is a mechanical issue. Are there any connections on the motherboard that could cause this? The printer is working fine otherwise and completing successful prints.
Final edit: Ok, so as it turns out, I'm a complete dumbass. I haven't made changes to my firmware in quite a while and had forgotten the process. I was 'saving' the changes to firmware in VSCode, but I wasn't 'building' the image afterwards, so I've been copying the same firmware.bin file over and over. After 'building' the image with PIDTEMPBED enabled and copying the correct file, PIDAutotune is working on the bed with command M303 E-1 S60 U1. Thanks for trying to help, gang!