Revision as of 15:38, 7 January 2010

Software Compatibility

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?

Windows Vista (32-bit) is known to have dongle driver problems.

MotoHawk Library Blocks

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 something like that 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.

@@ Line 12: / Line 12: @@
 =MotoHawk Library Blocks=
 ==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?'''''
+===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 something like that 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.

MotoHawk-FAQ: Difference between revisions