Show all posts by user
Page 2 of 5
Pages: 12345
Results 31 — 60 of 125
That must be a custom version of Marlin. Keep an eye out for the Marlin 1.1.0 release, coming soon. Meanwhile, we have a new release candidate posted at
by
Thinkyhead
-
Firmware - Marlin
Those MELZIs always were a bit twitchy.
If you're using a RAMPS 1.4 then you have a few firmware options.
Marlin and Repetier Firmware are the most popular.
Personally, I prefer Marlin.
by
Thinkyhead
-
Firmware - Marlin
The main Marlin branch is still written with the assumption that both of your extruders are identical. So all you need to do is set EXTRUDERS to 2, set your EXTRUDER_OFFSET_X and EXTRUDER_OFFSET_Y, and that's all. If you add an extra value to DEFAULT_AXIS_STEPS_PER_UNIT Marlin will just ignore it.
Your slicer should operate independently of the machine. You just have to configure your slicer's s
by
Thinkyhead
-
Firmware - Marlin
QuoteSlackdaddyI can not "go into" the firmware loaded on the Ardunio board (RAMPS) and edit what is already on there, I have to get the original source code, edit that and then "upload" it to the Ardunio (RAMPS)?
That's the key. Download the source code for the current release candidate (1.1.0-RC6) or other versions of Marlin at
by
Thinkyhead
-
Firmware - Marlin
What kind of printer do you have? Many Arduino boards are supported "out of the box" with the Arduino IDE, but not all 3D printer boards necessarily. Gen7, Sanguinololu, and some others may need to have extra hardware support installed.
by
Thinkyhead
-
Firmware - Marlin
The Z2 pins are defined by pins.h in the latest Marlin code by assigning them to the first set of unused E pins. See
Also, for CoreXY I would recommend the most recent Marlin, which later tonight will be 1.1.0-RC6. We only just recently completed Core support for all the normal functions.
If you don't want to wait for the release, you can get the most recent code at
by
Thinkyhead
-
Firmware - mainstream and related support
QuoteGeorgeL16Starting from scratch with the github source.
Excellent. Yeah, some manufacturers use very old versions of Marlin which are usually fine, but not the prettiest source code. It's been getting a lot of cleanup and patches, but believe me there's plenty more to go! We're accelerating the release cycle, so I should be releasing 1.1.0-RC5 later tonight, which includes all the patches fr
by
Thinkyhead
-
Firmware - mainstream and related support
QuoteRoxyI would not remove the heater code. I would just relax it so it doesn't do anything.
Setting TEMP_SENSOR_BED to 0 disables the heated bed. I believe Marlin will complain if you set all TEMP_SENSOR_n settings to 0. It wants at least 1. Roxy, I wonder if it's worth modifying Marlin to allow zero temperature sensors, since I see more users all the time who would like to do paste extrusion
by
Thinkyhead
-
Firmware - Marlin
My best suggestion is to try 1.1.0-RC3 and see if it has already been fixed. Version 1.0.2 still has some lingering issues with homing and bed leveling that have been patched in 1.1.0.
by
Thinkyhead
-
Firmware - Marlin
Is the move to the middle of the bed something you expect out of G28, or is the move to the middle of the bed something you do afterward with G0 or G1?
by
Thinkyhead
-
Firmware - Marlin
Have you had any version of Marlin where homing with COREXY was working for you? I know we've made a series of changes affecting COREXY handling, so it would be good to know where this started to become a problem.
by
Thinkyhead
-
Firmware - Marlin
Marlin should be fairly easy to modify for this. It is similar to the modifications needed for a clay extruder. See this video, for example:
by
Thinkyhead
-
Firmware - Marlin
Broken and unwanted printers are among the donations I will accept to help my work developing Marlin.
by
Thinkyhead
-
Firmware - Marlin
What position does it report when you do G28 by itself? It should be (0, 0, 0) but it can be affected by things like M206. And what version of Marlin are you using?
by
Thinkyhead
-
Firmware - Marlin
Does this look like a bug introduced in 1.1.0-RC3, and has anyone posted an issue about it on the project? The main servo-related change that stands out is that the SERVO0_PIN is now assumed to differ between RAMPS 1.3 and 1.4. Does this seem like an error to anyone?
#ifdef IS_RAMPS_14
#define SERVO0_PIN 11
#else
#define SERVO0_PIN 7 // RAMPS_13 // Will conflict with BTN_EN2 on
by
Thinkyhead
-
Firmware - Marlin
So, are you using a Delta? A deltabot with a graphical display pushes the limits of a Mega2560, so you may need to reduce DELTA_SEGMENTS_PER_SECOND to get acceptable performance.
If you're not using a delta machine, this is something to look into, as it could mean there is too much processing during the main interrupt.
by
Thinkyhead
-
Firmware - Marlin
I'm confused about this RAMPS 1.3 vs 1.4 change also. I will ask the author about it. The only thing it applies to at all is this:
#ifdef IS_RAMPS_14
#define SERVO0_PIN 11
#else
#define SERVO0_PIN 7 // RAMPS_13 // Will conflict with BTN_EN2 on LCD_I2C_VIKI
#endif
by
Thinkyhead
-
Firmware - Marlin
I haven't noticed any difference. What LCD controller are you using?
by
Thinkyhead
-
Firmware - Marlin
This is the current Setup Guide. It needs work, so please provide feedback about anything that is confusing. Meanwhile you may also find videos on YouTube on how to set up Marlin, so give that a search as well.
by
Thinkyhead
-
Firmware - Marlin
Sorry about the documentation for this feature. It needs work! Please feel free to fix any errors or missing parts that you notice in the Marlin documentation. We can always use more contributors who care.
To clarify this feature, let's look at a simple example of using the "Set Home Offsets" (M428) command:
Let's say your current home_offset is [0, 0, 0]. Assuming a cartesian machine with only
by
Thinkyhead
-
Firmware - Marlin
No guarantee this will be of any help or pertain to this issue. But there was a patch to the createTemperatureLookupMarlin.py script a couple months ago that hasn't been published yet. Check out the version here:
by
Thinkyhead
-
Firmware - Marlin
The main trouble with adding support for add-on boards is finding the available pins and having room for any added processing overhead. If the supplied USB library needs resources that are already in use by Marlin or pins already used by the RAMPS, it may be difficult to integrate. But if the interface can be as simple as that used by an SD Card reader, maybe it's not too hard. Someone who knows
by
Thinkyhead
-
Firmware - Marlin
I believe that homing with COREXY is now working correctly, in the same manner as it behaves with regular cartesians. That is, I believe you can either home XY together with a diagonal move, or separately with one after the other. Just enable or disable the "QUICK_HOME" option, as usual.
by
Thinkyhead
-
Firmware - Marlin
QuoteDjDemonD…I will have a look at the y_max and y_probe values and see if it makes a difference changing them.
Cool. I suspect that the value of Y_PROBE_OFFSET_FROM_EXTRUDER might be an empty string or a floating-point value instead of an integer. It must be an integer.
by
Thinkyhead
-
Prusa i3 and variants
QuoteDjDemonDThis is the verbose output from Arduino 1.6.0...
The issue appears to be that we can't use the min() macro inside of a precompiler #if statement. However, I'm using Arduino 1.6.6, and it compiles it without any problem!
Plus, the error you're getting is "operator '-' has no right operand" which indicates the arguments being passed to min() are the real culprit.
So, what values have
by
Thinkyhead
-
Prusa i3 and variants
QuoteDjDemonDI can't even get marlin 1.1.0 to compile!
Where is it failing to compile? What version of Arduino are you using? Are you using older Configuration.h and Configuration_adv.h files, or did you start with the latest and edit them?
by
Thinkyhead
-
Prusa i3 and variants
QuotesvantegOne thing I haven't fixed yet is the missing reset for last_position when/if e_position is reset. I think there is one somewhere in the code...
I've done a global search for (last|e)_position to see where this might be, but I couldn't find anyplace where this should go. Maybe you can point out the line in pid_with_kc/Marlin/temperature.cpp — or maybe everything is as it should be alr
by
Thinkyhead
-
Firmware - experimental, borrowed, and future
Quotedev Marlin is tripping the thermal runaway far too easily
It might just be the default settings are too touchy. Are you able to adjust the thermal runaway parameters in Configuration_adv.h to a point where it behaves better? If so, please post them here or in an issue on the Marlin Github page.
by
Thinkyhead
-
CoreXY Machines
Please check out for my implementation of PID_ADD_EXTRUSION_RATE based on the example code above. It probably needs some revision, so please give your feedback on the PR, and I will try to make it as solid as possible!
by
Thinkyhead
-
Firmware - experimental, borrowed, and future
Quotedc42IMO having to edit the firmware source, re-build it and re-flash it every time you want to change the configuration is ridiculous. Modern electronics/firmware combinations use a configuration file on the SD card instead. Marlin is showing its age.
You don't have to re-flash just to change configurations. You only have to re-flash if you want to add or remove a feature, thus adding or re
by
Thinkyhead
-
Firmware - mainstream and related support
Page 2 of 5
Pages: 12345