Quantcast
Channel: Reprap Forum - Firmware - Marlin
Viewing all 2831 articles
Browse latest View live
↧

xy offsets (no replies)

September 4, 2018, 8:07 pm
$
0
0
Marlin 1.1.8

My home is 15mm from edge of bed on x and 8mm from bed on the y
Is there an offset in Marlin for this so when I do mesh bed leveling manually it's above my workarea
↧
Search

Dual X carraige second layer error on Z axis (no replies)

September 4, 2018, 11:28 pm
$
0
0
I have a home built P3Steel which I recently modified to a dual X carraige.
I have happily been printing with the primary extruder for some time with no issues.

I needed to use both extruders today for a part with support material of a different type but after tuning M218 to correct alignment issues between the two extruders, It would print the first layer well but then try to print the second layer about 1.5mm above the first.

I have M851 set to account for the height difference between the proximity sensor and the T0 nozzle, and use M218 to account for the height difference between T0 and T1 nozzles. It seems M218 T1 Z? is the height difference between the two nozzles plus the probe offset).

I tried setting M851 to 0 and setting M206 instead but that did not work.

I am running Bugfix-1.1.x

Output of M503:
G21    ; (mm)
M149 C ; Units in Celsius
Filament settings: Disabled
M200 D1.75
M200 T1 D1.75
M200 D0
Steps per unit:
M92 X80.00 Y80.00 Z4000.00 E94.00
Maximum feedrates (units/s):
M203 X300.00 Y300.00 Z2.00 E25.00
Maximum Acceleration (units/s2):
M201 X3000 Y3000 Z100 E10000
Acceleration (units/s2): P R T
M204 P3000.00 R3000.00 T3000.00
Advanced: B S T X Y Z E
M205 B20000 S0.00 T0.00 X10.00 Y10.00 Z0.30 E5.00
Home offset:
M206 X0.00 Y0.00 Z0.00
Hotend offsets:
M218 T1 X-0.40 Y0.00 Z0.95
Auto Bed Leveling:
M420 S0 Z0.00
G29 W I0 J0 Z-0.35125
G29 W I1 J0 Z-0.26350
G29 W I2 J0 Z-0.14125
G29 W I0 J1 Z-0.02000
G29 W I1 J1 Z0.01250
G29 W I2 J1 Z-0.02000
G29 W I0 J2 Z0.14825
G29 W I1 J2 Z0.08300
G29 W I2 J2 Z0.02175
Material heatup parameters:
M145 S0 H180 B70 F0
M145 S1 H240 B110 F0
PID settings:
M301 P22.20 I1.08 D114.00
Z-Probe Offset (mm):
M851 Z-0.85

Any ideas why it would change height and print the second layer in mid air would be appreciated.

Thanks in advance.
↧
↧

Update 1.1.8 to 1.1.9 Auto Bed Lleveling Bilinear Problem (3 replies)

September 6, 2018, 6:59 am
$
0
0
Hi, I have a problem after updating Merlin from version 1.1.8 to version 1.1.9.
I have used the same parameters from the Configuration.h and Configuration_adv.h files of the older version,
but the AUTO_BED_LEVELING_BILINEAR behaves badly with the new firmware.
Homing and axis movements work correctly with the new firmware, the problem occurs when I try the bed leveling, the y axis moves to position 0, but when it has to increase it does not work, it seems that the stepper motor runs in the opposite direction.
My printer is a HICTOP 3DP11 Prusa i3.

In this video we see the behavior of the printer.
[www.youtube.com]

Has anyone encounter the problem or have any advice for me?
Thanks
↧

Can't get mesh bed leveling to work (no replies)

September 6, 2018, 12:48 pm
$
0
0
Hi I'm trying to enable the mesh bed leveling feature on my printer.
My printer is a Ender-3 patched with the latest version of Marlin (1.1.9)

I've already done it in the past on another printer, but this time I can't get it to work.

I think I followed all the procedure :

Enable MESH_BED_LEVELING in configuration.h
Enable LCD_BED_LEVELING in configuration.h

Level the bed and save to eeprom (using LCD)

Add M420 S1 after the G28 in the startup GCODE

During a print, the Z axis doesn't move to compensate the mesh data.
It's still moving when going to the next layer, but it's completely idle while a layer is printing.

I connected to my printer with pronterface,

If I do a M420 S1, the printer answer me with

Bed Leveling On
Fade Height Off

