502 Bad Gateway error in configurator after update
After hard recovery update of ratos and rat-configurator, every function in configuration stops working (vaoc, main configurator etc.).
Any idea hot to fix that? before update everything works fine...
Solution:
Ratos reinstallation fixed the problem, so topic closed
Upgrading From Hybrid To IDEX 2x T0 but no T1 in Setup Wizard
Setup Wizard shows that I have two T0 zero toolboards, but no T1. I'm unable to actually complete the setup wizard as I can't unselect a Z probe from one of the T0 toolheads, and no way to specify the stepper driver for the T1 extruder (only choices are for motor slots on the MCU)
Both the T0 and T1 toolboards are EBB42 connected via USB with jumper to be powered via USB in place right now as I go through the setup wizard. Both are powered, LEDS are on. This was a previously functioning hybrid setup that is being upgraded to IDEX.
Not sure what other information would be helpful, but let me know!...
Solution:
dyocis gave me the answer. Need to restart fresh to get it to work. In the printer selection tab, I clicked on IDEX, then back on Hybrid and it gave me a prompt asking if I wanted to start fresh. Clicked on that, then clicked on IDEX again and got the same prompt, which I again clicked "start fresh." Everything is working appropriately now
RatOS installation: Flashing Octopus V1.1 via DFU - DFU not detected
Octopus v1.1 - RatOS-2.1.0-RC2. Initial setup, connecting RPi to Octopus, power supply is connected but not powered.
My board doesn't reflect the image in the setup Wizard, but I believe I've got the DFU jumper set correctly (img 1 & 2).
Moonraker lights up green, while Klipper turns red in the Wizard.
When I connect a monitor to the Pi I see an error message "unknown config object 'bed_mesh'" (img 3).
Can I continue with the build guide pt 12 electronics as my board is detected in the configurator or is there something wrong ?...
Solution:
That's the dfu jumper. The one you've highlighted is the V_USB jumper that connects USB 5V to the onboard 5V rail (you very much want to remove that..).
Issues with fine tuning Beacon contact
Ive been fighting with my printer for a while now. When I installed the beacon and did the z offset calibration https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/beacon_contact.md I had a perfect first layer.
But Now im having issues with the first layer. I have cleaned the bed and redone the calibration a couple of times. But to no avail. Also tried the fine tuning z offset in the webui during prints. But doesnt matter which way i go up or down it still keeps issues....
No trigger in probe after full movement
I do not know why when i try to make the z-tilt, make very big adjustment and then show the error "no trigger on probe after full movement"
I am doing the inicial configuration...
RatOS - No network connection available
Verified working RPi 4 B 4gb. Verified working SD cards, SD readers. Have tried downloading the image multiple times, even using different browsers. Using Balena as requested by RatOS docs, produces an error during the verification process every time, regardless of download, SD card, SD reader, etc. Using Pi Imager does not produce errors.
Again, regardless of SD card, SD reader, or download, once I boot up the PI, the OS will not allow it to connect via the wired connection. I can connect to the hotspot via my phone and computer AND laptop, how ever, i can NOT connect to http://ratos.local/configure or http://192.168.50.1/configure on all three devices I attempted. Using the same SD cards, I can load the current version of Raspberry Pi OS 32-bit, and it connects to my network via the LAN card just fine....
Solution:
yeah, you will NEVER be able to connect on your LAN to http://192.168.50.1/configure , that is the hotspot sub-network
webcam stream not found
I get the error as in title when I go to VAOC tab in mainsail. I can see the stream from the camera when I add it to mainsail so the camera itself is working. I added the configuration to crowsnest.conf as per idex commisioning guide. In chrome console I see the following errors:
