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..
45 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..
This seems like an old disciussion/thread, but Im encountering this on a new install. Does anyone have this error recently with SciChart library being too old ? I've udated all my libraries, everything seemed/appeareed to be running properly for me until the part in commissioning process where the Realtime Analysis tool is used. @miklschmidt any thoughts on this? The only messages on this subject I could find are this thread and then some other stuff just discussing it's usage, no problems.
I have the same issue.
There are a bunch of threads I've seen all reporitng same. This kind of a big issue it seems like as there does not appear to be any info from team on a fix
Do what does commissioning look without this portion? Is it safe to run a print? I just got to this part of the commissioning process and I don't know what to do
I think this is required part of proceeeding. Even looking through the docs, the VAOC calibration is the last remaining step after all the resonance analysis but I think that be predicated on this stuff completing. To that end I think cannot proceed. Which sucks.
Im actually in the process of redoing ratos. I just made a new sdcard with a fresh install, gonna try and see if I can get it to work. But in another thread where someone else had the exact same problem, he says it was eventually just magically fixed when he updated some os components. I examined the version he is on and it's not the version I am on. His thread was started back in earlier June, a couple weeks ago, I wonder if something has changed in the last couple weeks that has broken everything.
it's all related to this chart library. either there was a license in the ratos package and it's no longer working / valid or it's using the community version (and probably violating the license if its, but it's a bit of a gray area I suspect) and they changed somehting on their end.
I went ahead and attempted a print going very very slow, and it's just not working well. Especially the belt adjustment needs to be made I believe in order to get a halfway decent print
Definitely I think belt tuning is required. And I believe this chart library issue with resonance analysis prevents that from being done at all.
Have any of you begun a report with ratrig about this by chance? I haven't had to do so yet, so rather than flood them I figured I'd ask
I did not, not sure about others. I was thinking about sending an email, but it's difficult to get a timely response from them and they are not super helpful in my experience.
(as an aside, I'm formatting a new sdcard and going to try to re-install everything to see if that works. I'll message if it does)
@rms497 Very cool thanks for that. šš»
Looks like belt tension and shaper graphs are unaffected by this issue, but "real-time analysis" is definitely broken.
oh nice. @leobg , are you in the process of comissioning or have you already completed this? Curious if just skipping and concentrating on belt tension is viable to get a print going or if this realtime analysis data is a requirement. From I take away from reading the commissioning docs it seems like this is something that must be done, but I have never commissioned a DIY / kit style printer before.
the real-time graphs are a really nice to have but you can still do the belt tension and resonance shaping steps without it
just skip the bit titled Ressonance analysis ... having it real-time enables you to find things that are loose/wrong much easier, but you can get the same info by running the Input ShapER (IS) (CoreXY+Hybrid) step and paying attention to any noises you hear and at what frequency you hear them. The graphs that result from that step will show you that same graphs as the real-time stuff just a snapshot after the fact
Thank you for the heads up. I did a refresh of packages and see the new
RatOS Core: Configurator & Configuration available. Confirmed that updating this works!!! Version v2.1.0-RC3-27-g6970de2a is the good one.
Working on my v-core3. Been on RatOS 1 for 3 years now. Going from scratch with most recent RC2 on Github. No VAOC etc here. Just input shaper, but that piece works.
Thanks @miklschmidt for quickly fixing it!