If I do a M420 V1 the saved mesh is correctly returned.
Then if I move the head around the X and Y axis, the Z axis is still idle and not compensating for the mesh.
Shouldn't the Z axis be moving ?

I attached my configuration.h and configuration_adv.h if it can help.

Anybody have an idea ?
Thanks
↧

problem with LCD and encoder mod (no replies)

September 7, 2018, 2:03 pm
$
0
0
Hello. I'm reading this forum for a while but now I have a problem with a printer mod. I'm talking about: [www.thingiverse.com]
I have made the hardware part some months ago and then I was used Marlin/skynet. Now I'm using v.1.1.9 and I have problems with implement this mod in new marlin.
Can someone tell me generally which part should I change to use 2004 LCD with I2C controler and encoder? I try to understand marlin but it's very hard. I don't wont to destroy the MOBO or something else. I have make some try but with no success, to change something is wors than write it from begining :/
↧
↧

First time install of Marlin (no replies)

September 7, 2018, 3:22 pm
$
0
0
Hi. I am. building a hypercube core xy printer and I am getting an error when installing marlin.. Below is the error and I would appreciated any help, Thanks,

Arduino: 1.8.6 (Mac OS X), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"

Conditionals.h:27:2: error: #error "Old configurations? Please delete all #include lines from Configuration.h and Configuration_adv.h."
#error "Old configurations? Please delete all #include lines from Configuration.h and Configuration_adv.h."
^
exit status 1
#error "Old configurations? Please delete all #include lines from Configuration.h and Configuration_adv.h."

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
↧

TMC2208 with Marlin CoreXY, XY Axes move at an angle(not perpendicular) (no replies)

September 8, 2018, 6:29 am
$
0
0
Hi,

Machine Specs:
Marlin Firmware(tested on the latest bug fix also)
CoreXY
24V PSU
XY Axes: TMC2208
Z & E : A4988

I have been using DRV8825 with MKS Gen 1.4 and they have been working fine.
I recently got TMC2208 for my X and Y axes and setup the jumpers and Marlin firmware to work with it but I am facing a weird problem.
The axes move at an angle of approximately 30 degrees, obviously one motor is moving more w.r.t the other, but I cant figure out why.Verified all settings on Marlin and rechecked.

Anyone faced a similar issue?
Thanks in advance.
↧

UBL - how are probe points calculated? (1 reply)

September 8, 2018, 11:22 am
$
0
0
I am running Marlin 1.1.9 on a Creality CR-10s with a BLTouch probe.
I am trying to auto probe as much of the bed area as I can and am trying to fool the printer into going past the bed size (the mechanics allow the nozzle to go to x 319). Unfortunately, no matter what I try, the auto probing will not go to 319. The bed size has been specified as X 319 Y 300 and there is no inset specified for x max.
As part of trying to understand what UBL does, I thought I would record what x and y positions the automatic print routine goes to. I would have assumed that if I specify a 10 by 10 point matrix that the x probing would happen at minimum x (0) + mesh inset (5) - probe offset (-40). It does indeed start at the right location (45)
I then figured that to calculate the distance between probe points, that the UBL system would figure out the maximum point it could reach (319) and subtract the minimum point the nozzle could reach (0) divide that by 10 as I am calling for a 10 by 10 matrix (32) and derive the probe points from that.

This is what I get:

head position

x 45 63 81 100 118 136 154 173 191 209 x x offset = 40 inset 5 step size 18

y 14 47 80 112 145 178 211 243 276 y y offset = 9 inset 5 step size 33

It doesn't make sense to me. Neither the positions that are probed nor why I can't get to my end position makes sense.
I should add that in Marlin 1.1.8 I could fool the routine to probe at the full X position (X319) (the probing would happen at 319 - the probe offset of 40 or X279)

As I am looking at this, I am wondering if the above x and y positions are correct - I have been trying a number of different configurations and none have resulted in anything that makes sense so take these positions with a grain of salt and consider the bigger question as :

"how does Marlin determine which x and y positions it will probe" and
" how can I fool Marlin into probing the biggest area possible if I can physically exceed the print bed area with the nozzle"
↧
Search

Z offset after homing (2 replies)

September 8, 2018, 6:21 pm
$
0
0
Hi
Marlin 1.1.8
Anybody know how to offset z height to physically be 1mm above the mechanical endstop switch after homing
↧
↧

SD init fail.....make me crazy:X 2560 rev b. (no replies)

