MotoHawk-FAQ
Latest Version of MotoHawk
2010a Beta3
This is Beta 3 for features in the MotoHawk 2010a release.
- Support for MATLAB 7.5 (R2007b) to MATLAB 8.0 (R2010a) and, in a subsequent service pack, MATLAB 8.1 (R2010b).
This release supports MATLAB 7.5 (R2007b) to MATLAB 7.9 (R2009b).
Support for (pre-release) MATLAB 8.0 (R2010a) is not yet scheduled (The Mathworks made this Pre-Release available to our developers today 14-Dec.).
- New features! This beta contains additional structural support for new features.
- MPC 5xx targets: Add support for encoder 36+1 crank with 12+1 cam
- ECM70: Add support for FrequencyIn behavior on CNK, CNKDG, CAM pins
- ECM70: Add support for ECM-S12X-070-1002 (ECM70-1002) module
- CCP Slave protocol handler: change default behavior to IDLE_EVENT-triggered priority
- General updates and improvements.
- For registered users, MotoHawk 2010a Beta 3 may be downloaded from the mcs.woodward.com website, Support, Downloads page. (You must be logged into the website for the links below to work. If clicking on the link takes you to a blank page, please go to mcs.woodward.com/ the MSC website and log in. Access level of "beta customer" is required.)
MotoHawk 2010a Beta 3 for MATLAB 7.5 (R2007b) to 7.9 (R2009b):
[[1]]
Release notes for MotoHawk 2010a Beta 3 can be found at:
[[2]]
IMPORTANT!! Please use Windows Control Panel "Add/Remove Programs" to un-install any previous MotoHawk install before running these new installers.
IMPORTANT!! MotoTune / MotoServerRuntime 8.13.7.87 (or later) are REQUIRED for MotoHawk 2010a Beta 3. These may also be downloaded from the mcs.woodward.com website, Support, Downloads page.
IMPORTANT!! If you have been using GCC in earlier MotoHawk releases, you will need to change your GCC installation for MotoHawk 2009b Beta 3 and subsequent releases.
IMPORTANT!! For customers using MotoHawk Custom Security blocks, you must use version 1.0.4 (or newer) of your security block for MotoHawk 2009b Beta 3 and subsequent releases.
MotoHawk 2010a releases require a valid MotoHawk license to do a code-generation build. You can verify the licensing in your silver MotoTron USB licensing token (dongle) using the MotoTron License Viewer (Start, All Programs, MotoTools, MotoTron License Viewer). "MotoHawk (v5.0)" or "MotoHawk (2010a)" is required to use MotoHawk 2010a releases. To use MotoHawk 2010a releases, most users will need to have MotoHawk 2010a permissions added to their license tokens, and may also need to update their software maintenance agreements.
Memory Questions
How is memory initialized, without having to build a specific flash file, for a new application?
- There should be an init checkbox in the fixed Non-Volatile manager window. This will allow you to say if you want the app to load the default values or values previously on the module. This should take care of initializing the values yourself.
- Similarly, the same result is done by performing an offline calibration change in the System | NonVolatile Storage | NonVolatile Storage Config | NonVolatileRestoreOnFirstStartup calibration. After changing this cal to "Load saved application values on next startup," you just need to merge back into your programming file, and then use the merged file for programming.
Software Compatibility
Can MotoHawk run on a Linux System?
- MATLAB 64-bit versions are not supported. The "MEX" files used by many MotoHawk blocks are built for 32-bit MATLAB only (.MEXW32); 64-bit uses a different binary MEX file format.
- We have a couple of customers who are using MotoHawk and MotoTune on Windows Vista 64-bit with MATLAB 32-bit. They report:
- After installing MotoServerRuntime, MotoTune, and MotoHawk (using right-click install-as-administrator), copy the entire directory tree "C:\Program Files (x86)\MotoTron\..." to "C:\Program Files\MotoTron\..." (substitute "Woodward" for "MotoTron" for MotoHawk 2009b and later releases). When it is time to uninstall, remember to delete the "C:\Program Files\MotoTron\..." copy before uninstalling with Add/Remove Programs.
- Windows Vista (32-bit) is known to have dongle driver problems. Not sure what you will encounter with this configuration.