| View previous topic :: View next topic |
| Author |
Message |
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
 Posted: 26/05/2018 15:46 Post subject: Cimplicity connection failure |
 |
|
Good morning, I have a project in cimpliciy version 4.01 service pack 10.
A few days ago I get a connection error .
"26/05/2018 15.32.27 Failure 1892 TCPIP0 hct_9070_read_da -9
Device: PLC_ANALISI: Timeout occurred while waiting for an HCT request to compl
Error of type: COR_DCRP_ERR, Code: 20016"
Is it possible to know the cause?
Thank you |
|
| Back to top |
|
 |
gebnizz
Junior
Joined: 24 May 2018
Posts: 2
|
| Posted: 26/05/2018 19:59 Post subject: Re: Cimplicity connection failure |
|
|
| Glave wrote: | Good morning, I have a project in cimpliciy version 4.01 service pack 10.
A few days ago I get a connection error .
"26/05/2018 15.32.27 Failure 1892 TCPIP0 hct_9070_read_da -9
Device: PLC_ANALISI: Timeout occurred while waiting for an HCT request to compl
Error of type: COR_DCRP_ERR, Code: 20016"
Is it possible to know the cause?
Thank you |
Verify the Port Configuration
| Code: | After you have configured your ports and started your CIMPLICITY project, you can check the Status Log to verify that each marquee resident process was able to connect to its configured port on the terminal server.
Successful connections.
Write errors.
Communication failures.
Successful Connections
For each port, an entry will appear in the Status Log similar to the following:
8/14/97 6:00:00PM Success PORT1 ReaderThread COR_DCRP_ERROR 20016 0 connection established: 1600@3.26.7.171, port=PORT1
This entry indicates that for process PORT1, a successful connection was made to telnet port 1600 on the terminal server whose IP address is 3.26.7.171.
Write Errors
Occasionally, you may see the following warning message in the Status Log:
8/14/97 6:00:00PM Failure PORT1 dc_telnet_write_windows_tty COR_DCRP_ERR 20016 0 write failure,port=PORT1
This message indicates that a write error occurred. The Marquee Resident process will automatically attempt to resend the message to the marquee.
Communication Failures
You may see the following failure message in the Status Log:
8/14/97 6:00:00PM Failure PORT1 dc_telnet_write_windows_tty COR_DCRP_ERR 20016 0 connection reset, 1600 @ 3.26.7.171, port=PORT1 |
This Status Log entry indicates that the Marquee Resident process is unable to communicate with the port on the terminal server. It resets the IP connection and attempts to re-establish communications with the port. Check your network state, network connections and your terminal server configuration if you receive this message.
Set up the Terminal Server
Each port on the terminal server to which a marquee is connected must be configured for TCP/IP communications. Use the following steps to configure your terminal server:
| Code: |
Log into your terminal server, and set privileged mode by issuing the following command. Enter the privileged password when prompted (typically "system"):
> set priv
Password>
Enter the following command so that the permanent database and the operational database will be updated when a define command is issued:
>> set server change enabled
For each port to which a marquee is attached, enter the following set of commands where:
<port> is the actual port number to which the marquee is attached. Note that it is possible to specify a range of port numbers instead of a single port (for example, 1-10 signifies ports 1 through 10).
<ip_port> is the telnet port number.
<parity> is odd, even, or none.
<stop> is the number of stop bits.
<speed> is the baud rate of the marquee.
>> define port <port> access remote
>> define port <port> telnet remote <ip_port>
>> define port <port> telnet transmit immediate
>> define port <port> parity <parity>
>> define port <port> character size 8
>> define port <port> stop bits <stop>
>> define port <port> autobaud disabled
>> define port <port> speed <speed>
>> define port <port> line editor disabled
>> define port <port> telnet csi escape enabled
>> define port <port> telnet binary session mode passall
>> define port <port> loss notification disabled
>> define port <port> autoprompt disabled
>> define port <port> verification disabled
>> define port <port> outboundsecurity disabled
>> define port <port> broadcast disabled
>> define port <port> default session mode transparent
>> define port <port> internet tcp keepalive 2 |
To utilize a terminal server port instead of a standard serial port, you must map the logical port name configured within your CIMPLICITY project to an actual physical port on the terminal server.
Configure a CIMPLICITY Terminal Server Port
| Code: | Select the Project Parameters section in the Workbench.
Enter the value for the appropriate project parameter.
TSERV_<PORT>
TSERV_<COM>
Note: CIMPLICITY will update the glb_parms.idt file with your entries.
At startup, the Marquee resident process will check the glb_parms.idt file for each Marquee port that is configured. If an entry exists, it will use the corresponding Terminal Server port for its communication.
You make an entry for each port to which a marquee is attached.
Important: When configuring ports in the Marquee Ports configuration window, a given marquee resident process can control at most one port on a terminal server.
In addition, a given port on a terminal server can be controlled by at most one Marquee process. Thus, when configuring ports in CIMPLICITY:
Be sure to specify a unique Service ID for each port to be controlled on the terminal server.
Make sure that two CIMPLICITY projects do not attempt to control the same terminal server port.
|
|
|
| Back to top |
|
|
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
| Posted: 26/05/2018 21:16 Post subject: |
|
|
The project initially connects to the "MASTER_TCPIP0" port, then after a few minutes it disconnects, then reconnects and so always.
My project involves two PLCs geFanuc 9030, PLC1 and PLC2, PLC1 every period of time disconnects from the TCPIP network, PLC2 is always connected. |
|
| Back to top |
|
|
gebnizz
Junior
Joined: 24 May 2018
Posts: 2
|
| Posted: 30/05/2018 12:15 Post subject: |
|
|
I have to repeat...
Check your network state, network connections and your terminal server configuration if you receive this message. |
|
| Back to top |
|
|
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
| Posted: 31/05/2018 06:10 Post subject: |
|
|
Resolved, some company employee installed a printer in the same Plc network and put the tcpip address equal to one of the two PLCs.
Thank you all for your help. |
|
| Back to top |
|
|
Anthony_34
Junior
Joined: 18 Aug 2016
Posts: 5
|
| Posted: 30/06/2018 03:16 Post subject: |
|
|
| Hi. Do you have cimplicity 4.01 Installer? |
|
| Back to top |
|
|
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
| Posted: 30/06/2018 13:50 Post subject: |
|
|
| Anthony_34 wrote: | | Hi. Do you have cimplicity 4.01 Installer? |
Yes, cimplicity v4.01 and svpk 10 |
|
| Back to top |
|
|
Anthony_34
Junior
Joined: 18 Aug 2016
Posts: 5
|
| Posted: 01/07/2018 06:38 Post subject: |
|
|
| can you get me download link for cimpicity 4.01 installer? |
|
| Back to top |
|
|
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
| Posted: 01/07/2018 20:48 Post subject: |
|
|
| Anthony_34 wrote: | | can you get me download link for cimpicity 4.01 installer? |
I'll put the link on you soon |
|
| Back to top |
|
|
Glave
Junior
Joined: 12 May 2016
Posts: 6
|
| Posted: 02/07/2018 12:09 Post subject: |
|
|
| Glave wrote: | | Anthony_34 wrote: | | can you get me download link for cimpicity 4.01 installer? |
I'll put the link on you soon |
http://www.mediafire.com/file/uhe8c4xa8jrsgik/HMI.rar/file |
|
| Back to top |
|
|
Anthony_34
Junior
Joined: 18 Aug 2016
Posts: 5
|
| Posted: 02/07/2018 22:09 Post subject: |
|
|
| thanks for the download link. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