September 8, 2018, 1:56 pm
$
0
0
Hi at all.Sorry my English,but I think here it's the best place for my problem.

Surely it's my mistake.But on my A10 I can't have access to SD card.
With stock no problem,try with marlin 1.1.9 and the problem appear. Try with last 2.0 bugfix same.

The problem is. On screen detect SD "card inserted".But if I go in menu "no SD card"

I try several way,but nothing to do.(low level format,change SD,check the firm pin)
I switch back with stock firm and still not working
What the hell?
The "SD init fail" appear in repieter on startup menu.


What I say.why? Why also with the stock?

But maybe it's my mistake.
Since was the first time I upload a firm on print,I take it from thinkinverse.In the file there were 2 files .hex
One with bootloader,and other normal.
I flash with bootloader and have to recover my board with my Arduino Uno as ISP,cause I cannot detect print.(no access to LCD,no detect via USB )
All ok...load marlin,and the sd problem begin.

Can that fact have cause some issue with LCD/sd?

I hope someone understand and help me rework SD.Cause for me it's very very important print from SD,due pc-print distance.

Best regards
↧

babystepping z (no replies)

September 10, 2018, 9:42 am
$
0
0
Hello
I activated the babystepping on my prusa i3 pro c double extruder, the babystepping works, the motors move it but on the LCD it shows no value.
What could I have done wrong?
attached my firmware and a photo of the problem.
[attachment 106959 firmware.rar]
[attachment 106960 foto.PNG]
↧

Auto Leveling not working. (1 reply)

September 10, 2018, 12:24 pm
$
0
0
Hi Guys,
Im new in this so please be gentle.lol
i have a cube X printer and did the upgrade to reprap. everything works great, but i cant seem to get the auto level working.
on marlin i activated the auto level process but nothing. when i use the G29 nothing happens. the printer just stays put at whatever location it may be. This being home position.
Can someone help me out? Thank you
↧

Start G-Code , in firmware not slicer, does this exists ? (no replies)

September 10, 2018, 1:16 pm
$
0
0
Hi.
i've been wanting to remove my start gcode from the slicer in order to be able to use the same gcode file on multiple printers.
typically i can use the same temps and speeds, but the start up code differs in terms of tool cleaning and nozzle prime position.
So i would like to have the start g-code in firmware and maybe call a Gxxx or Mxxx to activate this start gcode.
that way it's possible to put the homing, probing , move Z, goto Xxx Yxx, extrude , or whatever the needs might be, everytime a print is started.

Does this functionality exist already ?
i've seen the Autostart, but this is only for power up,and requires an SD, and i want it to run every time i start a print (typically from SD)
and there's also the CUSTOM_USER_MENUS , but these have to be activated through the LCD.

Anybody did this already ?
↧
↧

Can G-code scripts be run automatically on inserting an SD card when using Marlin Firmware? (no replies)

September 11, 2018, 3:26 am
$
0
0
A colleague posted this question on Stack Exchange 3D Printing (of which I am one of the moderators), and I wondered if there was a solution, or software hack, for this?

Quote

When running Marlin Firmware, is it possible to run G-code scripts/series of commands automatically when you insert the SD card?

I'm running Marlin on a 3D printer board using an ATmega 2560 based board with a reprap discount LCD controller with an SD card slot. I would like to do this without the need to add another computer/board, so native from the board running the Marlin Firmware.

Note that I am not asking about the startup codes upon power on, with the SD already inserted, but rather printing is triggered, on a printer already turned on, just by inserting the SD card. The files that can be run upon start up were mentioned in this answer to a different question:

Quote

With Marlin 1.1.0, you can automatically run a G-Code file when powering on the printer with a SD card already present.

Add a file named auto0.g at the root of your card, containing the following G-Code:

G28 ;Auto-homing
G29 ;Bed leveling


Normally the bed leveling map should be reused for all subsequent prints, until the printer is turned off.

It is possible to provide up to 10 files, from auto0.g to auto9.g.

Just to re-iterate, the answer above is for power on of the printer. However, I am looking for a solution for a printer already switched on and it is the insertion of the SD card which triggers the printing.

Thanks in advance
↧

Adding optoencoder to endstop slot to provide filament odometer - firmware help needed (no replies)

September 11, 2018, 10:13 pm
$
0
0
I'm trying to figure out how to add a filament travel monitor to (hopefully) provide early warning of filament slippages.
I use Ramps and have 3 free endstop slots so I want to repurpose one to work as an encoder to count toggles (change from open to closed) to provide the filament travel detector.

