-
-
Notifications
You must be signed in to change notification settings - Fork 7
Home
Before attempting to Upgrade to OpenOrangeStrom, get sure you don't need the printer immediately! Some things might not work out and need a bit of tinkering. This is still a work in progress! The repository this page is referring to is the one of Galloant, where an attempt at fixing some bugs has been made, but is still in evaluation if it's working or not. If you went through the installation process described here and you find your machine to be working, please let us know so we can pull the repository fixes into the mainline.
For now, neither Wifi nor the Elegoo screen is working with OpenOrangeStorm!
If you need help, hop over to Discord and enable the giga-development channel. Before you go there and ask questions, try to solve the issue yourself. That is the best way to learn.
It might be a good idea to get your terminology right, which for we suggest to visit the Terminology page first. Not only will this help you understand better what you're doing and follow the instructions accurately, but it also helps you when asking for help.
- Prerequisites
- Flashing OpenOrangeStorm
- Initial Configurations & Updates
- Setup a CAN0 interface
- Flashing / Updating Klipper MCUs
- Post-Installation Setup
- Importing OrcaSlicer Profiles
- Printer Calibration & Levelling
- Safely Powering Off your Printer
- Keeping your Printer Updated
- How to revert back to Original Elegoo eMMC image
- Acquire an eMMC to USB Adapter: MKS USB3 Adapter - AliExpress or Adapter with spare eMMC - AliExpress / 32GB version (without adapter).
- Back up your printer.cfg to a file off your printer.
- Power off the printer and access the Mainboard by removing all silver screws securing the underside access panel.
- Remove the two screws securing the eMMC module and safely lift it free.
- Wifi is not working as for now and you need to connect the printer via Ethernet
Download the latest OpenOrangeStrom Image.
- Linux:
- Use balenaEtcher or dd with;
xz -dc -T0 file.img.xz | sudo dd of=/dev/sdX bs=4M conv=fsync status=progress
- MacOS:
- Use balenaEtcher
- Windows:
Note If the eMMC is not detected, ensure the chip is the correct way round in the adapter.
- Reinsert the eMMC into the mainboard.
- If your printer now features an externally accessible microSD slot, reattach the access panel to the printer (Important for cooling).
- Power on the printer
- NOTE: Your touchscreen will continue to hang on loading, this is normal please continue with the installation.
- Access your printer's terminal console (via SSH or Serial)
-
Connect the printer via Ethernet to your router / LAN switch (NOT directly to a PC)
-
Determine the new IP of your printer (two options below):
a. Use your router's web interface > DHCP lease table.
b. Or use AngryIP (Settings Cog>Ports> Clearport selectionentries, type7125,Ok, thenStart) -
Connect via SSH using:
ssh mks@YOUR-PRINTERS-IP. Password:makerbase.
-
Connect your computer to the printer's USB-C port (
1500000 BaudSerial terminal).
a.Windowsusers can use PuTTY. Here is a useful quick connection Guide.
b.Linuxusers can usescreenfor terminal access (linux commands below).lsusbFind the relevant ttyACM / ttyUSB device then paste yours into the command below.
screen /dev/tty* 1500000To exit screen, press
Ctrl + Afollowed byK, then confirm withY. -
Once connected login using: User:
mks. Password:makerbase.
- To configure WiFi run the following command.
sudo nmtui - Select
Edit a Connection, and press enter. - Right arrow to
<Add>, and press enter. - Down arrow to
Wi-Fi, and press enter. - Give the profile a name, like
HomeorWork, then skip down to theSSID(this is your network name). - At Security, choose
WPA & WPA2 Personal, then add your password. (this security should be correct for most setups) - Leave the IPv4 and IPv6 on automatic, and select
Ok. - Select
Backand thenQuit. - Once connected, consider logging into your WiFi router and enabling a
static IPaddress for your printer. This will prevent the IP address from changing over time. (usually within DHCP settings).
- Set the correct timezone through Armbian configuration:
sudo armbian-config - Navigate to
Personal>Timezoneto set your zone. - Exit the menu then reboot your printer with;
sudo reboot
- Execute the Kiauh script (you may have to run the command again after it updates itself):
~/kiauh/kiauh.sh - Select menu
Option 2, update all programs. It will take a while to check for updates on the first boot. - Type (
a) for[Update all]when prompted by####### Perform action:, then exit kiauh once complete.
-
Copy and paste the following command into the terminal
cd ~/OpenOrangeStorm/ && git remote set-url origin https://github.com/Galloant/OpenOrangeStorm.git && git fetch --all && git reset --hard origin/fixes && git clean -fdFollowed by
chmod -R 777 ~/OpenOrangeStorm ~/OpenOrangeStorm/OpenOrangeStorm.sh -
Select
Option (1)(Install/Update OpenOrangeStormprinter.cfg)
The first run will ask you to select your printer model it then installs the relevantprinter.cfg -
Select
Option (2)(Install/Update KAMP/Moonraker/fluiddGUI confs) then selectOption 1) All -
Quit
openorangestormand run;sudo reboot
sudo nano /etc/network/interfaces.d/can0
Copy and paste this configuration:
allow-hotplug can0
iface can0 can static
bitrate 1000000
up ip link set $IFACE txqueuelen 128
Press CTRL+X to exit, Y to confirm and ENTER to save. Reboot your system with sudo reboot now.
After reboot, check if CAN0 state is up and running:
ip -details -statistics link show can0
- After the reboot run the command
openorangestorm
- Select Menu Option
4) Update MCU & Virtual MCU Firmwareto update MCUs - Select Option 1
STM32 - Follow the steps in the terminal
- If successful, you need to restart the machine (top right
...>Host>Shutdown> wait 20 seconds > power off > wait 20 seconds > power on) and then you can do the first 3 steps for the RP2040
If it doesn't work, you have two options:
- Go on with the guide as there are other ways to flash the firmware
- Go to the Discord server and ping Gallo in the #giga-development channel. He wrote the script for the automatic update, but had limited possibilities to try it on a board which was freshly upgraded to OpenOrangeStorm and would need to do some tests. He's on CET (Central European Time), so he might not be available immediately. If you have time to wait, it would be highly appriciated.
**only for the STM32! For the RP2040 visit this page **
- If the automatic update fails, the firmware file be put in the configuration folder
- Visit:
http://your_printer_ip/#/configure - Click the
Firmwarefolder in theConfiguration Filescolumn (left) - Right-click and Download
ZNP-Giga.bin - Copy both files to a
FAT32formattedmicroSDcard - Safely eject your
microSDcard (don't insert into the printer just yet) - Continue with the script (
y) - Shutdown the host (top right
...>Host>Shutdown) - (
Wait ~20s) It is now safe to power off the printer at the power/mains switch - Insert the
microSDcard once the printer is fully powered down - Power on the printer, then check the MCU versions in Fluidd's system tab (
v0.12.x). - You can now
removethemicroSDfrom the printer -
Note: One of the
.binfiles on the microSD will be renamed to.CURif the update was successful.
Sidenote You can check if your MCUs are connected via CAN with this command:
cd ~/katapult/scripts && python3 flash_can.py -i can0 -q
but only after you have installed Katapult. Katapult will be installed automatically when running the firmware update script. The output should be something like this:
Resetting all bootloader node IDs...
Checking for Katapult nodes...
Detected UUID: 06727e55c686, Application: Klipper
Detected UUID: 4c61f6fc8b08, Application: Klipper
Query Complete
If nothing works If the update of the MCUs fails, you will need to update them manually. This page will guide you through it.
After having finished the firmware update process, restart the machine as before.
After that, run the command:
cd ~/katapult/scripts && python3 flash_can.py -i can0 -q
The output should be similar as follows:
Resetting all bootloader node IDs...
Checking for Katapult nodes...
Detected UUID: 06727e55c686, Application: Klipper
Detected UUID: 4c61f6fc8b08, Application: Klipper
Query Complete
- The first UUID is the mcu UUID (STM32)
- The second UUID is the mcu1 (RP2040 / printhead)
- Replace the UUIDs in your
printer.cfgwith the once you've got like here:
[mcu]
canbus_uuid: cb43a94be3aa
[mcu mcu1]
canbus_uuid: 7c22a34d7700
- Run the following command:
openorangestorm
- Select
7) * Advanced Options Menu * - Then
8) Probe Timeout Fix (Only for Orange Storm Giga)
Find details about why and what here
Configure it via Fluidd or Mainsail
- Run the following command:
openorangestorm - Select
7) * Advanced Options Menu * - Then
3) Resize Active Armbian Partition - for eMMC > 8GB
-
fluiddis the default web interface for this project, accessible at http://your_printer_ip/ - That being said,
mainsailcomes pre-installed - Mainsail access via http://my.mainsail.xyz/
- Enter your printer
IP address(or hostname) in theHostnamefield
- Download & install the latest Official Release OrcaSlicer
- Configure your
Printer Modelin Orca with0.4mm nozzleandPLAdefault presets -
Check/ Confirm Bambu Network Engine install - Download the latest OrcaSlicer Profiles (ensure you click the icon for
rawfile download) - In OrcaSlicer click [
File>Import>Import Configs...] - Within each of the three dropdown menus on the left for
Printer,Filament&Processselect the relevantOpenNept4uneUser preset (note not to select PETG unless required) - Click the
WiFi symbolto the right of thePrinterpreset dropdown, and enter your printer's IP to enable network .gcode upload. - Your printer's
fluiddinterface will now be accessible via OrcaSlicerDevicetab.
- Save any config changes within the Fluidd interface to avoid losing them.
- To safely Power-off your printer, either use the touchscreen to shutdown the host or use the Fluidd interface:
Navigate to the top-right menu, selectHost, thenShutdown.
Wait until the Green LEDs (visible under the printer) turn off
Then you can power off the machine at the mains power switch.
This ensures that changes stored in RAM are correctly written to the eMMC, preventing data loss.
Visit this page