Hello Ron,
It seems that the EPICS driver is Ok. The problem may be the communication between the 5500 and pmac.
The controller is without DPRAM. And I use the TPMAC-3-11 for EPICS control.
The VME was setup as,
I90=$39, I91=$4, I92=$FF,I93=$7F, I94=$A0, I95=$1,I96=$A1, I97=$46, I98=$60,I99=$A
In the startup scripts(st.cmd file), the system was configured as,
pmacVmeConfig(0,0x7fa000,0,0xa1,1)
pmacAsynConfig( "PMAC_MBX_PORT_", 0 )
pmacDrvConfig(0,0,0,0,"PMAC_MBX_PORT_0")
AND I loaded a simple db,
record(stringin, "motorStrCmd") {
field(FLNK, motorStrRsp.PROC PP MS")
}
record(stringout, "motorStrRsp") {
field(DTYP, "PMAC-VME ASCII")
field(DOL, motorStrCmd.VAL NPP MS")
field(OMSL, "closed_loop")
field(OUT, "#C0S1 @#8")
}
After I executed the “caput motorStrCmd ‘j=1000’” command, the ioc printed no error information. But the pmac controller seemed to have no resonse. The pewin32pro software was running simultaneously.
The debug information shows:
0x1ec62bd0(cas-client): devPmacMbxSo_write command [#8j=1000]
0x1ec62bd0(CAS-client): drvPmacMbxScan: rngBufPut completed.
I am looking forward to your reply.
Best regards.
On 12/6/2016 11:03 PM, zzh wrote:
the 5500 and pmac will both crash immediately.
Is there a crash message from VxWorks on the 5500? If so, what exactly is the message?
Does anyone has experiences with the 5500+pmac-vme-mailbox?
I have some experience with Delta Tau Turbo PMAC2 VME Ultralight used with various VME CPU boards (5100/6100), but not the 5500.
Ron