Fw: Re:RE: EPICS exmaple application problem

["M.C.Shao" <ShaoMingchao97@mails.tsinghua.edu.cn>]

--
> >From:"Jeff Hill" <johill@lanl.gov>
> >
> >You might see this message in ordinary situations where the medm program
> >has lost communication with the IOC such as when the IOC powers down,
> >reboots, or its network cable is removed. This message might also occur
> >if there are software problems but it is difficult to speculate further
> >with this information. 
> >
> >What version of EPICS are you running?
> 
> my EPICS version is R3.14.0beta2
> 
> >Here are some steps you can follow to find the cause of the problem.
> >
> >1) Use the ping command from the medm workstation to verify that there
> >is network connectivity to your IOC.
> 
> yes, I could ping the ioc successfully.
> 
> >2) Verify that there is not a CPU saturation problem on your RTEMS IOC
> >where 100% of the CPU is consumed.
> 
> No, there is not such problem.
> 
> >3) Did the medm screen only disconnect briefly and then reconnect on its
> >own? Temporary disconnect problems existed in one of the early beta
> >releases of R3.14.
> 
> After turned to "execute" mode, the medm mornitor screen is white always.
> And the client exception message come out again and again, described in last
> mail.
> 
> >4) If not, does another program such as caEventRate connect to the IOC
> >in this situation?
> 
> when I use "caEventRate root:aiExample", it return nothing, and without error.
> On the ioc side, issue a "casr" command, I could see the connection like this:
> epics>casr
> Channel Access Server V4.11
> 166.111.32.251:32798(): User="", V4.0, Channel count=0, Priority=0
> ...
> when use medm, there is a record like above too.
> 
> 
> >Jeff
> >
> >
> best wishes,
> 
> Shao Mingchao
> Tsinghua University,Beijing,China
> 
> 
>