.

mpiControlInit / meiControlInit

Declaration: mpiControlInit

 
long mpiControlInit(MPIControl   control)

  Required Header: stdmpi.h
Change History: Modified in the 03.04.00

Description

mpiControlInit initializes the control object. ControlInit must be called after mpiControlCreate(...) and before any other MPI calls in your application. ControlInit establishes communication with the motion controller hardware and initializes any SynqNet networks connected to the controller. Controller communication can occur through direct memory access, device driver, or remote via client/server.

 
control a handle to the Control object
   
 
Return Values
MPIMessageOK  
MPIControlMessageLIBRARY_VERSION  
MPIControlMessageADDRESS_INVALID  
MPIControlMessageCONTROL_INVALID  
MPIControlMessageTYPE_INVALID  
MPIControlMessageCONTROL_NUMBER_INVALID  
MEIControlMessageFIRMWARE_INVALID  
MEIControlMessagePACK_ALIGNMENT  
MEIControlMessageSYNQNET_STATE  
MEIPacketMessageADDRESS_INVALID  
MEIPlatformMessageDEVICE_INVALID  
MEIPlatformMessageDEVICE_MAP_ERROR  
MEISynqNetMessageSTATE_ERROR  
MEISynqNetMessageTOPOLOGY_MISMATCH  
MEISynqNetMessageTOPOLOGY_MISMATCH_FLASH  
MEISynqNetMessageNODE_LATENCY_EXCEEDED  
MEISynqNetMessageNODE_FPGA_VERSION  
MEISynqNetMessageNODE_MAC_VERSION  
MEISynqNetMessageNODE_INIT_FAIL  

Sample Code

 
MPIControl   control; /* motion controller object handle */ 

long         result; 

control =
mpiControlCreate(MPIControlTypeDEFAULT, NULL);
result = mpiControlValidate(control); msgCHECK(result); /* Initialize motion controller */ returnValue =
mpiControlInit(control);
msgCHECK(result);

 

Declaration: meiControlInit

 
long meiControlInit(MPIControl   control
                    const  char  *mpiVersion)
  Required Header: stdmpi.h

Description

meiControlInit initializes the Control object. ControlInit must be called after mpiControlCreate(...) and before any other MPI calls in your application. ControlInit establishes communication with the motion controller hardware. Unlike mpiControlInit(...), it does NOT initialize any SynqNet networks connected to the controller. Controller communication can occur through direct memory access, device driver, or remote via client/server.

 
control a handle to the Control object.
mpiVersion Should always be MPI_INTERFACE_VERSION.
   
 
Return Values
MPIMessageOK  
MPIControlMessageLIBRARY_VERSION  
MPIControlMessageADDRESS_INVALID  
MPIControlMessageCONTROL_INVALID  
MPIControlMessageTYPE_INVALID  
MPIControlMessageCONTROL_NUMBER_INVALID  
MEIControlMessageFIRMWARE_INVALID  
MEIControlMessageSYNQNET_STATE  
MEIPacketMessageADDRESS_INVALID  
MEIPlatformMessageDEVICE_INVALID  
MEIPlatformMessageDEVICE_MAP_ERROR  
MEISynqNetMessageSTATE_ERROR  

Sample Code

 
MPIControl   control; /* motion controller object handle */ 

long         result; 

control =
mpiControlCreate(MPIControlTypeDEFAULT, NULL);
result = mpiControlValidate(control); msgCHECK(result); /* Initialize motion controller, but not SynqNet */
returnValue =
meiControlInit(control, MPI_INTERFACE_VERSION);
msgCHECK(result);

See Also

mpiControlCreate | mpiControlDelete | MPI_INTERFACE_VERSION

 

       Legal Notice  |  Tech Email  |  Feedback
      
Copyright ©
2001-2010 Motion Engineering