There are two types of messaging modes, custom messaging and messaging mapping.
The custom messaging API is used to pass MotionSolve
message directly to a user-written subroutine (MESSAGE_SUB). Messaging
mapping is used to overwrite MotionSolve standard
messages in the log file, or append your additional comments to the standard MotionSolve message.
Messaging API
MotionSolve calls MESSAGE_SUB at every instance when it accesses
the log file.
You access the same ID tagged message as passed to the MotionSolve
log file via MESSAGE_SUB as shown below:Figure 1. Example of a Standard MotionSolve Log
File