Setup step 1 issues
Hello, I am having some issues setting up RatOS. It’s my first time using it and I don’t know what I’m doing wrong. I am in the setup page and when I try to update/ download the firmware and move to the next step, it won’t let me. It is says board not detected. But it has auto flashed before. I checked the firmware file and it is .cur file so I know it did it right. Can I just skip the rest of the set up and go to mainsail and add my stuff. I am also getting a mcu error on mainsail. Any help would be appreciated.
67 Replies
Screenshot of the error? What version of ratos?
I would get the latest ratos 2.1 rc2 and run the configurator. If you have any troubles please be as verbose as you can with what you have tried and what the issue is. Good luck
How do I get it?
https://github.com/Rat-OS/RatOS/releases
Scroll down to "Assets", expand it, grab the image for your board.
GitHub
Releases · Rat-OS/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Rat-OS/RatOS
I keep getting the same error
What directions are you following? You may need to add/remove a jumper for it to show up
None really
I’m trying the dfu mode with a jumper on the Boot0 and it won’t detect it
USB-C on the octopus, USB-A on the pi.
Correct
Okay then either you aren't following the instructions or your board isn't powered (or literally dead, which is unlikely)
Show a picture of your board and pi
Hard to tell from the photo if the boot jumper is set
you need to take that SD card out
dfu doesn't work with the SD card in
I tried that an it still won’t go into dfu mode
And how are you doing it?
I can't see the jumper in the pic
Without the SD card, I have the 5 V jumper on and the blue zero jumper on and then I plug-in the octopus version 1.1, I hit the reset button in the only light that comes on is the green LED
OK, I’ve got three lights on now. But it is still not detecting the DFU boot. This is a brand new octopus V1.1 446. I just do t know what to do
That board is confusing. It has separate power for motors but doesn't say octopus pro. Nor does it match the image for the MCU flashing he posted earlier
all octopus's have a separate motor power input. Only the Pro has a selector on each driver to switch between that and VIN. The board matches the image.
Did you put the DFU jumper in before you connected it to power? You need to do as instructed and put the dfu jumper in after you get to that screen.
Otherwise there's no way to know that the dfu device is actually the octopus (it could be any other board).
all stm chips in DFU mode look the same.
Ok. I’ll try that
make sure the board is booted after you've removed the DFU jumper. Then go through the configurator, and then put the DFU jumper in and boot the board when instructed.
It is up and running now!
Here is my problem now. What do I need to change in the config?
It happens for both x any y
You need to check the wiring of your end stops. Hopefully they aren't wired incorrectly and burned out your port
I can see that they work in the machine tab and physically open and close them
Please download a debug-zip from the sidebar in the configurator and post it here
That's odd.. The homing is behaving very strange, but the config looks fine. Wonder if it's something related to the bltouch.. looking into it..
I'm gonna need you to home and then send me a new one (debug zip), the klippy.log is practically empty, looks like it rolled over just before you downloaded it.
There's nothing in it, looks like it just booted for the first time.
Also you have stealthchop enabled, but your video does not sound like stealthchop is enabled.
Looks like a log from one printer and a video from another lol
I'm assuming it's not moving to the middle after homing X because of the error. And then you manually press G28 Y afterwards off-camera?
This may help:
Put that in the printer.cfg right here
OK, thank you. Whenever I home the X it moves the Y axis some I’m not sure if you can sit in the video, but I will send another one if that doesn’t work.
Here is what is happening
Could you please go through this section: https://os.ratrig.com/docs/configuration#verify-stepper-directions (verify stepper directions)
Configuring RatOS | RatOS
RatOS only needs minimal configuration to work, but comes with a lot of optional functionality that you can enable manually.
If X / Y doesn't move in the correct directions when you click the arrows in the toolhead dialog in mainsail, you have some wiring issues we need to fix (can be done through configuration)
Here is the issue
wtf.. Can i see a picture of your stepper wiring on the board?
It’s from earlier, the steppers are wired like the left
And the third cable from the bottom is wired to your extruder, right?
Correct
My z and extruder are fine
I'll be honest, i have no idea how this is even possible in the first place. Does it consistenly move X to the left on both the left and bottom arrow buttons? And Y towards the front on both up and right arrow?
@Helge Keck take a look at this, it's wild.
@miklschmidt yes it does
@Lance disable "Stealthmode" in the configurator and see if that changes anything.
Ok
I'm grasping at straws, but something is acting strange.
I've been doing this for a very long time now, debugged hundreds if not thousands of user printers. This is the first time i've ever seen this.
Shit
How do I disable stealthchop, from the cfg?
Go to the ratos configurator wizard, click the "Hardware Selection" step, go down to "Motion", switch off the toggle next to "Stealthmode", save your changes on the next page.
Ok
did that change the movement?
Same test as this with
SET_CENTER_KINEMATIC_POSITION
I will try it after work
@miklschmidt it still does the same thing
Aight, it has to be a driver or slot issue, try moving x and y drivers and connectors to slot 4 and 5, then tell the configurator (enable advanced in motion settings on the hardware selection page) that your X is now in slot 4 and Y is in slot 5.
Like this?
No wrong end, you moved z1 and z2
Ok
Solution
Then:
then click next, and save the configuration.
Accept the changes to printer.cfg for good measure (works without it, but then we're sure everything is reset to stock)
Holy shit it worked!!
Hooray!