Core-V4 Hybrid 500 - Commissioning Issue - no 'mainsail'
Hello,
this is my first post in discord.
I have build up my Core-V4 Hybrid 500 and now trying to commission it. Raspi is starting and I could connect to ratos.local (respectively to the static ip-adress over ethernet). A 7" BTT-Toucscreen is attached and shows klipper-screen. I could start the Setup-Wizzard. Setup ist completed and afterwards mainsail should be available - but the only display shows "initializing" forever. On klipper I could run home-x and home-y and it is working (after fixing an issue with a factory-assembled motor-cable. It seems klipper is up and running, x- and y-motors and belts are installed correct. When I run z-home, all steppermotors are start running in the same direction (looks also good), but will not stop and will bump into endposition.
I would like to run the sanity-checks with mainsail, but that is not reachable.
What I have already checked:
* "using ratos.local" or "static-ip"
* using 3 different browsers - clear browser-cache
Pls can someone help me get mainsail to be available?
Best regards, Holger
24 Replies
Are you able to ssh into the raspi?
Yes
Hm, so that at least means it is on the network
I don't know how to diagnose a mainsail issue, and you've tried a lot of the things I would have thought of like refreshing, different browsers, hard refresh.
I'm assuming a power cycle hasn't changed anything?
Yes, I can ping it on the network. And if I use a browser, there is an interetsite coming up - see the screenshot of my last post. In Klipper I can run home-x, home-y and home-z (the z-axis has still a problem with the position, but all motors are running in the same direction). So at least mechanic, electric wiring, Octopus-board and Klipper on Pi is working.
I think there was a problem with the setup-wizzard and something was not finished. Who can help examine that problem? I have the log-files from the setup copied via FTP, so I can provide them.
by the way, I did the complete process twice. After the first time I prepared a new SD-card from scratch and started the wizzard again - it ended up in the same problem 😩
drop your debug.zip in here and someone can take a look.
ok, but ... do You mean the log-files in '~/printer_data/logs/klippy' - or something else?
i mean the debug.zip. Should be available in the left hand column after selecting "Configurator"
Thank’s a lot for Your efforts and patience with me!!! I guess You mean the menu in mainsail - but mainsail is not working on my Pi 😩
@blacksmithforlife Do you know if the debug.zip is generated on request through mainsail, or is it hiding somewhere in the filesystem?
I believe the UI just zips up various files already on the filesystem
@Holger Then I'm not sure what files could point us in the right direction. Maybe start with moonraker.log, ratos-configurator.log, klippy.log?
I have zipped the complete log folder
I guess You mean the web-interface to RatOS with "UI". But this is not accessable on my Pi ... 😩
Yeah, that was his answer to me. I'll try and take a look at the logs later today. Do you do anything "weird" with your network? It is in an office and not at home or anything?
It‘s a „special class-c network“ 😳😂. I had a small company programming control systems for the industry, so we used a „non public network“. 🤗
That might be affecting it, I've seen other reports of not being able to reach mainsail on office networks. Might need to find your sysadmin for help in your specific case.
probably need to make some update to mookraker for your specific network setup then. As you can see ratos whitelists a bunch of common network setups, but you are doing something crazy then probably doesn't match
https://github.com/Rat-OS/RatOS/blob/v2.1.x/src/modules/moonraker/filesystem/home/pi/printer_data/config/moonraker.conf
Hey guys, You made my day 🙏👍. I have put 194.114.54.0/24 to the whitelist in moonraker.conf and I can reach mainsail 👏👏👏👏
By the way - I‘m my own sysadmin 🧐😆. Thanks a lot again!!!!
Lol, 194...
Writing that one down for the future, thanks blacksmith
It's very rare, and frankly if you're running a weird network yourself, then it should be on you to deal with all the repercussions. But just my $0.02
sure, but that gives a place to look/fix it from
I agree, but the setup-wizard was running. So I thought that the network is ok 🤷
They're on different web services, that's tripped up others before as well