FC AG_SEND and AG_RECEIVE

cfbosch

Member
Join Date
Jun 2008
Location
Gauteng
Posts
15
AG_SEND keeps reporting Error 8183: No configuration or the service has not yet started on the Ethernet CP.

Under module information on the CP-> operating mode-> status information, it does report the service is in STOP, supplying a reason: not configured.

Where does one configure it other than netpro?

I have an ISO on TCP connection configured in NetPro for both CPUs. The send and receive calls' block parameters are set up as in the connection properties by netpro. The industrial ethernet network segment is connecting both CP cards on the two PLCs.
These are 313C and 313C-2 CPUs

Can anyone point out what I'm missing? Please?
 
Hi cfbosch.

There was one thread where the problem was that the CPU was incompatible with AG_SEND/AG_RECV. What type # and firmware do the CPUs and CPs have ?

Also, do you have ONE project with both CPUs ?
And, have you downloaded from NetPro to both Stations ?
 
Hi Jasper - man, you've helped me out on all my posts if I'm not mistaken!

The PLCS are:

6ES7 313-6CF03-0AB0 (I used V 2.6, how critical is having the exact version? Physically it might be a 2.6.1 - it's 700m down a mine, can't go look)

and
6ES7 313-6CF03-0AB0 V2.0 (V2.0 in hw config - Physically is a 2.0.12)


Yes, downloaded in Netpro to each station, and yes, both PLCs in one step7 project
 
I dont know the exact relation between the CP343-1 and the required CPU and firmware version. Maybe it is stated in the doc for the CP343-1. If you find out that this is the problem, then maybe a firmware update can do the trick.

I have found many times that a simple power cycle does wonders when you have changed the configuration. Have you done that ? Since it takes a 700 m descent to cycle the power, I guess that maybe you skipped this step ?

You forgot to state the details for the CP343-1 modules. Is important too.

Also, try to investigate the diagnostics buffer of the CP343-1 modules, not just the CPUs.

edit: I dont think I have ever responded to one your posts before, so if I have helped you before, then it must be because you have investigated previous threads rather than just starting a new one.
That deserves a pat on the back. :)
 
Last edited:
I've only cycled power on the surface PLC - I'll try the power cycle on the underground PLC tonight - have to wait for the pumps to shut down @ 18:00 GMT+2 so I can't give you an immediate answer.

Thanks Jesper



The CPs are 343-1CX10-0XE0 V2.0

The diagnostic buffer is at the end of this post - all I saw was:

Surface CP:
The new system data download info and the IO enable (with previous disables) so with my lacking experience I can't say I see any info in the diag buffer that points to worrying issues.

Surface CPU:
Just the stop/startup/run regarding the download.

Underground CP:
Same as surface, some network cable disconnects and reconnects from when I was down there on Thursday.

Underground CPU:
Nothing of interest - read errors from remote IO that probably did not have power for a while on Thursday.










Surface:
========


Diagnostic buffer of module CP 343-1 Lean
Order No./ Description Component Version
6GK7 343-1CX10-0XE0 Hardware 3
- - - Firmware V 2.0.16
Boot Rom Firmware expansion V 1.17.1
Rack: 0
Slot: 4

Event 1 of 41: Event ID 16# F9C1:0220
I/O enable by S7 CPU
External error, Incoming event
06:24:29.274 PM 01/04/1994

Event 2 of 41: Event ID 16# F9C1:0215
Downloading the module database causes module restart
External error, Incoming event
06:24:29.270 PM 01/04/1994

Event 3 of 41: Event ID 16# F9C1:0627
The SIMATIC mode was selected automatically for synchronizing the internal clock. Forwarding the time of day is not activated.
External error, Incoming event
06:24:28.451 PM 01/04/1994

Event 4 of 41: Event ID 16# F9C1:0266
Module STOP due to modification of the database.
External error, Incoming event
06:24:28.350 PM 01/04/1994

Event 5 of 41: Event ID 16# F9C1:0A06
A new IP address was assigned by a STEP 7 configuration. IP address: 192.168.0.201
External error, Incoming event
06:24:28.252 PM 01/04/1994

Event 6 of 41: Event ID 16# F9C1:0A01
A new IP address is expected from a STEP 7 configuration.
External error, Incoming event
06:24:28.252 PM 01/04/1994

Event 7 of 41: Event ID 16# F9C1:0221
I/O disable by S7 CPU
External error, Incoming event
06:24:22.338 PM 01/04/1994









Diagnostic buffer of module CPU 313C
Order No./ Description Component Version
6ES7 313-5BF03-0AB0 Hardware 1
- - - Firmware V 2.0.12
Rack: 0
Slot: 2

Event 1 of 10: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered via MPI; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered via MPI; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
03:02:40.534 PM 12/01/2008

Event 2 of 10: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"
Startup information:
- Startup without modified system configuration
- No difference between setpoint and actual configuration
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered via MPI; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered via MPI; last power on backed up
Requested OB: Startup OB (OB100)
Priority class: 27
Incoming event
03:02:40.533 PM 12/01/2008

Event 3 of 10: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by PG stop operation or by SFB 20 "STOP"
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered via MPI; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of the automatic startup type at power on:
- Warm restart triggered via MPI; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
03:02:40.134 PM 12/01/2008

Event 4 of 10: Event ID 16# 4304
STOP caused by PG stop operation or by SFB 20 "STOP"
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Incoming event
03:02:33.791 PM 12/01/2008




Underground:
============


Diagnostic buffer of module CP 343-1 Lean
Order No./ Description Component Version
6GK7 343-1CX10-0XE0 Hardware 3
- - - Firmware V 2.0.16
Boot Rom Firmware expansion V 1.17.1
Rack: 0
Slot: 5

Event 1 of 25: Event ID 16# F9C1:0259
Netinterface port 1: Automatic setting, TP/ITP with 100 Mbps full duplex
External error, Incoming event
04:35:13.019 PM 01/02/1994

Event 2 of 25: Event ID 16# F9C1:025A
Netinterface port 2: no Link
External error, Incoming event
04:33:59.399 PM 01/02/1994

Event 3 of 25: Event ID 16# F9C1:0259
Netinterface port 2: Automatic setting, TP/ITP with 100 Mbps full duplex
External error, Incoming event
04:21:14.151 PM 01/02/1994

Event 4 of 25: Event ID 16# F9C1:025A
Netinterface port 2: no Link
External error, Incoming event
04:17:55.771 PM 01/02/1994

Event 5 of 25: Event ID 16# F9C1:025A
Netinterface port 1: no Link
External error, Incoming event
03:14:59.118 PM 01/02/1994

Event 6 of 25: Event ID 16# F9C1:0259
Netinterface port 2: Automatic setting, TP/ITP with 100 Mbps full duplex
External error, Incoming event
03:14:53.609 PM 01/02/1994

Event 7 of 25: Event ID 16# F9C1:0220
I/O enable by S7 CPU
External error, Incoming event
03:13:58.922 PM 01/02/1994

Event 8 of 25: Event ID 16# F9C1:0215
Downloading the module database causes module restart
External error, Incoming event
03:13:40.078 PM 01/02/1994

Event 9 of 25: Event ID 16# F9C1:0627
The SIMATIC mode was selected automatically for synchronizing the internal clock. Forwarding the time of day is not activated.
External error, Incoming event
03:13:39.279 PM 01/02/1994

Event 10 of 25: Event ID 16# F9C1:0266
Module STOP due to modification of the database.
External error, Incoming event
03:13:39.194 PM 01/02/1994

Event 11 of 25: Event ID 16# F9C1:0A06
A new IP address was assigned by a STEP 7 configuration. IP address: 192.168.0.95
External error, Incoming event
03:13:39.160 PM 01/02/1994

Event 12 of 25: Event ID 16# F9C1:0A01
A new IP address is expected from a STEP 7 configuration.
External error, Incoming event
03:13:39.160 PM 01/02/1994

Event 13 of 25: Event ID 16# F9C1:0221
I/O disable by S7 CPU
External error, Incoming event
03:09:36.373 PM 01/02/1994
 
Thanks Jesper - the project is too large for this site though. I'll have to continue tomorrow - have to make arrangements to go underground. I'll let you know how it goes
 
Hi Jesper

Thanks for all the help - many and many times over and over!

The power cycle did not work - but low and behold - I deleted the system data on both containers for the PLCs in the project, recompiled and saved their HW configs to regen these, went to NetPro, recompiled and saved there, back to HW config, recompiled and saved there to iteratively get all the changes from the one side to the other worked out - downloaded to both stations in HW config, Manager, and Netpro -

and then it started working.

What do you recommend with the order between compiling and saving in HW config and compiling and saving in NetPro?

If you download from NetPro, does it transport all the blocks, or just the network data? (I cannot test, I was pushed for time and I don't have the luxury of a PLC to test with) - so EG can one download from NetPro as a rule, rather than downloading in HW config and then downloading blocks from Manager?

So at least I learned - hard way yet again, but hey, does one EVER learn the easy way?
 
Congrats that you got it working. :)

What do you recommend with the order between compiling and saving in HW config and compiling and saving in NetPro?
HW Config first.
Then NetPro.
Then all data and code blocks from the Simatic Manager.

If you download from NetPro, does it transport all the blocks, or just the network data?
Downloading from NetPro will download just the changed network connections.
 

Similar Topics

Hello All, Currently I am migrating S7 300 to S7 1500 & I am unable to use DP send & receive data from Master PLC. Which instruction is...
Replies
4
Views
1,589
All, I am up a creek and not only did I lost my paddle, but the creek is on fire. What I am attempting to do is to connect Wonderware System...
Replies
2
Views
2,252
Hello every one ... i want to know if the communication functions " AG SEND " and "AG RECEIVE" works with TCP only ? or with other communication...
Replies
5
Views
2,586
Hey guys, I hae an RSLinx that will not connect. So what I have is 5 machines, communicating in series from a DH485 to a coupler to ethernet to a...
Replies
2
Views
1,365
Send/Receive Data(ethernet comm..) between CPU 315-2 DP & S7-1200 OVER CP 343-1 Lean I have 2 programs. In 1.(first program ) my hardware...
Replies
0
Views
2,649
Back
Top Bottom