Background follows, but any help for the following would be appreciated:
Steps:
1. repurpose the endstop slot to count toggles
2. every time the internal marlin odometer gained another 5cm (?) then check the encoder count is in the right ballpark (eg 49-51 toggles).
Obviously 2x retract distance would have to be subtracted from the count as the encoder will count upwards with filament movement in either direction.
3. sound an alarm/trigger M300 code if the values in 2 differ significantly.
3a. send the ratio to the LCD with M117 [string]
4. reset the toggle count
5. repeat endlessly...

There are a number of posts on the web by people who claim to have added filament odometer which "works with Marlin", but none include instructions and there doesn't seem to be a g-code relevant (just the M600 runout code).
I'm thus a bit suspicious no-one has *actually* done it in Marlin.

I have printed the physical parts for a simple filament odometer using an optoendstop and an encoder wheel which just rolls along the filament.
The wheel has 1 "slot" per mm, and is printed in clear filament.
I accidentally printed the wheel at too high a temperature which meant the slots melted, so the optoendstop reads "open" when shining through the clear plastic and "closed" when shining through the opaque "gap" but otherwise works perfectly.
I coated the edge of the wheel with gorilla glue (essentially PVA) to increase grip where it contacts the filament, and it seems to turn reasonably accurately.

As above I'd like to trigger the buzzer on a 12864 LCD Controller if the measured travel distance is signficantly different to the expected distance (as commanded by G1 extrusion)
Icing on the cake would also be to output to the LCD the odometer as well as measured:commanded travel ratio

Hoping someone can help.
Tx
David
↧
Search

Delta TMC2130 sensorless homing Marlin 2.0 (1 reply)

September 12, 2018, 10:35 am
$
0
0
Hello everyone,

yesterday I tried Marlin 2.0 on my delta machine. I use the einsy rambo - yes, very exotic for delta machines. I also enabled sensorless homing:

I played around with the sensitivity but the Z axis keeps crashing. X and Y axis homing works fine. Any Ideas what to do?

Also homing a single axis with "G28 X" just homes all axis - is this command disabled on delta machines?

Thanks for your help!
↧

Autoleveling issue with BLTOUCH (no replies)

September 12, 2018, 3:41 pm
$
0
0
Suddenly, my Anycubic Kossel Linear Plus printer is sending the print head crashing into the bed whenever i run the G29 command.

Here is the debug log:
18:26:03.746 : X:0.00 Y:0.00 Z:233.83 E:0.00 Count X: 37578 Y:37578 Z:37578
18:26:13.164 : echo:DEBUG:LEVELING
18:26:17.454 : current_position=(0.00, 0.00, 233.83) : >>> gcode_G29
18:26:17.454 : Machine Type: Delta
18:26:17.454 : Probe: BLTOUCH
18:26:17.455 : Probe Offset X:0 Y:-35 Z:-1.40 (Middle-Front & Below Nozzle)
18:26:17.455 : Auto Bed Leveling: BILINEAR
18:26:17.455 : G29 Auto Bed Leveling
18:26:17.458 : current_position=(0.00, 0.00, 233.82) : sync_plan_position_kinematic
18:26:17.463 : current_position=(0.00, 0.00, 233.82) : setup_for_endstop_or_probe_move
18:26:17.465 : current_position=(0.00, 0.00, 233.82) : set_probe_deployed
18:26:17.465 : deploy: 1
18:26:17.467 : do_probe_raise(50.00)
18:26:17.469 : >>> do_blocking_move_to(0.00, 0.00, 233.82)
18:26:17.469 : destination=(0.00, 0.00, 233.82) : set_destination_to_current
18:26:17.474 : current_position=(0.00, 0.00, 233.82) : xy move
18:26:17.475 : <<< do_blocking_move_to
18:26:17.475 : reset_bed_level
18:26:17.477 : >>> probe_pt(-55.00, -55.00, no stow)
18:26:17.482 : current_position=(0.00, 0.00, 233.82) :
18:26:17.482 : do_probe_raise(10.00)
18:26:17.482 : >>> do_blocking_move_to(-55.00, -20.00, 233.82)
18:26:17.483 : destination=(0.00, 0.00, 233.82) : set_destination_to_current
18:26:17.915 : current_position=(-55.00, -20.00, 233.82) : xy move
18:26:17.978 : <<< do_blocking_move_to
18:26:17.982 : current_position=(-55.00, -20.00, 233.82) : set_probe_deployed
18:26:17.982 : deploy: 1
18:26:17.984 : current_position=(-55.00, -20.00, 233.82) : >>> run_z_probe
18:26:17.986 : >>> do_blocking_move_to(-55.00, -20.00, 11.40)
18:26:17.988 : destination=(-55.00, -20.00, 233.82) : set_destination_to_current
18:26:17.992 : current_position=(-55.00, -20.00, 233.82) : xy move
18:26:17.994 : destination=(-55.00, -20.00, 11.40) : prepare_uninterpolated_move_to_destination
18:26:17.998 : current_position=(-55.00, -20.00, 11.40) : z lower move
18:26:25.720 : <<< do_blocking_move_to
18:26:25.720 : current_position=(-55.00, -20.00, 11.40) : >>> do_probe_move
18:26:25.774 : set_bltouch_deployed(1)
18:26:25.774 : >>> do_blocking_move_to(-55.00, -20.00, -300.26)
18:26:25.775 : destination=(-55.00, -20.00, 11.40) : set_destination_to_current
18:26:25.780 : current_position=(-55.00, -20.00, 11.40) : xy move
18:26:25.782 : destination=(-55.00, -20.00, -300.26) : prepare_uninterpolated_move_to_destination
18:26:25.786 : current_position=(-55.00, -20.00, -300.26) : z lower move
18:26:28.550 : Printer reset detected - initalizing

