Marlin for the R2 - UBL Enabled

Oh, I think I figured it out. The gcode.cpp and gcode.h files shouldn't be there anymore, since they were renamed to parser.cpp and parser.h in a previous version of Marlin. Removing them makes it compile correctly.

 

I am attempting this on a MKS GEN 1.4. I changed the board to

Code:

// The following define selects which electronics board you have.
// Please choose the name from boards.h that matches your setup
#ifndef MOTHERBOARD
  #define BOARD_MKS_13  // [MKS GEN 1.4]
#endif

I am getting this error:
boards.h:150:46: error: operator '==' has no right operand
#define MB(board) (MOTHERBOARD==BOARD_##board)
^
sketch\pins.h:106:7: note: in expansion of macro 'MB'
#elif MB(MKS_13)
^
exit status 1
operator '==' has no right operand

Have I defined the board improperly?

 

The problem was that I defined the board as

Code:

// The following define selects which electronics board you have.
// Please choose the name from boards.h that matches your setup
#ifndef MOTHERBOARD
  #define BOARD_MKS_13  // [MKS GEN 1.4]
#endif

instead of

Code:

// The following define selects which electronics board you have.
// Please choose the name from boards.h that matches your setup
#ifndef MOTHERBOARD
  #define MKS_13  // [robo]
#endif

After changing to MKS_13 from BOARD_MKS_13 it compiles.
Thanks for pointing me in the right direction.

 

Robos labeling is just wrong, the actual pins are correct.

 

First, thanks to everyone for the hard work on this.
After reading through all posts (several times), I eventually got it to work and the first print was pretty good.
I ran into a problem, though: I was trying to move down the build bed but in fact in moved up into the extruder. I did some investigation and found that it would move up when setting the resolution to 0.1 mm and 1.0 mm, it actually moves down (about 0.2 mm) when setting it to 10 mm - really strange. „Up" is alway going up (just not at the correct resolution), so it is not reversed.
I have the same behavior in the web-interface, directly on the printer and also when I enter it into the terminal. G1 Z0.1 goes „up“ by about 10 mm same as G1 Z1.0 or G1 Z-1.0 - only G1 Z10 moves down slightly.
I reset the EEPROM defaults and it works again correctly. As soon as I run G29 P1 I seem to have the problem.
It seems like no one else was having this problem, otherwise I assume it would have been posted somewhere (or maybe I missed it). Does anyone have an idea? If I can’t fix this I would have to go back to the Robo release without UBL.
Moving into x and y direction works fine...

 

Actually, I did have this problem when I first started UBL. The reason (for me) was that when I reset EEPROM, I did not set my z-offset before issuing the G29 P1 command. Anytime you reset the EEPROM or reload the firmware, the FIRST thing you need to do is set the z-offset; before doing anything else. If you don't, the printer will act like it is right now. I don't know why, but it does make sense. Before it can perform G29, it has to know where z=0.

Don't forget to issue M500 after setting M206 Z#.###

 

Thanks for the replies. I actually did do the z-offset and it also showed up correctly in the EEPROM - also after running UBL. Also printing is working alright (I guess the gcode uses absolute numbers for setting the z value - I am not an expert here).
I am using Waldo's 1.1.8 release - I was not able to compile 1.1.9., I ran into several errors.
Shall I try downgrading from Robo OS 2.0 to 1.xx? Is that worth trying?

 

Not sure. I think I'm actually running 2.0 and my UBL is perfect. I'll see if I am or not.

 

Yep, I'm definitely running 2.0. Not sure what the problem is on your end. UBL can be hard to do (for me anyway). I definitely had lots of trouble when I first started doing it but now I'm doing good every time.

 

Are you running Marlin 1.1.8 or 1.1.9?

 

1.1.8 actually