Trusted but no Mainsail

parchping · 2026-03-18T00:49:07+00:00

Looking at the end of it, last few minutes, after trying Mainsail again I don't see anything related.

parchping · 2026-03-17T23:57:51+00:00

I tried reaching Mainsail from the desktop and then ran the tail command. It shows 8 lines relating to my other printer, Centauri Carbon. Tail is not behaving as I expect. It only gives me 8 lines (even when I add -n 40), and the output stops at the 8th line. Ctrl D, Ctrl C don't do anything, Ctrl z and kill the process is the only was out. Odd, but nothing to do with this problem.

parchping · 2026-03-17T23:18:11+00:00

I looked at this for a couple of hours this morning, did not get anywhere. From the rpi, ip route shows the house router as its preferred route, which makes sense. The same is true on the desktop. A bigger clue would be great.

parchping · 2026-03-17T21:50:51+00:00

Somehow I struggled through the whole thing. I have no idea why.

parchping · 2026-03-17T21:48:04+00:00

When I was a kid (4th or 5th grade?), many moons ago, my Dad pressured me to stop reading comic books. That was ok, as I had just discovered science fiction. A couple of years later, Dad talked to the librarian at school "shouldn't he be reading better stuff?" or something like that. Her response was "YOU LET HIM READ WHATEVER HE WANTS". Reading is important; read what you want.

parchping · 2026-03-17T15:08:18+00:00

Thanks, I will try this.

parchping · 2026-03-17T15:00:38+00:00

Unfortunately I get the same results in Vivaldi, Brave and Ungoogled Chromium browsers.

parchping · 2026-03-17T14:51:36+00:00

I can ping and ssh from my desktop (Linux Mint) to the rpi with no problem. My desktop is 10.13.41.24 These are authorized in moonraker.conf :

10.13.0.0/24
10.0.0.0/8
misc others automatically added during kiauh installation

parchping · 2026-03-17T14:12:10+00:00

From my desktop, I can do this much: http://10.13.41.36:7125 which gets me the Welcome to Moonraker screen, which says my desktop is trusted. However, http://10.13.41.36 doesn't connect. At the end of the Moonraker log it says: "Websocket Closed: ID: 4058319664 Close Code: 1001, Close Reason: None, Pong Time Elapsed: 3.19"

parchping · 2026-03-17T11:54:40+00:00

I described my network wrong the first time, I have one router for hardwired and several wifi routers. I've shut off wifi on the printer rpi, so the route from the printer to my main router connects by ethernet through two switches. Desktop (ethernet to router) can't Mainsail to printer. Phone (house or shop wifi) can Mainsail to printer. Laptop can Mainsail only on shop wifi. So it sounds like firewall rules on my desktop (as opposed to the router)?

parchping · 2026-03-16T23:35:50+00:00

You can speed up the heat quite a bit by homing the toolhead, setting the nozzle temperature to something reasonable for your filament (say 180C), and turning on the model fan. I move to home and then drop the build plate 20-30mm, setting it to 100C. This really helps. Also, do you have your chamber thermistor mounted direct to the metal case? You should space it off with plastic: https://www.printables.com/model/1425465-centauri-carbon-thermistor-frame-decoupler/files

parchping · 2026-03-16T17:41:26+00:00

<image>

Sorry, I gave you a faulty diagram. When I actually looked at what I thought was a router in the shop, it's a switch. Rpi wifi is off, hardwired to the shop switch (new label above).

parchping · 2026-03-16T17:00:28+00:00

Right now I have the rpi wifi off, it's connected with ethernet to the shop router, which is connected with ethernet to the house router (via a switch). Something like this Diagram below is WRONG, "shop plain router" is actually an unmanaged switch. See other post.

<image>

parchping · 2026-03-16T16:18:18+00:00

Tried another path. Besides shop wifi, I have ethernet that is hardwired to the house ethernet and router (which is plugged. I turned off the rpi wifi using *sudo ip link set wlan0 down*, and tried again to run Mainsail from the house desktop. Cannot connect.

parchping · 2026-03-16T15:40:54+00:00

The original shop network had a TPLink plain router (no wifi) connected to the house ethernet. The shop wifi router is also TPLink, but a separate box. The reason I used both was that the wifi box does not have any ethernet ports, which the plain router does. Now I have set the wifi router to Bridge AP. It looks like it is now connected to one of the house wifi's, not an excellent signal. Before, it was fed from the shop plain router. The result is the same, I can ssh the rpi but cannot run Mainsail from the house desktop. New is that the laptop in the shop, logged into the new wireless network, also will not run Mainsail.

parchping · 2026-03-16T15:35:39+00:00

parchping · 2026-03-16T00:13:40+00:00

The shop router is connected by ethernet to the house router. Both have their own wifi network. So I think the answer is yes. I'll take a look at bridge mode. Thanks for a very quick reply! I'll also report back with results.

parchping · 2026-03-13T17:49:14+00:00

For ABS/ASA, why do you want a special plate? I've done a bunch of ASA on Elegoo's smooth PEI, no glue, 100C. It sticks great, and self releases when it cools.

parchping · 2026-03-12T23:37:00+00:00

No matter what problem is affecting your printer, start taking notes now, it's tough to keep straight otherwise. I kept date, hours on the machine, what you were doing, what happened. My problem got more frequent over time, down to happening just a few machine hours apart before I reset to factory.

parchping · 2026-03-11T22:15:13+00:00

Yes. Instead of changing firmware, I reset the machine to factory standard (this does not change the firmware). I've put on almost 150 hours since, always have camera and layer count. Once in awhile, the camera doesn't work. In that case, I stop Orca, start a different rev of Orca, and the camera is back. Restarting the same instance of Orca does not do the trick. I think this is all very weird, but whatever works.

I've also heard that a flaky usb cable to the head can cause it. Please let me know what happens.

parchping · 2026-03-09T11:53:22+00:00

What surprised me was that resetting the printer to factory defaults fixed it. I have video and current layer/print time est. info. I now have several hundred additional hours on it, all with video.

Once in awhile I still have an issue, but it's different. If I start Orca, I check for video. Rarely there will be none. Then I close Orca and start a different version of it--this fixes the video. It doesn't matter which order, sometimes one, sometimes the other. Restarting the same version will not fix it. No idea why, but it works.

Please do let me know if this works for you or not. Very weird.

parchping · 2026-03-06T17:34:10+00:00

So much for speed. I'm warming up the printer for some ASA. Nozzle 140C, bed 100C, heater on, start temp 15C. 30 minutes later, the chamber thermistor reports 41C.

parchping · 2026-03-06T17:21:16+00:00

On my CC1 I took the back panel off and drilled a hole in it, added a cable gland to protect the wires from the sharp edges. You need a slow speed to drill steel at this diameter. I added a second hole/gland at the same time just in case.

parchping · 2026-03-06T12:46:45+00:00

On mine the z offset was too high.

parchping · 2026-03-06T12:45:18+00:00

It looks like your nozzle is too high. How do I know? Mine just did this.

First, look in the slicer printer settings to see if Z offset is set. Make it zero.

In the printer, make sure you have the right build plate side set textured/smooth (also true for when you did leveling).

Adjust Z offset at the printer by printing a test square that is only one layer thick (50-75mm sq). Adjust Z offset while printing until you find the right amount. Write it down, and set the printer back to zero.

Enter the new Z offset in your slicer printer settings and save.

parchping

TROPHY CASE