Synchronisation types of M functions (P-CHAN-00041)
P-CHAN-00041 | Synchronisation type of M functions |
Description | In the array m_synch[i], the synchronization type of the corresponding M function is defined. Here, the field index 'i' defines the number of the M function. The value indicates the synchronisation type of the M function, i.e. when a check is made for presence of a PLC acknowledgement. A motion is not executed, or is stopped at the latest towards the end of the block, if no acknowledgement has arrived from the PLC. The synchronisation type is defined as a string constant or a hexadecimal value. |
Parameter | m_synch[i] where i = 0 999 (maximum number of M functions, application-specific) |
Data type | STRING |
Data range | See the table below. |
Dimension | ---- |
Default value | NOT_VALID * |
Remarks | M functions are consumption information and must be fetched (read) by the PLC. This also applies to M functions of the type MOS, MOS_TS, MEP_MOS and MET_MOS. Otherwise, this results in a blocked interface to the HLI in the CNC and as a consequence to an unexpected processing stop.
*Note: The
Caution: The following applies to synchronisation types with associated time and path-related pre-output (MET_SVS, MET_MOS, MEP_SVS, MEP_MOS): If one of these synchronisation types is later changed into one which requires no pre-output value, P-CHAN-00070 (m_pre_outp[i]) must be assigned to 0. Otherwise, a license error is generated in case of microjoints if this function is not licensed or not enabled (seeP-CHAN-00600 Alternatively: P-STUP-00060) is inactive.
Example: m_synch[12] MVS_SVS 0x00000002
Note: Programming a UNS32 variable is permissible for downward compatibility reasons. Example: m_synch[12] 0x00000002 |
Constant | Value | Meaning |
NOT_VAILD | -1 | No valid M function |
NO_SYNCH | 0x00000000 | No output of M function to PLC |
MOS | 0x00000001 | Output of M function to PLC without synchronisation. If the M function is programmed within a motion block, the output of the M function is executed before the movement. M function must be fetched from PLC! |
MVS_SVS | 0x00000002 | Output of the M function to the PLC before the motion block, |
MVS_SNS | 0x00000004 | Output of the M function to the PLC before the motion block, |
MNS_SNS | 0x00000008 | Output of the M function to the PLC after the motion block, |
MNE_SNS | 0x00000020 | Output of M function to PLC after measurement event and removal of distance to go, |
MVS_SLM | 0x00004000 | Late synchronisation, output of M function to PLC within the block, synchronisation during transition to G01/G02/G03 (implicit synchronisation) |
MVS_SLP | 0x00008000 | Late synchronisation, output of M function to PLC within the block, synchronisation by NC command #EXPL SYN (explicit synchronisation) |
MOS_TS | 0x00040000 | Output of the M function to the PLC before motion block without synchronisation, |
MEP_MOS | 0x00100000 | Pre-output of M function with specified path, without synchronisation. |
MET_MOS | 0x00200000 | Pre-output of M function with specified time, without synchronisation. |
BWD_SYNCH | 0x00400000 | Synchronisation of M function during backward motion with MVS_SVS |
FWD_SYNCH | 0x00800000 | Synchronisation of M function during 'Simulated forward motion' based on the defined synchronisation type |
MEP_SVS | 0x01000000 | Output of M function with specified path, synchronisation before next block |
MET_SVS | 0x02000000 | Pre-output of M function with specified time, synchronisation before next block |
FAW_SYNCH | 0x10000000 | Decoding stop (Flush and Wait): Output of M function to PLC and stop of program decoding at block end until program run is completed. FAW_SYNCH can be set in addition to other synchronisation types. M functions with FAW_SYNCH may not be used when tool radius compensation (TRC), polynomial contouring and HSC mode are active. |