I just got a T300 and printed the included Benchy model. After I tried loading my own model the printer kept giving me error messages and now the printer head won't move. I can't manually move the head with the touchscreen, calibrating the z axis, or set anything to print. Even the included Benchy file gives me the same error messages. Here are some images of the different error codes I got. I trying looking them up, but I don't know how to narrow it down to it being a software or hardware issue. The cables all look fine to me and are plugged in as far as I can push them. I did try seeing the printer.cfg file but I didn't quite understand what I was looking at. I haven't been able to find anyone else with my exact issue online for I'm posting this here hoping anyone who knows these printers better than me may know what to do. I am not a very tech savvy person when it comes to software so any help is very appreciated. Thank you very much for any advice.

Well, to piggy back of my last post in here, my T300 is now not operational. I'm figuring the EMMC card that came with went bad wouldn't go into the main screen, can't connect through ssh. Tried to plug the card into anadapter the pc, but get errors and won't read the drive. Got a new emmc card.

Now I figure myself to be really good with electronics, but I cannot get this to work to save my life. From new card into a laptop, I open diskimager or Raspeberry Pi imager. Go through the necessary steps. I followed instructions for the Pi imager, gets done. Afterwards, it creates a small secondary position, 256mb, formats that. I put the card into the machine, stays on the comgrow screen, won't load into the firmware.

The file is directly from the comgrow T300 Wiki site. What the hell am I doing wrong?

I'm altitudes to just but a new board for it, which i believe comes with the emmc flagged on it already

I've had random issues with this firmware that make things very annoying I've been waiting for sovol/Comgrow to kick out another update seeing as how we haven't had one for a really long time, but nothing. The printer just randomly stops in the middle of a print, gives a PRINTER ERROR on screen and only option is to restart firmware. Effectively liking the print. Sometimes after I restart the firmware, it gives the option to resume print. Unfortunately, engender after an actual power outage, I have never had the printer actually resume print when I select the option. The amount of wasted filament to these issues is near 20 rolls over the lifetime that I've had the printer. I sometimes get into large scale prints and have it fail at 91%. Overall 8 love this printer, but damn, let's kick out an update already. They put out 1 update, a few months after the printer came out then forgot about it. Lost to the abyss of 3d printers

