VAOC not loading and Realtime analysis giving errors....

I've updated to the newest versions of everything, now I'm not able to start the VAOC anymore and when going to Realtime analysis, I'm getting this error message as attached. I've switched my nozzles and wanted to do a VOAC so this time I noticed, it is not working. Everthing else seemt to work fine on my VC4-Idex... Please help me. Debugs enclosed as well.
Solution:
The motor slots have changed, you likely have a Y and either X/DC swapped. Just set them like you have it connected in the hardware configurator.
Jump to solution
17 Replies
miklschmidt
miklschmidt•2w ago
First, a few general comments: delete this from your moonraker.conf:
[update_manager fluidd]
type: web
repo: HelgeKeck/fluidd
path: ~/fluidd
[update_manager fluidd]
type: web
repo: HelgeKeck/fluidd
path: ~/fluidd
Start properly shutting down your pi, abruptly cutting power can lead to filesystem corruption:
Unsafe Shutdown Count: 32
To fix your current issue, make sure your hardware configuration is set correctly, it's complaining it can't read your settings from the moonraker database, particularly one of your toolheads does not have a configured accelerometer for Y.
Kinetik
KinetikOP•6d ago
done the fluidd Shutdowns, talk to Helge 😉 It was his printer xD I'll try to fix the issues with the hardware config then. Can I see, where it is actually complaining about something? I went through this and it went through...
Kinetik
KinetikOP•6d ago
I can't go any further in the setup now
No description
miklschmidt
miklschmidt•6d ago
We have fluidd at home: https://github.com/Rat-OS/fluidd
GitHub
GitHub - Rat-OS/fluidd: RatOS Experimental fork of the Fluidd klipp...
RatOS Experimental fork of the Fluidd klipper frontend - Rat-OS/fluidd
miklschmidt
miklschmidt•6d ago
(it's already in the RatOS moonraker.conf) reselect the printer, toolhead state is broken (select a different printer, then select IDEX again, i recommend "start fresh", you'll have to set your settings again)
Kinetik
KinetikOP•6d ago
Yes, have the newest version now installed changing the printer did the trick... now reconfiguring no idea why, but now the printer tries to home X on the wrong side... It moves the T0 carriage to the right side and not to the left where the physical endstop is located.... pins and directions are the same as before... Need to look into this tomorrow... Any idea? need to leave now Think I found something. Will check tomorrow
miklschmidt
miklschmidt•6d ago
prolly swapped DC and X in the motor slot configuration, i changed the defaults recently so there wouldn't be a conflict when merging IDEX into an existing hybrid configuration.
Kinetik
KinetikOP•6d ago
Ok, I don't know, whats happening here... The X-Axis both needed to be reversed using the dir_pin: !x_dir_pin and the same with the dual_carriage Also now the 2 carriages slam together very heavy when trying to home the Y-Axis... and it basically does not home at all I'm kind of confused now what happened here... the Y-Axis needs to be inverted now as well...
Kinetik
KinetikOP•6d ago
No description
Kinetik
KinetikOP•6d ago
So no idea, what is wrong here, but this is my printer.cfg now... All pins are inverted compared to the version before... At least, now the printer moves correctly again
Kinetik
KinetikOP•6d ago
No description
Kinetik
KinetikOP•6d ago
what I find as well, in the homing.cfg, there is tmc2209 written for driver x and y, but I have 5160 selected in the config Realtime Analysis now works, VAOC however does not load... here is the newest debug.zip Maybe you can find something in here
Kinetik
KinetikOP•6d ago
ok, the fans are not working either... what just happened...
Solution
miklschmidt
miklschmidt•5d ago
The motor slots have changed, you likely have a Y and either X/DC swapped. Just set them like you have it connected in the hardware configurator.
miklschmidt
miklschmidt•5d ago
You're not looking at what you think you're looking at. You'll be less confused if you look at the files generated for you (sensorless-homing-y.cfg). Which fans, and do you have them properly connected? Your camera configuration is wrong, the v-core 4 does not use a rpicam v2
Kinetik
KinetikOP•5d ago
Ok, got it back to work... Also the camera is working... I had to reset the entire board again, reflashed 3 times the board and did the config wizard 2 times. then everything worked again... thanks for your help and your patience 😉 will you be at the Formnext on site?
Want results from more Discord servers?
Add your server