Ramps 1.6 board with a TFT35 onto an R1 plus.

Never heard of one, but looking at it I would say it is a minor change to the existing RAMPS layout so probably fine to use.

I would imagine not. If you use standard stepper drivers you should be fine.

As for the LCDs I have not played around with anything other than the RepRap Discount, the Full Graphics and the LCD/Pi modification to work like the R2/C2 (see the other thread on this).

Some LCDs are already predefined in Marlin and just need to have the configuration file edited to get them going (the Full Graphics controller is that way).

 

Maybe it adds nothing from a practical standpoint. I have never used one other than the 1.4 RAMPS at least and it supports everything in general that the printer is capable of.

Faster USB may help to a point, the Arduino can only support 2.0 so anything faster than that is moot.
There are a number of LCD screen types supoprted by Marlin, but many of them require changing the configuration.h file and recompiling then reloading to the Arduino.

 

@BrooklynBay the screen you point to (regardless of reseller it is made by Makerspace in China) works because it has its own firmware on board. there are no settings involved other than on the TFT itself. It has a config.txt file that can change some of the parameters as outlined in their documentation (Google it for yourself) There are even alternative sets of icons that can be loaded (another Google search for you to do). You cannot modify the layout, but there is one page of the screen where you can add buttons and macros associated to those buttons.

 

One more thing, there is no official RAMPS 1.5 or 1.6 boards, those are vendors that are making small modifications to the existing RAMPS 1.4 boards, in this case the modifications are evident MOSFETS and Heatsink over them.

 

Not really, and I have one of the 3.2 screens sitting in my junk box, somewhere. It is okay but not great. I posted a thread a long time ago when I had the TFT28 screen and even created a set of icons for it, but others have better sets. There is no way to modify the firmware in any significant manner and the text displayed is incorrect in a few places. In order to get the spelling right you have to HEX edit the firmware. Way too much work for the little benefit you get out of the touchscreen.

 

I had one but never used it, scrapped the project altogether and went with a setup using Octopi and a Raspberry Pi instead.

 

As a follow-up here is a picture to illustrate the differences:

 

Please note, RAMPS versions beyond 1.4 are designed and built by specific vendors and were not designed by reprap and could claim to be closed source. Of course it isn't in their best interest to build it out of spec, so they are usually 100% RAMPS 1.4 compatible.

 

Yep, refer to this page:

http://reprap.org/wiki/RAMPS_1.5

Technically 1.6 and (if any) later are completely off-book.

1.5 had some specs and drawings.

 

All three of those boards have the same pinouts, 1.4, 1.5, & 1.6

 

well reading the link provided "The layout of the RAMPS 1.5 is virtually identical to that of the RAMPS 1.4. The only real difference between the two are the MOSFETs and the fuses"

There you go.
The 1.6 is not specified by RepRap so no clue on what else might have been done.

 

I am not aware of any, but there are a lot of folks. Someone else might chime in.
This is all I have read: http://reprap.org/wiki/Jy-mcu

Frankly, these days, it is easier to simply front the printer with a RaspberryPi using OctoPrint/OctoPi and be done with it.
Similar to what I did here: http://community.robo3d.com/index.p...roller-modification-for-the-beta-r1-r1.17834/

Or running it completely headless and just using HTTP to access it.

 

The R1+ isn't a 1.4 board. Its one of those vendor changed undocumented boards (Robo had them custom made) if you want to use a standard 1.4...or .5.... or .6 It will wire up the same as the thread on converting to a generic ramps thats on the forum somewhere. the R1+ pinouts/locations are slightly modified for whatever reason but nothing software wise, everything is just in a different location/labeled differently.