FW: medm question of simDetectorIOC

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

The problem was just a typo in the prefix.

 

From: timesir <mrlong336 at gmail.com>
Sent: Wednesday, August 16, 2023 12:42 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Subject: Re: medm question of simDetectorIOC

 

thank you very much. it works. :)

 

Mark Rivers <rivers at cars.uchicago.edu> 于2023年8月17日周四 01:05写道：

The example IOC in ADSimDetector uses the prefix 13SIM1:.  You started medm with 13SIM_1:, i.e. with an underscore.  That could be the problem.

 

Mark

 

 

From: timesir <mrlong336 at gmail.com>
Sent: Wednesday, August 16, 2023 11:21 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Subject: Re: medm question of simDetectorIOC

 

Yes, they are running on the same machine and the firewall is down.

 

Mark Rivers <rivers at cars.uchicago.edu> 于2023年8月17日周四 00:00写道：

The problem is almost certainly that EPICS Channel Access is not able to connected from the medm client to the simDetector IOC.

 

• Are medm and the IOC running on the same machine?
• Is there a firewall running on that machine?  If yes then it needs to allow ports 5064 and 5065 for UDP and TCP, or be disabled.
• If they are on different machines have you set any of the EPICS_CA_* environment variables?  Normally you don’t need to.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of timesir via Tech-talk
Sent: Wednesday, August 16, 2023 10:57 AM
To: tech-talk at aps.anl.gov
Subject: medm question of simDetectorIOC

 

Hi all,

1. start IOC
../../bin/linux-x86_64/simDetectorApp st.cmd
2. start medm
  cd areaDetector/ADSimDetector/simDetectorApp/op/adl
  medm -x -macro "P=13SIM_1:, R=cam1:" simDetector.adl

The following picture shows the effect of medm after startup, why is there nothing in the picture?