MotoHawk FAQs
From NewEagleWiki
Application - MotoHawk Functions
The MotoHawk rapid-prototyping software development environment installs as a toolbox in Matlab. The control algorithm architecture and development process begins in Simulink. MotoHawk is an added library within the Matlab program. The benefit of using the MotoHawk block set is that it is easy to access ECU module hardware features such as crank/cam position inputs, analog and digital (switch or frequency) inputs, and Pulse-Width-Modulated (PWM) or discrete outputs (including crank/cam-synchronized control of fuel injector and spark timing outputs). There are "calibration" and "probe" memory access blocks and 1D and 2D table blocks, all of which may be accessible in real-time using MotoTune. MotoTune is a calibration/display tool.
Duty Cycle of a PWM Signal
The Motohawk_frequency_in block in the Advanced Digital I/O section of MotoHawk has a selectable option to provide DutyCycle in the form of 0-4096 counts. Note this will be the duty cycle that the signal is over the threshold. If you want the duty cycle under the threshold you will need to take 4096 - the output of this block. This number will work the best for short rise and fall times at the transitions.
DRVP Function
DRVP is an INPUT to the module. It is how we source power for high side drives and H-bridge outputs (ESTs may be powered this way as well on some modules).
Note, this input may come from the MPRD (Main Power Relay) so that these actuations will be powered or de-powered under the control of MPRD. It may also come from battery if the afore mentioned drivers need to be powered ANY time the module is active.
Producing an Analog Output
At present, there is no hardware support for an analog voltage output (say, 0-10Vdc output) on external pins on Woodward MCS control modules. However, there are methods to provide such a signal, including (1) various low-pass R-C filter options and (2) commercially available devices, some of which have a CAN bus interface. For a project with significant volume, Woodward can also offer custom hardware minor or major variants with specific capabilities, upon request.
Low-Pass Filter Options In Harness
There are a number of ways to generate an analog voltage output, for instance 0-10V output:
• an R-C low-pass filter circuit with PWM input/control, using an analog input for closed-loop feedback.
• an R-C low-pass filter circuit with digital potentiometer input controlled by an ESTx, using an analog input for closed-loop feedback.
• an R-C low-pass filter circuit with external transistor and PWM control, using an analog input for closed-loop feedback.
Notes: The low-side driver output would be operated as Pulse-Width-Modulation (PWM) with high frequency and duty cycle to achieve desired output voltage, as monitored by analog input AN6M. The R and C values must be designed for the load impedance and to provide suitably fast response. The PWM duty cycle is varied to control the external PNP transistor, which in turn controls build-up of charge in, and voltage across, the capacitor.
Commercial Off-The-Shelf Devices
Method: Use an ESTx TTL-level PWM output channel to control the 5B45-05 analog output module for 0-5Vdc output.
- Frequency-to-voltage converter: Analog Devices, 5B45-05 analog module.
- Contact: Signal Conditioning Solutions, Novi MI, phone 248-615-4441, Signal Conditioning Solutions
- CAN-to-voltage converter: ASCON, AO-08HL analog output module 8-channel.
Method: Send messages to the device using CANopen protocol for 0-10Vdc, 0-20mA, 4-20mA output.
- Contact (factory): ASCON Corporation, 1884 East Fabyan Parkway, Batavia, Illinois 60510, phone 630-482-2950, fax 630-482-2956, www.asconcorp.com; Davide Bugatti (Technical Manager) (d.bugatti@asconcorp.com), Steve Rakers (s.rakers@asconcorp.com).
- Contact (distributor): Schlemmer Associates, 800 Compton Road Unit 35, Cincinnati OH 45231, phone 513-522-8340, fax 513-522-2727; Bill Kief (Sr. Sales Engineer) (cell 513-910-9594, wkief@schlemmerassociates.com).
- CAN-to-voltage converter: Axiomatic TDAX030500, 4 analog signal output CAN controller.
MotoHawk Blockset
The MotoHawk Blockset supports many different behaviors including I/O, fault management, calibration, online viewing via calibration tools, and many more.
MotoHawk Block Categories
CCP CAN Protocol Handler
Target Definition Block
Target Definitions for MotoHawk
ECM5554-112
MotoHawk Target Definition Block target names to use:
- ECM-5554-112-0902-kD: PCM0902 module with knock development interface, DV release hardware
- ECM-5554-112-0902-kP: PCM0902 module with knock development interface, PV release hardware
- ECM-5554-112-0902-xD: PCM0902 module, DV release hardware
- ECM-5554-112-0902-xP: PCM0902 module, PV release hardware
Use this target for ECM-5554-112-0902-F00 ("PROD") and ECM-5554-112-0902-CP0 ("DEV") modules.
- ECM-5554-112-0904-xD: PCM0904 module, DV and PV release hardware
Use this target for ECM-5554-112-0904-F00 ("PROD") and ECM-5554-112-0904-CP0 ("DEV") modules.
3rd Party I/O Interfaces
Thermocouple to Analog Converter
A thermocouple to analog converter can turn any chart recorder, analog or digital voltmeter into an accurate, wide range temperature measuring instrument. For more information, please visit the following link:
http://www.omega.com/ppt/pptsc.asp?ref=TAC80B&nav
UEGO to CAN
http://www.innovatemotorsports.com/products/lc1.php
PWM to Analog Output
The New Eagle EVIM receives a PWM signal from a MotoHawk PWM output, and can convert into a pure analog, 0-5 volt output. Single or multiple channels are available.
Build Counter
Is there a convenient way to reset the motohawk_build_version counter? For instance, if I copy a model for a new project I’d like to reset the build counter?
- There is a MotoHawk command to update this value. To do this have the model open and go to the MATLAB command prompt and type in:
- number = ‘000’; %the value between the ticks can be any number you want motohawk_build_version(bdroot, number);
- This will set the 3 character build version to 000. You can also place the value directly into the expression just remember to use the ticks(‘).
- You can also type “help motohawk_build_version;” from the command line and get help for more advanced features.
CAN Messaging
How to send / receive a message greater than 8 bytes
- A multi-page CAN message would satisfy sending or receiving messages greater than 8 bytes. Typical application would include message PGN65251-Engine Configuration found in the SAE J1939 protocol.
- The Motohawk 'CAN Raw' and the 'CAN Messages' block would both be utilized in setting up a multi-page message.
STARTUP_Event Trigger with Custom Memory Initialization App
If the STARTUP_EVENT function trigger is placed inside the main foreground block, would it execute on startup before the memory initialization application starts running just like it would if it were outside?
- The startup event only triggers once so its output will basically be a constant once it has ran. I am not sure what the memory initialization app needs to do to initialize the memory, but you probably need to do that in a periodic task. There it will have time to interact with components in the system outside the module. Try setting a datastore flag to enable the initialization code, and when it has finished the initialization, unsets the flag so the main application starts running. This can be done with enabled subsystems.
Do I need to explicitly keep the main foreground loop from running until the startup_code has run with a flag or does Motohawk do this for me (run the startup event stuff before the main application loops starts). In other words, is it a sequence of: STARTUP_EVENT --> Main Application, or do they run in parallel (with the startup stuff obviously only running once)?
- The application will wait for the startup event to finish before it starts any of its code.
Application - Engine Control
How Smart Coil Works with MotoHawk's Ignition Ouput
The battery (coil supply) voltage, engine speed, engine load, and air/fuel ratio are taken into account in determining both the proper spark timing and needed coil dwell. These calculations are generally made in the base software time frame and are updated by default at 200 Hz, regardless of engine speed.
Once proper timing and dwell are determined for a given engine condition, a request is sent to the TPU for execution as a single pulse output for a given cylinder, cylinder pair, or distributor, where the rising edge 5-volt signal level pulse is sent to a high impedance devise (Smart Coil). The pulse energizes a transistor in the Smart Coil to turn on its primary. The 5-volt signal is then timed to stop energizing the primary and force the spark on the falling edge of the control signal as it de-energizes the transistor, forcing the coil energy to discharge through the secondary.
The output of the ECM is an on/off signal with no modulation for current control. There is no feedback to the ECM for primary or secondary coil current as the property of the coil determines energy storage from how long it is energized, as based on the supply voltage and coil inductance. For supply voltages and coil impedance used, the inductance of the coil is such that the coil current does not saturate for the dwell times (angle) we specify. Thus there is no need to measure current as it can be calculated quite accurately if needed. The only failure in current is total (all or none) resulting in a correct spark or total misfire, which can also be detected.
How quickly does MotoHawk Start an Engine during Crank?
The engine should start 2 revolutions from receipt of crank pulses. Some patterns can sync within 1 revolution.
What Encoder Patterns are Supported in MotoHawk?
MotoHawk™ supports a variety of crank and cam encoder patterns that continues to grows with each release. The following comes from MotoHawk version 2010a SP 0.
These patterns can be selected by going to the Motohawk Encoder Definition block as shown in the picture below:
N Teeth with X Missing Encoder Style
General Description
The N teeth with X missing encoder style describes those encoder patterns that consist of N equidistant teeth distributed about a wheel with X adjacent teeth then removed. The most common form of this pattern is the "N minus 1" and "N minus 2" patterns. The 60 minus 2, sometimes known as 58X is a member of this encoder style as is 36 minus 1.
Synchronization
The missing teeth are used to communicate synchronization information. Speaking generally, a single missing tooth is detected if a synchronous crank encoder edge is not detected within 1.5 times the previously observed tooth period. If there were two missing teeth then the multiplicand is 2.5 times the previous period.
A crank synchronization error will be flagged if the correct number of missing teeth have been observed without having observed the correct number of real teeth. Thus the 60 minus 2 pattern would issue a synchronization error if two missing teeth were observed without having previously observed 58 physical teeth.
A resynchronization can temporarily impact the behavior of crank-synchronous blocks. Impacts include a pulse not scheduling as expected, having it occur twice, or being malformed. The system will recover, but the initial impact is unavoidable because the correction to the crank angle position results in a step change in position that may disrupt the underlying pulse scheduling software.
Tooth and Halfmoon Cams
Cam No Go Region
The Tooth Cam and the Halfmoon Cam are both considered to be of tooth cam style. Neither edge of the halfmoon cam nor the synchronous edge of the tooth cam should fall within the missing tooth region for all engine operating conditions. Unreliable crank encoder synchronization may occur (which will lead to encoder errors) if an edge transition were to occur within this region.
No go region for the 60 Minus 2 (58X) Encoder
Halfmoon Cam Width Tolerance
The width of a half moon cam should approximate 360 crank angle degrees. That is, a cam edge should be observed approximately every 360 crank angle degrees. The tolerance will vary depending upon the number of teeth in the system. For a 60 tooth crank encoder, consecutive cam edges shall be:
- at least 330 crank angle degrees apart, and
- no more than 390 crank angle degrees apart
Utilizing a Tooth Cam configuration in place of the halfmoon will still allow a fully featured crank-synchronous model to be developed. Therefore a Tooth Cam can be used in place of a halfmoon cam if there is an issue with the width. Cam errors will be reported if a halfmoon is in use that does not conform to the width restrictions.
Halfmoon Cam Sensor Assumptions
The halfmoon cam arrangement assumes that a zero speed sensor is in place. Such a sensor is able to reliably report the presence or absence of metal with minimal to no rotation. A halfmoon should be treated as a tooth cam if such a sensor is not available.
Crank Teeth from Cam Edge to Crank Tooth Zero Setting
The crank teeth from cam edge to crank tooth zero setting is used to assist ControlCore in making an informed guess as to what the half cycle state is when it first observes missing teeth. Correctly setting this value will improve start quality. The setting is ignored when it has a value of -1. Instead ControlCore determines an appropriate value that won't be optimal. A positive value implies that the setting is to be used and communicates to ControlCore the number of crank encoder teeth that need to be observed from speed zero before the system can categorically conclude whether the cam edge would have been observed if it was going to occur prior to the observed missing teeth.
The figure illustrates a setting of 3 teeth. If at least 3 teeth had been observed before the first missing tooth is observed (from speed zero) and a cam tooth has not been observed then the system knows that the detected missing tooth corresponds to the half-cycle that does not have the cam tooth. The system can't make that assumption if 2 or fewer teeth had been observed before the first missing tooth.
Duramax Cam
Duramax Topology
The duramax cam consists of three pulses distributed about two engine revolutions. ControlCore uses the narrow pulse widths depicted by the figure as half-cycle markers. The width of these pulses are defined as the number of teeth in an engine revolution divided by 8. Thus for a 60 tooth crank encoder the narrow width could be no wider than 7 crank encoder teeth.
Duramax Cam Alignment
The cam may have any alignment with the crank encoder provided the edge that completes the narrow width does not fall within the missing tooth region and that exactly one narrow width resides in each half-cycle.
Count the number of teeth from the start of the narrow width until the missing tooth region to calculate the Crank Teeth from Cam Edge to Crank Tooth Zero setting.
Duramax Cam Sensing Technologies
The cam uses pulse width to determine the half-cycle marker and as such must utilize a sensing technology that will accurately convey pulsewidth information. Thus this cam pattern does not support variable reluctance (VR) sensing.
Coyote Cam
Coyote Topology
The coyote cam consists of 8 pulses of varying widths. ControlCore looks for a sequence of widths in order to provide half-cycle synchronization information to the crank encoder.
Coyote Cam Alignment
Cam alignment is restricted to the range dipicted in the figure. Set the Cam Sync Polarity to match the figure. Coyote Cam Sensing Technologies
The cam uses pulse width to determine the half-cycle marker and as such must utilize a sensing technology that will accurately convey pulsewidth information. Thus this cam pattern does not support variable reluctance (VR) sensing.
X+1 Cam
X+1 Topology
The X+1 CAM compares the widths between CAM teeth to detect a narrow width + 1 pulse advanced or retarded within normal CAM teeth. The presence or absence of the +1 CAM tooth provides half-cycle synchronization information to the crank encoder. Normal CAM teeth are the equally spaced teeth. The +1 tooth occurs once per cycle within the same normal tooth pair.
X+1 Cam Alignment
If the CAM sync point is on or can move either side of the CRANK sync then encoder errors will occur, and TDC will move by 360degrees
MPC5xx module specific limitations
There must be at least two REAL (not missing) CRANK synchronous edges between any two CAM pulses.
- Encoders with 1 or 2 missing teeth: The CRANK Sync point is located between the last missing tooth and the next real tooth.
- Encoders with 3 or 4 missing teeth: The CRANK Sync point is located on the 1st real tooth after the missing.
Prosak Manual
The Knock detectioin on the ECM-5XX (48, 80, 128) uses the Motorola Prosak IC. The application / programming manual is available to customers upon request.
Application - CAN Systems
Show an example of configuring the MotoHawk CAN Block
Those settings are exposed by the custom CAN baud rate selection:
Here is an example of the block correctly configured for 500 kbaud operation on a ECM5554:
Purchase MotoHawk
Click Here to Purchase MotoHawk - Rapid Control Development System for the ECU
Maintenance and Support Policy
MotoHawk Maintenance
New purchases and maintenance purchasers of MotoHawk are entitled to the ability to upgrade their MotoHawk for 2 major releases of MotoHawk (i.e. 2009B and 2010a), and support to submit bug fixes / feature requests. The license is controlled via the USB dongle.
MotoHawk Support
New purchases and maintenance purchases have the ability to submit problems and make feature requests of the product (defined as "standard support", but are not entitled to applications consulting which is defined as extensive installation support, general trouble shooting, and general usage of Mathworks, MotoHawk, embedded hardware and software issues. These items are provided in applications support contracts that are sold via monthly retainers, time and Material consulting, or via a production supply agreement for modules.
Current MotoHawk customers are entitled to the ability to download additional documentation, participating on forums for trouble shooting and applications support, and the wiki.
MotoHawk customes are encouraged to attend a training class from New Eagle or a qualfied partner, or use the consulting contract as a means to gain experience with the product. For information on the training course, visit MotoHawk Training
Software
Latest Version of MotoHawk
MotoHawk 2010a Beta 6 has been released! And, MotoTune / MotoServerRuntime 8.13.7.120 have been released!
These releases support Windows XP (32-bit and 64-bit), Windows Vista (32-bit and 64-bit), and Windows 7 (32-bit and 64-bit). Please note that this new support for 64-bit versions of Windows still requires using the MATLAB 32-bit versions at this time. Support for MATLAB 64-bit versions is presently planned for MotoHawk 2010b, later this year.
This is Beta 6 for features in the MotoHawk 2010a release.
This beta provides a new installer experience, allowing for simultaneous "side-by-side" installs of different MotoHawk versions and easy re-configuration between installed MotoHawk releases using the MotoHawk Version Selector (from the Windows Start menu). The side-by-side installer feature and MotoHawk Version Selector are described further in this Woodward MCS wiki article Side-by-Side Installation.
• Support for MATLAB 7.5 (R2007b) to MATLAB 7.10 (R2010a) and, in a subsequent service pack, MATLAB 7.11 (R2010b). • Support for Windows XP (32-bit and 64-bit), Windows Vista (32-bit and 64-bit), and Windows 7 (32-bit and 64-bit), using MATLAB 32-bit versions. • Side-by-Side installer with MotoHawk Version Selector. • MPC 5554 112-pin targets**: Add support for 48-2 encoder pattern. MPC 5554 112-pin targets**: Change FUELPR output driver to hardware-disable when STOP is asserted.
- ECM-5554-112-09xx (PCM09xx) and GCM-5554-112-1001 (CCM1001) (1751-6456, 1751-6457) modules
• MPC 5xx targets: Add support for encoder 36+1 crank with 12+1 cam MPC 5xx targets: Add support for encoder 36–2 crank with X+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 6 may be downloaded from the New Eagle Downloads page. (You must be logged into the wiki for the links below to work).
MotoHawk 2010a Beta 6 for MATLAB 7.5 (R2007b) to 7.10 (R2010a) and Release Notes:
MotoHawk 2010a Beta 5
MotoHawk 2010a Beta 5 has been released and is available under the DOWNLOADS page, but you must have a login. Email support@neweagle.net for a login.
This is Beta 5 for features in the MotoHawk 2010a release.
- Support for MATLAB 7.5 (R2007b) to MATLAB 7.10 (R2010a) and, in a subsequent service pack, MATLAB 7.11 (R2010b).
This release supports MATLAB 7.5 (R2007b) to MATLAB 7.9 (R2009b).
Support for (pre-release) MATLAB 7.10 (R2010a) is not yet available.
- New features! This beta contains additional structural support for new features.
- MPC 5554 112-pin targets**: Add support for 48-2 encoder pattern.
- MPC 5554 112-pin targets**: Change FUELPR output driver to hardware-disable when STOP is asserted.
- ECM-5554-112-09xx (PCM09xx) and GCM-5554-112-1001 (CCM1001) (1751-6456, 1751-6457) modules
- MPC 5xx targets: Add support for encoder 36+1 crank with 12+1 cam
- MPC 5xx targets: Add support for encoder 36–2 crank with X+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.
Does Motohawk run on a 64bit OS?
As of right now, 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.
Some customers 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. '
What are some know problems with running Motohawk on Windows Vista?
Dongle Driver
Windows Vista (32-bit) is known to have dongle driver problems.
Error 1925 (insufficient privileges)
This error occurs when the install process is not run as Administrator. In Windows Explorer, right click on MotoHawk_(Version) and select 'Run as Administrator' rather than 'Open' or simply double clicking.
What Mathworks products / toolboxes are required or recommended with MotoHawk?
Required = Matlab, Simulink, RTW Embedded Coder
Recommended = Stateflow, Stateflow Coder
MotoHawk/MATLAB Version Compatibility
MotoHawk versions have been designed so that they work with all versions of MATLAB, 6.5.1 to the current. Beginning with MotoHawk 2009a, support for older MATLAB versions is being discontinued. See table below for MotoHawk / MATLAB version support:
| MATLAB Version | MotoHawkVersion | |||||
| 2008a | 2008b | 2009a | 2009b | 2010a | 2010b | |
| 6.5.1 | Y | Y | N | N | N | N |
| 7.0 | Y | Y | N | N | N | N |
| 7.0.1 | Y | Y | N | N | N | N |
| 7.0.4 | Y | Y | N | N | N | N |
| 7.1 | Y | Y | N | N | N | N |
| 7.2(R2006a) | Y | Y | N | N | N | N |
| 7.3(R2006b) | Y | Y | N | N | N | N |
| 7.4(R2007a) | Y | Y | Y | N | N | N |
| 7.5(R2007b) | Y | Y | Y | Y | Y(A) | N |
| 7.6(R2008a) | Y | Y | Y | Y | Y(A) | N |
| 7.7(R2008b) | Y | Y | Y | Y | Y(A) | Y(A) |
| 7.8(R2009a) | N | Y | Y | Y | Y(A) | Y(A) |
| 7.9(R2009b) | N | N | Y | Y | Y(A) | Y(A) |
| 7.10(R2010a) | N | N | N | Y(B) | Y(A) | Y(A) |
| 7.11(R2010b) | N | N | N | N | Y(B) | Y(B) |
A-in beta release, B-not yet available
MotoHawk License Viewer
The new MotoHawk License Viewer is installed with MotoHawk, beginning with release 2008a. Use this Viewer to see what MotoHawk Tool licenses you have - including Token, NodeLocked, or Evaluation types - and what permissions are included.
Launching License Viewer
To start the License Viewer, on your Windows desktop:
Click on Start -> All Programs -> MotoTools -> MotoTron License Viewer
The License Viewer Dialog appears (see below).
Using License Viewer
In the License Viewer dialog (see below), current licenses are listed located in the left pane, and detailed information is displayed on the right (for the selected license).
Beginning with MotoHawk 2009b, the license viewer now displays the MotoHawk release name (200Nx) rather than the version.
A license can be one of three types, as indicated by the letter listed with the license:
- N = NodeLocked
- E = Evaluation
- T = Token (dongle).
To view license information:
- Click on the license on the left, to show the corresponding license information on the right.
- Click the plus (+) next to the license to expand the list content and show what is included with the license. Click the minus (-) to contract the list content.
The MotoHawk expanded lists each include the modules which are accessible with the respective license. The right side for each MotoHawk license displays information about the license currently highlighted, including Product Name, Version, License Type, and Token Serial Number.
Note: MotoHawk Licenses have a version next to them that denotes the MotoHawk version licensed:
- v1.0 = 2008a
- v2.0 = 2008b
- v3.0 = 2009a
- v4.0 = 2009b
Beginning with MotoHawk 2009b, the license viewer now displays the MotoHawk release name (200Nx) rather than the version.
How do I identify what my unmarked dongle is licensed for?
If the dongle is unmarked and it is not even known if there's a Motohawk or Mototune on it, you should first plug it in and use the Moto Tron License Viewer to confirm if its a Motohawk or not. (A Motohawk license can also be verified if you go to the Command Window in MATLAB and type in motohawk_check_license . If it gives you an ans = 1, that means it has a motohawk license and if it gives a 0 (zero) then you are sure that its not activated for Motohawk.)
And then for Mototune only dongles, there's no such test you could perform. A way of knowing that a Mototune dongle works is to Start Mototune and see the Title Bar. If it has a designation (a name like <company name> or New Eagle LLC), it means that there's a Mototune license on it. If there is no license, the title bar would say 'Unlicensed'.
To pull out the license information, you could use the Motoserver, the instructions for which are as follows:
1. Start Mototune 2. Go to the Motoserver icon on the right side of taskbar, right click on it and click on 'About Motoserver'. 3. A small window shows up on the screen and you could click on 'License Info'.
While doing the same you would see a button called 'About token' when you press 'License Info'. On clicking that, you will be able to see information about the dongle. In case you need more information about what you can do or can not do with that license, you can forward us the 'Serial Number (S/N)' from there at support@neweagle.net. Using that, we can extract more information from here.
Just as a reminder, the dongle needs to remain plugged in at all times when you are trying to find license info on MATLAB, Motoserver, License Viewer OR Mototune.
Can I speed up the build on the ECM5554-112?
MotoHawk 2010a Beta 5 made improvements in this area to make the build times between 55xx and 5xx much closer.
Installing MotoHawk
Side by Side Installer
Older versions of MotoHawk only allowed one version of MotoHawk to be installed at any one time. The MotoHawk Side-by-Side installer, new with MotoHawk2010a, allows for many versions of MotoHawk to be installed at one time along with one legacy MotoHawk (MotoHawk2009bSP0 or earlier). An example of this is having one project in the final stages of development or already in production using MotoHawk such as 2009a, and starting a new project and wanting to use the newest software. The Side-by-Side installer allows you to have the two working environments installed at the same time and switch between them easily. To allow this easy change, the Side-by-Side installer includes a MotoHawk Version Selector which allows you to select which version of MotoHawk will run with a specific version of MATLAB.
Changes to Installation and Use Procedures
Installation
- Old
- Use Add/Remove programs to uninstall any previous versions of MotoHawk.
- Run Installer and select the versions of MATLAB with which to integrate MotoHawk.
- New
- Run installer to install MotoHawk. At the end there is a prompt to launch the MotoHawk Version Selector.
Use
- Old
- Launch MATLAB and it will start MotoHawk if it was integrated at Installation.
- New
- Use MotoHawk Version Selector to integrate a version of MATLAB with a version of MotoHawk.
- Launch MATLAB and it will start the version of MotoHawk with which it was integrated.
Using MotoHawk Version Selector
The Side-by-Side installer also installs the MotoHawk Version Selector tool. To get to this program, go to start->All Programs->Woodward->MCS->MotoHawk->MotoHawk Version Selector. After you have selected MATLAB and MotoHawk versions, launching the selected versions of MATLAB will launch MotoHawk.
Select MATLAB version
The top has a drop down list titled MATLAB Version. This drop down will list all versions of MATLAB on the machine. Select the version of MATLAB for which you want to change the MotoHawk Version or select the check-box below that is labeled "Use same MotoHawk Toolbox for all MATLAB versions." Note that all MotoHawk versions will not support all MATLABs, so the Side-by-Side installs may be grayed out if the check-box is used
Disabled
This radio button selection will allow MATLAB to launch without initializing any version of MotoHawk. It is also the default choice on MATLAB versions the most recent installer supports.
Side-by-Side Installation
All of the Side-by-Side installations will be listed in radio buttons in the Select MotoHawk Toolbox Version panel. Select the radio button next to the version you want to use and it will integrate into the selected version of MATLAB.
Using MOTOHAWK_DIR Environment Variable
This feature uses the Environment Variable MOTOHAWK_DIR to point to the installation location of the version of MotoHawk you want to run. To change the environment variable do the following based on OS version:
- Windows XP
- Right click on my computer and select properties
- Select the advanced tab
- Click the Environment Variables button at bottom of page
- Find MOTOHAWK_DIR and select edit button, or click the new button if MOTOHAWK_DIR does not already exist.
- Change the Variable value to the directory MotoHawk is installed. (eg: "C:\Program Files\Woodward\MotoHawk" without the quotes)
- Windows Vista / Windows 7
- Right click on my computer and select properties
- Select the Advanced System settings text on the left side of the window
- Click the Environment Variables button at bottom of page
- Find MOTOHAWK_DIR and select edit button, or click the new button if MOTOHAWK_DIR does not already exist.
- Change the Variable value to the directory MotoHawk is installed. (e.g.: "C:\Program Files\Woodward\MotoHawk" without the quotes)
Custom / Legacy MotoHawk Version
This radio button allows you to specify a path to the MotoHawk install directory.
Starting a New Project
Try the command in the Matlab window "Motohawk_project addname" to create a new project called "add name"
Compilers
HCS12X Metrowerks Compiler
There is a free version for the S12X compiler. We are looking for Beta testers to determine whether this will work or whether you need the professional version for $1995. http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW-HCS12X
MPC5XX / MPC55XX Compiler Options
Greenhills
The Greenhills PowerPC compiler is recommended for production programs. It can be purchased from New Eagle in the form of a node-locked, dongle, or networked license. GHS 3.6 and 4.2.1 on both the 5xx and 55xx MotoHawk controllers.
Greenhills Demo License
Greenhills compilers can be demonstrated for 30 days by downloading the software. After installing, go to Start/Multi…./Licensing/License request Generator. It automatically takes you to the Green-Hills web site and requests the license. Typical turn-around is 24 hrs.
GCC (Free)
There is a GCC version of the license downloadable for the MPC5XX and MPC55XX modules. Download the file from [[1] GCC Compiler]
MotoHawk Application Library Notes
Vector DBC to M-file Conversion
Product:
Common Errors
Error while running the .exe file on XP:
This occurs because the motohawk_candb2mhcan application has a dependency on the Vector canDBlib. Make sure that all files from the Vector CanDBlib disk are installed. Installing the files should place the cdbmsmo.dll on the computer. If it is not installed to the Windows\System32 directory, than simply make sure the motohawk_canb2mhcan.exe and the cdbmsmo.dll are in the same directory.
Links to Outside Customers / Users / Testimonials
Dual Fuel Diesel (CNG & Diesel)
Vehicle Height Control System
R2 Dual Fuel Testimonial
http://www.r2powertrain.com/Clean%20Air%20Power%20uses%20MotoHawk%20exclusively.pdf
90% Reuse Between Applications
Azure Dynamics Mathworks Testimonial
Snowmobile Control System
http://www.mtukrc.org/download/madison/madison_ze_design_paper_2010.pdf
Commercial EV / HEV Trucks
http://watch.bnn.ca/clip311865#clip311865
New Eagle Supervisory controller.
Hawk Dual-Fuel ECU Application
http://www.cleanairpower.com/admin/pdf/CAP_Advanced_Dual-Fuel_Engine_System.pdf
Target-based prototyping system applied to fuel control
Marine Vessel Control Systems
HCCI Motorcyle Application
University of Tapei Research Paper
| Whos here now: Members 0 Guests 0 Bots & Crawlers 1 |
