Besides changing the Z Probe Offset number in configuration.h, you also need to do a M502 and M500 to get the value updated in the EEPROM.by Roxy - Firmware - Marlin
QuoteGaRv3 Ok, the latest problem was caused by the cold end fan screw touching the probe. I like it when people say what was wrong at the end of thread. And especially when the problem turns out not to be Marlin's fault.by Roxy - Firmware - Marlin
Quoteauggie246 Yes my Z_PROBE_OFFSET_FROM_EXTRUDER is at a number which when I do G1 Z0, my nozzle barely touches the bed. However after I do a G29 P1. my mean mesh is around -0.9 G29 T gives Bed Topography Report: Yes. But if that was true... There should be some mesh point on that Topography map that is close to 0.00 mm. Your Z-Probe_Offset_From-Extruder is not right. All of the bedby Roxy - Firmware - Marlin
The very first bed leveling firmware that came out was the 3-Point leveling. It used a model of the print bed being a plane that can be tilted. The author simplified what the user would have to specify by introducing the concept of ``` <---<<< GitHub code quotes!!! #define X_PROBE_OFFSET_FROM_EXTRUDER 38 // X offset: -left +right #define Y_PROBE_OFFSET_FROM_EXTRUDER -7by Roxy - Firmware - Marlin
You should adjust your Z_PROBE_OFFSET_FROM_EXTRUDER number such that when you home, you can lower the nozzle and when it just barely touches the bed, the LCD is saying Z is equal to 0.00 mm. If you set your printer up to home in the center of the bed, and post a G29 T we will have a much better idea what is happening. Probably, you should post a G29 W also.by Roxy - Firmware - Marlin
In the UBL system, X & Y can be used to specify the starting location of an operation. That can be automatic probing, manual probing, invalidation of mesh points or editing. What ever the specified X & Y location is, the nozzle is moved to the closest mesh point to that location (not necessarily that location). With a G26 Mesh Validation Pattern printed on the bed... It is easy to eby Roxy - Firmware - Marlin
Yes. But you are probably better off just bringing up UBL. It will automatically probe the reachable areas of the mesh You can do a G29 P3 to fill in the unprobed mesh points with reasonable values You can print a G26 Mesh Validation Pattern You can then do a G29 P4 R to edit any mesh point that isn't perfect You can use the 'Cheat Sheet' of commands at the front of this page to bringby Roxy - Firmware - Marlin
Ideally, the mean of the mesh points should be close to 0.000 mm. I think things work out best homing the Z Axis at the center of the bed. If you home in the center of the bed, you can look at the G29 T map to see which corners are too high (or low) and adjust them.by Roxy - Firmware - Marlin
Yes... It is very possibly a side effect of the fade height. How large is your Z_PROBE_OFFSET_FROM_EXTRUDER number? Or what is the G29 P5 number? If you have a large number (say greater than 1 mm) you are going to see the fade height impact things.by Roxy - Firmware - Marlin
Probably this should be implemented so it can be controlled with GCode. And the code should wire up the M109 logic to wait for the enclosure to reach temperature. This is a good idea and will have value to a lot of users.by Roxy - Firmware - Marlin
I think you need to install Git-Bash. I forget why that is necessary now but it has to do with some repository that needs to be checked out.by Roxy - Firmware - Marlin
Actually... The CoreXY machines should not be much different than the normal Cartesian machines from a computational perspective. Probably that quote is from this thread: That is where we are tracking the bulk of the 32-bit issues. That quote is from 6 months ago. If you start reading from that point in time, there will be updates to how to use the USB Serial as well as flashing imagby Roxy - Firmware - Marlin
If you want to use the Atmega-2560 there is no reason not to use the Bugfix-v1.1.x branch. The feature set is identical with the Bugfix-v2.0.0 branch. We are using Re-ARM boards with RAMPS boards as the 'Reference Platform' to bring up the Bugfix-v2.0.0 branch. Half of the people with 32-bit processors helping with the effort are using Re-ARM boards. The USB-Serial does work. I know thisby Roxy - Firmware - Marlin
For sure... You want to move to Bugfix v1.1.x Use a visual diff program like Notepad++ (with the visual diff add on enabled) to help with the migration. It should only take 10 minutes to cross your setting over if you have a visual diff program up and running. (Move settings from both configuration.h and configuration_adv.h)by Roxy - Firmware - Marlin
If you generate (and add) a table... Try to be smart about the range of values and the spacing. Marlin does a sequential, linear search from the end of the table. So just a few values at the higher temperatures. And then some closer spacing of values near the normal print temperatures.by Roxy - Firmware - Marlin
My suggestion would be to turn off all bed leveling. And get the Z_PROBE_OFFSET_FROM_EXTRUDER number correct so you can home in the center of the bed, and print a small object there. Perhaps a 20mm calibration cube. When you can do that (with no bed leveling turned on or built into the firmware), then you are ready to turn on UBL and follow those steps in the 'Cheat Sheet'. If you do this,by Roxy - Firmware - Marlin
Well...Its good to see that entire work flow. You are obviously very serious about having the printer setup right. One of the problems with that work flow is measuring the distance between the nozzle and bed with a business card is not highly accurate. I'm highly biased. After all... That is why I wrote the UBL bed leveling system. I thought it was needed. If you bring up the UBL bed lby Roxy - Firmware - Marlin
The Z-Probes need some amount of clearance. Set it as low as you can without damaging your printer. But seriously... Even a 10 mm move is nothing in the big picture. Most of my prints are 6 or 10 hours long. Is a 10 mm move on the Z-Axis to protect your printer that big of a deal?by Roxy - Firmware - Marlin
You can buy a new RAMPS v1.4 board for under $4 (including shipping) on eBay: If you are doing this because you enjoy it and just want to play with things, that is fine. I'm 100% supportive. But if you are doing this to regain lost functionality of the RAMPS board, I'm thinking it doesn't make sense.by Roxy - Firmware - Marlin
Yes... Use G29 P1 U T That will start probing the bed with the points as far away from previously probed points as possible. When you have 8 or 12 points.. It usually makes sense to stop the probing and do the physical adjustment of the bed. And then do the command again until you have the bed as physically level as you can get it. At that point you can do a G29 P1 (with or withouby Roxy - Firmware - Marlin
On the work to move Marlin to 32-bits we are primarily using Re-ARM boards with Graphical LCD's. The Graphical LCD's need to be talked to very slowly.... The bits are pulsed in one at a time and each bit (and clock) needs to be fairly long for reliable transmission.by Roxy - Firmware - Marlin
The character based (non-graphic) LCD panels are the fastest. And they don't use u8glib. Something like this will give you the best results:by Roxy - Firmware - Marlin
200 segments per second is a lot. But you have some options. You can lower the max feed rates so the printer moves a little bit slower. Or you could go back to the 20x4 LCD display. That uses a lot less CPU cycles than the graphical display. Or... you could bump up #define LCD_UPDATE_INTERVAL 100 in the ultralcd.h file. That will make the LCD panel more sluggish, but it will still worby Roxy - Firmware - Marlin
Dust... Do you have any ideas why his board can flash Marlin v1.6 once but then gets sick?by Roxy - Firmware - Marlin
Not a 'Guide' per say. But if you look at the Sticky threads here... They all add GCodes and MCodes to Marlin. Marlin Hacksby Roxy - Firmware - Marlin
This may not be the right place to get help... But at the GitHub MarlinFirmware forum, there are experts that can get a boot loader onto any AVR board. I've never needed to do that. But if I kill the boot loader, I'm confident somebody there will have both what I need and the instructions to fix the board. I don't think you need to worry about killing the board.by Roxy - Firmware - Marlin
Marlin knows how to move and home Scara arms. You would just add a tool type for each weird tool you have. And then what ever extra support you need for the particular operations the tool would do. But all of the positioning of the tool is already in the code base for Scara's.by Roxy - Firmware - Marlin
QuoteRoberts_Clif All Marlin 1.1.X worked fine for me until I hit Marlin 1.1.6 then I cannot get it to work correctly. Marlin 1.1.6 will run once maybe twice then will not boot again. And then it takes forever to get a re-flash back to Marlin 1.1.5 to work correctly. So I have stopped at marlin 1.1.5 Good Luck. Roberts_Clif... What controller board are you using? And which Arduino are youby Roxy - Firmware - Marlin
The BL-Touch needs to be plugged into the Servo 0 connector... Do you have that done?by Roxy - Firmware - Marlin
G28 clears the bed leveling data for most of the bed leveling systems. G28 does NOT clear the state or data for UBL.by Roxy - Firmware - Marlin