Ender-3 Max Neo &Nebula Smart Kit

Fiete_Cux · September 14, 2024, 5:49am

Good morning
I have the ender-3 max neo.
I bought the Nebula Smart Kit and am trying to flash it together with the printer.
There is a firmware for compatibility with the
Max Neo and the Nebula Kit.

(NEBULA_ota_img_V1.1.0.27.img)
1.Is this for the pad? And how do I flash this .img file?

2.Which firmware do I need to use for the printer?

This is a bit confusing if it is not described properly. Can anyone help me with this?

Firmeware for Nebula Kit and Max Neo

Thanks for any tips.

Glenn_De_Backer · September 14, 2024, 10:34am

Same problem, so I’m going to follow along

Grimfoo · September 21, 2024, 6:44pm

So i took the flash drive and removed everything from it and put just the NEBULA_ota_img_V1.1.0.27.img file on it

It recognized the file and updated the printer to show the Ender 3 max Neo as a printer selection. But now im running into a system error where it doesnt detect the 3 axis. This has turned into a headache.

Fiete_Cux · September 21, 2024, 9:13pm

Hello,
I managed to get the Ender-3 Max Neo to work with the Nebula Smart Kit.
You don’t just have to flash the pad so that

the Max Neo is there, you also have to flash the printer.
I did that.

Flash the pad. The printer must be off.
After selecting Max Neo in the pad
you will be prompted to flash the printer (Klipper).
Insert the SD card into the printer and switch it on.
After that comes the setup, the self-test and the calibration
of the sensor. The print head and the
heated bed must be calibrated with the sensor.
Now everything works perfectly.

Tomorrow I can explain step by step which firmware to use for the printer and how to calibrate the G sensor and which Creality Slicer version works to print from there via WiFi and which settings have to be managed. The current slicer does not have the Max Neo in it. Only the K1 models.

Tarl72 · October 6, 2024, 9:40pm

Hi Fiete_Cux,
Quick question, which motherboard are you using? I’ve got an Ender-3 Max Neo with a CR probe and I upgraded the motherboard to a V4.2.7 (broke the old one when I removed it, so can’t replace it. GGGrrrrrrr) and I can’t get the Nebula to work. I can select a E3MN with a CR probe, but only with a 4.2.2 motherboard. I then get as far as the home calibration wizard and get a key:2022 error message. Any suggestions? I know that all the wires are properly seated (first thing I checked!), and I know that the x, y and z motors are working (when I swapped the screen back to the original one and re-flashed the firmware to remove the Nebula screen everything works perfectly), so I’m thinking it’s a firmware issue (not talking to the 4.2.7 motherboard correctly or they changed the pin layout).
Many thanks in advance,
Tarl (most people call me ‘TC’)

Tarl72 · October 6, 2024, 9:43pm

Hi,
Are you are using the new V4.2.7 motherboard? If so, I’m having the same issue. If you have any advice on how I can fix it I’d be very grateful to hear about it.
Tarl.

Fiete_Cux · October 7, 2024, 6:12am

Hello Tarl,

First of all I have a few questions. I had the same problem at the beginning.
I’ve had the printer for 2 years and still have the original mainboard. So 4.2.2. But that doesn’t matter, because the firmware runs with 4.2.2 and 4.2.7

Are you using the complete Smart Kit with camera and G-sensor?
Which printer firmware are you using?
Does the G-sensor only test the extruder X-axis during the test run?

Tarl72 · October 7, 2024, 11:01am

Hi there,
Yes, I have the full Nebula kit (screen, G-sensor and camera). I have updated the firmware on the camera without a problem. As for the firmware; Currently on the printer is the latest version for the V4.2.7 motherboard with a CR Sensor and Filament sensor (Ender3-Max-Neo-HW4.2.7-SW1.4.1_G_CF.bin) from the Creality website. On the Nebula I tried the NEBULA_ota_img_V1.1…0.27.img to install the Max Neo printers into the Nebula, but the only options are for the 4.2.2 motherboards. As for the G-sensor tests, I don’t get that far. I get the key:2022 unknown exception error message and I have to restart. If I move on to the next screen (to set the z-axis) I can set it to whatever I like, but the head doesn’t move.

Fiete_Cux · October 7, 2024, 11:59am

OK, the firmware for the pad is correct.
But you can’t use the original Marlin V4.2.7 for the printer.
Nebula works with Klipper, so you have to use the printer firmware from Nebula.
It is compatible with the 4.2.7 boards.
See my picture with red marking.

And don’t start the firmware until the Nebula pad asks you to after you select the printer in the pad.

Tarl72 · October 7, 2024, 1:32pm

Well, unfortunately, that didn’t work at all. When I click the first E3MN I get the same Key:2022 error message when calibrating the auto-home. If I select the second one I get an almost instant System Error Try Restarting. Anything else I can try? I’ll make a quick video and upload the link in a minute so you can see what I do.

Tarl72 · October 7, 2024, 1:46pm

Here’s the youtube link. Entitled ‘7-10-24 Nebula start sequence’ (about two and a half minutes long)

Tarl72 · October 7, 2024, 2:03pm

Okay, here’s something to confuse matters! I just selected the Ender-3 with CR-Touch STM32F103 V4.2.7 (just to see if it would work), and I sailed straight through the homing issue, the x, y and z axis all work perfectly. The only problem, obviously, is that I’ve not got the ability to use all of my bed.

Fiete_Cux · October 7, 2024, 3:04pm

That’s strange. You enter the size of the bed in the slicer when you select the max neo. Try it when you’re ready.
I’ll write something about the video again. It’ll take a while

Tarl72 · October 7, 2024, 4:56pm

Right, good news first. I can control the printer, camera, temps and fans through the Nebula itself, via the app(ish) the app seems a bit clunky and through the Creality Print (BOTH V5.1 and V4.3.8.7058).

Now the not so good news;

I’ve used the app and the Creality Printer to change the printer to my E3MN but the Nebula itself does not take a blind bit of notice (it still thinks it’s a standard Ender-3) and will only print within that size bed.
When I tried printing outside of the 220mm size (I tried sending a small print job via the cloud) it fails with the unknown issue message as soon as the extruder reaches the limit of the bed it thinks it has.
Using the Creality Print 5.1, I was able to connect easily enough but can’t move the extruder beyond the 230mm limits.
In all the slicers I have I have (where possible) selected the Ender-3 Max Neo. This is not possible in the Creality Print 5.1, so I connected the Nebula Pad and added the IP address.
Lastly, 5) You mentioned that I could enter the bed size in the slicer? a) which slicer are you using? and b) How do I do that so it will apply when I print something? I’m playing with 5.1 at the moment, and have tried saying that the E3 has a larger bed to print on, so this might solve this issue!! (I hope!!!) NOPE!!

I’m really sorry for being such a pain, and many thanks for all your help.
TC

Fiete_Cux · October 7, 2024, 7:41pm

I use the
Creality Print V4.3.8.7062
the current versions did not have the E3MN in the program.

I also still use the Creality Slicer 4.8.2 from time to time, old habits.

It’s fine, you’re not disturbing me. But it would be nice if everything worked immediately as you want it to. It just doesn’t always work. But at least it works for you. Even if it’s not 100 percent

Fiete_Cux · October 7, 2024, 7:48pm

You can change it in the slicer. Where in Creality Print. I’ll have to look tomorrow. I haven’t needed it yet.