Ender 3 V3 SE & Nebula Smart Pad: Better documentation needed!

[Mikey_Mike_Mik]

G’day!

You may remember me from threads like “Ender-3 V3 SE: config settings to roll our own firmware please”, where some cleverer people than me have modded Marlin to print on the SE to 300 degress, & to play well with Octoprint.

Now, I’m trying to get the same thing happening with the E3V3SE & the Nebula Smart Kit.

There’s so much to love about the kit, but so much to HATE as well due to the lack of information … so I’m trying to collate all the good info I’ve been able to use to get where I am so far:

Ender 3 V3 SE: added Ceramic hot end, X-axis Rail, Z-axis stabilisation, Nebula Smart Kit - Pad, Camera, vibration sensor.

Nebula Pad: Updated to latest firmware, rooted:
GitHub - koen01/nebula_firmware: create custom nebula pad (retail version) firmware

Using CLI (GitHub - Guilouz/Creality-Helper-Script: Helper Script for Creality K1 / KE / Ender-3 V3 Series), updates script, Fluidd, Mainsail, Moonraker, et al …

https://www.reddit.com/r/Ender3V3SE/comments/1hp8omt/rooted_nebula_pad_firmware_11027/

https://www.reddit.com/r/Ender3V3SE/comments/1f0zx6c/nebula_pad_issues_fix_for_ender_3_v3_se/

Also using Tailscale so I don’t have to leave a port open to remote access.

Issues:

• Does the vibration sensor need to be attached at all times, or (as I suspect) only while testing?

• The Nebula Pad will not display the progress of a job initiated via Klipper/Fluidd/Mainsail - no progress bar, no percent.
•• Hint: If you pause the job vial Fluidd, then restart - the % & time magically gets updated on the Nebula interface (and the previously non-responsive Creality Cloud app).

• What are all the ports on the Nebula for (including the hidden internal USB port), and can they be used for other purposes?

• The Vibration sensor uses two USB ports (USB-C & USB-A).
•• Is one for (additional) power and the other for data?

• When jobs end - the Nebula pad will often throw an error or hang, requiring a reboot. Any settings found to remove this?
•• Note: I have a workaround where I can remotely turn the plug in the powerboard off then back on again - performing a full reboot (the Klipper based restarts don’t seem to suffice).

Yes - I will add screen shots of the errors (when I get home - having lunch at work now), and throw more deets, but if you have answers, or point me in the right direction - we’ll see what we can come up with!

[Radical_Data]

@Mikey_Mike_Mik

You may remember me from threads like

Hello Mikey_Mike_Mik,

Sure do remember you

So, the main thing is … once you get the Nebula pad sorted, are you going after the Sonic pad .

Asking for a friend

Cheers.

[Mikey_Mike_Mik]

“Sonic” sounds too much like a hedgehog to me …

I’d rather try a Pie (I like pie!) with an external display - or maybe an old Android phone (I have a few Sammy A12’s with knackered microphones that would be perfect for the job!).

AFAIK, Nebula & Sonic are fruit from the same tree … what works for one should be relatively applicable for the other.

[Radical_Data]

Cheers Mikey_Mike_Mik,

I will let him know

[Bonfireman]

@Mikey_Mike_Mik

Does the vibration sensor need to be attached at all times, or (as I suspect) only while testing?

Only used in the testing/setup, not used after that so can be removed. You say it uses 2 USB ports, this is different than the Sonic Pad which uses a round serial connector instead, same sensor, different cable which has caught a few people out. I think the internal port is just for flashing.

[Mikey_Mike_Mik]

BTW: Didn’t you kill my brother?

Ullo John, got a new motor?

[Bonfireman]

He hasn’t updated it to include a Qidi Q1Pro…tardy Ozzie probably throwing a couple of shrimp on the barby. or fending off killer spiders and snakes.

[Radical_Data]

@Bonfireman

He hasn’t updated it to include a Qidi Q1Pro

Have now …

And Mikey_Mike_Mik, it’s a Mazda 3 about 11 years old.

[TechieZebra]

@Mikey_Mike_Mik

• Does the vibration sensor need to be attached at all times, or (as I suspect) only while testing?

No, only when testing it’s required

• The Nebula Pad will not display the progress of a job initiated via Klipper/Fluidd/Mainsail - no progress bar, no percent.
•• Hint: If you pause the job vial Fluidd, then restart - the % & time magically gets updated on the Nebula interface (and the previously non-responsive Creality Cloud app).

I’ve had the same experience. I’m sure that it worked with the root .23 firmware, but that firmware wouldn’t show the printing image

• What are all the ports on the Nebula for (including the hidden internal USB port), and can they be used for other purposes?

• The Vibration sensor uses two USB ports (USB-C & USB-A).
•• Is one for (additional) power and the other for data?

Yes, USB-C is for serial data, USB-A for power.

• When jobs end - the Nebula pad will often throw an error or hang, requiring a reboot. Any settings found to remove this?
•• Note: I have a workaround where I can remotely turn the plug in the powerboard off then back on again - performing a full reboot (the Klipper based restarts don’t seem to suffice).

I haven’t had this problem. When a print finishes, the Nebula pad shows a “Print Job” finished with an “Finish” button. I can then start another print without issues.