Winston
Lorenzo von Matterhorn
- Joined
- Jan 31, 2009
- Messages
- 9,560
- Reaction score
- 1,748
For your motor files, please fix their most common errors and inconsistencies I've found in Thrustcurve.org downloads, errors and inconsistencies that really mess up the motor selection presentation within simulation programs, then offer them in a zipped file as detailed below. The common errors and inconsistencies I've found:
Make sure all available motor delays for a given motor in both ENG and RSE file types are included and correct.
If both file types aren't available on Thrustcurve.org, create the missing type using EngEdit 9 for inclusion in your zipped file mentioned below.
In a motor's RSE file, be sure the motor TYPE is specified.
Make sure your company name or the abbreviation for your company name is exactly the same in all files for your motors.
Correct any other errors or missing information within each file.
CSI, please standardize the motor naming convention within your motor files to be the same as the one you use on your web site. This isn't your fault, of course, and has to do with the preferences of the much appreciated individuals who upload CSI motor files to Thrustcurve.org.
Then, with those nice, clean, consistent and error free motor files:
Create a file name dated zip file with both the ENG and RSE files only for the motors you currently offer for sale and make it available for download. Why only the ones you currently offer for sale? So that we can select a motor from a list of motors that are actually available. The owners of OOP motors can just go to Thrustcurve.org and download the motor file(s) for their OOP motor(s); no need to have those OOP motors polluting everyone else's motor choices within the sim.
Please do not offer a zip file containing all of your motors in a merged *.eng file without also providing a merged *.rse file. Why? Because the by far most popular simulation programs can use RSE files which, unlike ENG files, contain the very useful piece of information about motor type (single use/reloadable).
Also, if you don't make certain that all common errors and inconsistencies mentioned above are corrected (but why didn't you?) in your motor files, individual rather than merged *.eng and *.rse files would be preferable so we can correct the individual files ourselves using EngEdit 9.
-----
CSI offers a current zip file with merged ENG and RSE files, but I haven't checked whether they are free of the common errors and inconsistencies listed above and only for motors they currently sell.
Aerotech offers a current zip file with merged ENG, but not RSE files, but I haven't checked whether they are free of the common errors and inconsistencies and only for motors they currently sell.
Estes provides nothing that I can find.
-----
To any individuals who might already have the above products due to their own efforts, please don't offer a download link unless you are willing to make the commitment that your product will be properly updated indefinitely. It's up to the manufacturers to have one of their employees spend an hour or two to do this and, later, much smaller amounts of time maintaining their file as new motors are offered and old motors are discontinued.
The individuals gracious enough to create and upload those files for your motors to Thrustcurve.org have already done most of the work for you. Please do the rest so we all don't have to do the same individually in order to have neat and valid motor selections within our sims.
Make sure all available motor delays for a given motor in both ENG and RSE file types are included and correct.
If both file types aren't available on Thrustcurve.org, create the missing type using EngEdit 9 for inclusion in your zipped file mentioned below.
In a motor's RSE file, be sure the motor TYPE is specified.
Make sure your company name or the abbreviation for your company name is exactly the same in all files for your motors.
Correct any other errors or missing information within each file.
CSI, please standardize the motor naming convention within your motor files to be the same as the one you use on your web site. This isn't your fault, of course, and has to do with the preferences of the much appreciated individuals who upload CSI motor files to Thrustcurve.org.
Then, with those nice, clean, consistent and error free motor files:
Create a file name dated zip file with both the ENG and RSE files only for the motors you currently offer for sale and make it available for download. Why only the ones you currently offer for sale? So that we can select a motor from a list of motors that are actually available. The owners of OOP motors can just go to Thrustcurve.org and download the motor file(s) for their OOP motor(s); no need to have those OOP motors polluting everyone else's motor choices within the sim.
Please do not offer a zip file containing all of your motors in a merged *.eng file without also providing a merged *.rse file. Why? Because the by far most popular simulation programs can use RSE files which, unlike ENG files, contain the very useful piece of information about motor type (single use/reloadable).
Also, if you don't make certain that all common errors and inconsistencies mentioned above are corrected (but why didn't you?) in your motor files, individual rather than merged *.eng and *.rse files would be preferable so we can correct the individual files ourselves using EngEdit 9.
-----
CSI offers a current zip file with merged ENG and RSE files, but I haven't checked whether they are free of the common errors and inconsistencies listed above and only for motors they currently sell.
Aerotech offers a current zip file with merged ENG, but not RSE files, but I haven't checked whether they are free of the common errors and inconsistencies and only for motors they currently sell.
Estes provides nothing that I can find.
-----
To any individuals who might already have the above products due to their own efforts, please don't offer a download link unless you are willing to make the commitment that your product will be properly updated indefinitely. It's up to the manufacturers to have one of their employees spend an hour or two to do this and, later, much smaller amounts of time maintaining their file as new motors are offered and old motors are discontinued.
The individuals gracious enough to create and upload those files for your motors to Thrustcurve.org have already done most of the work for you. Please do the rest so we all don't have to do the same individually in order to have neat and valid motor selections within our sims.