You can verify this by using the monitoring capability of the moxa
device. If tcp/ip ports stay connected indefinitely after the ioc exits,
then you will have to find a way to explicitly close the sockets. While
this might be true for VxWorks, I doubt it is true under linux. So, also
take a look at the moxa time-out/stay-alive/etc. configuration options.
I also use (and highly recommend) the MOXA N-PORT 5600 and do see that
some small amount of time is required before the connection can be re-
established but the connections do eventually close (there is some moxa
configuration that affects this behavior, but I can't remember the
details).
John Sinclair
On Fri, 2006-07-28 at 11:38 -0700, Emmanuel Mayssat wrote:
> I believe the number of connections to those MOXA is limited to a small
> number.
> The MOXA must consider that the maximum number of connections is
> currently open. Hence, the telnet to port 23 or 80 or any other do not
> work.
>
> To close the connection/socket on exit, you have to modify your iocsh.
> There was a thread on how to do this not so long ago.
>
> Hope this help,
>
> --
> E
>
> On Fri, 2006-07-28 at 14:26 -0400, John Dobbins wrote:
> > Dear All,
> >
> > I am using a MOXA N-PORT 5600, EPICS R3.14.7, ASYN 4-2-1. I have 8 serial
> > devices connected to the N-Port. Device support is based on ASYN using
> > drvAsynIPPort. The IOC is a soft IOC running on Linux (SL3).
> >
> > Sometimes when I restart the IOC by typing "exit" at the ioc command line the
> > MOXA will crash, by which I mean it will no longer respond on any of the ports
> > including the web server and telnet ports. The only way to recover the MOXA is
> > to cycle power.
> >
> > I am wondering if anyone else has had a similar experience and what advice
> > people might have for understanding this.
> >
> > Regards and thanks,
> >
> > John Dobbins
> >
> > Cornell Laboratory for Accelerator Sciences and Education
> > Cornell University
> > Ithaca, NY
> >
> >
>