PISO-CPM100(U) / PCM-CPM100 user manual (ver. 2.02) Dec/03/2012 ----------------- 78
4.5.44. CPM100_InstallPDO_List
Description:
This function is similar with the CPM100_InstallPDO function. It can
install the old or new PDO object in the PDO object list of the CPM100.
It is the same as CPM100_InstallPDO. But the
CPM100_InstallPDO_List doesn’t send any message to check if the
PDO object exists in the real slave. It just changes the list in the memory
of the CPM100. It means that user can use this function to install PDO
and change PDO mapping data arbitrarily without disturbing the
CANopen network. After using this function, the CPM100 will process
the slave PDOs which have the same IDs configured by the function
CPM100_InstallPDO_List. It is very useful when the CPM100 is running
in listen mode. User can use the function CPM100_RemovePDO_List to
remove the PDO object which is installed by CPM100_InstallPDO_List.
Syntax:
WORD
CPM100_InstallPDO_List(
BYTE
BoardNo,
BYTE
Node,
WORD
Cobid,
BYTE
RxTx,
WORD
PDO_No,
BYTE
EntryUse,
DWORD
*EntryData,
BYTE
BlockMode)
Parameter:
BoardNo:
[input] CPM100 board number (0~7).
Node:
[input] Slave device Node-ID (1~127). If the “Node” parameter is
the CPM100 Node-ID, the parameters, EntryUse & EntryData,
will be useless. In this case, users can use the function
CPM100_InstallRxPDOISR or CPM100_InstallRemotePDOISR
to install the users’ callback function to process the received
PDOs of the CPM100.
Cobid:
[input] COB-ID used by the PDO object.
RxTx:
[input] PDO type (0: RxPDO, 1: TxPDO).
PDO_No:
[input] PDO mapping object No (1 ~ 512).
EntryUse:
[input] Total entry of mapping object that will be installed.
*EntryData:
[input] Double Word array information of mapped application
object. For example:
