Realtime Analysis - SciChart too old.. error
I'm getting this screen when trying to access the Analysis Tool..
Sorry! This version of SciChart is too old to be used for the community edition. Please update to the latest version.
RatOS fully updated..
29 Replies
@miklschmidt
Same!
updating, gimme a sec š
Solution
Fixed. Update ready in 5 minutes.
It introduced a weird graphical error in the live signal graphs that we'll have to live with for now. It seems to be missing a piece of the end, not sure why.
@Chrizzar @rubino25 Can you guys check if it works for you after the update?
No Sorry.. the error is on customer printer. Not mine. Sorry
Gotcha, as far as i can tell it works now, but always nice to have it confirmed š
I was having the same error, updated and its working again
Happy new year!
I'm still getting this error. Everything up to date except the RatOS Configurator repository as it keeps breaking my system (Bad Gateway) even if I stick to the recommended order of updates
Rat-OS configurator is what needs to be updated...
Thanks. I've just commisioned my V-Core 4. I had re-installed RatOS 4 times.
First time it was my mistake as I just hit "Update All".
Second and third time I followed the procedure, still got the infamous BAD GATEWAY error.
I'm not gonna update it for now š
pi@ratos02:~ $ ratos doctor
error: unknown command 'doctor'
"pi@ratos02:~ $ ratos --version" returns nothing
pi@ratos02:~ $ ratos info
Machine IP 192.168.3.42
RatOS Version v2.1.0-RC2 (bullseye)
Configurator Version v2.1.0-RC3-83-g3a6a8b0
Klipper Version v0.12.0-316-g96cceed23
You haven't updated
True. Because I tried three times and it always broke my system (Nginx: 502 BAD GATEWAY).
First time was my fault, because I just hit update all. The other two times I followed the given update order. Still same issue.
I did reflash ratos between each attempt
It's not just an order thing, you need to restart moonraker and refresh mainsail etc before doing the final update.
see this: https://discord.com/channels/582187371529764864/1324058506193797131/1324138855162581046
(this is temporary btw)
it's just until RC4 is out
Gotcha. I have a print running for the next 90 minutes. Will try afterwards. Thank you!
I think what's tripping everyone up is that the new deployment action forced push (apparently that was default behavior) and killed a bunch of the history.
At least that wasn't hitting. I've just finished comissioning on the new years eve
You might be able to update your current installation by doing the following:
during the print?
never do stuff to your system during a print
š
Ok, here's what I did:
1. Restarted moonraker (I did id anyways even though I had rebooted earlier.)
2. Everything else was up to date and I did update ratos first
3. Tried updating ratos-configurator through the GUI (cloning from github should be possible anyways)
4. Waited for 20 minutes but the process wouldn't finish. No timeout. Last message "updating npm and pnmp...". Don't know where to find the logs, just have a screenshot.
5. ssh ratos02.local -l pi
6. mv ratos-configurator/ ratos-configurator.bak
7. git clone https://github.com/Rat-OS/RatOS-configurator.git ratos-configurator
8. cd ratos-configurator
9. git checkout v2.1.x-deployment
10. ratos doctor
This has fixed the missing dependencies. After restarting moonraker I got a fresh klipper update.
GitHub
GitHub - Rat-OS/RatOS-configurator: The RatOS Configurator
The RatOS Configurator. Contribute to Rat-OS/RatOS-configurator development by creating an account on GitHub.
Does it make sense to mark this as solution or will it be contra-productive once RC4 is out?
Oh, and thank you!
4. Waited for 20 minutes but the process wouldn't finish. No timeout. Last message "updating npm and pnmp...". Don't know where to find the logs, just have a screenshot.This is normal and is mentioned in the announcement. Mainsail isn't fast enough to keep up with the output of everything (the state management is very unfortunate), just refreshing your browser should help. The rest of the steps probably weren't necessary (but depends if you've done "hard recovery" on the configurator, in which case all the scripting has been deleted and the update scripts won't run, and thus you need
ratos doctor afterwards).
regardless, no harm no foul, cloning the configurator and running ratos doctor will fix most issues.
Mark it as the solution for now, hopefully i'll remember to update here once RC4 is out šDon't have the permission to mark it as solution here.
Ah, not the author, i'll do it š
i set it back again, it's not related to the thread topic
Thank you Mikkel.
I will check tomorrow if I have time.
It has been a hard and busy last week..