Add Teensy35_36_SIMPLE on LulzBot Mini2_Hibiscus and Mini2_Hibiscus_Experimental

[xxxajk]

See Configuration.h for details.

Requirements

As listed in Configuration.h:

/**
 * NOTE! This config file is a bare-bones starting point for replacing
 * the RAMBO board in the LULZBOT Mini2 (Hibiscus_Experimental)
 *
 * NOTE! The hardware for this particular config is for a LULZBOT Mini 2 Hibiscus,
 * with an CecropiaSilk_SingleExtruderAeroV2 and the TEENSY35_36_SIMPLE layout.
 * *ANY* board/cpu can be used with the same config file
 *        *providing the following conditions are met*
 * The original 24V power supply, SingleExtruderAeroV2, 2.85mm as the toolhead and
 * the Z Axis is using a belt and belt-brake remain, and that you use TMC2130 stepper drivers.
 * The same config has been used with an AVR 2560 and RAMPS 6+.
 *
 * NOTE!
 * You *WILL LOSE THE LCD DISPLAY*, this is intentional, so that you can add
 * whatever LCD you want to.
 * The largest difference overall is the resolution for this printer has been doubled.
 * The reason is because I like to sometimes print using 0.2 and 0.1mm nozzles.
 */

Description

See above.

Benefits

Allows replacement of AVR with something better.

Related Issues

None.

[thisiskeithb]

Did you start with a fresh / default config from the import-2.1.x branch? You're missing these lines for example:

Configurations/config/default/Configuration.h

Lines 23 to 24 in c27da0b

	#error "Don't build with import-2.1.x configurations!"
	#error "Use the 'bugfix...' or 'release...' configurations matching your Marlin version."

Also, Configs are also sorted by OEM -> Model, so these should be moved under /config/examples/LulzBot folder.

This also needs MarlinFirmware/Marlin#24318 to be merged first.

[xxxajk]

Yes, it's from a fresh pull, but the config isn't, I'll fix it

[xxxajk]

This config also directly fits into 2.1-bugfix

[thisiskeithb]

Bugfix strips out those errors automatically.

They need to be there in the import branches.

Please fix it.

[xxxajk]

:-) Didn't know that. Nice! and Done!

[thisiskeithb]

It is important that you start with a fresh/clean copy of import-2.1.x because you're missing these from Configuration.h:

Configurations/config/default/Configuration.h

Lines 2733 to 2736 in c27da0b

	//
	// CR-6 OEM touch screen. A DWIN display with touch.
	//
	//#define DWIN_CREALITY_TOUCHLCD

and

Configurations/config/default/Configuration.h

Lines 2763 to 2767 in c27da0b

	//
	// PanelDue touch controller by Escher3D
	// http://escher3d.com/pages/order/products/product2.php
	//
	//#define PANELDUE

You're also missing these from Configuration_adv.h:

Configurations/config/default/Configuration_adv.h

Lines 1665 to 1672 in c27da0b

	/**
	* By default the framework is responsible for the shared media I/O.
	* Enable this if you need Marlin to take care of the shared media I/O.
	* Useful if shared media isn't working properly on some boards.
	*/
	#if ENABLED(SDSUPPORT) && DISABLED(NO_SD_HOST_DRIVE)
	//#define DISKIO_HOST_DRIVE
	#endif

and

Configurations/config/default/Configuration_adv.h

Lines 3891 to 3897 in c27da0b

	/**
	* CNC Drilling Cycle - UNDER DEVELOPMENT
	*
	* Enables G81 to perform a drilling cycle.
	* Currently only supports a single cycle, no G-code chaining.
	*/
	//#define CNC_DRILLING_CYCLE

and

Configurations/config/default/Configuration_adv.h

Lines 4442 to 4443 in c27da0b

	// Continue unloading if sensor detects filament after the initial unload move
	//#define MMU_IR_UNLOAD_MOVE

[xxxajk]

