It is sounding like a mechanical issue. The gcode does not change. If it works once, it should always work the same way. However, a Gcode file is a result of a previous slicer. No telling what the settings were on the slicer. Maybe you should try to reslice the model.by ruggb - Firmware - Marlin
Repetier thinks you have 2 extruders when you tell it you have 2 extruders in the config Extruder TAB. Maybe you have 2 configurations and are using the wrong one.by ruggb - Repetier
the only setting is the temperature. Every time you slice a model, the first thing slic3r must do is bring the temp up before starting the print. Therefore, it places an M109 command in the gcode at the start. I don't understand what is annoying about bringing the temp up b4 you print. You could manually turn the heaters on and wait til the bell rang, then start the print. The M109 command then wby ruggb - Repetier
Yes, It is basically to compensate for probe hysteresis and trip position. IE, when my piezo nozzle probe activates, it does so when the nozzle hits the bed. I can't anticipate the bed as I can with a mechanical endstop. Therefore, I must have an offset so that when it hits the bed, Marlin declares that Z=0 is at Ztrip +- offset. My probe triggers at Z = -0.1 So, to get a 0.1 (paper thickness) clby ruggb - Firmware - Marlin
there is a setting in Marlin, but I don't know about anything elseby ruggb - Repetier
where are you with this?by ruggb - Repetier
I posted this on the Marlin github The question is where is the problem, Marlin or Repetier Host.by ruggb - Repetier
I currently have FIX_MOUNTED_PROBE defined with #define NOZZLE_TO_PROBE_OFFSET { 0, 0, 0 } So should I have NOZZLE_AS_PROBE defined with this (undefined) //#define NOZZLE_TO_PROBE_OFFSET { 0, 0, 0 } Seems like the same thing but different. Why the redundancy?by ruggb - Firmware - Marlin
So what is new? I have a nozzle mounted piezo probe/endstop == NOT carriage mounted, The Nozzle IS the probe. based on this excerpt from configuration.h, I should enable both FIX_MOUNTED_PROBE and NOZZLE_AS_PROBE but that does not work /** * A Fix-Mounted Probe either doesn't deploy or needs manual deployment. * (e.g., an inductive probe or a nozzle-based probe-switch.) */ //#define FIX_by ruggb - Firmware - Marlin
OK, either you have a serious bed level issue OR your method of measuring the Z0 position is flawed OR your offset is set in the wrong direction. When you home Z, it is not positioned at the offset height. It does not go there until you issue a G0 Z0 command. If your nozzle is at the correct level after a home Z then hits the bed I think your offset is in the wrong direction or you don't really nby ruggb - Firmware - Marlin
Marlin ver bugfix 2.0.x.8cfcabe Repetier v2.1.6 I home all with G28. Z_AFTER_HOMING is set to 30mm I then run this script g0 x50 y50 ; place XY on bed g28 z ; home Z and raise to 30mm (Z_AFTER_HOMING) g0 z0 ; Z=0 = measure offset It goes to x50, y50 then homes Z which ends up at Z=30mm then it move Z to 0 to test my offset which is set at 0.20mm Repetier Log 20:23:54.770 : N79 G28*45 20:24:03by ruggb - Firmware - Marlin
I think it is sunspots. NOTHING seems to be working as it should lately. I had and am having issues with Repetier Host displaying the correct Z height with offset. If you home Z with no offset what is the Z distance indication and does it appear to be touching the bed? If it is digging into the bed with a - offset, try a + one. I have long been on ver 2 so I can't remember the details of v1.1.9by ruggb - Firmware - Marlin
motor direction this is v2.0.x bugfix, but I think it is similar in 1.1.9 // Invert the stepper direction. Change (or reverse the motor connector) if an axis goes the wrong way. #define INVERT_X_DIR false #define INVERT_Y_DIR false //11 #define INVERT_Z_DIR true //11 Y & Z are not default, they are my changes.by ruggb - Firmware - Marlin
I'm old, you are suppose to interpret what I write. Seems like you did. Yes. VERTICAL. Lateral and horizontal are the same thing. You have to remember that developers are engineers and engineers can't communicate very well. I know, I am one. I am not sure where this came from #define Z_PROBE_OFFSET_FROM_EXTRUDER -0.5 // Z offset: -below +above ” I have seen it and it is old. The latest 2.0 bugfby ruggb - Firmware - Marlin
QuoteRhartl Z_PROBE_OFFSET_FROM_EXTRUDER THIS NOT THE OFFSET YOU NEED!!!!!!!!!!! Read previous post again. The above is a LATERAL offset./////// probe here ...........nozzle here This is the horizontal offset //#define HOTEND_OFFSET_Z { 0.0, 0.00 } // (mm) relative Z-offset for each nozzle Nozzle here | | offset | | bed here When you change it you must do an M500 to save it If you hby ruggb - Firmware - Marlin
Yep, looks like it is a runaway. The only strange thing I see is the thermistor selection of 6. You must eliminate things so I would start by changing the thermistors to 1 If that does not help, disconnect E1 and see if you can tune E0 to get good numbers. Do the same thing for E1, then try that. Obviously, it should not heat E1 if the command is M303 C5 E0 S230. It should also get limited at 260by ruggb - Firmware - Marlin
Are you using Repetier Host? If so the issue may be there and not Marlin. I am running Marlin v2 and I don't see any way to change that. However, if Repetier has a setting under configuration/printer settings/extruder for Max extruder and Max bed temps. You can create different configs and set it for each. You can also change it while connected to a printer but you must disconnect to change a difby ruggb - Firmware - Marlin
QuoteRhartl So with a few tweaks to the above procedure I am printing again. Thank you to all for you kind indulgence. Great! here is a TIP I would suggest flagging lines that you edit. I use //** or just add the ** to a comment. This way if you have to upload your files people can easily find what you edited and it makes it easier for you to find the items also. I also use double numbers so I caby ruggb - Firmware - Marlin
Previous builds displayed Babystep with 3 digits .xxx which was perfect - it is BABY steps after all. Now it is showing xx.xxx in the newest release. While looking for something else I stumbled upon something that indicated it would change the digits displayed, but I forgot where/what it was. I do not think it is in the config files and I have searched for "baby" in all the files but can't find iby ruggb - Firmware - Marlin
there is a setting to deal with inverted motors. Your fix it trying to tell it to go to Z= -84 // Invert the stepper direction. Change (or reverse the motor connector) if an axis goes the wrong way. #define INVERT_X_DIR false #define INVERT_Y_DIR false #define INVERT_Z_DIR true That is mine and are not default.by ruggb - Firmware - Marlin
I assume you are using Arduino IDE. If so, ignore it. If it compiles, ignore those library error. been there done that.Apparently Arduino can't handle Marlin. I get a crap load of them. PlatformIO work much better, but I can't figure out how to use it yet.by ruggb - Firmware - Marlin
around line 1000 in config....h /** * Multiple Probing * * You may get improved results by probing 2 or more times. * With EXTRA_PROBING the more atypical reading(s) will be disregarded. * * A total of 2 does fast/slow probes with a weighted average. * A total of 3 or more adds more slow probes, taking the average. */ //#define MULTIPLE_PROBING 2 //#define EXTRA_PROBING 1by ruggb - General
it looks like it is losing steps and it occurs right after the top layer of the rest of it. Might have something to do with speed. Try slowing it down and see what changes. I had shift problems and installed flyback diodes on the axis steppers and it went away.by ruggb - Firmware - Marlin
I just posted "Z after Homing". It may give you a clue. I also have a note in my configs that the backoff entries mess with other things. But I put that there a while ago so I don't remember what was going on then.by ruggb - Firmware - Marlin
I am confused again. Maybe someone has figured this out already. I'm talking bigfix 2.0.x 64876f7 For Configs there is; //#define HOMING_BACKOFF_POST_MM { 2, 2, 2 } // (mm) Backoff from endstops after homing //#define Z_AFTER_HOMING 10 // (mm) Height to move to after homing Z //#define Z_AFTER_PROBING 5 When I do a Z home with Z_AFTER_HOMING undefined, Z_AFTER_PROBING = 15by ruggb - Firmware - Marlin
Quotejdebuhr ok.. I will try that.. BUT WHY did it work 2-3 times prior? nothing was added or changed to the libraries.. just the Configuration.h I have gone around the world chasing errors in Arduino compile. The answer is, wait for it, Arduino can't handle the Marlin project. Unless the errors are at the end of the compile and it does not compile, ignore them. PlatformIO is much better. I alsoby ruggb - Firmware - Marlin
as I found stated in an Arduino help file, you cannot simply rename a library folder. You must move it out of the library path. Try it and report back it they were correct.by ruggb - Firmware - Marlin
upload your config files and/or anything else you may have changedby ruggb - Firmware - Marlin
I am using 2.0.x bugfix. what are you using?by ruggb - Firmware - Marlin
QuoteRhartl The cardboard is probably between 1 and 2 mm thick. So from Marlin firmware I should set #define Z_PROBE_OFFSET_FROM_EXTRUDER somewhere between -1 and -2? Then recompile and load that? Right? THERE is the problem!! there are 2 offsets. THIS one is the distance laterally that the probe exists from the nozzle. the offset you are looking for is addressing is the offset of the nozzle fby ruggb - Firmware - Marlin