Our knowledgebase contains all the information you need to know about all things SmartBench
This release contains some UI improvements and minor patches
Click here to find out more about the big changes we put into v2.0.0 - the SmartManager release!
SmartManager and SmartTransfer metadata timestamps will now be local to your region.
Some users with slow or unstable internet connections may have experienced Console slowness immediately after sending job feedback, and at start-up. This has now been patched.
To fix this, the way that job file metadata is updated after a job has been changed.
If SmartBench suffers an unexpected power loss immediately after sending job feedback, the associated G-Code file may become corrupted while its metadata is being updated.
If this happens, it is recommended that you replace the copy of the G-Code file on the Console, and check the file on the Console before running it.
These are the more technical changes that we have put into this release. While they are important for improving SmartBench, there’s definitely some programming jargon in this section!
Improvements to how background threads manage external connections and functions, such as getting the public IP address of the Console.
Metadata is updated after a job using a full rewrite instead of sed.
The local timezone is found using the Console’s public IP address.
If SmartBench’s timezone is not what you expect, it may be because your SmartBench has an IP address that does not reflect it’s true location (for example, it is connected to a VPN).
Git tag: v2.0.5
Official release name: Bernard
Git commit: 50564af
Elliot. is the author of this solution
Glad we could be helpful. Thanks for the feedback.
Sorry we couldn't be helpful. Your feedback will help us improve this article.