About errors in controlling the motor controller.

[White via Tech-talk <tech-talk@aps.anl.gov>]

Hi，

I am using EPICS to remotely control a stepper motor controller (IP: 192.168.0.11), which supports the Modbus-TCP protocol. I want to use the homing trigger function for axis 0. My st.cmd file and db file are as follows, and it runs without errors. but the PV does not connect successfully. The same situation applies to relative motion and absolute motion commands.the Modbus addresses are in the attachment, ( the vendor said that the addresses need to be incremented by one)

 

drvAsynIPPortConfigure(“CAT2”,”192.168.0.11:502”,0,0,0)

modbusInterposeConfig("CAT2",0,2000,0)

drvModbusAsynConfigure("0X1R","CAT2",1,5,1,10,0,100,"CAT2")

 

record(bo, "$(DEVNAME):HOMING_TRIGGER")

{

field(DTYP, "asynUInt32Digital")

field(OUT, "@asynMask(0X1R 1 0x1)")

field(ZNAM,"0")

field(ONAM,"1")

field(SCAN, "I/O Intr")

}

When I enter dbpr, it displays as follows:

epics> dbpr FMC01:HOMING_TRIGGER

ASG :               DESC:               DISA: 0             DISP: 0             

DISV: 1             NAME: FMC01:SEARCH_0_TRIGGER            RBV : 0             

RVAL: 0             SEVR: INVALID       STAT: UDF           TPRO: 0             

VAL : 0

 

 Did I make a mistake somewhere?

 

Thanks

White

Attachment: modbus address.xlsx
Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet