Marlin Firmware Upgrade 1.1.0 RC8 & RCBugFix (For R1 & R1+PLUS)

@danzca6 & @WheresWaldo The IR probe, does as we know sense for some of the RAMPS compatible boards, as long as there is the sense input, optical or other. You know @danzca6 that was the KISS method I was going to look into,MESH first, then proceed to software control from a spare arduino pin.......hoping in Gods Green Earth @WheresWaldo or @danzca6 first would fix code....not the proper coder thing, but you know...........

 

These are the same RC Bugfix with MESH from above, just renamed for the most part correct? I just want to make sure I properly align what I'm getting with what I have. Thanks.

 

OK thanks, I almost tried to compile ABL when I use MESH. I hate being the new guy lol.

 

Getting the following error message during compiling:

Arduino: 1.6.9 (Windows 10), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"

fork/exec C:\Users\Arduino\hardware\tools\avr/bin/avr-gcc.exe: The filename or extension is too long.
Error compiling for board Arduino/Genuino Mega or Mega 2560.

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

Apparently it's a Windows file system issue. I'll try to figure out a way around it but I thought it might be a good idea to post it here so anyone in the future who has the same problem can find it.

Just to clarify for myself; I can run the MESH leveling from the Simplify console, right? I don't need an LCD? I looked it up in the Marlin documentation but it only said that 'It can be done'. Not how it can be done.

EDIT:

Ok it seems to have been a mismatch with the version of the U8glib library I used. I downgraded to 1.18.0 and it compiled.

EDIT 2:

The new firmware is now on the printer. I connected through Simplify3D and tried homing all axes but it was a no-go on the z-axis. It doesn't recognise the IR sensor.

I found the following instructions to perform MESH bed leveling without a controller:

• G29 or G29 S0 Print mesh info
• G29 S1 Initiate probing, will do a homing + travel to first probe point. Now use Printrun or what you use to slowly lower the hotend until it touches the bed, i.e. with a paper between to feel when it's close enough.
• G29 S2 Save current height for the current point, then travel to next probe point. Repeat the manual lowering until touches. Do this until all points have been probed.

Upon sending a G29 command to my printer, despite it not being commented out in the firmware, I get the message back:

"READ: Mesh bed leveling not active."

EDIT 3:

Realised I had made a mistake in not changing the following line:

"const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop. //robo"

When I changed it, it started using the IR sensor to home the z-axis. In a different manner than before. Much slower and 'more carefully'. But hopefully that turns out to be okay.

Sorry if this is all pointless spam. It's possible someone as new to this side of the printer as I am will have the same troubles so I'm trying to be detailed.

 

Ah I see.

I have no choice as I don't have a controller, so I'll get started on that. Thanks, Waldo.

 

Sure thing Waldo! I'll open up my printer a little later after I have a go at the MESH leveling. I have run in to a problem that I thought I might find last night. The printer won't go down any further after the IR sensor is triggered, meaning the nozzle won't touch the bed. If I move the IR sensor higher in its bracket, it kind of makes the sensor a bit pointless since it won't be stopping the hot nozzle touching the PRINTinZ plate and damaging it (not that I'm performing this procedure with the nozzle heated, I just mean for regular axis homing).

 

Okay I'll give that a go. The idea would be for the printer to home using the IR sensor, but give me control ultimately. I wouldn't like it to ignore the sensor and to drive itself in to the bed.

 

Code:

//#define ENDSTOPPULLUP_ZMIN
and change this one back to "false"

This one did not seem to change the functionality of the z-homing for me.

Code:

#define Z_MIN_ENDSTOP_INVERTING true //--ROBO-BH set to true to invert the logic of the endstop.
You might also need to play with Configuration_adv.h and this define

I changed this line in order to get the IR sensors input to be recognised. It worked but still will not allow any more movement downwards after the sensor is triggered.

Code:

// If you want endstops to stay on (by default) even when not homing
// enable this option. Override at any time with M120, M121.
//#define ENDSTOPS_ALWAYS_ON_DEFAULT

I will try this next. It sounds like it will simply not allow any movement, since it will consider all endstops to be triggered, but I'll try it regardless.

 

That's no problem. I'll write that up when I get it working. For now I would like to see MESH leveling in action so I plugged the z-endstops back in and modified the firmware so they work. I'll get MESH working like that for now before working on the getting the IR sensor letting me go below it's trigger point.

 

In response to your last message, if I set a value for the Z_PROBE_OFFSET_FROM_EXTRUDER that lets the extruder touch the bed in the center (which would be a hard value to obtain anyway since the IR sensor will not go below its trigger point), then won't that value only be valid for the center? And not for any of the other MESH points on the bed?

 

I just ran the first MESH leveling procedure. Between each point I noticed the printer pausing. Each pause was marked with an entry in the console that said 'echo busy: processing'. It appeared that the printer thought it was moving during these pauses, as it was quite out of line by the last row of points and hit the X-endstop, meaning I could not complete the procedure. I will try running the sequence with a more powerful PC to see if it was my notebooks slow processor that caused the issue.