Bevel gears maker (Advanced)Win64, English
General Usage Instructions
You can find the add-in under the GEARS panel in SHWIVEL tab of DESIGN workspace.
For creating gears you have to run this add-in. The window has default parameters so you don't need to set them at the start.
The installer that ran when you downloaded this app/plug-in from Autodesk App Store has already installed the app/plug-in.
OR, simply double-click the MSI to install the app.
You can unload the add-in without uninstalling it by clicking the "Stop" button when the add-in is selected in the list box on the "Add-Ins" tab of the "Scripts and Add-Ins" dialog.
Unchecking "Run on Startup" causes the add-in not to be loaded in future sessions of Autodesk® Fusion 360™.
To uninstall this plug-in, exit the Autodesk product if you are currently running it, simply rerun the installer, and select the "Uninstall" button.
OR, you can uninstall it from 'Control Panel\Programs\Programs and Features' (Windows 7/8.1/10), just as you would uninstall any other application from your system.
All files created and used by the plugin should be located in the plugin directory. If your user doesn't have read/write permissions to this directory, files won't be created but you'll be informed (on the "Information" tab) what you should do. Files created and used by the plugin are:
last_used_parameters.json - contains settings for last used parameters; it is useful when you want to repeat shaft for the same values without setting all the fields once again,
Statistics.json - contains times in milliseconds of most important operations performed by the plugin; it is used for estimating time,
Error_YYMMDD_HHmmss.json, Stacktrace_YYMMDD_HHmmss.txt - contains information about last used parameters and exact place in code where the problem occurred; it is used for searching causes of errors,
./docs/*.html - contains documentation about the plugin, this file should be attached in the installation package; it is used for displaying information when you're working offline
No Internet communication is done by the plugin. The only user data which are stored (only in case of errors) are paths of directories. This is a natural consequence of how the logging stores stack trace of errors. It is a normal and common behavior in all programming languages and technologies and it helps to search the cause of error in files and to find solutions.
In case of error, you'll be informed by a dialog window, where exactly files have been written. There can be two of them: Error_YYMMDD_HHmmss.json with last used parameters and Stacktrace_YYMMDD_HHmmss.txt with information about the place in the program where exactly the problem occurred. You can easily check the content of the files using the simplest text editors. If you want me to reproduce the error you can send these files to me (as an attachment or as text) but it's your decision if you want to.
The program has been tested for many cases with various sets of parameters. Most of the errors have been found and fixed but it doesn't mean that they won't appear for some configurations. When you encounter an error, please send an email to: firstname.lastname@example.org (response would take few hours).
- You have any questions,
- The script does not work as expected,
- Cause errors,
- You have requests for new options.
Please send mail to email@example.com
|Version Number||Version Description|
|**Version 3.0.1 (2020-10-20):** Fixed: * plugin doesn't work - errors of incompatibility with new API Changed: * max. range of clearance is now 0.3|