There is a strange call to do_blocking_move to -300 just after the bltouch is deployed.

Has anyone seen this? Any suggestions on what could be happening?
↧
↧

Linear Advance questions (no replies)

September 14, 2018, 9:33 am
$
0
0
Hi, I am interested in tuning linear advance on my printer running RAMPS with Marlin 1.1.9 release

I tried generating test patterns using this page: [marlinfw.org]

The first one I did in the default range 0-2, then I tried 0-10, and even 0-100, and I never see the effect of under/over extrusion going away or reversing.

Does this not work with higher acceleration values? I have 3000 mm/s^2 accel on XY and 10mm/s jerk. The extruder is a greg's wade 1.75mm (no bowden).
I was testing 15mm/s to 40mm/s speed difference.

Is it possibly some conflict between extruder vs XY accel / jerk?

edit: Is there a setting I missed in Configuration.h to enable this in the first place?

Also should I be running the 1.1.9 bugfix instead? I never quite understand why the branch with fixed bugs would be the one that is cautioned *against* using on the download page.
↧

Cant get manual auto leveling to work (no replies)

September 14, 2018, 11:56 am
$
0
0
hello everyone...

so i received anet a8 printer a couple of days ago and now i've put marlin on it. so far so good. except that manual auto leveling feature will not work because Z offset will not go into negative once it hits Z endstop trigger.

i tried commenting this out
// Min software endstops constrain movement within minimum coordinate bounds
//#define MIN_SOFTWARE_ENDSTOPS
//#if ENABLED(MIN_SOFTWARE_ENDSTOPS)
//  #define MIN_SOFTWARE_ENDSTOP_X
//  #define MIN_SOFTWARE_ENDSTOP_Y
//  #define MIN_SOFTWARE_ENDSTOP_Z
//#endif

and i tried sending pronterface commands like this:

>>> M211 S0
SENDING:M211 S0
echo: Soft endstops: Off  Min: X-33.00 Y-10.00 Z0.00  Max: X220.00 Y220.00 Z240.00
echo:enqueueing "G28"
echo:enqueueing "G29 V1"
G29 Auto Bed Leveling
Manual G29 point 1 of 9
echo:endstops hit:  Z:-0.05

and you can see it hits endpoint and it wont move anymore down so i have to tediously level the bed the old fashioned way with turning screws... and i hate it lol... takes a lot of time
↧

can't compile with PARKING_EXTRUDER in 1.1.9 (no replies)

September 16, 2018, 6:33 pm
$
0
0
Hi guys. I have been trying to update to 1.1.9 from 1.1.8, I have double checked everything I can think of. Compiles perfectly when I disable PARKING_EXTRUDER. 1.1.8 is working great for me but I was looking to try a few of the newer features. I have also tried the latest bug fix version also with the same issues. Any help with a solution to this problem would be great and thanks in advance.
↧
Viewing all 2831 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>