sand escarp
My old SD card for mainsail started to have issues with corruption and wouldn't update
I've finally backed up the old printer.cfg, flashed a new SD card with mainsailos using raspberry pi imager, cut the 5v line on the micro SD serial cable, and uploaded the old printer.cfg (wil attach below)
I assume there will be more steps to get back online, and I assume with pi 3-4 upgrade it will have to do with the "serial-by-id" line?
All these settings were tuned by hand because I have an oddball undocumented creality Ender 3 Neo V1
Which guides and steps should I take here to return to sanity?
tulip dragonBOT
Ahoi @sand escarp!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message
sand escarp
I feel that the printer.cfg / printer.txt I provided is sufficient under the understanding of a fresh install from raspberry pi imager
uncut topaz
I feel that the printer.cfg / printer.txt I provided is sufficient under the und...
Pls Upload a log file!
sand escarp
Pls Upload a log file!
uncut topaz
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:'
this serial path should not change, with a new pi. so it looks like the printer is not connected right now.
sand escarp
So when I was connected via ssh, I queried /dev/serial/by-id/* and it gave that result (unsure if that changes with connection)
And in mainsail UI I have the devices below
So is my pi seeing my printer serial connection, but not able to connect klipper?
The printer is plugged in, and turned on
The 5v line has been trimmed to prevent back feed power
sand escarp
```
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/se...
pi@mainsailos:~ $ ls /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
cat broke it, ls I don't think is the command I want
I am not good at probing serial
by all means and sights I don't know what information I need to look at or share,
is this still an issue where my connection between my pi and my printer could be the cause? I need help with some input
uncut topaz
cat broke it, ls I don't think is the command I want
you cannot "cat" the serial port itself....
this path is the path to the serial port from your pi to the mcu (printer board). ls is the right comand to check it
sand escarp
you cannot "cat" the serial port itself....
That's a fair point, it was interesting to see the corruption that came out
uncut topaz
ls -l /dev/serial/by-id/*
ls -l
Yes that's what I was attempting to do
uncut topaz
this should list all existing seriel ports "by id" (there is an other command for "by path", which you need, if you have 2 same ids)
uncut topaz
So when I was connected via ssh, I queried ``/dev/serial/by-id/*`` and it gave t...
pls upload a new klippy.log
this looks wrong, when klipper doesnt see it, but it is here. maybe it was just an old log
uncut topaz
ok. this is now a complete different error message:
Traceback (most recent call last):
File "/home/pi/klipper/klippy/klippy.py", line 131, in _connect
self.send_event("klippy:mcu_identify")
File "/home/pi/klipper/klippy/klippy.py", line 223, in send_event
return [cb(*params) for cb in self.event_handlers.get(event, [])]
File "/home/pi/klipper/klippy/klippy.py", line 223, in <listcomp>
return [cb(*params) for cb in self.event_handlers.get(event, [])]
File "/home/pi/klipper/klippy/mcu.py", line 799, in _mcu_identify
raise error(str(e))
mcu.error: mcu 'mcu': Unable to connect
so it could find the the serial path, but there is no answer on the serial bus
so you just changed the rpi and the board was already flashed?
sand escarp
so you just changed the rpi and the board was already flashed?
I moved from pi 3 to pi 4, replaced SD card, flashed new SD card
The only thing that stayed the same were the printer and the printer.cfg
Could it have to do with the flash of my mainboard?
sand escarp
so you just changed the rpi and the board was already flashed?
I haven't reflashed since I moved from marlin
But yeah, before this change, it was flashed and running (unhappily, but running)
uncut topaz
no, you dont have to reflash it. normally you could just change the pi. it doesnt matter if the sd card was in a pi3 before, because it is the identical OS
sand escarp
my previous installation also had some update corruption, crowsnest and a few other applications were broken, so yeah I just reflashed the OS and imported the printer.cfg
okay, what are my options for diagnosis going forward? I see nothing astoundingly wrong with the PI end
I am not crazy for cutting the 5v line on the USB cable to prevent backfeed, correct?
uncut topaz
my previous installation also had some update corruption, crowsnest and a few ot...
corruption in the update manager means only that the git file is corrupted (just a brocken git history). so a git reset would just fix this state. but this have nothing todo with the programms itself.
sand escarp
corruption in the update manager means only that the git file is corrupted (just...
sorry, my jargon is a little off, I meant crowsnest had some update corruption, and a few of the other modules in the update manager were also refusing to hard update. so the camera "program" was broken in the UI
Yeah, you are correct it all doesn't matter though, that's why I refreshed my install
What's next to try?
uncut topaz
i just find it very strange that your board does not report properly via the usb-serial connection. it looks like your board has not flashed a klipper, but when it was working before you reflash the SD card, this couldnt be the problem
sand escarp
I mean, I flashed it once, I could do it again, but I'm unsure if it'd help
sand escarp
my previous installation also had some update corruption, crowsnest and a few ot...
I just brought my printer back online with these steps, and now It's not connecting to serial
uncut topaz
its just impossible, that it doesnt work any more only with a reflash from the sdcard. your board has nothing todo with that...
sand escarp
ok, what do I need to investigate then to know what I have to do to get my printer online?
sand escarp
its just impossible, that it doesnt work any more only with a reflash from the s...
Is it possible if a wayward SD card was placed in the SD card slot by some idiot, possibly the SD card for another raspberry installation, and the printer may have tried loading FW from the first .bin file it found and corrupted it?
(I am the idiot in this hypothetical, and I am very frustrated with this idiot)
I just don't know where the hell the point of failure is?
I've been working on this again now for several days
uncut topaz
Is it possible if a wayward SD card was placed in the SD card slot by some idiot...
the board cannot grab anything from the board itself.
as long as you dont try to flash the board (wrong), after swapping your pi, i have no glue how this issue can come.
you can try to flash your board, but normally it is not neseesary, because you would flash the exact same code right now...
sand escarp
Is there anything to diagnose or rule out?
If not we can rule this out, I'll do it this evening, I just have to confirm my mainboard version again
uncut topaz
you can only confirm the mainboard firmware, when it connects
sand escarp
you can only confirm the mainboard firmware, when it connects
When I get a moment I'll manually confirm the creality motherboard revision and the appropriate chip set version to flash for
sand escarp
Continuing to have issues
I have to pull the new errors again, but when I went to reflash the board it says that my chipset is in DFU / Bootloader mode?
This may be a hardware issue on the printer side (screw me)
uncut topaz
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
is a path from a ch430. this is a usb-to-serial chip. this is between your usb port and your mcu. so you should not see if your mcu is in dfu-mode.
pls post the output of lsusb
sand escarp
```
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
```
is a path from a ch430....
pi@mainsailos:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@mainsailos:~ $
is your board plugged in?
sand escarp
yes, now it's not registering
BTW it's a Creality 4.2.2 with a GD32F303 chipset
which seems to be strange
It was definitely there before,
No way a logitech unifying adapter would confuse this at all would it?
sand escarp
yeah, I'm looking now, I might have even more of a funky printer I thought
Looks like my chipset is a
"GigaDevice stm32f103 clone"
[*] Disable SWD at startup (for GigaDevice stm32f103 clones)
uncut topaz
you should not see this chip, because the creap creality boards uses a ch340 usb-to-serial chip...
sand escarp
I have some weird issues I have to scratch out