#problem after installed tailscale and nkilpper cannot connect
1 messages · Page 1 of 1 (latest)
Do as a favor, delete the moonraker and Klipper log. Reboot the system and download both files new
The log is so big and contains a lot of errors so that is it not clear what of them fresh or old
one moment
total 52
drwxr-xr-x 10 pi pi 4096 Dec 18 22:33 crowsnest
drwxr-xr-x 7 pi pi 4096 Dec 26 22:45 kiauh
drwxr-xr-x 2 pi pi 4096 Dec 26 22:50 kiauh-backups
drwxr-xr-x 11 pi pi 4096 Jan 3 13:45 klipper
drwxr-xr-x 5 pi pi 4096 Jan 3 13:46 klippy-env
drwxr-xr-x 5 pi pi 4096 Dec 18 22:33 mainsail
drwxr-xr-x 3 pi pi 4096 Dec 18 22:33 mainsail-config
drwxr-xr-x 8 pi pi 4096 Jan 3 13:24 moonraker
drwxr-xr-x 5 pi pi 4096 Dec 18 22:29 moonraker-env
drwxr-xr-x 7 pi pi 4096 Dec 18 22:32 moonraker-timelapse
drwxr-xr-x 5 pi pi 4096 Jan 3 13:22 pgcode
drwxr-xr-x 10 pi pi 4096 Jan 3 13:24 printer_data
drwxr-xr-x 8 pi pi 4096 Dec 18 22:35 sonar
Ok
ls -l ```
ls -l
total 4964
-rw-r--r-- 1 pi pi 1166091 Jan 3 15:26 crowsnest.log
-rw-r--r-- 1 pi pi 800164 Jan 1 00:00 crowsnest.log.2023-01-01
-rw-r--r-- 1 pi pi 825324 Jan 2 00:00 crowsnest.log.2023-01-02
-rw-r--r-- 1 pi pi 855516 Jan 3 12:58 crowsnest.log.2023-01-03
-rw-r--r-- 1 pi pi 93398 Jan 3 15:04 klippy.log
lrwxrwxrwx 1 root root 34 Dec 18 22:33 mainsail-access.log -> /var/log/nginx/mainsail-access.log
lrwxrwxrwx 1 root root 33 Dec 18 22:33 mainsail-error.log -> /var/log/nginx/mainsail-error.log
-rw-r--r-- 1 pi pi 1011049 Jan 3 15:28 moonraker.log
-rw-r--r-- 1 pi pi 38700 Jan 1 23:49 moonraker.log.2023-01-01
-rw-r--r-- 1 pi pi 265387 Jan 2 20:59 moonraker.log.2023-01-02
lrwxrwxrwx 1 root root 18 Dec 18 22:36 sonar.log -> /var/log/sonar.log
rm klippy.log
ls -l```
rm moonraker* it does not do anything
pi@mainsail:~/printer_data/logs $ ls -l
total 3572
-rw-r--r-- 1 pi pi 1166091 Jan 3 15:26 crowsnest.log
-rw-r--r-- 1 pi pi 800164 Jan 1 00:00 crowsnest.log.2023-01-01
-rw-r--r-- 1 pi pi 825324 Jan 2 00:00 crowsnest.log.2023-01-02
-rw-r--r-- 1 pi pi 855516 Jan 3 12:58 crowsnest.log.2023-01-03
lrwxrwxrwx 1 root root 34 Dec 18 22:33 mainsail-access.log -> /var/log/nginx/mainsail-access.log
lrwxrwxrwx 1 root root 33 Dec 18 22:33 mainsail-error.log -> /var/log/nginx/mainsail-error.log
lrwxrwxrwx 1 root root 18 Dec 18 22:36 sonar.log -> /var/log/sonar.log
You see logs are gone 😉
Now reboot and after that download the new logs
Ok what is there error you seeing
no error but stuck at Klipper reports: STARTUP
and the circle is loading all the time
I had but I uninstalled it because I read about that maybe cause this problme
but nothing
webhooks client 1972569112: New connection
webhooks client 1972569112: Client info {'program': 'Moonraker', 'version': 'v0.7.1-794-g225ec58'}
TMC stepper_y failed to init: Timeout on wait for 'tmcuart_response' response```
That’s your real issue
with the stepper ?
Is,it a buster install? Make a picture of the host system section
Go to the Maschine tab
Becausee Klipper needs both to run, the host PC and the mcu board
Ok that’s not the klipperscreen problem
Send the Klipper.log again let’s see what happens next
yes but the always loading problem occured after I instlled klipperscreen and mayb tailscale
And honestl for the rat rig OS you should ask them
also when I power on th eprinter, the same again the always loading
Tailscale has nothing to do with that, you have a Klipper issue
its the theme of the rat rig
As said switch on also the 24V of the board
hard fresh u mean f5?
I do not know what browser you use
No clue what brave needs for many it would be CTRL F5
There is a refresh and a hard refresh (that also clears the cache)
The log does not change
And that I do not believe
Yes reboot again wait 5 minutes and send log again
ok
I need to complete booting sequence yours stop in the middle. The tmc error will also occur if you start without 24V
so if I try to restart firmware with 24v on it, u will have the complete boot sequense right?'
Hopefully 😉
b'Got EOF when reading from device'
I see that the second time … that’s not good at all
That has nothing to do with Tailscale but indicate a serious problem in your system
shit
Could be a bad usb cable
I can try to change the usb
but
it keeps on loading even if not usb is connected
this is the first time I see that
Save your printer.cfg on your PC, make a new MainsailOS SDCard, and only get your printer.cfg on it
Let’s see if it boots up than
I have a already ready with mainsail new one
If you did changes to your moonraker.conf you need that too
Perfect than use that, I suspect it will change but it rules out everything you did install
ok
in 3 minutes it will be up
yeap
its working hahahah
I knew it it was something I did
so I will just reinstall mainsail on the other sd for the other printer
or u want me to try again the old sd for maybe we fix it ?
so the problem was my moonraker cfg because when I put my old moonraker cfg, same problem occur but when I leave the new one, all ok so I just copied my settings to the new one and its working
but the 2 of them are exaclty the same
anyway, problem solved
one more question if u know
when I reboot the relay goes off and on in a few seconds and then off (because I put on the cfg of the moonraker to be off when power on) but is there a way not to go off-on and off but just stays off?
I found it and fixed that, it was something in th emoonraker cfg so its ok now, both sd are working
That klippy_uds_address: ~/printer_data/comms/klippy.sock has changed
Every time you use a new shine MainsailOS take care and compare your moonraker.conf to ours. In doubt always use ours
is there a copy of the stock moonraker.cfg ? because I forgot to download it and now I need again to disasseble and change the sd in order to download it
Not a complete one but https://github.com/mainsail-crew/MainsailOS/blob/develop/src/modules/moonraker/filesystem/home/pi/printer_data/config/moonraker.conf
It only misses some Update sections as they are added during the build process
its ok, I will copy them
Show me your config
There is an initial state for relays
I need to understand what you really have there
[power Printer power]
type: gpio
pin: gpio14
initial_state: off
off_when_shutdown: True
locked_while_printing: True
on_when_job_queued: True
bound_service: klipper
restart_klipper_when_powered: true
restart_delay: 5
thats the secion for the relay
its off but when I reboot, it turns off-on in a 2 seconds and again off in 10 seconds
Ok I see it’s a high active relay that means as soon the PI starts booting it’s on and than when moonraker is up and running it goes off
So nothing you can do about that
What you could try is set it in config.txt to set the behavior at boot see https://www.raspberrypi.com/documentation/computers/config_txt.html#gpio-control
I will read it carefully and try it but
if I choose a low level relay for the other printers, it wont behave like that right?
Should work yes [power psu] type: gpio pin: !gpio14 initial_state: on bound_service: klipper restart_klipper_when_powered: True locked_while_printing: True
I have mine on at power up but yes
I will