-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto Cleanup #54
Comments
Hi @ve3elb, Sorry for the delayed response! This can sometimes happen if too many files are saved in the emwin directory - eventually, it becomes too much, since tens of thousands of files are saved in the emwin file every day. Have you configured the This is just a guess based on what I've seen before; you may get some more info if you set debug = true in config.ini file |
No I have not configured any cleanup file. Where will that file be located. I have looked and did not see it. |
Take a look at the Additional Scripts documentation. You're probably a bit behind in cleanup right now, so it's probably best to do a one-time cleanup of files. The long and short of it is:
Once done, you should still have data available in Vitality GOES, but older files have been cleaned up. Now, I'd recommend configuring a scheduled task in Windows to run |
@JVital2013 Thank you for the info it's working. However still have an issue. Maybe you can help. After adding the windows schedule tasks. It's does not work. When the scheduled task runs it only open the files on the desktop. Running the files manually works. |
Sorry for the delayed response - Can you please share how you're scheduling this that it's not working? Either screenshots or exporting the scheduled task should work. |
For the past few days I have had an issue with Vitality Goes. All images from all pages are showing except for the EMWIN Graphics page. It keeps showing (server returned error code 500) I have not change any settings or done anything to the setup.
Does any one have any ideas what I can do to fix this.
Running Windows 10
Thank You
Vince.
The text was updated successfully, but these errors were encountered: