Sign in to follow this  
Followers 0
Graham EDL

PLC5 DH+ to Prosoft Gateway Channel Lockout

4 posts in this topic

Hi.

I have a DH+ network with several PLCs, an Engineering station and a PRosoft ANX Gateway. I am using the gateway to read data files from the PLCs to a CLX then to my HMI.

 

PLC-1 has 2 data files

PLC-2 has 2 data files

PLC-3 has 3 data files

PLC-4 has 12 data files. (one of these, F8, has length of 395 and takes around 4000ms to read.)

PLC-4 also has a couple of write Messages that are sent on change of datafile entry and only a few times a day, for alarm resets and setpoint changes.

 

My issue is that one of my PLC-4 (PLC5/40B) stops communicating through Channel 1A (Node Address 7) to the gateway when it is getting requests from the CLX. All messages are in a queue that waits for 200ms from previous read .DN before initiating the next read. The queue has the PLC data file separated as much as possible.

eg

PLC-4/1 then

PLC-4/2 then

PLC-1/1 then 

PLC-4/3 then

PLC-1/2 then

etc.

 

I have to then change the DH+ cable to Channel 2A (Node address 5) and change my MESSAGE blocks in CLX to read from that node instead.

 

I cannot go online to PLC-4 at Node address 7 as it is not seen in Linx but when I go to node address 5 I can get in through the back door and go online. I am unable to communicate with, say, PLC-1 from PLC-4 when I make a new MESSAGE block in PLC-4 (reading into node 5).

 

When I connect another Gateway DH+ cable to node address 7 I can see the gateway in Linx but not address 7.

 

It's like Channel 1A has locked, so how do I unlock while the PLC is running? Before I've had to cycle power to the CPU to restore comms.

 

Thanks in advance.  

 

Share this post


Link to post
Share on other sites
1 hour ago, Graham EDL said:

I am unable to communicate with, say, PLC-1 from PLC-4 when I make a new MESSAGE block in PLC-4 (reading into node 5).

I can communicate between PLCs when I make a new MESSAGE block but not when I do a copy-paste of an existing one.

Share this post


Link to post
Share on other sites

With our process shut down I tried to change the key position from REM-PROG-RUN-REM to see if it would reset my locked port but no joy. Eventually had to cycle power to the PLC to restore the comms, which are now working in both channels, for now.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0