I'll have to hand patch those manually, not a big deal. I'll push those changes shortly. Thanks for finding these.
I actually started with the 2.1-bugfix configs... So I don't know why they would be out of date, unless the zip file was behind.

[cp2004]

It is important that you start with a fresh/clean copy of import-2.1.x

I actually started with the 2.1-bugfix configs...

The import-2.1.x configs are different to bugfix-2.1.x

[xxxajk]

Right, Not a big deal, they're patched, updating them...

[xxxajk]

Let me know if I missed/messed up anything else, but the UUID is required, which is why it's in a deeply nested directory specifically naming the machine.

[thisiskeithb]

The import-2.1.x configs are different to bugfix-2.1.x

@cp2004 That is correct and intentional.

Through the magic of scripting/deployment, pending features & “Do not build with…” lines are removed when changes are deployed to bugfix.

[thisiskeithb]

but the UUID is required, which is why it's in a deeply nested directory specifically naming the machine

This still needs to be moved to the main Lulzbot folder.

[xxxajk]

Is there one? Problem is that it's no longer really a lulzbot machine... it's Teensy based now, just uses the lulzbot frame, and none of the electronics except for the wiring harness, and steppers/sensors.

[xxxajk]

Oh yeah, and worse, it was a prototype, never released! Notice that I disabled any use of the display too, so a regular user is going to be very confused as to why it no longer displays anything... the driver for the display must be heavily patched, because of the software spi implementation trying to move data at 30MHz on this particular board... and I'm not going to be using that anyway.

[thisiskeithb]

Is there one?

Yes: https://github.com/MarlinFirmware/Configurations/tree/import-2.1.x/config/examples/LulzBot/

Problem is that it's no longer really a lulzbot machine...

See the Ender-3 config folder (or any other Creality config) where it has the most configs/upgrades: https://github.com/MarlinFirmware/Configurations/tree/import-2.1.x/config/examples/Creality/Ender-3

The standard patten is OEM -> Model -> Boards/Upgrades

It would also help to add a README.md in the same folder as your new configs explaining the differences over a stock machine so we aren't stuck trying to troubleshoot it if/when something doesn't work down the road.

[thisiskeithb]

Oh yeah, and worse, it was a prototype, never released!

So should this config really be added then or is this just a one-off for your personal use?

[xxxajk]

Good idea, I'll add the readme, I'm sure others out there who want to upgrade easily DIY.
Currently I have the only machine with the hardware replaced, however, there's no real examples at all for Teensy, and that ends up making this modification difficult for the average user. they've got no place to start! TAZ-4 != the Mini2.
I'm sure many others have tried to replace the board, only to be disappointed, and this opens up the avenue for the replacement. I'll also at some point have a board offering that allows this modification anyway, posted on github...

So... the TLDR is:
Basically this isn't an "approved modification" and isn't anything that will ever be commercially supplied. The config does give others a starting point, and increases the resolution on the X/Y/Z axis over the stock old firmware in any case. there isn't one single Teensy anything example, so my goal here is to give a starting point for others.

[thisiskeithb]

TAZ-4 != the Mini2.

I never said it was. I am saying that you need to move your config to the Lulzbot folder.

[xxxajk]

That's fine, but won't it cause confusion? Are there any other taz-4's that have the guts torn out and replaced?
I'm guessing not... It's already 32bit :-) As long as you think it won't cause owners of the Mini2 any confusion as to why it doesn't work on the stock RAMBO or einsy retro board, I'm fine with the move... and No, I can't do the mods for that board, since the whole reason I'm replacing it is that the AVR is too slow for double resolution, and the RAMBO board fried, and I can't justify the cost of replacment, especially since I can build my own hardware...

[xxxajk]

Hopefully this won't cause any confusion, I'll put a README.md for Teensy (and name it Teensy boards) so that people can at least locate an example for the board if you think that would be a good idea.

[thinkyhead]

@xxxajk — This one still doesn't build because there's no BOARD_TEENSY35_36_SIMPLE existing. Where can we acquire the pins definition for this board, or should we use one of the existing board definitions?