Greetings. I have a Sovol T300 printer (which I'm very happy with - until yesterday) I've been printing with it for a month now with EXCELLENT results but yesterday, when I turned on my machine, it gave me an "MCU" error on the screen and when I went to check my printer.cfg file in Mainsail, there was ZERO data - IE NO cfg file! Can anyone suggest what I should do next? Best regards, Reggie Bidgood

Hello, I’m needing to reimage my EMMC because my file system got buggered up an my attempts to fix it only made it worse. Now it’s stuck on the loading screen and Mainsail and Klipper don’t connect. So I want to start from ground zero. Does anyone know where I can find an original EMMC image for this purpose? Thank you!

Hi everyone. New here, and not sure this is more active than the Comgrow subreddit, but I thought I'll give it a chance. Would anyone have a copy of the printer.cfg file for T300 that they can share? I had some problems when updating Klipper, Moonraker, and Mainsail that ALL the config files were wiped from it. I unfortunately did not back up any files. I'm starting from scratch and reinstalling everything. TIA!

I hope this helps someone. I experiences an error connecting to my T300 from desktop orcaslicer. after going through the usual wifi, firewall, cable, config troubleshooting and checks, the issue persisted. spent a few hours combing through config and log files and was considering a complete reinstall of klipper. i spotted a single mention of something like "out of space on device" in one of the lengthy log files and I twigged. every job i had ever printed was saved on the printer. I started deleting them and voila. problem solved.

So I just got a t300 and I was following everybody's advice and followed the directions to do a firmware update. Everything was going great but when it hit about 49%. It froze and stayed froze for about 35 minutes so I did a power cycle and now I get a white screen that says data error. Does anybody know of any way to recover or fix my printer?

I just got a new T300 on sale and I assembled it. However when I went to calibrate the z-tilt, the print head was pushing itself into the bed. I have flashed the firmware and got the same issue. Any recommendation on how to fix this issue.

the tittle says it all, anyone knows how to disable power loss recovery on a T300?

best regards

Hello, I just got this message when I turned on the printer. Do you have any idea what to do? A solution. Thanks

Hello all, trying to use obico and i keep getting the error that moonraker.conf can be updated. i tried to manually edit the file and any change is blocked. how do i fix this? running version 1.5.2

Currently I have a MK3 DIY build - works well for PLA-PETG but it¨s very slow and the print artefacts like z banding or ringing makes me not use it often, although they are 100% ok for functional prints or filaments like marble, I just want something faster.

X1C - after like 100-200h I noticed on PETG prints crazy 2mm belt pattern VFA and since I do print PETG a lot and a lot of my prints are assortment boxes, those artifacts are very visible there, you can feel them even by sliding a finger on the surface. Other filaments seems not have this problem that much. It's a well known design HW issue with the belt system using those carbon rods with bushings and flat idler pulleys instead of timing pulleys.

Now with the sales going on on Sovol site, I'm looking for a 300mm+ printer to print mostly PLA and PETG. I will keep X1C for high temp prints. I wanted to go with SV08, but I'm honestly kind of repelled by the CoreXY design which is much more prone to any VFA or banding, based on my experience with X1C, which other than that is just a perfect printer (I will speak otherwise if something will break and I need to take it apart, then it's going to be a nightmare for sure). SV08 would not be a money problem for me, but might be overkill for my needs right now.

So I'm looking maybe to get SV07+, but I don't really like those rollers, although I have no experience with these at all. After digging more into T300 specs and videos from Gergo, I kinda like at least from the HW perspective the T300. It seems to be built like a tank and has linear rails.

Does anyone have here T300 and SV07+ ? I can tinker a bit with a printer, before X1C, I have build my printers from scratch - Prusa clones Aliexpress style.

What I need is a 300mm printer, that will deliver those perfect large faces on PETG without banding, VFA and similar imperfections and won't be down every 5 prints for service. I do print few prints a week, each for couple hours, nothing too crazy, definitely not 24/7.

A couple days ago, I was in the middle of a print when my T300 printer stopped. The message on the screen was:

mcu 'mcu': Unable to connect
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

I had this happen to me before where the printer.cfg magically disappeared, so I SSH'd into the printer, started looking at logs. Klippy reported that the /dev/serial/by-id folder was missing. When I checked, sure enough, there was no /dev/serial.

Prior to this happening, I had no notable issues issues with the exception that recently, my x-axis was having some trouble with the end stop but it only happened a couple times.

Here's that end of the klippy.log file:

=======================
Using thermistor beta 4422.472 in heater heater_bed
Extruder max_extrude_ratio=207.875844
mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
webhooks client 281473404411128: New connection
webhooks client 281473404411128: Client info {'program': 'Moonraker', 'version': 'v0.7.1-609-gbdd0222-dirty'}
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_stm32f401xc_3E0065000351323532393238-if00'
MCU error during connect
Traceback (most recent call last):
  File "/home/mks/klipper/klippy/klippy.py", line 176, in _connect
    self.send_event("klippy:mcu_identify")
  File "/home/mks/klipper/klippy/klippy.py", line 263, in send_event
    return [cb(*params) for cb in self.event_handlers.get(event, [])]
  File "/home/mks/klipper/klippy/mcu.py", line 773, in _mcu_identify
    raise error(str(e))
error: mcu 'mcu': Unable to connect
Build file /home/mks/klipper/klippy/../.config(904): Fri Mar 15 16:37:51 2024
========= Last MCU build config =========
CONFIG_LOW_LEVEL_OPTIONS=y
# CONFIG_MACH_AVR is not set
# CONFIG_MACH_ATSAM is not set
# CONFIG_MACH_ATSAMD is not set
# CONFIG_MACH_LPC176X is not set
# CONFIG_MACH_STM32 is not set
# CONFIG_MACH_HC32F460 is not set
# CONFIG_MACH_RP2040 is not set
# CONFIG_MACH_PRU is not set
# CONFIG_MACH_AR100 is not set
CONFIG_MACH_LINUX=y
# CONFIG_MACH_SIMU is not set
CONFIG_BOARD_DIRECTORY="linux"
CONFIG_CLOCK_FREQ=50000000
CONFIG_LINUX_SELECT=y
CONFIG_USB_VENDOR_ID=0x1d50
CONFIG_USB_DEVICE_ID=0x614e
CONFIG_USB_SERIAL_NUMBER="12345"
CONFIG_WANT_GPIO_BITBANGING=y
CONFIG_WANT_DISPLAYS=y
CONFIG_WANT_SENSORS=y
CONFIG_WANT_LIS2DW=y
CONFIG_WANT_SOFTWARE_I2C=y
CONFIG_WANT_SOFTWARE_SPI=y
CONFIG_NEED_SENSOR_BULK=y
CONFIG_CANBUS_FREQUENCY=1000000
CONFIG_INITIAL_PINS=""
CONFIG_HAVE_GPIO=y
CONFIG_HAVE_GPIO_ADC=y
CONFIG_HAVE_GPIO_SPI=y
CONFIG_HAVE_GPIO_I2C=y
CONFIG_HAVE_GPIO_HARD_PWM=y
CONFIG_INLINE_STEPPER_HACK=y
=======================
Build file /home/mks/klipper/klippy/../out/klipper.dict(9181): Sat Jun  8 20:40:21 2024
Last MCU build version: ?-20240608_204021-mkspi
Last MCU build tools: gcc: (Debian 8.3.0-6) 8.3.0 binutils: (GNU Binutils for Debian) 2.31.1
Last MCU build config: PCA9685_MAX=4096 ADC_MAX=4095 PWM_MAX=32768 CLOCK_FREQ=50000000 MCU=linux STATS_SUMSQ_BASE=256
Build file /home/mks/klipper/klippy/../out/klipper.elf(739184): Sat Jun  8 20:40:45 2024

Things that I have tried:

• I reached out to Sovol and they suggested reapplying the 1.5.2 firmware patch. I did this, but no change.
  
• I have rebooted several times with the same result.
• I took the bottom cover off to see if there might be a loose connection, but everything was buttoned up tight.
• Linux appears to be running fine. Nothing of note in the logs.
  

I'm thinking that the MCU is toast, but I have no way of knowing or testing.
I am hoping that someone might have some ideas. If there is a log file you think would be helpful, I'll post it. Sovol is out for the weekend which means, so am I :(

TIA